Free tier usage monitoring in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the AWS CLI command to check free tier usage alerts.

AWS

aws ce get-[1] --time-period Start=2023-01-01,End=2023-01-31 --metrics "UsageQuantity"

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

Ausage-forecasts

Bbudgets

Ccost-and-usage

Dbilling

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'budgets' instead of 'cost-and-usage' will not show detailed usage data.

Using 'billing' is incorrect because it does not provide usage metrics.

The cost-and-usage command fetches detailed usage data, including free tier usage.

2fill in blank

medium

Complete the AWS CLI command to create a budget alert for free tier usage.

AWS

aws budgets create-budget --account-id 123456789012 --budget [1]

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

A"{\"BudgetName\": \"FreeTierUsage\", \"BudgetLimit\": {\"Amount\": \"15\", \"Unit\": \"HOURS\"}, \"TimeUnit\": \"DAILY\", \"BudgetType\": \"USAGE\"}"

B"{\"BudgetName\": \"FreeTierUsage\", \"BudgetLimit\": {\"Amount\": \"15\", \"Unit\": \"GB\"}, \"TimeUnit\": \"MONTHLY\", \"BudgetType\": \"USAGE\"}"

C"{\"BudgetName\": \"FreeTierUsage\", \"BudgetLimit\": {\"Amount\": \"15\", \"Unit\": \"USD\"}, \"TimeUnit\": \"MONTHLY\", \"BudgetType\": \"COST\"}"

D"{\"BudgetName\": \"FreeTierUsage\", \"BudgetLimit\": {\"Amount\": \"15\", \"Unit\": \"USD\"}, \"TimeUnit\": \"MONTHLY\", \"BudgetType\": \"USAGE\"}"

Attempts:

3 left

💡 Hint

Common Mistakes

Setting BudgetType to COST instead of USAGE will track cost, not usage.

Using HOURS as unit when monitoring storage usage is incorrect.

The budget is set for usage in GB monthly, which fits typical free tier usage monitoring.

3fill in blank

hard

Fix the error in the AWS CLI command to describe free tier usage alerts.

AWS

aws budgets describe-[1] --account-id 123456789012 --budget-name FreeTierUsage

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

Abudgets

Balert

Cnotifications

Dalerts

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'alert' causes a command not found error.

Using 'budgets' is incorrect because it lists budgets, not alerts.

The correct subcommand is alerts to list budget alerts.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that filters free tier usage data for services with usage over 1000 units.

AWS

usage_over_1000 = {service: data[1] for service, data in usage_data.items() if data [2] 1000}

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

A.get('UsageQuantity', 0)

B>

C>=

D['UsageQuantity']

Attempts:

3 left

💡 Hint

Common Mistakes

Using ['UsageQuantity'] can cause errors if the key is missing.

Using '>=' includes 1000, but the task asks for over 1000.

Use .get('UsageQuantity', 0) to safely access usage quantity, and > to filter values over 1000.

5fill in blank

hard

Fill all three blanks to create a filtered dictionary of services with usage below 500 units and convert service names to uppercase.

AWS

filtered_usage = [1]: data for service, data in usage_data.items() if data[2] 500 and service[3] 's3'

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

Aservice.upper()

B<

C!=

Dservice.lower()

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' instead of '!=' includes the 's3' service, which is not desired.

Using '>' instead of '<' filters the wrong usage range.

Convert service names to uppercase, filter usage less than 500, and exclude 's3' service.

Practice

1. What is the main purpose of AWS free tier usage monitoring?

easy

A. To avoid unexpected charges by tracking usage

B. To increase the AWS free tier limits automatically

C. To disable all AWS services after free tier expires

D. To get free AWS support for all services

Solution

1. Step 1: Understand free tier usage monitoring

   It is designed to track how much of the free tier you have used to prevent surprise bills.

2. Step 2: Compare options with purpose

   Only To avoid unexpected charges by tracking usage matches the goal of monitoring usage to avoid unexpected charges.

3. Final Answer:

   To avoid unexpected charges by tracking usage -> Option A

4. Quick Check:

   Free tier monitoring = avoid surprise charges [OK]

Hint: Free tier monitoring means tracking usage to avoid bills [OK]

Common Mistakes:

• Thinking free tier monitoring increases limits
• Believing it disables services automatically
• Assuming it provides free support

2. Which AWS CLI command correctly lists your free tier usage costs using Cost Explorer?

easy

A. aws free-tier usage --period 2024-01

