[May-2024] Nutanix NCP-DB Exam Basic Questions With Answers [Q34-Q53]

[May-2024] Nutanix NCP-DB Exam: Basic Questions With Answers

New 2024 Realistic Free Nutanix NCP-DB Exam Dump Questions and Answer

NEW QUESTION # 34
An administrator has configured NDB HA across multiple Nutanix clusters.
Which failure scenario will require manual interaction for the recovery?

• A. One repository VM is down.
• B. NDB Server process is down.
• C. More than one API Server VM is down.
• D. More than one HA proxy VM is down.

Answer: C

Explanation:
NDB HA is a feature that provides high availability and resilience for the NDB service and its components.
NDB HA creates a cluster of API server VMs, repository VMs, and HAProxy VMs across multiple Nutanix clusters. Each component has a leader and a set of followers that are synchronized and can take over the leader role in case of a failure. NDB HA also monitors the health and status of the NDB components and performs automatic failover and recovery actions when possible. However, some failure scenarios may require manual intervention from the administrator to restore the NDB service. One such scenario is when more than one API server VM is down. The API server VMs are responsible for handling the requests from the NDB UI and CLI, as well as communicating with the repository VMs and the HAProxy VMs. If more than one API server VM is down, the NDB service may become unavailable or unstable, and the administrator will need to manually restart or redeploy the affected API server VMs. The other options do not require manual interaction for the recovery, as NDB HA can handle them automatically. If one repository VM is down, NDB HA will fail over to another repository VM that has the latest data. If more than one HAProxy VM is down, NDB HA will route the traffic to the remaining HAProxy VMs. If the NDB server process is down, NDB HA will restart the process or fail over to another API server VM. 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 Support & Insights, RA-2035: Nutanix Database Service High Availability, Section: NDB HA Failure Scenarios and Recovery Actions

NEW QUESTION # 35
An administrator created a database clone that is scheduled for removal on the last day of the month.
A request has been received to keep the clone for an additional 14 days.
After selecting the desired clone, how should the administrator satisfy this task?

• A. Select Update and modify the Removal schedule.
• B. Update the Removal schedule to the end of the month.
• C. Update the Removal schedule to the desired date.
• D. Remove the Removal schedule, then add the desired removal schedule.

Answer: A

Explanation:
The Removal schedule is a feature of Nutanix Era that allows you to specify when a database clone will be automatically deleted. You can modify the Removal schedule of an existing clone by selecting the clone from the Clones page, clicking on the Update button, and changing the Removal schedule option to the desired date.
This way, you can extend or shorten the lifespan of a clone as per your requirements. You do not need to remove the existing Removal schedule and add a new one, as this would be an unnecessary step. You also do not need to update the Removal schedule to the end of the month, as this would not meet the request of keeping the clone for an additional 14 days. References:
* Nutanix Database Management & Automation Training Course, Module 4: Protecting Databases Using Time Machine, Lesson 3: Cloning Databases, Slide 10: Clone Removal Schedule
* Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 5: Protect NDB-managed Databases Using Time Machine, Objective 5.3: Given business requirements, perform a database clone

NEW QUESTION # 36
An administrator needs to create a custom PostgreSQL HA software profile.
Which software component manages the state of the cluster and handles failover?

• A. HAProxy
• B. keepa lived
• C. etcd
• D. Patroni

Answer: D

Explanation:
NDB supports PostgreSQL HA software profiles for provisioning PostgreSQL databases with high availability. PostgreSQL HA software profiles consist of three components: etcd, HAProxy, and Patroni.
etcd is a distributed key-value store that provides a reliable way to store configuration data across a cluster of machines. etcd is used by Patroni to store and synchronize the cluster state and configuration.
HAProxy is a load balancer that distributes incoming requests to the PostgreSQL nodes. HAProxy is used to expose a single endpoint for database connections even as the roles of the individual nodes change.
Patroni is a template for PostgreSQL high availability. Patroni is responsible for managing the state of the cluster and handling failover. Patroni uses etcd as the distributed configuration store and relies on HAProxy for load balancing.
Therefore, the software component that manages the state of the cluster and handles failover is Patroni.
References:
* Nutanix Database Automation (NCP-DB) Course Details, Section 2.4: Provisioning PostgreSQL Databases
* Nutanix Database Automation (NCP-DB) Certification Details, Objective 2.4: Provision PostgreSQL Databases
* Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 2.4: Provisioning PostgreSQL Databases
* [Nutanix Database Automation (NCP-DB) User Guide], Section 2.4: Provision PostgreSQL Databases
* [PostgreSQL High Availability: Under the Hood - Nutanix.dev]

