Why must QA log off when deployment is in progress?
-
Impact software upgrades deployment time
-
Impact software upgrades deployment time & no longer testing current code version
-
May no longer be testing correct version of code
-
Lunch break
QA must log off during software deployments because their active testing sessions can delay the deployment process (impacting upgrade timelines) and they risk testing outdated code once the deployment completes. Option B captures both critical reasons: time impact and version correctness.
During a live deployment, application code, configuration, and possibly the database are being changed in place. If a QA tester stays logged in and continues exercising the system while this is happening, two problems compound: their activity (extra load, open transactions, held locks/sessions) can slow down or interfere with the deployment itself, and any results they observe mid-deployment are unreliable because they might be testing a half-upgraded, inconsistent mix of old and new code rather than either version cleanly. The correct option captures both of these reasons together. The other options only capture one half of the reasoning (just the deployment-impact side, or just the wrong-version side) or are irrelevant ('lunch break'), which is why the combined answer is the most complete and correct one.