Question 300
Query Profile shows 85% of time spent in a SortMergeJoin with extensive exchange traffic. Which observation BEST proves that the corrective action succeeded?
Explanation
Correct Answer
The new profile shows less network shuffle and acceptable executor memory. This is the most directly relevant verification 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
Physical locality should reflect current frequently filtered dimensions. The controlling issue in this question is that shuffling large join inputs dominates execution when a smaller side could be broadcast.
Background adaptive maintenance is not synonymous with synchronous full-table rewrite. Here the important technical distinction is that shuffling large join inputs dominates execution when a smaller side could be broadcast.
Overlapping compaction or layout jobs can waste compute or interfere with predictable operations. The reported failure instead depends on this fact: shuffling large join inputs dominates execution when a smaller side could be broadcast.