NEW QUESTION # 37
Which disk is omitted from a Software Profile?

• A. System Page File
• B. System Database
• C. User Database
• D. SQL Installation

Answer: A

Explanation:
According to the Nutanix Database Automation (NCP-DB) course, a Software Profile is a template that defines the configuration of the database engine, such as the version, edition, features, and parameters1. It also specifies the disk layout for the database installation, such as the size, type, and mount point of each disk1. However, the System Page File disk is omitted from the Software Profile, as it is automatically created by the NDB service based on the memory size of the database server VM1. The other options are included in the Software Profile, as they are essential for the database operation and performance1. References:
* 1: Nutanix Database Automation (NCP-DB) course, Module 2: Database Provisioning, Lesson 2.3:
Software Profiles, slide 5

NEW QUESTION # 38
An administrator needs to deploy a cumulative update (CU) for SQL Server.
What steps would the administrator take to prepare this deployment with NDB?

• A. Create a new Software Profile using the CU executable and publish that profile.
• B. Apply the patch to the profile VM, delete the existing Software Profile and create a new Software Profile using the profile VM as the source.
• C. Create a new Software Profile version using the CU executable and publishthatversion.
• D. Apply the patch to the profile VM, then create a new Software Profile version using the profile VM as the source.

Answer: D

Explanation:
The correct answer is C because it follows the recommended procedure for applying a CU to a SQL Server Software Profile in NDB. By applying the patch to the profile VM, the administrator ensures that the CU is compatible with the existing Software Profile settings and configuration. By creating a new Software Profile version, the administrator preserves the previous version of the Software Profile for rollback purposes and allows the new version to be tested and published. Option A is incorrect because it deletes the existing Software Profile, which may cause data loss and prevent rollback. Option B is incorrect because it does not apply the patch to the profile VM, which may result in errors or inconsistencies in the Software Profile. Option D is incorrect because it creates a new Software Profile instead of a new version, which may cause confusion and duplication.
References: The following sources provide more information about the Software Profile management and patching in NDB:
* Nutanix Database Management & Automation (NDMA) course, Module 5: Patching Databases Using NDB, Lesson 5.2: Creating and Modifying Software Profiles
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section
4 - Operate and Maintain an NDB Environment
* Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.2:
Creating and Modifying Software Profiles
* Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.3:
Testing and Publishing Database Patches

NEW QUESTION # 39
How would an administrator enter the NDB command line to change the static IP address on the NDB VM?

• A. era
• B. era-server
• C. arithmos cli
• D. cerebro_cli

Answer: D

Explanation:
To change the static IP address on the NDB VM, an administrator would need to enter the NDB command line using the cerebro_cli command. The cerebro_cli command is used to access the Cerebro service, which is responsible for managing the NDB instance and its components. The cerebro_cli command can be run from the NDB VM or from any other VM that has network connectivity to the NDB VM. The cerebro_cli command has various subcommands and options to perform different tasks, such as changing the IP address, hostname, password, or certificate of the NDB VM. To change the static IP address, the administrator would need to use the cerebro_cli network update subcommand with the appropriate parameters, such as the new IP address, netmask, gateway, and DNS servers. The cerebro_cli network update subcommand also requires the administrator to provide the current password of the NDB VM for authentication. After changing the IP address, the administrator would need to restart the NDB VM for the changes to take effect. References:
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 2 - Deploy and Configure an NDB Solution, Objective 2.2: Configure an NDB Instance
* Nutanix Database Management & Automation (NDMA) Course, Module 3: Nutanix Database Service (NDB) Installation and Configuration, Lesson 3.2: Configuring NDB, Topic: Changing the IP Address of the NDB VM
* Nutanix Database Service (NDB) Command Line Interface Guide, Chapter 2: Cerebro CLI, Section:
cerebro_cli network update

NEW QUESTION # 40
A database administrator wants to define initialization variables for different types of database engines and workloads, like OLTP and DW.
What type of profile would be used?

• A. Network
• B. Compute
• C. Software Profile Version
• D. Database Parameters

Answer: D

