County auditors ask whether adopting ZTP removes the need to plan out-of-band or management-plane reachability. What is the correct assessment?
Select an answer to reveal the explanation.
Short Explanation
ZTP is not a magic skip for management design—the leaves still need a clear path to DHCP and the file server. Auditors should hear that OOB or in-band management planning stays on the checklist. Automation needs a road to the warehouse, not a hope that configs appear from thin air.
Full Explanation
ZTP still requires L2/L3 reachability to DHCP and file services, so management-plane design remains necessary. Automation reduces console staging; it does not erase provisioning-path planning for county auditors. Claiming devices invent configs offline without management networks misrepresents network-assisted ZTP. Relying only on data-plane VXLAN tunnels skips the management path that feeds DHCP and files. Saying ZTP replaces physical cabling planning after one spine is online ignores underlay and management cabling realities. Exam caveat: OOB or in-band designs both must guarantee first-boot reachability to provisioning services. Operational check: From the leaf’s management attachment, validate VLAN, gateway, relay, and file-server routing/ACLs before sign-off. In civic data-center practice, treat the correct concept as part of a controlled management design rather than an isolated checkbox, and document the expected show-command or log evidence so the next on-call engineer can prove the fabric behavior without re-deriving the theory under pressure. In civic data-center practice, treat the correct concept as part of a controlled management design rather than an isolated checkbox, and document the expected show-command or log evidence so the next on-call engineer can prove the fabric behavior without re-deriving the theory under pressure.