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'.

Practice

1. Why is cost management important when using AWS cloud services?

easy

A. It guarantees 100% uptime for services.

B. It helps control spending and avoid unexpected bills.

C. It automatically fixes security issues.

D. It increases the speed of cloud servers.

Solution

1. Step 1: Understand the purpose of cost management

   Cost management is about tracking and controlling how much you spend on cloud services.

2. Step 2: Identify the main benefit

   Controlling spending helps avoid surprises in bills and keeps costs predictable.

3. Final Answer:

   It helps control spending and avoid unexpected bills. -> Option B

4. Quick Check:

   Cost control = Avoid surprises [OK]

Hint: Cost management means controlling spending to avoid surprises [OK]

Common Mistakes:

• Confusing cost management with performance improvements
• Thinking cost management fixes security automatically
• Assuming cost management guarantees uptime

2. Which AWS tool is used to set alerts for when your cloud spending exceeds a budget?

easy

A. AWS CloudTrail

B. AWS Lambda

C. AWS Budgets

D. AWS EC2

Solution

1. Step 1: Identify AWS tools related to cost

   AWS Budgets is designed to track and alert on spending limits.

2. Step 2: Match tool to function

   CloudTrail tracks API calls, Lambda runs code, EC2 is a server service, so only Budgets fits alerting on costs.

3. Final Answer:

   AWS Budgets -> Option C

4. Quick Check:

   Budget alerts = AWS Budgets [OK]

Hint: Budget alerts come from AWS Budgets tool [OK]

Common Mistakes:

• Confusing CloudTrail with cost alerts
• Thinking Lambda manages budgets
• Mixing EC2 with cost monitoring

3. Look at this AWS Cost Explorer report snippet:
Service: EC2, Cost: $120
Service: S3, Cost: $30
Service: Lambda, Cost: $10
Which service is costing the most and should be reviewed first to reduce expenses?

medium

A. EC2

B. S3

C. Lambda

D. All cost the same

Solution

1. Step 1: Compare the costs listed

   EC2 costs $120, S3 costs $30, Lambda costs $10.

2. Step 2: Identify the highest cost

   EC2 has the highest cost, so it should be reviewed first to reduce expenses.

3. Final Answer:

   EC2 -> Option A

4. Quick Check:

   Highest cost = EC2 $120 [OK]

Hint: Highest cost service is the first to review [OK]

Common Mistakes:

• Choosing the lowest cost service
• Assuming all costs are equal
• Ignoring the cost numbers

4. You set an AWS Budget alert but never receive notifications even though spending exceeded the limit. What is the most likely cause?

medium

A. Cost Explorer must be enabled first.

B. Budget alert thresholds are set too high.

C. AWS Budgets only works for EC2 costs.

D. You did not enable notifications or specify email recipients.

Solution

1. Step 1: Understand AWS Budget alert setup

   Alerts require enabling notifications and specifying who receives them.

2. Step 2: Identify common misconfiguration

   If no notifications are enabled or no emails set, alerts won't be sent despite exceeding budget.

3. Final Answer:

   You did not enable notifications or specify email recipients. -> Option D

4. Quick Check:

   Missing notification setup = No alerts [OK]

Hint: Enable notifications and add emails to get alerts [OK]

Common Mistakes:

• Assuming alerts work without notification setup
• Thinking Budgets only track EC2
• Believing Cost Explorer controls alerts

5. Your company wants to reduce AWS costs by cleaning up unused resources monthly. Which combination of AWS tools and actions best supports this goal?

hard

A. Use AWS Cost Explorer to analyze spending and AWS Trusted Advisor to identify idle resources.

B. Use AWS CloudTrail to monitor API calls and AWS EC2 to stop unused servers manually.

C. Use AWS Budgets to set cost limits and AWS Lambda to automate resource cleanup.

D. Use AWS S3 to store logs and AWS IAM to restrict user access.

Solution

1. Step 1: Identify tools for cost analysis and resource cleanup

   AWS Cost Explorer helps analyze spending patterns; Trusted Advisor identifies idle or underused resources.

2. Step 2: Match tools to monthly cleanup goal

   Combining Cost Explorer and Trusted Advisor supports reviewing costs and finding cleanup targets effectively.

3. Final Answer:

   Use AWS Cost Explorer to analyze spending and AWS Trusted Advisor to identify idle resources. -> Option A

4. Quick Check:

   Cost analysis + idle resource check = Cost reduction [OK]

Hint: Combine Cost Explorer and Trusted Advisor for cleanup [OK]

Common Mistakes:

• Confusing Budgets with cleanup automation
• Using CloudTrail for cost analysis
• Choosing unrelated tools like S3 and IAM