[May 08, 2026] Download Free Nutanix NCP-US-6.10 Real Exam Questions [Q58-Q81]

[May 08, 2026] Download Free Nutanix NCP-US-6.10 Real Exam Questions

Pass Your Exam With 100% Verified NCP-US-6.10 Exam Questions

NEW QUESTION # 58
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?

• A. Sequential
• B. Asynchronous
• C. Random
• D. Default

Answer: C

Explanation:
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 # 59
Question:
An administrator needs to configure Nutanix Objects in AHV.
Which IP range must be available for this task?

• A. 192.168.1.0/24
• B. 10.100.1.0/24
• C. 10.100.0.0/16 and 10.200.0.0/16
• D. 172.100.0.0/16 and 172.200.0.0/16

Answer: C

Explanation:
When deploying Nutanix Objects, internal communication and data flow between Object services are isolated usinginternal overlay IP rangesto avoid collisions with existing customer networks.
The NCP-US and NUSA course materials state:
"Nutanix Objects requires two separate internal IP address ranges: 10.100.0.0/16 and 10.200.0.0/16. These ranges are used exclusively for internal communication within the Nutanix Objects deployment, such as for object metadata, S3 gateway, and load balancing services."
* These10.x.x.x rangesmust not overlap with existing client or management networks.
* They provide fully isolated internal object service communication.

NEW QUESTION # 60
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?

• A. Select multiple iSCSI adapters within the VM
• B. Enable load-balancing for the volume-group using ncli
• C. Enable load-balancing for the volume-group using acli
• D. Select multiple initiator IQNs when creating the volume-group

Answer: C

Explanation:
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 # 61
Which share workload type should be configured to support workloads with small I/O?

• A. Sequential
• B. Random
• C. Default
• D. Compression

Answer: B

Explanation:
To support workloads with small I/O operations in Nutanix Files, the share should be configured with the Randomworkload type. Small I/O operations, typically less than 64 KB, are characteristic of random I/O patterns, which are common in workloads like databases, virtual desktops, or applications with frequent small read/write operations. Nutanix Files allows administrators to optimize share performance by selecting a workload type that aligns with the I/O pattern.
TheNutanix Unified Storage Administration (NUSA)course states, "Nutanix Files supports configuring shares with a Random workload type to optimize performance for small I/O operations, which are typical of random access patterns." The Random workload type adjusts internal optimizations, such as caching and data placement, to better handle the characteristics of small, non-sequential I/O operations, improving performance for such workloads.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further elaborates that "the Random workload type in Nutanix Files is designed for shares hosting applications with small I/O sizes, ensuring efficient handling of random read and write operations." This contrasts with sequential workloads, which involve larger, contiguous I/O operations, such as those seen in media streaming or backups.
The other options are incorrect:
* Sequential: The Sequential workload type is optimized for large, contiguous I/O operations, not small I
/O, making it unsuitable for this scenario.
* Compression: Compression is a data reduction feature, not a workload type, and does not directly address I/O performance optimization.
* Default: The Default workload type applies a balanced configuration but does not specifically optimize for small I/O operations like the Random type does.
The NUSA course documentation emphasizes that "configuring a share with the Random workload type ensures optimal performance for workloads with small I/O, aligning with the random access patterns of such applications." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: "Configuring workload types for share optimization." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Workload type configuration for Nutanix Files shares." Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: "Setting workload types for share performance."

NEW QUESTION # 62
Question:
What should be enabled for Windows clients when using the SMB protocol in a Nutanix Files deployment?

• A. Distributed File System
• B. Internet Information Services
• C. Automatic Windows Update
• D. Zettabyte File System

Answer: A

Explanation:
SMB (Server Message Block)protocol is the foundation for file sharing in Windows environments. In a Nutanix Files deployment, enablingDistributed File System (DFS)on Windows clients enhances SMB functionality by:
Allowingnamespace-based accessto shares.
Providingclient failover and load balancingwhen used with Nutanix Files SMB shares.
According to the NUSA course:
"For Windows clients accessing Nutanix Files via SMB, enabling Distributed File System (DFS) ensures they can dynamically discover and connect to the most optimal FSVM, even during failovers. DFS enhances resiliency and performance by maintaining a consistent namespace." The other options:
Zettabyte File System- not relevant for Windows or SMB.
Internet Information Services- web server technology, not related to SMB shares.
Automatic Windows Update- not directly tied to SMB access.
Thus,enabling Distributed File System (DFS)on Windows clients ensures smooth SMB integration and high availability.

