An administrator has created a multi-protocol department share on Nutanix Files with the following configuration:Max Size of 800GB -SMB is configured as the primary protocol NFS is configured for read-write access Quota policy for AD group HR, limiting to 20GB A second quota policy of 30GB was set for AD group Finance A user who is a member of the HR group has begun receiving daily email notifications, telling them that they have consumed all available space. However, they are still able to write new files. Another user who is a member of the Finance AD group and uses a Linux workstation is able to write files and receives no email notification. What should an administrator do to restrict the HR user from writing new data?
Answer(s): B
Why option B – “Set hard-limit enforcement” – is the correct actionNutanix Files enforces quotas at the policy level. When a quota is defined for an AD group (e.g., HR = 20 GB, Finance = 30 GB) it operates in soft-limit mode by default. A soft limit only generates a warning/email when the threshold is crossed; the user can still write data until the hard limit is reached. The email the HR user receives indicates that the soft limit has been exceeded, but because the hard limit has not been enabled, writes are still permitted. To truly prevent further writes once the quota is exhausted, the administrator must activate the hard-limit enforcement for the HR group’s quota policy. This causes any subsequent write attempts to be rejected with an “insufficient space” error, eliminating the ability to continue storing new files.Why the other choices are not appropriateA: Reduce the Finance quota limit – The Finance quota is unrelated to the HR user’s consumption; lowering it would not affect HR’s ability to write data. C: Remove the default quota policy – Removing the policy eliminates all quota enforcement, which would allow unlimited writes for every user, worsening the problem rather than solving it. D: Set a user level quota – While a user-level quota could also cap the HR user, the question specifically asks what should be done to restrict the HR user in the context of the existing AD-group quota design. The proper, policy-driven method is to enforce the hard limit on the existing HR group quota, not to add a separate user-level rule.Step-by-step technical justification1. Verify that the HR AD group quota is configured with a soft limit of 20 GB. 2. Enable hard-limit enforcement on that quota policy (via the Nutanix Files UI or REST API).3. Once hard limits are active, any write attempt by an HR member that would exceed 20 GB results in an “insufficient space” error, preventing further file creation. 4. The existing email notification will still be generated when the soft limit is crossed, but writes will be blocked, effectively restricting the user.
Nutanix Files Administration Guide – Quotas : https://docs.nutanix.com/books/frameset/admin/nutanix-files/quotas.html Managing AD-Group Quotas in Nutanix Files : https://docs.nutanix.com/books/frameset/admin/nutanix-files/ad-group-quotas.htmlThese documents detail how soft and hard limits work, how to configure them for AD groups, and the impact of enabling hard-limit enforcement on write operations.
Refer to the exhibits.An administrator has received a complaint from a user that the Windows VM had a service disruption that caused it to randomly lose access to an iSCSI Volume Group (VG) during a maintenance window of an ESXi-based Nutanix cluster. The cluster configuration is as follows: Six-node cluster: ESXi IP addresses: 172.20.100.41 to 172.20.100.46 vCenter IP address: 172.20.100.40 CVM IP addresses: 172.20.100.101 to 172.20.100.106 Virtual IP (VIP): 172.20.100.200 Data Services IP (DSIP): 172.20.100.50 The administrator retrieved the configuration from the VM. as shown in the exhibit. After reviewing the VM iSCSI configuration, they found that the iSCSI is not properly configured. What recommended change should the administrator make to resolve this disruption?
Answer(s): A
A company is managing two Nutanix clusters between two different availability zones:One on-prem -One running in the public cloud (NC2) The company is evaluating Nutanix Files and are looking for a solution that supports: 15 minute RPO or lessGuided DR process -Minimal operations at failover time Which data protection strategy should be considered?
Answer(s): D
JustificationSmart DR (Option D) is designed specifically for cross-zone disaster-recovery with an automated, guided workflow that can achieve RPOs of 15 minutes or less. It orchestrates replication of files from the on-premises cluster to the NC2 cloud, handles failover execution, and minimizes manual tasks when switching over. Smart Sync (Option A) provides low-latency, cache-level replication for workload-level consistency but does not include a built-in, step-by-step DR orchestration process; it is focused on keeping a secondary storage in sync rather than managing failover. Protection Domain (Option B) groups resources for backup and restore but does not natively support 15-minute RPO guarantees or automated failover across two distinct sites; its primary purpose is snapshot-based protection within a single cluster. Cloud Connect (Option C) enables movement of VM images or files into a cloud bucket for long-term retention, yet it lacks real-time replication, granular RPO control, and a guided failover procedure required for immediate DR scenarios.Therefore, Smart DR is the only option that meets the dual requirements of sub-15-minute RPO and a fully guided, low-operation failover process for cross-zone protection.
1. Nutanix Files Smart DR – https://files.nutanix.com/cev2/?l=/nlp/smart-dr 2. Nutanix Files Protection Domains Overview – https://files.nutanix.com/cev2/?l=/nlp/protection-domain
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?
Answer(s): A – Create a Federated NamespaceThe architecture requires a common namespace that spans multiple geographically-separate object-store instances while preserving their individual Prism Central domains. Federated Namespace is the Nutanix Acropolis (now Calm/Frame) concept that ties together multiple object stores under a single globally-unique namespace, enabling seamless cross-region data access and replication. It is explicitly designed for scenarios where each region has its own Prism Central but needs a unified namespace for applications and services that consume data across both sites.Why the other options are not suitableFile System Namespace – provides a unified POSIX-compatible file system view; it does not address the need for a global namespace across distinct object stores and therefore cannot expose the underlying S3-compatible buckets in a unified manner. Global Namespace – this term is sometimes used interchangeably with “Federated Namespace” but in Nutanix documentation it refers to a specific global namespace service that requires a separate service tier and is not the intended method for simply joining multiple Prism Central-managed object stores under a shared namespace. Kubernetes Namespace – is a logical network partition for Kubernetes resources; it is unrelated to storage namespace federation and would not provide the required cross-region object-store semantics.
Nutanix Acropolis File Services – Federation Overview: https://docs.nutanix.com/acropolis-project-5-15/acropolis-fileservices/overview-federation.html Configuring Cross-Region Object Store Replication: https://support.nutanix.com/s/article/000042135
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?
Technical JustificationNutanix Objects – Legal Hold (Option D) provides an immutable lock on a stored object that can only be released by users who possess the Legal Hold Management privilege. The lock is persistent until an authorized administrator explicitly removes it, satisfying the requirement for indefinite protection with controlled removal. Blocked File Types for Files (Option A) merely restricts which file extensions may be uploaded; it does not place any retention or lock flag on the object, so the file remains deletable by any privileged user. Nutanix Objects with WORM versioning (Option B) enforces write-once and read-only semantics for a version, but the WORM state is tied to version creation and can be superseded by later versions; it does not provide a distinct, admin-only removal flow for a single object. Data Lens Ransomware Protection (Option C) is a detection and quarantine mechanism that automatically isolates suspicious files; it does not offer a configurable, authorized-removal lock that can be deliberately maintained indefinitely.Conclusion – The only feature that directly implements a persistent, authorized-only unlock capability is Nutanix Objects Legal hold .
Nutanix Prism Web UI – Legal Hold Management: https://portal.nutanix.com/page.html? o=prism&a=Legal%20Hold Nutanix Storage Services – Managing Legal Hold on Objects: https://docs.nutanix.com/books/Frames_EBooks_Enterprise/frames.html#Content/Storage/legal_hold.html? toc=/books/Frames_EBooks_Enterprise/toc.jsonPrepared for Nutanix Certified Professional – Unified Storage v6.10 review.
Post your Comments and Discuss Nutanix NCP-US v6.10 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the NCP-US v6.10 content, but please register or login to continue.