CV0-003 · Question #438
Asynchronous data replication for a SaaS application occurs between Regions A and B. Users in Region A are reporting that the most current data for an insurance claims application is not available…
The correct answer is D. Check the storage commit logs in both regions. When asynchronous replication is delayed despite available network bandwidth, the bottleneck is likely in the storage write or commit process. Storage commit logs reveal the exact timing of when data writes are finalized, directly identifying the source of the delay.
Question
Asynchronous data replication for a SaaS application occurs between Regions A and B. Users in Region A are reporting that the most current data for an insurance claims application is not available to them until after 11:30 a.m. The cloud administrator for this SaaS provider checks the network utilization and finds that only about 10% of the network bandwidth is being used. Which of the following describes how the cloud administrator could BEST resolve this issue?
Options
- ACheck the storage utilization logs in both regions.
- BCheck the RAM utilization logs in both regions.
- CCheck the CPU utilization logs in both regions.
- DCheck the storage commit logs in both regions.
How the community answered
(18 responses)- A17% (3)
- B6% (1)
- C11% (2)
- D67% (12)
Why each option
When asynchronous replication is delayed despite available network bandwidth, the bottleneck is likely in the storage write or commit process. Storage commit logs reveal the exact timing of when data writes are finalized, directly identifying the source of the delay.
Storage utilization logs show capacity consumption over time but do not capture the timing of individual data write commits, so they would not identify a commit-based replication delay.
RAM utilization logs track memory consumption and have no bearing on why replicated data is unavailable until a specific time each day.
CPU utilization logs show processor load but do not provide information about storage write commit timing that would explain the data availability delay.
Storage commit logs record when data writes are actually committed to persistent storage in each region. Since network bandwidth is not the bottleneck at only 10% utilization, the delay in data availability until 11:30 a.m. points to a storage commit queue backlog or a scheduled batch commit process. Reviewing the commit logs in both regions would reveal whether writes are queued, throttled, or batched in a way that explains the consistent daily delay.
Concept tested: Diagnosing asynchronous replication delays via storage commit logs
Topics
Community Discussion
No community discussion yet for this question.