Nutanix Database Automation (NCP-DB) introduces the concept of MS SQL Server database groups, which allows multiple databases running in the same database instance to be grouped as one Time Machine entity1. This applies to both single DB Server VM setups, standalone databases, as well as to Availability Group databases1. However, it does not support Point In Time Recovery (PITR)-based Service Level Agreements (SLAs) for database groups containing mixed Recovery Models. This means that if the databases within the group have different recovery models, PITR-based SLAs cannot be applied to the group as a whole.

The correct answer is D because it matches the requirement of taking multiple snapshots per day and retaining them for one week. Option A is incorrect because it only takes one snapshot per day, which is not enough for the administrator's need. Option B is incorrect because it only retains the snapshots for one week, which means the older snapshots will be deleted after seven days. Option C is incorrect because it only takes two snapshots per week, which is not frequent enough for the administrator's need.
References: The following sources provide more information about the SLA retention policies and how to create and modify them in NDB:
* Nutanix Database Management & Automation (NDMA) course, Module 4: Protecting Databases Using Time Machine, Lesson 4.1: Creating and Modifying SLA Retention Policies
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section
5 - Protect NDB-managed Databases Using Time Machine
* Nutanix Database Service (NDB) User Guide, Chapter 6: Protecting Databases Using Time Machine, Section 6.1: Creating and Modifying SLA Retention Policies

The correct answer is B because setting VM-Host affinity ensures that the DB Server VMs are not migrated to another host during the LCM upgrade process. This way, the DB Server VMs can continue to serve the database requests without interruption. Option A is incorrect because updating the Nutanix cluster does not prevent the DB Server VMs from being moved to another host. Option C is incorrect because removing the Nutanix cluster from NDB will make the DB Server VMs unmanaged by NDB and lose the benefits of NDB features. Option D is incorrect because unsetting VM-Host affinity will allow the DB Server VMs to be migrated to another host during the LCM upgrade process, which may cause downtime or performance degradation.
The following sources provide more information about the LCM upgrades and VM-Host affinity in NDB:
Nutanix Database Management & Automation (NDMA) course, Module 6: Administering an NDB Environment, Lesson 6.3: Performing NDB Software Upgrades Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 6 - Administer an NDB Environment Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.3:
Performing NDB Software Upgrades
Nutanix Support & Insights, Your guide to the Upgrades, LCM Design
Nutanix Life Cycle Manager Guide, Chapter 3: Upgrading Software and Firmware, Section 3.2: Preparing for an Upgrade, VM-Host Affinity

Patroni continuously monitors PostgreSQL HA members and can promote a standby when it determines that the leader has failed. During an in-place point-in-time restore, NDB intentionally stops normal cluster automation: it pauses Patroni monitoring and places the cluster in maintenance mode while the database state is rewound. This prevents Patroni from interpreting controlled shutdowns or role changes as failures and initiating an unwanted promotion. After recovery and cluster validation, normal Patroni management can resume. Nutanix documents Patroni as the component responsible for monitoring PostgreSQL instances and performing automated failover, which explains why its automation must be suspended during this coordinated recovery operation. NDB neither promotes every node nor deletes and rebuilds the Patroni configuration.
Therefore, option C is correct. Nutanix Patroni overview

NDB Time Machine protects Microsoft SQL Server databases through application-consistent snapshots and a continuous sequence of transaction-log backups captured by Log Catch-up operations. When the latest protected time is selected, NDB uses the appropriate snapshot as the baseline and applies the required transaction logs through the most recent available recovery point. This produces a transactionally consistent clone rather than a crash-consistent VM copy. NDB does not need to leave the source database in read-only mode, and Volume Shadow Copy Service alone cannot provide the transaction-log replay required for granular point-in-time cloning. "Latest Time" means the latest point covered by the valid Time Machine snapshot and log chain, not an unprotected wall-clock instant after the last log capture. Nutanix's Database Log Backup Management documentation explains that Log Catch-up captures database transaction logs for point-in-time cloning.