Setting up billing alerts in AWS - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a billing alarm that triggers when the estimated charges exceed $100.

AWS

AlarmName: "BillingAlarm"
MetricName: "EstimatedCharges"
Namespace: "AWS/Billing"
Statistic: "Maximum"
Period: 21600
EvaluationPeriods: 1
Threshold: [1]
ComparisonOperator: "GreaterThanThreshold"

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

A50

B100

C200

D10

Attempts:

3 left

💡 Hint

Common Mistakes

Setting the threshold too low or too high.

Confusing threshold with evaluation periods.

The threshold should be set to 100 to alert when charges exceed $100.

2fill in blank

medium

Complete the code to specify the currency unit for the billing metric.

AWS

MetricName: "EstimatedCharges"
Namespace: "AWS/Billing"
Dimensions:
  - Name: "Currency"
    Value: [1]

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

AGBP

BEUR

CJPY

DUSD

Attempts:

3 left

💡 Hint

Common Mistakes

Using a currency code not supported by AWS billing.

Leaving the currency dimension empty.

The billing alerts typically use USD as the currency unit.

3fill in blank

hard

Fix the error in the alarm action to notify the billing team via SNS topic ARN.

AWS

AlarmActions:
  - [1]

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

A"arn:aws:sns:us-east-1:123456789012:BillingAlerts"

BBillingAlerts

C"BillingAlerts"

Darn:aws:sns:us-east-1:123456789012:BillingAlerts

Attempts:

3 left

💡 Hint

Common Mistakes

Using just the topic name without ARN.

Missing quotes around the ARN string.

The alarm action requires the full SNS topic ARN as a quoted string.

4fill in blank

hard

Fill both blanks to complete the CloudFormation snippet for billing alarm with SNS notification.

AWS

Resources:
  BillingAlarm:
    Type: "AWS::CloudWatch::Alarm"
    Properties:
      AlarmName: "BillingAlarm"
      MetricName: "EstimatedCharges"
      Namespace: "AWS/Billing"
      Statistic: "Maximum"
      Period: 21600
      EvaluationPeriods: 1
      Threshold: [1]
      ComparisonOperator: [2]
      AlarmActions:
        - "arn:aws:sns:us-east-1:123456789012:BillingAlerts"

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

A100

BGreaterThanThreshold

CLessThanThreshold

D200

Attempts:

3 left

💡 Hint

Common Mistakes

Using LessThanThreshold which triggers alert on lower charges.

Setting threshold too high or too low.

The threshold should be 100 and the comparison operator should be GreaterThanThreshold to alert when charges exceed $100.

5fill in blank

hard

Fill all three blanks to complete the billing alert setup with metric dimension and SNS action.

AWS

Resources:
  BillingAlarm:
    Type: "AWS::CloudWatch::Alarm"
    Properties:
      AlarmName: "BillingAlarm"
      MetricName: "EstimatedCharges"
      Namespace: "AWS/Billing"
      Dimensions:
        - Name: [1]
          Value: [2]
      Threshold: 100
      ComparisonOperator: "GreaterThanThreshold"
      AlarmActions:
        - [3]

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

A"Currency"

B"USD"

C"arn:aws:sns:us-east-1:123456789012:BillingAlerts"

D"EstimatedCharges"

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong dimension name or value.

Not quoting the SNS topic ARN.

The dimension name is "Currency" with value "USD" and the alarm action is the SNS topic ARN as a quoted string.

Practice

1. What is the primary purpose of setting up billing alerts in AWS?

easy

A. To disable services when spending is high

B. To automatically increase your cloud budget

C. To get notified when your cloud spending reaches a certain limit

D. To get detailed logs of all service usage

Solution

1. Step 1: Understand billing alerts purpose

   Billing alerts notify you when your spending reaches a set threshold to help control costs.

2. Step 2: Compare options

   Only To get notified when your cloud spending reaches a certain limit describes notification on spending limits; others describe unrelated actions.

3. Final Answer:

   To get notified when your cloud spending reaches a certain limit -> Option C

