The answer is to use a higher-cardinality partition key that distributes writes across partitions. This is correct because a low-cardinality key like the current date funnels all writes into a single partition, causing DynamoDB write throttling when traffic spikes during business hours. By designing a high-cardinality partition key—such as combining the date with a random suffix or user ID—you ensure writes are spread evenly across partitions, fully utilizing provisioned write capacity without needing custom scripts. On the SAA-C03 exam, this scenario tests your understanding of partition design and hot partition mitigation, a common trap being to overcomplicate solutions with scripts or secondary indexes. The key insight is that DynamoDB’s throughput is per-partition, so a single hot partition throttles even if total capacity is unused. Memory tip: “Low cardinality, high throttling; high cardinality, smooth sailing.”
SAA-C03 Design High-Performing Architectures Practice Question
This SAA-C03 practice question tests your understanding of design high-performing architectures. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. A key principle to apply: dynamoDB distributes data and throughput based on the partition key.. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A DynamoDB table for a travel booking site has a partition key based only on the current date. Write throttling occurs during business hours. What is the best design change? The design must avoid adding custom operational scripts.
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a higher-cardinality partition key that distributes writes across partitions
Option D is correct because using a low-cardinality partition key like the current date causes all writes to land on a single partition, leading to throttling. By designing a higher-cardinality key (e.g., combining date with a random suffix or user ID), writes are distributed evenly across partitions, fully utilizing the provisioned write capacity without custom scripts.
Key principle: DynamoDB distributes data and throughput based on the partition key.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Create a global secondary index with the same date key
Why it's wrong here
A GSI with the same hot key can suffer the same partition problem.
✗
Move the table to S3 Glacier Instant Retrieval
Why it's wrong here
S3 Glacier is object storage and not a DynamoDB write scaling solution.
✗
Reduce the table's write capacity
Why it's wrong here
Reducing capacity worsens throttling.
✓
Use a higher-cardinality partition key that distributes writes across partitions
Why this is correct
A low-cardinality hot partition causes throttling; a better key spreads writes more evenly.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
DynamoDB distributes data and throughput based on the partition key.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think adding a GSI (Option A) solves the issue, but GSIs inherit the same partition key design flaws and can also throttle independently.
Detailed technical explanation
How to think about this question
DynamoDB partitions data by the partition key's hash value; a low-cardinality key like a date hashes to the same partition, causing a 'hot partition.' A higher-cardinality key (e.g., '2025-03-28#user123') spreads writes across multiple partitions, each with its own 1,000 WCU limit. This design leverages DynamoDB's internal hash distribution without needing custom sharding logic.
KKey Concepts to Remember
DynamoDB distributes data and throughput based on the partition key.
A 'hot partition' occurs when a single partition key receives excessive requests, causing throttling.
High-cardinality partition keys distribute writes more evenly across partitions.
Redesigning the partition key is crucial for avoiding hot partitions and improving write scalability.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
DynamoDB distributes data and throughput based on the partition key.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Review dynamoDB distributes data and throughput based on the partition key., then practise related SAA-C03 questions on the same topic to reinforce the concept.
Design High-Performing Architectures — This question tests Design High-Performing Architectures — DynamoDB distributes data and throughput based on the partition key..
What is the correct answer to this question?
The correct answer is: Use a higher-cardinality partition key that distributes writes across partitions — Option D is correct because using a low-cardinality partition key like the current date causes all writes to land on a single partition, leading to throttling. By designing a higher-cardinality key (e.g., combining date with a random suffix or user ID), writes are distributed evenly across partitions, fully utilizing the provisioned write capacity without custom scripts.
What should I do if I get this SAA-C03 question wrong?
Review dynamoDB distributes data and throughput based on the partition key., then practise related SAA-C03 questions on the same topic to reinforce the concept.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
What is the key concept behind this question?
DynamoDB distributes data and throughput based on the partition key.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A DynamoDB table for a travel booking site has a partition key based only on the current date. Write throttling occurs during business hours. What is the best design change? The architecture review board prefers a managed AWS-native control.
hard
A.Create a global secondary index with the same date key
B.Move the table to S3 Glacier Instant Retrieval
C.Reduce the table's write capacity
✓ D.Use a higher-cardinality partition key that distributes writes across partitions
Why D: Option D is correct because using a low-cardinality partition key like the current date causes all writes to land on a single partition, leading to throttling. By choosing a higher-cardinality partition key (e.g., combining date with a user ID or booking ID), writes are distributed evenly across multiple partitions, leveraging DynamoDB's internal partitioning to handle the throughput. This is a managed, AWS-native design change that resolves hot partition issues without additional services.
Variation 2. A DynamoDB table for a travel booking site has a partition key based only on the current date. Write throttling occurs during business hours. What is the best design change?
hard
A.Create a global secondary index with the same date key
B.Move the table to S3 Glacier Instant Retrieval
C.Reduce the table's write capacity
✓ D.Use a higher-cardinality partition key that distributes writes across partitions
Why D: Option D is correct because using a low-cardinality partition key like the current date concentrates all writes into a single partition, causing throttling when write demand exceeds that partition's 1,000 WCU limit. A higher-cardinality key (e.g., combining date with user ID or session ID) distributes writes evenly across multiple partitions, allowing the table to use its full provisioned write capacity without throttling.
Last reviewed: Jun 11, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.