AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A financial services company runs a critical API on a fleet of Amazon EC2 instances within an Auto Scaling group (ASG) behind an Application Load Balancer (ALB). The current deployment process, which replaces all instances at once, causes brief but unacceptable service interruptions. The company needs to implement a new CI/CD strategy that eliminates downtime and minimizes the 'blast radius' of a potentially faulty deployment. However, due to strict budgeting, they want to avoid provisioning a full, parallel set of infrastructure for each deployment. Which deployment strategy should a Solutions Architect recommend?
Implement a blue/green deployment strategy by creating a new, identical Auto Scaling group for the new version and then shifting all ALB traffic once it passes tests.
Implement a canary deployment by provisioning a new, smaller Auto Scaling group to receive a small percentage of traffic before manually scaling it up to replace the old fleet.
Configure AWS CodeDeploy to perform an all-at-once deployment, which stops the application on all existing instances and deploys the new version simultaneously for speed.
Implement a rolling update strategy on the existing Auto Scaling group, replacing a small percentage of instances in batches and using ALB health checks to validate each batch.
The correct answer is to implement a rolling update strategy. A rolling update incrementally replaces instances in the existing Auto Scaling group with new instances running the updated application version. This approach meets all the specified requirements:
It eliminates downtime by ensuring a minimum number of instances are always in service and passing health checks before old instances are terminated.
It minimizes the blast radius because if a bug is detected, only the small batch of newly updated instances is affected, and the update can be rolled back.
It is cost-effective because it reuses the existing infrastructure without needing to provision a full parallel environment.
A blue/green deployment is incorrect because it explicitly requires provisioning a full parallel 'green' environment, which violates the cost constraint of avoiding a duplicate set of infrastructure.
An all-at-once deployment is incorrect because it is the strategy currently in use that causes service interruptions. It updates all instances simultaneously, leading to downtime.
A canary deployment with a separate, smaller fleet is incorrect. While it excels at limiting blast radius, creating a separate fleet (even a small one) still introduces additional infrastructure and complexity not required by a rolling update. The rolling update strategy inherently accomplishes the goal of incremental rollout within the existing infrastructure, making it the most direct and cost-effective solution for this scenario.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a rolling update strategy in AWS?
Open an interactive chat with Bash
How does a rolling update minimize the blast radius in deployments?
Open an interactive chat with Bash
What is the difference between a rolling update and blue/green deployment?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Continuous Improvement for Existing Solutions
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access