City standards require DHCP logs retained for device identity audits during ZTP. What operational value does that logging provide?
Select an answer to reveal the explanation.
Short Explanation
DHCP logs are the city clerk’s receipt book for who got which address and boot pointers during ZTP. Audits use them to prove bring-up accountability—not to replace config backups or auto-fix bad role files. Keep the logs; they tell the deployment story.
Full Explanation
Retained DHCP logs support deployment accountability by recording which municipal devices received which addressing and option sets during ZTP bring-up. Logs do not replace configuration backups on the switches. Logs do not prove VXLAN VNI assignments without fabric state checks. Logs do not automatically remediate wrong role configs without operator review. Exam caveat: Retention supports audits; it does not substitute for artifact hygiene or post-ZTP validation. Operational check: During a sample ZTP, pull lease/option history for the leaf serial/MAC and attach it to the change ticket. 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.