You have an application running in production on Cloud Run. Your team needs to change one of the application's services to return a new field. You want to test the new revision on 10% of your clients

Question

Options

• AReplace the current service with the new revision. Deploy the new revision with no traffic
• BUpdate the current service with the new changes. Deploy the new revision. After the deployment,
• CUpdate the current service with the new changes. Deploy the new revision with no traffic
• DReplace the current service with the new revision. Deploy the new revision. Create a load

• A
  15% (9)
• B
  3% (2)
• C
  73% (44)
• D
  8% (5)

Explanation

Cloud Run natively supports traffic splitting between multiple revisions. The correct approach is: deploy the new revision with 0% traffic (so it goes live without receiving requests), then configure traffic splitting to send 10% of traffic to the new revision and 90% to the existing one. This allows real user testing with minimal blast radius. Deploying with no traffic first is critical-it lets you verify the revision is healthy before routing any real clients to it. Options A and D describe replacing the service, which doesn't achieve a gradual rollout. Option B implies deploying and then splitting, but lacks the 'no traffic on deploy' step that makes the rollout controlled and safe.

No community discussion yet for this question.