Ops wonders whether DHCP is only for servers and not for switches in the municipal fabric. Which statement is accurate for ZTP-based DC switch deployment?
Select an answer to reveal the explanation.
Short Explanation
Switches need a first address and a pointer to their playbook just like servers do on install day. For ZTP, DHCP is a first-class dependency for leaf and spine bring-up, not a “servers only” leftover. Ops should plan DHCP for the fabric management path.
Full Explanation
DHCP is a required service dependency for ZTP-based Juniper DC switch deployment: leaves and spines need dynamic addressing and boot/file pointers during first boot on the municipal management path. Claiming DHCP is irrelevant because Junos cannot obtain addresses dynamically during bring-up is false for ZTP workflows. Limiting DHCP to hypervisors only ignores fabric device provisioning on leaf and spine management interfaces. Deferring DHCP until after EVPN is fully operational is backwards; ZTP happens before the overlay is up. Exam caveat: Include switch provisioning capacity and security controls in municipal DHCP planning, not only server scopes. Operational check: Verify a factory-default leaf receives a lease and options on the management network before overlay validation begins. 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.