Two DHCP servers answer in the municipal management network with conflicting options. What is the most likely ZTP impact?
Select an answer to reveal the explanation.
Short Explanation
Two chefs yelling different recipes into the same kitchen wreck dinner. Conflicting DHCP options send leaves to the wrong file server or with mismatched boot data, and ZTP becomes a coin flip. Municipal management needs one authoritative provisioning DHCP voice.
Full Explanation
Conflicting DHCP responders on the municipal management network can hand leaves inconsistent boot or file information, breaking reliable ZTP bring-up and making day-0 nondeterministic. Conflicting options do not make ZTP faster by letting devices pick the better image automatically. Junos will not safely invent a correct file-server URL when options conflict. VXLAN does not quarantine DHCP servers until options match. Exam caveat: Authoritative provisioning DHCP must be singular and controlled; rogue responders are an ops incident. Operational check: Identify which servers answered during a failed ZTP, compare option sets, and isolate or disable the conflicting responder. 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.