Smoke testing is the best fit because it is a quick, high-level validation that a new build's most critical functions work and the build is stable enough to proceed to deeper testing. The scenario specifically says
"ready for the next testing phase," which is exactly the gate smoke testing supports: confirm the build is not
"broken" and that core paths execute without major failures. CompTIA Project+ includes smoke testing as one of the testing cycles/methods candidates should recognize in project quality activities. () The other options are not the best match. Unit testing is low-level testing of individual components (often done by developers) and doesn't validate that the integrated build's critical workflows function end-to-end.
Regression testing is broader and verifies existing features weren't broken by changes; it typically takes more time and is usually run after the build passes smoke checks. Performance testing evaluates responsiveness, throughput, and resource usage-important, but not the initial readiness check for a new build entering the next test stage.
So, to quickly confirm essential functionality and determine readiness to proceed, the PM should ensure a smoke test is performed.