Examkin

Question

Difficulty: EasyRelease Management and Deployment Strategies (Blue-Green, Canary, Rolling)

Your team is releasing an updated revision of a microservice hosted on Cloud Run. To minimize the impact of potential software bugs, you want to route only 5% of production traffic to the new revision while keeping 95% of traffic on the existing stable revision. After verifying metrics such as latency and error rates, you plan to shift the remaining traffic. Which release management strategy is being implemented in this scenario?

  1. Canary deploymentAnswer
  2. B
    Blue-green deployment
  3. C
    Re-platforming to Google Kubernetes Engine (GKE) with full cluster replacement
  4. D
    Rolling update without verifying resource quota availability

Answer

Canary deployment
Canary deployment is a release management strategy where a small fraction of live traffic is directed to a newly deployed revision to monitor performance and error metrics in production before completing a full rollout.

Step-by-Step Solution

1
Identify the release requirement from the scenario
The scenario describes routing a small subset (5%) of live user traffic to a new release version while observing telemetry.
Gradually routing a small proportion of user traffic isolates potential defects to a minority of users.
2
Map the requirement to deployment strategies
Exposing a minor percentage of live traffic to validate a new revision before full promotion is the defining characteristic of a canary deployment.
Cloud Run traffic splitting directly supports canary deployment patterns by assigning percentage weights to target revisions.

Key Concept

Canary deployment strategy using Cloud Run traffic splitting
Estimated Time:1m 0s
Rate this question

Topics

Release Management and Deployment Strategies (Blue-Green, Canary, Rolling)