Which of the following is the correct way to create a cost anomaly detection monitor using AWS CLI?
easy📝 Configuration Q12 of 15
AWS - Cost Optimization
Which of the following is the correct way to create a cost anomaly detection monitor using AWS CLI?
Aaws ec2 create-anomaly-monitor --name MyMonitor
Baws ce create-budget --name MyMonitor
Caws ce start-anomaly-monitor --monitor-name MyMonitor
Daws ce create-anomaly-monitor --monitor-name MyMonitor
Step-by-Step Solution
Solution:
Step 1: Identify correct AWS CLI command for anomaly monitor
The AWS Cost Explorer (ce) service uses 'create-anomaly-monitor' to create anomaly monitors.
Step 2: Check options for correct syntax and service
aws ce create-anomaly-monitor --monitor-name MyMonitor uses 'aws ce create-anomaly-monitor' with correct parameter '--monitor-name'. Others use wrong commands or services.
Final Answer:
aws ce create-anomaly-monitor --monitor-name MyMonitor -> Option D
Quick Check:
Correct CLI command for anomaly monitor creation = aws ce create-anomaly-monitor --monitor-name MyMonitor [OK]
Quick Trick:Use 'aws ce create-anomaly-monitor' to create monitors [OK]
Common Mistakes:
Using 'create-budget' instead of anomaly monitor command
Using EC2 service commands for cost anomaly detection
Incorrect parameter names like '--name' instead of '--monitor-name'
Master "Cost Optimization" in AWS
9 interactive learning modes - each teaches the same concept differently