Question 130
A dashboard query returns too many intermediate rows after joining two tables with nonunique keys. Before implementing the planned approach, which prerequisite should be checked most directly?
Explanation
Correct Answer
Check whether the join keys are unique or whether a missing predicate causes fan-out. The condition matters because an exploding join can multiply intermediate rows and dominate both execution cost and runtime.
Incorrect Answers
Confirm predicate compatibility, query frequency and maintenance/credit costs. That preparatory check belongs to a huge event table receives repeated point-lookups on a highly selective identifier. Here, the decisive check is check whether the join keys are unique or whether a missing predicate causes fan-out.
Check package compatibility, connection context and warehouse resource sizing. That preparatory check belongs to a Python developer wants to filter and join large Snowflake DataFrames without pulling all rows into pandas. Here, the decisive check is check whether the join keys are unique or whether a missing predicate causes fan-out.
Check eligibility, workload characteristics, and cost settings before enabling. That preparatory check belongs to a large eligible analytical query has heavy scan and filter work that may be offloaded for faster completion. Here, the decisive check is check whether the join keys are unique or whether a missing predicate causes fan-out.





SnowPro Core COF-C03 Practice Tests