Get Latest [Apr-2025] Conduct effective penetration tests using Pass4Leader NCP-DB-6.5
Penetration testers simulate NCP-DB-6.5 exam PDF
Nutanix NCP-DB-6.5 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 87
What are two status values that can be set within the Alerts Dashboard? (Choose two.)
- A. Resolved
- B. Acknowledged
- C. Auto
- D. Data Resiliency
Answer: A,B
Explanation:
The correct answer is B and D because these are the two status values that can be set within the Alerts Dashboard in NDB. Resolved means that the alert has been fixed and no longer requires attention.
Acknowledged means that the alert has been seen and is being worked on. Option A is incorrect because Auto is not a status value, but a mode that automatically resolves alerts based on predefined rules. Option C is incorrect because Data Resiliency is not a status value, but a feature that ensures the availability and integrity of the data in NDB.
Reference: The following sources provide more information about the Alerts Dashboard and its status values in NDB:
Nutanix Database Management & Automation (NDMA) course, Module 3: Monitoring Alerts and Storage Usage Within an NDB Implementation, Lesson 3.1: Monitoring Alerts Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 3 - Monitor Alerts and Storage Usage Within an NDB Implementation Nutanix Database Service (NDB) User Guide, Chapter 3: Monitoring Alerts and Storage Usage Within an NDB Implementation, Section 3.1: Monitoring Alerts
[Nutanix Support & Insights], Resolving All Alerts Related to a Database or Database Server VM in NDB
NEW QUESTION # 88
Where would an administrator find the total space being used by all Era clones for a specific database?
- A. Under the Cloning widget on the Databases > Clones database summary page.
- B. On the Database > Overview dashboard.
- C. On the Era Dashboard Database Summary Table under Clones.
- D. Under the Capacity widget on the Database Server VMS > List database summary page.
Answer: A
Explanation:
Nutanix Era leverages the Nutanix time-efficient snapshots to create the clones1. These database clones are highly space-efficient, consuming near-zero bytes by having only the further writes constituting to its size1. Therefore, an administrator would find the total space being used by all Era clones for a specific database under the Cloning widget on the Databases > Clones database summary page. The other options do not specifically provide information about the total space used by all Era clones for a specific database. Therefore, the correct answer is A. Under the Cloning widget on the Databases > Clones database summary page.
NEW QUESTION # 89
An administrator needs to take multiple snapshots per day and retain them for one week.
How should the administrator define and schedule the SLA?
- A. * Weekly snapshot retention: 1 week
* Daily Snapshot at: 2 - B. * Daily snapshot retention: 7 days
* Daily snapshot at: 2 - C. * Weekly snapshot retention: 1 week
* Snapshots per Day: 2 - D. * Daily snapshot retention: 7 days
* Snapshots per Day: 2
Answer: D
Explanation:
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.
Reference: 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
NEW QUESTION # 90
What is used to temporarily store the transaction logs of the source database before they are copied to the log?
- A. NDB Profiles
- B. Time Machine
- C. Database Agent
- D. NDB Drive
Answer: C
Explanation:
The Database Agent is used to temporarily store the transaction logs of the source database before they are copied to the log. This is a critical component for ensuring data consistency and recovery in database operations.
Reference: Nutanix Database Automation documentation, focusing on database agents and their roles in transaction log management.
NEW QUESTION # 91
An administrator is asked to refresh a database everyday at 9:30PM with data from as close to the refresh time as possible.
What is the best way achieve this requirement?
- A. Schedule an SLA policy that performs a snapshot at 99M and log catchup for every 15 min.
- B. Schedule an SLA policy to perform snapshot everyday at 9.30PM.
- C. Schedule an SLA policy to perform snapshot everyday at 9PM.
- D. Schedule e log catchup everyday at 9:30PM.
Answer: B
Explanation:
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.
NEW QUESTION # 92
Which default roles are available within Era for Role-Based Access Control?
- A. Era Oracle Admin
Era SQLServer Admin
* Era PostgreSQL Admin Era Mariadb Admin - B. prism Admin
* Era Super Admin
* Era Database Admin Era Infrastructure Admin - C. Super Admin Database Admin
Database Infrastructure Admin
* Infrastructure Admin - D. Super Admin Database Admin
Database Infrastructure Admin prism Infrastructure Admin
Answer: B
Explanation:
Nutanix Era offers Role-Based Access Control capabilities by organically embedding them in the product.
It provides the ability to add and remove users from Era, create and assign roles to users, and associate various privileges with a role1.
The default roles available within Era for Role-Based Access Control are:
prism Admin
Era Super Admin
Era Database Admin
Era Infrastructure Admin1
These roles allow for the management of both physical resources like IP addresses and VLANs along with database entities like databases, time-machines, clones, and so on1.
NEW QUESTION # 93
For which database engine does Era support rolling back a patch using CLI?
- A. MongoDB
- B. Microsoft SQL Server
- C. Oracle
- D. PostgreSQL
Answer: C
Explanation:
Nutanix Era supports a variety of database engines, including Oracle, PostgreSQL, MySQL, and Microsoft SQL Server1. However, when it comes to rolling back a patch using the Command Line Interface (CLI), this feature is specifically supported for the Oracle database engine1. This allows for efficient validation of critical database updates and simplifies database rollback1. Please note that while Era does provide support for other database engines, the ability to rollback a patch using CLI is currently specific to Oracle1.
NEW QUESTION # 94
Which action should be completed before updating Oracle Database software?
- A. Verify CVMs have the required memory allocated.
- B. Verify the Oracle OS version is supported on AHV.
- C. Perform rolling reboots of the Oracle Database VMs.
- D. Download the PSU from Oracle support.
Answer: B
NEW QUESTION # 95
An administrator needs to work with databases and time machines, but not database parameter profiles.
Which role satisfies this requirement?
- A. super Administrator
- B. Infrastructure Administrator
- C. Database Administrator (DBA)
- D. Database Infrastructure Administrator
Answer: C
Explanation:
In the Nutanix Database Automation (NCP-DB) framework, the role that allows an administrator to work with databases and time machines, but not database parameter profiles, is the Database Administrator (DBA)123. This role provides the necessary permissions to manage databases and time machines, which are essential components of the Nutanix Era solution. However, it does not grant access to database parameter profiles, which are typically managed by other roles45.
NEW QUESTION # 96
An administrator is creating a Windows Domain profile in Era.
Which optional field can be skipped and provided during the provisioning process?
- A. Domain Account
- B. Organizational Units
- C. Domain to join
- D. SQL Service Startup Account
Answer: D
Explanation:
When an administrator is creating a Windows Domain profile in Era, the SQL Service Startup Account is an optional field that can be skipped and provided during the provisioning process. This account is used to start the SQL Server service when the server starts up. If this field is not provided during the creation of the Windows Domain profile, it can be provided later during the provisioning process1.
NEW QUESTION # 97
Which disk is omitted from a Software Profile?
- A. User Database
- B. System Page File
- C. SQL Installation
- D. System Database
Answer: B
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.
Reference: 1: Nutanix Database Automation (NCP-DB) course, Module 2: Database Provisioning, Lesson 2.3:
Software Profiles, slide 5
NEW QUESTION # 98
A development team has requested that an administrator provide them a copy of the production Finance database. The business requires that any financial data is masked before going into development.
How should the administrator create a clone with masked data for the development environment?
- A. From the Time Machine, create a clone and paste the masking commands in the pre-clone field of the Pre-Post Commands section.
- B. 1. Create a script to mask the data.
2. Create the clone from the Time Machine and define the post-clone option with the full path\name of the masking script. - C. From the Time Machine, create a clone and paste the masking commands in the post-clone field of the Pre-Post Commands section.
- D. 1. Create a masking script on the source DB VM, Dev VM or SW Profile VM.
2. Create the clone from the Time Machine and define the post-clone option with the full path\name of the masking script.
Answer: D
Explanation:
According to the Nutanix Database Automation (NCP-DB) course, the Pre-Post Commands section allows the administrator to specify custom scripts that can be executed before or after the clone operation1. The masking script can be created on any of the VMs that have access to the source database, such as the source DB VM, the Dev VM, or the SW Profile VM2. The script should contain the commands to mask the sensitive data in the Finance database, such as replacing the real values with dummy values or encrypting the data2. The administrator can then create the clone from the Time Machine and define the post-clone option with the full path and name of the masking script1. This will ensure that the script is executed after the clone is created, and the data is masked before it is available for the development team1. The other options are not correct, as they either use the wrong field (pre- clone instead of post-clone), or do not specify where to create or store the masking script.
Reference: 1: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson
4.4: Pre-Post Commands, slide 5
2: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 7
NEW QUESTION # 99
What are two of the required steps to provision a new network in Clusters and extend it to Era?
(Choose two.)
- A. Add the new network in Era Multi-Clu5ter Management
- B. Add a new.' subnet to the correct VPC.
- C. Add the new VLAN in Ere Networks.
- D. Add the new subnet end VLAN in Network Configuration in PE.
Answer: C,D
Explanation:
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.
NEW QUESTION # 100
What are the three severity levels displayed under the Alert dashboard?
- A. Failed, Warning, Stopped
- B. Failed, Warning, Error
- C. Critical, Warning Info
- D. Critical. Waiting, Failed
Answer: C
Explanation:
The Alerts dashboard in Nutanix displays alert messages with three severity levels: Critical, Warning, and Info1. These severity levels help users understand the importance and urgency of each alert, allowing them to prioritize their responses accordingly1.
NEW QUESTION # 101
Which two encryption methods can be used when configuring an SMTP server? (Choose two.)
- A. S/MIME
- B. IPsec
- C. SSL
- D. TLS
Answer: C,D
Explanation:
NDB supports SMTP server configuration for sending email notifications and alerts. SMTP server configuration requires specifying the SMTP server address, port, username, password, and encryption method. The encryption method determines how the email messages are secured during transmission.
NDB supports two encryption methods for SMTP server configuration: TLS and SSL. TLS (Transport Layer Security) is a protocol that encrypts and authenticates data between the email client and the SMTP server. TLS can operate in two modes: explicit and implicit. In explicit mode, the email client and the SMTP server negotiate the encryption method and parameters after establishing a plain text connection. This mode typically uses port 587. In implicit mode, the email client and the SMTP server assume that the connection is encrypted from the start, without any negotiation. This mode typically uses port 465.
SSL (Secure Sockets Layer) is a predecessor of TLS that also encrypts and authenticates data between the email client and the SMTP server. SSL operates in implicit mode only, and uses port 465 by default.
SSL is less secure than TLS, but it is still widely used and supported by many email providers. S/MIME (Secure/Multipurpose Internet Mail Extensions) is a standard that encrypts and signs email messages at the application layer, rather than the transport layer. S/MIME requires the use of digital certificates and public key cryptography to ensure the confidentiality and integrity of email messages. S/MIME is not a valid encryption method for SMTP server configuration, as it does not affect the connection between the email client and the SMTP server.
IPsec (Internet Protocol Security) is a suite of protocols that secures IP packets at the network layer, rather than the application or transport layer. IPsec can encrypt and authenticate data between any two IP endpoints, such as routers, firewalls, or hosts. IPsec is not a valid encryption method for SMTP server configuration, as it does not apply to the specific protocol or port used by SMTP.
Reference: Nutanix Database Automation (NCP-DB) Course Details, Section 1.4: NDB Alerts and Notifications Nutanix Database Automation (NCP-DB) Certification Details, Objective 1.4: Configure NDB Alerts and Notifications Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 1.4: NDB Alerts and Notifications
[Nutanix Database Automation (NCP-DB) User Guide], Section 1.4: Configure SMTP Server Settings
NEW QUESTION # 102
An administrator needs to protect a database with a Point In Time Recovery (PITR) SLA that provides a minimum of seven days of log recovery.
What is the minimum Default SLA that meets this requirement?
- A. DEFAULT_008 BRASS SLA
- B. DEFAULT_008 SILVER SLA
- C. DEFAULT_008 BRONZE SLA
- D. DEFAULT_008 GOLD SLA
Answer: B
Explanation:
Nutanix Era (NDB) utilizes DEFAULT_008 SLAs with varying frequencies for snapshots and log backups to achieve different recovery point objectives (RPOs). Here's how they compare: DEFAULT_008 GOLD SLA: Typically has frequent log backups (e.g., every 15 minutes) and snapshots every few hours. This is designed for critical databases with very low RPOs.
DEFAULT_008 SILVER SLA: Offers a balance between protection and resource usage. Log backups might occur every hour with snapshots less frequently. This SLA is often suitable for databases requiring a good RPO without being overly resource-intensive.
DEFAULT_008 BRONZE SLA: Has less frequent log backups (e.g., every few hours) and less frequent snapshots. This is used for databases with less stringent RPO requirements.
DEFAULT_008 BRASS SLA: This has infrequent log backups and is usually considered the least protective SLA with the longest potential RPO Reasoning:
Since the requirement is to have at least a 7-day log recovery period, any SLA with more frequent log backups than daily is excessive. The DEFAULT_008 SILVER SLA, with its hourly log backups, easily satisfies this requirement, offering the ability to restore to a point in time within the last hour of the past seven days.
Reference: Nutanix Era User Guide/SLA
Management: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-NDB-User-Guide- v2_5:top-sla-management-c.html]
NEW QUESTION # 103
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 a separate mount point
- B. On the same disk as the operating system
- C. On the same mount point
- D. On the same disk as the binary installation
Answer: A
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.
Reference: 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 # 104
A request is received to refresh a database clone from a new manual snapshot. When the administrator attempts to create the new snapshot from the Time Machine, it is in a Frozen state.
What causes a Time Machine to enter the Frozen state and what are the administrator's options to complete the request?
- A. Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
Resolution: To complete the request the database must be re-registered in NDB, create a new Time Machine and create a new clone. - B. Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
Resolution: To complete the request the database must be re-registered in NDB, this thaws the Time Machine and it resumes operation so the clone can be refreshed. - C. Cause: The Time Machine enters a Frozen state after too many snapshot or log catchup failures.
Resolution: Remediate the snapshot or log catchup failures, this thaws the Time Machine, allowing normal operations to continue and the request can be completed. - D. Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
Resolution: The Time Machine must be paused, then the database re-registered with a new Time Machine and a new clone created.
Answer: B
Explanation:
A Time Machine is a core construct of the copy data management service in NDB that captures and manages the data of a database to deliver a recovery point objective (RPO) SLA. A Time Machine can enter a Frozen state for various reasons, such as database de-registration, snapshot or log catchup failures, or manual intervention. When a Time Machine is in a Frozen state, it stops taking new snapshots and log backups, and cannot perform any clone, refresh, or restore operations. To resume the normal operation of a Time Machine, it must be thawed by resolving the root cause of the freeze. One of the common causes of a Time Machine freeze is when the database is de-registered from NDB without removing the Time Machine. This can happen when the administrator wants to move the database to a different NDB instance or cluster, or when the database is accidentally de-registered. In this case, the Time Machine becomes orphaned and frozen, and cannot be used for any operations. To complete the request to refresh a database clone from a new manual snapshot, the administrator must first re-register the database in NDB using the same database name and ID as before. This will automatically thaw the Time Machine and resume its operation. The administrator can then create a new manual snapshot from the Time Machine and use it to refresh the database clone. The other options are not correct, as they either require unnecessary steps or do not address the root cause of the freeze.
Reference: Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 5 - Protect NDB-managed Databases Using Time Machine, Objective 5.1: Create, delete, and modify SLA retention policies Nutanix Database Management & Automation (NDMA) Course, Module 4: Nutanix Database Service (NDB) Data Protection, Lesson 4.1: Data Protection Overview, Topic: Time Machine Concepts Nutanix Support & Insights, TN-2101: Nutanix Database Service Time Machine Under the Hood, Section: Time Machine States and Transitions
NEW QUESTION # 105
What behavior is observed when applying patch profiles as a Super Admin?
- A. Hidden patches can be applied.
- B. Published patches cannot be applied if currently deprecated.
- C. Unpublished patches can be applied.
- D. Deprecated patches can be applied.
Answer: B
Explanation:
In the context of Nutanix Database Automation (NCP-DB), a Super Admin has the authority to apply patch profiles. However, if a patch is marked as deprecated, even if it's published, it cannot be applied.
This is because deprecation is a status that indicates the patch is outdated or has been superseded by a newer version, and thus should not be used1. This behavior ensures that only the most up-to-date and secure patches are applied to the system, maintaining the integrity and security of the database environment1.
NEW QUESTION # 106
Which ports are used by the NDB database agent for API calls?
- A. 5985 and 9389
- B. 443 and 9440
- C. 443 and 8080
- D. 3205 and 3260
Answer: B
NEW QUESTION # 107
An administrator needs to perform patching on a MongoDB server cluster within an NDB environment.
How should the administrator accomplish this task?
- A. Apply the patch to all nodes at once.
- B. Perform a rolling upgrade, applying the patch to the secondary members first, followed by the primary member.
- C. Perform a rolling upgrade, applying the patch to the primary member first, followed by the secondary members.
- D. Disable the replica set while patching.
Answer: B
Explanation:
The administrator should perform a rolling upgrade, applying the patch to the secondary members first, followed by the primary member, to accomplish the task of patching a MongoDB server cluster within an NDB environment. A rolling upgrade is a method of applying patches or updates to a cluster without downtime or interruption of service. The administrator can use the NDB patching feature to perform a rolling upgrade on a MongoDB server cluster, which consists of a primary member and one or more secondary members that form a replica set. The NDB patching feature allows the administrator to select the software profile version, the database parameters profile, and the network profile for the patching operation.
The NDB patching feature also automates the steps of the rolling upgrade, such as:
Step 1: The administrator initiates the patching operation on the NDB instance, and selects the MongoDB server cluster to be patched.
Step 2: The NDB instance verifies the prerequisites and compatibility of the patching operation, and creates a pre-patch snapshot of the MongoDB server cluster.
Step 3: The NDB instance applies the patch to the first secondary member of the MongoDB server cluster, and waits for the patching to complete successfully.
Step 4: The NDB instance verifies the status and functionality of the patched secondary member, and repeats the patching process for the remaining secondary members of the MongoDB server cluster, one at a time.
Step 5: The NDB instance performs a failover of the primary member to one of the patched secondary members, and applies the patch to the original primary member.
Step 6: The NDB instance verifies the status and functionality of the patched primary member, and performs a failback of the primary member to the original primary member, if desired.
Step 7: The NDB instance creates a post-patch snapshot of the MongoDB server cluster, and completes the patching operation.
Performing a rolling upgrade, applying the patch to the secondary members first, followed by the primary member, is the recommended and best practice method of patching a MongoDB server cluster within an NDB environment, as it ensures the high availability, consistency, and performance of the MongoDB server cluster and the databases.
Performing a rolling upgrade, applying the patch to the primary member first, followed by the secondary members, is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Applying the patch to the primary member first would disrupt the replication and synchronization of the MongoDB server cluster, and would require manual intervention and recovery steps to restore the MongoDB server cluster to a functional state.
Applying the patch to all nodes at once is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Applying the patch to all nodes at once would require shutting down the entire MongoDB server cluster, and would expose the MongoDB server cluster and the databases to potential errors, failures, and corruption during the patching process.
Disabling the replica set while patching is not a valid or feasible method of patching a MongoDB server cluster within an NDB environment, as it would cause downtime, data loss, and inconsistency of the MongoDB server cluster and the databases. Disabling the replica set while patching would break the replication and synchronization of the MongoDB server cluster, and would require manual intervention and recovery steps to re-enable the replica set and restore the MongoDB server cluster to a functional state.
Reference:
Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slides 11-12, 15-16.
Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.3: Nutanix Era Patching, slides 5-9.
Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.4: Nutanix Era Patching Lab, slides 5-10.
Nutanix Database Management & Automation Training Course, Module 7: Nutanix Era Troubleshooting, Lesson 7.1: Nutanix Era Troubleshooting, slide 6.
NEW QUESTION # 108
What does a Time Machine frozen status indicate?
- A. The NDB agent is stopped on the database VM.
- B. The database is paused on the database VM.
- C. The database was de-registered from NDB without removing the associated time machine.
- D. The Time Machine is paused and all automatic snapshot and log catch-up activities are halted.
Answer: C
Explanation:
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.
Reference: Nutanix Support & Insights, section "Resolving All Alerts for a Time Machine"
NEW QUESTION # 109
......
Tested Material Used To NCP-DB-6.5 Test Engine: https://www.pass4leader.com/Nutanix/NCP-DB-6.5-exam.html
Steps Necessary To Pass The NCP-DB-6.5 Exam: https://drive.google.com/open?id=1GPj9-k8JC5MyYSFwu91LKCiILppIcU1Z