AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A media-analytics company runs a stateless REST API on Amazon EC2 instances that belong to an Auto Scaling group spread across two Availability Zones and fronted by an Application Load Balancer. Deployments are performed in-place with AWS CodeDeploy, using the default OneAtATime deployment configuration. Product management now mandates that production releases finish in under 1 minute. Brief downtime is acceptable, but every deployment must still roll back automatically if an Amazon CloudWatch alarm reports that more than 5 % of HTTP requests return 5xx errors.
As the lead solutions architect, which change to the deployment strategy will best satisfy the new release-time objective while requiring the least modification to the existing pipeline and still providing automatic rollback?
Switch the deployment type to a blue/green deployment that shifts traffic after the new version passes health checks.
Replace CodeDeploy with AWS Systems Manager Run Command to execute the installation script on every instance simultaneously and handle any rollback manually.
Update the CodeDeploy deployment group to use the predefined configuration CodeDeployDefault.AllAtOnce and retain the existing CloudWatch alarm-based automatic rollback.
Create a custom rolling deployment configuration that updates 25 % of instances at a time to reduce risk while shortening overall deployment duration.
The predefined deployment configuration CodeDeployDefault.AllAtOnce deploys the new revision to all instances in the deployment group simultaneously, completing in the shortest possible time. Because it is still an AWS CodeDeploy in-place deployment, existing CloudWatch alarms and the automatic-rollback setting on the deployment group continue to function without additional changes.
Blue/green traffic-shifting deployments would add the complexity of maintaining two environments and would take longer than 1 minute because health checks must pass before traffic is shifted. Custom rolling configurations (for example, HalfAtATime or other percentages) still deploy in multiple batches, so total deployment time exceeds the 1-minute target. Using AWS Systems Manager Run Command removes CodeDeploy's built-in health tracking and automatic rollback, requiring custom scripting to achieve equivalent safety.
Therefore, updating the deployment group to use CodeDeployDefault.AllAtOnce while keeping the existing CloudWatch alarm-based automatic rollback meets all stated requirements with minimal pipeline changes.
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 CodeDeployDefault.AllAtOnce, and why is it suitable for this use case?
Open an interactive chat with Bash
How does AWS CodeDeploy handle automatic rollback using CloudWatch alarms?
Open an interactive chat with Bash
What is the difference between in-place and blue/green deployments in AWS CodeDeploy?
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