Smart Tiering is a feature that allows Files to tier data across different storage tiers based on the file size and access frequency. Smart Tiering supports files with a minimum size of 64 KiB and a maximum size of 5 TiB2. References: Nutanix Files Administration Guide2

Nutanix Objects requires a Data Services IP to be configured on the Prism Infrastructure (PI) cluster, which is used to expose the S3 API endpoint for accessing buckets and objects. Nutanix Objects also requires AHV IP Address Management (IPAM) to be disabled on the VLAN used for Objects, as Objects uses its own DHCP service to assign IP addresses to the Objects VMs1. Reference: Nutanix Objects Administration Guide1

Nutanix Objects supports directory services integration, which allows administrators to configure access keys based on directory and email-based users. This enables granular access control and security for buckets and objects. The administrator can configure directory services under the Access Keys section in Prism Central, and then generate access keys for internal users from the directory service and for the consultant from an email address2. References: Nutanix Objects Administration Guide2

The administrator can achieve this requirement by creating a bucket replication rule and setting the destination Objects instance. Bucket replication is a feature that allows administrators to replicate data from one bucket to another bucket on a different Objects instance for disaster recovery or data migration purposes. Bucket replication can be configured with various parameters, such as replication mode, replication frequency, replication status, etc. Bucket replication can also replicate all versions of objects, including delete markers, which are special versions that indicate that an object has been deleted. By creating a bucket replication rule and setting the destination Objects instance, the administrator can replicate data from one Objects instance to another asynchronously, including all delete markers and versions. Reference: Nutanix Objects User Guide, page 19; Nutanix Objects Solution Guide, page 9

Explanation:
The correct task order for creating an object store is:
* Select ObjectStore Service and click Enable
* Click Create Object Store to start creating the first Object store
* Click Download Creation Checklist to download the list of prerequisites for deploying an Object store The first step is to enable the ObjectStore Service, which is a service that allows users to create and manage object storage clusters on a Nutanix cluster. The second step is to create an Object store, which is an object storage cluster that provides S3-compatible access to buckets and objects for various applications and users.
The third step is to download the Creation Checklist, which is a document that lists the prerequisites and configurations that are required for deploying an Object store, such as cluster details, network details, storage details, etc. The administrator should review and complete the Creation Checklist before proceeding with the deployment of the Object store.

File Analytics is deployed as a VM, and Nutanix provides its binary image in QCOW2 format for AHV, which is the primary hypervisor for Nutanix clusters. QCOW2 is the standard disk image format for AHV, making it the correct choice for the File Analytics deployment image.
Exact Extract from Nutanix Documentation:
From the Nutanix File Analytics Deployment Guide (available on the Nutanix Portal):
“The File Analytics VM is provided as a binary image in QCOW2 format for deployment on AHV clusters.
To deploy File Analytics, download the QCOW2 image from the Nutanix Portal and import it into the cluster using Prism Central or Prism Element.”
:
Nutanix File Analytics Deployment Guide, Version 4.0, Section: “Deploying File Analytics” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix File Analytics Deployment”.

The Nutanix-enabled technology that meets these requirements is Objects – WORM with versioning. WORM (Write-Once Read-Many) is a feature that prevents anyone from modifying or deleting data in a bucket while the policy is active. WORM policies help comply with strict data retention regulations that mandate how long specific data must be stored. Versioning is a feature that keeps multiple versions of an object in a bucket whenever it is overwritten or deleted. Versioning policies help preserve previous versions of an object for backup or recovery purposes. By enabling WORM and versioning for an Objects bucket, the administrator can ensure that data is kept for two years without being deleted or overwritten. References: Nutanix Objects User Guide, page 17; Nutanix Objects Solution Guide, page 9