NEW QUESTION # 63
Question:
A user with Edit Buckets permission has been tasked with deleting old Nutanix Objects buckets created by a former employee.
Why is this user unable to execute the task?

• A. User is only able to delete buckets assigned to them.
• B. The buckets don't have Object Versioning enabled.
• C. User does not have the Delete Buckets permission.
• D. The buckets don't have a Lifecycle Policy associated.

Answer: C

Explanation:
In Nutanix Objects,bucket management permissionsare granularly controlled. TheEdit Bucketspermission allows a user tomodify bucket configurations(such as policy changes, tagging, and settings), but it doesnot grant the ability todeletethe bucket.
From the NUSA training:
"The Delete Buckets permission is separate from Edit Buckets. Users with Edit Buckets can change configurations but cannot remove the bucket itself." Thus, the user's inability to delete buckets stems fromlacking the explicit Delete Buckets permission.

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

• A. download.nutanix.com
• B. portal.nutanix.com
• C. kubernetes.io
• D. docker.io

Answer: A,D

Explanation:
In the Nutanix Unified Storage architecture, Nutanix Objects is a service that leverages container-based deployment for its microservices architecture. When deploying Objects inonline mode, Prism Central (which orchestrates the deployment) needs todownloadthe container images and additional software artifacts directly from Nutanix and trusted external registries.
* download.nutanix.com:This is Nutanix's primary repository for all official Nutanix software artifacts, including Objects installation packages and associated dependencies. In the official NUSA deployment module, it states:
"Prism Central must be able to reach download.nutanix.com to retrieve Objects binary packages and installation files. This ensures that Objects components are properly deployed and integrated into the cluster environment."
* docker.io:Nutanix Objects uses containerized microservices (e.g., object metadata, S3 gateway) that are packaged as Docker images. The deployment processpulls these images directly from docker.io, which is the default container registry for Docker images. The NUSA course explicitly mentions:
"During the Objects deployment, container images are pulled from docker.io. Prism Central must have connectivity to docker.io to ensure all components of Objects are downloaded and deployed successfully."
* portal.nutanix.com and kubernetes.io:
* portal.nutanix.comis used for documentation and support but is not needed for direct deployment of Objects.
* kubernetes.iois also not required since Nutanix Objects uses its own container orchestration within the Nutanix platform, not Kubernetes from the internet.
Thus, for an online Objects deployment, themandatory external dependenciesare:
download.nutanix.com
docker.io

NEW QUESTION # 65
What is the maximum number of snapshots that can be configured for a Nutanix Files snapshot schedule?

• A. 0
• B. 1
• C. 2
• D. 3

Answer: D

Explanation:
The maximum number of snapshots that can be configured for a Nutanix Files snapshot schedule is100.
Nutanix Files supports snapshot schedules to automate the creation of point-in-time snapshots for file shares, which are useful for data protection, recovery, and backup purposes. The snapshot schedule defines how frequently snapshots are taken and how many are retained.
According to theNutanix Unified Storage Administration (NUSA)course, Nutanix Files allows administrators to configure snapshot schedules with a maximum retention of100 snapshotsper share. The course states, "Nutanix Files snapshot schedules can be configured to retain up to 100 snapshots, providing flexible data protection for file shares." This limit ensures that administrators can maintain a sufficient number of recovery points while managing storage efficiency.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide reinforces this by noting that
"the snapshot schedule for Nutanix Files supports a maximum of 100 snapshots per share, allowing for granular recovery options." Administrators can configure the frequency (e.g., hourly, daily) and retention period, but the total number of snapshots retained cannot exceed 100 per share.
The other options (25, 50, 75) underestimate the maximum snapshot limit for Nutanix Files, as the system supports up to 100 snapshots to accommodate various data protection needs.
References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: "Configuring snapshot schedules and retention policies." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Snapshot management for Nutanix Files." Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: "Snapshot schedules and maximum retention limits."

NEW QUESTION # 66
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?

• A. Locate the iSCSI NIC on the same VLAN as the cluster DSIP
• B. Add additional virtual disks to the volume group
• C. Add an additional NIC for iSCSI connectivity and enable MPIO
• D. Increase the iSCSI adapter maximum transfer length

Answer: C

Explanation:
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 # 67
What is a requirement for Smart DR?

• A. File servers may have different FSVM numbers at the primary and recovery sites.
• B. Primary and recovery file servers must have different domain names.
• C. The Files Manager must have only one file server.
• D. Primary and recovery file servers must support the same protocols.