B. aws ce list-usage --start 2024-01-01 --end 2024-01-31

C. aws ce get-cost-and-usage --time-period Start=2024-01-01,End=2024-01-31 --metrics "BlendedCost"

D. aws cost-explorer show-usage --from 2024-01-01 --to 2024-01-31

Solution

1. Step 1: Identify correct AWS CLI syntax for Cost Explorer

   The correct command uses 'aws ce get-cost-and-usage' with --time-period and --metrics parameters.

2. Step 2: Check options for correct syntax

   Only aws ce get-cost-and-usage --time-period Start=2024-01-01,End=2024-01-31 --metrics "BlendedCost" matches the official AWS CLI syntax for cost and usage retrieval.

3. Final Answer:

   aws ce get-cost-and-usage --time-period Start=2024-01-01,End=2024-01-31 --metrics "BlendedCost" -> Option C

4. Quick Check:

   Correct AWS CLI syntax = aws ce get-cost-and-usage --time-period Start=2024-01-01,End=2024-01-31 --metrics "BlendedCost" [OK]

Hint: Use 'aws ce get-cost-and-usage' with time period and metrics [OK]

Common Mistakes:

• Using non-existent commands like 'list-usage'
• Wrong parameter names like --start or --from
• Mixing service names incorrectly

3. Given this AWS CLI command output snippet for free tier usage:

{
  "ResultsByTime": [
    {"TimePeriod": {"Start": "2024-04-01", "End": "2024-04-30"}, "Total": {"BlendedCost": {"Amount": "0.00", "Unit": "USD"}}}
  ]
}

What does this output indicate about your free tier usage for April 2024?

medium

A. You have used services but incurred no cost within free tier limits

B. You have exceeded free tier limits and were charged

C. No AWS services were used in April 2024

D. The command failed to retrieve usage data

Solution

1. Step 1: Analyze the 'Amount' field in output

   The 'Amount' is "0.00" USD, meaning no cost was charged.

2. Step 2: Interpret zero cost with usage

   Zero cost with usage means usage stayed within free tier limits, so no charges applied.

3. Final Answer:

   You have used services but incurred no cost within free tier limits -> Option A

4. Quick Check:

   Zero cost means usage within free tier [OK]

Hint: Zero cost in output means usage stayed free [OK]

Common Mistakes:

• Assuming zero cost means no usage
• Thinking zero cost means command error
• Confusing free tier limits with no charges

4. You run this AWS CLI command to check free tier usage but get an error:

aws ce get-cost-and-usage --time-period Start=2024-01-01,End=2024-01-31 --metrics BlendedCost

What is the likely cause of the error?

medium

A. Incorrect date format in --time-period

B. AWS CLI is not installed

C. Using 'ce' instead of 'cost-explorer' in the command

D. Missing quotes around the BlendedCost metric value

Solution

1. Step 1: Check syntax for --metrics parameter

   The metric name must be enclosed in quotes, e.g., "BlendedCost".

2. Step 2: Validate other parts of the command

   Date format and 'ce' alias are correct; AWS CLI installation error would be different.

3. Final Answer:

   Missing quotes around the BlendedCost metric value -> Option D

4. Quick Check:

   Metric names need quotes in AWS CLI [OK]

Hint: Always quote metric names in AWS CLI commands [OK]

Common Mistakes:

• Not quoting metric names
• Changing date format incorrectly
• Confusing service aliases
• Assuming AWS CLI not installed without checking

5. You want to set up an automated alert to notify you when your AWS free tier usage approaches its limit. Which AWS service combination is best suited for this task?

hard

A. AWS CloudTrail with AWS Lambda

B. AWS Budgets with Amazon SNS notifications

C. Amazon CloudWatch Logs with AWS Config

D. AWS IAM with AWS Organizations

Solution

1. Step 1: Identify service for cost and usage alerts

   AWS Budgets allows setting thresholds and alerts for cost and usage.

2. Step 2: Identify notification method

   Amazon SNS can send notifications via email or SMS when budget thresholds are met.

3. Final Answer:

   AWS Budgets with Amazon SNS notifications -> Option B

4. Quick Check:

   Budgets + SNS = automated cost alerts [OK]

Hint: Use AWS Budgets and SNS for free tier alerts [OK]

Common Mistakes:

• Using CloudTrail which tracks API calls, not costs
• Confusing CloudWatch Logs with cost alerts
• Using IAM or Organizations which manage access, not alerts