A metro fabric documents which DHCP options point new Junos leaves to the config and image file paths during ZTP. What should operators treat those options as providing?
Select an answer to reveal the explanation.
Short Explanation
Picture a new leaf asking DHCP for directions like a courier asking for the warehouse address and which dock holds the boot package. Those DHCP options do not invent routes or STP—they hand the switch the file-server map for image and config. Without that map, ZTP stalls even if the leaf already has an IP.
Full Explanation
DHCP options for Juniper DC ZTP provide option-driven pointers to the transfer method and the locations of the Junos image and configuration files—the map from lease to artifacts. Options are not merely a VRF name that replaces file-server reachability. Options are not merely a BGP AS number that skips underlay addressing. Options are not Spanning Tree parameters for joining L2 before IP assignment. Exam caveat: Document which options carry file locations as part of metro fabric deployment design. Operational check: Decode the Offer on a bringing-up leaf and confirm image/config URLs match the municipal file-server inventory. 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. 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.