
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?
A
Attach the AWSCloudFormationFullAccess IAM policy to the AWS CloudFormation role.
B
Automatically recover the stack resources by using AWS CloudFormation drift detection.
C
Issue a ContinueUpdateRollback command from the AWS CloudFormation console or the AWS CLI.
D
Manually adjust the resources to match the expectations of the stack.
E
Update the existing AWS CloudFormation stack by using the original template.