Budgets and cost anomaly detection in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a budget with a specified amount.

AWS

aws budgets create-budget --account-id 123456789012 --budget '{"BudgetName": "MyBudget", "BudgetLimit": {"Amount": "[1]", "Unit": "USD"}, "TimeUnit": "MONTHLY", "BudgetType": "COST"}'

Drag options to blanks, or click blank then click option'

A1000

BMonthly

CUSD

DCost

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'USD' or 'Monthly' instead of a numeric amount.

Leaving the amount field empty.

The Amount field requires a numeric value as a string representing the budget limit. Here, "1000" sets the budget to $1000.

2fill in blank

medium

Complete the code to specify the time unit for the budget.

AWS

aws budgets create-budget --account-id 123456789012 --budget '{"BudgetName": "MyBudget", "BudgetLimit": {"Amount": "500", "Unit": "USD"}, "TimeUnit": "[1]", "BudgetType": "COST"}'

Drag options to blanks, or click blank then click option'

ADAILY

BWEEKLY

CYEARLY

DMONTHLY

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase instead of uppercase for time units.

Choosing a time unit that does not match the billing cycle.

The TimeUnit defines how often the budget resets. "MONTHLY" means the budget resets every month.

3fill in blank

hard

Fix the error in the command to enable cost anomaly detection monitor.

AWS

aws ce [1]-anomaly-monitor --monitor-name "MyMonitor" --monitor-type "COST_AND_USAGE"

Drag options to blanks, or click blank then click option'

Astart

Bupdate

Ccreate

Ddelete

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'start' or 'delete' instead of 'create'.

Confusing the monitor type with the action.

The correct command to create a cost anomaly detection monitor uses the create-anomaly-monitor action. The word 'create' is the right choice.

4fill in blank

hard

Fill both blanks to create a budget notification for when actual cost exceeds a threshold.

AWS

aws budgets create-notification --account-id 123456789012 --budget-name "MyBudget" --notification '{"NotificationType": "[1]", "ComparisonOperator": "[2]", "Threshold": 80, "ThresholdType": "PERCENTAGE"}'

Drag options to blanks, or click blank then click option'

AACTUAL

BFORECASTED

CGREATER_THAN

DLESS_THAN

Attempts:

3 left

💡 Hint

Common Mistakes

Using FORECASTED instead of ACTUAL for actual cost alerts.

Using LESS_THAN instead of GREATER_THAN for threshold comparison.

The notification triggers when the ACTUAL cost is GREATER_THAN 80% of the budget.

5fill in blank

hard

Fill all three blanks to create a cost anomaly subscription with email notification.

AWS

aws ce create-anomaly-subscription --subscription-name "MySubscription" --frequency [1] --monitor-arn-list ["[2]"] --subscribers '[{"Address": "[3]", "Type": "EMAIL"}]'

Drag options to blanks, or click blank then click option'

ADAILY

Barn:aws:ce:us-east-1:123456789012:anomaly-monitor/MyMonitor

[e-mail]

DWEEKLY

Attempts:

3 left

💡 Hint

Common Mistakes

Using DAILY instead of WEEKLY for frequency when weekly alerts are needed.

Incorrect ARN format or missing ARN.

Missing or invalid email address.

The subscription frequency is set to WEEKLY, the monitor ARN is specified correctly, and the subscriber email is provided.