A metro DC wants ZTP to upgrade Junos to the fabric standard before applying configuration. Which statement about ZTP scope is correct?
Select an answer to reveal the explanation.
Short Explanation
Day-0 should land the right OS build and the right config—like issuing both a uniform and a duty roster before the officer hits the street. Metro fabric standards often need ZTP to pull the Junos image, then apply config. Image provisioning is in scope, not an afterthought bolted only to EVPN.
Full Explanation
ZTP can include software image retrieval and upgrade in addition to configuration delivery so metro leaves meet the fabric Junos standard before production join. Limiting ZTP to routing-protocol passwords only understates image staging as part of day-0 civic bring-up. Requiring hardware SKU replacement before image upgrade confuses software baseline work with unnecessary chassis swaps. Waiting for full EVPN Type-2 convergence before ZTP image upgrade puts overlay readiness ahead of provisioning. Exam caveat: Large image transfers need file-server capacity and reboot-time planning inside the ZTP window. Operational check: Stage the standard Junos image, point DHCP options at it, and verify upgrade-plus-config completes before overlay checks. 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.