Answer-first summary for fast verification
Answer: Update the current service with the new changes. Deploy the new revision with no traffic allocated. Split the traffic between the current service and the new revision.
To test the new revision on 10% of traffic while maintaining backward compatibility with minimal effort, the correct approach involves deploying the new revision with 0% traffic initially. This ensures the existing revision (current service) continues handling 100% of traffic. After deployment, traffic is split between the previous revision (still serving requests) and the new revision. Option C correctly describes this process: updating the current service (deploying a new revision) with no traffic allocated, then splitting traffic between the current service's active revision (which remains the previous one until traffic is adjusted) and the new revision. Options A and D incorrectly refer to replacing the service or using a load balancer, which adds unnecessary complexity. Option B would route all traffic to the new revision immediately, which is not desired.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You have a production application running on Cloud Run. Your team needs to modify one of the application's services to return a new field. You want to test the new revision with 10% of your traffic while minimizing effort and maintaining backward compatibility.
What should you do?
A
Replace the current service with the new revision. Deploy the new revision with no traffic allocated. After the deployment, split the traffic between the previous service and the new revision.
B
Update the current service with the new changes. Deploy the new revision. After the deployment, split the traffic between the current service and the new revision.
C
Update the current service with the new changes. Deploy the new revision with no traffic allocated. Split the traffic between the current service and the new revision.
D
Replace the current service with the new revision. Deploy the new revision. Create a load balancer to split the traffic between the previous service and the new revision.
No comments yet.