Data Lens is a feature that provides insights into the data stored in Files, such as file types, sizes, owners, permissions, and access patterns. Data Lens allows administrators to create reports on various aspects of their data and schedule them to run automatically on a weekly basis. References: Nutanix Data Lens Administration Guide

The component that must first be upgraded to a compatible version before upgrading Files or creating a file server is Prism Central. Prism Central is a web-based user interface that allows administrators to manage multiple Nutanix clusters and services, including Files. Prism Central must be upgraded to a compatible version with Files before upgrading an existing file server or creating a new file server. Otherwise, the upgrade or creation process may fail or cause unexpected errors.  References:  Nutanix Files Administration Guide, page 21; Nutanix Files Upgrade Guide

Nutanix Objects, part of Nutanix Unified Storage (NUS), is an S3-compatible object storage solution that can be deployed on AHV or ESXi hypervisors. Deploying Objects has specific prerequisites to ensure successful installation and operation.

Analysis of Options:

Option A (Prism Central version is 5.17.1 or later) : Incorrect. While Nutanix Objects requires Prism Central for deployment and management, the minimum version for Objects deployment is typically lower (e.g., Prism Central 5.15 or later, depending on the Objects version). Version 5.17.1 is not a specific requirement for Objects deployment on AHV or ESXi.

Option B (Port 9440 is accessible on both PE and PC) : Correct. Port 9440 is used for communication between Prism Element (PE) and Prism Central (PC), as well as for internal Nutanix services. When deploying Objects, Prism Central communicates with the cluster (via Prism Element) to deploy Object Store Service VMs. This communication requires port 9440 to be open between PE and PC, making it a key prerequisite.

Option C (Valid SSL Certificate) : Incorrect. While a valid SSL certificate is recommended for secure communication (e.g., for S3 API access), it is not a strict prerequisite for deploying Objects. Objects can be deployed with self-signed certificates, though Nutanix recommends replacing them with valid certificates for production use.

Option D (Nutanix STARTER License) : Incorrect. The Nutanix STARTER license is an entry-level license for basic cluster functionality (e.g., VMs, storage). However, Nutanix Objects requires a separate license (e.g., Objects license or a higher-tier AOS license like Pro or Ultimate). The STARTER license alone does not support Objects deployment.

Why Option B?

Port 9440 is critical for communication between Prism Element and Prism Central during the deployment of Objects. If this port is blocked, the deployment will fail, as Prism Central cannot communicate with the cluster to deploy the Object Store Service VMs.

Exact Extract from Nutanix Documentation :

From the Nutanix Objects Deployment Guide (available on the Nutanix Portal):

“Before deploying Nutanix Objects on AHV or ESXi, ensure that port 9440 is accessible between Prism Element (PE) and Prism Central (PC). This port is required for communication during the deployment process, as Prism Central manages the deployment of Object Store Service VMs on the cluster.”

Nutanix Files, part of Nutanix Unified Storage (NUS), can be installed or upgraded using Life Cycle Manager (LCM), a tool in Prism Central or Prism Element for managing software updates. Before installing or upgrading Files, LCM must ensure that the underlying components are compatible to avoid issues during the process.

Analysis of Options:

Option A (Nutanix Cluster Check) : Correct. Nutanix Cluster Check (NCC) is a health and compatibility checking tool integrated with LCM. LCM requires a compatible version of NCC to perform pre-upgrade checks and validate the cluster’s readiness for a Files installation or upgrade. NCC ensures that the cluster environment (e.g., hardware, firmware, software) is compatible with the Files version being installed or upgraded.

Option B (Active Directory Services) : Incorrect. Active Directory (AD) Services are used by Nutanix Files for user authentication (e.g., for SMB shares or multiprotocol access, as in Question 60), but AD is not a component managed by LCM, nor is it a prerequisite for LCM compatibility. AD configuration is a separate requirement for Files functionality, not LCM operations.

Option C (File Server Module) : Incorrect. There is no “File Server Module” component in Nutanix terminology. Nutanix Files itself consists of File Server Virtual Machines (FSVMs), but this is the component being upgraded, not a prerequisite for LCM. LCM manages the Files upgrade directly and does not require a separate “module” compatibility.

