Free NCP-US v6.10 Exam Braindumps
Nutanix Certified Professional - Unified Storage v6.10 Questions 11–15 (page: 4)

Updated On: 3-Sep-2026

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 had to restore the VG. Upon restoring the VG, the VMs lost connectivity to the Volume Group.
What should the administrator have done differently to prevent this from happening?

  1. Use the VM UUID in the VG allowlist
  2. Use the iSCSI IQN entry in the VG allowlist.
  3. Use the VM hostname in the VG allowlist.
  4. Use the NIC MAC address of the VM's in the VG allowlist.

Answer(s): B

Explanation:

Why option B is correct
Nutanix Volume Group allowlists identify the in-guest iSCSI initiator by its iSCSI IQN . The IQN is a persistent, globally unique identifier that does not change when the VM is moved, recreated, or restored. Adding the IQN guarantees that the restored Volume Group can still map to the correct initiator and restore connectivity.
Why the other options are less suitable
A – VM UUID – The UUID is generated by the hypervisor at VM creation and changes whenever the VM is redeployed or restored; it is not used by the VG allowlist for initiator identification.
C – VM hostname – Hostnames are user-defined and can be altered at any time; they are not a stable identifier for storage-level initiator mapping. D – NIC MAC address – MAC addresses are not guaranteed to stay constant across VM migrations or rebuilds and are not the attribute the allowlist uses for iSCSI initiator verification.
Using the iSCSI IQN therefore provides the most reliable and persistent mapping between a restored VM and its access to the Volume Group.


Reference:

Nutanix Prism Volume Group Allowlist Configuration – explains that IQNs are the recommended identifier for iSCSI initiator allowlist entries. https://docs.nutanix.com/calm/v6/volume-groups#allowlist iSCSI Initiator Setup for Nutanix Volumes – outlines how to retrieve and use the iSCSI IQN for allowlisting. https://docs.nutanix.com/calm/v6/iscsi-initiator



An administrator is managing a Nutanix Files instance at a dark site. The administrator has been tasked to configure a solution to alert the security team when more than 500 files are renamed hourly.
Which configuration should be applied?

  1. Set up Data Management Protection in Files Manager.
  2. Configure Nutanix Data Lens ransomware protection.
  3. Add MMC Snap-In for Nutanix Files.
  4. Define an anomaly rule in File Analytics.

Answer(s): D

Explanation:

Technical justification
Correct choice –
D: Define an anomaly rule in File Analytics File Analytics collects rename events per hour for each directory. It can generate anomaly alerts when rename volume exceeds a configurable threshold (e.g., >500 renames/hour). By defining a custom anomaly rule with the exact threshold and alert destination, the security team will be notified in real-time.
Why the other options are unsuitable
A – Set up Data Management Protection : This feature enforces policy-based protection (e.g., encryption, retention) but does not provide frequency-based rename analytics or custom alerts. B – Configure Nutanix Data Lens ransomware protection : Data Lens monitors ransomware patterns cluster-wide; it is not tuned for per-directory rename counts or for alerting on a simple hourly rename volume. C – Add MMC Snap-In for Nutanix Files : The MMC Snap-In is a management UI for browsing and administering Files; it offers no built-in analytics or alerting capabilities for rename activity.
Thus, only File Analytics provides the granular rename-event data needed to create a specific “>500 renames per hour” anomaly alert.


Reference:

Nutanix Files – Monitor and Alert on File Activity using File Analytics: https://portal.nutanix.com/page/files-analytics
Create and Configure Anomaly Rules in File Analytics: https://docs.nutanix.com/frames/files-analytics-anomaly-rules.html



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?

  1. Examine the File Distribution by Type widget in the File Analytics dashboard for the File Server.
  2. Examine the File Distribution by Type widget from the Files Console for the File Server.
  3. Examine the Usage Summary table for the File Server Container in the Prism Element Storage page.
  4. Examine the File Activity widget in the File Analytics dashboard for the File Server.

Answer(s): A

Explanation:

