Question 20
An engineer schedules an hourly refresh but executives expect source changes visible in five minutes. Which change most directly addresses the operational problem?
Explanation
Correct Answer
Align pipeline trigger or refresh cadence and table type with the explicit freshness SLA. This is the most directly relevant remediation because a correct data definition does not guarantee latency lower than its update schedule. A concrete acceptance check is: A timestamped source change appears within the measured five-minute target. To reduce recurrence: Alert on end-to-end freshness rather than job completion alone.
Incorrect Answers
Timer schedules are unrelated to actual upstream file availability. Here the important technical distinction is that a correct data definition does not guarantee latency lower than its update schedule.
Pipeline scheduling requires explicit data lineage to enforce upstream-before-downstream execution. The reported failure instead depends on this fact: a correct data definition does not guarantee latency lower than its update schedule.
At-least-once event transport can replay the same logical change. That consideration does not remove the current constraint: a correct data definition does not guarantee latency lower than its update schedule.