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
In Juniper data-center ZTP, DHCP does more than assign an address: vendor and boot-related options tell the device how and where to retrieve the Junos image and configuration. Documenting which options carry those file locations is therefore part of the deployment design. Options that only describe VRF names, BGP AS numbers, or Spanning Tree do not fulfill the file-location role the ZTP sequence depends on.