During a pilot, an administrator finds that an applied optimization suggestion has changed a batch job's output totals. What does this symptom indicate?
Select an answer to reveal the explanation.
Short Explanation
If a batch job's totals change after you apply an optimization, that means the suggestion wasn't validated well enough. You should've confirmed the behavior stayed the same before shipping it.
Full Explanation
Optimization advice should improve how code runs while leaving what it computes unchanged. A shift in output totals is the signature of a suggestion that was applied without confirming it preserved behaviour, so the answer about inadequate validation altering preserved behaviour is correct. The answer claiming the prior totals were wrong and the new totals are corrected is incorrect because nothing in the scenario supports that assumption. The answer saying the tool is defective and should be uninstalled is incorrect because offering a suggestion that needed validation is not itself a defect; skipping validation is the process gap. The answer saying the change is expected and unrelated because performance changes do not affect output values is incorrect because performance-focused changes can alter behaviour, especially around ordering, precision, or loop conditions. For the exam, treat any change in computed results after an optimization as a validation failure to investigate.