Helpdesk confuses ZTP with an engineer pushing configuration via NETCONF from a laptop. What is the key distinction?
Select an answer to reveal the explanation.
Short Explanation
ZTP is the self-service kiosk at first boot; NETCONF from a laptop is an engineer walking up with a remote control. Helpdesk should separate automated day-0 bring-up from ad-hoc remote config sessions. Both can load config, but they are not the same workflow.
Full Explanation
ZTP is automated first-boot provisioning via DHCP and file services, while NETCONF from a laptop is engineer-driven remote configuration after reachability and credentials exist. Helpdesk must keep those moments distinct. Treating them as identical because both always need pre-existing production config is wrong: ZTP targets blank first boot. Calling laptop NETCONF the only supported first-boot image method ignores network-assisted ZTP. Saying ZTP permanently replaces SSH/NETCONF confuses day-0 automation with essential day-2 management channels. Exam caveat: After ZTP, CLI/NETCONF/automation remain valid change methods; ZTP does not obsolete them. Operational check: Publish separate runbooks for factory-default ZTP versus engineer NETCONF/CLI and train staff to choose by device state. 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.