DOP-C02 Question 268
Single answerYour company is running a highly available web application hosted on Amazon EC2 instances behind an Application Load Balancer (ALB) in multiple Availability Zones. To optimize the deployment process, you are using AWS CodePipeline integrated with AWS CodeDeploy to perform blue/green deployments. During a recent deployment, you noticed some users experienced downtime due to DNS propagation delays when switching traffic between environments. How can you minimize downtime for future deployments while using blue/green strategies?
- A
Use an Application Load Balancer with weighted routing to gradually shift traffic between the old and new environments.
- B
Configure CodeDeploy to use an Elastic Beanstalk environment for deployment, which automatically manages DNS propagation.
- C
Integrate Amazon Route 53 with CodeDeploy and leverage weighted DNS records to control traffic distribution during the deployment.
- D
Manually update the DNS records in Route 53 to point to the new environment after the deployment.
Show answer and explanation
Correct answer: C
Explanation
To minimize downtime during blue/green deployments, it is crucial to control traffic distribution without relying on DNS propagation. Amazon Route 53 supports weighted DNS records, which allow gradual or immediate traffic shifting between environments. Integrating Route 53 with AWS CodeDeploy ensures a streamlined and automated process for managing traffic during deployments, reducing the risk of downtime.
- A. Incorrect.
Incorrect. While Application Load Balancers can handle traffic shifting, they do not address DNS propagation delays since they are not directly tied to DNS record management.
- B. Incorrect.
Incorrect. Elastic Beanstalk simplifies application deployment but does not eliminate DNS propagation delays, and it is not specifically designed to integrate with CodeDeploy for blue/green deployments.
- C. Correct.
Correct. By integrating Route 53 with CodeDeploy and using weighted DNS records, you can control traffic gradually without waiting for full DNS propagation, thereby minimizing downtime.
- D. Incorrect.
Incorrect. Manually updating DNS records introduces delays and risks errors during the deployment process, making it unsuitable for minimizing downtime in blue/green deployments.