SAA-C03 ยท Cost management, databases and network costs
Cost-effective database choices
DynamoDB on-demand versus provisioned with auto scaling, Aurora Serverless v2, reserved DB instances, and snapshot frequency and retention costs.
Key points
- DynamoDB on-demand (default): per request, no planning; new, spiky, unknown traffic.
- Provisioned: hourly for set capacity, used or not; steady traffic, auto scaling, reserved capacity.
- Aurora Serverless v2: ACU-hours; 1 ACU ~2 GiB memory plus CPU; 0 (auto-pause) to 256 ACUs, 0.5 steps.
- Steady 24/7 relational: Reserved DB instances (1 or 3 years).
- Backups: short retention; delete unused manual snapshots (kept until deleted).
Source: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2.how-it-works.html
Practice questions
In Aurora Serverless v2, roughly how much memory does one Aurora capacity unit (ACU) represent?
- About 512 MiB
- About 2 GiB
- About 8 GiB
- About 16 GiB
Show answer
Answer: B. About 2 GiB
Each ACU combines about 2 GiB of memory with matching CPU and networking, and you set the minimum and maximum ACUs for the cluster. The other values do not match the ACU definition.
Which statements about DynamoDB capacity modes are correct?
- On-demand mode charges per read and write request
- Provisioned mode charges for configured capacity even if unused
- On-demand is the default capacity mode for new tables
- Provisioned mode removes all need for capacity planning
- On-demand mode requires you to write auto scaling policies
Show answer
Answer: A. On-demand mode charges per read and write request, B. Provisioned mode charges for configured capacity even if unused, C. On-demand is the default capacity mode for new tables
On-demand is the default mode and bills per read and write request; provisioned mode bills for the capacity you configure per hour even if it goes unused. Provisioned mode does need capacity planning (or auto scaling), and on-demand needs no scaling policies at all.
With a DynamoDB table in provisioned mode, you pay only for the read and write capacity your application actually consumes.
Show answer
Answer: False
False. Provisioned mode bills for the capacity you configured each hour, whether or not it is used. Paying only for consumed requests is how on-demand mode works, which is why idle provisioned capacity is wasted money.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
