Answer-first summary for fast verification
Answer: Run the gcloud run deploy booking-engine --no-traffic --tag dev command. Use the https://dev--booking-engine-abcdef.a.run.app URL for testing.
Option A is correct because the `gcloud run deploy` command with `--no-traffic` ensures the new revision is not exposed to customer traffic. The `--tag dev` assigns a tag, allowing developers to test the revision via the dedicated URL `https://dev--booking-engine-abcdef.a.run.app`. This isolates testing from the production environment. Option B routes all traffic to the latest revision, exposing it prematurely. Option C uses authentication but accesses the current public revision without isolation. Option D references a non-existent URL and fails to address revision-based testing.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
How can you enable developers to test the latest revisions of a Cloud Run-hosted service at https://booking-engine-abcdef.a.run.app via HTTPS requests before the service is made available to customers?
A
Run the gcloud run deploy booking-engine --no-traffic --tag dev command. Use the https://dev--booking-engine-abcdef.a.run.app URL for testing.
B
Run the gcloud run services update-traffic booking-engine --to-revisions LATEST=1 command. Use the https://booking-engine-abcdef.a.run.app URL for testing.
C
Pass the curl –H “Authorization:Bearer $(gcloud auth print-identity-token)” auth token. Use the https://booking-engine-abcdef.a.run.app URL to test privately.
D
Grant the roles/run.invoker role to the developers testing the booking-engine service. Use the https://booking-engine-abcdef.private.run.app URL for testing.
No comments yet.