0
0
DynamoDBquery~20 mins

Why cost management prevents surprises in DynamoDB - Challenge Your Understanding

Choose your learning style9 modes available
Challenge - 5 Problems
🎖️
Cost Management Mastery
Get all challenges correct to earn this badge!
Test your skills under time pressure!
🧠 Conceptual
intermediate
2:00remaining
Understanding Cost Management Benefits
Why is cost management important in DynamoDB to prevent unexpected charges?
AIt disables billing to prevent any charges.
BIt automatically deletes unused tables to save money.
CIt increases read/write capacity without notifying the user.
DIt helps monitor usage and set alarms to avoid exceeding budget limits.
Attempts:
2 left
💡 Hint
Think about how tracking usage helps avoid surprises.
query_result
intermediate
2:00remaining
Identifying High-Cost Tables
Given a DynamoDB billing report, which table shows the highest cost for the month?
DynamoDB
TableName | ReadCapacityUnits | WriteCapacityUnits | Cost
Users     | 100               | 50                | 120
Orders    | 200               | 100               | 250
Products  | 50                | 25                | 80
Logs      | 300               | 150               | 400
ALogs
BOrders
CProducts
DUsers
Attempts:
2 left
💡 Hint
Look for the highest cost value in the table.
📝 Syntax
advanced
2:30remaining
Correcting a Cost Alert Configuration
Which option correctly defines a DynamoDB cost alert using AWS CLI to notify when monthly charges exceed $100?
DynamoDB
aws cloudwatch put-metric-alarm --alarm-name DynamoDBCostAlert --metric-name EstimatedCharges --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 --dimensions Name=Currency,Value=USD
Aaws cloudwatch put-metric-alarm --alarm-name DynamoDBCostAlert --metric-name EstimatedCharges --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 --dimensions Name=Currency,Value=USD
Baws cloudwatch put-metric-alarm --alarm-name DynamoDBCostAlert --metric-name EstimatedCharges --namespace AWS/Billing --statistic Average --period 3600 --threshold 100 --comparison-operator LessThanThreshold --evaluation-periods 1 --alarm-actions arn:aws:sns:us-east-1:123456789012:NotifyMe --dimensions Name=Currency,Value=USD
Caws cloudwatch put-metric-alarm --alarm-name DynamoDBCostAlert --metric-name EstimatedCharges --namespace AWS/Billing --statistic Maximum --period 21600 --threshold 100 --comparison-operator LessThanThreshold --evaluation-periods 1 --alarm-actions arn:aws:sns:us-east-1:123456789012:NotifyMe --dimensions Name=Currency,Value=USD
Daws cloudwatch put-metric-alarm --alarm-name DynamoDBCostAlert --metric-name EstimatedCharges --namespace AWS/Billing --statistic Maximum --period 21600 --threshold 100 --comparison-operator GreaterThanThreshold --evaluation-periods 0 --alarm-actions arn:aws:sns:us-east-1:123456789012:NotifyMe --dimensions Name=Currency,Value=USD
Attempts:
2 left
💡 Hint
Check the comparison operator and evaluation periods for correctness.
optimization
advanced
2:00remaining
Reducing Unexpected DynamoDB Costs
Which strategy best helps reduce unexpected DynamoDB costs caused by sudden traffic spikes?
AManually increase capacity units once a month.
BDisable billing alerts to avoid distractions.
CEnable Auto Scaling for read and write capacity with defined limits.
DUse on-demand capacity mode without monitoring usage.
Attempts:
2 left
💡 Hint
Think about automatic adjustment to traffic changes.
🔧 Debug
expert
3:00remaining
Diagnosing Unexpected High Costs
A DynamoDB table shows unexpectedly high monthly costs. Which cause is most likely based on this query result? Query: SELECT TableName, ConsumedReadCapacityUnits, ConsumedWriteCapacityUnits FROM BillingReport WHERE Month = '2024-05'; Result: { "TableName": "UserActivity", "ConsumedReadCapacityUnits": 500000, "ConsumedWriteCapacityUnits": 1000000 } Options:
ABilling report is delayed and shows last month's data.
BA sudden increase in write operations caused the high cost.
CRead capacity units are too low causing throttling.
DThe table was deleted but billing still shows old data.
Attempts:
2 left
💡 Hint
Look at the capacity units consumed and relate to cost.