Question 470
A customer can have multiple transactions at exactly the same timestamp, and an analyst must return one predictably chosen latest transaction per customer. Which choice is the best corrective decision?
Explanation
Correct Answer
ROW_NUMBER with an explicit tie-breaking column creates stable per-customer selection even when timestamps alone cannot distinguish records. This selection must be evaluated against the exact requirement: A customer can have multiple transactions at exactly the same timestamp, and an analyst must return one predictably chosen latest transaction per customer.
Incorrect Answers
A global LIMIT chooses one row overall, not one reproducible row within each customer group. The scenario to solve is: A customer can have multiple transactions at exactly the same timestamp, and an analyst must return one predictably chosen latest transaction per customer.
More compute cannot resolve a logical tie between equal timestamps or define business ordering. The scenario to solve is: A customer can have multiple transactions at exactly the same timestamp, and an analyst must return one predictably chosen latest transaction per customer.
Metadata caching can help planning but cannot choose a business-specific tie-breaker. The scenario to solve is: A customer can have multiple transactions at exactly the same timestamp, and an analyst must return one predictably chosen latest transaction per customer.





SnowPro Core COF-C03 Practice Tests