A township wants DHCP only during rack-and-stack, then static management addressing in steady state. How should that policy be understood relative to DHCP’s DC role?
Select an answer to reveal the explanation.
Short Explanation
Use DHCP like temporary scaffolding while the rack goes up, then bolt on permanent static management addresses if policy says so. Township day-0 ZTP can still lean on DHCP even if steady state goes static. Those phases are complementary, not mutually exclusive forever.
Full Explanation
DHCP can provide day-0 provisioning addressing while township steady-state management later uses static addresses per policy; those phases are complementary for civic fabrics. Using DHCP at bring-up does not permanently forbid later static management addressing. Choosing static steady-state addresses does not mean ZTP/DHCP concepts never apply at any phase. Infinite leases are not a historical requirement proving a past ZTP event was valid. Exam caveat: Convert to static only after documentation and reachability checks so you do not strand mid-provisioning devices. Operational check: After ZTP completes, apply the static management plan, update IPAM, and confirm file-server/automation reachability still works. 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.