You want to gradually roll out a new version of a payment service to 10% of users while keeping 90% on the old version. Which traffic management strategy is best suited for this?

hard📝 Trade-off Q15 of 15

Microservices - Service Mesh

AUse routing based on URL path to send 10% of requests to new service

BUse traffic splitting with weights 90% to old and 10% to new service

CDeploy both versions without traffic control and monitor errors

DUse a load balancer that randomly sends requests without weights

Step-by-Step Solution

Solution:

Step 1: Understand gradual rollout needs
Gradual rollout means controlling what percentage of users see the new version.
Step 2: Choose traffic management method
Traffic splitting with weights allows precise control of request percentages to each version.
Step 3: Evaluate other options
Routing by URL path cannot split traffic by percentage. Random load balancing lacks control. Deploying without control risks all users seeing new version.
Final Answer:
Use traffic splitting with weights 90% to old and 10% to new service -> Option B
Quick Check:
Splitting controls rollout percentages [OK]

Quick Trick: Use weighted splitting for gradual rollout [OK]

Common Mistakes:

MISTAKES

Using URL path routing for percentage split
Ignoring traffic control during rollout
Relying on random load balancing

Master "Service Mesh" in Microservices

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Arch Try Challenge Design Recall Scale

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Microservices Quizzes

You want to gradually roll out a new version of a payment service to 10% of users while keeping 90% on the old version. Which traffic management strategy is best suited for this?

Step 1: Understand gradual rollout needs

Step 2: Choose traffic management method

Step 3: Evaluate other options

Final Answer:

Quick Check:

Want More Practice?