An application is installed in EC2 and sends customized metrics to AWS CloudWatch. You have configured lots of AWS CloudWatch alarms based on these metric reports data. You have found that there are several CloudWatch alarms that have the state of “INSUFFICIENT_DATA” at times. You confirmed with developers that certain metric data is only intermittently generated by design. What should you perform to ignore these “INSUFFICIENT_DATA” alarms?

Answer options:

A.Configure the CloudWatch alarms to change the state of “INSUFFICIENT_DATA” to “OK” after 5 minutes.
B.Configure these CloudWatch alarms to treat missing data points as “ignore” so that “INSUFFICIENT_DATA” does not show up.
C.Create a Lambda function which calls CloudWatch Alarm API to check the reason of “INSUFFICIENT_DATA” and modifies the alarm state to “OK” if there is no data received from the EC2 instance during the time.
D.Create a CloudWatch Event. When an “INSUFFICIENT_DATA” CloudWatch alarm appears, use an SNS to notify the team to react accordingly.

Correct Answer – B
Refer to https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html on how to configure CloudWatch alarms when missing data happens.
Option A is incorrect: Because this cannot be done for CloudWatch alarms.
Option B is CORRECT: Because this is the suggested way and missing data will not cause an “INSUFFICIENT_DATA” alarm:
Option C is incorrect: This brings lots of unnecessary efforts if compared with Option
B.Option D is incorrect: Because it still needs some manual work for the team to perform actions on the “INSUFFICIENT_DATA” alarms. In this scenario, the issue can be addressed by an automated method.