Data stewards want to confirm how many permit records entered and left each stage of a nightly MapReduce cleanse. What MapReduce observability feature supports that check?
Select an answer to reveal the explanation.
Short Explanation
Counters are the trip odometer on the MapReduce truck—records in, records out, weird rejects. Stewards use them to sanity-check civic data quality overnight. Turning metrics off or never committing output hides the truth.
Full Explanation
MapReduce jobs expose counters for framework and user-defined metrics such as records read, written, or rejected. Civic data-quality teams use those numbers to validate nightly cleanses. Disabling job history, avoiding durable commits, or removing metadata works against observability goals.