[Full-Version] 2026 New Preparation Guide of Nutanix NCP-US-6.5 Exam
NCP-US-6.5 Practice Exam - 118 Unique Questions
Nutanix NCP-US-6.5 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 16
A company is currently using Objects 3.2 with a single Object Store and a single S3 bucket that was created as a repository for their data protection (backup) application. In the near future, additional S3 buckets will be created as this was requested by their DevOps team. After facing several issues when writing backup images to the S3 bucket, the vendor of the data protection solution found the issue to be a compatibility issue with the S3 protocol. The proposed solution is to use an NFS repository instead of the S3 bucket as backup is a critical service, and this issue was unknown to the backup software vendor with no foreseeable date to solve this compatibility issue. What is the fastest solution that requires the least consumption of compute capacity (CPU and memory) of their Nutanix infrastructure?
- A. Deploy Files and create a new Share with multi-protocol access enabled.
- B. Upgrade Objects to the latest version, create a new bucket, and enable NFS v3 access.
- C. Delete the existing bucket, create a new bucket, and enable NFS v3 access.
- D. Redeploy Objects using the latest version, create a new bucket, and enable NFS v3 access.
Answer: A
Explanation:
The company is using Nutanix Objects 3.2, a component of Nutanix Unified Storage (NUS), which provides S3-compatible object storage. Due to an S3 protocol compatibility issue with their backup application, they need to switch to an NFS repository. The solution must be the fastest and consume the least compute capacity (CPU and memory) on their Nutanix infrastructure.
Analysis of Options:
* Option A (Delete the existing bucket, create a new bucket, and enable NFS v3 access): Incorrect.
Nutanix Objects does support NFS access for buckets starting with version 3.5 (as per Nutanix documentation), but Objects 3.2 does not have this capability. Since the company is using Objects 3.2, this option is not feasible without upgrading or redeploying Objects, which is not mentioned in this option. Even if NFS were supported, deleting and recreating buckets does not address the compatibility issue directly and may still consume compute resources for bucket operations.
* Option B (Deploy Files and create a new Share with multi-protocol access enabled): Correct.
Nutanix Files, another component of NUS, supports NFS natively and can be deployed to create an NFS share quickly. Multi-protocol access (e.g., NFS and SMB) can be enabled on a Files share, allowing the backup application to use NFS as a repository. Deploying a Files instance with a minimal configuration (e.g., 3 FSVMs) consumes relatively low compute resources compared to redeploying or upgrading Objects, and it is the fastest way to provide an NFS repository without modifying the existing Objects deployment.
* Option C (Redeploy Objects using the latest version, create a new bucket, and enable NFS v3 access): Incorrect. Redeploying Objects with the latest version (e.g., 4.0 or later) would allow NFS v3 access, as this feature was introduced in Objects 3.5. However, redeployment is a time-consuming process that involves uninstalling the existing Object Store, redeploying a new instance, and reconfiguring buckets. This also consumes significant compute resources during the redeployment process, making it neither the fastest nor the least resource-intensive solution.
* Option D (Upgrade Objects to the latest version, create a new bucket, and enable NFS v3 access):
Incorrect. Upgrading Objects from 3.2 to a version that supports NFS (e.g., 3.5 or later) is a viable solution, as it would allow enabling NFS v3 access on a new bucket. However, upgrading Objects involves downtime, validation, and potential resource overhead during the upgrade process, which does not align with the requirement for the fastest solution with minimal compute capacity usage.
Why Option B is the Fastest and Least Resource-Intensive:
* Nutanix Files Deployment: Deploying a new Nutanix Files instance is a straightforward process that can be completed in minutes via Prism Central or the Files Console. A minimal Files deployment (e.g.,
3 FSVMs) requires 4 vCPUs and 12 GiB of RAM per FSVM (as noted in Question 2), totaling 12 vCPUs and 36 GiB of RAM. This is a relatively low resource footprint compared to redeploying or upgrading an Objects instance, which may require more compute resources during the process.
* NFS Support: Nutanix Files natively supports NFS, and enabling multi-protocol access (NFS and SMB) on a share is a simple configuration step that does not require modifying the existing Objects deployment.
* Speed: Deploying Files and creating a share can be done without downtime to the existing Objects setup, making it faster than upgrading or redeploying Objects.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Deployment Guide (available on the Nutanix Portal):
"Nutanix Files supports multi-protocol access, allowing shares to be accessed via both NFS and SMB protocols. To enable NFS access, deploy a Files instance and create a share with multi-protocol access enabled. A minimal Files deployment requires 3 FSVMs, each with 4 vCPUs and 12 GiB of RAM, ensuring efficient resource usage." From the Nutanix Objects Administration Guide (available on the Nutanix Portal):
"Starting with Objects 3.5, NFS v3 access is supported for buckets, allowing them to be mounted as NFS file systems. This feature is not available in earlier versions, such as Objects 3.2."
:
Nutanix Files Deployment Guide, Version 4.0, Section: "Deploying Nutanix Files and Configuring Shares" (Nutanix Portal).
Nutanix Objects Administration Guide, Version 4.0, Section: "NFS Access for Buckets" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Files and Objects Comparison".
NEW QUESTION # 17
An administrator has received an alert AI60068 - ADSDuplicationIPDetected details of alert as follows:
Which error log should the administrator review to determine the related Duplicate IP address involved?
- A. Solver.log
- B. Minerva_cvm.log
- C. Tcpkill.log
- D. Minerva.nvm.log
Answer: B
Explanation:
The Minerva_cvm.log file contains information about the Minerva service, which is responsible for managing the FSVMs and their communication with Prism Central. The Minerva_cvm.log file can be used to troubleshoot issues related to Nutanix Files, such as duplicate IP address detection. The log file can be found in /home/nutanix/data/logs/minerva on any CVM in the cluster. Reference: Nutanix Support Portal - Troubleshooting Nutanix Files
NEW QUESTION # 18
An administrator needs to enable a Nutanix feature that will ensure automatic client reconnection to shares whenever there are intermittent server-side networking issues and FSVM HA events. Which Files feature should the administrator enable?
- A. Multi-Protocol Shares
- B. Durable File Handles
- C. Connected Shares
- D. Persistent File Handles
Answer: B
Explanation:
Nutanix Files, part of Nutanix Unified Storage (NUS), provides file shares (e.g., SMB, NFS) that clients access. Intermittent server-side networking issues or FSVM High Availability (HA) events (e.g., an FSVM failover, as discussed in Question 40) can disrupt client connections. The administrator needs a feature to ensure automatic reconnection to shares during such events, minimizing disruption for users.
Analysis of Options:
* Option A (Multi-Protocol Shares): Incorrect. Multi-Protocol Shares allow a share to be accessed via both SMB and NFS (as in Questions 8 and 60), but this feature does not address client reconnection during networking issues or FSVM HA events-it focuses on protocol support, not connection resilience.
* Option B (Connected Shares): Incorrect. "Connected Shares" is not a recognized feature in Nutanix Files. It appears to be a made-up term and does not apply to automatic client reconnection.
* Option C (Durable File Handles): Correct. Durable File Handles is an SMB feature in Nutanix Files (as noted in Question 19) that ensures automatic client reconnection after temporary server-side disruptions, such as networking issues or FSVM HA events (e.g., failover when an FSVM's IP is reassigned, as in Question 40). When enabled, Durable File Handles allow SMB clients to maintain their session state and automatically reconnect without user intervention, meeting the requirement.
* Option D (Persistent File Handles): Incorrect. "Persistent File Handles" is not a standard feature in Nutanix Files. It may be confused with Durable File Handles (option C), which is the correct term for this SMB capability. Persistent File Handles is not a recognized Nutanix feature.
Why Option C?
Durable File Handles is an SMB 2.1+ feature supported by Nutanix Files that ensures clients can automatically reconnect to shares after server-side disruptions, such as intermittent networking issues or FSVM HA events (e.g., failover). This feature maintains the client's session state, allowing seamless reconnection without manual intervention, directly addressing the administrator's requirement.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Administration Guide (available on the Nutanix Portal):
"Durable File Handles is an SMB feature in Nutanix Files that ensures automatic client reconnection to shares during server-side disruptions, such as intermittent networking issues or FSVM HA events. Enable Durable File Handles to maintain client session state and allow seamless reconnection without user intervention."
:
Nutanix Files Administration Guide, Version 4.0, Section: "SMB Features in Nutanix Files" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Files SMB Features".
NEW QUESTION # 19
What is the minimum number of AHV nodes in a cluster required to use Objects?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: B
Explanation:
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."
:
Nutanix Objects Deployment Guide, Version 4.0, Section: "Minimum Requirements for Objects Deployment" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Objects Deployment Requirements".
NEW QUESTION # 20
An administrator wants to monitor their Files environment for suspicious activities, such mass deletion or access denials.
How can the administrator be alerted to such activities?
How can the administrator be alerted to such activities?
- A. Create a data protection policy in the Files view in Prism Central.
- B. Deploy the Files Analytics VM. and configure anomaly rules.
- C. Configure Alerts & Events in the Files Console, filtering for Warning severity.
- D. Configure Files to use ICAP servers, with monitors for desired activities.
Answer: B
Explanation:
The administrator can monitor their Files environment for suspicious activities, such as mass deletion or access denials, by deploying the File Analytics VM and configuring anomaly rules. 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 alert the administrator when there is an unusual or suspicious activity on file data, such as mass deletion, encryption, permission change, or access denial. The administrator can configure anomaly rules to define the threshold, time window, and notification settings for each type of anomaly. References: Nutanix Files Administration Guide, page 93; Nutanix File Analytics User Guide
NEW QUESTION # 21
What is a prerequisite for deploying Smart DR?
- A. The Files Manager must have at least three file servers.
- B. Open TCP port 7515 on all client network IPs (uni-directionally on the source and recovery file servers).
- C. Requires one-to-many shares.
- D. The primary and recovery file servers must have the same domain name.
Answer: B
Explanation:
Smart DR is a feature that allows share-level replication between active file server instances for disaster recovery. To configure Smart DR, one of the prerequisites is to open TCP port 7515 on all client network IPs (uni-directionally on the source and recovery file servers). This port is used for communication between the FSVMs and the replication engine. Reference: Nutanix Files Administration Guide, page 79; Nutanix Files Solution Guide, page 9
NEW QUESTION # 22
An administrator has been asked to confirm the ability of a physical windows Server 2019 host to boot from storage on a Nutanix AOS cluster.
Which statement is true regarding this confirmation by the administrator?
- A. Physical servers may boot from a volume group from the data services IP and MPIO is not required.
- B. Physical servers may boot from an object bucket from the data services IP and MPIO is required.
- C. Physical servers may boot from a volume group from the data services IP and MPIO is
- D. Physical servers may boot from an object bucket from the data services IP address and MPIO is not required.
Answer: C
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 servers1. Reference: Nutanix Volumes Administration Guide1
NEW QUESTION # 23
Workload optimization on Files is configured on which entity?
- A. Share
- B. File Server
- C. Volume
- D. Container
Answer: B
Explanation:
Workload optimization in Nutanix Files, part of Nutanix Unified Storage (NUS), involves tuning the Files deployment to handle specific workloads efficiently. This was previously discussed in Question 13, where workload optimization was based on FSVM quantity. The question now asks which entity workload optimization is configured on.
Analysis of Options:
* Option A (Volume): Incorrect. Volumes in Nutanix refer to block storage provided by Nutanix Volumes, not Nutanix Files. Workload optimization for Files does not involve Volumes, which are a separate entity for iSCSI-based storage.
* Option B (Share): Incorrect. Shares in Nutanix Files are the individual file shares (e.g., SMB, NFS) accessed by clients. While shares can be tuned (e.g., quotas, permissions), workload optimization in Files is not configured at the share level-it applies to the broader file server infrastructure.
* Option C (Container): Incorrect. Containers in Nutanix are logical storage pools managed by AOS, used to store data for VMs, Files, and other services. While Files data resides in a container, workload optimization is not configured at the container level-it is specific to the Files deployment.
* Option D (File Server): Correct. Workload optimization in Nutanix Files is configured at the File Server level, which consists of multiple FSVMs (as established in Question 13). The File Server is the entity that manages all FSVMs, shares, and resources, and optimization tasks (e.g., scaling FSVMs, adjusting resources) are applied at this level to handle workloads efficiently.
Why Option D?
Workload optimization in Nutanix Files involves adjusting resources and configurations at the File Server level, such as scaling the number of FSVMs (as in Question 13) or tuning memory and CPU for the File Server. The File Server encompasses all FSVMs and shares, making it the entity where optimization is configured to ensure the entire deployment can handle the workload effectively.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Administration Guide (available on the Nutanix Portal):
"Workload optimization in Nutanix Files is configured at the File Server level. This involves adjusting the number of FSVMs, allocating resources (e.g., CPU, memory), and tuning configurations to optimize the File Server for specific workloads."
:
Nutanix Files Administration Guide, Version 4.0, Section: "Optimizing Nutanix Files for Workloads" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Files Performance Optimization".
NEW QUESTION # 24
Which Data Lens feature maximizes the available file server space by moving cold data from the file server to an object store?
- A. Versioning
- B. Smart Tier
- C. Backup
- D. Smart DR
Answer: B
Explanation:
Nutanix Data Lens, part of Nutanix Unified Storage (NUS), provides data governance and analytics for Nutanix Files, including features to optimize storage usage. The administrator wants to maximize available space on the file server by moving cold (infrequently accessed) data to an object store (e.g., AWS S3, Azure Blob), which aligns with a specific Data Lens feature.
Analysis of Options:
* Option A (Smart Tier): Correct. Smart Tier is a feature in Data Lens (and Nutanix Files, as noted in Question 34) that identifies cold data based on access patterns and tiers it to an external object store, such as AWS S3 or Azure Blob. This process frees up space on the file server while keeping the data accessible through the same share, maximizing available space as required.
* Option B (Smart DR): Incorrect. Smart DR is a disaster recovery solution for Nutanix Files that automates replication policies between file servers (e.g., using NearSync). It replicates data to a recovery site for DR purposes, not to an object store, and does not free up space on the primary file server-it creates a copy.
* Option C (Backup): Incorrect. Data Lens does not have a "Backup" feature. While Nutanix Files can be backed up using third-party tools or replication, this is not a Data Lens feature, and backups do not move cold data to an object store to free up space-they create additional copies for recovery purposes.
* Option D (Versioning): Incorrect. Versioning is a feature in Nutanix Objects (as seen in Questions 11 and 15), not Data Lens, and it retains multiple versions of objects, not file server data. Even if versioning were applied to Files shares (e.g., via snapshots), it does not move cold data to an object store-it retains versions locally, consuming more space.
Why Option A?
Smart Tier, supported by Data Lens, identifies cold data on the file server and moves it to an external object store, freeing up space on the primary storage while keeping the data accessible. This directly addresses the requirement to maximize available file server space by offloading cold data, aligning with Data Lens's data management capabilities.
Exact Extract from Nutanix Documentation:
From the Nutanix Data Lens Administration Guide (available on the Nutanix Portal):
"Data Lens supports Smart Tier, a feature that maximizes available file server space by identifying cold data based on access patterns and tiering it to an external object store, such as AWS S3 or Azure Blob. This process frees up space on the file server while maintaining data accessibility."
:
Nutanix Data Lens Administration Guide, Version 4.0, Section: "Smart Tier with Data Lens" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Data Lens Features".
NEW QUESTION # 25
An administrator is required to place all iSCSI traffic on an isolated network.
How can the administrator meet this requirement?
- A. Configure the Data Services IP on an isolated network.
- B. Configure network segmentation for Volumes.
- C. Create a Volumes network in Prism Central.
- D. Create a new network interface on the CVMs via ncli.
Answer: B
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. Reference: Nutanix Volumes Administration Guide, page 15; Nutanix Volumes Solution Guide, page 7
NEW QUESTION # 26
An administrator is trying to create a Distributed Share, but the Use Distributed Share/Export type instead of Standard option is not present when creating the share.
What is most likely the cause for this?
- A. The file server does not have the correct license
- B. The cluster is configured with hybrid storage
- C. The file server resides on a single node cluster.
- D. The cluster only has three nodes.
Answer: C
Explanation:
The most likely cause for this issue is that the file server resides on a single node cluster. A distributed share is a type of SMB share or NFS export that distributes the hosting of top-level directories across multiple FSVMs, which improves load balancing and performance. A distributed share cannot be created on a single node cluster, because there is only one FSVM available. A distributed share requires at least two nodes in the cluster to distribute the directories. Therefore, the option to use distributed share/export type instead of standard is not present when creating a share on a single node cluster. References: Nutanix Files Administration Guide, page 33; Nutanix Files Solution Guide, page 8 A single-node cluster cannot support a Distributed Share because it can only host one FSVM, whereas Distributed Shares require at least three FSVMs for distribution and high availability. This limitation causes the "Use Distributed Share/Export type instead of Standard" option to be absent when creating a share, as the cluster does not meet the minimum requirements.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Administration Guide (available on the Nutanix Portal):
"Distributed Shares require a minimum of three FSVMs to ensure scalability and high availability, which typically requires a cluster with at least three nodes. On a single-node cluster, only Standard Shares are supported, and the option to create a Distributed Share will not be available in the Files Console."
:
Nutanix Files Administration Guide, Version 4.0, Section: "Distributed Shares Requirements" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Files Share Types".
NEW QUESTION # 27
Which port is required between a CVM or Prism Central to insights,nutanix.com for Data Lens configuration?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: C
Explanation:
Data Lens is a SaaS that provides file analytics and reporting, anomaly detection, audit trails, ransomware protection features, and tiering management for Nutanix Files. To configure Data Lens, one of the network requirements is to allow HTTPS (port 443) traffic between a CVM or Prism Central to insights.nutanix.com.
This allows Data Lens to collect metadata and statistics from the FSVMs and display them in a graphical user interface. References: Nutanix Files Administration Guide, page 93; Nutanix Data Lens User Guide Data Lens is a cloud-based service hosted at insights.nutanix.com, and Nutanix requires secure communication over HTTPS (port 443) for configuration and operation. The CVMs or Prism Central must have outbound access to insights.nutanix.com on port 443 to enable Data Lens, authenticate with the service, and send/receive analytics data.
Exact Extract from Nutanix Documentation:
From the Nutanix Data Lens Administration Guide (available on the Nutanix Portal):
"Data Lens requires outbound connectivity from the Nutanix cluster (CVMs or Prism Central) to insights.
nutanix.com over port 443 (HTTPS). Ensure that this port is open for secure communication to enable Data Lens configuration and operation."
:
Nutanix Data Lens Administration Guide, Version 4.0, Section: "Network Requirements for Data Lens" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Data Lens Network Configuration".
NEW QUESTION # 28
Within the Prism Central Entity > Services > Objects menu option, what is the correct task order for creating an object storage?
Answer:
Explanation:
NEW QUESTION # 29
What is a mandatory criterion for configuring Smart Tier?
- A. Certificate
- B. VPC name
- C. Target URL over HTTP
- D. Access and secret keys
Answer: D
Explanation:
Smart Tiering in Nutanix Files, part of Nutanix Unified Storage (NUS), allows infrequently accessed (Cold) data to be tiered to external storage, such as a public cloud (e.g., AWS S3, Azure Blob), to free up space on the primary cluster (as noted in Question 34). Configuring Smart Tiering requires setting up a connection to the external storage target, which involves providing credentials and connectivity details.
Smart Tiering requires a connection to an external storage target, such as a cloud provider. The access key and secret key are mandatory to authenticate Nutanix Files with the target (e.g., an S3 bucket), enabling secure data tiering. Without these credentials, the tiering configuration cannot be completed, making them a mandatory criterion.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Administration Guide (available on the Nutanix Portal):
"To configure Smart Tiering in Nutanix Files, you must provide the access key and secret key for the external storage target (e.g., AWS S3, Azure Blob). These credentials are mandatory to authenticate with the cloud provider and enable data tiering to the specified target."
:
Nutanix Files Administration Guide, Version 4.0, Section: "Configuring Smart Tiering" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Files Smart Tiering".
NEW QUESTION # 30
An administrator is looking for a tool that includes these features:
* Permission Denials
* Top 5 Active Users
* Top 5 Accessed Files
* File Distribution by Type
Nutanix tool should the administrator choose?
- A. Files Console
- B. Prism Central
- C. File Server Manager
- D. File Analytics
Answer: D
Explanation:
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. Reference: Nutanix Files Administration Guide, page 93; Nutanix File Analytics User Guide
NEW QUESTION # 31
An administrator has received an alert A130357 - VolumeGroupProtectionFailedOnPC with the following details:
* Block Serial Number: 16Suxxxxxxxx
* Alert Time: Thu Jan 19 2023 20:31:10 GMT-0800 (PST)
* Alert Type: VolumeGroupProtectionFailedOnPC
* Alert Message: A130357:VolumeGroupProtectionFailedOnPC
* Cluster ID: xxxxx
* Alert Body: Volume Group protection failed on PCWhich two conditions need to be addressed to allow successful protection of the Volume Group? (Choose two.)
- A. The Protection Policy applied on Volume Group has a NearSync snapshot schedule applied.
- B. Volume Group is protected in a legacy protection domain.
- C. Volume Group is not protected in a legacy protection domain.
- D. The Protection Policy applied on Volume Group has an Async snapshot schedule applied.
Answer: A,B
Explanation:
The alert A130357 - VolumeGroupProtectionFailedOnPC in a Nutanix environment indicates a failure to protect a Volume Group (VG) in a Protection Domain (PD) managed through Prism Central (PC). Nutanix Volumes, part of Nutanix Unified Storage (NUS), provides block storage via iSCSI, and Volume Groups can be protected using Protection Domains for snapshots and replication. The alert suggests that the protection process failed, likely due to incompatible configurations.
Understanding the Issue:
* Volume Group Protection: A Volume Group in Nutanix Volumes can be added to a Protection Domain in Prism Central for data protection (e.g., snapshots, replication).
* Protection Failed on PC: The failure occurred during the protection process, managed through Prism Central, indicating an issue with the Protection Domain or policy settings.
* Conditions to Address: The failure is likely due to configuration mismatches or unsupported settings in the Protection Domain or policy.
Analysis of Conditions:
* Option A (Volume Group is protected in a legacy protection domain): Correct. A "legacy protection domain" refers to an older protection mechanism in Nutanix (e.g., from earlier AOS versions) that may not be fully compatible with newer Prism Central features or Volume Group protection workflows. If the Volume Group is part of a legacy PD, the protection process may fail due to deprecated features or APIs. Addressing this involves migrating the Volume Group to a modern Protection Domain in Prism Central, ensuring compatibility.
* Option B (The Protection Policy applied on Volume Group has an Async snapshot schedule applied): Incorrect. An Async (asynchronous) snapshot schedule is a standard and supported configuration for Volume Group protection in a Protection Domain. Async schedules take snapshots at intervals (e.g., hourly, daily) and replicate them to a remote site, and this does not cause protection failures-it's a valid setup.
* Option C (The Protection Policy applied on Volume Group has a NearSync snapshot schedule applied): Correct. NearSync is a near-synchronous replication schedule (e.g., 1-minute RPO, as in Question 24) that is supported for VMs and some Nutanix Files configurations, but it is not supported for Volume Groups in a Protection Domain. If a NearSync schedule is applied to a Volume Group's Protection Policy, the protection will fail because Volume Groups only support Async schedules.
Addressing this involves changing the schedule to an Async policy, which is compatible with Volume Groups.
* Option D (Volume Group is not protected in a legacy protection domain): Incorrect. This option suggests that the Volume Group is already in a modern (non-legacy) Protection Domain, which would not cause the failure. The issue lies in specific conditions (e.g., legacy PD or incompatible schedule), so this option does not identify a condition that needs addressing.
Selected Conditions:
* A: A legacy Protection Domain can cause compatibility issues, leading to protection failures. Migrating to a modern PD in Prism Central resolves this.
* C: A NearSync schedule is not supported for Volume Groups, causing the protection to fail. Switching to an Async schedule ensures compatibility.
Why These Conditions?
* Legacy Protection Domain (A): Legacy PDs may use outdated mechanisms that are incompatible with Prism Central's modern protection workflows for Volume Groups, causing failures.
* NearSync Schedule (C): Volume Groups in a Protection Domain only support Async snapshot schedules. A NearSync schedule, designed for low-RPO replication, is not supported and will cause the protection process to fail.
Exact Extract from Nutanix Documentation:
From the Nutanix Prism Alerts Reference Guide (available on the Nutanix Portal):
"Alert A130357 - VolumeGroupProtectionFailedOnPC: This alert is triggered when Volume Group protection fails in a Protection Domain managed through Prism Central. Common causes include:
* The Volume Group is protected in a legacy protection domain, which is not fully compatible with modern Prism Central workflows. Migrate the Volume Group to a modern Protection Domain.
* The Protection Policy applied to the Volume Group has a NearSync snapshot schedule, which is not supported for Volume Groups. Change the schedule to an Async policy to allow successful protection."
:
Nutanix Prism Alerts Reference Guide, Version 6.0, Section: "Alert A130357 - VolumeGroupProtectionFailedOnPC" (Nutanix Portal).
Nutanix Volumes Administration Guide, Version 6.0, Section: "Protecting Volume Groups with Protection Domains" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Volumes Data Protection".
NEW QUESTION # 32
Within the Prism Central Entity > Services > Objects menu option, what is the correct task order for creating an object storage?
Answer:
Explanation:
Explanation:
The correct task order for creating an object store is:
* Select ObjectStore Service and click Enable
* Click Create Object Store to start creating the first Object store
* Click Download Creation Checklist to download the list of prerequisites for deploying an Object store The first step is to enable the ObjectStore Service, which is a service that allows users to create and manage object storage clusters on a Nutanix cluster. The second step is to create an Object store, which is an object storage cluster that provides S3-compatible access to buckets and objects for various applications and users.
The third step is to download the Creation Checklist, which is a document that lists the prerequisites and configurations that are required for deploying an Object store, such as cluster details, network details, storage details, etc. The administrator should review and complete the Creation Checklist before proceeding with the deployment of the Object store.
NEW QUESTION # 33
An administrator is tasked with performing an upgrade to the latest Objects version.
What should the administrator do prior to upgrade Objects Manager?
- A. Upgrade Objects service
- B. Upgrade Lifecycle Manager
- C. Upgrade MSP
- D. Upgrade AOS
Answer: D
Explanation:
Before upgrading Objects Manager, the administrator must upgrade AOS to the latest version. AOS is the core operating system that runs on each node in a Nutanix cluster and provides the foundation for Objects Manager and Objects service. Upgrading AOS will ensure compatibility and stability for Objects components. Reference: Nutanix Objects Administration Guide, Acropolis Operating System Upgrade Guide
NEW QUESTION # 34
An existing Object bucket was created for backups with these requirements:
* WORM policy of one year
* Versioning policy of one year
* Lifecycle policy of three years
A recent audit has reported a compliance failure. Data that should be retained for three years has been deleted prematurely.
How should the administrator resolve the compliance failure within Objects?
- A. Recreate a new bucket with the retention policy of three years.
- B. Modify the existing bucket versioning policy from one year to three years.
- C. Modify the existing bucket WORM policy from one year to three years.
- D. Create a tiering policy to store deleted data on cold storage for three years.
Answer: C
Explanation:
The administrator should resolve the compliance failure within Objects by modifying the existing bucket WORM (Write-Once Read-Many) policy from one year to three years. WORM is a feature that prevents anyone from modifying or deleting data in a bucket while the policy is active. WORM policies help comply with strict data retention regulations that mandate how long specific data must be stored. The administrator can extend the WORM retention period for a bucket at any time, but cannot reduce it or delete it. By extending the WORM policy from one year to three years, the administrator can ensure that data in the bucket is retained for the required duration and not deleted prematurely. References: Nutanix Objects User Guide, page 17; Nutanix Objects Solution Guide, page 9 Nutanix Objects, part of Nutanix Unified Storage (NUS), supports several policies for data retention and management:
* WORM (Write Once, Read Many): Prevents objects from being modified or deleted for a specified period.
* Versioning: Retains multiple versions of an object, with a policy to expire non-current versions after a specified time.
* Lifecycle Policy: Deletes objects (or versions) after a specified time (e.g., "Expire current objects after X years").
The bucket in question has:
* A WORM policy of one year (objects cannot be modified/deleted for one year).
* A versioning policy of one year (non-current versions are deleted after one year).
* A lifecycle policy of three years (current objects are deleted after three years).
The compliance failure indicates that data expected to be retained for three years was deleted prematurely, meaning some data was deleted before the three-year mark.
Analysis of Policies and Issue:
* The lifecycle policy of three years means the current version of an object is deleted after three years, which aligns with the retention requirement.
* The WORM policy of one year ensures that objects cannot be deleted or modified for one year, after which they can be deleted (unless protected by another policy).
* The versioning policy of one year means that non-current versions of an object are deleted after one year. Since versioning is enabled, every time an object is updated, a new version is created, and the previous version becomes a non-current version. With a versioning policy of one year, these non- current versions are deleted after one year, which is likely causing the compliance failure-data (past versions) that should be retained for three years is being deleted after only one year.
Analysis of Options:
* Option A (Modify the existing bucket versioning policy from one year to three years): Correct. The versioning policy determines how long non-current versions are retained. Since the compliance requirement is to retain data for three years, and the lifecycle policy already ensures the current version is kept for three years, the versioning policy should be updated to retain non-current versions for three years as well. This prevents premature deletion of past versions, resolving the compliance failure.
* Option B (Modify the existing bucket WORM policy from one year to three years): Incorrect. The WORM policy prevents deletion or modification of objects for the specified period (one year).
Extending it to three years would prevent manual deletion for a longer period, but it does not address the issue of non-current versions being deleted by the versioning policy after one year. The lifecycle and versioning policies are the primary mechanisms for automatic deletion, and WORM does not override them once the WORM period expires.
* Option C (Create a tiering policy to store deleted data on cold storage for three years): Incorrect.
Tiering policies in Nutanix Objects move data to cold storage (e.g., AWS S3, Azure Blob) for cost optimization, but they do not apply to deleted data. Once data is deleted (e.g., by the versioning policy), it cannot be tiered. This option does not address the root cause of premature deletion.
Why Option A?
The compliance failure is due to non-current versions being deleted after one year (per the versioning policy), while the requirement is to retain all data for three years. By extending the versioning policy to three years, non-current versions will be retained for the full three-year period, aligning with the lifecycle policy for the current version and resolving the compliance issue.
Exact Extract from Nutanix Documentation:
From the Nutanix Objects Administration Guide (available on the Nutanix Portal):
"When versioning is enabled, the versioning policy determines how long non-current versions of an object are retained before deletion. For example, a versioning policy of one year will delete non-current versions after one year. To meet compliance requirements, ensure that the versioning policy aligns with the desired retention period for all versions of an object, in conjunction with the lifecycle policy for current objects."
:
Nutanix Objects Administration Guide, Version 4.0, Section: "Versioning and Lifecycle Policies" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Objects Data Retention".
NEW QUESTION # 35
An administrator has been requested to set up a Files instance in a Nutanix environment. After testing data in the environment, it was determined an estimated 4,000 connections on average will be needed per node. What is the proper memory sizing that the administrator should use to configure this environment?
- A. 40 GiB RAM per node
- B. 96 GiB RAM per node
- C. 32 GiB RAM per node
- D. 128 GiB RAM per node
Answer: B
Explanation:
Nutanix Files, part of Nutanix Unified Storage (NUS), uses File Server Virtual Machines (FSVMs) to manage file services (e.g., SMB, NFS). Each FSVM runs on a node in the Nutanix cluster, and the number of connections per node impacts the resource requirements, particularly memory (RAM), for the FSVMs. The administrator needs to size the memory for a Files instance where each node will handle an average of 4,000 connections.
Sizing Guidelines:
Nutanix provides sizing guidelines for Files deployments based on the number of connections per FSVM (and thus per node, assuming one FSVM per node, which is the default configuration). The memory requirements scale with the number of connections to ensure performance and stability:
* The minimum memory per FSVM is 12 GiB (as noted in Question 2), which supports up to 1,000 connections.
* For higher connection counts, Nutanix recommends increasing the memory proportionally.
According to Nutanix documentation:
* Up to 1,000 connections: 12 GiB RAM per FSVM.
* 1,000 to 2,000 connections: 24 GiB RAM per FSVM.
* 2,000 to 4,000 connections: 48 GiB RAM per FSVM.
* 4,000 to 8,000 connections: 96 GiB RAM per FSVM.
Since the question specifies 4,000 connections per node, and assuming one FSVM per node (standard deployment), the FSVM on each node needs to handle 4,000 connections. Based on the sizing guidelines:
* 4,000 connections fall into the 4,000 to 8,000 range, requiring 96 GiB RAM per FSVM.
* Since each node hosts one FSVM, this translates to 96 GiB RAM per node dedicated to the FSVM.
Analysis of Options:
* Option A (32 GiB RAM per node): Incorrect. 32 GiB RAM per node is sufficient for up to 2,000 connections (24 GiB for the FSVM, plus some overhead), but it is insufficient for 4,000 connections, which require 96 GiB.
* Option B (40 GiB RAM per node): Incorrect. 40 GiB RAM per node is still too low for 4,000 connections, as it falls short of the 96 GiB recommended for this connection range.
* Option C (96 GiB RAM per node): Correct. 96 GiB RAM per node aligns with Nutanix's sizing guidelines for an FSVM handling 4,000 to 8,000 connections, ensuring the Files instance can manage the expected load efficiently.
* Option D (128 GiB RAM per node): Incorrect. While 128 GiB RAM per node would work, it exceeds the recommended sizing for 4,000 connections. Nutanix recommends 96 GiB for up to 8,000 connections, and 128 GiB is typically reserved for even higher connection counts (e.g., >8,000) or additional workloads on the node. The question asks for the "proper" sizing, which is the minimum recommended for the given load, making 96 GiB the correct choice.
Why Option C?
For 4,000 connections per node, Nutanix recommends 96 GiB RAM per FSVM (one FSVM per node), which translates to 96 GiB RAM per node dedicated to the FSVM. This ensures the Files instance can handle the connection load without performance degradation, aligning with Nutanix's sizing guidelines.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Sizing Guide (available on the Nutanix Portal):
"For Nutanix Files deployments, memory sizing depends on the number of connections per FSVM. For 4,000 to 8,000 connections, allocate 96 GiB of RAM per FSVM. Assuming one FSVM per node, this translates to
96 GiB RAM per node dedicated to the FSVM to ensure optimal performance." Additional Notes:
* The question assumes one FSVM per node, which is the default configuration for Nutanix Files unless otherwise specified. If multiple FSVMs were on a single node, the total RAM would need to be adjusted, but the question's phrasing ("per node") aligns with the standard one-FSVM-per-node deployment.
* The 96 GiB RAM is for the FSVM itself; the node may require additional RAM for other workloads (e.
g., CVM, VMs), but the question focuses on the Files instance's memory sizing, making 96 GiB the correct answer.
:
Nutanix Files Sizing Guide, Version 4.0, Section: "Memory Sizing for Nutanix Files" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Files Sizing and Performance".
NEW QUESTION # 36
Deploying Files instances require which two minimum resources? (Choose two)
- A. 8 GiB of memory per host
- B. 8 vCPUs per host
- C. 4 vCPUs per host
- D. 12 GiB of memory per host
Answer: A,C
Explanation:
The two minimum resources that are required for deploying Files instances are 8 GiB of memory per host and
4 vCPUs per host. Memory and vCPUs are resources that are allocated to VMs (Virtual Machines) to run applications and processes. Files instances are file server instances (FSIs) that run on FSVMs (File Server VMs) on a Nutanix cluster. FSVMs require at least 8 GiB of memory and 4 vCPUs per host to function properly and provide SMB and NFS access to file shares and exports. The administrator should ensure that there are enough memory and vCPUs available on each host before deploying Files instances. References: Nutanix Files Administration Guide, page 27; Nutanix Files Solution Guide, page 6
NEW QUESTION # 37
What are two ways to manage Objects? (Choose two.)
- A. CLI
- B. SSH
- C. PC
- D. API
Answer: C,D
Explanation:
There are two ways to manage Objects: PC (Prism Central) and API (Application Programming Interface). PC is a web-based user interface that allows administrators to create, configure, monitor, and manage Objects clusters, buckets, users, and policies. API is a set of S3-compatible REST APIs that allows applications and users to interact with Objects programmatically. API can be used to perform operations such as creating buckets, uploading objects, listing objects, downloading objects, deleting objects, and so on. References: Nutanix Objects User Guide; Nutanix Objects API Reference Guide
NEW QUESTION # 38
Which protocols are supported by Files?
- A. SMBv1. SMBv2, NFSv3, NFSv4
- B. SMBv1. SMBv2, NFSv2, NFSv3
- C. SMBv2 SMBv3, NFSv2, NFSv3
- D. SMBv2 SMBv3, NFSv3, NFSv4
Answer: D
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. Reference: Nutanix Files Administration Guide, page 31; Nutanix Files Solution Guide, page 6
NEW QUESTION # 39
What is the binary image extension of File Analytics?
- A. VMDK
- B. QCOW2
- C. ISO
- D. JSON
Answer: B
Explanation:
File Analytics is deployed as a VM, and Nutanix provides its binary image in QCOW2 format for AHV, which is the primary hypervisor for Nutanix clusters. QCOW2 is the standard disk image format for AHV, making it the correct choice for the File Analytics deployment image.
Exact Extract from Nutanix Documentation:
From the Nutanix File Analytics Deployment Guide (available on the Nutanix Portal):
"The File Analytics VM is provided as a binary image in QCOW2 format for deployment on AHV clusters.
To deploy File Analytics, download the QCOW2 image from the Nutanix Portal and import it into the cluster using Prism Central or Prism Element."
:
Nutanix File Analytics Deployment Guide, Version 4.0, Section: "Deploying File Analytics" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix File Analytics Deployment".
NEW QUESTION # 40
......
Latest Questions NCP-US-6.5 Guide to Prepare Free Practice Tests: https://www.testvalid.com/NCP-US-6.5-exam-collection.html
Reliable NCP-US-6.5 Dumps Questions Available as Web-Based Practice Test Engine: https://drive.google.com/open?id=1BleKiCJIssRkTjsyEUNMEf8lxozmaZds