Explanation:
The database parameters profile is used to define the initialization variables for different types of database engines and workloads, such as OLTP and DW. The database parameters profile allows the database administrator to customize the configuration settings for each database engine, such as Oracle, SQL Server, PostgreSQL, and MySQL. The database parameters profile can also be applied to different database operations, such as provisioning, cloning, and patching. The database parameters profile helps to optimize the performance and functionality of the databases according to the specific requirements and best practices of each database engine and workload.
The software profile version is used to define the software version and edition for each database engine, such as Oracle 19c Enterprise Edition or SQL Server 2019 Standard Edition. The software profile version is required for provisioning new databases and patching existing databases. The software profile version helps to ensure the compatibility and compliance of the databases with the supported software versions and editions.
The network profile is used to define the network configuration and security settings for the database server VMs and the databases, such as the IP address, subnet mask, gateway, DNS, firewall rules, and SSL certificates. The network profile is required for registering new database server VMs and provisioning new databases. The network profile helps to ensure the connectivity and protection of the database server VMs and the databases within the network environment.
The compute profile is used to define the compute resources and storage policies for the database server VMs and the databases, such as the CPU, memory, disk size, disk type, compression, deduplication, and replication factor. The compute profile is required for provisioning new databases and cloning existing databases. The compute profile helps to ensure the availability and efficiency of the database server VMs and the databases within the Nutanix cluster.
References:
* Nutanix Database Management & Automation Training Course, Module 4: Nutanix Era Configuration, Lesson 4.1: Nutanix Era Configuration, slides 6-9.
* Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slides 5-8, 11-12, 15-16.

NEW QUESTION # 41
An administrator needs to roll back an Oracle patch on a database server VM using NDB. What is required for this action to be successful?

• A. The database must be shut down.
• B. The database must be in read-only mode.
• C. The patch must have been applied using NDB.
• D. The patch must have been applied on Grid home only using NDB.

Answer: C

Explanation:
To roll back an Oracle patch on a database server VM using NDB, the patch must have been applied using NDB in the first place. This is because NDB maintains a patch inventory and history for each database server VM and database that it manages. NDB uses this information to determine which patches can be rolled back and how to revert the changes made by the patch. If the patch was applied outside of NDB, NDB would not have the patch information and would not be able to roll back the patch. Therefore, the patch must have been applied using NDB for the rollback action to be successful. The other options are not required for the rollback action. The database does not need to be shut down or in read-only mode, as NDB can perform the rollback operation online. The patch does not need to be applied on Grid home only, as NDB can roll back patches applied on both Grid home and Database home. References:
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 4 - Operate and Maintain an NDB Environment, Objective 4.4: Determine the correct method to apply Linux OS patches
* Nutanix Database Management & Automation (NDMA) Course, Module 5: Nutanix Database Service (NDB) Patching, Lesson 5.1: Patching Overview, Topic: Patching Concepts
* [Nutanix Database Service (NDB) User Guide], Chapter 7: Patching, Section: Rolling Back a Patch

NEW QUESTION # 42
Within NDB, an administrator needs to register a PostgreSQL database server VM with a database.
Where should the database data and log files be located in order to successfully complete this task?

• A. On the same disk as the operating system
• B. On the same disk as the binary installation
• C. On the same mount point
• D. On a separate mount point

Answer: D

Explanation:
To register a PostgreSQL database server VM with a database on NDB, the database data and log files must be located on a separate mount point from the operating system and the binary installation. This is because NDB uses the mount point as the identifier for the database server VM and the database. If the data and log files are on the same mount point as the operating system or the binary installation, NDB will not be able to recognize them as a valid database server VM or database. Therefore, the administrator should create a separate mount point for the data and log files and specify it during the registration process. References: Nutanix Database Automation (NCP-DB) Course Details, Nutanix Database Automation (NCP-DB) Certification Details, Nutanix Database Automation (NCP-DB) YouTube Playlist, [How to Allow Remote Access to PostgreSQL database], [5 Ways to Host PostgreSQL Databases], [Starting the Database Server].

NEW QUESTION # 43
The NDB user interface can display which language option?

• A. German
• B. French
• C. Japanese
• D. Korean

Answer: C

Explanation:
The NDB user interface supports multiple languages, including English, Chinese, and Japanese. You can change the language preference in the NDB settings page. The NDB user interface does not support Korean, French, or German languages at this time. References:
* Nutanix Database Management & Automation Training Course, Module 1: Introduction to Nutanix Era, Lesson 1: Nutanix Era Overview, Slide 7: NDB User Interface
* Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 1: Describe NDB Concepts, Objective 1.6: Languages

NEW QUESTION # 44
An administrator is tasked with auditing NDB SLAs. What data will the administrator be reviewing?

• A. Snapshot schedules
• B. Data retention policies
• C. Recovery Time Objective
• D. Clone Management

Answer: B

