Free NCP-US Exam Dumps Preview

Explanation: Nutanix Volumes is a feature that allows users to create and manage block storage devices (volume groups) on a Nutanix cluster. Volume groups can be accessed by external hosts using the iSCSI

protocol. To secure volume groups from unauthorized access, Nutanix recommends configuring CHAP (Challenge-Handshake Authentication Protocol) for each volume group in Prism Element. CHAP is a security feature that authenticates iSCSI initiators and targets before allowing access to a volume group.
CHAP requires both the initiator and the target to have a shared secret (a password) that is used to generate a challenge and a response during the authentication process. CHAP can prevent unauthorized access to volume groups and protect data from malicious attacks.
References:
Nutanix Volumes Administration Guide, page 25
Nutanix Volumes Security Guide

Explanation: Nutanix File Analytics is a feature that provides insights into the usage and activity of file data stored on Nutanix 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. The FAVM collects metadata and statistics from the FSVMs and displays them in a graphical user interface (GUI). The FAVM must be deployed on the same network as the FSVMs, which is the Client-side network. This network is used for communication between File Analytics and FSVMs, as well as for accessing the File Analytics UI from a web browser. The Client-side network must have DHCP enabled and must be routable from the external hosts that access the file shares and File Analytics UI.
References:
Nutanix Files Administration Guide, page 93
Nutanix File Analytics Deployment Guide

Explanation: The two network requirements for a four-node FSVM deployment are five available IP addresses on the Client network and five available IP addresses on the Storage network. The Client network is used for communication between the FSVMs and the clients, while the Storage network is used for communication between the FSVMs and the CVMs. For each FSVM, one Client IP and one Storage IP are required. Additionally, one extra Client IP is required for the file server VIP (Virtual IP), which is used as a single point of access for all shares and exports on the file server.
References:
Nutanix Files Administration Guide, page 28
Nutanix Files Solution Guide, page 7

Explanation: Volumes is a feature that allows users to create and manage block storage devices (volume groups) on a Nutanix cluster. Volume groups can be accessed by external hosts using the iSCSI protocol.
To ensure maximum performance, throughput, and redundancy for Oracle RAC on Linux implementation, while using the native method for securing workloads, the recommended configuration is to use Volumes with MPIO (Multipath I/O) and a single vDisk (virtual disk). MPIO is a technique that allows multiple paths between an iSCSI initiator and an iSCSI target, which improves performance and availability. A single vDisk is a logical unit number (LUN) that can be assigned to multiple hosts in a volume group, which simplifies management and reduces overhead.
References:
Nutanix Volumes Administration Guide, page 13
Nutanix Volumes Best Practices Guide

The "X" on the icon represents a distributed shared file, which is a file that belongs to a distributed share or export. A distributed share or export is a type of SMB share or NFS export that distributes the hosting of top-level directories across multiple FSVMs. The "X" indicates that the file is not hosted by the current FSVM, but by another FSVM in the cluster. The "X" also helps to identify which files are eligible for migration when using the Nutanix Files Migration Tool.
References:
Nutanix Files Administration Guide, page 34
Nutanix Files Migration Tool User Guide, page 10

Explanation: The protocols that are supported by Files are SMBv2, SMBv3, NFSv3, and NFSv4. SMB (Server Message Block) is a protocol that allows clients to access files, printers, and other resources on a network. NFS (Network File System) is a protocol that allows clients to access files on a remote server as if they were local. Files supports both SMB and NFS protocols for creating shares and exports that can be
accessed by different types of clients.
References:
Nutanix Files Administration Guide, page 31
Nutanix
Files Solution Guide, page 6

Explanation: The two platforms that are currently supported for Smart Tiering are AWS Standard and Azure Blob. Smart Tiering is a feature that allows administrators to tier data from Files to cloud storage based on file age, file size, and file type. Smart Tiering can help reduce the storage cost and optimize the performance of Files. Smart Tiering currently supports AWS Standard and Azure Blob as the cloud storage platforms, and more platforms will be added in the future.
References:
Nutanix Files Administration Guide,
page 99
Nutanix Files Solution Guide, page 11

Explanation: Nutanix Volumes allows physical servers to boot from a volume group that is exposed as an iSCSI target from the data services IP. To ensure high availability and load balancing, multipath I/O (MPIO) is required on the physical server. Object buckets cannot be used for booting physical servers 1.
References:
Nutanix Volumes Administration Guide1

Explanation: The administrator can meet this requirement by configuring network segmentation for Volumes. Network segmentation is a feature that allows administrators to isolate network traffic for different types of services, such as Volumes, Files, or Objects, on a Nutanix cluster. Network segmentation can improve the security, performance, and manageability of network traffic. By configuring network segmentation for Volumes, the administrator can place all iSCSI traffic on an isolated network and prevent it from interfering with other services or applications.
References:
Nutanix Volumes Administration Guide,
page 15
Nutanix Volumes Solution Guide, page 7

Explanation: The prerequisite that must be performed before performing one-click hypervisor upgrades is to disable the anti-affinity rules on all FSVMs. Anti-affinity rules are rules that prevent two or more VMs from running on the same host at the same time. Anti-affinity rules can improve the availability and performance of FSVMs by distributing them across different hosts in a cluster. However, anti-affinity rules can interfere with one-click hypervisor upgrades, which require all VMs on a host to be migrated to another host before upgrading the host. Therefore, the administrator must disable the anti-affinity rules on all FSVMs before performing one-click hypervisor upgrades, and re-enable them after the upgrades are
completed.
References:
Nutanix Files Administration Guide, page 22
Nutanix Files Upgrade Guide

Explanation: The error log that the administrator should review to determine why the relay service is down is Cerebro.ERROR. Cerebro is a service that runs on each FSVM and provides relay functionality for Data Lens. Relay service is responsible for collecting metadata and statistics from FSVMs and sending them to Data Lens via HTTPS. If Cerebro.ERROR log shows any errors or exceptions related to relay service, it can indicate that relay service is down or not functioning properly.
References:
Nutanix Files Administration Guide, page 23
Nutanix Data Lens User Guide