A township wants ZTP only for initial image and configuration, then permanent local management afterward. How should that goal be framed relative to ZTP’s role?
Select an answer to reveal the explanation.
Short Explanation
ZTP is the moving truck that gets furniture into the building—not the facilities team that rearranges desks every week. The township can use it for day-0 image and config, then run steady-state management locally or with other tools. That is a normal split between first-boot automation and day-2 ops.
Full Explanation
ZTP addresses initial provisioning: software and configuration delivery so devices join the fabric without manual staging. Continuous day-2 orchestration, monitoring, and change control are separate concerns and may use local management, automation platforms, or telemetry stacks. Treating ZTP as a permanent controller for every future change overstates its deployment role. Role limits (spine-only) are not how ZTP is defined for DC leaf/spine bring-up.