Why cost management matters in AWS - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a budget alert in AWS Budgets.

AWS

aws budgets create-budget --account-id 123456789012 --budget-name "MonthlyBudget" --budget [1]

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

A{"BudgetType": "COST", "BudgetLimit": {"Amount": "100", "Unit": "USD"}, "TimeUnit": "MONTHLY", "TimePeriod": {"Start": "2024-01-01", "End": "2024-12-31"}}

B{"BudgetType": "USAGE", "BudgetLimit": {"Amount": "100", "Unit": "GB"}}

C{"BudgetType": "SAVINGS", "BudgetLimit": {"Amount": "50", "Unit": "USD"}}

D{"BudgetType": "CREDITS", "BudgetLimit": {"Amount": "10", "Unit": "USD"}}

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a budget type other than COST.

Using incorrect units like GB for cost budgets.

The budget type must be set to COST with a limit in USD to track spending.

2fill in blank

medium

Complete the code to enable cost allocation tags in AWS Billing.

AWS

aws ce enable-cost-allocation-tags --tag-keys [1]

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

A["Service"]

B["Region"]

C["Environment"]

D["User"]

Attempts:

3 left

💡 Hint

Common Mistakes

Using tags that are not enabled for cost allocation.

Using tags unrelated to cost tracking.

Enabling the 'Environment' tag helps track costs by development stages like production or testing.

3fill in blank

hard

Fix the error in the AWS CLI command to retrieve cost and usage data.

AWS

aws ce get-cost-and-usage --time-period Start=[1],End=2024-05-31 --granularity MONTHLY --metrics "BlendedCost"

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

A2024-05-01

B"2024-05-01"

C"05-01-2024"

DMay-01-2024

Attempts:

3 left

💡 Hint

Common Mistakes

Using unquoted dates causing syntax errors.

Using wrong date formats.

The date must be in quotes and in the format YYYY-MM-DD.

4fill in blank

hard

Fill both blanks to create a cost anomaly detection monitor with AWS CLI.

AWS

aws ce create-anomaly-monitor --monitor-name [1] --monitor-type [2]

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

A"ProdMonitor"

B"TestMonitor"

C"COST"

D"USAGE"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'USAGE' instead of 'COST' for anomaly detection.

Using generic or unclear monitor names.

The monitor name should be descriptive like 'ProdMonitor' and the monitor type for cost anomalies is 'COST'.

5fill in blank

hard

Fill all three blanks to create a cost category with rules using AWS CLI.

AWS

aws ce create-cost-category-definition --name [1] --rule-version [2] --rules '[3]'

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

A"TeamCosts"

B"CostCategoryExpression.v1"

C[{"Value": "TeamA", "Rule": {"Dimensions": {"Key": "LINKED_ACCOUNT", "Values": ["123456789012"]}}}]

D{"Value": "TeamB", "Rule": {"Dimensions": {"Key": "SERVICE", "Values": ["AmazonEC2"]}}}

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect rule version strings.

Providing invalid JSON for rules.

Mismatching account IDs or service names.

The cost category is named 'TeamCosts', uses rule version 'CostCategoryExpression.v1', and the rule assigns costs from account '123456789012' to 'TeamA'.