AWS Certified Solutions Architect - Professional free question 9 / 10 · Domain 5: Operational Excellence and Automation
In a CloudFormation stack update, you watch the application's alarms for 30 minutes after deployment and roll the update back if an alarm goes to ALARM. You also want the same rollback if an alarm goes to INSUFFICIENT_DATA. How do you configure it?
- Set the monitoring time to 0 minutes; with 0 minutes, rollback also happens partway through the update on INSUFFICIENT_DATA
- Register 6 triggers and prepare a separate alarm for INSUFFICIENT_DATA; the limit is 6, and you specify them for each state
- On the rollback trigger alarm, treat missing data as breaching so that INSUFFICIENT_DATA also rolls back; by default only ALARM does
- The default behavior is enough; rollback triggers revert the update both when an alarm goes to ALARM and when it goes to INSUFFICIENT_DATA
Show the answer and explanation
Answer: C
Why this is correct
Rollback triggers watch the CloudWatch alarms that you specify during stack creation and update, and during the monitoring time after the resources are deployed (up to 180 minutes), and they roll back the operation if an alarm goes to ALARM. By default, CloudFormation rolls back only if an alarm goes to ALARM state, not INSUFFICIENT_DATA. To roll back on INSUFFICIENT_DATA as well, edit the CloudWatch alarm to treat missing data as breaching.
Why the other options are wrong
"The default behavior is enough; rollback triggers revert the update both when an alarm goes to ALARM and when it goes to INSUFFICIENT_DATA" … By default, INSUFFICIENT_DATA does not trigger a rollback. Only ALARM reverts the operation.
"Set the monitoring time to 0 minutes; with 0 minutes, rollback also happens partway through the update on INSUFFICIENT_DATA" … A monitoring time of 0 minutes does not change which alarm states are watched. It only means CloudFormation does not wait after deployment.
"Register 6 triggers and prepare a separate alarm for INSUFFICIENT_DATA; the limit is 6, and you specify them for each state" … The maximum is 5 rollback triggers, and there is no way to specify them per state. How the state is treated is decided by the alarm's missing data setting.
Key point
By default, rollback triggers act on ALARM only. To roll back on INSUFFICIENT_DATA too, treat missing data as breaching on the alarm. Maximum 5 triggers, and a monitoring time of 0 to 180 minutes.