You have an application running on Cloud Run that receives a large volume of traffic. You need to deploy a new version of the application. You want your deployment process to minimize the risk of down

Question

Options

• AUse Cloud Run emulator to test changes locally before deploying the new version of the
• BUse Cloud Build to create a pipeline, and configure a test stage before the deployment stage.
• CUse Cloud Load Balancing to route a percentage of production traffic to a separate Cloud Run
• DUse traffic splitting to have a small percentage of users test out new features on the new revision

• A
  11% (4)
• B
  14% (5)
• C
  5% (2)
• D
  70% (26)

Explanation

Cloud Run natively supports traffic splitting between revisions, making it the idiomatic Google-recommended approach for low-risk deployments. By routing a small percentage (e.g., 5–10%) of live traffic to the new revision, you can validate behavior in production with real users, monitor error rates and latency, and either gradually increase traffic or roll back instantly - all without downtime. Option A (Cloud Run emulator) helps with pre-deployment testing but does not address production deployment risk. Option B (Cloud Build pipeline) improves CI/CD but does not directly minimize deployment downtime. Option C (Cloud Load Balancing with a separate service) is a heavier blue/green approach that is more complex to manage than Cloud Run's built-in revision traffic splitting.

No community discussion yet for this question.