AWS Certified Cloud Practitioner (CLF-C02)Cloud Technology and ServicesMedium
An e-commerce company wants to route 80% of user traffic to a new application version and 20% to the legacy version to test performance before a full rollout. Which Route 53 routing policy should they configure?
- AFailover routing
- BWeighted routing
- CGeolocation routing
- DLatency-based routing
Show answer & explanationAnswer & explanation
Correct answer: B. Weighted routing
Weighted routing lets you assign relative weights to resource records, allowing traffic to be split by percentage between multiple versions of an application, ideal for canary testing or gradual rollouts.
Why the other options are wrong
- A. Failover routing is for active-passive disaster recovery, not controlled traffic splitting.
- C. Geolocation routing directs traffic based on user location, not percentage-based testing.
- D. Latency-based routing sends traffic to the region with lowest latency, not a specified percentage split.
Route 53 Weighted Routing
A routing policy that distributes traffic across multiple resources based on assigned weight values, useful for testing and gradual deployments.
- Weights determine traffic percentage
- Common for A/B testing and canary releases
- Weights can be adjusted dynamically
Memory trick: Weighted = Weigh out the traffic split