A retail chain allows production switch updates only during an approved maintenance window. A critical patch is ready at noon, outside that window. What should the engineer do?
Select an answer to reveal the explanation.
Short Explanation
The patch is the medicine and the window is the appointment, so you do not dose every store at noon just because the bottle arrived early. You wait for the approved window unless an emergency change says otherwise. Editing a template that never reaches production, or calling the ISP, does not patch the switches.
Full Explanation
Change control limits production updates to an approved window so stores are not surprised by a midday outage. The patch is ready at noon and the window is elsewhere, so the engineer waits, unless the company's emergency process explicitly authorizes an out-of-window change. Installing at noon because the file is ready ignores the control the chain put in place. Updating only the golden template leaves the production switches unpatched, which does not remediate the vulnerability on the live devices. A service-level claim is a conversation with a provider about a missed commitment. The ISP does not apply the retailer's switch patch because of that claim. Exam caveat: an actively exploited vulnerability can justify an emergency change, and that path is still a change, with an approver, not a silent edit. Operational check: record the patch in the change for the next window, name the rollback, and confirm the production switches report the new version after the window. After the window, confirm each production switch reports the patched version.