NEW QUESTION # 45
A user accidentally drops a table in the database at 10:42pm and the NDB administrator is tasked with restoring the table.
The snapshot schedule is set for every 30 minutes and the log catchup is set for every 15 minutes. The last available snapshot is at 10:30pm.
What is the optimal path to restore the table back with minimum data loss?

• A. Restore the 10:42pm snapshot.
• B. Restore using point in time till 10:41pm.
• C. Restore the 10:30pm snapshot.
• D. Restore using point in time till 10:42pm.

Answer: D

Explanation:
The optimal path to restore the table back with minimum data loss is to use the point in time restore feature of NDB, which allows the administrator to restore the database to a specific point in time based on the available snapshots and logs1. By restoring using point in time till 10:42pm, the administrator can recover the table just before it was dropped by the user, and minimize the data loss to the least possible amount1. The other options are not optimal, as they either involve restoring an older snapshot, which may result in more data loss, or restoring a non-existent snapshot, which is not possible. References:
* 1: Nutanix Database Automation (NCP-DB) course, Module 6: Database Recovery, Lesson 6.2: Point in Time Restore, slide 5

NEW QUESTION # 46
An administrator needs to patch a PostgreSQL database server VM from version 13.4 to 13.8.
What is the first step within the NDB patching workflow to accomplish this task?

• A. Create a Software Profile Version with PostgreSQL 13.8.
• B. Create a maintenance window and add this PostgreSQL server 13.8 to the queue.
• C. Create a new Database Parameters profile for PostgreSQL server 13.8.
• D. Create a new Software Profile with PostgreSQL 13.8.

Answer: A

Explanation:
NDB supports patching for PostgreSQL database instances. Patching for PostgreSQL is validated on VMs provisioned by NDB (greenfield deployments). To patch PostgreSQL database server VMs, you must create a software profile version by uploading the PostgreSQL update file in NDB. You can then use the PostgreSQL update to patch other database server VMs or provision a new database server VM with the updated software profile. The first step in the NDB patching workflow is to create a software profile version with the desired PostgreSQL version.
References:
* Nutanix Database Automation (NCP-DB) Course Details, Section 4.1: NDB Patching Overview
* Nutanix Database Automation (NCP-DB) Certification Details, Objective 4.1: Perform Database Patching
* Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 4.1: NDB Patching Overview
* Nutanix Database Automation (NCP-DB) User Guide, Section 4.4: Patch PostgreSQL Database Software

NEW QUESTION # 47
How can HA drivers for a Database VM be upgraded?

• A. One-click software upgrade
• B. Database VM OS patching
• C. LCM driver upgrade
• D. Database software patching

Answer: C

Explanation:
HA drivers are software components that enable high availability features for database VMs, such as failover, fencing, and heartbeat. HA drivers can be upgraded using the Life Cycle Management (LCM) feature of Nutanix Prism. LCM can detect the available updates for HA drivers and apply them to the database VMs in a non-disruptive manner. LCM can also perform health checks and pre-upgrade validations to ensure the successful completion of the upgrade process. One-click software upgrade is a feature of Nutanix Era that allows you to upgrade the Era software itself, not the HA drivers. Database VM OS patching is a feature of Nutanix Era that allows you to patch the operating system of the database VMs, not the HA drivers. Database software patching is a feature of Nutanix Era that allows you to patch the database software of the database VMs, not the HA drivers. References:
* Nutanix Database Management & Automation Training Course, Module 2: Deploying and Configuring an NDB Solution, Lesson 3: Configuring NDB High Availability, Slide 9: HA Driver Upgrade
* Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 4: Operate and Maintain an NDB Environment, Objective 4.4: Upgrade databases

NEW QUESTION # 48
Which response shows two ways to upgrade an NDB Server?

• A. Out-of-Place Upgrade and In-place Upgrade
• B. One-click Upgrade and Offline Upgrade
• C. Upgrade and Manual Upgrade
• D. One-click Upgrade and In-place Upgrade Auto

Answer: B

Explanation:
There are two ways to upgrade an NDB Server: one-click upgrade and offline upgrade. One-click upgrade is the recommended method, as it automatically downloads and installs the latest NDB software version from the Nutanix portal. Offline upgrade is an alternative method, which requires you to manually download the NDB software bundle and upload it to the NDB Server VM. Both methods require you to have a valid Nutanix account and an internet connection. References:
* Nutanix Certified Professional - Database Automation (NCP-DB), Section 6 - Administer an NDB Environment
* Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 10, Objective 6.2
* Nutanix Database Management & Automation (NDMA) course, Module 6, Lesson 6.1 - NDB Software Upgrade

