The correct option is Require review and testing of AI generated code before merging or deploying.

Keeping humans in the loop through pull requests ensures that generated changes are understood and meet standards and avoid security or licensing issues. Automated pipelines in Cloud Build should run unit tests and linters and static analysis and dependency scans, and they should gate merges and releases on passing results. This approach lets you benefit from Copilot Chat while maintaining traceability and auditability.

Let GitHub Copilot Chat push commits directly to the main branch to save review time is incorrect because it bypasses peer review and continuous integration checks and it increases the risk of introducing defects or insecure code.

Configure Cloud Build to skip unit tests for AI generated code to speed up deployments is incorrect because AI output warrants at least the same level of scrutiny as human written code and skipping tests undermines reliability and security.

Use GitHub Copilot Chat to generate complete services without developer involvement is incorrect because developers must design, validate, and own the code and they must review architecture, performance, and security choices.

Full AWS Practitioner Certification Question