Final answer:
To distribute traffic among A and B test versions of a web application and the current production version, a weighted routing policy should be utilized. This policy allows specific percentages of traffic to be allocated to each version, meeting the need for controlled traffic distribution during A/B testing.
Step-by-step explanation:
For rolling out A and B test versions of a web application and allocating specific percentages of traffic to each version, the appropriate routing policy to use is weighted routing. Weighted routing allows you to assign weights to different DNS records (which could be different versions of your web application), effectively distributing incoming requests according to those weights. In this scenario, you would assign a weight of 10 to version A, 10 to version B, and 80 to the current production version, assuming a weight total of 100 for simplicity. This ensures that 10 percent of your traffic is routed to version A, another 10 percent goes to version B, and the remaining 80 percent continues to your current production version.
Why not the other options?
- Simple routing doesn't support traffic distribution based on different weights; it's typically used for a single resource.
- Geolocation routing directs traffic based on the geographic location of the users, which is not relevant to this requirement.
- Failover routing is intended for active-passive failover setups and not for traffic distribution.