Which statement best summarises how a team should handle code optimization advice for a mainframe modernisation project?
Select an answer to reveal the explanation.
Short Explanation
Optimization advice earns its keep after validation, not instead of it. You use the advice to spot improvement opportunities, then test each accepted change to prove the program still behaves the same.
Full Explanation
The correct statement says to use optimization advice to identify improvement opportunities, then validate through testing that each accepted change preserves the program's original behaviour. Optimization suggestions are useful because they point at real opportunities, but they only belong in production once testing confirms the underlying behaviour is unchanged.
Applying every suggestion the analysis tool produces is incorrect because blanket application skips the check that catches suggestions unsuitable for the specific code or data involved.
Using the advice to remove unfamiliar code is incorrect because unfamiliarity is not a basis for deletion, and doing so risks removing logic the advice never intended to touch.
Treating runtime improvements as correct without checking output is incorrect because a faster routine that computes something different is a regression dressed up as an improvement.
For the exam, pair every optimization with validation before it is considered accepted.