After mappers emit (reason-code, 1) pairs for municipal 311 tickets, what must the shuffle and group stages guarantee before reduce runs?
Select an answer to reveal the explanation.
Short Explanation
Think of sorting mail into one bin per zip code before anyone totals the letters. Shuffle and group pull every sticky note with the same reason code into the same reducer. Without that co-location, citywide tallies would be incomplete.
Full Explanation
Shuffle and group are the bridge between map and reduce: the framework partitions, sorts, and groups intermediate pairs by key. Same-key co-location is what lets a reducer see the full value list for each reason code. Randomly separating identical keys would break aggregation. MapReduce does not require writing intermediates to a public API or turning keys into ML embeddings.