Question 520
An engineer schedules an hourly refresh but executives expect source changes visible in five minutes. Which principle BEST explains why the implementation failed?
Explanation
Correct Answer
A correct data definition does not guarantee latency lower than its update schedule. This is the most directly relevant technical explanation 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. That consideration does not remove the current constraint: a correct data definition does not guarantee latency lower than its update schedule.
Unbounded event-time join state retains data awaiting hypothetical future matches. For the observed behavior, a correct data definition does not guarantee latency lower than its update schedule.
Data quality edge cases may never appear in basic valid-row samples. The controlling issue in this question is that a correct data definition does not guarantee latency lower than its update schedule.