An administrator pushed a firewall rule change to allow a new vendor IP range during business hours. Minutes later, payroll users lost access to an internal service. Which change management practice would have best reduced the impact?

Apply changes directly in production so they take effect as quickly as possible.

Fast deployment without testing increases the chance that a bad rule will disrupt business services.

Avoid documenting the change until after the maintenance window ends.

Delayed documentation makes troubleshooting harder and removes accountability when a change causes an outage.

Use verbal approval from the payroll manager instead of the normal ticket process.

Verbal approval does not replace testing, traceability, or a documented rollback strategy for risky changes.

What does this SY0-701 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Test the change in a staging environment and include a rollback plan in the request. — This is the best practice because staging validation can reveal unintended access impacts before production is touched. A rollback plan gives operators a fast, documented way to restore service if the change breaks something critical. Together, testing and rollback planning reduce outage duration and support safer operational hardening by making the change controlled, reviewable, and reversible. Why others are wrong: A favors speed over control and is exactly how accidental outages happen. C hurts traceability and makes incident reconstruction more difficult. D is not sufficient because approval alone does not prevent a misconfigured rule from affecting unrelated internal services.

What should I do if I get this SY0-701 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.