Nutanix Files, part of Nutanix Unified Storage (NUS), stores its data in containers managed by the Nutanix Acropolis Operating System (AOS). AOS supports data compression to optimize storage usage, which can be applied to Files containers. After an AOS upgrade, compression settings may take effect after a delay, as the system needs to stabilize and apply the new configuration.
Analysis of Options:
* Option A (30 minutes): Incorrect. A 30-minute delay is too short for AOS to stabilize and initiate compression after an upgrade. Compression is a background process that typically requires a longer delay to ensure system stability.
* Option B (60 minutes): Correct. According to Nutanix documentation, after an AOS upgrade, there is a default delay of 60 minutes before compression begins on containers, including those used by Nutanix Files. This delay allows the system to complete post-upgrade tasks (e.g., metadata updates, cluster stabilization) before initiating resource-intensive operations like compression.
* Option C (12 hours): Incorrect. A 12-hour delay is excessive for compression to start. While some AOS processes (e.g., data deduplication) may have longer delays, compression typically begins sooner to optimize storage usage.
* Option D (24 hours): Incorrect. A 24-hour delay is also too long for compression to start. Nutanix aims to apply compression relatively quickly after the system stabilizes, and 60 minutes is the documented delay for this process.
Why Option B?
After an AOS upgrade, compression on containers (including Files containers) is delayed by 60 minutes to allow the cluster to stabilize and complete post-upgrade tasks. This ensures that compression does not interfere with critical operations immediately following the upgrade, balancing system performance and storage optimization.
Exact Extract from Nutanix Documentation:
From the Nutanix AOS Administration Guide (available on the Nutanix Portal):
“After an AOS upgrade, compression on containers, including those used by Nutanix Files, is delayed by 60 minutes. This delay allows the cluster to stabilize and complete post-upgrade tasks before initiating compression, ensuring system reliability.”
:
Nutanix AOS Administration Guide, Version 6.0, Section: “Compression Settings Post-Upgrade” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Files Storage Optimization”.

With the settings shown on the exhibit, if there were 1000 files in the repository, 10 files would have to be deleted within an hour to trigger an anomaly alert to the administrator. Anomaly alert is a feature that notifies the administrator when there is an unusual or suspicious activity on file data, such as mass deletion or encryption. Anomaly alert can be configured with various parameters, such as threshold percentage, time window, minimum number of files, and so on. In this case, the threshold percentage is set to 1%, which means that if more than 1% of files in a repository are deleted within an hour, an anomaly alert will be triggered.
Since there are 1000 files in the repository, 1% of them is 10 files. Therefore, if 10 or more files are deleted within an hour, an anomaly alert will be sent to the administrator. References: Nutanix Files Administration Guide, page 98; Nutanix Data Lens User Guide

Nutanix Volumes, part of Nutanix Unified Storage (NUS), provides block storage via iSCSI to VMs and external hosts. A Volume Group (VG) in Nutanix Volumes is a collection of volumes that can be attached to VMs. For VMs with intensive I/O, performance can be improved by distributing the I/O load across multiple Controller VMs (CVMs) in the Nutanix cluster. The vg.update command in the Nutanix CLI (e.g., ncli) is used to modify Volume Group settings, including parameters that affect I/O distribution.
Analysis of Options:
* Option A (flash_mode=enable): Incorrect. The flash_mode parameter enables flash mode for a Volume Group, which prioritizes SSDs for I/O operations to improve performance. While this can help with intensive I/O, it does not distribute I/O across multiple CVMs-it focuses on storage tiering, not load balancing.
* Option B (load_balance_vm_attachments=true): Correct. The load_balance_vm_attachments=true parameter enables load balancing of VM attachments for a Volume Group. When enabled, this setting distributes the iSCSI connections from VMs to multiple CVMs in the cluster, balancing the I/O load across CVMs. This improves performance for VMs with intensive I/O by ensuring that no single CVM becomes a bottleneck.
* Option C (load_balance_vm_attachments=enable): Incorrect. While this option is close to the correct parameter, the syntax is incorrect. The load_balance_vm_attachments parameter uses true or false as its value, not enable. The correct syntax is load_balance_vm_attachments=true (option B).
* Option D (flash_mode=true): Incorrect. Similar to option A, flash_mode=true enables flash mode for the Volume Group, prioritizing SSDs for I/O. This does not distribute I/O across multiple CVMs, as it addresses storage tiering rather than load balancing.
Why Option B?
The load_balance_vm_attachments=true parameter in the vg.update command enables load balancing for VM attachments to a Volume Group, distributing iSCSI connections across multiple CVMs. This ensures that the I
/O load from VMs with intensive I/O is balanced across the cluster’s CVMs, improving performance by preventing any single CVM from becoming a bottleneck. This directly addresses the requirement to distribute I/O for better performance.
Exact Extract from Nutanix Documentation:
From the Nutanix Volumes Administration Guide (available on the Nutanix Portal):
“To improve performance for Volume Groups with intensive I/O, use the vg.update command to enable load balancing with the parameter load_balance_vm_attachments=true. This setting distributes iSCSI connections from VMs across multiple CVMs in the cluster, balancing the I/O load and preventing bottlenecks.”
:
Nutanix Volumes Administration Guide, Version 6.0, Section: “Optimizing Performance for Volume Groups” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Volumes Performance Tuning”.

