Your company is currently planning to use Route53 for managing Blue-Green deployments.
They have already set up an 80%-20% for a new deployment.
How can you ensure to stop sending traffic to the older setup once all testing is complete?
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - D.
The AWS Documentation mentions the following to support this answer.
Enter an integer between 0 and 255
To disable routing to a resource, set Weight to 0
If you set the Weight to 0 for all of the records in the group, traffic is routed to all resources with equal probability.
This ensures that you don't accidentally disable routing for a group of weighted records.
Options A and B are incorrect since you need to mark the resource record as 0.
Option C is incorrect because this will cause the reverse, and all traffic will flow to the application.
For more information on setting values for the weighted resource records, please refer to the below URL:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-values-weighted.htmlBlue-Green deployment is a method for releasing new versions of applications by creating a parallel environment (Green) identical to the existing environment (Blue). Once the new environment has been tested and deemed to be working correctly, traffic is routed to the new environment and the old environment is decommissioned. Amazon Route 53 is a Domain Name System (DNS) web service that provides reliable and scalable routing of end-users to applications running in the AWS cloud.
To manage Blue-Green deployments using Amazon Route 53, a weighted routing policy can be used. This routing policy directs traffic to different resources based on the weights assigned to each resource. In the context of a Blue-Green deployment, the traffic is directed to the Blue environment and the Green environment based on their respective weights.
To ensure that traffic is stopped to the older setup once all testing is complete, the following options are available:
A. Delete the weighted resource record: This option will remove the resource record for the older setup entirely. However, this will prevent any traffic from being routed to that resource, including rollback scenarios.
B. Change the resource record to a simple routing policy: This option will change the routing policy for the resource record to simple routing. With this option, the resource record will only contain a single IP address or endpoint, and all traffic will be routed to that endpoint. However, this will not provide a way to roll back to the previous version.
C. Change the resource record weight to 100: This option will set the weight of the new deployment to 100, indicating that all traffic should be directed to the new deployment. However, this will not provide a way to roll back to the previous version.
D. Change the resource record weight to 0: This option will set the weight of the older setup to 0, indicating that no traffic should be directed to the older setup. This option is preferred because it allows for a quick rollback in case of issues with the new deployment.
In summary, option D is the best option to ensure traffic is stopped to the older setup once all testing is complete because it provides a way to quickly rollback in case of issues with the new deployment.