A 311 application's broadcast domain is the entire VLAN spanning two civic buildings, so a noisy VM affects both. Which traditional issue is that?
Select an answer to reveal the explanation.
Short Explanation
A giant stretched VLAN is one huge party line across two buildings. One chatty VM wakes everyone. Virtual networks can keep the 311 neighborhood small and logical instead of one citywide broadcast domain.
Full Explanation
Large Layer-2 failure domains appear when a 311 application's broadcast domain is an entire VLAN spanning two civic buildings, so a noisy VM affects both. Virtual networks can keep broadcast domains small and logical instead of stretching a huge VLAN. Stretching a VLAN does not shrink the broadcast domain. Horizon session timeouts do not isolate Ethernet broadcasts. A noisy VM can affect peers on the same VLAN, not only the hardware firewall. Exam caveat: overlays help, but operators must still avoid unnecessarily large segments and should monitor broadcast/multicast behavior. Operational check: redesign 311 tiers onto smaller overlay segments scoped per building or tier and verify broadcast scope with controlled traffic tests. 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. Prefer verifying with a non-production agency workload before promoting the same pattern to life-safety systems.