Question 800
Query Profile shows 85% of time spent in a SortMergeJoin with extensive exchange traffic. Which long-term safeguard BEST reduces recurrence?
Explanation
Correct Answer
Track plan changes as table sizes grow. This is the most directly relevant preventive control because shuffling large join inputs dominates execution when a smaller side could be broadcast. A concrete acceptance check is: The new profile shows less network shuffle and acceptable executor memory. To reduce recurrence: Track plan changes as table sizes grow.
Incorrect Answers
Update events can contain both before and after versions for one source operation. Here the important technical distinction is that shuffling large join inputs dominates execution when a smaller side could be broadcast.
Excessive partition cardinality generates tiny files and expensive metadata operations. The reported failure instead depends on this fact: shuffling large join inputs dominates execution when a smaller side could be broadcast.
Clustering cost can exceed benefit on trivially small datasets. That consideration does not remove the current constraint: shuffling large join inputs dominates execution when a smaller side could be broadcast.