Ultimate access to all questions.
After updating an AWS CloudFormation template for a critical business application, the stack update failed and AWS CloudFormation initiated a rollback. Subsequently, a DevOps engineer found the application was still unavailable, and the stack was stuck in the UPDATE_ROLLBACK_FAILED state. What should the DevOps engineer do to successfully complete the stack rollback?
Explanation:
To resolve the UPDATE_ROLLBACK_FAILED state and complete the stack rollback, the DevOps engineer should:
Issue a ContinueUpdateRollback command from the AWS CloudFormation console or the AWS CLI (Option C). This command resumes the rollback process, allowing AWS CloudFormation to attempt to restore the stack to its previous state.
Manually adjust the resources to match the expectations of the stack (Option D). This involves correcting any configuration or dependency issues that caused the rollback to fail, ensuring that the resources are in sync with the stack's expected state.