mediummultiple choiceObjective-mapped

A firewall rule change was implemented directly in production to allow a new vendor IP range. Within minutes, several internal services became unreachable because the rule order changed unexpectedly. Which change-management practice would have most likely prevented this outage?

Question 1mediummultiple choice
Full question →

A firewall rule change was implemented directly in production to allow a new vendor IP range. Within minutes, several internal services became unreachable because the rule order changed unexpectedly. Which change-management practice would have most likely prevented this outage?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Testing the change in a staging environment and approving it through a peer-reviewed change process before production.

A tested, peer-reviewed change process helps catch rule-order problems, dependency issues, and unintended access impacts before production is affected. Firewall changes can alter traffic flow in subtle ways, so validating them in a nonproduction environment and having a formal approval path reduces the chance of service disruption. A backout plan also gives the team a quick recovery path if the production change behaves differently than expected.

B

Distractor review

Applying the rule during business hours so the team can respond faster if something breaks.

Business hours may improve response time, but they do not prevent configuration mistakes or hidden traffic-impact issues.

C

Distractor review

Making the change first in production because that is the only environment that matters.

Production-only testing increases risk and can interrupt critical services when rule interactions are not fully understood.

D

Distractor review

Documenting the outage after the vendor confirms their IP range is valid.

Post-incident documentation does not prevent outages and does not replace pre-change validation or approval.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Related practice questions

Related SY0-701 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

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: Testing the change in a staging environment and approving it through a peer-reviewed change process before production. — The best preventative control is a formal change process with testing and review before production deployment. Firewall rules can affect routing, access control, and rule precedence, so a small change may have broad side effects. Staging validation and peer review help identify unintended service impact early. Having an approved backout plan also means the team can quickly revert if the production behavior differs from the tested behavior. Why others are wrong: Scheduling the change during business hours can help with troubleshooting, but it does not reduce the likelihood of mistakes. Changing production first is the opposite of good change control and can create outages. Documenting the problem after the vendor confirms the IP range is valid is reactive and does not address the configuration risk that caused the outage.

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.

Discussion

Loading comments…

Sign in to join the discussion.