Which set of additional actions should the DevOps engineer take to meet these requirements?
Configure the Datapoints to Alarm value to be 3 out of 12. Configure the alarm to treat missing data as breaching the threshold. Add an AWS Systems Manager action to stop the instance when the alarm enters the ALARM state.
Configure the Datapoints to Alarm value to be 3 out of 12. Configure the alarm to treat missing data as not breaching the threshold. Add an EC2 action to stop the instance when the alarm enters the ALARM state.
Configure the Datapoints to Alarm value to be 9 out of 12. Configure the alarm to treat missing data as breaching the threshold. Add an EC2 action to stop the instance when the alarm enters the ALARM state.
Configure the Datapoints to Alarm value to be 9 out of 12. Configure the alarm to treat missing data as not breaching the threshold. Add an AWS Systems Manager action to stop the instance when the alarm enters the ALARM state.
Explanations:
The “Treat missing data as breaching the threshold” setting would cause the alarm to trigger when data is missing, which is not desired. The requirement specifies that the alarm should not trigger if there is missing data.
The “Treat missing data as not breaching the threshold” setting ensures the alarm does not trigger when data is missing. Configuring Datapoints to Alarm to 3 out of 12 is correct to meet the requirement of 3 hours of low traffic (less than 5 packets) in a 12-hour period.
The “Datapoints to Alarm value of 9 out of 12” would mean 9 out of 12 hours must meet the threshold condition, which contradicts the requirement of only needing 3 hours. Additionally, treating missing data as breaching is incorrect.
The “Datapoints to Alarm value of 9 out of 12” is too high, as it would require 9 hours of low traffic instead of 3. Also, using AWS Systems Manager instead of an EC2 action is unnecessary and doesn’t match the requirements.
I sort that the answer is:
Configure the Datapoints to Alarm value to be 3 out of 12. Configure the alarm to treat missing data as not breaching the threshold. Add an EC2 action to stop the instance when the alarm enters the ALARM state.