SAP-C02 Continuous Improvement for Existing Solutions Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Deploy a new version to a single instance, test, then scale out.

  Why it's wrong here

  Testing on one instance then scaling out leaves the remaining fleet on the old version during the test, and a failed test still requires manual intervention to revert. It is tempting as a canary-style approach, but it does not shift traffic atomically or provide the instant rollback the scenario demands.

• ✓

  Use blue/green deployment with a second Auto Scaling group and switch the ALB target group.

  Why this is correct

  Blue/green deployment with a second Auto Scaling group satisfies the zero-downtime and quick-rollback constraints: the new version runs in a parallel environment, and the ALB listener shifts traffic by swapping target groups. Rollback is a single target-group switch back, avoiding the gradual instance replacement and mixed-version window of rolling updates.

• ✗

  Perform rolling updates with a single Auto Scaling group, updating a few instances at a time.

  Why it's wrong here

  Rolling updates replace instances gradually within one Auto Scaling group, so both versions serve traffic simultaneously and reverting means re-running the deployment backwards. It is tempting because it avoids full downtime, but rollback is slow and not atomic, unlike blue/green with instant traffic switching.

• ✗

  Use an immutable deployment by launching a new Auto Scaling group and terminating the old one.

  Why it's wrong here

  An immutable deployment replaces the whole Auto Scaling group, so rollback requires relaunching the previous group rather than instantly reverting traffic. It is tempting because immutability avoids configuration drift, but the requirement for quick rollback favours blue/green with weighted target groups.