NEW QUESTION # 49
An administrator needs to add a stretched VLAN across two clusters in NDB Which two prerequisites should be met prior to completing this action? (Choose two.)

• A. VLAN must be IPAM.
• B. Nutanix Cluster Management must be enabled.
• C. Both clusters must be registered in NDB.
• D. VLAN must be static.

Answer: C,D

Explanation:
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

NEW QUESTION # 50
Which policies define Time Machine data availability across multiple registered clusters in NDB?

• A. Service Level Agreements
• B. Data Protection
• C. Recovery Plans
• D. Data Access Management

Answer: C

Explanation:
The recovery plans policy defines the Time Machine data availability across multiple registered clusters in NDB. The recovery plans policy allows the database administrator to specify the source and target clusters, the frequency and retention of the cross-cluster snapshots, and the network and compute profiles for the recovery operations. The recovery plans policy helps to ensure the disaster recovery and business continuity of the NDB-managed databases in case of a cluster failure or outage.
The data access management policy defines the access permissions and roles for the NDB users and groups.
The data access management policy allows the database administrator to grant or revoke access to the NDB instance, the database server VMs, the databases, and the database operations. The data access management policy helps to ensure the security and compliance of the NDB-managed databases and users.
The data protection policy defines the backup and restore settings for the NDB-managed databases. The data protection policy allows the database administrator to specify the frequency, retention, and compression of the database snapshots, and the backup location and encryption for the database backups. The data protection policy helps to ensure the backup and recovery of the NDB-managed databases within the same cluster.
The service level agreements policy defines the performance and availability metrics for the NDB-managed databases. The service level agreements policy allows the database administrator to monitor and enforce the database uptime, latency, throughput, and IOPS. The service level agreements policy helps to ensure the quality of service and performance of the NDB-managed databases.
References:
* Nutanix Database Management & Automation Training Course, Module 4: Nutanix Era Configuration, Lesson 4.1: Nutanix Era Configuration, slide 9.
* Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slides 8, 12, 16, 20.
* Nutanix Database Management & Automation Training Course, Module 6: Nutanix Era Disaster Recovery, Lesson 6.1: Nutanix Era Disaster Recovery, slides 5-7.

NEW QUESTION # 51
Which NDB feature collects logs and snapshots from databases?

• A. SLA
• B. One-click Patching
• C. Database Restore
• D. Time Machine

Answer: D

Explanation:
The correct answer is B because the Time Machine feature of NDB collects logs and snapshots from databases and stores them in a distributed file system. The Time Machine enables the administrator to protect, clone, and restore databases using the SLA policies and the NDB UI or API. The Time Machine also manages the replication of database snapshots in an NDB multicluster environment. The other options are not correct because they describe different features or functions of NDB. Option A is not correct because Database Restore is an operation that uses the Time Machine to restore a source database or a clone to a previous point in time. Option C is not correct because SLA is a policy that defines the frequency and retention of database snapshots and logs. Option D is not correct because One-click Patching is a feature that allows the administrator to test, publish, and apply database patches using the NDB UI or API. 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 Support & Insights

NEW QUESTION # 52
An administrator has been tasked with restoring an Oracle database that has recently failed. The administrator must restore the database to the prior day's state.
Which two restore options could be used? (Choose two.)

• A. Most Recent Time Available
• B. Point in Time
• C. Snapshot
• D. Tail Logs Backup

Answer: B,C

Explanation:
The correct answer is B and D because they are the two restore options that can be used to restore an Oracle database to the prior day's state using Nutanix Era. A snapshot is a point-in-time copy of a database that is stored in the Era Time Machine, which is a distributed file system that collects logs and snapshots from databases. A point in time is a specific moment in time within the retention period of the SLA policy that is applied to the database. By using either of these options, the administrator can select the snapshot or the point in time that corresponds to the prior day's state and restore the database from it. The other options are not correct because they are not restore options that are available in Nutanix Era. Option A is not correct because Most Recent Time Available is not a restore option, but a clone option that creates a clone of the database from the most recent snapshot or log backup. Option C is not correct because Tail Logs Backup is not a restore option, but a backup option that captures thetransaction logs of the database that have not been backed up by the SLA policy. 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 Database Services: Database modernization with Era - Now available]

NEW QUESTION # 53
......

Guaranteed Success in Nutanix Certified Professional (NCP) NCP-DB Exam Dumps: https://validexam.pass4cram.com/NCP-DB-dumps-torrent.html