NCP-US-6.5 Exam Dumps - Nutanix Certified Professional (NCP) Questions and Answers

Nutanix Objects, part of Nutanix Unified Storage (NUS), provides S3-compatible object storage and is deployed as a set of Object Store Service VMs on a Nutanix cluster running AHV (or ESXi). The minimum number of nodes required for an Objects deployment ensures high availability and fault tolerance.

Analysis of Options:

Option A (1): Incorrect. A single-node cluster does not meet the minimum requirements for Nutanix Objects, as it cannot provide the necessary fault tolerance and high availability. Objects requires at least three nodes to distribute Object Store Service VMs and ensure data redundancy.

Option B (2): Incorrect. A two-node cluster also does not meet the minimum requirements for Objects. Nutanix requires at least three nodes to ensure that the Object Store Service VMs can be distributed across nodes and maintain availability in case of a node failure.

Option C (3): Correct. Nutanix Objects requires a minimum of three AHV nodes in a cluster to deploy and operate. This ensures that the Object Store Service VMs (typically three or more) can be distributed across nodes, providing high availability and fault tolerance. A three-node cluster is the minimum configuration for Objects to ensure data redundancy and resilience.

Option D (5): Incorrect. While a five-node cluster can certainly support Objects, it exceeds the minimum requirement. Nutanix specifies that three nodes are sufficient for a basic Objects deployment, making five nodes unnecessary for the minimum requirement.

Why Option C?

Nutanix Objects requires at least three nodes to ensure high availability, fault tolerance, and data redundancy. This allows the Object Store Service VMs to be distributed across nodes, ensuring that the service remains available even if a node fails. Three nodes is the minimum cluster size specified by Nutanix for deploying Objects.

Exact Extract from Nutanix Documentation:

From the Nutanix Objects Deployment Guide (available on the Nutanix Portal):

“Nutanix Objects requires a minimum of three AHV nodes in a cluster to ensure high availability and fault tolerance. This allows the Object Store Service VMs to be distributed across nodes, providing redundancy and ensuring service availability in case of a node failure.”

The most efficient way to generate a report listing the files matching those in the exhibit is to use Report Builder in File Analytics. Report Builder is a feature that allows administrators to create custom reports based on various filters and criteria, such as file name, file type, file size, file owner, file age, file access time, file modification time, file permission change time, and so on. Report Builder can also export the reports in CSV format for further analysis or sharing. References: Nutanix Files Administration Guide, page 97; Nutanix File Analytics User Guide

The tool that includes these features is File Analytics. File Analytics is a feature that provides insights into the usage and activity of file data stored on Files. File Analytics consists of a File Analytics VM (FAVM) that runs on a Nutanix cluster and communicates with the File Server VMs (FSVMs) that host the file shares. File Analytics can display various reports and dashboards that include these features:

Permission Denials: This report shows the number of permission denied events for file operations, such as read, write, delete, etc., along with the user, file, share, and server details.

Top 5 Active Users: This dashboard shows the top five users who performed the most file operations in a given time period, along with the number and type of operations.

Top 5 Accessed Files: This dashboard shows the top five files that were accessed the most in a given time period, along with the number of accesses and the file details.

File Distribution by Type: This dashboard shows the distribution of files by their type or extension, such as PDF, DOCX, JPG, etc., along with the number and size of files for each type. References: Nutanix Files Administration Guide, page 93; Nutanix File Analytics User Guide

Nutanix Files, part of Nutanix Unified Storage (NUS), supports WORM (Write Once, Read Many) shares to enforce immutability for compliance and data retention. A WORM share prevents files from being modified or deleted for a specified retention period. The “cool-off interval” (or cool-off period) is the time after a file is written to a WORM share during which it can still be modified or deleted before becoming immutable. The default cool-off interval is typically 1 minute, and the administrator wants to update it to 5 minutes.

Analysis of Options:

Option A (Delete and re-create the WORM share): Incorrect. Deleting and re-creating the WORM share would remove the existing share and its data, which is disruptive and unnecessary. The cool-off interval can be updated without deleting the share, making this an inefficient and incorrect approach.

Option B (Update the worm_cooloff_interval parameter using CLI): Correct. The worm_cooloff_interval parameter controls the cool-off period for WORM shares in Nutanix Files. This parameter can be updated using the Nutanix CLI (e.g., ncli or afs commands) on the file server. The administrator can log into an FSVM, use the CLI to set the worm_cooloff_interval to 5 minutes (300 seconds), and apply the change without disrupting the share. This is the most direct and efficient method to update the cool-off interval.

Option C (Contact support to update the WORM share): Incorrect. Contacting Nutanix support is unnecessary for this task, as updating the cool-off interval is a standard administrative action that can be performed using the CLI. Support is typically needed for complex issues, not for configurable parameters like this.

Option D (Use FSM to update the worm_cooloff_interval parameter): Incorrect. FSM (File Server Manager) is not a standard Nutanix tool or interface for managing Files configurations. The correct method is to use the CLI (option B) to update the worm_cooloff_interval parameter. While the Files Console (FSM-like interface) can manage some share settings, the cool-off interval requires CLI access.

Why Option B?

The worm_cooloff_interval parameter is a configurable setting in Nutanix Files that controls the cool-off period for WORM shares. Updating this parameter via the CLI (e.g., using ncli or afs commands on an FSVM) allows the administrator to change the cool-off interval from the default (1 minute) to 5 minutes without disrupting the existing share. This is the recommended and most efficient method per Nutanix documentation.

Exact Extract from Nutanix Documentation:

From the Nutanix Files Administration Guide (available on the Nutanix Portal):

“The cool-off interval for a WORM share, which determines the time after a file is written during which it can still be modified, is controlled by the worm_cooloff_interval parameter. To update this interval, use the CLI on an FSVM to set the parameter (e.g., to 300 seconds for 5 minutes) using commands like ncli or afs, then apply the change.”