A school district already snapshots vCenter as part of cyber-recovery. Which additional control-plane backup keeps NSX-T firewall policy recoverable after a Manager disaster?
Select an answer to reveal the explanation.
Short Explanation
vCenter snapshots are the principal's office photos; they are not the school-safety playbook. NSX Manager holds the firewall objects, so back that control plane up on its own schedule.
Full Explanation
When a school district already snapshots vCenter as part of cyber-recovery, the additional control-plane backup that keeps NSX-T firewall policy recoverable after a Manager disaster is to schedule NSX Manager configuration backups separately from vCenter snapshots so Distributed Firewall objects can be restored. Treat NSX Manager backup as the separate school rulebook vault—vCenter photos do not store that book. Treating vCenter snapshots as sufficient because NSX-T stores all firewall objects only inside vCenter fails by concept because NSX-T security policy lives in NSX Manager, not solely inside vCenter snapshots. Exporting Carbon Black Cloud device-control policies and importing them as NSX Manager backups fails because CBC device control is not NSX Manager configuration. Skipping NSX Manager backup and publishing a Distributed Firewall any-any after failover until policy can be rebuilt fails because any-any is an unsafe stand-in for recoverable policy. Exam caveat: schedule NSX Manager configuration backups independently of vCenter snapshots for DFW recoverability. Operational check: enable scheduled NSX Manager backups to secure storage, test restore of a security section in a lab, verify DFW objects return, and document NSX backup cadence beside vCenter cyber-recovery steps.