A school technician has confirmed that a firewall rule is dropping the lab. The technician is not allowed to edit the firewall. Which methodology step fits?
Select an answer to reveal the explanation.
Short Explanation
You found the locked door, and you do not have the key. The next step is to hand the confirmed fix to the people who are allowed to open it. Picking the lock, closing the ticket while the lab is still dropped, or replacing PCs that were never the cause all skip the handoff you are supposed to make.
Full Explanation
Escalation is the step you take when the required change is outside your authority or your skill. The school technician has a confirmed cause and is not allowed to edit the firewall, so the methodology step is to escalate that change to the firewall team, with the evidence attached. Editing the firewall anyway violates the access rule and can take down more than the lab. Closing the ticket leaves the drop in place. Knowing the cause is not the same as restoring service. Replacing the lab PCs does not change the rule that is dropping their traffic. Exam caveat: escalation still includes your notes on what you tested and what you need changed. You do not toss the ticket over the wall with no evidence. Operational check: open the request to the firewall team, include the rule and the test that proved it, and verify the lab after they make the change. Include the test that proved the rule, so the firewall team is not guessing. Stay on the ticket until the firewall team confirms the rule and the lab user retries successfully.