Question 210
A job dashboard counts every retry as a separate business delivery and inflates run totals. Which implementation choice BEST addresses the stated failure?
Explanation
Correct Answer
Distinguish retries and task attempts from distinct logical job executions. This is the most directly relevant remediation because attempt-level telemetry is not the same as successfully delivered business batches. A concrete acceptance check is: A simulated retry counts once for business delivery while retaining its attempts. To reduce recurrence: Store logical batch IDs with operational run metadata.
Incorrect Answers
Aggregate progress can conceal a blocked or overloaded stateful task. For the observed behavior, attempt-level telemetry is not the same as successfully delivered business batches.
Notebook execution counts do not directly capture all billable compute consumption. The controlling issue in this question is that attempt-level telemetry is not the same as successfully delivered business batches.
Saving the query does not guarantee downstream notification transport succeeds. The reported failure instead depends on this fact: attempt-level telemetry is not the same as successfully delivered business batches.