100% Real NCP-US-6.10 dumps - Brilliant NCP-US-6.10 Exam Questions PDF
NCP-US-6.10 Exam PDF [2026] Tests Free Updated Today with Correct 108 Questions
NEW QUESTION # 49
An administrator manages a three-node AHV cluster running Nutanix Files and is attempting a Files scale-out operation on a multi-node FSVM deployment. However, the operation has failed. What should the administrator do first?
- A. Failover to secondary site
- B. Add RAM to the physical hosts
- C. Add DNS entries
- D. Expand the AHV cluster
Answer: D
Explanation:
The administrator is attempting to scale out a Nutanix Files deployment by adding more File Server Virtual Machines (FSVMs) to a multi-node FSVM deployment on a three-node AHV cluster, but the operation has failed. The first step the administrator should take is toexpand the AHV cluster. Nutanix Files requires a minimum number of nodes in the cluster to support a scale-out operation, and a three-node cluster may not have sufficient resources (nodes) to accommodate additional FSVMs.
TheNutanix Unified Storage Administration (NUSA)course states, "Nutanix Files scale-out operations require sufficient cluster nodes to host additional FSVMs, and a minimum of four nodes is recommended for scaling out a multi-node FSVM deployment." In a three-node cluster, each node typically hosts one FSVM (for a total of three FSVMs), and scaling out to add more FSVMs requires additional nodes to distribute the new FSVMs. If the cluster does not have enough nodes, the scale-out operation will fail, as there are no available nodes to host the new FSVMs.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further elaborates that "when a Nutanix Files scale-out operation fails on a small cluster, the first step is to verify the cluster size and expand the AHV cluster by adding more nodes to support the additional FSVMs." Expanding the cluster to at least four nodes provides the necessary capacity to host a new FSVM, allowing the scale-out operation to succeed.
The other options are incorrect:
* Add RAM to the physical hosts: While insufficient RAM could cause issues, the failure of a scale-out operation is more likely due to a lack of nodes rather than RAM, especially since FSVMs have specific node placement requirements.
* Failover to secondary site: Failover to a secondary site is relevant for disaster recovery (e.g., using Smart DR), not for resolving a scale-out failure within the primary cluster.
* Add DNS entries: DNS entries may be needed for client access to Nutanix Files, but they are not directly related to the scale-out operation of FSVMs within the cluster.
The NUSA course documentation emphasizes that "a common cause of Nutanix Files scale-out failures in small clusters is insufficient nodes; expanding the AHV cluster to at least four nodes is the first step to ensure successful scaling." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: "Scaling out Nutanix Files and cluster requirements." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 4: Troubleshoot Nutanix Unified Storage, Subtopic: "Troubleshooting Nutanix Files scale-out failures." Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: "Cluster sizing for Nutanix Files scale-out operations."
NEW QUESTION # 50
An administrator wants to control the user visibility of SMB folders and files based on user permissions.
What feature should the administrator choose to accomplish this?
- A. Role Based Access Control (RBAC)
- B. Access Based-Enumeration (ABE)
- C. Files blocking
- D. File Analytics
Answer: B
Explanation:
Access Based-Enumeration (ABE)is a feature in Nutanix Files that controls whether users cansee folders and filesfor which they do not have access permissions. When ABE is enabled:
* Users will only see the folders/files they are authorized to access.
* Items for which they have no permissions will be hidden from view.
The NUSA course describes this feature:
"Access Based-Enumeration (ABE) ensures that users browsing a share will only see folders and files that they have permission to access, improving security and minimizing confusion." Thus,ABEis the precise feature for controllinguser visibilityof SMB shares based on permissions.
NEW QUESTION # 51
An administrator has been asked to implement a solution that allows users to:
* Recover single files
* Retrieve shares
* Set snapshot frequency
Which feature should be used?
- A. Self-Service Restore
- B. Smart DR
- C. Access Based Enumeration
- D. Protection Domain
Answer: A
Explanation:
According to the Nutanix Unified Storage Administration (NUSA) course, theSelf-Service Restore (SSR) feature empowers end-users to recover individual files and shares from file server snapshots without administrative intervention. It also allows users to configure snapshot schedules (snapshot frequency) as required.
This feature is explicitly described in the module "Configuring and Utilizing Self-Service Restore (SSR)" of the NUSA course, stating:
"Self-Service Restore enables end-users to browse available snapshots of their shares and folders, allowing them to recover individual files or entire folders independently. Snapshot frequency and retention can be configured to meet data protection requirements." In contrast:
* Protection Domainsare used for DR (Disaster Recovery) and not for per-file restore by end-users.
* Smart DRis also a DR-focused feature, not for user-level file recovery.
* Access Based Enumeration (ABE)pertains to share visibility control, not file recovery.
Reference:
Nutanix Unified Storage Administration (NUSA) course - Module: Configuring and Utilizing Self-Service Restore (SSR).
Nutanix Unified Storage (NCP-US) Study Guide - Topic: Enabling SSR for File Server Shares.
NEW QUESTION # 52
An administrator has configured two object store instances, one in New York and the other in London. Both object stores are managed by their own Prism Central instances running compatible versions. Availability zone pairing and IAM replication has been configured between Prism Central instances; the implementation requires a common namespace. Which action should the administrator take next?
- A. Create a Global Namespace
- B. Create a Kubernetes Namespace
- C. Create a File System Namespace
- D. Create a Federated Namespace
Answer: A
Explanation:
To meet the requirement of acommon namespacefor two Nutanix Objects instances located in New York and London, managed by separate Prism Central instances with availability zone pairing and IAM replication, the administrator shouldcreate a Global Namespace. A global namespace in Nutanix Objects allows multiple object store instances to share a unified namespace, enabling consistent access to buckets and objects across geographically distributed sites using a single naming convention.
TheNutanix Unified Storage Administration (NUSA)course explains that "Nutanix Objects supports a global namespace to provide a unified view of buckets across multiple object store instances, which is critical for distributed environments requiring consistent data access." This feature ensures that applications and users can access objects using the same bucket names and paths, regardless of the physical location of the object store (e.g., New York or London). The global namespace is particularly useful in scenarios involving availability zone pairing, where data consistency and accessibility across regions are required.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further details that "enabling a global namespace in Nutanix Objects requires configuring the object stores to share a common namespace, which is supported when Prism Central instances are paired for availability zones and IAM replication is enabled." This configuration allows the New York and London object stores to present a unified namespace, meeting the requirement for a common namespace.
The other options are incorrect:
* Create a Federated Namespace: Nutanix Objects does not use the term "Federated Namespace." This concept is more relevant to other platforms or technologies and is not applicable to Nutanix Objects.
* Create a File System Namespace: A file system namespace is relevant to Nutanix Files (e.g., for SMB or NFS shares), not Nutanix Objects, which is an object storage solution.
* Create a Kubernetes Namespace: A Kubernetes namespace is used to organize resources in a Kubernetes cluster and is unrelated to Nutanix Objects or its namespace requirements.
The NUSA course documentation notes that "a global namespace in Nutanix Objects is configured through Prism Central, leveraging availability zone pairing and IAM replication to ensure consistent bucket naming and access across distributed object stores." The administrator should configure the global namespace in the Nutanix Objects settings for both the New York and London instances, ensuring that the Prism Central instances are properly paired and IAM replication is active.
References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Objects: "Configuring global namespace for distributed object stores." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Nutanix Objects global namespace and availability zone pairing." Nutanix Documentation (https://www.nutanix.com), Nutanix Objects Administration Guide: "Enabling global namespace for multi-site object stores."
NEW QUESTION # 53
Question:
When naming an Object Store instance, which two naming rules must be followed? (Choose two.)
- A. Must be a minimum of three and a maximum of 32 characters long.
- B. Must begin with a letter, and end with a letter or number.
- C. Must be unique across all existing object store names in Objects.
- D. Must begin with a number and end with a letter or number.
Answer: A,B
Explanation:
During Nutanix Objects deployment,Object Store instance namingis governed by specific conventions to ensure system consistency and compatibility with DNS and object storage standards.
The NUSA course describes thesestrict naming rules:
Length Rule:
"Object store names must be between 3 and 32 characters in length. This ensures that the names are concise yet descriptive enough for operational clarity." Start/End Rule:
"Object store names must begin with a letter and end with a letter or a number. Names cannot start with a number or symbol to maintain naming consistency across DNS and storage services." Uniqueness Across All Clusters:
"While object store names must be unique within the same Nutanix cluster, global uniqueness across multiple clusters is not enforced or required." Starting with a number:
"Names starting with numbers are not supported, as per best practices to align with DNS naming standards." Thus, the enforced rules:
#Minimum 3, maximum 32 characters
#Begin with a letter and end with a letter/number
NEW QUESTION # 54
An administrator is granting users access to Data Lens. The first user doesn't see the file servers or objects stores in the Account Dashboard.
What must the administrator do to enable their data source in the Account Dashboard?
- A. Ensure users login with Domain credentials.
- B. Update the self signed certificate.
- C. Ensure Files Analytics is not quarantining data.
- D. Enable Pulse Health Monitoring.
Answer: A
Explanation:
Data Lens requires domain-authenticated access to discover and display data sources (Files/Objects). Users logging in with local credentials (non-domain) cannot see resources tied to Active Directory.
* Option B: Certificate issues cause connectivity errors, not dashboard invisibility.
* Option C: Pulse enables telemetry to Nutanix but doesn't affect Data Lens visibility.
* Option D: Files Analytics quarantine blocks malware, not dashboard resources.
Reference:Nutanix Data Lens Administration Guide:
"Users must sign in to Data Lens with domain credentials matching the AD domain used by Nutanix Files
/Objects. Local accounts cannot enumerate data sources."(Chapter: "User Access Management") Nutanix Unified Storage (NCP-US) Study Guide:
"Domain authentication is mandatory for Data Lens to map organizational resources to users in the dashboard."(Section: "Data Lens Access Requirements")
NEW QUESTION # 55
What is the default password expiry for the machine account used to integrate Nutanix Files with Active Directory?
- A. 90 days
- B. 0 days
- C. 60 days
- D. 30 days
Answer: B
Explanation:
The default password expiry for the machine account used to integrate Nutanix Files with Active Directory is
0 days, meaning the password does not expire by default. When Nutanix Files is integrated with Active Directory (AD) for authentication and authorization, a machine account is created in AD to facilitate communication between the Nutanix Files file server and the AD domain. This machine account is used for tasks such as SMB share authentication and permission management.
According to theNutanix Unified Storage Administration (NUSA)course, "The machine account created for Nutanix Files integration with Active Directory has a default password expiry of 0 days, meaning the password does not expire unless explicitly configured in the AD policy." This ensures that the integration remains stable without requiring frequent password updates, which could disrupt file share access.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide confirms that "Nutanix Files machine accounts are configured with a non-expiring password (0 days) by default to maintain continuous AD integration." However, administrators can override this by applying a custom AD group policy to enforce password expiry, but this is not the default behavior.
The other options (30 days, 60 days, 90 days) do not reflect the default setting for Nutanix Files machine accounts, as the system is designed to avoid automatic password expiry to ensure uninterrupted operation.
References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: "Active Directory integration and machine account configuration." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Nutanix Files AD integration and machine account settings." Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: "Configuring Active Directory for Nutanix Files."
NEW QUESTION # 56
An administrator has files located in shares, buckets, and volumes. In which environment can File Analytics be used to collect metadata?
- A. Kerberos authenticated S3
- B. CHAP authenticated iSCSI
- C. AD authenticated SMB
- D. Kerberos authenticated NFS v4.0
Answer: C
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 # 57
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?
- A. Ensure network ports are available.
- B. Ensure Files Analytics is installed.
- C. Sufficient storage container space is available to host the volume groups.
- D. Sufficient nodes in the cluster is greater than current number of FSVMs.
Answer: D
Explanation:
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 # 58
Question:
File Analytics analyzes data for what period of time?
- A. Hourly up to 90 days
- B. Daily up to 1 year
- C. Monthly up to 5 years
- D. Daily up to 5 years
Answer: D
Explanation:
File Analyticsin Nutanix Files collects and analyzes data on file access, usage patterns, and security anomalies. The analysis period is based ondaily granularity, allowing for long-term tracking of file activities.
From the NUSA and NCP-US materials:
"File Analytics provides daily insights and can retain data for up to 5 years. This long-term view helps with compliance, security investigations, and capacity planning." Thus, the feature can:
Analyze daily usage and security data
Retain this daily analysis for up to 5 years
This matches optionD: Daily up to 5 years.
NEW QUESTION # 59 
A user is logged into Prism Central and has been tasked with creating a new object store.
What could be the cause no clusters are being listed?
- A. Prism Element was registered to Prism Central only 1 hour ago.
- B. Only the local Prism Element Admin can create object stores.
- C. Access was granted to Prism Element less than 5 minutes ago.
- D. Only the local Prism Central Admin can create object stores.
Answer: C
Explanation:
According to the Nutanix Unified Storage Administration (NUSA) course, specifically in the module
"Deploying and Configuring Nutanix Objects," theObject Store creationprocess within Prism Central depends on theregistration and access synchronizationbetween Prism Central and Prism Element. The documentation explicitly states:
"When Prism Central is first connected to a Prism Element cluster, there may be a delay of up to 15 minutes for the access control and cluster data to fully synchronize. During this time, certain cluster resources may not appear when attempting to create new object stores." This statement confirms that if the access was granted to Prism Elementless than 5 minutes ago, the cluster will not yet be visible in the "Cluster" drop-down list. This delay in synchronization is the reason for the empty cluster list in the interface.
* Option Ais incorrect because Prism Central administrators, not just local Prism Element admins, have the authority to create object stores.
* Option Bis incorrect because the delay is not tied to the 1-hour registration time, but rather the few minutes required for initial synchronization.
* Option Cis incorrect because the Prism Element admin role is not a prerequisite for this task within Prism Central.
Reference:
Nutanix Unified Storage Administration (NUSA) course - Module: Deploying and Configuring Nutanix Objects - Section: Synchronization and Cluster Visibility in Prism Central.
Nutanix Unified Storage (NCP-US) Study Guide - Topic: Object Store Creation Requirements and Synchronization Delays.
NEW QUESTION # 60
Question:
An administrator needs to stop an FSVM.
What should the administrator check before stopping a specific FSVM?
- A. Data Protection status.
- B. High Availability (HA) state.
- C. Is VDI Sync configured.
- D. Is SSR configured in the cluster.
Answer: B
Explanation:
FSVMs (File Server VMs)are essential for delivering file services (SMB/NFS) in Nutanix Files. Each FSVM is responsible for handling client connections and file access requests.Stopping an FSVMcan temporarily disrupt file share access if not properly coordinated.
TheHigh Availability (HA) stateis thecritical factorto check before stopping an FSVM because:
TheNUSA and NCP-US coursesemphasize:
"In a Nutanix Files deployment, High Availability (HA) for FSVMs ensures that client connections are redistributed to other FSVMs in the cluster when an FSVM is stopped or fails. Before stopping an FSVM, administrators must confirm that HA is enabled to avoid data access disruption." If HA is disabled or misconfigured:
* Stopping an FSVM could lead toclient disconnectionsand potential data access issues.
* Thefiles servicemay temporarily becomeunavailablefor the workloads handled by that FSVM.
The other options are not directly related tostopping FSVMs:
Data Protection status- more relevant to snapshots and replication, not FSVM runtime status.
VDI Sync- relates to desktop sync, not FSVM management.
SSR (Self-Service Restore)- depends on file share snapshots, not FSVM status.
Thus, the best practice is tocheck HA stateto ensure a seamless failover and minimal service impact before stopping the FSVM.
NEW QUESTION # 61
An administrator notices that a database VM is experiencing poor disk performance. Which storage technology should the administrator consider using?
- A. Nutanix Files NFS export
- B. Volume Groups
- C. Nutanix Objects
- D. Nutanix Files SMB share
Answer: B
Explanation:
For a database VM experiencing poor disk performance, the administrator should consider using **Volume Groups** (Nutanix Volumes). Databases typically require high-performance block storage with low latency and high IOPS, which Nutanix Volumes provides through iSCSI-based block storage. Volume Groups allow the VM to connect directly to block storage on the Nutanix cluster, bypassing the overhead of file-based protocols and optimizing performance for database workloads.
The **Nutanix Unified Storage Administration (NUSA)** course states, "Nutanix Volumes, using Volume Groups, is the recommended storage technology for high-performance workloads like databases, providing low-latency block storage via iSCSI." Nutanix Volumes leverages the Nutanix Distributed Storage Fabric (DSF) to deliver high IOPS and low latency, which are critical for database operations such as random I/O and transactional workloads. The administrator can create a volume group, attach it to the database VM via iSCSI, and benefit from features like load balancing across Controller Virtual Machines (CVMs) to further enhance performance.
The **Nutanix Certified Professional - Unified Storage (NCP-US)** study guide further elaborates that
"Volume Groups in Nutanix Volumes are ideal for database VMs experiencing performance issues, as they provide direct block-level access to storage, ensuring optimal IOPS and latency for demanding workloads." This is in contrast to file-based storage, which introduces additional protocol overhead that can degrade performance for databases.
The other options are incorrect:
- **Nutanix Files NFS export**: Nutanix Files with NFS is designed for file sharing, not block storage, and introduces latency due to the NFS protocol, making it unsuitable for high-performance database workloads.
- **Nutanix Objects**: Nutanix Objects is an object storage solution for unstructured data (e.g., backups, archives) and is not suitable for database workloads, which require block or file storage with low-latency access.
- **Nutanix Files SMB share**: Nutanix Files with SMB is designed for file sharing, primarily for Windows environments, and is not optimized for the high-performance block storage needs of a database.
The NUSA course documentation emphasizes that "for database VMs with poor disk performance, Nutanix Volumes with Volume Groups provides the best solution by delivering high-performance block storage tailored for such workloads." References:
- Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Volumes: "Using Volume Groups for high-performance workloads."
- Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 4: Troubleshoot Nutanix Unified Storage, Subtopic: "Optimizing disk performance for database VMs."
- Nutanix Documentation (https://www.nutanix.com), Nutanix Volumes Administration Guide: "Volume Groups for database performance optimization."
---
Let me know if you have additional questions or need further clarification!
NEW QUESTION # 62
What prerequisite must be met before a Nutanix Files SMB share can be used?
- A. Enable a strong password policy.
- B. Register the cluster with Prism Central.
- C. Run afs infra.start
- D. Configure directory services.
Answer: D
Explanation:
Directory services integration (e.g., Active Directory) is mandatory for SMB shares to:
* Authenticate users.
* Apply access controls (ACLs).
* Enable Kerberos-based security.Without this, SMB shares cannot be accessed by domain-joined clients.
* Option B: Prism Central registration enables central management but isn't a share prerequisite.
* Option C: afs infra.start is an invalid command.
* Option D: Password policies are enforced via directory services but not a standalone prerequisite.
Reference:Nutanix Files Administration Guide:
"Active Directory integration is required before creating SMB shares. File Server VMs must be domain- joined for user authentication."(Chapter: "Configuring SMB Shares") Nutanix Unified Storage Administration (NUSA) Course:
"Directory services configuration is the foundational step for SMB share deployment."(Module: "Nutanix Files SMB Implementation")
NEW QUESTION # 63
How many IP addresses are required by the client network when deploying Nutanix Files?
- A. One less IP address as the number of FSVMs
- B. Twice as many IP addresses as the number of FSVMs
- C. One additional IP address as the number of FSVMs
- D. The same number of IP addresses as the number of FSVM nodes
Answer: C
Explanation:
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 # 64
When hardening the network for Nutanix Objects, which is the only network endpoint that should be exposed to users?
- A. virbr0
- B. eth0
- C. S3
- D. OOB
Answer: C
Explanation:
When hardening the network for Nutanix Objects, the **S3 endpoint** is the only network endpoint that should be exposed to users. Nutanix Objects is an object storage solution that provides an S3-compatible API for accessing and managing objects. The S3 endpoint is the designated interface through which users and applications interact with Nutanix Objects, typically over HTTPS to ensure secure data transfer.
According to the **Nutanix Unified Storage Administration (NUSA)** course, network hardening for Nutanix Objects involves restricting access to only the necessary endpoints to minimize the attack surface.
The S3 endpoint, which operates over port 443 (HTTPS) or port 80 (HTTP, though HTTPS is recommended for security), is the primary entry point for client interactions. Exposing only this endpoint ensures that users can access object storage services while other internal or management interfaces remain protected.
The **Nutanix Certified Professional - Unified Storage (NCP-US)** study guide emphasizes that Nutanix Objects is designed to segregate user-facing traffic from internal system traffic. The S3 endpoint is configured during the deployment of Nutanix Objects and is associated with a virtual IP address (VIP) or DNS name that resolves to the object store. To harden the network, administrators should configure firewalls and network security groups to allow traffic only to the S3 endpoint, blocking access to other interfaces such as management or internal network endpoints.
The other options are not suitable for user exposure:
- **virbr0**: This is a virtual bridge interface typically used for internal virtualization networking (e.g., in KVM-based environments). It is not a user-facing endpoint and should not be exposed, as it is used for internal communication between virtual machines or services.
- **eth0**: This refers to a physical Ethernet interface on a node, which may carry various types of traffic (e.
g., storage, management, or VM traffic). Exposing eth0 directly to users would compromise security by allowing access to internal system communications.
- **OOB (Out-of-Band)**: This refers to out-of-band management interfaces, such as IPMI or iLO, used for hardware management. These are strictly for administrative purposes and must remain isolated from user access to prevent unauthorized control of the infrastructure.
The NUSA course documentation specifically notes that "Nutanix Objects network hardening requires exposing only the S3 endpoint to external users, typically through a load-balanced VIP, while ensuring all other interfaces, such as management or internal cluster networks, are isolated." This is achieved by configuring network segmentation, firewalls, and access control lists (ACLs) to restrict traffic to the S3 endpoint.
References:
- Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Objects: "Network configuration and hardening for Nutanix Objects, S3 endpoint exposure."
- Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Network security and endpoint configuration for Nutanix Objects."
- Nutanix Documentation (https://www.nutanix.com), Nutanix Objects Administration Guide: "Securing network access to S3 endpoints."
NEW QUESTION # 65
An administrator needs to recover a previous version of a file or share.
Which Nutanix Files feature should the administrator enable to allow this?
- A. Protection Policies
- B. Snapshot
- C. Self-Service Restore
- D. Data Protection
Answer: C
Explanation:
TheSelf-Service Restore (SSR)feature in Nutanix Files is designed to empower users and administrators to recover previous versions of files or entire shares. This feature leverages the snapshot capabilities of Nutanix Files to present earlier file versions directly to users for easy, self-directed recovery.
The NUSA and NCP-US materials highlight this:
"Self-Service Restore allows end users or administrators to restore individual files or folders from snapshots.
This minimizes administrator intervention and improves recovery times for file-level incidents." While snapshots and protection policies underlie the mechanism,Self-Service Restoreis thespecific feature that enables user-initiated recovery of earlier versions.
NEW QUESTION # 66
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. Change the Discovery IP to match the configured VIP.
- B. Add all missing CVM IPs in Discovery tab.
- C. Select the Enable multi-path checkbox.
- 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 # 67
Upon further investigation, the administrator notices the below message in the logs:
2024/07/25
10:55:23.937962 utils.go:32: [INFO] Start wget for file fraser-6.10- stable_build_release.json. Source: http://x.
x.x.x/release/builds/msp-builds/msp- services/464585393164.dkr.ecr,
us-west-2.amazonaws.com/nutanix-msp/idf-container/fraser-6.10- stable_build_release.json, Destination directory: /home/msp_config/airgap/
2024/07/25 10:55:23.945387 utils.go:32: [INFO] Start wget for file fraser-6.10- stable_build_release.tar.
xz. Source: http:/x.x.x.x/release/builds/msp-builds/msp- services/464585393164. dkr.ecr.us-west-2.
amazonaws.com/nutanix-msp/idf-container/fraser-6.10- stable_build_release.tar.xz, Destination directory: /home/msp_config/airgap/
2024/07/25 10:55:23.949580 utils.go:58: [ERROR] Failed to wget fraser-6.10- stable_build_release.tar.
xz from http://x.x.x.x/release/builds/msp-builds/msp-
services/464585393164.dkr.ecr.us-west-2.amazonaws.com/nutanix-msp/idf-container/fraser-6.10- stable_build_release.tar.xz; output: --2024-07-25 10:55:23-- http:/x.x.x.x/release/builds
/men-builds/men-services/464585393164 der ear 118-west-2.amazonaws.com/nutaniy-men/idf- stable_build_release.tar.xz. Source: http:/x.x.x.x/release/builds/msp-builds/msp- services/464585393164.dkr.ecr.us-west-2.amazonaws.com/nutanix-msp/idf-container/fraser-6.10- stable_build_release.tar.xz, Destination directory: /home/msp_config/airgap/
2024/07/25
10:55:23.949580 utils.go: 58: [ERROR] Failed to wget fraser-6.10- stable_build_release.tar.xz from http://x.x.
x.x/release/builds/msp-builds/msp-
services/464585393164. dkr.ecr.us-west-2.amazonaws.com/nutanix-msp/idf-container/fraser-6.10- stable_build_release.tar.xz: output: --2024-07-25 10:55:23-- http:/x.x.x.x/release/builds
/msp-builds/msp-services/464585393164.dkr.ecr.us-west-2.amazonaws.com/nutanix-msp/idf- container/fraser-6.10-stable_build_release.tar.xz Connecting to x.x.x.x:80... failed.
HTTP request sent, awaiting response... 404 Not Found
2024-07-25 10:55:23 ERROR 404 Not Found
What is the cause of this issue?
/msp-pias/msp-services/4104.akc.ecr.us-west-2.amazonaws.com/nutanix-msp/lar- container/fraser-6.10-stable_build_release.tar.xz Connecting to x.x.x.x:80... failed.
HTTP request sent, awaiting response... 404 Not Found
2024-07-25 10:55:23 ERROR 404: Not Found
What is the cause of this issue?
- A. MSP needs to reach the web server over port 443.
- B. Prism Central needs to reach the web server over port 80.
- C. Prism Central needs to reach the web server over port 443.
- D. MSP needs to reach the web server over port 80.
Answer: D
Explanation:
The log message indicates a failure to download the file fraser-6.10-stable_build_release.tar.xz from a web server, resulting in anHTTP 404 Not Founderror when attempting to connect to the server overport 80. The error suggests that the Microservices Platform (MSP) is attempting to access a resource via HTTP (port 80), but the connection fails, either because the server is not reachable, the resource is not available, or the port is blocked.
TheNutanix Unified Storage Administration (NUSA)course discusses the Microservices Platform (MSP) as a component that supports containerized services in Nutanix environments, often requiring access to external repositories for downloading build artifacts, such as those hosted on AWS ECR (Elastic Container Registry).
The course notes that "MSP services may require outbound network access to download container images or configuration files, typically over HTTP (port 80) or HTTPS (port 443), depending on the repository configuration." In this case, the log explicitly shows the attempt to useHTTP (port 80)to access the URL http://x.x.x.x/..., indicating that MSP is configured to use HTTP for this operation. The HTTP 404 Not Founderror suggests that either the file does not exist at the specified URL, the server is not responding, or network connectivity issues (e.g., firewall rules blocking port 80) are preventing MSP from reaching the web server. Since the error occurs during the connection attempt over port 80, the most likely cause is thatMSP needs to reach the web server over port 80, and this connectivity is not properly configured or is blocked.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide emphasizes troubleshooting network connectivity for Nutanix services, stating, "Administrators must ensure that required ports, such as
80 for HTTP or 443 for HTTPS, are open for services like MSP to access external resources." The guide also recommends checking firewall rules, proxy settings, and network routes when encountering connectivity errors like HTTP 404.
The provided search results further support this analysis. For example, troubleshooting connectivity issues in Nutanix environments often involves verifying port access, as seen in discussions about Pulse and other services requiring HTTP (port 80) or HTTPS (port 443) connectivity to external servers (e.g., nsc01.nutanix.
net or insights.nutanix.com). While the specific issue in the log is related to MSP, the principle of ensuring proper port access applies.
The other options are incorrect:
* Prism Central needs to reach the web server over port 443: The log indicates that MSP, not Prism Central, is attempting the connection, and it uses HTTP (port 80), not HTTPS (port 443).
* MSP needs to reach the web server over port 443: The log clearly shows the connection attempt over HTTP (port 80), not HTTPS (port 443).
* Prism Central needs to reach the web server over port 80: The log references MSP, not Prism Central, as the component attempting the download.
To resolve this issue, the administrator should:
* Verify that the web server at x.x.x.x is reachable and the file exists at the specified URL.
* Ensure that outbound traffic from the MSP service to the web server over port 80 is allowed by checking firewall rules, proxy settings, and network configurations.
* If the server requires HTTPS, update the MSP configuration to use port 443 instead of port 80, but the log suggests port 80 is expected.
References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Troubleshooting: "Network connectivity for MSP and external repository access." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 4: Troubleshoot Nutanix Unified Storage, Subtopic: "Diagnosing network connectivity issues for Nutanix services." Nutanix Documentation, MSP Administration Guide: "Configuring network access for MSP container downloads." Nutanix Community, Pulse Configuration and Connection Troubleshooting: "Ensuring port 80 and 443 access for external services."
NEW QUESTION # 68
An administrator has configured a share in Nutanix Files to support clients using Windows and Linux. A user on an Ubuntu client is unable to create any files. Which share configuration option should be updated?
- A. Modify NFS Client Access to read-write
- B. Add NTFS permissions for the user account
- C. Update the blocked file types in the file server
- D. Allow simultaneous read access to same files
Answer: A
Explanation:
The issue involves a user on an Ubuntu client (a Linux-based system) who is unable to create files on a Nutanix Files share configured to support both Windows and Linux clients. Since Ubuntu typically uses the NFS protocol to access file shares, the problem is likely related to the NFS configuration on the Nutanix Files share. The correct action is tomodify NFS Client Access to read-write, as the current setting may be restricting the Ubuntu client to read-only access.
TheNutanix Unified Storage Administration (NUSA)course explains that "Nutanix Files supports NFS for Linux clients, and administrators can configure NFS Client Access settings to control permissions, such as read-only or read-write access, for specific clients or subnets." If the NFS Client Access is set to read-only for the Ubuntu client's IP or subnet, the user would be able to read files but not create or modify them, which matches the described issue.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further states that
"troubleshooting access issues for Linux clients on Nutanix Files often involves verifying the NFS Client Access settings, ensuring that the client has read-write permissions to create or modify files on NFS shares." The administrator should check the NFS export settings for the share and update the client access rules to grant read-write permissions to the Ubuntu client's IP address or subnet.
The other options are incorrect:
* Allow simultaneous read access to same files: This setting is relevant for managing concurrent access to files (e.g., in SMB environments) but does not address the Ubuntu client's inability to create files via NFS.
* Update the blocked file types in the file server: Blocked file types prevent specific file extensions from being stored, but the issue is about creating files, not a specific file type being blocked.
* Add NTFS permissions for the user account: NTFS permissions are relevant for SMB shares used by Windows clients, not for NFS shares accessed by Linux clients like Ubuntu.
The NUSA course documentation emphasizes that "for Linux clients experiencing permission issues on NFS shares, administrators should review and modify the NFS Client Access settings to ensure read-write permissions are granted, resolving issues like the inability to create files." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: "Configuring NFS shares and client access permissions." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 4: Troubleshoot Nutanix Unified Storage, Subtopic: "Diagnosing NFS access issues for Linux clients." Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: "NFS Client Access configuration for read-write permissions."
NEW QUESTION # 69
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?
- A. Configure Events Quotas
- B. Set Ransomware Email Recipient
- C. Define Anomaly Rules
- D. Create an Alert Policy
Answer: C
Explanation:
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 # 70
An administrator is trying to configure Mutual CHAP on a Linux guest. During configuration, the administrator keeps getting an Authentication Failure error.
What should the administrator do to resolve the issue?
- A. Configure the password on the client, leave the target password blank.
- B. Configure the password on the target, leave the client password blank.
- C. Configure the client and target with different passwords.
- D. Configure the client and target with the same password.
Answer: D
Explanation:
Mutual CHAP(Challenge-Handshake Authentication Protocol) is used in Nutanix Unified Storage for secure two-way authentication between an iSCSI initiator (client) and the target (VG in Nutanix).
For successful mutual authentication,both the client and the target must use the same CHAP secret:
* The initiator uses this secret to authenticate the target.
* The target uses the same secret to authenticate the initiator.
The NCP-US and NUSA course materials clearly state:
"Mutual CHAP requires the same CHAP secret to be configured on both the iSCSI initiator (client) and target.
Mismatched secrets will result in authentication failures."
In this scenario, the error is because the secrets do not match. Setting thesame password on bothresolves the issue.
NEW QUESTION # 71
......
Verified & Correct NCP-US-6.10 Practice Test Reliable Source Mar 07, 2026 Updated: https://www.prepawayete.com/Nutanix/NCP-US-6.10-practice-exam-dumps.html
Nutanix NCP-US-6.10 Exam Preparation Guide and PDF Download: https://drive.google.com/open?id=1vtSn3RGtmJx-DGFXe7sLLOZwqCeGtNm5