Question 290
A review of the governed data platform at Aspen Digital documents this problem: A source produces continuous events requiring minute-level freshness but the team proposes a once-nightly batch load. The team reports that the correction is complete. Which result BEST verifies that the specific issue was resolved?
Explanation
Correct Answer
An event published during the test appears in the destination within the required freshness interval. The observation provides evidence that the proposed fix (Choose a streaming ingestion design with an achievable latency and checkpointing strategy.) addressed the reported issue (A source produces continuous events requiring minute-level freshness but the team proposes a once-nightly batch load.) for Aspen Digital and its client advisory systems and shared files. It verifies an observable outcome instead of relying only on a completed task ticket.
Incorrect Answers
The approved connector transfers the expected source records without the custom screen-scraping dependency. This is suitable evidence for another condition (A SaaS source has a supported managed Lakeflow connector but engineers schedule fragile screen-scraping notebooks for every ingestion cycle.) after a different response (Evaluate Lakeflow Connect for its supported connector and managed ingestion lifecycle.). For Aspen Digital, it does not prove the required result: An event published during the test appears in the destination within the required freshness interval.
A sample of events in the same day retains their distinct required timestamps and ordering. This is suitable evidence for another condition (An event model records only day-level timestamps despite a requirement to audit sub-minute sequence and ordering.) after a different response (Model time columns at a supported granularity that retains the required event resolution.). For Aspen Digital, it does not prove the required result: An event published during the test appears in the destination within the required freshness interval.
A changed label replaces the prior value without creating unnecessary historical dimension rows. This is suitable evidence for another condition (A lookup attribute must always show the latest label and no historical label versions are needed.) after a different response (Choose an SCD Type 1 overwrite strategy for that specific attribute.). For Aspen Digital, it does not prove the required result: An event published during the test appears in the destination within the required freshness interval.