Physical change control forbids Friday VLAN adds, which blocked a weekend 311-portal launch. How does software-defined networking address that change-window coupling?
Select an answer to reveal the explanation.
Short Explanation
Friday VLAN freeze is like closing the paint shop the night before opening day. An overlay network is a new floor plan on the same streets, so 311 can launch without a physical VLAN ticket. Reloading the core or borrowing the GIS VLAN is still the old parade.
Full Explanation
Software-defined networking provisions the 311 overlay network on the existing underlay without a Friday physical VLAN change, decoupling civic launches from rigid physical change windows. When physical change control forbids Friday VLAN adds, the weekend portal can still land on overlay objects if transport capacity already exists. Filing an emergency core-switch reload to force a VLAN after freeze is the anti-pattern. Hosting the portal only on Carbon Black-isolated endpoints until Monday does not create the network. Stretching the GIS VLAN across festival cameras avoids a new object by enlarging risk. Exam caveat: production overlays still need authorized change records; the point is removing physical VLAN freeze coupling, not skipping governance. Operational check: create a non-prod 311 segment on Friday without a VLAN add and validate app connectivity on the existing underlay. Keep municipal naming and change tickets aligned with the software objects so civic audits can trace intent. Prefer verifying with a non-production agency workload before promoting the same pattern to life-safety systems. Record realization state and underlay health in the runbook used by on-call city operators.