A new library-branch application waited six weeks for a VLAN and ACL change window. Which traditional challenge does virtual networking shorten?
Select an answer to reveal the explanation.
Short Explanation
Six weeks for a VLAN is the city's old work-order queue. Virtual networking stands up a logical network in software while the underlay stays put. The library branch should not sit dark waiting on a core ACL weekend.
Full Explanation
Slow physical provisioning—weeks for VLAN and ACL windows—is shortened when logical networks are created in software in minutes. A library-branch application waiting six weeks illustrates the traditional challenge; NSX segments and policy can be instantiated without waiting on every physical change window. Overlay segments do not inherently require a six-week physical window. Geneve overlays are not blocked until the next spanning-tree reconvergence as a create prerequisite. Workspace ONE enrollment does not provision library VLANs in place of NSX. Exam caveat: production still needs CAB approval; the technical create path is short, governance may still schedule releases. Operational check: create a non-prod library segment during a normal workday without a chassis VLAN ticket and compare elapsed time to the historical six-week median. 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. Keep municipal naming and change tickets aligned with the software objects so civic audits can trace intent.