Question 830
A database team repairs this problem: A reporting dashboard uses asynchronous replica data but displays it as if it were current to the second. Which measured outcome validates the correction?
Explanation
Correct Answer
Displayed report timestamps reflect actual lag and meet the business limit. This distinguishes actual recovery from a merely healthy-looking console. The targeted correction was: Expose or enforce an appropriate replica freshness limit and route critical reads to current data.
Incorrect Answers
This finding relates to a situation in which a read replica of a large MySQL instance increasingly lags after a nightly reconciliation writes millions of rows. The current remediation must instead show that displayed report timestamps reflect actual lag and meet the business limit.
The result would be meaningful for a problem where a replication scaling change causes a database to exceed its approved network and storage budget even though user latency improved. For this question, closure depends on confirming that displayed report timestamps reflect actual lag and meet the business limit.
The result would be meaningful for a problem where a Bigtable table is created with dozens of column families for each sensor field and maintenance becomes difficult. For this question, closure depends on confirming that displayed report timestamps reflect actual lag and meet the business limit.