The provided exhibit shows the "Enable Multi-Cluster" configuration wizard in NDB, where the VLAN dropdown is empty with a "Nothing found" message, indicating that no VLANs are available for selection. This issue arises because NDB requires a network profile to be created before provisioning the NDB Agent VM and enabling multi-cluster support. A network profile defines the static VLANs managed by NDB, which are essential for network configuration during multi-cluster setup. The warning in the exhibit ("An NDB managed static vLAN is required to provision the NDB Agent VM. Add an NDB managed static vLAN using the Networks page to continue.") reinforces that the administrator must create a network profile via the Networks page to populate the VLAN dropdown.
Option A (A network profile must be created first) is correct as it addresses the root cause by ensuring VLANs are defined in a network profile.
Option B (Verify if subnet leverages advanced network control) is incorrect because advanced network control is not a prerequisite for VLAN selection in this context.
Option C (IP address pool must be managed in NDB) is incorrect because IP address pools are managed separately and not required for VLAN selection at this stage.
Option D (VLAN subnet must use IP address management) is incorrect because IP address management is not a direct requirement for enabling VLAN selection in the wizard.
After creating the network profile, the administrator can proceed with the multi-cluster enablement.
References
Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: Configuring Network Profiles for Multi-Cluster
Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting VLAN Issues in NDB Multi-Cluster Setup"
Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 3: Configure an NDB Environment