Answer: D

Explanation:
A requirement forSmart DR(Disaster Recovery) in Nutanix Files is thatprimary and recovery file servers must support the same protocols. Smart DR is a feature that enables automated disaster recovery for Nutanix Files by replicating file shares between a primary site and a recovery site, ensuring business continuity in case of a failure.
According to theNutanix Unified Storage Administration (NUSA)course, "Smart DR requires that the primary and recovery file servers support the same file-sharing protocols (e.g., SMB, NFS) to ensure seamless failover and consistent client access." This ensures that clients can access the same shares with the same protocol after a failover, maintaining application compatibility and user experience.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further states that "Smart DR configurations mandate that the primary and recovery file servers are configured with identical protocol support to enable consistent replication and recovery of file shares." For example, if the primary file server uses SMB for Windows clients, the recovery file server must also support SMB.
The other options are incorrect:
* Primary and recovery file servers must have different domain names: Smart DR does not require different domain names. In fact, using the same domain name can simplify AD integration and client access during failover.
* File servers may have different FSVM numbers at the primary and recovery sites: While Smart DR allows flexibility in FSVM counts, it is not a requirement. The number of FSVMs can be the same or different based on site resources, but this is not mandated.
* The Files Manager must have only one file server: Nutanix Files Manager can manage multiple file servers, and Smart DR does not restrict the environment to a single file server.
The NUSA course documentation highlights that "Smart DR ensures protocol consistency between primary and recovery sites to support seamless failover, making protocol support a critical requirement for configuration." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: "Configuring Smart DR for disaster recovery." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Smart DR requirements and configuration." Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: "Smart DR setup and protocol requirements."

NEW QUESTION # 68
Question:
The administrator creates an S3 bucket as the backup target. While creating the Nutanix Objects endpoint to the newly created S3 bucket, the following error is observed:
"Method Not Allowed: An object from the object-lock enabled bucket can not be modified or deleted unless the retention period is elapsed." What is the most likely cause?

• A. Write Once Ready Many (WORM) is enabled on the S3 bucket.
• B. Object-Level permissions are incorrect for GET, HEAD, and PUT bucket-level permissions.
• C. The S3 bucket name is incorrect.
• D. The API key is not configured correctly.

Answer: A

Explanation:
The error message explicitly references anobject-lock enabled bucketand restrictions onmodifying/deleting objects. This points directly to theWORM (Write Once Read Many)feature being enabled on the S3 bucket.
WORM (Object Lock):
* Object Lock (also called WORM)prevents objects from being deleted or modifiedfor a retention period set by the bucket's policy.
* The error states:
"An object from the object-lock enabled bucket can not be modified or deleted unless the retention period is elapsed."
* This directly matches the behavior of an S3 bucket withWORM retention.
The other options:
* A. Bucket name incorrect: Would result in a "NoSuchBucket" or "Not Found" error, not "Method Not Allowed."
* C. Object-Level permissions: Insufficient permissions would cause "Access Denied" or "Forbidden," not WORM-specific errors.
* D. API key misconfiguration: Would typically produce authentication errors ("SignatureDoesNotMatch," etc.), not a WORM policy restriction.
The NUSA course discusses WORM behavior:
"If WORM is enabled on a bucket, objects cannot be deleted or modified until the retention period expires.
Attempting to do so will generate 'Method Not Allowed' errors."
Thus, the error here is directly caused byWORM retention(Object Lock) being active on the S3 bucket.

NEW QUESTION # 69
Question:
An administrator needs to move infrequently accessed data to lower-cost storage based on file type and owner, and automatically recall data if data access frequency has increased.
What should administrator do to satisfy these requirements?

• A. Configure Smart tiering in Files.
• B. Configure Advanced tiering in Data Lens.
• C. Create an SSR-enabled share in Files.
• D. Create a Lifecycle Rule in Objects Buckets tab.

Answer: A

