The correct answer is D because it meets the requirements of maintaining five days of time-travel capability to any second and an additional seven days of discrete recovery at a daily interval. Continuous log retention allows the administrator to restore the database to any point in time within the specified number of days, while snapshot retention allows the administrator to restore the database to a specific point in time at a fixed interval. Therefore, by setting the daily snapshot retention to 7 days, the administrator can ensure that there is a discrete recovery point for each day of the week. By setting the continuous log retention to 5 days, the administrator can ensure that there is a time-travel capability to any second within the last five days. The other options do not meet the requirements because they either have less than five days of continuous log retention or less than seven days of snapshot retention. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, Nutanix Certified Professional - Database Automation (NCP-DB) datasheet

A stretched VLAN is a virtual network that spans across multiple Nutanix clusters and allows the communication between VMs on different clusters using the same subnet. A stretched VLAN can be used to provide high availability and load balancing for NDB components, such as HAProxy VMs, that require a virtual IP address (VIP) to beaccessible from any cluster. To add a stretched VLAN across two clusters in NDB, the administrator needs to meet two prerequisites: the VLAN must be static and both clusters must be registered in NDB. A static VLAN is a VLAN that is manually created and configured by the administrator, as opposed to an IPAM VLAN that is automatically created and managed by NDB. A static VLAN can be added to a stretched VLAN in NDB, while an IPAM VLAN cannot. Both clusters must be registered in NDB before adding a stretched VLAN, as NDB needs to have the information and access to the clusters and their networks.
The administrator can register the clusters in NDB using the Prism Element details, agent network configuration, and storage container information. The other option, Nutanix Cluster Management, is not a prerequisite for adding a stretched VLAN in NDB. Nutanix Cluster Management is a feature that allows the administrator to manage multiple Nutanix clusters from a single NDB UI, such as creating or deleting clusters, adding or removing nodes, or performing cluster operations. Nutanix Cluster Management is not required for adding a stretched VLAN, as the VLANs are created and configured in Prism Element, not in NDB. References:
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 2 - Deploy and Configure an NDB Solution, Objective 2.3: Configure NDB High Availability
* Nutanix Database Management & Automation (NDMA) Course, Module 3: Nutanix Database Service (NDB) Installation and Configuration, Lesson 3.3: Configuring NDB High Availability, Topic: NDB HA Architecture and Components
* Nutanix Database Service High Availability Deployment Overview, Section: HAProxy VMs and Stretched VLANs
* [Configuring a Virtual NIC to Operate in Access or Trunk Mode - Nutanix], Section: Creating a vNIC in Access or Trunk Mode

A Time Machine frozen status indicates that the database that was associated with the Time Machine has been de-registered from NDB, but the Time Machine itself has not been deleted. This means that the Time Machine still contains the snapshots and logs of the de-registered database, but it cannot perform any further operations on it. To resume the normal functioning of the Time Machine, the administrator can either re-register the database with NDB, or delete the Time Machine and free up the storage space.
References: Nutanix Support & Insights, section "Resolving All Alerts for a Time Machine"

When completing the NDB (Nutanix Database Service) Wizard for initial setup or configuration, certain steps are mandatory to ensure the environment is properly configured, while others are optional based on specific needs. Network Segmentation is an optional step that allows for advanced network isolation and configuration, but it is not required for basic NDB deployment. Mandatory steps include specifying the NDB Cluster Name, selecting a Storage Container, and configuring Services (e.g., database services), as these are essential for NDB to function and manage databases.
* Option A (Network Segmentation) is correct as it is an optional feature for advanced networking, not a required step in the wizard.
* Option B (NDB Cluster Name) is incorrect because assigning a cluster name is a mandatory step to identify the NDB instance.
* Option C (Storage Container) is incorrect because selecting a storage container is required for data storage and protection.
* Option D (Services) is incorrect because configuring services (e.g., database engines) is a core requirement for NDB operation.
Note: The question mentions "NDE Wizard," which is assumed to be a typo for "NDB Wizard" based on context.
References
* Nutanix Database Service (NDB) User Guide, Chapter 1: Deploying NDB, Section: Completing the NDB Wizard
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 1: Deploy NDB

The "Savings over traditional cloning" metric in the Data Usage widget on the NDB dashboard reflects the efficiency of NDB's cloning technology compared to traditional full-copy cloning methods. NDB leverages Nutanix's near-zero byte cloning capability, which creates lightweight clones by sharing base data and only storing changes (deltas). This metric specifically quantifies the disk space saved by using these efficient clones instead of duplicating entire datasets, as would occur in traditional cloning. It highlights NDB's storage optimization for database provisioning and management.
* Option A is correct as it directly ties to NDB's near-zero byte cloning technology, a core feature for space efficiency.
* Option B (Compression) is incorrect because compression is a separate storage optimization technique not specifically tied to cloning savings.
* Option C (Shadow clones) is incorrect because shadow clones are a Nutanix feature for caching, not the cloning mechanism used by NDB Time Machines.
* Option D (Deduplication) is incorrect as deduplication, while related to storage savings, is not the primary mechanism reflected in this cloning-specific metric.
This metric helps administrators quantify the benefits of NDB's cloning approach in terms of storage utilization.
References
* Nutanix Database Service (NDB) User Guide, Chapter 1: Introduction to NDB, Section: Understanding Cloning and Storage Efficiency
* Nutanix Support & Insights, Technical Note: "Interpreting NDB Dashboard Metrics"
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 1: NDB Concepts and Architecture