What is the state of a CloudWatch alarm immediately after it is created but before any metric data is received?
Think about what happens when there is no data to evaluate the alarm.
When a CloudWatch alarm is first created, it has no data to evaluate. Therefore, its state is INSUFFICIENT_DATA until metric data arrives and the alarm can evaluate its condition.
You want to create a CloudWatch alarm that triggers when the average CPU utilization of an EC2 instance exceeds 70% for 5 consecutive minutes. Which configuration below correctly sets the evaluation period and threshold?
Remember that the period is in seconds and evaluation periods count how many periods must breach the threshold.
To check if CPU utilization exceeds 70% for 5 consecutive minutes, set Period to 300 seconds (5 minutes) and EvaluationPeriods to 1. Statistic should be Average to measure average CPU usage.
Which IAM permission is required to allow a user to create and manage CloudWatch alarms that send notifications to an SNS topic?
Check the exact IAM actions for CloudWatch alarms and SNS publishing.
To create or update alarms, the user needs cloudwatch:PutMetricAlarm permission. To send notifications to SNS, sns:Publish permission is required.
You want to monitor an application deployed in two AWS regions and trigger a single alarm if the error rate exceeds 5% in either region. Which architecture best achieves this?
Consider how CloudWatch alarms work regionally and how to aggregate alerts.
CloudWatch alarms are regional and cannot monitor metrics from other regions directly. Creating alarms in each region and aggregating notifications via SNS and Lambda allows triggering a single global alarm.
You have many CloudWatch alarms monitoring various metrics. To reduce costs without losing critical alert accuracy, which approach is best?
Think about combining alarms to reduce noise and cost.
Composite alarms combine multiple alarms into one, reducing the number of notifications and API calls, which lowers costs while maintaining alert accuracy.