Option D (Acropolis Operating System) : Correct. The Acropolis Operating System (AOS) is the core operating system of the Nutanix cluster, managing storage, compute, and virtualization. LCM requires a compatible AOS version to install or upgrade Files, as Files relies on AOS features (e.g., storage, networking) and APIs. LCM checks the AOS version to ensure it meets the minimum requirements for the target Files version.

Selected Components:

A : NCC ensures cluster compatibility and readiness, which LCM relies on for Files installation or upgrades.

D : AOS provides the underlying platform for Files, and LCM must ensure its version is compatible with the Files version being deployed.

Exact Extract from Nutanix Documentation :

From the Nutanix Files Administration Guide (available on the Nutanix Portal):

“Before installing or upgrading Nutanix Files using Life Cycle Manager (LCM), ensure that LCM has compatible versions of Nutanix Cluster Check (NCC) and Acropolis Operating System (AOS). NCC performs pre-upgrade checks to validate cluster readiness, while AOS must meet the minimum version requirements for the target Files version.”

Smart DR in Nutanix Files, part of Nutanix Unified Storage (NUS), is a disaster recovery (DR) solution that simplifies the setup of replication policies between file servers (e.g., using NearSync, as seen in Question 24). After configuring a Smart DR policy, the administrator expects to see it in the Policies tab in Prism Central, but it is not visible despite confirmed connectivity between FSVMs and Prism Central via port 9440 (used for Prism communication, as noted in Question 21). This indicates a potential mismatch or configuration issue.

Analysis of Options:

Option A (The primary and recovery file servers do not have the same version) : Correct. Smart DR requires that the primary and recovery file servers (source and target) run the same version of Nutanix Files to ensure compatibility. If the versions differ (e.g., primary on Files 4.0, recovery on Files 3.8), the Smart DR policy may fail to register properly in Prism Central, resulting in it not appearing in the Policies tab. This is a common issue in mixed-version environments, as Smart DR relies on consistent features and APIs across both file servers.

Option B (Port 7515 should be open for all External/Client IPs of FSVMs on the Source and Target cluster) : Incorrect. Port 7515 is not a standard port for Nutanix Files or Smart DR communication. The External/Client network of FSVMs (used for SMB/NFS traffic) communicates with clients, not between FSVMs or with Prism Central for policy management. Smart DR communication between FSVMs and Prism Central uses port 9440 (already confirmed open), and replication traffic between FSVMs typically uses other ports (e.g., 2009, 2020), but not 7515.

Option C (The primary and recovery file servers do not have the same protocols) : Incorrect. Nutanix Files shares can support multiple protocols (e.g., SMB, NFS), but Smart DR operates at the file server level, not the protocol level. The replication policy in Smart DR replicates share data regardless of the protocol, and a protocol mismatch would not prevent the policy from appearing in the Policies tab—it might affect client access, but not policy visibility.

Option D (Port 7515 should be open for all Internal/Storage IPs of FSVMs on the Source and Target cluster) : Incorrect. Similar to option B, port 7515 is not relevant for Smart DR or Nutanix Files communication. The Internal/Storage network of FSVMs is used for communication with the Nutanix cluster’s storage pool, but Smart DR policy management and replication traffic do not rely on port 7515. The key ports for replication (e.g., 2009, 2020) are typically already open, and the issue here is policy visibility, not replication traffic.

Why Option A?

Smart DR requires compatibility between the primary and recovery file servers, including running the same version of Nutanix Files. A version mismatch can cause the Smart DR policy to fail registration in Prism Central, preventing it from appearing in the Policies tab. Since port 9440 connectivity is already confirmed, the most likely issue is a version mismatch, which is a common cause of such problems in Nutanix Files DR setups.

Exact Extract from Nutanix Documentation :

From the Nutanix Files Administration Guide (available on the Nutanix Portal):

“Smart DR requires that the primary and recovery file servers run the same version of Nutanix Files to ensure compatibility. A version mismatch between the source and target file servers can prevent the Smart DR policy from registering properly in Prism Central, resulting in the policy not appearing in the Policies tab.”

