A batch job's comments were rewritten to be clearer, with the executable logic left untouched, and the change was logged as an optimisation pass. What is wrong with that approach?
Select an answer to reveal the explanation.
Short Explanation
You can rewrite every comment in the file and the CPU still does exactly what it did before. Comments don't affect runtime behaviour, so that change isn't an optimisation.
Full Explanation
The correct answer is the statement that comments do not affect runtime behaviour, so rewriting them cannot improve performance regardless of how much clearer they read. Optimisation concerns executed code; comments are documentation and are stripped or ignored at compile and run time, so touching them cannot change throughput, latency or resource use. The option claiming comment rewrites add compilation risk is wrong because comment-only edits carry essentially no compilation risk. The option requiring separate team review of comments is wrong because no such review requirement is tied to comments specifically. The option saying clearer comments trigger stricter compliance policy is wrong because compliance policy is not triggered by comment wording. For the exam, target executable paths, not comments, when the goal is performance.