Question 1
An administrator has deployed a new VMware Cloud Foundation (VCF) management domain.
To be compliant with company policy, backups must be configured to occur anytime a change is made to the NSX configuration.
How can the administrator ensure that complete configuration backups are captured every time a change occurs?
- AOption A:
Configure an alarm to detect configuration changes and automatically trigger a complete configuration backup.
- BOption B:
No action is required as by default NSX will automatically perform a complete backup every time a change is
made to the configuration.
- COption C:
Configure a cron job on the NSX Manager to automatically perform an incremental backup of the NSX
configuration every hour.
- DOption D:
Create a recurring backup schedule and explicitly indicate that backups should be captured anytime the
configuration changes.
Show answer and explanation
Correct answer: D
Comprehensive and Detailed 250 to 350 words of Explanation From VMware Cloud Foundation (VCF) documents:
In VMware Cloud Foundation (VCF) , the protection of the NSX Manager configuration is paramount, as it contains the state of the entire software-defined network,
including firewall rules, logical switches, and routing topologies. To meet strict compliance requirements for real-time or change-based protection,
NSX offers specific automated backup triggers.
Within the NSX Manager UI (under System > Lifecycle > Backup & Restore), an administrator can configure the backup behavior.
While a time-based schedule (e.g., daily at 2:00 AM) is common, it does not satisfy the requirement for backups "anytime a change is made." To accomplish this,
the administrator must enable the "Backup on Configuration Change" toggle within the backup scheduling configuration.
When this feature is enabled, the NSX Manager monitors its own management database (DS) for write operations.
Once a configuration change is detected (such as adding a segment or modifying a DFW rule), the system initiates an automated backup process.
This ensures that the backup repository always contains a near-instantaneous reflection of the current network state, minimizing data loss in the event of a cluster failure.
Option B is incorrect because this feature is not enabled by default; it requires an external SFTP/FTP server to be configured first. Option C
(Cron jobs) is an unsupported manual workaround that bypasses the SDDC-native management tools. Option A is redundant as the
functionality is built directly into the NSX backup engine. Consequently, the verified method for compliance is to use the native recurring backup schedule with the
"Detect Configuration Change" option enabled .