Prism Central registration is the prerequisite that makes Nutanix Objects discoverable and manageable by NDB. Nutanix states that one or more Prism Central domains must be registered with NDB before an Object Store can be provisioned or registered. Once that relationship exists, the administrator can select the appropriate Prism Central and Object Store from the NDB workflow and then configure the store for database log backups. Registering an S3-compatible store is a later object-store onboarding step, not the initial prerequisite. An NC2 deployment is optional, and directly registering only the Prism Element instance hosting Objects does not satisfy the documented integration sequence. Therefore, option C is correct. The candidate file's supplied answer D conflicts with the official prerequisite and has been corrected. Nutanix Prism Central registration documentation

This is because it allows the database to be refreshed at the exact time specified (9:30 PM) with the most recent data. The other options either perform the snapshot before the desired time or do not specify when the snapshot would occur. Please note that the exact answer might depend on the specific database system and its capabilities. Always refer to the database's documentation for the most accurate information.

In the context of Nutanix Database Automation (NCP-DB), when provisioning a new Oracle SIHA DB & VM, if only ASMFD is available in the ASM Driver drop-down, it indicates that ASMLIB is not included in the current software profile. To provision the requested SIHA DB and DB VM with ASMLIB, it's essential to update the software profile to include the ASMLIB driver. This action will enable ASMLIB as an option in the ASM Driver drop-down during the provisioning workflow.
References:
* Nutanix Database Automation (NCP-DB) Course Details, Section 2.3: Provisioning Oracle Databases
* Nutanix Database Automation (NCP-DB) Certification Details, Objective 2.3: Provision Oracle Databases
* Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 2.3: Provisioning Oracle Databases
* [Nutanix Database Automation (NCP-DB) User Guide], Section 2.3: Provision Oracle Databases

Configuring VM Host Affinity in a Nutanix AHV-powered cluster ensures that VMs are placed on specific hosts to optimize performance or HA. However, after a host failure, if database VMs cluster on a single remaining host, it indicates that the affinity rules alone are insufficient to maintain high availability (HA) during failover scenarios. To prevent this, the administrator should configure anti-affinity rules, which dynamically ensure that VMs (e.g., database server VMs) are spread across multiple hosts. Anti-affinity rules override default VM placement behavior during failover, reducing the risk of a single point of failure by keeping VMs separated even after a host outage.
* Option A (Assign additional backup VMs on the same host) is incorrect because placing backups on the same host increases risk rather than mitigating it.
* Option B (Increase affinity zones) is incorrect as "affinity zones" is not a standard Nutanix term in this context, and it does not address dynamic VM separation.
* Option C (Configure automatic host failover in Prism Central) is incorrect because while failover is managed by AHV, it does not inherently prevent VMs from clustering without specific rules.
* Option D is correct as anti-affinity rules proactively distribute VMs, enhancing HA in failure scenarios.
This approach leverages Nutanix AHV's VM placement policies to ensure resilience.
References
* Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section:
Configuring VM Affinity and Anti-Affinity
* Nutanix AHV Administration Guide, Section: VM High Availability and Placement Rules
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 3: Configure an NDB Environment

In Nutanix Database Automation (NCP-DB), the Database Parameters profile is used to manage database-specific settings, including the maximum number of database connections. This profile would be the appropriate choice when an administrator needs to change these settings during the cloning workflow1.