A team applies an optimization suggestion and notices the transformed routine now runs noticeably faster. What does that improvement, by itself, confirm?
Select an answer to reveal the explanation.
Short Explanation
You only know the routine got faster. You still have to prove it behaves the same, because speed and correctness are separate checks.
Full Explanation
The correct conclusion is only that the change improved performance. A measured speed-up says the transformed routine runs faster; it says nothing on its own about whether the outputs the routine produces are still the ones the business depends on, so behaviour must be validated separately.
The claim that the change is correct because a genuine performance gain would not be possible if behaviour had changed is incorrect, because performance and correctness are independent properties, and it is entirely possible to make broken code faster.
The claim that no further review of the change is needed before it can be merged is incorrect, because a performance result is not a substitute for validating behaviour.
The claim that the same change can safely be applied everywhere else in the codebase without additional review is incorrect, because even a validated change in one location does not guarantee the same change is safe in a different context with different data or callers.
For the exam, keep performance and correctness as two separate questions with two separate answers.