- A
Review the CloudWatch metrics for ReplicationLatency and PendingReplicationCount for the global table.
These metrics show the replication status and can identify delays or errors in the replication process.
- B
Modify the application to use the eu-west-1 endpoint for writes.
Why wrong: Writes to the global table are replicated automatically; using the local endpoint does not fix replication issues.
- C
Check that the table has an active DynamoDB Streams stream with StreamSpecification set to KEYS_ONLY.
Why wrong: Global tables require streams to be enabled, but they are automatically configured; checking this does not diagnose the delay.
- D
Verify that the TTL attribute on the table is correctly configured.
Why wrong: TTL is for item expiration, not replication; it does not affect replication delays.
Diagnosing DynamoDB Global Tables Replication Latency
This DBS-C01 practice question tests your understanding of management and operations. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. 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 company uses Amazon DynamoDB with global tables for a multi-region application. The application writes to the table in us-east-1. A developer notices that updates made in us-east-1 are not appearing in the replica in eu-west-1 after several minutes. Which action should be taken to diagnose the issue?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Review the CloudWatch metrics for ReplicationLatency and PendingReplicationCount for the global table.
Option A is correct because CloudWatch metrics ReplicationLatency (the time lag between when an item is written to one replica and when it appears in another) and PendingReplicationCount (the number of items waiting to be replicated) directly help diagnose replication delays in DynamoDB global tables. Option B is incorrect because writes should continue to the local region (us-east-1); using the eu-west-1 endpoint would not resolve replication latency and could cause consistency issues. Option C is incorrect because DynamoDB Streams is automatically enabled for global tables with NEW_AND_OLD_IMAGES (not KEYS_ONLY) to replicate updates; checking the stream specification is not a diagnostic step for delays. Option D is incorrect because TTL (Time to Live) is for automatic item expiration, not related to replication performance or delays.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Review the CloudWatch metrics for ReplicationLatency and PendingReplicationCount for the global table.
Why this is correct
These metrics show the replication status and can identify delays or errors in the replication process.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Modify the application to use the eu-west-1 endpoint for writes.
Why it's wrong here
Writes to the global table are replicated automatically; using the local endpoint does not fix replication issues.
- ✗
Check that the table has an active DynamoDB Streams stream with StreamSpecification set to KEYS_ONLY.
Why it's wrong here
Global tables require streams to be enabled, but they are automatically configured; checking this does not diagnose the delay.
- ✗
Verify that the TTL attribute on the table is correctly configured.
Why it's wrong here
TTL is for item expiration, not replication; it does not affect replication delays.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
- Use explanations to understand the rule behind the answer.
TExam Day Tips
- Underline the problem statement mentally.
- 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
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Visual reference
What to study next
Got this wrong? Here's your next step.
Identify which DBS-C01 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
- →
Management and Operations — study guide chapter
Learn the concepts, then practise the questions
- →
Management and Operations practice questions
Targeted practice on this topic area only
- →
All DBS-C01 questions
1,730 questions across all exam domains
- →
AWS Certified Database Specialty DBS-C01 study guide
Full concept coverage aligned to exam objectives
- →
DBS-C01 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related DBS-C01 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Workload-Specific Database Design practice questions
Practise DBS-C01 questions linked to Workload-Specific Database Design.
Deployment and Migration practice questions
Practise DBS-C01 questions linked to Deployment and Migration.
Management and Operations practice questions
Practise DBS-C01 questions linked to Management and Operations.
Monitoring and Troubleshooting practice questions
Practise DBS-C01 questions linked to Monitoring and Troubleshooting.
Database Security practice questions
Practise DBS-C01 questions linked to Database Security.
DBS-C01 fundamentals practice questions
Practise DBS-C01 questions linked to DBS-C01 fundamentals.
DBS-C01 scenario practice questions
Practise DBS-C01 questions linked to DBS-C01 scenario.
DBS-C01 troubleshooting practice questions
Practise DBS-C01 questions linked to DBS-C01 troubleshooting.
Practice this exam
Start a free DBS-C01 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this DBS-C01 question test?
Management and Operations — This question tests Management and Operations — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Review the CloudWatch metrics for ReplicationLatency and PendingReplicationCount for the global table. — Option A is correct because CloudWatch metrics ReplicationLatency (the time lag between when an item is written to one replica and when it appears in another) and PendingReplicationCount (the number of items waiting to be replicated) directly help diagnose replication delays in DynamoDB global tables. Option B is incorrect because writes should continue to the local region (us-east-1); using the eu-west-1 endpoint would not resolve replication latency and could cause consistency issues. Option C is incorrect because DynamoDB Streams is automatically enabled for global tables with NEW_AND_OLD_IMAGES (not KEYS_ONLY) to replicate updates; checking the stream specification is not a diagnostic step for delays. Option D is incorrect because TTL (Time to Live) is for automatic item expiration, not related to replication performance or delays.
What should I do if I get this DBS-C01 question wrong?
Identify which DBS-C01 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
Same concept, more angles
1 more ways this is tested on DBS-C01
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 company is using Amazon DynamoDB with global tables (multi-region) for a gaming application. The application writes to a table in us-east-1 and reads from a table in eu-west-1. The team notices that writes in us-east-1 are taking longer than expected to propagate to eu-west-1. What is the most likely cause?
hard- ✓ A.Network latency between the regions is causing replication delay
- B.The write capacity in eu-west-1 is insufficient
- C.Conflicts are being resolved due to concurrent writes
- D.DynamoDB Streams is disabled on the table
Why A: The correct answer is A because DynamoDB global tables use asynchronous replication across regions, and network latency between regions is the primary factor causing delays in propagation. Option B is incorrect because read and write capacity is independent per region; insufficient capacity in eu-west-1 does not affect replication speed from us-east-1. Option C is incorrect while conflict resolution can occur with concurrent writes, it does not inherently cause delays; replication delay is due to network latency. Option D is incorrect because DynamoDB Streams are required for global tables to function; if they were disabled, replication would not occur at all, not just be delayed.
Keep practising
More DBS-C01 practice questions
- A company is deploying a new application on Amazon RDS for PostgreSQL. The security policy requires that all data be enc…
- Match each AWS service to its primary purpose.
- A financial services company runs a production Amazon Aurora MySQL database cluster (1 writer, 2 readers) in us-east-1.…
- A company is designing a database for a global e-commerce platform that requires low-latency reads and writes from multi…
- A security auditor reviews the output of a DynamoDB table description command as shown in the exhibit. Which statement a…
- A company is migrating an on-premises Oracle database to Amazon RDS for Oracle. The database contains sensitive data tha…
Last reviewed: Jun 20, 2026
This DBS-C01 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 DBS-C01 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.