You need to deploy a new feature into production on Cloud Run. Your company's SRE team mandates gradual deployments to avoid large downtimes caused by code change errors. You want to configure this de

Question

Options

• AConfigure the application's frontend load balancer to toggle between the new and old revisions.
• BConfigure the application code to send a small percentage of users to the newly deployed
• CDeploy the feature with "Serve this revision immediately" unchecked, and configure the new
• DDeploy the feature with "Serve this revision immediately" checked. Check for errors, roll back to

• A
  8% (3)
• B
  3% (1)
• C
  74% (29)
• D
  15% (6)

Explanation

Cloud Run natively supports traffic splitting between revisions. Deploying with 'Serve this revision immediately' unchecked means the new revision receives 0% of traffic upon deployment. You then configure a traffic split (e.g., 5% new, 95% old) directly in the Cloud Run console or via gcloud - this is the gradual rollout with minimal effort. Option D deploys immediately to 100% of traffic, which is the opposite of gradual. Option A requires configuring an external load balancer, which adds complexity. Option B requires application-level code changes, which adds development effort and is error-prone.

No community discussion yet for this question.