After the courts NSX Manager cluster forms, the install checklist still has no NSX backup configured. What should the security administrator include as part of standing up NSX-T?
Select an answer to reveal the explanation.
Short Explanation
A brand-new Manager cluster without a backup is a courthouse with no spare keys. SFTP backup is part of standing NSX-T up, not a later GRC essay. Carbon Black alerts and Edge-only snapshots will not restore Manager config.
Full Explanation
After the courts NSX Manager cluster forms, standing up NSX-T is incomplete without SFTP backup of NSX Manager configuration. Include Manager backup in the post-cluster install workflow so Distributed Firewall and security objects can be restored after control-plane disaster, independent of workload snapshots.
A records-retention policy statement without product backup does not protect Manager configuration. Carbon Black Cloud alert export is not an NSX Manager configuration backup. Snapshotting only Edge nodes while treating Managers as stateless ignores that security policy and inventory live in the Manager cluster.
Exam caveat: Manager configuration backup is part of install hygiene, not a later “nice to have.”
Operational check: configure SFTP backup targets and schedule, run a test backup, confirm backup files land, document restore steps in the courts cyber-recovery plan, and verify backups after the next policy change.
SFTP Manager backups are the courts’ insurance binder for security policy. Schedule backups, encrypt credentials per standard, perform a quarterly restore test into an isolated lab Manager, and prove a sample DFW section returns—Edge snapshots alone will not resurrect Manager inventory after ransomware or disk loss.