SOA-C02 Deployment, Provisioning, and Automation 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.

• ✗

  Rolling update

  Why it's wrong here

  A rolling update replaces instances in batches (e.g., 20% at a time) but does not create a fully independent parallel environment. During the transition, the fleet contains a mix of old and new versions, and capacity is temporarily reduced because some instances are being updated. If a problem is detected, rollback is not instantaneous: you must re-run the previous deployment, which takes time and briefly repeats the same batch-wise cycle, so it does not provide zero downtime or immediate traffic switching.

• ✓

  Blue/green deployment

  Why this is correct

  Blue/green deployment provisions a complete second environment (green) alongside the current production environment (blue), allowing you to run tests against the new version while old traffic continues to flow. Once the new environment is validated, you shift traffic at the load balancer or DNS level—either all at once or gradually—making the cutover near-instantaneous. If the new environment fails, you simply switch traffic back to the still-available blue environment, enabling instant rollback with zero downtime, which is why this is the correct choice for high-availability web applications.

• ✗

  All at once deployment

  Why it's wrong here

  The 'AllAtOnce' deployment configuration stops every existing instance before starting any new ones, meaning the application is completely unavailable during the entire stop, re-provision, and startup sequence. Unlike blue/green, there is no old environment held in reserve; the original instances are terminated, so if a rollback is needed, you must redeploy the previous version from scratch, causing additional downtime. This approach maximizes speed of deployment but sacrifices both availability and rapid recovery, making it unsuitable for production workloads that require continuous service.

• ✗

  Canary deployment

  Why it's wrong here

  A canary deployment routes a small percentage of traffic to the new version initially, then gradually increases it. While it reduces risk, it does not provide an instant full rollback like blue/green, and the rollout process is slower.