Question 380
A platform governance committee considers: A finance report uses RANK to assign unique row numbers but produces ties and gaps in the sequence. What preventive check should be standardized?
Explanation
Correct Answer
Document expected tie behavior in analytic report requirements. This reduces recurrence of: ROW_NUMBER, RANK and DENSE_RANK differ in tie handling and numbering gaps. The verification should demonstrate: A controlled tie fixture shows precisely the required ranking behavior.
Incorrect Answers
Test idempotent replay and multiple-source-match conflicts before release. That safeguard is aimed at ANOTHER risk: A developer wants to update target customer records from daily source changes but uses INSERT for every delivery. It is less targeted than the control for: ROW_NUMBER, RANK and DENSE_RANK differ in tie handling and numbering gaps.
Include NULL fixtures in transformation and business-rule regression tests. That safeguard is aimed at ANOTHER risk: A customer segmentation query uses CASE in multiple branches without handling NULL values and classifies unknown regions incorrectly. It is less targeted than the control for: ROW_NUMBER, RANK and DENSE_RANK differ in tie handling and numbering gaps.
Set freshness alerts and recovery playbooks for every critical stream. That safeguard is aimed at ANOTHER risk: An ingest pipeline uses a stream and task but falls behind for days beyond the underlying change-tracking retention period. It is less targeted than the control for: ROW_NUMBER, RANK and DENSE_RANK differ in tie handling and numbering gaps.