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.

• ✗

  Delete the existing service and recreate it with the new task definition.

  Why it's wrong here

  Deleting and recreating the service causes downtime and loses service configuration, contradicting the rolling-update requirement. It is tempting because recreating does apply the new task definition, but it would be acceptable only for non-production services where an outage is tolerable.

• ✗

  Modify the task definition and then restart the service.

  Why it's wrong here

  Restarting a service redeploys the existing task definition revision, so the new environment variables never take effect. It is tempting because restarting forces fresh tasks, which helps with stuck containers, but ECS rolling updates require registering a new revision and calling UpdateService with the new task definition.

• ✓

  Update the service with the new task definition and use a rolling update deployment controller.

  Why this is correct

  Updating the service with the new task definition and the rolling deployment controller replaces tasks incrementally, honouring the minimum healthy percent and maximum percent settings. This satisfies the minimal-impact constraint, since capacity remains available throughout, unlike recreate, which stops all tasks before starting replacements.

• ✗

  Create a new service with the new task definition and delete the old one.

  Why it's wrong here

  Creating a second service duplicates the ALB target group registration and leaves two services competing for the same listener, causing downtime during cutover rather than a rolling replacement. This pattern suits blue/green deployments with CodeDeploy traffic shifting, not an in-place environment variable change.