4. Quick Check:

   Billing alerts = notifications on spending [OK]

Hint: Billing alerts notify you about spending limits reached [OK]

Common Mistakes:

• Thinking alerts automatically change budgets
• Confusing alerts with service shutdown
• Assuming alerts provide detailed usage logs

2. Which AWS service is used to create billing alerts easily?

easy

A. Amazon S3

B. AWS CloudTrail

C. AWS Lambda

D. AWS Budgets

Solution

1. Step 1: Identify service for billing alerts

   AWS Budgets is designed to create budgets and alerts for billing thresholds.

2. Step 2: Eliminate unrelated services

   CloudTrail tracks API calls, Lambda runs code, S3 stores data; none create billing alerts.

3. Final Answer:

   AWS Budgets -> Option D

4. Quick Check:

   AWS Budgets = billing alerts service [OK]

Hint: Use AWS Budgets to set billing alerts quickly [OK]

Common Mistakes:

• Choosing CloudTrail for billing alerts
• Confusing Lambda with alert setup
• Selecting S3 as billing alert tool

3. Given this AWS Budgets alert setup:
Threshold: 80% of $1000 budget
Notification: Email to [e-mail]
What triggers the alert?

medium

A. When spending reaches $800

B. When spending reaches $1000

C. When spending reaches $200

D. When spending reaches $1200

Solution

1. Step 1: Calculate 80% of $1000 budget

   80% of $1000 = 0.8 x 1000 = $800.

2. Step 2: Understand alert trigger

   The alert triggers when spending reaches $800, the threshold set.

3. Final Answer:

   When spending reaches $800 -> Option A

4. Quick Check:

   80% x 1000 = 800 [OK]

Hint: Multiply budget by threshold percent to find alert trigger [OK]

Common Mistakes:

• Using full budget amount instead of threshold
• Confusing 80% with 20%
• Choosing amounts above budget

4. You set a billing alert but never receive notifications. What is a likely cause?

medium

A. Your AWS account has no budget set

B. You did not verify the email address for notifications

C. Billing alerts only work with SMS, not email

D. Alerts only trigger after spending exceeds twice the budget

Solution

1. Step 1: Check notification setup requirements

   AWS requires email addresses to be verified before sending alerts.

2. Step 2: Evaluate other options

   A budget is required to create alerts; alerts support email notifications; alerts trigger when spending reaches the threshold, not after twice the budget.

3. Final Answer:

   You did not verify the email address for notifications -> Option B

4. Quick Check:

   Email verification needed for alerts [OK]

Hint: Verify email to receive AWS billing alerts [OK]

Common Mistakes:

• Assuming alerts work without email verification
• Thinking alerts only support SMS
• Believing alerts trigger only after double spending

5. You want to set a billing alert that notifies you by email when your AWS spending exceeds $500 and again at $750. How can you configure this using AWS Budgets?

hard

A. Create one budget with two notification thresholds: 50% and 75% of $1000 budget

B. Create two separate budgets each with one notification at $500 and $750

C. Create one budget with a single notification at $625 (average of $500 and $750)

D. Create one budget with a notification only at $750 and manually check for $500

Solution

1. Step 1: Understand AWS Budgets notification capabilities

   AWS Budgets allows multiple notification thresholds per budget.

2. Step 2: Apply thresholds to a single budget

   Set budget at $1000 with notifications at 50% ($500) and 75% ($750) to get alerts at both amounts.

3. Step 3: Evaluate other options

   Creating two budgets is unnecessary; a single notification at the average misses the exact alert points; manual checking is inefficient.

4. Final Answer:

   Create one budget with two notification thresholds: 50% and 75% of $1000 budget -> Option A

5. Quick Check:

   Multiple notifications per budget = correct setup [OK]

Hint: Use multiple thresholds in one budget for several alerts [OK]

Common Mistakes:

• Creating multiple budgets instead of multiple notifications
• Using average threshold instead of exact values
• Relying on manual checks instead of alerts