Explanation:
Smart Tieringin Nutanix Files is a built-in feature that allows administrators toautomatically move infrequently accessed data(cold data) tolower-cost storage tiers(like NFS or S3-compatible storage). It also supportsautomatically recalling dataif it becomes hot (frequently accessed) again.
According to NUSA course details:
"Smart Tiering policies in Nutanix Files allow administrators to define rules based on file metadata (type, size, owner) and last access time. Cold data is tiered off to cheaper storage, and Files can recall the data if needed, ensuring transparent access for users." Key reasons why Smart Tiering is the solution:
* Automatically identifies cold data(based on access patterns).
* Moves cold data to external or cheaper storagetransparently.
* Re-hydrates dataautomatically if it becomes hot again, maintaining performance and user experience.
The other options:
Advanced tiering in Data Lens- Data Lens is for analytics and reporting, not for moving data.
Lifecycle Rules in Objects- manages data lifecycle for object buckets, not Files shares.
SSR (Self-Service Restore)- is for file recovery, not data tiering.
Thus, the administrator shouldconfigure Smart Tiering in Nutanix Filesto satisfy the requirement.

NEW QUESTION # 70
An administrator wants to provide access to users or to user groups to manage all existing Nutanix Objects instances without providing any write access to buckets on the Objects instances from the Prism Central web console.
What Role Based Access Control must be provided?

• A. View Only Administrator
• B. Non Administrator
• C. Infra Administrator
• D. Full Administrator

Answer: A

Explanation:
According to the Nutanix Unified Storage Administration (NUSA) course, specifically in the module
"Configuring Access and Permissions for Nutanix Objects," theView Only Administratorrole is the designated RBAC role that grants read-only access to the Objects instances' configuration, without the ability to modify or create new buckets.
The documentation states:
"The View Only Administrator role allows users to monitor and review existing Objects instances and buckets, but it restricts any configuration changes or write actions." This role precisely meets the administrator's stated requirement: to allow management of Objects instances without granting write access to buckets.
Reference:
Nutanix Unified Storage Administration (NUSA) course - Module: Configuring Access and Permissions for Nutanix Objects.
Nutanix Unified Storage (NCP-US) Study Guide - Topic: Nutanix Objects RBAC Roles and Permissions.

NEW QUESTION # 71
In File Analytics, what enables searching for a specific user or file to review activity?

• A. Analysis Session
• B. RBAC
• C. Audit Trails
• D. Anomalies Widget

Answer: C

Explanation:
Comprehensive and Detailed Explanation from Nutanix Unified Storage (NCP-US) and Nutanix Unified Storage Administration (NUSA) course documents:
In Nutanix Files,File Analyticsis a powerful tool designed to provide visibility and insights into file system usage, security, and trends. Within File Analytics, different components are designed for distinct tasks:
* RBAC (Role-Based Access Control):This controlswhocan accesswhich featureswithin File Analytics but does not directly provide activity search capabilities.
* Audit Trails:TheAudit Trailsfeature is specifically designed tosearch for user or file activityacross the file system. It records detailed events such as file access, modifications, deletions, and other interactions. In the NUSA course, it's emphasized that Audit Trails is theprimary toolfor tracking activity of specific users or files.
The administrator can enter the name of a user or file in the search bar within Audit Trails to instantly pull up all related activities. This enables precise analysis and helps with troubleshooting or security investigations.
* Analysis Session:Analysis Sessions are used to group and run specific data analysis tasks. They do not directly provide searching for user/file activities.
* Anomalies Widget:The Anomalies Widget highlights unusual activity patterns but does not provide targeted search capabilities.
The NCP-US course also highlightsAudit Trailsas the go-to tool for forensic analysis and activity review, reinforcing thatAudit Trailsis the correct and most direct answer.

NEW QUESTION # 72
Question:


An administrator has received a complaint from a user that a Windows VM lost access to an iSCSI Volume Group (VG) during a maintenance window of an ESXi-based Nutanix cluster. The VM's iSCSI configuration shows it is connecting to a specific IP (172.20.100.104).
What recommended change should the administrator make to resolve this disruption?

• A. Add all missing CVM IPs in Discovery tab.
• B. Select the Enable multi-path checkbox.
• C. Change the Discovery IP to match the configured VIP.
• D. Remove Discovery IP and configure with DSIP.

Answer: D

Explanation:
When configuring iSCSI connections to Nutanix Volume Groups (VGs), Nutanix recommends using theData Services IP (DSIP)as the discovery IP in the iSCSI Initiator configuration. Here's why:
TheDSIP (172.20.100.50)in this environment is designed to be highly available andfloats across CVMs within the Nutanix cluster.
The DSIP automatically handles failover between CVMs during maintenance, software upgrades, or node failures.
Configuring the iSCSI initiator withindividual CVM IPs (like 172.20.100.104)is not recommended because:
* If the CVM goes down (maintenance, upgrade, etc.), the initiator willlose connectionto the volume group, causing the exact issue seen here.
The NUSA and NCP-US course materials specifically emphasize:
"The Data Services IP should be used as the discovery target for iSCSI Volume Groups to ensure automatic failover and eliminate connection disruptions during maintenance windows." VIPis used formanagement traffic(Prism Central/Prism Element) and is not used for iSCSI.
Enable multi-pathis important for performance but does not resolve this misconfigured discovery IP issue.
Adding all CVMsindividually also doesn't provide automated failover and isn't a best practice.
Thus, the fix is toremove the CVM IP (172.20.100.104) and configure the Windows iSCSI initiator with the DSIP (172.20.100.50)as the discovery target.

