The correct option is Ask Copilot to build an end to end test that sends HTTP requests to the Cloud Run route and checks that users 21 or older can view restricted content while younger users are blocked.

This approach directs Copilot to exercise the real HTTP interface of the Cloud Run service so it validates routing, middleware, request parsing, the handler, and the integration with the age helper in one flow. It verifies that users who are at least 21 receive an allowed response and that younger users are blocked, which proves the enforcement logic works where it actually matters at the service boundary.

By testing through the service URL you can catch issues that unit tests often miss such as misconfigured authentication, incorrect status codes, or handler logic that fails to apply the helper result. This gives confidence in the full behavior of the deployed service rather than only the internal function.

Generate unit tests with Copilot for only the is_of_age check and assume that integration is covered elsewhere is incorrect because it isolates the helper and does not validate the HTTP handler, routing, or responses, so it cannot prove the service enforces the restriction correctly.

Cloud Monitoring is incorrect because it is an observability product for metrics and logging. It does not generate or execute tests and it does not validate end to end request behavior.

Instruct Copilot to ignore web routing and verify only the return values from the is_of_age helper is incorrect because it explicitly avoids the HTTP path where access is enforced, so it would miss failures in authorization handling and response behavior.

Full AWS Practitioner Certification Question