Question 220
A platform governance committee considers: A team needs the latest event per customer, but SELECT DISTINCT keeps multiple records with different timestamps. What preventive check should be standardized?
Explanation
Correct Answer
Require deterministic tie-breakers for latest-record deduplication. This reduces recurrence of: Window ranking selects rows by partition and order, unlike DISTINCT over complete row values. The verification should demonstrate: The result returns one predictable most-recent event for each customer.
Incorrect Answers
Alert when new categories appear outside approved reporting dimensions. That safeguard is aimed at ANOTHER risk: An analyst pivots event records to monthly metrics but assumes unexpected new event categories appear automatically in a fixed static pivot. It is less targeted than the control for: Window ranking selects rows by partition and order, unlike DISTINCT over complete row values.
Include empty-array and missing-key cases in flattening tests. That safeguard is aimed at ANOTHER risk: A dataset stores orders as nested JSON arrays, but a report produces one row per order instead of one per line item. It is less targeted than the control for: Window ranking selects rows by partition and order, unlike DISTINCT over complete row values.
Require performance and cost evidence rather than raw elapsed time alone. That safeguard is aimed at ANOTHER risk: A data engineer expects a larger warehouse always to reduce a query's credit cost even if runtime barely changes. It is less targeted than the control for: Window ranking selects rows by partition and order, unlike DISTINCT over complete row values.