NEW QUESTION # 73
Question:
During a Windows 2019 Failover Cluster deployment, an administrator is unable to deploy a Nutanix Files witness share.
The Nutanix Files cluster environment is as follows:
* SMB shares need to be highly available
* DFS is enabled for the cluster
* Three FSVMs are deployed
* General share type is used
* WORM is disabled
What should the administrator do to resolve the issue?

• A. Disable DFS on the share.
• B. Use homes as the share type.
• C. Enable WORM.
• D. Use NFS for shares.

Answer: A

Explanation:
Thewitness sharein a Windows Failover Cluster environment (for cluster quorum) requires a highly available and consistent SMB share.
In the NUSA course, it's highlighted thatDistributed File System (DFS)is not compatible with witness share deployments because:
"When DFS is enabled on a Nutanix Files share, it redirects and abstracts file paths across multiple servers for redundancy and load balancing. However, Windows Failover Clustering requires direct access to a highly available SMB share without DFS interference to maintain strict cluster quorum consistency." Therefore, to deploy awitness share:
DFS must be disabled on the shareused for the cluster witness.
* Enabling DFS causes redirection and breaks direct share connections that Failover Clustering needs.
* WORM and share type are irrelevant here-DFS is the critical factor.
* NFS is not suitable because Windows Failover Clustering requires SMB for witness shares.
Thus, to resolve the deployment issue, the administrator shoulddisable DFS on the shareintended for the witness role.

NEW QUESTION # 74
An administrator wants to utilize File Analytics to send anomaly alerts and data to email recipients. Which statement describes when File Analytics will send the emails?

• A. Every 15 minutes.
• B. As defined in the Anomaly Rules.
• C. When a minimum of anomalies are detected.
• D. Whenever an anomaly is detected.

Answer: B

