Free AWS DVA-C02 Actual Exam Questions - Question 12 Discussion
There is a new version of the website that needs to be deployed in the Elastic Beanstalk
environment. The company cannot tolerate having the website offline if an update fails.
Deployments must have minimal impact and rollback as soon as possible.
B/D? Rolling could work by updating instances in batches to avoid downtime, but it risks partial failures. Immutable is safer because the whole environment is replaced atomically, ensuring immediate rollback.
This sounds like a classic case for immutable deployments (D) because they create a new set of instances and only switch traffic once those pass health checks. That way, if the update fails, the old environment is still up and running—no downtime. Rolling updates (B) could cause partial outages if something goes wrong mid-deploy, and all at once (A) definitely risks downtime. Snapshots (C) don’t really fit here since they’re about backups, not deployment strategies. Does anyone think rolling updates could still be safe enough with health checks, or is immutable definitely the safest bet?
A/B? Not sure if just installing the daemon (B) is enough or if you still need the SDK (A) to capture data inside the app itself. The question asks for least config though.