Why cost management prevents surprises in DynamoDB - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a billing alarm for DynamoDB usage.

DynamoDB

aws cloudwatch put-metric-alarm --alarm-name DynamoDBUsageAlarm --metric-name [1] --namespace AWS/Billing --statistic Maximum --period 21600 --threshold 100 --comparison-operator GreaterThanThreshold --evaluation-periods 1 --alarm-actions arn:aws:sns:us-east-1:123456789012:NotifyMe

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

AConsumedReadCapacityUnits

BThrottledRequests

CProvisionedWriteCapacityUnits

DEstimatedCharges

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a capacity metric instead of a billing metric.

Using a metric that tracks usage but not cost.

The EstimatedCharges metric tracks AWS billing charges, which helps prevent cost surprises.

2fill in blank

medium

Complete the code to enable detailed billing reports for DynamoDB.

DynamoDB

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

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

AEnvironment

BCostCenter

CProject

DService

Attempts:

3 left

💡 Hint

Common Mistakes

Selecting tags unrelated to cost management.

Confusing service tags with cost allocation tags.

Enabling the CostCenter tag helps allocate costs and manage budgets effectively.

3fill in blank

hard

Fix the error in the query to get DynamoDB cost data from AWS Cost Explorer.

DynamoDB

aws ce get-cost-and-usage --time-period Start=2023-01-01,End=2023-01-31 --granularity MONTHLY --metrics [1] --filter '{"Dimensions":{"Key":"SERVICE","Values":["DynamoDB"]}}'

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

AUnblendedCost

BBlendedCost

CUsageQuantity

DTotalCost

Attempts:

3 left

💡 Hint

Common Mistakes

Using UsageQuantity which shows usage, not cost.

Choosing TotalCost which is not a valid metric.

The UnblendedCost metric provides the actual cost without blending, which is accurate for cost management.

4fill in blank

hard

Fill both blanks to create a budget alert for DynamoDB costs exceeding $500.

DynamoDB

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

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

A500

B1000

CCOST

DUSAGE

Attempts:

3 left

💡 Hint

Common Mistakes

Setting the budget type to USAGE instead of COST.

Using an incorrect amount value.

The budget limit is set to 500 USD and the budget type is COST to track spending.

5fill in blank

hard

Fill all three blanks to filter DynamoDB cost data by linked account and service.

DynamoDB

aws ce get-cost-and-usage --time-period Start=2023-05-01,End=2023-05-31 --granularity DAILY --metrics [1] --filter '{"And":[{"Dimensions":{"Key":"[2]","Values":["[3]"]}},{"Dimensions":{"Key":"SERVICE","Values":["Amazon DynamoDB"]}}]}'

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

AUnblendedCost

BLINKED_ACCOUNT

C123456789012

DUsageQuantity

Attempts:

3 left

💡 Hint

Common Mistakes

Using UsageQuantity instead of a cost metric.

Using SERVICE as the filter key for account ID.

The metric UnblendedCost shows actual cost. The filter uses LINKED_ACCOUNT key with the account ID 123456789012 to narrow down costs.