Technical justification
The File Distribution by Type widget is located in the File Analytics dashboard, which aggregates detailed, per-type consumption metrics (e.g., images, videos, documents). This widget directly shows the proportion of each file type stored, allowing the administrator to identify whether personal media files dominate the storage pool. Option B references the same widget but from the Files Console , which does not provide the same analytics view; it only lists files and folders without the distribution breakdown. Option C points to the Usage Summary table on the Prism Element Storage page, which reports overall capacity and utilization but lacks granularity by file type, making it unsuitable for pinpointing photo/video consumption. Option D mentions the File Activity widget, which tracks access patterns (read/write frequency) rather than composition of stored data, so it cannot confirm the presence of personal media files.


Reference:

File Analytics – File Distribution by Type: https://registry.terraform.io/providers/nutanix/providers/nutanix/6.10/docs Files Console Overview: https://Docs.nutanix.com/frameset/release-6-10/Frame.html#/files/Files_Console? tocpath=Files%20Console%7C _____
((A))



After enabling Nutanix Objects, what action should be performed before starting the deployment?

  1. Perform an LCM inventory
  2. Create a Volume Group
  3. Create a Container
  4. Create Object Store

Answer(s): A

Explanation:

Justification
Correct choice – A: Perform an LCM inventory
Before any new Nutanix service (including Objects) can be consumed, the LCM (Lifecycle Management) engine must refresh its inventory so it is aware of the latest hardware and software state. An up-to-date inventory ensures that the deployment wizard sees all required nodes, storage containers and metadata, preventing version mismatches or missing prerequisite checks. Skipping this step can leave stale information in the LCM database, which later manifests as deployment failures or unexpected resource re-balancing.
Why the other options are not appropriate at this stage
B – Create a Volume Group – Volume Groups are part of traditional block storage provisioning and are not a prerequisite for enabling the Objects service. They can be created later after the Objects service is already configured. C – Create a Container – Containers are the logical storage units for objects, but they are created after the Objects service is enabled and the LCM inventory is refreshed; otherwise the container would be orphaned if the deployment were aborted. D – Create Object Store – The Object Store is the actual backing store for objects; it is provisioned during the Objects deployment workflow, not as a pre-deployment prerequisite. Attempting it before the LCM inventory refresh would have no effect on the service’s ability to start.
Resulting workflow
1. Verify and refresh LCM inventory → confirms cluster health and available resources. 2. Enable Nutanix Objects via the UI/CLI. 3. Create Containers and Object Stores as needed for the workload.


Reference:

Nutanix LCM Inventory Refresh Guide: https://docs.nutanix.com/frames/frames-lcm-inventory Deploying Nutanix Objects Overview: https://docs.nutanix.com/frames/frames-objects-deployment



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?

  1. A distributed share
  2. A standard share
  3. A connected share
  4. A WORM share

Answer(s): A

Explanation:

Justification
Distributed share (Correct answer – A) – User profile data must be available from any compute node, provide fault-tolerance, and scale with demand. A distributed share is replicated across the storage fabric and presented to all hosts, ensuring continuous access, load-balanced I/O, and resilience if a node fails. This makes it the optimal choice for centrally stored, frequently accessed environments such as employee profiles. Standard share (B) – A standard share is tied to a single storage node or a single server. It lacks the replication and automatic fail-over that a distributed implementation provides, so it cannot guarantee uninterrupted access for profiles when a node goes down. Connected share (C) – Connected shares are typically bound to a specific host for local workloads and are not designed for multi-node visibility. They do not automatically propagate changes across the cluster, making them unsuitable for a shared profile repository. WORM share (D) – WORM (Write-Once-Read-Many) enforces a read-only or append-only policy. Employee profiles require both read and write operations for regular updates, so a WORM-configured share would prevent necessary modifications.
Conclusion – For a requirement that demands centralised, highly available, and writable access to user profiles across the cluster, a distributed share is the only option that fulfills all technical constraints.


Reference:

Nutanix Prism Administration Guide – Share Types Overview: https://next.nutanix.com/docs/r/Prism-Administration-Guide#share-types Nutanix Files Cluster – Configuring Distributed SMB Shares: https://next.nutanix.com/docs/r/Files-Cluster#distributed-smb-share



Viewing page 4 of 16
Viewing questions 16 - 20 out of 74 questions


Post your Comments and Discuss Nutanix NCP-US v6.10 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!