Refer to the exhibit.
An administrator has opened the Enable Multi-Cluster configuration for an NDB instance, but the wizard does not present the VLAN, as shown in the exhibit.
Which configuration allows to choose a VLAN in the drop-down box?
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.
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) v6.5 Blueprint, Section 3: Configure an NDB Environment
Why would an administrator want to publish a software profile update for Microsoft SQL Server that is created in NDB?
In NDB, publishing a software profile update for Microsoft SQL Server makes it available for broader use within the NDB environment. When an administrator creates and publishes an updated software profile (e.g., with a new SQL Server patch or version), this action allows all authorized NDB users to leverage that profile to patch or update the database software on their managed VMs. This is a key feature of NDB's software profile management, enabling centralized control and distribution of standardized database configurations.
Option A is correct because publishing a profile democratizes access, allowing all users to apply the update to their database VMs, aligning with NDB's collaborative administration model.
Option B is incorrect because it suggests the profile patches itself, which is not the intent; publishing enables usage, not self-application.
Option C is incorrect because publishing does not automatically deprecate older profiles; deprecation is a separate administrative decision.
Option D is incorrect because publishing facilitates patching, not stalls it.
This process enhances efficiency and consistency in managing SQL Server updates across an organization.
Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Creating and Publishing Software Profiles
Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Software Profiles
When performing a SQL Server Restore Source Database operation, what is a valid reason an administrator would choose the Restore
Location as New Location?
When an Oracle database is upgraded using Era, what is the type of upgrade category?
An Era-managed production MSSQL database crashed during a busy holiday weekend and the administrator has to restore the database to
the most recent timestamp with an objective to reduce the restore time and minimize data loss.
What option should the administrator do to achieve this objective?
Cornell
7 days agoHyman
1 months agoChau
2 months agoAlverta
2 months agoEleonore
2 months agoKimbery
2 months agoLauran
3 months agoGeorgeanna
3 months agoNieves
3 months agoDona
4 months agoMignon
4 months agoGerald
4 months agoRegenia
4 months agoTommy
4 months agoFatima
5 months agoAmina
5 months agoCaitlin
5 months agoAfton
5 months agoNettie
5 months agoSanda
6 months agoKimi
6 months agoWillis
6 months agoWhitney
6 months agoTran
6 months agoGerman
7 months agoStefanie
7 months agoYesenia
7 months agoTanesha
7 months agoTimothy
7 months agoFredric
8 months agoSabra
8 months agoNadine
8 months agoSimona
10 months agoGlennis
10 months agoVal
10 months agoValentin
10 months agoNikita
11 months agoGeraldine
11 months agoValentine
12 months agoRueben
12 months ago