Medium1 markMultiple Choice
Domain 4.3: Managing Cloud Run resourcesCloud RunTraffic SplittingCanary DeploymentRevisions

GCP ACE · Question 36 · Domain 4.3: Managing Cloud Run resources

You have deployed version 1 (v1) of an application to Cloud Run. You just deployed version 2 (v2) and want to perform a canary release. You want 10% of user traffic to go to v2, while 90% remains on v1.

How should you configure this in Cloud Run?

Answer options:

A.

Deploy v2 to a separate Cloud Run service and configure a Global HTTP(S) Load Balancer to split traffic 90/10 between the two services.

B.

Use the Cloud Run traffic splitting feature to route 90% of traffic to the v1 revision and 10% to the v2 revision.

C.

Update the application code in v1 to randomly forward 10% of requests to the v2 endpoint.

D.

Cloud Run does not support traffic splitting; you must use GKE with Istio for this capability.

How to approach this question

Recognize that Cloud Run has built-in traffic management capabilities between revisions.

Full Answer

B.Use the Cloud Run traffic splitting feature to route 90% of traffic to the v1 revision and 10% to the v2 revision.✓ Correct
Use the Cloud Run traffic splitting feature to route 90% of traffic to the v1 revision and 10% to the v2 revision.
Cloud Run natively supports traffic splitting. Every time you deploy an update to a Cloud Run service, it creates a new 'Revision'. You can easily configure the service (via the Console or gcloud) to split incoming traffic across multiple revisions by specifying percentages (e.g., 90% to the old revision, 10% to the new revision). This makes canary deployments and A/B testing very straightforward without needing external load balancers or complex service meshes.

Common mistakes

Assuming you need an external Load Balancer or a complex tool like Istio to achieve simple traffic splitting in Cloud Run.

Practice the full GCP Associate Cloud Engineer Practice Exam 6

50 questions · hints · full answers · grading

More questions from this exam