Nutanix Files provides a built-in ransomware prevention feature that allows administrators to block malicious file signatures from being written to the file system. However, this feature has a limit of 300 signatures per share or export. If the list of malicious file signatures to block is greater than 300, a third-party solution is recommended2. Reference: Nutanix Files Administration Guide2

Smart DR is a feature that allows share-level replication between active file server instances for disaster recovery. To configure Smart DR, one of the prerequisites is to open TCP port 7515 on all client network IPs (uni-directionally on the source and recovery file servers). This port is used for communication between the FSVMs and the replication engine. Reference: Nutanix Files Administration Guide, page 79; Nutanix Files Solution Guide, page 9

The alert A130358 – ConsistencyGroupWithStaleEntities in a Nutanix environment indicates an issue with a Consistency Group, which is used in Nutanix data protection to ensure that related entities (e.g., VMs, Volume Groups) are protected together in a consistent state. This alert specifically points to “stale entities,” meaning there is a problem with the entities within the Consistency Group that prevents proper protection.
Analysis of Options:
* Option A (One or more VMs or Volume Groups belonging to the Consistency Group contains stale metadata): Correct. The “ConsistencyGroupWithStaleEntities” alert is triggered when entities (e.
g., VMs or Volume Groups) in a Consistency Group have stale metadata, meaning their metadata is outdated or corrupted. This can happen due to synchronization issues, failed operations, or manual changes that leave the metadata inconsistent with the actual state of the entity. This prevents the Consistency Group from being protected properly, as the system cannot ensure consistency.
* Option B (One or more VMs or Volume Groups belonging to the Consistency Group may have been deleted): Incorrect. If an entity in a Consistency Group is deleted, a different alert would typically be triggered (e.g., related to a missing entity). The “StaleEntities” alert specifically refers to metadata issues, not deletion. However, deletion could indirectly cause metadata staleness if the deletion was not properly synchronized, but this is not the primary cause described by the alert.
* Option C (The logical timestamp for one or more of the Volume Groups is not consistent between clusters): Incorrect. Inconsistent logical timestamps between clusters would typically trigger a different alert related to replication or synchronization (e.g., in Metro Availability or NearSync scenarios). The
“StaleEntities” alert is specific to metadata issues within the Consistency Group on the local cluster, not a cross-cluster timestamp issue.
* Option D (One or more VMs or Volume Groups belonging to the Consistency Group is part of multiple Recovery Plans configured with a Witness): Incorrect. Being part of multiple Recovery Plans or using a Witness (e.g., in Metro Availability) does not directly cause a “StaleEntities” alert.
This scenario might cause other issues (e.g., conflicts in recovery operations), but it is not related to stale metadata within a Consistency Group.
Why Option A?
The “ConsistencyGroupWithStaleEntities” alert explicitly indicates that the entities in the Consistency Group have stale metadata, which must be resolved to allow proper protection. The administrator would need to investigate the affected VMs or Volume Groups, clear the stale metadata (e.g., by refreshing the Consistency Group or removing/re-adding the entity), and ensure synchronization with the cluster’s state.
Exact Extract from Nutanix Documentation:
From the Nutanix Prism Alerts Reference Guide (available on the Nutanix Portal):
“Alert A130358 – ConsistencyGroupWithStaleEntities: This alert is triggered when one or more entities (e.g., VMs or Volume Groups) in a Consistency Group have stale metadata, preventing the group from being protected consistently. Stale metadata can occur due to failed operations, synchronization issues, or manual changes. To resolve, identify the affected entities, clear the stale metadata, and ensure the Consistency Group is properly synchronized.”
:
Nutanix Prism Alerts Reference Guide, Version 6.0, Section: “Alert A130358 – ConsistencyGroupWithStaleEntities” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Data Protection Troubleshooting”.