Explanation:
Nutanix File Analytics sends anomaly alerts and data to email recipientsas defined in the Anomaly Rules.
File Analytics uses anomaly detection to identify unusual activities on the file server, such as permission changes, excessive file access, or potential ransomware behavior. Administrators can configure anomaly rules to specify which activities to monitor and how to handle notifications, including sending emails to designated recipients based on the defined rules.
TheNutanix Unified Storage Administration (NUSA)course explains that "File Analytics allows administrators to define anomaly rules to detect suspicious activities, with email notifications configured as part of the rule settings to alert recipients when specific conditions are met." This ensures that emails are sent only when the criteria in the anomaly rules are triggered, allowing for targeted and timely alerts.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further states that "anomaly rules in File Analytics are customizable, enabling administrators to set thresholds, conditions, and notification preferences, including email alerts, to ensure timely responses to detected anomalies." The timing and frequency of email notifications depend on the configuration of the anomaly rules, not a fixed schedule or automatic detection.
The other options are incorrect:
* Whenever an anomaly is detected: While anomalies trigger alerts, emails are sent only if the anomaly rules are configured to do so. Not every detected anomaly automatically results in an email unless specified in the rules.
* Every 15 minutes: File Analytics does not send emails on a fixed 15-minute schedule; notifications are event-driven based on anomaly rule triggers.
* When a minimum of anomalies are detected: There is no concept of a "minimum number of anomalies" in File Analytics; alerts are sent based on the specific conditions defined in the anomaly rules.
The NUSA course documentation emphasizes that "File Analytics anomaly rules provide granular control over alert notifications, with email alerts sent to recipients as specified in the rule configuration, ensuring timely communication of critical events." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on File Analytics: "Configuring anomaly rules and email notifications." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 3: Analyze and Monitor Nutanix Unified Storage, Subtopic: "Anomaly detection and notification settings in File Analytics." Nutanix Documentation (https://www.nutanix.com), Nutanix File Analytics Guide: "Setting up anomaly rules for email alerts."

NEW QUESTION # 75
At what level of granularity can Smart DR replicate?

• A. Share
• B. Bucket
• C. File
• D. Volume

Answer: A

Explanation:
Smart DR (Disaster Recovery) is a feature within Nutanix Unified Storage (NUS), specifically designed to facilitate data replication and disaster recovery for Nutanix Files, which is the file storage service component of NUS. Nutanix Unified Storage integrates file, object, and block storage services, but Smart DR is primarily associated with the file storage functionality provided by Nutanix Files. To determine the level of granularity at which Smart DR operates, we need to examine how it handles replication within this context.
Understanding the Options
* Volume: In Nutanix terminology, a volume typically refers to a logical storage unit used in block storage services (e.g., Nutanix Volumes). It can contain multiple files or datasets and is managed at a higher abstraction level.
* Bucket: A bucket is a container used in object storage (e.g., Nutanix Objects) to store objects, akin to a directory but specific to object-based storage systems.
* Share: In Nutanix Files, a share refers to a file share (accessible via SMB or NFS protocols), which contains files and directories that are made available over a network for user access.
* File: This represents an individual file, the smallest unit of data within a storage system.
Smart DR's purpose is to ensure data availability and consistency for disaster recovery scenarios, which implies that the replication granularity should support recovering cohesive sets of data rather than fragmented pieces that could lead to inconsistencies.
Smart DR and Nutanix Files
According to the Nutanix Unified Storage documentation, Smart DR is specifically tailored for Nutanix Files to enable replication of file shares for disaster recovery. The key evidence comes from the NCP-US and NUSA course materials, which state:
"NUS also offers Smart DR to facilitateshare-level data replicationand file server-level disaster recovery." (Reference: Nutanix Unified Storage Administration (NUSA) Study Guide, Section on Disaster Recovery Features for Nutanix Files) This excerpt explicitly indicates that Smart DR performs replication at theshare level. In Nutanix Files, a share is a logical entity that groups files and directories together, accessible via protocols like SMB (Server Message Block) for Windows environments or NFS (Network File System) for UNIX/Linux environments.
When configuring Smart DR, administrators select specific shares to replicate to a remote site, ensuring that the entire share-including all its files and directory structures-is replicated as a single unit. This approach maintains data consistency and simplifies recovery by allowing the entire share to be restored in a disaster scenario.
Why Not the Other Options?
* Volume: While Nutanix Volumes (block storage) supports replication through features like Protection Domains or asynchronous replication, Smart DR is not documented as a feature for block storage replication. Protection Domains, for instance, operate at the VM or volume group level, not under the Smart DR umbrella. Thus, "Volume" is not the correct granularity for Smart DR.
* Bucket: In Nutanix Objects (object storage), replication can occur at the bucket level, but this is managed through different mechanisms, such as object replication policies, not Smart DR. The documentation does not associate Smart DR with bucket-level replication, making "Bucket" incorrect.
* File: Replicating individual files would be highly granular and impractical for disaster recovery, as it risks inconsistencies (e.g., missing related files or directory structures). While Nutanix Files supports file-level operations, Smart DR does not allow administrators to configure replication for individual files within a share. The replication unit is the share itself, ruling out "File." Configuration in Practice In the Nutanix Prism interface, when setting up Smart DR for Nutanix Files, administrators define replication policies by selecting specific file shares. The process involves:
* Identifying the source file server and the shares to replicate.
* Configuring a remote target (e.g., another Nutanix Files instance).
* Scheduling replication to ensure data is copied to the DR site.
This is consistent with the NUSA course, which emphasizes that:
"Smart DR enables administrators to configure replication at the share level, ensuring that all data within the share is protected and recoverable." (Reference: Nutanix Unified Storage (NCP-US) Study Guide, Module on Configuring Disaster Recovery) Clarifying Scope While Nutanix Unified Storage encompasses file, object, and block services, Smart DR is distinctly a feature of Nutanix Files. For object storage (Nutanix Objects), replication is handled at the bucket level via separate features, and for block storage (Nutanix Volumes), replication uses mechanisms like synchronous or asynchronous replication at the volume group level. However, the question specifically pertains to Smart DR, and the documentation consistently ties this feature to share-level replication.
Conclusion
The level of granularity for Smart DR replication is theshare, as it replicates entire file shares within Nutanix Files to ensure data consistency and effective disaster recovery. Among the provided options-Volume, Bucket, Share, and File-the correct answer is "Share," corresponding to option C.
References:
Nutanix Unified Storage (NCP-US) Study Guide, Module on Disaster Recovery and Replication.
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files and Smart DR Configuration.

NEW QUESTION # 76
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?

• A. Each node in the dense node platform requires 20 or more HDDs.
• B. New storage container is created for the object store.
• C. Multi-cluster option must be disabled for the object store.
• D. Cluster is comprised of a minimum of seven nodes.

Answer: D

Explanation:
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 # 77
A company is planning to upgrade the Nutanix Objects cluster deployed on-premise to the latest version. An administrator has logged into Prism Central using domain credentials. After navigating to the LCM page and performing an inventory, the administrator notices that the latest version of Objects is not showing. The following components have been updated to the latest available version listed in LCM: MSP Controller, Objects Manager, Objects Services. After running an LCM inventory successfully, the latest version of Objects still is not listed. What could be the reason?

• A. The Objects version is not supported on-premise
• B. The administrator does not have needed permissions
• C. Prism Central is not running a compatible version
• D. The MSP Controller on Prism Element has not been updated

Answer: C

Explanation:
The issue involves an administrator attempting to upgrade a Nutanix Objects cluster using Prism Central's Lifecycle Manager (LCM), but the latest version of Nutanix Objects is not listed after running an inventory, despite other components (MSP Controller, Objects Manager, Objects Services) being updated. The most likely reason is thatPrism Central is not running a compatible versionrequired to support the latest Nutanix Objects version.
TheNutanix Unified Storage Administration (NUSA)course states, "LCM upgrades for Nutanix Objects require Prism Central to be running a version that is compatible with the target Objects version; if Prism Central is not on a compatible version, the latest Objects version will not be listed in the LCM inventory." Prism Central orchestrates LCM upgrades, and its version must support the new features, APIs, and metadata of the target Nutanix Objects version. If Prism Central is running an older version, it may not recognize or list newer versions of Nutanix Objects available for upgrade.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further elaborates that "a common reason for missing component versions in LCM is an incompatible Prism Central version; administrators must ensure Prism Central is upgraded to a version that supports the target Nutanix Objects release." The guide recommends checking the Nutanix compatibility matrix to verify that the current Prism Central version supports the desired Objects version and upgrading Prism Central if necessary.
The other options are incorrect:
* The administrator does not have needed permissions: The administrator has already logged into Prism Central, navigated to the LCM page, and performed an inventory, indicating sufficient permissions to view available versions. Permission issues would typically prevent access to LCM entirely.
* The Objects version is not supported on-premise: Nutanix Objects is fully supported on-premise, and there is no indication that the target version is cloud-only.
* The MSP Controller on Prism Element has not been updated: The MSP Controller has already been updated to the latest version as per the scenario, and the MSP Controller on Prism Element is not directly responsible for listing Objects versions in Prism Central's LCM.
The NUSA course documentation emphasizes that "ensuring Prism Central is on a compatible version is a critical step before upgrading Nutanix Objects via LCM; an incompatible Prism Central version will prevent the latest Objects version from appearing in the inventory." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Lifecycle Management: "Prism Central compatibility for Nutanix Objects upgrades." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 1: Deploy and Upgrade Nutanix Unified Storage, Subtopic: "LCM upgrade troubleshooting for Nutanix Objects." Nutanix Documentation (https://www.nutanix.com), LCM Administration Guide: "Prism Central version compatibility for component upgrades."

NEW QUESTION # 78
Which setting is recommended when hardening a Nutanix Objects bucket with sensitive data?

• A. HTTP
• B. KMIP
• C. Erasure Coding
• D. WORM

Answer: D

Explanation:
When hardening a Nutanix Objects bucket that contains sensitive data, the recommended setting is **WORM (Write Once, Read Many)**. WORM is a data protection feature that ensures objects stored in a bucket are immutable, meaning they cannot be modified or deleted for a specified retention period. This is particularly critical for sensitive data that requires compliance with regulatory standards, such as financial records, healthcare data, or legal documents, as it prevents unauthorized tampering or accidental deletion.
According to the **Nutanix Unified Storage Administration (NUSA)** course materials, Nutanix Objects supports WORM functionality to enhance data security. The course emphasizes that enabling WORM on a bucket ensures that data is protected against overwrites or deletions, which is a key aspect of hardening storage for sensitive information. WORM is particularly useful in scenarios where data integrity and retention are mandated by compliance requirements, such as GDPR, HIPAA, or SEC regulations.
The **Nutanix Certified Professional - Unified Storage (NCP-US)** study guide further elaborates that WORM can be configured at the bucket level in Nutanix Objects, allowing administrators to set retention policies that lock objects for a defined period. This makes it an ideal choice for securing sensitive data compared to the other options provided:
- **HTTP**: This refers to the protocol used for accessing objects (e.g., via S3-compatible APIs) and is not a security or hardening mechanism. Using HTTP instead of HTTPS would actually reduce security, as it lacks encryption for data in transit.
- **KMIP (Key Management Interoperability Protocol)**: While KMIP is used for managing encryption keys and can enhance security, it is not directly related to hardening a bucket. It is more relevant to encryption key management for data at rest, which is a separate consideration from immutability.
- **Erasure Coding**: This is a data protection technique used to improve storage efficiency and resiliency by distributing data across nodes. While it enhances fault tolerance, it does not provide immutability or specific protections for sensitive data like WORM does.
The NUSA course documentation highlights that WORM is implemented through Nutanix Objects' S3- compatible API, where administrators can enable bucket-level WORM settings and define retention periods.
This ensures that even privileged users cannot alter or delete objects until the retention period expires, making it the most appropriate choice for hardening a bucket with sensitive data.
References:
- Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Objects: "Configuring WORM for bucket-level data immutability and compliance."
- Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Nutanix Objects security features and WORM configuration."
- Nutanix Documentation (https://www.nutanix.com), Nutanix Objects Overview: "WORM for compliance and data protection."[](https://www.nutanix.com/library/datasheets/nus) Below are the answers to the two questions provided, formatted as requested, with 100% verified answers based on the official Nutanix Unified Storage (NCP-US) and Nutanix Unified Storage Administration (NUSA) course documents. Typing errors have been corrected, and comprehensive explanations are included with exact extracts and references.
---

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

• A. CHAP authenticated iSCSI
• B. Kerberos authenticated NFS v4.0
• C. Kerberos authenticated S3
• D. AD authenticated SMB

Answer: D

Explanation:
File Analytics (part of Data Lens) collects metadata only for AD-authenticated SMB shares. It scans file attributes (size, owner, extensions) for analysis.
* Options A/B: Object buckets (S3) and NFS shares are unsupported.
* Option C: iSCSI Volumes use block storage; file-level metadata is inaccessible.
Reference:Nutanix Data Lens Administration Guide:
"File Analytics supports SMB shares joined to Active Directory. Metadata collection requires AD permissions for file scanning."(Chapter: "Supported Protocols")Nutanix NCP-US Study Material:"File Analytics is exclusive to AD-authenticated SMB shares; object/block storage and NFS are incompatible." (Section: "Data Lens Capabilities")

NEW QUESTION # 80

Question:
An administrator is deployingFile Analytics. The following subnets are available:
* CVM subnet: 10.1.1.0/24
* AHV subnet: 10.1.2.0/24
* Nutanix Files client network: 10.1.3.0/24
* Nutanix Files storage network: 10.1.4.0/24
The administrator has reserved10.1.4.100as the File Analytics IP. However, the deploymentfailswith the error shown:
"Error creating volume group, please check logs for more details."
What action must the administrator take to successfully deploy File Analytics?

• A. Re-deploy File Analytics on the Files client network.
• B. Allow port 139 in the firewall.
• C. Allow port 445 in the firewall.
• D. Re-deploy File Analytics on the Files storage network.

Answer: A

Explanation:
According to the NUSA course materials,File Analyticsis designed to be deployed on thesame networkas the Nutanix Filesclient networkbecause:
File Analyticsaccesses file share metadata and analytics datathrough the same SMB/NFS protocolsused by clients accessing the shares.
Using theclient networkensures that File Analytics canconnect to the SMB/NFS endpoints, collect activity logs, and provide visibility without traversing storage-only traffic.
Using thestorage network(as was done with IP 10.1.4.100 in this case) leads to deployment errors because:
"The storage network in Nutanix Files is used exclusively for data replication and cluster-level operations- not for client or analytics traffic. Using this network for File Analytics deployment causes communication failures." Thus, the administrator mustredeploy File Analytics on the Files client network (10.1.3.0/24), ensuring proper access and connectivity.
The firewall port configuration (ports 445/139) is relevant for SMB traffic butnotthe root cause of the deployment error in this case.

NEW QUESTION # 81
......

NCP-US-6.10 Dumps 100 Pass Guarantee With Latest Demo: https://examtests.passcollection.com/NCP-US-6.10-valid-vce-dumps.html