Nutanix Files, part of Nutanix Unified Storage (NUS), provides file sharing services via protocols like SMB and NFS. In environments where users access SMB shares, network interruptions can cause sessions to disconnect, requiring users to manually reconnect. Nutanix Files offers a feature to mitigate this issue for SMB shares.

Analysis of Options:

Option A (Durable File Handles) : Correct. Durable File Handles is an SMB feature in Nutanix Files that allows client sessions to automatically reconnect after temporary network interruptions. When enabled, it ensures that file handles remain valid during brief disconnects, allowing the client to resume the session without manual intervention.

Option B (Multi-Protocol Shares) : Incorrect. Multi-Protocol Shares allow a share to be accessed via both SMB and NFS, but this feature does not address session reconnection during network issues.

Option C (Connected Shares) : Incorrect. “Connected Shares” is not a feature in Nutanix Files. This appears to be a made-up term and does not apply to session reconnection.

Option D (Workload Optimization) : Incorrect. Workload Optimization in Nutanix Files involves adjusting the number of FSVMs or resources for performance (as noted in Question 13), but it does not address session reconnection for network issues.

Why Durable File Handles?

Durable File Handles is an SMB 2.1+ feature supported by Nutanix Files. It ensures that file handles persist during network disruptions, allowing clients to auto-reconnect without losing their session state, which directly addresses the users’ complaint.

Exact Extract from Nutanix Documentation :

From the Nutanix Files Administration Guide (available on the Nutanix Portal):

“Durable File Handles is an SMB feature that allows clients to automatically reconnect to a share after temporary network interruptions. When enabled on a Nutanix Files share, it ensures that file handles remain valid, preventing users from having to manually reconnect during brief network outages.”

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 address 2 . References: Nutanix Objects Administration Guide 2

 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 VMs 1 . References: Nutanix Objects Administration Guide 1

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 Files, part of Nutanix Unified Storage (NUS), integrates with Active Directory (AD) for user authentication and synchronization in a Windows environment. A key requirement for AD integration is that the time between the Files environment (specifically, the File Server Virtual Machines or FSVMs) and the AD server must be synchronized, as a time difference greater than 5 minutes can cause Kerberos authentication failures, leading to synchronization issues.

Analysis of Options:

Option A (Connect to every FSVM and edit the time manually) : Incorrect. Manually editing the time on each FSVM is a temporary fix and not a sustainable solution. It does not prevent future time drift, as the FSVMs’ clocks will continue to drift without proper synchronization.

Option B (Use the same NTP Servers for the Files environment and the AD Server) : Correct. The best way to prevent time differences is to ensure that both the Files environment (FSVMs) and the AD server use the same Network Time Protocol (NTP) servers for time synchronization. This ensures consistent timekeeping across both systems, avoiding authentication issues due to time skew.

Option C (Use 0.pool.ntp.org as the NTP Server for the AD Server) : Incorrect. While using 0.pool.ntp.org as the NTP server for the AD server is a valid approach, it does not ensure synchronization unless the Files environment also uses the same NTP server. If the Files environment uses a different NTP server, time drift can still occur.

Option D (Use 0.pool.ntp.org as the NTP Server for the Files environment) : Incorrect. Similar to option C, using 0.pool.ntp.org for the Files environment alone does not guarantee synchronization with the AD server unless the AD server also uses the same NTP server.

Why Option B?

Time synchronization between Nutanix Files and AD is critical for Kerberos authentication, which has a default tolerance of 5 minutes. Using the same NTP servers for both the Files environment (configured at the cluster level via Prism Element) and the AD server ensures that both systems maintain the same time, preventing future synchronization issues.

Exact Extract from Nutanix Documentation :

From the Nutanix Files Administration Guide (available on the Nutanix Portal):

“For successful Active Directory integration, the time between the Nutanix Files environment and the AD server must be synchronized within a 5-minute window. To prevent time drift, configure both the Nutanix cluster (which manages FSVM time) and the AD server to use the same NTP servers. This ensures consistent timekeeping and avoids Kerberos authentication failures.”