How should a team make use of code optimization advice generated for mainframe applications?
Select an answer to reveal the explanation.
Short Explanation
Treat optimization advice as a starting point for investigation, not a batch job you run and walk away from. Use it to spot candidate improvements, then validate that each change preserves the program's existing behaviour before applying it.
Full Explanation
The correct approach is to use optimization advice to identify candidate improvements, then validate that each one preserves the program's existing behaviour before it is applied. Optimization advice highlights places worth looking at, and each candidate change still needs to be validated so it does not alter the program's behaviour before it goes anywhere near production.
The approach that says to apply every suggestion the tool produces automatically is incorrect because it skips the validation step that catches advice that is unsuitable for the specific context.
The approach that says to use the suggestions as a guide for which unfamiliar sections of code can be safely deleted is incorrect because unfamiliarity with a section of code is not evidence it is safe, or even intended, to remove.
The approach that says to accept any suggestion that measurably improves runtime speed as correct without further checking is incorrect because a faster result that changes behaviour is a regression, not an improvement.
For the exam, treat optimization advice as candidates to evaluate, not instructions to execute blindly.