During a pilot, an administrator notices that recent optimization changes were applied without first recording how the application performed beforehand. What does this omission make difficult?

Skipping baseline measurement removes the reference point needed to say whether an optimization improved performance; a post-change number on its own proves nothing. The answer about confirming that the optimization actually improved anything is correct because there is no baseline to compare the new measurements against. The answer about compiling the application is incorrect because compiling does not depend on performance baselines at all. The answer about running the regression test suite is incorrect because baselines and regression tests are separate concerns; a missing baseline does not stop tests from running. The answer about deploying to production is incorrect because deployment tooling does not gate on baseline measurement; the gap is a process weakness, not a tooling block. For the exam, always capture a baseline before optimizing, so the improvement can be demonstrated rather than assumed.