A parks department management VLAN for DHCP is mis-scoped, and new leafs land on the wrong network. What should the deployment design emphasize?
Select an answer to reveal the explanation.
Short Explanation
Wrong VLAN scope is like handing park rangers keys to the public lobby instead of the ops closet. Leafs must DHCP on the intended management network, not a guest or random segment. Get scope-to-VLAN mapping right before blaming Junos.
Full Explanation
Correct DHCP scope and VLAN association ensure parks-department provisioning clients receive leases on the intended management network so ZTP file reachability and fabric onboarding match the design. Sharing one DHCP scope between guest Wi-Fi and fabric management invites wrong leases and weakens civic management isolation. Removing VLANs so DHCP floods every building port destroys segmentation and expands the provisioning blast radius. Binding ZTP exclusively to production server subnets puts day-0 switch bring-up on the wrong network class. Exam caveat: Scope-to-VLAN or VRF mapping errors often present as 'Junos ZTP broken' when the leaf simply leased on the wrong segment. Operational check: Confirm the leaf's management interface VLAN, the DHCP scope serving that VLAN, and that options still point to the municipal file server. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure.