Library edge boxes need a security patch, but Friday catalog-vision inference must stay up. How should BCM patching be planned?
Select an answer to reveal the explanation.
Short Explanation
You can protect Friday’s busiest catalog-vision service and still close the security gap by planning the BCM patch for an approved municipal service window. Availability matters, but skipping patches forever or yanking power cords at random is not safe maintenance.
Full Explanation
Library edge boxes that need a security patch while Friday catalog-vision inference must stay up require BCM patch application inside an approved municipal service window that avoids disrupting Friday inference. Change planning is part of installation-and-deployment professionalism: protect availability for citizen-facing vision services while still closing vulnerabilities. Applying the BCM patch to all library edge boxes at noon Friday, when inference is busiest, risks the greatest user-visible outage at the time branches are busiest. Skipping security patches indefinitely leaves edge boxes permanently exposed and may eventually force an emergency outage under active exploit. Yanking power cords in random branch order is destructive and unordered, and can corrupt state. Exam caveat: an approved service window may be overnight or staggered by branch, so document the plan; do not treat any downtime as a reason to skip patching. Practical check: select a low-traffic window, drain or shift catalog-vision inference off a pilot set of library boxes, apply BCM patches, validate that inference returns healthy, then proceed branch by branch with rollback criteria if health regresses.