You want to monitor a custom application metric that tracks the number of user logins per hour. The default AWS metrics do not provide this data. What is the best approach to achieve this?

hard📝 Best Practice Q15 of 15

AWS - CloudWatch

AEnable detailed monitoring on EC2 instances to get user login data.

BUse the default CPUUtilization metric to estimate user logins.

CSend custom metric data for user logins to CloudWatch using a unique namespace and metric name.

DCreate an alarm on default network metrics to infer user logins.

Step-by-Step Solution

Solution:

Step 1: Identify the need for custom data
User logins per hour is specific to the application and not tracked by default AWS metrics.
Step 2: Use custom metrics for application-specific data
Sending custom metric data with a unique namespace and metric name allows tracking exactly this information in CloudWatch.
Final Answer:
Send custom metric data for user logins to CloudWatch using a unique namespace and metric name. -> Option C
Quick Check:
Custom metrics track app-specific data [OK]

Quick Trick: Use custom metrics for app-specific tracking [OK]

Common Mistakes:

MISTAKES

Trying to use unrelated default metrics for app data
Assuming detailed monitoring tracks application events
Using alarms on unrelated metrics to guess user activity

Master "CloudWatch" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More AWS Quizzes

You want to monitor a custom application metric that tracks the number of user logins per hour. The default AWS metrics do not provide this data. What is the best approach to achieve this?

Step 1: Identify the need for custom data

Step 2: Use custom metrics for application-specific data

Final Answer:

Quick Check:

Want More Practice?