Several findings from a proof-of-concept review are being triaged for a governed optimisation plan. Which finding should be treated as a genuine optimisation candidate?
Select an answer to reveal the explanation.
Short Explanation
You should treat the routine that profiling shows consumes a disproportionate share of execution time under real workload data as the genuine optimisation candidate. Line count, recent edits, and one developer's readability complaint aren't performance signals.
Full Explanation
The correct finding is the routine identified by profiling as consuming a disproportionate share of execution time, confirmed against real workload data. A genuine hotspot is defined by where time is actually spent under real workload, which profiling measures directly rather than approximates from an unrelated property of the file. The longest file by line count is not necessarily slow; length and execution cost are not the same thing. The most recently modified file says nothing about runtime cost. A routine that a single developer personally finds difficult to read is a maintenance concern, not evidence of a performance problem. For the exam, base optimisation candidates on profiling data, not proxies.