Question 751 of 1,663
DBS-C01 Monitoring and Troubleshooting Practice Question
A company uses Amazon DynamoDB with global tables. They notice that changes made in one region are not appearing in another region after several minutes. Which CloudWatch metric should be monitored to check the replication lag?
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
✓
ReplicationLatency
ReplicationLatency measures the time between the last update on the source table and the last update on the replica table. Option A (ConsumedWriteCapacityUnits) is wrong because it measures write capacity usage, not replication lag. Option B (SuccessfulRequestLatency) is wrong because it measures request latency, not replication lag. Option D (ThrottledRequests) is wrong because it indicates throttling, not replication lag.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
ConsumedWriteCapacityUnits
Why it's wrong here
ConsumedWriteCapacityUnits measures the amount of write capacity units consumed by DynamoDB, not replication lag.
- ✗
SuccessfulRequestLatency
Why it's wrong here
SuccessfulRequestLatency measures the time taken for successful requests to complete, not the delay in replication.
- ✓
ReplicationLatency
Why this is correct
ReplicationLatency directly measures the time between an update on the source table and its appearance on a replica, making it the correct metric to monitor replication lag.
- ✗
ThrottledRequests
Why it's wrong here
ThrottledRequests counts requests that were throttled due to exceeding provisioned capacity, not replication lag.
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 way 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 uses Amazon DynamoDB global tables for a multi-region application. They notice that writes in one region are not appearing in another region after several minutes. What should they check first?
medium- ✓ A.Check the ReplicationLatency metric in Amazon CloudWatch
- B.Verify that auto scaling is configured identically in both regions
- C.Ensure DynamoDB Streams are enabled on the table
- D.Check the table size in both regions
Why A: The ReplicationLatency metric in CloudWatch directly measures the delay between a write in one region and its replication to another region in DynamoDB global tables. This is the most relevant metric to diagnose replication delays. Option B (auto scaling) affects capacity provisioning, not replication timing. Option C (DynamoDB Streams) are enabled by default for global tables to facilitate replication, but checking the metric is the immediate next step if delays are observed. Option D (table size) does not directly cause replication delays; replication is asynchronous and not size-dependent.
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.