Question 460
A platform governance committee considers: A transformation joins sales to a dimension table with two overlapping effective-date records and duplicates revenues. What preventive check should be standardized?
Explanation
Correct Answer
Validate uniqueness and date-range integrity for type-2 dimensions. This reduces recurrence of: An ambiguous many-to-many effective-date join duplicates fact rows rather than refining them. The verification should demonstrate: The joined result counts each sales event once and resolves the intended dimension version.
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: An ambiguous many-to-many effective-date join duplicates fact rows rather than refining them.
Document expected tie behavior in analytic report requirements. That safeguard is aimed at ANOTHER risk: A finance report uses RANK to assign unique row numbers but produces ties and gaps in the sequence. It is less targeted than the control for: An ambiguous many-to-many effective-date join duplicates fact rows rather than refining them.
Monitor refresh failure signals and run schema-compatibility tests before source deployments. That safeguard is aimed at ANOTHER risk: An incremental dynamic table refresh repeatedly fails after an upstream schema change, but analysts continue trusting stale downstream data. It is less targeted than the control for: An ambiguous many-to-many effective-date join duplicates fact rows rather than refining them.