Jun-2026 New Version NCP-US-6.10 Certificate & Helpful Exam Dumps is Online
NCP-US-6.10 Free Certification Exam Material with 108 Q&As
NEW QUESTION # 26
Question:
An administrator has been asked to lock a file indefinitely. The lock can be explicitly removed only by authorized users.
Which configuration matches the requirements of this task?
- A. Nutanix Objects Legal hold
- B. Blocked File Types for Files
- C. Nutanix Objects with WORM versioning
- D. Data Lens Ransomware Protection
Answer: A
Explanation:
Legal Holdin Nutanix Objects is a feature designed for compliance and regulatory use cases, ensuring that specific objects (files)cannot be deleted or modified for an indefinite period, even if WORM (Write Once Read Many) policies exist.
Here's how it matches the scenario:
Indefinite Lock:
* Legal Hold ensures that once applied, the object islocked indefinitely.
* Unlike WORM retention, which is based ona fixed duration (like days/months), Legal Hold hasno expirationuntil an authorized administrator explicitly removes it.
Authorized Removal Only:
* Only users withspecific Legal Hold management permissionscan remove the lock, maintaining compliance and governance integrity.
The NUSA course materials emphasize:
"Legal Hold is a compliance feature that prevents deletion or modification of specific objects. It can only be lifted by authorized administrators, ensuring that the data remains immutable as long as required by legal or regulatory processes." The other options:
WORM versioning- locks data for afixed retention period; it does not provide indefinite locking.
Data Lens Ransomware Protection- focuses on monitoring for anomalies, not explicit file locking.
Blocked File Types for Files- prevents certain files from being uploaded but does not lock already uploaded files.
Thus, toindefinitely lock a filein Nutanix Objects, the administrator should useLegal Hold.
NEW QUESTION # 27
Which Nutanix Objects metric provides the total input requests per second of a bucket?
- A. Gets
- B. NFS Reads
- C. Puts
- D. Throughput
Answer: C
Explanation:
In Nutanix Objects metrics:
* Puts: Measures PUT requests per second (object uploads), representing input operations.
* Gets (Option C): Measures output (download) requests.
* Throughput (Option B): Reports bandwidth (MB/s), not request rate.
* NFS Reads (Option D): Specific to NFS access, not general bucket input.
Reference:Nutanix Objects Administration Guide:
"The Puts metric tracks the number of successful object write operations (PUTs) per second to a bucket, indicating input request volume."(Chapter: "Monitoring Object Store Performance") Nutanix Unified Storage (NCP-US) Study Material:
"Use the 'Puts' metric to monitor ingress request rates for capacity planning and performance tuning."(Section:
"Objects Performance Analysis")
NEW QUESTION # 28
Question:
An administrator has been advised to access the Nutanix Files Server VM and ensure that passwords meet the organization's security policy for server access.
Which password complexity requirement does Nutanix Files support?
- A. At least 2 lowercase letters
- B. At least 2 uppercase letters
- C. At least 8 characters difference
- D. At least 8 characters long
Answer: D
Explanation:
When accessing Nutanix Files FSVMs (File Server VMs), Nutanix enforcespassword complexity policiesto meet common security standards. According to the NCP-US and NUSA materials, the defaultminimum requirementfor password complexity is:
"Passwords must be at least 8 characters long, supporting uppercase letters, lowercase letters, numbers, and special characters. However, the absolute minimum is an 8-character length." This ensures that even if the environment does not enforce uppercase/lowercase mixes or special character usage, theabsolute minimum lengthof8 charactersmust be met. This requirement ensures protection against basic dictionary attacks.
The other options (specific numbers of uppercase or lowercase letters, or a difference of 8 characters from previous passwords) arenot specifically requiredby Nutanix Files out-of-the-box.
NEW QUESTION # 29
At what level of granularity can Smart DR replicate?
- A. Volume
- B. Share
- C. File
- D. Bucket
Answer: B
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 # 30
Question:
An administrator is preparing to deploy Nutanix Objects on an AHV-based Nutanix cluster in a multi-cluster environment. The Virtual IP address and Data Services IP address have already been configured on the AHV cluster.
Which additional IP address should be configured for successful Objects deployment?
- A. Data Services IP on cluster where Prism Central is deployed
- B. Fallback Virtual IP of Prism Element on AHV cluster
- C. IPv6 address of Prism Element on AHV cluster
- D. Fallback Virtual IP on cluster where Prism Central is deployed
Answer: D
Explanation:
When deploying Nutanix Objects in amulti-cluster environment, Prism Central coordinates deployment across clusters.
In the NUSA deployment module, it's emphasized:
"Prism Central requires a Fallback Virtual IP (VIP) on the cluster it manages to ensure management traffic can be redirected even if a CVM or Prism Element service fails." Thus, theFallback Virtual IP on the cluster where Prism Central is deployedis a critical additional IP address for:
Ensuring management continuity
Supporting Object service deployment across clusters
The other options (like IPv6 or DSIP on Prism Central's cluster) are not required specifically for Nutanix Objects deployment.
NEW QUESTION # 31
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. Enable WORM.
- B. Use NFS for shares.
- C. Disable DFS on the share.
- D. Use homes as the share type.
Answer: C
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 # 32
When hardening the network for Nutanix Objects, which is the only network endpoint that should be exposed to users?
- A. virbr0
- B. S3
- C. eth0
- D. OOB
Answer: B
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 # 33
An administrator needs to configure an SMB share for the user profiles in a company. Which network share type is most suitable for this task?
- A. A connected share
- B. A distributed share
- C. A standard share
- D. A WORM share
Answer: B
Explanation:
To configure an SMB share for user profiles in a company using Nutanix Files, the most suitable network share type is a **distributed share**. User profiles typically require a share that can scale with the number of users, provide high availability, and ensure consistent performance across multiple clients. A distributed share in Nutanix Files is designed to meet these needs by distributing data and workload across all File Server Virtual Machines (FSVMs) in the file server, ensuring scalability and load balancing.
The **Nutanix Unified Storage Administration (NUSA)** course states, "A distributed share in Nutanix Files is ideal for workloads like user profiles, as it leverages all FSVMs to provide scalability, high availability, and consistent performance for large numbers of concurrent users." Distributed shares are optimized for environments where multiple users access the share simultaneously, such as in user profile scenarios where each user has a profile folder accessed via SMB. This share type ensures that the workload is balanced across FSVMs, preventing any single FSVM from becoming a bottleneck.
The **Nutanix Certified Professional - Unified Storage (NCP-US)** study guide further elaborates that
"distributed shares are recommended for user profile storage in Nutanix Files, as they provide seamless scalability and fault tolerance by distributing data across all FSVMs in the file server." This is particularly important for user profiles, which are often accessed during login/logout events, requiring low latency and high concurrency support.
The other options are incorrect:
- **A standard share**: A standard share is hosted on a single FSVM, which can become a performance bottleneck and lacks the scalability needed for user profiles with many concurrent users.
- **A connected share**: There is no such share type as a "connected share" in Nutanix Files; this term is not applicable.
- **A WORM share**: A WORM (Write Once, Read Many) share is designed for immutable data retention (e.g., for compliance), not for user profiles, which require frequent read/write operations.
The NUSA course documentation emphasizes that "distributed shares are the best choice for user profile storage in Nutanix Files, ensuring scalability and performance for enterprise environments with many users." References:
- Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: "Configuring distributed shares for user profiles."
- Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Share types in Nutanix Files for user workloads."
- Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: "Distributed shares for user profile storage."
---
NEW QUESTION # 34 
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 storage network.
- B. Allow port 445 in the firewall.
- C. Re-deploy File Analytics on the Files client network.
- D. Allow port 139 in the firewall.
Answer: C
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 # 35
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. Access Based-Enumeration (ABE)
- B. Role Based Access Control (RBAC)
- C. File Analytics
- D. Files blocking
Answer: A
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 # 36
Question:
What is the most likely cause no Prism Element clusters are listed when trying to create a new object store?
- A. Although Prism Element is registered, object stores cannot be added via Prism Central.
- B. Prism Element has not yet completed synchronization with Prism Central.
- C. Prism Element cluster CVMs must be restarted after registration.
- D. The administrator did not manually sync Prism Element to Prism Central after registration.
Answer: B
Explanation:
When creating a new Nutanix Objects instance viaPrism Central, Prism Central must havecompleted synchronizationwith the Prism Element cluster(s). This synchronization ensures that:
Cluster details and resources(such as available storage, network configurations, and capacity) are properly displayed in Prism Central.
Prism Central can create and manage Object Storesbased on accurate data from the registered cluster.
From the NUSA deployment module:
"After registering Prism Element clusters in Prism Central, there is an initial synchronization process that must complete before clusters appear in workflows such as object store creation." The other options:
Manual syncis not required; Prism Central automatically synchronizes after registration.
CVM restartsare not part of the normal registration or synchronization process.
Object stores can indeed be added via Prism Centralonce the sync is complete.
Therefore, the administrator shouldwait for Prism Central and Prism Element to finish synchronizing before proceeding.
NEW QUESTION # 37
An administrator is tasked with upgrading Objects Manager to the latest release that came out earlier in the week. The administrator has navigated to the LCM page in Prism Central and does not see the latest version of Objects Manager as an available upgrade. What is the likely reason the administrator does not see the current release of Objects Manager as an available upgrade?
- A. An LCM inventory has not been performed
- B. The administrator is logged in as local admin rather than a domain admin
- C. Prism Central needs to be scaled out
- D. The administrator needs to perform the upgrade through Prism Element
Answer: A
Explanation:
The administrator is attempting to upgrade Objects Manager (a component of Nutanix Objects) using Prism Central's Lifecycle Manager (LCM) but does not see the latest version, which was released earlier in the week (prior to June 05, 2025). The most likely reason is thatan LCM inventory has not been performed. LCM requires an inventory operation to check for available updates by querying Nutanix's external repositories or a dark site server (if configured), and without this step, the latest version of Objects Manager will not appear in the LCM page.
TheNutanix Unified Storage Administration (NUSA)course states, "Before upgrading components like Objects Manager via LCM, an inventory must be performed in Prism Central to retrieve the latest available versions from Nutanix repositories." The inventory process updates the LCM catalog with the latest software versions, including Objects Manager, ensuring that the administrator can see and select the new release for upgrade. If the inventory has not been run recently, LCM will only show versions that were available during the last inventory, which may not include the latest release from earlier in the week.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further elaborates that "a common reason for missing the latest component versions in LCM is the failure to perform an inventory; administrators must run an LCM inventory to ensure the latest versions, such as new releases of Objects Manager, are available for upgrade." Since the latest version was released recently, an inventory is necessary to refresh the LCM catalog.
The other options are incorrect:
* The administrator is logged in as local admin rather than a domain admin: The issue is not related to the type of admin account (local vs. domain). Both local and domain admins can perform LCM inventories and upgrades if they have the necessary permissions, and there is no indication of a permission error.
* The administrator needs to perform the upgrade through Prism Element: LCM upgrades for Nutanix Objects components, including Objects Manager, are performed through Prism Central, not Prism Element, as Prism Central provides centralized management for such operations.
* Prism Central needs to be scaled out: Scaling out Prism Central (e.g., adding more VMs) is not required to see available upgrades in LCM. The issue is related to the inventory process, not Prism Central's scale.
The NUSA course documentation emphasizes that "running an LCM inventory is a critical step to ensure the latest versions of components like Objects Manager are visible in Prism Central for upgrades, especially for recent releases." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Lifecycle Management: "Performing LCM inventory for component upgrades." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 1: Deploy and Upgrade Nutanix Unified Storage, Subtopic: "LCM inventory process for Nutanix Objects upgrades." Nutanix Documentation (https://www.nutanix.com), LCM Administration Guide: "Running inventory to check for available upgrades."
NEW QUESTION # 38
An administrator has a primary Nutanix Files instance running on an ESXi-based Nutanix cluster. An identical Files instance has been configured at a secondary site for disaster recovery purposes with less than
5ms latency between sites.
Management has asked that the primary Files instance be configured in such a way that provides a zero RPO.
Which File Server option needs to be enabled to support the request?
- A. vSphere Cluster Availability
- B. vSphere Cluster Services
- C. Metro Protection Domain
- D. Metro Protection Policy
Answer: C
Explanation:
The Nutanix Unified Storage Administration (NUSA) course, in the module "Configuring Metro Availability for Nutanix Files," specifies that for zero RPO between two Nutanix Files instances, aMetro Protection Domain (Metro PD)must be enabled. This synchronous replication method ensures zero data loss (RPO = 0) and near-instantaneous failover capability between two sites with low latency.
The course states:
"For Nutanix Files running on two clusters with <5ms latency, Metro Protection Domains enable synchronous replication of Files data, ensuring zero RPO in the event of a failure." Reference:
Nutanix Unified Storage Administration (NUSA) course - Module: Configuring Metro Availability for Nutanix Files.
Nutanix Unified Storage (NCP-US) Study Guide - Topic: Zero RPO with Metro Protection Domains.
NEW QUESTION # 39
What is the default password expiry for the machine account used to integrate Nutanix Files with Active Directory?
- A. 30 days
- B. 0 days
- C. 90 days
- D. 60 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 # 40 
An administrator is currently troubleshooting a failed Nutanix Objects deployment using LCM and sees the error message shown in the exhibit.
The Objects cluster deployment is experiencing the following symptoms:
* The Objects Home UI Page shows the error: unable to pull the docker images
* The docker pull is failing on the first image
The administrator determined that MSP cluster deployment has completed successfully looking at msp_controller.out.
Which log file should the administrator use to investigate and troubleshoot this issue further?
- A. cluster_health.out
- B. aoss_service_manager.out
- C. domain_manager.out
- D. 1cm_metrics_uploader.out
Answer: B
Explanation:
According to the Nutanix Unified Storage Administration (NUSA) course, in theTroubleshooting Nutanix Objects Deploymentsection, the aoss_service_manager.out log file is explicitly responsible for tracking the status and lifecycle of container services, including pulling Docker images during the deployment of Nutanix Objects.
This log file is where administrators should look for:
* Container image pull attempts
* Any errors during docker pull actions
* Overall container service management actions and errors
The module"Deploying and Troubleshooting Nutanix Objects"from the NUSA course states:
"During deployment of Nutanix Objects, the aoss_service_manager.out log file provides detailed status information regarding container image pulls, container lifecycle events, and object service startup procedures.
This log file is essential when troubleshooting deployment failures related to container image downloads." The other log files listed in the question are used for different components:
* domain_manager.out:Related to domain services and identity management.
* 1cm_metrics_uploader.out:Responsible for uploading metrics, not related to container image pulls.
* cluster_health.out:Used for overall cluster health, but not specific to container lifecycle events.
Reference:
Nutanix Unified Storage Administration (NUSA) course - Module: Deploying and Troubleshooting Nutanix Objects - Section: Key Logs for Troubleshooting Nutanix Objects Deployment.
Nutanix Unified Storage (NCP-US) Study Guide - Topic: Nutanix Objects Deployment Troubleshooting.
NEW QUESTION # 41
An administrator is tasked with migrating physical SQL workloads from a legacy SAN platform to a newly- deployed Nutanix environment. The current physical hosts boot from SAN. The Nutanix environment has plenty of storage resources available. Which action can the administrator take to complete this task?
- A. Boot using the NFS protocol with Nutanix Files
- B. Boot using PXE protocol with Nutanix Files
- C. Boot over iSCSI using Nutanix Volumes
- D. Boot using Nutanix Object stores
Answer: C
Explanation:
To migrate physical SQL workloads from a legacy SAN platform where hosts boot from SAN to a Nutanix environment, the administrator can useNutanix Volumesto enable booting overiSCSI. Nutanix Volumes is a block storage solution that provides iSCSI-based storage, allowing external hosts (such as physical servers) to access Nutanix storage as block devices. This is ideal for replacing SAN-based boot volumes, as it supports the same iSCSI protocol used in traditional SAN environments.
According to theNutanix Unified Storage Administration (NUSA)course, Nutanix Volumes enables external hosts to connect to Nutanix storage via iSCSI, which can be used for boot volumes or data volumes.
The course emphasizes that "Nutanix Volumes supports iSCSI boot for physical servers, making it a suitable solution for migrating workloads from legacy SAN environments to Nutanix." This allows the administrator to configure the physical SQL servers to boot from iSCSI targets provisioned on Nutanix Volumes, leveraging the Nutanix cluster's storage resources.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further details that Nutanix Volumes can be configured to present iSCSI LUNs to physical hosts, which can be used for both operating system boot and application data storage. For the SQL workloads, the administrator can create iSCSI targets on Nutanix Volumes, configure the physical hosts' iSCSI initiators to connect to these targets, and migrate the boot and data volumes from the legacy SAN to Nutanix.
The other options are not suitable for this task:
* Boot using PXE protocol with Nutanix Files: Nutanix Files is a file storage solution that supports SMB and NFS protocols, not PXE (Preboot Execution Environment) booting. PXE is typically used for network-based OS installation, not for booting SQL workloads or replacing SAN-based boot volumes.
* Boot using the NFS protocol with Nutanix Files: Nutanix Files supports NFS for file sharing, but NFS is not designed for booting physical servers. It is used for file-level access, not block-level access required for boot volumes.
* Boot using Nutanix Object stores: Nutanix Objects is an object storage solution designed for S3- compatible APIs, not for block or file-based booting. It is unsuitable for hosting bootable volumes or SQL workloads.
The NUSA course documentation highlights that "Nutanix Volumes provides a seamless migration path for SAN-based workloads, including boot-from-SAN configurations, by leveraging iSCSI to present storage to physical hosts." This makes it the only viable option for the described migration task.
References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Volumes: "Configuring iSCSI for external hosts and boot volumes." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 1: Deploy and Upgrade Nutanix Unified Storage, Subtopic: "Nutanix Volumes for SAN workload migration." Nutanix Documentation (https://www.nutanix.com), Nutanix Volumes Administration Guide: "Using iSCSI for boot and data volumes."
NEW QUESTION # 42
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. Full Administrator
- D. Infra 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 # 43
An administrator is concerned that storage in the Nutanix File Server is being used to store personal photos and videos. How can the administrator determine if this is the case?
- A. Examine the File Distribution by Type widget from the Files Console for the File Server.
- B. Examine the Usage Summary table for the File Server Container in the Prism Element Storage page.
- C. Examine the File Activity widget in the File Analytics dashboard for the File Server.
- D. Examine the File Distribution by Type widget in the File Analytics dashboard for the File Server.
Answer: D
Explanation:
To determine if the Nutanix File Server is being used to store personal photos and videos, the administrator shouldexamine the File Distribution by Type widget in the File Analytics dashboard for the File Server.
Nutanix File Analytics is a monitoring and analytics tool that provides detailed insights into file share activities, including the types of files stored on the file server. The File Distribution by Type widget specifically categorizes files by their extensions (e.g., .jpg, .mp4), allowing the administrator to identify whether image or video files are present.
TheNutanix Unified Storage Administration (NUSA)course states, "The File Analytics dashboard includes the File Distribution by Type widget, which displays the breakdown of file types stored on the Nutanix File Server, enabling administrators to identify specific file categories such as images or videos." This widget provides a visual representation of file types, making it easy to detect if personal photos (e.g., .jpg, .png) or videos (e.g., .mp4, .avi) are being stored.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further elaborates that "File Analytics offers granular visibility into file storage patterns through widgets like File Distribution by Type, which is ideal for identifying unauthorized or non-business-related content, such as personal media files." By accessing this widget in the File Analytics dashboard, the administrator can confirm the presence of photo and video files and take appropriate action, such as setting policies to restrict such content.
The other options are incorrect or insufficient:
* Examine the Usage Summary table for the File Server Container in the Prism Element Storage page: The Usage Summary table in Prism Element provides high-level storage metrics (e.g., capacity usage) but does not break down data by file type, so it cannot identify photos or videos.
* Examine the File Activity widget in the File Analytics dashboard for the File Server: The File Activity widget shows file access patterns (e.g., read/write operations) but does not provide details about file types, making it unsuitable for this purpose.
* Examine the File Distribution by Type widget from the Files Console for the File Server: The Nutanix Files Console is used for managing file servers and shares, but it does not include a File Distribution by Type widget. This widget is specific to the File Analytics dashboard.
The NUSA course documentation highlights that "the File Distribution by Type widget in File Analytics is a key tool for auditing file content, allowing administrators to detect and manage non-compliant or personal files, such as photos and videos, stored on the file server." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on File Analytics: "Using the File Analytics dashboard to monitor file types and storage patterns." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 3: Analyze and Monitor Nutanix Unified Storage, Subtopic: "File Analytics and file type distribution analysis." Nutanix Documentation (https://www.nutanix.com), Nutanix File Analytics Guide: "File Distribution by Type widget for file content auditing."
NEW QUESTION # 44
An administrator has recently added several NGT-enabled VMs with in-guest iSCSI initiators to a Volume Group (VG) using IP addresses in the VG allowlist. Several days later, the administrator restored the VG, after which the VMs lost connectivity to the Volume Group.
What should the administrator have done differently to prevent this from happening?
- A. Use the NIC MAC address of the VM's in the VG allow list.
- B. Use the VM UUID in the VG allow list.
- C. Use the VM hostname in the VG allowlist.
- D. Use the iSCSI IQN entry in the VG allowlist.
Answer: D
Explanation:
Volume Groups (VGs) require persistent identifiers for initiators in the allowlist. IP addresses can change during VM restores/reboots, breaking connectivity. The iSCSI Qualified Name (IQN) is a static, unique identifier for iSCSI initiators and persists across VM operations, ensuring stable access.
* Option B/C/D (VM UUID, hostname, MAC): These are unrelated to iSCSI authentication. Nutanix Volume Groups exclusively use IQNs or IPs (not recommended) for allowlisting.
Reference:Nutanix Unified Storage Administration (NUSA) Course Study Guide:
"Always use iSCSI IQN in Volume Group allowlists for NGT-enabled VMs. IP addresses are ephemeral and may change after restores, causing connectivity loss."(Section: "Configuring Volume Group Access Control") (Module: "Nutanix Volumes Best Practices") Nutanix Volumes Documentation:
"For persistent iSCSI connectivity, configure the allowlist with initiator IQNs instead of dynamic IP addresses."(Source: Volumes Configuration Guide, "Allowlist Management")
NEW QUESTION # 45
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. Sufficient nodes in the cluster is greater than current number of FSVMs.
- B. Sufficient storage container space is available to host the volume groups.
- C. Ensure Files Analytics is installed.
- D. Ensure network ports are available.
Answer: A
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 # 46
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. Select the Enable multi-path checkbox.
- B. Remove Discovery IP and configure with DSIP.
- C. Change the Discovery IP to match the configured VIP.
- D. Add all missing CVM IPs in Discovery tab.
Answer: B
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 # 47
Question:
What would an administrator need to do in order to move tagged objects to a remote Nutanix Objects instance after a period of time?
- A. Configure WORM on the Bucket and a Lifecycle Policy to tier tagged objects within the bucket.
- B. Configure a Cloud Bucket Endpoint with the Nutanix provider and a Lifecycle Policy to tier all objects within the bucket.
- C. Configure a Cloud Bucket Endpoint with the Nutanix provider and a Lifecycle Policy to tier tagged objects within the bucket.
- D. Configure WORM on the Bucket and a Lifecycle Policy to tier all objects within the bucket.
Answer: C
Explanation:
Lifecycle Policiesin Nutanix Objects allow administrators toautomate data tiering and archivalbased on specific criteria, including object tagging. According to the NUSA training:
"A Lifecycle Policy, combined with a Cloud Bucket Endpoint, enables automatic movement of objects (based on tags) to a remote Nutanix Objects instance or compatible S3 storage." Here's the detailed process:
The administrator first configures aCloud Bucket Endpointto establish connectivity to theremote Nutanix Objects instance.
Then, they create aLifecycle Policythat targets objects with specific tags for tiering.
This policy ensures that onlytagged objectsmeeting the policy's criteria are moved to the remote storage location.
Enabling WORM on the bucket is not required for tiering; WORM is forimmutability. Thekey mechanism for tiering tagged objects is:
#Cloud Bucket Endpoint + Lifecycle Policy for tagged objects.
NEW QUESTION # 48
......
Get The Important Preparation Guide With NCP-US-6.10 Dumps: https://freedumps.actual4exams.com/NCP-US-6.10-real-braindumps.html