Nutanix NCP-US-6.10 Real Exam Questions Guaranteed Updated Dump from ExamDumpsVCE [Q18-Q39]

NEW QUESTION 18
Question:
Which statement is true regarding Self-Service Restore?

Supports 15 minute snapshots.

Does not require NGT on the VM.

Supports Windows and Linux.

Supported with a Starter license.

NEW QUESTION 19
Which workload type describes I/O sizes for read and write operations that are less than or equal to 16 KB while file sizes are equal to 10 MB or more?

Sequential

Asynchronous

Random

Default

The workload type that describes I/O sizes for read and write operations that areless than or equal to 16 KB while file sizes are10 MB or moreisRandom. In Nutanix Files, workload types are used to optimize share performance based on I/O patterns. Small I/O sizes (#16 KB) indicate a random access pattern, as opposed to sequential, even if the files themselves are large (#10 MB). This is common in workloads like databases or virtual desktops, where small, non-contiguous I/O operations are performed on larger files.
TheNutanix Unified Storage Administration (NUSA)course states, “A Random workload type in Nutanix Files is characterized by small I/O sizes, typically 16 KB or less, regardless of file size, as it reflects random access patterns rather than sequential ones.” The Random workload type optimizes the share for such patterns by adjusting caching, prefetching, and data placement to handle frequent small I/O operations efficiently, even when the files are large.
TheNutanix Certified Professional – Unified Storage (NCP-US)study guide further elaborates that
“workloads with I/O sizes of 16 KB or less, even on large files (e.g., 10 MB or more), are classified as Random, as the small I/O size indicates non-sequential access patterns.” Large file sizes do not necessarily imply sequential I/O; the I/O size itself determines the workload type, and 16 KB or less is typical of random access.
The other options are incorrect:
* Sequential: Sequential workloads involve larger I/O sizes (typically >64 KB) and contiguous access patterns, such as those seen in media streaming or backups, not small I/O sizes like 16 KB or less.
* Asynchronous: Asynchronous is not a workload type in Nutanix Files; it may refer to replication or I/O handling methods but is not relevant here.
* Default: The Default workload type applies a balanced configuration but does not specifically optimize for small I/O sizes like the Random type does.
The NUSA course documentation emphasizes that “I/O sizes of 16 KB or less, even with large file sizes, indicate a Random workload type in Nutanix Files, ensuring optimal performance for random access patterns.” References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: “Understanding workload types based on I/O patterns.” Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: “Defining workload types for Nutanix Files shares.” Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: “Workload type definitions for share optimization.”

NEW QUESTION 20
An administrator needs to create a volume group (VG) that will host highly sensitive data. These two requirements must be met:
* The VG must be accessible only by the OS where the data is going to be used by the application
* The access needs to be secured with an additional security login
Which three features or settings will help the administrator meet those requirements? (Choose two.)

CHAP authentication needs to be setup for that Volume Group.

On-the-wire encryption must be enabled for all iSCSI traffic.

All CVMs must have RDMA-capable NICs to facilitate direct peer-to-peer communication.

The VG configuration must contain only the IQN of the client OS where the application runs.

NEW QUESTION 21
An administrator has an existing four-node Nutanix cluster at a primary site with three FSVM instances deployed. They want to configure Smart DR on a five-node Nutanix cluster at the recovery site.
How many FSVMs should be deployed on the recovery site for Smart DR?

1

2

3

4

NEW QUESTION 22
An administrator is tasked with upgrading Objects Manager to the latest release that came out earlier in the week. The administrator has navigated to the LCM page in Prism Central and does not see the latest version of Objects Manager as an available upgrade. What is the likely reason the administrator does not see the current release of Objects Manager as an available upgrade?

An LCM inventory has not been performed

The administrator is logged in as local admin rather than a domain admin

The administrator needs to perform the upgrade through Prism Element

Prism Central needs to be scaled out

The administrator is attempting to upgrade Objects Manager (a component of Nutanix Objects) using Prism Central’s Lifecycle Manager (LCM) but does not see the latest version, which was released earlier in the week (prior to June 05, 2025). The most likely reason is thatan LCM inventory has not been performed. LCM requires an inventory operation to check for available updates by querying Nutanix’s external repositories or a dark site server (if configured), and without this step, the latest version of Objects Manager will not appear in the LCM page.
TheNutanix Unified Storage Administration (NUSA)course states, “Before upgrading components like Objects Manager via LCM, an inventory must be performed in Prism Central to retrieve the latest available versions from Nutanix repositories.” The inventory process updates the LCM catalog with the latest software versions, including Objects Manager, ensuring that the administrator can see and select the new release for upgrade. If the inventory has not been run recently, LCM will only show versions that were available during the last inventory, which may not include the latest release from earlier in the week.
TheNutanix Certified Professional – Unified Storage (NCP-US)study guide further elaborates that “a common reason for missing the latest component versions in LCM is the failure to perform an inventory; administrators must run an LCM inventory to ensure the latest versions, such as new releases of Objects Manager, are available for upgrade.” Since the latest version was released recently, an inventory is necessary to refresh the LCM catalog.
The other options are incorrect:
* The administrator is logged in as local admin rather than a domain admin: The issue is not related to the type of admin account (local vs. domain). Both local and domain admins can perform LCM inventories and upgrades if they have the necessary permissions, and there is no indication of a permission error.
* The administrator needs to perform the upgrade through Prism Element: LCM upgrades for Nutanix Objects components, including Objects Manager, are performed through Prism Central, not Prism Element, as Prism Central provides centralized management for such operations.
* Prism Central needs to be scaled out: Scaling out Prism Central (e.g., adding more VMs) is not required to see available upgrades in LCM. The issue is related to the inventory process, not Prism Central’s scale.
The NUSA course documentation emphasizes that “running an LCM inventory is a critical step to ensure the latest versions of components like Objects Manager are visible in Prism Central for upgrades, especially for recent releases.” References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Lifecycle Management: “Performing LCM inventory for component upgrades.” Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Topic 1: Deploy and Upgrade Nutanix Unified Storage, Subtopic: “LCM inventory process for Nutanix Objects upgrades.” Nutanix Documentation (https://www.nutanix.com), LCM Administration Guide: “Running inventory to check for available upgrades.”

NEW QUESTION 23
An administrator has determined that adding File Server VMs to the cluster will provide more resources.
What must the administrator validate so that the new File Server VMs can be added?

Ensure network ports are available.

Sufficient nodes in the cluster is greater than current number of FSVMs.

Sufficient storage container space is available to host the volume groups.

Ensure Files Analytics is installed.

Comprehensive and Detailed Explanation from Nutanix Unified Storage (NCP-US) and Nutanix Unified Storage Administration (NUSA) course documents:
In the context of expanding Nutanix Files (which is the file services capability of Nutanix Unified Storage), adding additionalFile Server VMs (FSVMs)to the cluster allows the file service to scale out and provide more resources for file services workloads, including performance and capacity improvements.
The Nutanix Files architecture involves deploying FSVMs that are distributed across the cluster nodes. Each FSVM handles file protocol operations and interacts with the underlying Nutanix Distributed Storage Fabric (DSF).
Here’s what’s critical when adding new FSVMs:
* Sufficient Cluster Nodes Requirement:The Nutanix Unified Storage Administration (NUSA) course emphasizes that thenumber of FSVMs cannot exceed the number of physical nodes in the cluster.
This is because each FSVM is deployed as a VM on a physical node, and Nutanix best practices require that FSVMs be spread out evenly across available nodes for performance, load balancing, and resiliency. Therefore, you must ensure:
“The number of nodes in the cluster must be greater than or equal to the number of FSVMs you plan to deploy.” This ensures that FSVMs are properly balanced and have the physical resources they need for optimal operation.
* Network Ports:While ensuring that appropriate network ports are configured is important for the operation of Nutanix Files (including communication with clients via SMB/NFS and integration with Prism), it isnotthe gating factor for adding new FSVMs. The critical factor is theavailable cluster nodes.
* Storage Container Space:Storage container space is also essential for file data storage, but this is not a direct requirement when simply adding FSVMs. FSVMs use the existing DSF storage, and as long as there is available storage capacity overall, adding FSVMs does not require validating specific volume group space.
* Files Analytics:Files Analytics is an optional feature that provides advanced analytics for file shares, such as usage patterns and security insights. It isnot requiredto add new FSVMs.
* Design Best Practices:In the NUSA course, administrators are taught to always validate the number of cluster nodes first before deploying additional FSVMs. This ensures that the cluster can accommodate the new FSVMs without causing resource contention or violating best practice guidelines for balanced and resilient file server deployments.
* Resilience and High Availability:Because FSVMs are distributed across the physical cluster nodes, having more nodes than FSVMs ensures that if a node fails, the FSVMs can failover to other available nodes. This helps maintain the high availability of file services.
In summary, while other factors like network ports, container space, and analytics capabilities play roles in the broader operation and management of Nutanix Files, theabsolute requirement for adding FSVMs is ensuring that there are enough cluster nodes to host them. This ensures compliance with design best practices for scalability and resilience, as emphasized in the official Nutanix training courses.

NEW QUESTION 24
How many IP addresses are required by the client network when deploying Nutanix Files?

One additional IP address as the number of FSVMs

The same number of IP addresses as the number of FSVM nodes

One less IP address as the number of FSVMs

Twice as many IP addresses as the number of FSVMs

When deploying Nutanix Files, the client network requiresone additional IP address than the number of File Server Virtual Machines (FSVMs). Nutanix Files uses a distributed architecture where each FSVM handles file services for clients via protocols like SMB or NFS. The client network is used for client-facing traffic, and it requires one IP address per FSVM plus an additional virtual IP address (VIP) that serves as the primary access point for clients.
According to theNutanix Unified Storage Administration (NUSA)course, “Nutanix Files requires one IP address per FSVM on the client network for client communication, plus one additional VIP that provides a unified endpoint for accessing file shares.” The VIP is load-balanced across the FSVMs, ensuring high availability and seamless client access even if an FSVM fails.
TheNutanix Certified Professional – Unified Storage (NCP-US)study guide further clarifies that “the client network for Nutanix Files must be configured with one IP address for each FSVM and an additional VIP, resulting in a total of N+1 IP addresses, where N is the number of FSVMs.” For example, a deployment with three FSVMs requires four IP addresses: three for the FSVMs and one for the VIP.
The other options are incorrect:
* The same number of IP addresses as the number of FSVM nodes: This does not account for the additional VIP required for client access, which is essential for load balancing and failover.
* One less IP address as the number of FSVMs: This is not feasible, as each FSVM requires its own IP address, and the VIP adds an additional requirement.
* Twice as many IP addresses as the number of FSVMs: This overestimates the IP address needs, as only one additional VIP is required, not double the number of FSVMs.
The NUSA course documentation emphasizes that “the client network VIP simplifies client access to Nutanix Files by providing a single IP address that abstracts the underlying FSVMs, requiring one additional IP address beyond the FSVM count.” References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: “Network configuration for client access and VIP setup.” Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Topic 1: Deploy and Upgrade Nutanix Unified Storage, Subtopic: “Nutanix Files client network IP address requirements.” Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: “Client network configuration for Nutanix Files.”

NEW QUESTION 25
An administrator would like to protect an object store from a single node or two-drive failure. What are the requirements for enabling this level of resiliency on a newly-deployed object store?

Multi-cluster option must be disabled for the object store.

Each node in the dense node platform requires 20 or more HDDs.

Cluster is comprised of a minimum of seven nodes.

New storage container is created for the object store.

To protect a Nutanix Objects store from a single node or two-drive failure, the cluster must be comprised of a minimum of seven nodes. Nutanix Objects uses erasure coding to provide resiliency, distributing data and parity fragments across nodes to ensure fault tolerance. To withstand a single node failure or a two-drive failure, a specific number of nodes is required to maintain data availability and rebuild capability.
TheNutanix Unified Storage Administration (NUSA)course states, “Nutanix Objects requires a minimum of seven nodes to ensure resiliency against a single node failure or a two-drive failure, using erasure coding to distribute data and parity across the cluster.” This configuration typically uses an erasure coding scheme like
4+2 or 5+2 (data + parity fragments), which requires at least six nodes for data distribution and an additional node to handle failures, totaling seven nodes.
TheNutanix Certified Professional – Unified Storage (NCP-US)study guide further elaborates that “to achieve resiliency against a single node or two-drive failure in Nutanix Objects, the cluster must have at least seven nodes to support the erasure coding configuration needed for this level of fault tolerance.” This ensures that even if one node fails or two drives are lost, the remaining nodes have sufficient data and parity fragments to reconstruct the lost data.
The other options are incorrect:
* Multi-cluster option must be disabled for the object store: The multi-cluster option is not relevant to resiliency within a single Nutanix Objects deployment. It pertains to managing multiple clusters, not erasure coding or fault tolerance.
* Each node in the dense node platform requires 20 or more HDDs: There is no requirement for 20 or more HDDs per node to achieve this level of resiliency. Resiliency depends on the number of nodes and erasure coding, not the number of drives per node.
* New storage container is created for the object store: While Nutanix Objects uses storage containers, creating a new container is not a requirement for enabling resiliency. Resiliency is determined by the cluster configuration and erasure coding settings.
The NUSA course documentation highlights that “a minimum of seven nodes ensures Nutanix Objects can maintain data availability and rebuild data in the event of a single node or two-drive failure, leveraging erasure coding for resiliency.” References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Objects: “Configuring resiliency for Nutanix Objects.” Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: “Nutanix Objects resiliency and erasure coding requirements.” Nutanix Documentation (https://www.nutanix.com), Nutanix Objects Administration Guide: “Cluster sizing for resiliency in Nutanix Objects.”

NEW QUESTION 26

Question:
An administrator is attempting to connect to a newly created 1TiB Volume Group on a Windows Server 2022 VM.
* In the iSCSI Initiator Properties >Discovery tab, the Data Services IP (DSIP) appears as a target portal.
* But in theTargets tab, the Volume Group (LUN) is not listed as a discovered target.
What is the most likely cause of this?

The Windows VM IQN was not added to the client allowlist.

The Volume Group is too large for Windows to recognize.

The Windows VM needs to be rebooted to recognize the Volume Group.

The iSCSI initiator service is not started on the Windows VM.

NEW QUESTION 27
An administrator is setting a Windows client to access a Volume Group (VG) served by a Nutanix cluster.
Which configuration items should the administrator take from the cluster? (Choose two.)

The cluster’s data services IP (DSIP)

The cluster’s fully qualified domain name (FQDN)

The IPs of all cluster CVMs IP

The VG name

NEW QUESTION 28
A company is managing two Nutanix clusters between two different availability zones: one on-prem and one running in the public cloud (NC2). The company is evaluating Nutanix Files and is looking for a solution that supports: 15-minute RPO or less, guided DR process, and minimal operations at failover time. Which data protection strategy should be considered?

Smart DR

Protection Domain

Smart Sync

Cloud Connect

To meet the requirements of a15-minute RPO (Recovery Point Objective) or less, aguided DR (Disaster Recovery) process, andminimal operations at failover timefor Nutanix Files across two Nutanix clusters (on-prem and in the public cloud via NC2), the company should considerSmart DR. Smart DR is a disaster recovery feature specifically designed for Nutanix Files, enabling replication of file shares between primary and recovery sites with low RPOs, guided failover processes, and automated recovery workflows.
TheNutanix Unified Storage Administration (NUSA)course states, “Smart DR for Nutanix Files supports replication with an RPO as low as 15 minutes, provides a guided disaster recovery process through Prism Central, and minimizes operations at failover by automating client redirection and share activation.” Smart DR uses asynchronous replication to copy file share data to the recovery site, allowing for a 15-minute RPO by scheduling replication at 15-minute intervals. The guided DR process is facilitated through Prism Central’s UI, which provides step-by-step workflows for failover and failback. Additionally, Smart DR automates client redirection by leveraging AD and DNS updates, minimizing manual operations during failover.
TheNutanix Certified Professional – Unified Storage (NCP-US)study guide further elaborates that “Smart DR is ideal for Nutanix Files deployments across availability zones, such as on-prem and NC2, supporting RPOs as low as 15 minutes, guided recovery workflows, and automated failover with minimal operational overhead.” This makes Smart DR the best match for the company’s requirements, as it addresses all three criteria effectively.
The other options are incorrect:
* Protection Domain: Protection Domains are used for VM-level replication and disaster recovery in Nutanix, not for Nutanix Files. They also typically have higher RPOs (e.g., 1 hour) and are not designed for file share recovery.
* Smart Sync: Smart Sync is not a Nutanix feature; it may refer to third-party tools or unrelated functionalities and is not applicable here.
* Cloud Connect: Cloud Connect is a feature for backing up or replicating data to public cloud providers, but it is not specific to Nutanix Files and does not support a 15-minute RPO or guided DR processes for file shares.
The NUSA course documentation highlights that “Smart DR is the recommended data protection strategy for Nutanix Files in multi-site environments, offering low RPOs, guided DR workflows, and automated failover to minimize downtime and operational complexity.” References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: “Smart DR for disaster recovery across availability zones.” Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: “Smart DR capabilities for Nutanix Files.” Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: “Smart DR setup for multi-site file share protection.”

NEW QUESTION 29
Where are standard tiering policies managed?

Prism Central Admin Dashboard

Prism Element Data Protection Dashboard

Nutanix Files Console

Nutanix Data Lens

Standard tiering policies for Nutanix Unified Storage are managed inNutanix Data Lens. Nutanix Data Lens is a cloud-based service that provides data lifecycle management, analytics, and tiering capabilities for Nutanix Files and Objects. It enables administrators to define and manage tiering policies to move data between different storage tiers (e.g., from Nutanix storage to cloud storage like AWS S3) based on access patterns, age, or other criteria.
According to theNutanix Unified Storage Administration (NUSA)course, “Nutanix Data Lens is used to configure and manage standard tiering policies for Nutanix Files and Objects, allowing data to be tiered to cost-effective storage based on predefined rules.” This includes setting policies to archive infrequently accessed data to cloud storage, optimizing storage costs while maintaining accessibility.
TheNutanix Certified Professional – Unified Storage (NCP-US)study guide further clarifies that “Data Lens provides a centralized interface for managing tiering policies, enabling automated data movement to secondary storage tiers, such as cloud-based object stores.” Administrators can access Data Lens to define rules for data tiering, monitor tiering activities, and ensure compliance with organizational data management requirements.
The other options are incorrect:
* Prism Central Admin Dashboard: Prism Central is used for cluster management, monitoring, and orchestration but does not provide specific interfaces for managing tiering policies.
* Prism Element Data Protection Dashboard: Prism Element focuses on individual cluster management and data protection tasks (e.g., snapshots, replication), not tiering policies.
* Nutanix Files Console: The Nutanix Files Console is used for configuring and managing file servers and shares, but tiering policies are managed externally through Data Lens.
The NUSA course documentation emphasizes that “Nutanix Data Lens integrates with Nutanix Files to provide tiering capabilities, allowing administrators to manage data placement across on-premises and cloud storage tiers seamlessly.” References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Data Lens: “Configuring tiering policies for Nutanix Files and Objects.” Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: “Data lifecycle management with Nutanix Data Lens.” Nutanix Documentation (https://www.nutanix.com), Nutanix Data Lens Guide: “Managing standard tiering policies.”

NEW QUESTION 30
An administrator has been tasked with troubleshooting a storage performance problem for a large database VM with the following configuration:
* 16 vCPU
* 64 GB RAM
* One 50 GB native AHV virtual disk hosting the guest OS
* Six 500 GB virtual disks containing database files connecting via iSCSI to a Nutanix volume group
* One NIC for client connectivity
* One NIC for iSCSI connectivity
In the course of investigating the problem, the administrator determines that the issue is isolated to large block-size I/O operations. What step should the administrator take to improve performance for the VM?

Add an additional NIC for iSCSI connectivity and enable MPIO

Add additional virtual disks to the volume group

Increase the iSCSI adapter maximum transfer length

Locate the iSCSI NIC on the same VLAN as the cluster DSIP

The performance issue for the database VM is related to large block-size I/O operations over iSCSI, which connects to a Nutanix volume group. The VM has a dedicated NIC for iSCSI traffic, but a single NIC can become a bottleneck for large I/O operations, especially for a high-performance workload like a database. To improve performance, the administrator shouldadd an additional NIC for iSCSI connectivity and enable MPIO (Multipath I/O). This approach allows the VM to use multiple network paths for iSCSI traffic, increasing throughput and reducing latency for large block-size I/O operations.
TheNutanix Unified Storage Administration (NUSA)course states, “For high-performance workloads using Nutanix Volumes over iSCSI, enabling MPIO with multiple NICs on the VM can significantly improve I/O performance, especially for large block-size operations.” MPIO allows the VM to establish multiple iSCSI sessions to the Nutanix volume group, distributing I/O traffic across the available NICs and Controller Virtual Machines (CVMs) in the cluster. This is particularly effective for database workloads, which often involve large sequential I/O operations.
TheNutanix Certified Professional – Unified Storage (NCP-US)study guide further elaborates that “adding a second NIC for iSCSI traffic and configuring MPIO ensures load balancing and failover for iSCSI sessions, optimizing performance for VMs with high I/O demands, such as databases.” By adding another NIC, the VM can establish additional iSCSI paths to the volume group’s iSCSI Data Services IP (DSIP), leveraging the cluster’s distributed architecture to handle large block-size I/O more efficiently.
The other options are incorrect:
* Add additional virtual disks to the volume group: Adding more virtual disks does not address the network bottleneck caused by a single iSCSI NIC and may not improve performance for large block- size I/O operations.
* Increase the iSCSI adapter maximum transfer length: Adjusting the maximum transfer length (MTU) might help with network efficiency, but it does not address the fundamental issue of a single NIC being a bottleneck for large I/O operations. MPIO with multiple NICs is a more effective solution.
* Locate the iSCSI NIC on the same VLAN as the cluster DSIP: While placing the iSCSI NIC on the same VLAN as the DSIP can reduce latency by avoiding inter-VLAN routing, the primary issue here is the single NIC bottleneck, not VLAN configuration. MPIO with multiple NICs provides a better performance improvement.
The NUSA course documentation emphasizes that “for VMs with large block-size I/O requirements, such as databases, using MPIO with multiple iSCSI NICs ensures optimal performance by distributing traffic across multiple paths to the Nutanix volume group.” References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Volumes: “Optimizing iSCSI performance with MPIO for high-performance workloads.” Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Topic 4: Troubleshoot Nutanix Unified Storage, Subtopic: “Performance troubleshooting for iSCSI-based VMs.” Nutanix Documentation (https://www.nutanix.com), Nutanix Volumes Administration Guide: “Configuring MPIO for iSCSI performance optimization.”

NEW QUESTION 31
An administrator is required to provide a summary of metrics to the Security team.
The entity information being asked for by the Security team is as follows:
* Total folders where permissions are tracked
* Size of those folders
* Total unique users
* Total unique groups
In which product and dashboard would the administrator find all the requested data?

Data Lens – Recommendations

File Analytics – Top Users

Data Lens Footprint Widget

File Analytics File Operations

NEW QUESTION 32
An administrator has configured a volume-group with four vDisks and needs them to be load-balanced across multiple CVMs. The volume-group will be directly connected to the VM. Which task must the administrator perform to meet this requirement?

Enable load-balancing for the volume-group using ncli

Select multiple initiator IQNs when creating the volume-group

Select multiple iSCSI adapters within the VM

Enable load-balancing for the volume-group using acli

To load-balance a volume-group with four vDisks across multiple Controller Virtual Machines (CVMs) for a VM using Nutanix Volumes, the administrator mustenable load-balancing for the volume-group using acli.
Nutanix Volumes supports iSCSI-based block storage, and load-balancing ensures that I/O traffic from the VM is distributed across multiple CVMs, improving performance and scalability. The acli (AHV Command- Line Interface) is the tool used to configure this setting for volume-groups.
TheNutanix Unified Storage Administration (NUSA)course states, “Nutanix Volumes supports load- balancing of iSCSI traffic across CVMs, which can be enabled for a volume-group using the acli command to ensure optimal performance for VMs.” The specific command in acli allows the administrator to enable load- balancing, distributing the iSCSI sessions for the volume-group’s vDisks across the available CVMs in the cluster. This ensures that the VM’s I/O requests are handled by multiple CVMs, preventing any single CVM from becoming a bottleneck.
TheNutanix Certified Professional – Unified Storage (NCP-US)study guide further elaborates that “to enable load-balancing for a volume-group, the administrator can use the acli vg.update command with the enable_load_balancing=true option, ensuring that iSCSI traffic is distributed across CVMs for better performance.” This is particularly important for volume-groups with multiple vDisks, as in this case with four vDisks, to optimize I/O distribution.
The other options are incorrect:
* Enable load-balancing for the volume-group using ncli: The ncli (Nutanix Command-Line Interface) is used for cluster-wide configurations, but load-balancing for volume-groups is specifically managed via acli, which is tailored for AHV and volume-group operations.
* Select multiple initiator IQNs when creating the volume-group: Initiator IQNs (iSCSI Qualified Names) are used to authenticate and connect initiators to the volume-group, but selecting multiple IQNs does not enable load-balancing across CVMs.
* Select multiple iSCSI adapters within the VM: Configuring multiple iSCSI adapters in the VM is a client-side configuration that can help with multipathing, but it does not control load-balancing across CVMs, which is a cluster-side setting.
The NUSA course documentation highlights that “enabling load-balancing via acli for a volume-group ensures that iSCSI traffic is distributed across multiple CVMs, optimizing performance for VMs with direct- attached volumes.” References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Volumes: “Configuring load- balancing for volume-groups.” Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: “Nutanix Volumes load-balancing with acli.” Nutanix Documentation (https://www.nutanix.com), Nutanix Volumes Administration Guide: “Enabling load- balancing for volume-groups using acli.”

NEW QUESTION 33
Question:
Which two URLs must Prism Central have access to, in an online deployment, for a Nutanix Objects server?
(Choose two.)

download.nutanix.com

portal.nutanix.com

kubernetes.io

docker.io

NEW QUESTION 34
An administrator notices the option to upgrade Objects Manager is disabled. What is the most likely reason?

Objects Service upgrade previously failed

Provided access keys are wrong

Objects browser is not available

Prism Element upgrade previously failed

The administrator is attempting to upgrade Objects Manager, a component of Nutanix Objects, but notices that the upgrade option is disabled in Prism Central’s Lifecycle Manager (LCM). The most likely reason is that an **Objects Service upgrade previously failed**. Nutanix Objects consists of multiple components, including Objects Manager and Objects Service, and LCM enforces dependencies between these components during upgrades. If a prior upgrade of Objects Service failed, LCM will disable the upgrade option for Objects Manager until the issue with Objects Service is resolved.
The **Nutanix Unified Storage Administration (NUSA)** course states, “LCM may disable the upgrade option for Objects Manager if a dependency, such as Objects Service, has a failed upgrade, as Nutanix Objects components must be upgraded in a specific order to maintain system stability.” Objects Service is a core component of Nutanix Objects that handles the underlying object storage operations, while Objects Manager provides management and orchestration. A failed Objects Service upgrade can leave the system in an inconsistent state, preventing further upgrades of related components like Objects Manager until the failure is resolved.
The **Nutanix Certified Professional – Unified Storage (NCP-US)** study guide further elaborates that “a common reason for a disabled upgrade option in LCM for Objects Manager is a previous failure in upgrading Objects Service, which must be addressed by troubleshooting the failed upgrade and ensuring all dependencies are met.” The administrator should check the LCM logs for details of the failed Objects Service upgrade, resolve the issue (e.g., by addressing network connectivity, disk space, or version compatibility problems), and then retry the upgrade process.
The other options are incorrect:
– **Provided access keys are wrong**: Access keys are relevant for S3-compatible API access to Nutanix Objects buckets, not for LCM upgrades of Objects Manager.
– **Objects browser is not available**: The “Objects browser” is not a component or requirement for upgrading Objects Manager; this term may refer to the UI for browsing objects, which is unrelated to LCM upgrades.
– **Prism Element upgrade previously failed**: A failed Prism Element upgrade might affect cluster-level operations, but it is less likely to directly disable the Objects Manager upgrade option, as Objects Manager upgrades are managed through Prism Central and depend on Objects Service, not Prism Element.
The NUSA course documentation emphasizes that “a failed Objects Service upgrade is a frequent cause of disabled upgrade options for Objects Manager in LCM, requiring administrators to resolve the failure before proceeding.” References:
– Nutanix Unified Storage Administration (NUSA) Course, Section on Lifecycle Management:
“Troubleshooting disabled upgrade options in LCM.”
– Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Topic 4: Troubleshoot Nutanix Unified Storage, Subtopic: “Diagnosing upgrade issues for Nutanix Objects components.”
– Nutanix Documentation (https://www.nutanix.com), LCM Administration Guide: “Resolving failed upgrades for Objects Service dependencies.”
—

NEW QUESTION 35
Refer to the exhibit.

In the exhibit, what does “AIXforyou@123” represent?

Volume Group

CHAP Secret

Volume Name

iSCSI Host

NEW QUESTION 36
An administrator would like to load balance an SMB share across multiple FSVMs.
What feature should the administrator enable to accomplish this?

Distributed

Disaster Recovery

Multiple Copies

High Availability

NEW QUESTION 37
An administrator would like to get notified by email of unusual behavior related to permission changes on their corporate file shares. How would the administrator configure File Analytics to receive notifications in a timely fashion?

Create an Alert Policy

Configure Events Quotas

Define Anomaly Rules

Set Ransomware Email Recipient

To receive email notifications about unusual behavior related to permission changes on corporate file shares, the administrator shoulddefine anomaly rulesin Nutanix File Analytics. File Analytics is a monitoring and analytics tool for Nutanix Files that provides visibility into file share activities, including permission changes, access patterns, and potential security threats. Anomaly rules allow administrators to detect and be notified of unusual or suspicious activities, such as unexpected permission modifications.
TheNutanix Unified Storage Administration (NUSA)course explains that File Analytics includes an anomaly detection feature that uses machine learning to identify deviations from normal behavior. The course states, “Administrators can define anomaly rules in File Analytics to monitor specific activities, such as permission changes, and configure email notifications for timely alerts.” By setting up anomaly rules, the administrator can specify criteria for permission-related events and enable email alerts to be sent when such anomalies are detected.
TheNutanix Certified Professional – Unified Storage (NCP-US)study guide further elaborates that “File Analytics anomaly rules can be customized to track permission changes, excessive file access, or other suspicious activities, with notifications sent via email to ensure timely response.” This makes anomaly rules the most appropriate method for addressing the administrator’s requirement.
The other options are not suitable:
* Create an Alert Policy: Alert policies in Nutanix are typically used for system-level events (e.g., hardware failures or cluster issues) managed through Prism Central, not for file share-specific activities like permission changes.
* Configure Events Quotas: Events quotas are used to manage resource limits or thresholds, not to monitor or notify about specific activities like permission changes.
* Set Ransomware Email Recipient: This option is specific to ransomware detection in File Analytics, which focuses on identifying file encryption or mass file modifications, not permission changes.
The NUSA course documentation notes that “File Analytics anomaly rules provide granular control over monitoring file share activities, with email notifications ensuring administrators are promptly informed of potential security issues like unauthorized permission changes.” References:
Nutanix Unified Storage Administration (NUSA) Course, Section on File Analytics: “Configuring anomaly rules for monitoring and notifications.” Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Topic 3: Analyze and Monitor Nutanix Unified Storage, Subtopic: “File Analytics and anomaly detection.” Nutanix Documentation (https://www.nutanix.com), Nutanix File Analytics Guide: “Setting up anomaly rules and email notifications.”

NEW QUESTION 38
An administrator has files located in shares, buckets, and volumes. In which environment can File Analytics be used to collect metadata?

Kerberos authenticated S3

Kerberos authenticated NFS v4.0

CHAP authenticated iSCSI

AD authenticated SMB

NEW QUESTION 39
Question:
When naming an Object Store instance, which two naming rules must be followed? (Choose two.)

Must be a minimum of three and a maximum of 32 characters long.

Must begin with a number and end with a letter or number.

Must begin with a letter, and end with a letter or number.

Must be unique across all existing object store names in Objects.