A hospital network runs its patient-scheduling web application on 60 Linux servers in its own data centers, not on AWS. The servers are not in an Auto Scaling group and cannot be replaced by new instances.
Releases are copied to each server with scripts that stop the web service for several minutes. An error on one server has left the application half-upgraded in the past. The operations team wants releases to roll out in batches, with each server checked after its install and a failed release rolled back automatically.
The servers have outbound HTTPS access to AWS but no inbound access from the internet, and the team wants deployment records kept in AWS.
Which TWO actions meet these requirements? (Choose two.)
Choose two answers.
AA. Register each server with AWS CodeDeploy as an on-premises instance by using an IAM user or session ARN, and install the CodeDeploy agent on each server so that it polls the service over HTTPS.
BB. Deploy the application with AWS Systems Manager Run Command to all 60 servers at once, running the same install script, and check the results with a command status query afterward.
CC. Move the scheduling application onto Amazon EC2 instances in an Auto Scaling group behind a load balancer, and replace the data-center servers with rolling instance refreshes.
DD. Add a ValidateService hook to the AppSpec file that calls the application's health endpoint, and set a deployment configuration that updates the fleet in batches and rolls back automatically when a deployment fails.
EE. Keep the scripts, but run them as a cron job on each server every night, with a script that restarts the service and writes its log to a central file share.
B. Wrong: Run Command runs scripts across many servers at once, but it has no rolling batches and no automatic rollback. A failed install would still leave some servers upgraded and others not. Learn more: AWS Systems Manager Run Command (opens in a new tab)
D. Right: Correct. AppSpec lifecycle hooks such as ValidateService run checks after each install, and a deployment configuration sets how many servers update at once. Automatic rollback on failure stops a bad release from spreading across the batches. Learn more: AppSpec 'hooks' section (opens in a new tab)
E. Wrong: A nightly cron job does not provide batched rollouts or health gating, and the file share would be the only deployment record. It keeps the same risks that left servers half-upgraded.
Explanation
CodeDeploy can deploy to servers outside AWS once they are registered as on-premises instances and run the agent, which polls outbound only. AppSpec hooks run health checks after each install, and a deployment configuration limits how many servers update at a time and rolls back on failure. Run Command, cron jobs and an Auto Scaling migration do not give the same gating.
Want more on CodeDeploy on EC2 and on-premises (agent, AppSpec, hooks)? The 5 full-length practice sets have 9 more CodeDeploy on EC2 and on-premises (agent, AppSpec, hooks) questions, 375 in all, none of them in the free exam. One payment of $14.99, no subscription. See the practice sets →