Question 430
During a scheduled ingestion recovery rehearsal at Eastport Research Hospital, the data engineering team identifies a Databricks issue: A source table contains multiple rows per order due to repeated extracts and a downstream report counts each copy independently. The team reports that the correction is complete. Which result BEST verifies that the specific issue was resolved?
Explanation
Correct Answer
The cleaned result retains the intended record per order and reconciles expected totals. The observation provides evidence that the proposed fix (Deduplicate using a stable business key and a documented precedence or event-time rule.) addressed the reported issue (A source table contains multiple rows per order due to repeated extracts and a downstream report counts each copy independently.) for Eastport Research Hospital and its medical research systems and directory accounts. It verifies an observable outcome instead of relying only on a completed task ticket.
Incorrect Answers
Events around the midnight boundary are assigned to the intended reporting day. This is suitable evidence for another condition (A daily aggregation mixes UTC event times with local dates without a time-zone conversion rule, shifting some transactions to wrong reporting days.) after a different response (Define and apply the business time-zone and event-time conversion consistently before date-based grouping.). For Eastport Research Hospital, it does not prove the required result: The cleaned result retains the intended record per order and reconciles expected totals.
Missing-address records follow the agreed exception path and accepted records meet the non-null contract. This is suitable evidence for another condition (An address field is required but incoming rows contain null values and the team ignores them until business reports fail.) after a different response (Apply a defined null-handling or quarantine rule before loading the required downstream dataset.). For Eastport Research Hospital, it does not prove the required result: The cleaned result retains the intended record per order and reconciles expected totals.
The lifetime-value total matches the transaction fact table without inflation caused by tag multiplicity. This is suitable evidence for another condition (A pipeline computes customer lifetime value using a raw many-to-many join that duplicates each transaction for every marketing tag.) after a different response (Aggregate or deduplicate at a documented grain before joining to many-valued classification data.). For Eastport Research Hospital, it does not prove the required result: The cleaned result retains the intended record per order and reconciles expected totals.