NCP-US-6.10 Nutanix Certified Professional - Unified Storage (NCP-US) v6.10 Free Practice Exam Questions (2025 Updated)

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.

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.

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.

Legal Holdin Nutanix Objects is a feature designed for compliance and regulatory use cases, ensuring thatspecific 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.

Nutanix Files includes several features for managing data availability and mobility across sites. Here’s the detailed breakdown:

Data Sync— This feature is designed toreplicate user data between file servers at different locations. It enablesbi-directional or one-way file-level replicationfor use cases such as:

Branch office file sharing

Geo-dispersed data access

Centralized backups of branch data

From the NUSA course materials:

“Data Sync provides file-level replication across geographically distributed Nutanix Files deployments, ensuring consistent data access and synchronization across multiple sites.”

This feature is purpose-built forcross-location file data replication, meeting the administrator’s need.

Data Protection— Refers to snapshot-based local or remote protection of theentire file server or shares, not file-level sync across different locations.

Smart Sync— Specific to Object data within Nutanix Objects, not for Files.

VDI Sync— Designed for syncing user profiles in VDI environments, not general file share replication.

Thus, the administrator should useData Syncfor replicating user data across file servers in different locations.

The issue involves Nutanix Objects stopping the collection of analytics data for Nutanix Data Lens approximately nine months after being enabled. To resume Data Lens functionality, the administrator shoulddisable and re-enable analytics on the object store. Nutanix Data Lens is a cloud-based service that provides analytics and lifecycle management for Nutanix Objects, and issues with analytics data collection can often be resolved by resetting the analytics configuration.

TheNutanix Unified Storage Administration (NUSA)course states, “If Nutanix Data Lens stops gathering analytics data for an object store, a common troubleshooting step is to disable and re-enable analytics on the object store to reset the connection and resume data collection.” This process forces the object store to re-establish its integration with Data Lens, clearing any potential configuration or connectivity issues that may have caused the analytics to stop. The nine-month period suggests a possible timeout or licensing issue with Data Lens, which can be resolved by this action.

TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further elaborates that “disabling and re-enabling analytics on a Nutanix Objects store is an effective way to troubleshoot Data Lens functionality issues, ensuring that the object store re-syncs with Data Lens for analytics data collection.” The administrator can perform this action through Prism Central by navigating to the Nutanix Objects configuration, disabling analytics for the affected object store, and then re-enabling it.

The other options are incorrect:

Rename the bucket within the object store: Renaming a bucket does not affect Data Lens integration or analytics data collection, as Data Lens operates at the object store level, not the bucket level.

Remove and re-add IAM user permissions on the object store: IAM user permissions control access to the object store but are not directly related to Data Lens analytics collection. Changing permissions is unlikely to resolve this issue.

Disable and re-enable versioning on the object store: Versioning allows multiple versions of objects to be stored but does not impact Data Lens analytics functionality.

The NUSA course documentation emphasizes that “resetting analytics by disabling and re-enabling the feature on the object store is a standard troubleshooting step to resume Data Lens functionality when analytics data collection stops unexpectedly.”

Toenable Nutanix Objects(deploy a new Objects instance and manage bucket creation), a non-admin user must have the following minimum permissions:

Cluster Admin:

Grants full cluster-level privileges, including resource provisioning, configuration, and management.

Required to deploy services like Objects because it interacts with cluster resources directly.

User Admin:

Allows user management and security roles necessary for configuring access to Objects.

Critical when setting up Object Stores and managing authentication.

According to the NUSA course:

“A non-admin user must have at least the Cluster Admin role and the User Admin role to enable and manage Nutanix Objects deployments. Cluster Admin manages resources, and User Admin manages user-level permissions.”

The other roles:

Files Admin— manages Nutanix Files only.

Category Admin— relates to category/tag management in Prism, not Objects deployment.

Thus, toenable Nutanix Objects, the user needsCluster AdminandUser Adminpermissions.

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 featurethat enables user-initiated recovery of earlier versions.

The error message explicitly references anobject-lock enabled bucketand restrictions onmodifying/deleting objects. This points directly to theWORM (Write Once Read Many)feature being enabled on the S3 bucket.

WORM (Object Lock):

Object Lock (also called WORM)prevents objects from being deleted or modifiedfor a retention period set by the bucket’s policy.

The error states:

“An object from the object-lock enabled bucket can not be modified or deleted unless the retention period is elapsed.”

This directly matches the behavior of an S3 bucket withWORM retention.

The other options:

A. Bucket name incorrect: Would result in a “NoSuchBucket” or “Not Found” error, not “Method Not Allowed.”

C. Object-Level permissions: Insufficient permissions would cause “Access Denied” or “Forbidden,” not WORM-specific errors.

D. API key misconfiguration: Would typically produce authentication errors (“SignatureDoesNotMatch,” etc.), not a WORM policy restriction.

The NUSA course discusses WORM behavior:

“If WORM is enabled on a bucket, objects cannot be deleted or modified until the retention period expires. Attempting to do so will generate ‘Method Not Allowed’ errors.”

Thus, the error here is directly caused byWORM retention(Object Lock) being active on the S3 bucket.