Why monitoring matters in AWS - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is monitoring critical in cloud environments?

Imagine you run a website on AWS. Why is monitoring your resources important?

A It helps detect problems early and keeps the website running smoothly.

B It automatically fixes all bugs without human help.

C It reduces the cost of AWS services by deleting unused resources.

D It replaces the need for backups and security measures.

💡 Hint

Think about how you would know if your website is slow or down.

Monitoring lets you see how your resources perform and alerts you to issues early, so you can fix them before users notice.

💻 Command Output

intermediate

What does this AWS CloudWatch command output?

Look at this AWS CLI command and its output. What does it show?

AWS

aws cloudwatch get-metric-statistics --metric-name CPUUtilization --start-time 2024-06-01T00:00:00Z --end-time 2024-06-01T01:00:00Z --period 300 --namespace AWS/EC2 --statistics Average --dimensions Name=InstanceId,Value=i-1234567890abcdef0

A Total network traffic for the EC2 instance during the hour.

B List of all running EC2 instances in the account.

C Current status of the EC2 instance i-1234567890abcdef0.

D Average CPU usage of the EC2 instance over 5-minute intervals in the specified hour.

💡 Hint

Look at the metric name and statistics requested.

The command fetches average CPU usage data points for the given EC2 instance in 5-minute periods.

🔀 Workflow

advanced

Order the steps to set up AWS CloudWatch alarms for monitoring

Arrange these steps in the correct order to create a CloudWatch alarm that notifies you when CPU usage is high.

A 2,3,1,4

B 1,2,3,4

C 2,1,3,4

D 3,2,1,4

💡 Hint

Think about setting up notifications before creating the alarm.

You first create the SNS topic, subscribe your email, then create the alarm that uses the topic, and finally test it.

❓ Troubleshoot

advanced

Why might your CloudWatch alarm not send notifications?

You set up a CloudWatch alarm with an SNS topic, but you never get email alerts. What could be the cause?

A The EC2 instance is stopped, so no metrics are sent.

B You forgot to confirm the subscription email sent by SNS.

C CloudWatch alarms do not support email notifications.

D You set the alarm threshold too low.

💡 Hint

Check if you completed all steps to receive notifications.

SNS sends a confirmation email that must be accepted to activate notifications. Without confirmation, no alerts are sent.

✅ Best Practice

expert

Which practice improves monitoring efficiency in AWS?

To reduce costs and improve monitoring, which approach is best when setting CloudWatch metrics and alarms?

A Create alarms for every metric available to catch all issues.

B Enable detailed monitoring on all resources regardless of usage.

C Monitor only critical metrics and set alarms for key thresholds.

D Disable all alarms and rely on manual checks.

💡 Hint

Think about balancing cost and usefulness.

Monitoring only important metrics and setting alarms on key thresholds helps catch issues without unnecessary cost or noise.

Practice

1. Why is monitoring important in AWS environments?

easy

A. It helps detect issues early to keep systems running smoothly.

B. It automatically fixes all system errors without human help.

C. It increases the cost of running AWS services.

D. It disables alarms to reduce notifications.

Solution

1. Step 1: Understand monitoring purpose

   Monitoring tracks system health and performance in real time.

2. Step 2: Identify the benefit of early detection

   Early detection helps fix problems before they affect users.

3. Final Answer:

   It helps detect issues early to keep systems running smoothly. -> Option A

4. Quick Check:

   Monitoring = Early issue detection [OK]

Hint: Monitoring = early alerts to avoid bigger problems [OK]

Common Mistakes:

• Thinking monitoring fixes issues automatically
• Believing monitoring increases costs unnecessarily
• Assuming monitoring disables alarms

2. Which AWS service is primarily used for monitoring and setting alarms?

easy

A. Amazon CloudWatch

B. Amazon EC2

C. AWS S3

D. AWS Lambda

Solution

1. Step 1: Identify AWS monitoring services

   AWS CloudWatch collects metrics and logs for monitoring.

2. Step 2: Match service to alarms and monitoring

   CloudWatch allows setting alarms to notify on issues.

3. Final Answer:

   Amazon CloudWatch -> Option A

4. Quick Check:

   Monitoring + alarms = CloudWatch [OK]

Hint: CloudWatch = AWS monitoring and alarms tool [OK]

Common Mistakes:

• Confusing Lambda with monitoring service
• Thinking S3 stores monitoring data directly
• Assuming EC2 handles alarms

3. What will happen if you create a CloudWatch alarm for CPU usage > 80% and the CPU usage reaches 85%?

medium

A. The CPU usage will automatically reduce.

B. The alarm will ignore the CPU usage.

C. The alarm will trigger and notify you.

D. The alarm will delete the instance.

Solution

1. Step 1: Understand CloudWatch alarm behavior

   Alarms trigger when the monitored metric crosses the threshold.

2. Step 2: Apply to CPU usage scenario

   CPU usage > 80% triggers the alarm at 85% usage.

3. Final Answer:

   The alarm will trigger and notify you. -> Option C

4. Quick Check:

   CPU > threshold = alarm triggers [OK]

Hint: Alarm triggers when metric exceeds threshold [OK]

Common Mistakes:

• Thinking alarms fix issues automatically
• Believing alarms ignore threshold breaches
• Assuming alarms delete resources

4. You set a CloudWatch alarm but never receive notifications when thresholds are crossed. What is a likely cause?

medium

A. The CPU usage never exceeded the threshold.

B. The alarm is not linked to any notification action.

C. CloudWatch does not support alarms.

D. The AWS account is inactive.

Solution

1. Step 1: Check alarm configuration

   Alarms must have notification actions (like SNS) to send alerts.

2. Step 2: Identify missing notification setup

   If no notification is linked, no alerts are sent despite threshold breaches.

3. Final Answer:

   The alarm is not linked to any notification action. -> Option B

4. Quick Check:

   Missing notification = no alerts [OK]

Hint: Link alarms to notifications to get alerts [OK]

Common Mistakes:

• Assuming alarms send notifications automatically
• Ignoring notification setup in alarm
• Thinking CloudWatch lacks alarm support

5. You want to keep your AWS app reliable by monitoring multiple metrics and sending alerts only when several conditions happen together. Which approach should you use?

hard

A. Create multiple independent CloudWatch alarms without combining them.

B. Disable alarms to reduce noise.

C. Rely on manual checks instead of alarms.

D. Use CloudWatch composite alarms to combine multiple alarms into one alert.

Solution

1. Step 1: Understand composite alarms

   Composite alarms combine multiple alarms using logical conditions.

2. Step 2: Apply composite alarms for multi-condition alerts

   This lets you alert only when all or some conditions happen together.

3. Final Answer:

   Use CloudWatch composite alarms to combine multiple alarms into one alert. -> Option D

4. Quick Check:

   Multi-condition alert = composite alarms [OK]

Hint: Use composite alarms for combined conditions [OK]

Common Mistakes:

• Creating separate alarms without combination
• Ignoring composite alarms feature
• Disabling alarms to avoid alerts