AWS's fully managed NoSQL database, and when to reach for it over relational. Seven questions, CLF-C02, 2026 edition.
Try 7 free Amazon DynamoDB questions in the exam's own style — every answer explained, no sign-up.
Straight to the 7 free questions ↓DynamoDB is AWS’s fully managed NoSQL database, and the exam tests two things: what that means, and when to reach for it instead of a relational database. Neither needs hands-on modelling — just the ability to match a data shape to the right service.
Amazon DynamoDB stores data in a key-value and document model — you fetch items by key rather than joining relational tables. It is fully managed: AWS runs the servers, scaling, patching and replication, so there is nothing to provision. And it delivers consistent single-digit-millisecond performance at any scale, which is its headline promise. When a question stresses NoSQL, key-value, and fast at scale, it is describing DynamoDB.
DynamoDB has two capacity modes, and the exam may ask which fits:
Unpredictable points to on-demand; steady and predictable points to provisioned.
The choice the exam plants most is DynamoDB against a relational database:
Read the data shape. Joins across tables → RDS. Schema-less, huge scale, key lookups → DynamoDB. Typical DynamoDB use cases are high-traffic web and mobile apps: user profiles, session state, shopping carts.
For multi-Region, low-latency access with a local copy everywhere, DynamoDB offers global tables, which replicate a table across Regions. That is distinct from RDS’s Multi-AZ and read replicas, which the exam may offer as distractors.
Answer each one before you reveal the explanation, and when you miss, read past the correct letter to why the other three fail. The distractors are always another data service — RDS where NoSQL belongs, Redshift or S3 offered for the wrong job. Matching the data shape to DynamoDB is the whole skill, and the reasoning below drills it. For the wider picture, see the databases overview.
In which data model does Amazon DynamoDB store data?
DynamoDB is a NoSQL database using a key-value and document model — you retrieve items by key rather than joining relational tables. Why not the others: relational with SQL joins describes RDS/Aurora, a data warehouse is Redshift, and a graph model is Amazon Neptune. Key-value/document NoSQL is DynamoDB.
What does it mean that DynamoDB is 'fully managed'?
Fully managed means AWS operates everything underneath — servers, scaling, patching, replication — and you just use the database. Why not the others: you do not run it on EC2 or manage servers yourself (that would be the opposite of managed), and it is a cloud service, not on-premises. No infrastructure to manage is the point.
What performance does DynamoDB provide?
DynamoDB is built to deliver consistent single-digit-millisecond latency regardless of how large the table grows. Why not the others: it does not slow down as data grows, it is not limited to small datasets, and its performance is designed to be consistent rather than unpredictable. Fast and steady at scale is the DynamoDB promise.
DynamoDB offers on-demand and provisioned capacity modes. What is on-demand mode best suited for?
On-demand capacity charges per request and scales automatically, which suits workloads whose traffic you cannot predict — no capacity planning required. Why not the others: steady, predictable workloads are exactly where provisioned capacity can be cheaper. DynamoDB is built to scale, and archival storage is S3 Glacier, not DynamoDB. Unpredictable traffic points to on-demand.
Which is a reason to choose DynamoDB over Amazon RDS?
DynamoDB fits flexible, schema-less data at huge scale with fast key lookups — the NoSQL profile. Why not the others: complex joins across relational tables are exactly what RDS/Aurora are for. A data warehouse is Redshift. Large media files belong in S3. Schema-less scale with key lookups is the DynamoDB case.
How can DynamoDB serve users in multiple AWS Regions with low latency and a local copy of the data?
DynamoDB global tables replicate a table across multiple Regions so users everywhere read and write to a nearby copy. Why not the others: a Multi-AZ standby and read replicas are RDS concepts within or near one Region, and CloudFront caches content, not database writes. Multi-Region replication is global tables.
Which is a typical use case for DynamoDB?
DynamoDB shines for high-traffic applications that look data up by key quickly — profiles, sessions, carts. Why not the others: joined relational reporting is RDS/Aurora, cold archival is S3 Glacier, and warehouse analytics is Redshift. Fast key-based lookups at scale is the DynamoDB use case.
That is exactly how every question in the course works — answer, explanation, why-not. The real set continues in the practice player: 10 free questions, no sign-up.
Continue with the 10 free questions →The exam does not test whether you recognise a term — it tests whether you can rule out three plausible answers under time pressure. That is what the explanations above are for, and there are 390 more questions built exactly like them.
Collecting questions yourself
Practising with a system
Straight into the player. No account, no email.
Updated for CLF-C02 (July 2026). The sample questions above are our own work in the style of the exam — not real exam items. The exam itself is set and marked by the certification body.