Nutanix Files provides a built-in ransomware prevention feature that allows administrators to block malicious file signatures from being written to the file system. However, this feature has a limit of 300 signatures per share or export. If the list of malicious file signatures to block is greater than 300, a third-party solution is recommended2 Neither File Analytics nor Data Lens supports signature-based ransomware prevention with a large list of malicious file signatures (300+). Signature-based blocking requires a dedicated security solution with a robust signature database, which third-party tools are designed to handle. Nutanix Files supports integration with such tools, making a third-party solution the best choice for this requirement.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Administration Guide (available on the Nutanix Portal):
“For advanced ransomware prevention requiring signature-based blocking, such as when the list of malicious file signatures exceeds 300, Nutanix Files supports integration with third-party security solutions. These solutions can handle large signature databases and perform file scanning/blocking at scale, complementing the behavioral detection capabilities of File Analytics and Data Lens.”
:
Nutanix Files Administration Guide, Version 4.0, Section: “Ransomware Protection with Third-Party Solutions” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Files Security Integrations”.

The most likely cause for this issue is that the file server resides on a single node cluster. A distributed share is a type of SMB share or NFS export that distributes the hosting of top-level directories across multiple FSVMs, which improves load balancing and performance. A distributed share cannot be created on a single node cluster, because there is only one FSVM available. A distributed share requires at least two nodes in the cluster to distribute the directories. Therefore, the option to use distributed share/export type instead of standard is not present when creating a share on a single node cluster. References: Nutanix Files Administration Guide, page 33; Nutanix Files Solution Guide, page 8 A single-node cluster cannot support a Distributed Share because it can only host one FSVM, whereas Distributed Shares require at least three FSVMs for distribution and high availability. This limitation causes the “Use Distributed Share/Export type instead of Standard” option to be absent when creating a share, as the cluster does not meet the minimum requirements.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Administration Guide (available on the Nutanix Portal):
“Distributed Shares require a minimum of three FSVMs to ensure scalability and high availability, which typically requires a cluster with at least three nodes. On a single-node cluster, only Standard Shares are supported, and the option to create a Distributed Share will not be available in the Files Console.”
:
Nutanix Files Administration Guide, Version 4.0, Section: “Distributed Shares Requirements” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Files Share Types”.

The protocols that are supported by Files are SMBv2, SMBv3, NFSv3, and NFSv4. SMB (Server Message Block) is a protocol that allows clients to access files, printers, and other resources on a network. NFS (Network File System) is a protocol that allows clients to access files on a remote server as if they were local.
Files supports both SMB and NFS protocols for creating shares and exports that can be accessed by different types of clients. References: Nutanix Files Administration Guide, page 31; Nutanix Files Solution Guide, page 6

The two steps that are required for enabling Data Lens are:
In Prism, enable Pulse health monitoring: Pulse is a feature that collects diagnostic and usage information from Nutanix clusters and services and sends it to Nutanix for analysis and support purposes. Pulse health monitoring is a feature that monitors the health status of Nutanix clusters and services and sends alerts to Nutanix if any issues are detected. To enable Data Lens, Pulse health monitoring must be enabled in Prism Element or Prism Central.
Configure the Data Services IP in Prism Central: Data Services IP is an IP address that is used for communication between Prism Central and Data Lens. Data Services IP must be configured in Prism Central before enabling Data Lens for any file server. Data Services IP must be routable from both Prism Central and Data Lens. Reference: Nutanix Files Administration Guide, page 93; Nutanix Data Lens Deployment Guide

Nutanix Objects supports versioning, which is a feature that allows multiple versions of an object to be preserved in the same bucket. Versioning can be useful for developers who need to upload their code for testing API calls and retain older iterations as newer code is developed and tested. Versioning can also provide protection against accidental deletion or overwrite of objects. Reference: Nutanix Objects Administration Guide

