A CloudFormation stack update failed due to a bad template and CloudFormation started rolling back, but the stack remains in UPDATE_ROLLBACK_FAILED and the application is still down. What actions should a DevOps engineer take so the rollback can finish successfully? (Choose two.)

When a CloudFormation stack enters UPDATEROLLBACKFAILED, it means CloudFormation encountered an issue during the rollback process and couldn't complete it. To resolve this, you must first address the underlying problem that prevented the rollback. This often involves manually modifying the affected resources to bring them into a state that CloudFormation expects, allowing the rollback to proceed. Once the resource state is corrected, you can then use ContinueUpdateRollback via the AWS Management Console or AWS CLI to instruct CloudFormation to resume and complete the rollback. Attaching AWSCloudFormationFullAccess is unlikely to fix a rollback failure unless it was a permissions issue, which is not implied here. Drift detection identifies differences but doesn't automatically restore resources or fix rollback failures. Reapplying the original template won't work while the stack is in a failed rollback state.