Before any tuning work starts on a transformed application, the team wants to know which review best prepares them to optimise it safely. What should the review cover?
Select an answer to reveal the explanation.
Short Explanation
You need a review that points to real execution hotspots, the data access patterns behind them, and duplicated logic. That's what tells you where tuning can safely improve performance. Cosmetic checks won't get you there.
Full Explanation
Hotspots identified from real execution, the data access patterns those hotspots depend on, and duplicated logic across the codebase prepare the team to optimise safely. These areas are where changing behaviour can actually move performance; everything else is a code-quality or cosmetic concern that does not identify where to optimise. The style guide check confirming consistent indentation across the codebase is incorrect because indentation consistency has no effect on runtime performance. The count of how many classes were generated during transformation is incorrect because class count from transformation is a structural artefact, not a performance indicator. The comparison of variable naming conventions between the legacy and transformed code is incorrect because naming convention differences do not affect execution speed or resource use. For the exam, keep the optimisation review focused on hotspots, data access, and duplicated logic.