According to the Nutanix Database Automation (NCP-DB) learning documents, to provision a new network in Clusters and extend it to Era, you need to:
B; Add the new subnet and VLAN in Network Configuration in PE1. C. Add the new VLAN in Era Networks1.
These steps ensure that the new network is properly configured in both the Nutanix environment and Era, allowing for seamless communication and operation. Please refer to the official Nutanix documentation and training materials for more detailed information1.

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.
References
* 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

NDB coordinates Oracle-native recovery mechanisms when restoring a selected PDB to a specified point in time. Time Machine supplies the required snapshot and transaction-log recovery points, while Oracle Recovery Manager restores the necessary PDB datafiles and applies archived redo through the requested timestamp. Oracle redo is maintained at the container database level, so the process does not literally use a completely independent redo stream for each PDB. Nevertheless, Oracle's recovery operation limits the recovery scope to the selected PDB and processes all required archived-log switches automatically. NDB does not reconstruct Oracle transactions using Prism Central's Cassandra data, apply flat-text backup files, or require the administrator to append database blocks manually. Nutanix documents the ability to restore selected PDBs by snapshot or timestamp in its official Oracle PDB and CDB management guidance.

A Log Catchup gap in Nutanix Database Service (NDB) occurs when transaction logs are missing or corrupted, disrupting point-in-time restore (PITR) operations for cloning or database restoration via Time Machine. The NDB Time Machine Heal Snapshot feature addresses this by repairing snapshots to resolve such gaps.
Option A (By default the time machine auto-heal feature is enabled) is incorrect because the auto-heal feature is not enabled by default; it requires explicit configuration or manual invocation.
Option B (Manual Heal is only used when gaps in Log Catchup are detected once the operation has begun failing) is incorrect because manual heal can be initiated proactively or reactively, not solely after failure detection.
Option C is correct because a successful Time Machine Heal process restores the snapshot integrity, allowing PITR to span the previously gapped period.
Option D is correct as the auto-heal process, when enabled, runs every 5 minutes to detect and address healable conditions, aligning with NDB's automated maintenance schedule.
Together, C and D reflect the operational mechanics of the Heal Snapshot feature.
References
Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Healing Snapshot Gaps Nutanix Support & Insights, Knowledge Base Article: "Resolving Log Catchup Gaps with Time Machine Heal" Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 5: Protect Databases Using Time Machine

MySQL HA uses MySQL Router as the application-facing routing layer. When NDB provisions an HA instance, the Create MySQL Router option can be enabled so clients connect through router VMs instead of targeting individual database nodes. The router uses cluster topology information to direct traffic to the appropriate active member and maintain connectivity when failover changes the primary. HAProxy is the component NDB commonly uses for PostgreSQL HA and for the NDB control plane; it is not the native routing choice for a MySQL InnoDB HA deployment. An external load balancer can be used in a custom design, but it is not the requested NDB-managed option. A multi-host connection string shifts failover handling to the application rather than enabling automated routing in NDB. Nutanix exposes this setting in the MySQL HA provisioning workflow.