Before installing or upgrading Files, Life Cycle Manager (LCM) must check the compatibility versions of Nutanix Cluster Check (NCC) and Acropolis Operating System (AOS). NCC is a framework of scripts that helps diagnose cluster health, and AOS is the core operating system that runs on each node in a Nutanix cluster. LCM will not proceed with the installation or upgrade if NCC or AOS versions are incompatible with Files. Reference: Nutanix Files Administration Guide, Nutanix Cluster Check Guide

Nutanix Files, part of Nutanix Unified Storage (NUS), uses File Server Virtual Machines (FSVMs) to manage file services (e.g., SMB, NFS). Each FSVM runs on a node in the Nutanix cluster, and the number of connections per node impacts the resource requirements, particularly memory (RAM), for the FSVMs. The administrator needs to size the memory for a Files instance where each node will handle an average of 4,000 connections.
Sizing Guidelines:
Nutanix provides sizing guidelines for Files deployments based on the number of connections per FSVM (and thus per node, assuming one FSVM per node, which is the default configuration). The memory requirements scale with the number of connections to ensure performance and stability:
* The minimum memory per FSVM is 12 GiB (as noted in Question 2), which supports up to 1,000 connections.
* For higher connection counts, Nutanix recommends increasing the memory proportionally.
According to Nutanix documentation:
* Up to 1,000 connections: 12 GiB RAM per FSVM.
* 1,000 to 2,000 connections: 24 GiB RAM per FSVM.
* 2,000 to 4,000 connections: 48 GiB RAM per FSVM.
* 4,000 to 8,000 connections: 96 GiB RAM per FSVM.
Since the question specifies 4,000 connections per node, and assuming one FSVM per node (standard deployment), the FSVM on each node needs to handle 4,000 connections. Based on the sizing guidelines:
* 4,000 connections fall into the 4,000 to 8,000 range, requiring 96 GiB RAM per FSVM.
* Since each node hosts one FSVM, this translates to 96 GiB RAM per node dedicated to the FSVM.
Analysis of Options:
* Option A (32 GiB RAM per node): Incorrect. 32 GiB RAM per node is sufficient for up to 2,000 connections (24 GiB for the FSVM, plus some overhead), but it is insufficient for 4,000 connections, which require 96 GiB.
* Option B (40 GiB RAM per node): Incorrect. 40 GiB RAM per node is still too low for 4,000 connections, as it falls short of the 96 GiB recommended for this connection range.
* Option C (96 GiB RAM per node): Correct. 96 GiB RAM per node aligns with Nutanix’s sizing guidelines for an FSVM handling 4,000 to 8,000 connections, ensuring the Files instance can manage the expected load efficiently.
* Option D (128 GiB RAM per node): Incorrect. While 128 GiB RAM per node would work, it exceeds the recommended sizing for 4,000 connections. Nutanix recommends 96 GiB for up to 8,000 connections, and 128 GiB is typically reserved for even higher connection counts (e.g., >8,000) or additional workloads on the node. The question asks for the “proper” sizing, which is the minimum recommended for the given load, making 96 GiB the correct choice.
Why Option C?
For 4,000 connections per node, Nutanix recommends 96 GiB RAM per FSVM (one FSVM per node), which translates to 96 GiB RAM per node dedicated to the FSVM. This ensures the Files instance can handle the connection load without performance degradation, aligning with Nutanix’s sizing guidelines.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Sizing Guide (available on the Nutanix Portal):
“For Nutanix Files deployments, memory sizing depends on the number of connections per FSVM. For 4,000 to 8,000 connections, allocate 96 GiB of RAM per FSVM. Assuming one FSVM per node, this translates to
96 GiB RAM per node dedicated to the FSVM to ensure optimal performance.” Additional Notes:
* The question assumes one FSVM per node, which is the default configuration for Nutanix Files unless otherwise specified. If multiple FSVMs were on a single node, the total RAM would need to be adjusted, but the question’s phrasing (“per node”) aligns with the standard one-FSVM-per-node deployment.
* The 96 GiB RAM is for the FSVM itself; the node may require additional RAM for other workloads (e.
g., CVM, VMs), but the question focuses on the Files instance’s memory sizing, making 96 GiB the correct answer.
:
Nutanix Files Sizing Guide, Version 4.0, Section: “Memory Sizing for Nutanix Files” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Files Sizing and Performance”.