To place all iSCSI traffic on an isolated network, the best approach is to create a Volumes network in Prism Central. This allows the administrator to assign iSCSI traffic to a dedicated VLAN and IP subnet, effectively isolating it from other network traffic. This solution ensures network segmentation tailored for iSCSI traffic.

File servers require the following minimum configurations. A minimum of four vCPUs per host. A minimum of 12 GiB of memory per host. For each file server, the number of CVMs must be equal to or greater than the number of file server VMs (FSVMs) to ensure availability if there is a node failure.

To configure unique data protection policies for different shares in a Files cluster, configure the policies in the Files view in Prism Central. Starting with Files 3.8, Prism Central allows you to replicate individual shares to a remote Nutanix Files server and configure different recovery policies based on share requirements. This method requires two active Files servers on two different AOS (Acropolis Operating System) clusters.

The two primary ways to manage Nutanix Objects are through the CLI and API. Both allow for in-depth, customizable management and configurations.
  The CLI is often used for hands-on, command-driven management of objects, enabling efficient, direct control.
The API is used for automation, integration, and programmatic access, making it suitable for environments that require custom scripts or application-level integration.
Prism Central (PC) and SSH are not specifically designed for managing objects themselves, though they might be involved in the broader Nutanix environment management.

Enabling Smart Tiering within the File Console is the best way to meet this requirement. Smart Tiering allows you to move cold data to a remote location such as Nutanix Objects, Microsoft Azure, AWS Standard, AWS IA, or Wasabi. This will free up space on the Files cluster for newer data. Since the organization already uses the Public Cloud for other storage needs and has added a node with more storage, this makes Smart Tiering an ideal solution. It is important to note that you can only have one tiering profile and location for each file server, and files smaller than 64 KiB or larger than a certain size cannot be tiered.

Permissions in Nutanix Files ensure data is accessed only by approved users/groups, which is critical for compliance.

When booting a physical Windows Server from a Nutanix AOS volume group, the physical server connects to the volume via iSCSI using the data services IP. MPIO is not required in this case, as the single-path iSCSI connection is sufficient for booting the server. This is the standard method for booting physical servers from Nutanix block storage in a Nutanix AOS environment.

utanix Files supports 50 configured snapshots for Self-Service Restore (SSR). This limit is considerably lower than some competitors‘ offerings such as NetApp (1023 snapshots per volume), Powerscale/Isilon (20K per cluster), and Pure Storage (400K per cluster). Additionally, there is a limit of 30,000 SSR snapshots per node. Any attempt to create more snapshots beyond the limit of 50 for SSR will result in an error message.

1

Incorrect: Deleting only 1 file from a repository of 1000 results in a 0.1% change. If the anomaly detection threshold is set higher (e.g., 1%), this single deletion would not trigger an alert.

Correct answer

10

Correct: If the threshold in File Analytics is configured for anomaly detection at delete 10 files, or deleting 100% out of 1000 will trigger the alert. This aligns with the anomaly detection settings typically seen in the File Analytics UI.

100

Incorrect: While 100 deletions would absolutely trigger the alert, this option overshoots the minimum required to meet the threshold. The question specifically asks how many are needed to trigger it, so 100 is more than necessary.

1000

Incorrect: Deleting all files would trigger the alert, but similar to option C, it far exceeds the minimum threshold. Choosing this would not reflect an understanding of the configured detection limit.

Details:

The exhibit indicates an anomaly threshold (total operation 10 files) is configured. With 1000 files, deleting 10 files or 100% from the files (1000) triggers an alert. This matches expected behavior in Nutanix Data Lens anomaly detection logic, so once 10 files deleted from the share alert will be generated.

The incorrect Files license has been applied.

Incorrect: Nutanix Files licensing affects capacity and feature usage overall, but it does not directly control the visibility of multiprotocol access settings in the UI. Even with a standard license, the UI should show the multiprotocol setting if the feature is available based on the initial file server configuration.

NFS is configured to use unmanaged authentication

Incorrect: While authentication method (managed vs unmanaged) can impact user access behavior and identity mapping, it does not hide or disable the multiprotocol access setting in the share creation UI. This is more about behavioral differences after configuration.

The connection to Active Directory has not been configured.

Incorrect: Active Directory (AD) is needed for SMB user authentication, but its absence would result in errors when creating SMB shares or mapping permissions — not in disabling or hiding the multiprotocol access setting. Furthermore, the admin would still see the option even if AD wasn’t connected.

Correct answer

The File server instance was only configured with SMB.

Correct: When creating a new Files Server (in Nutanix Files), you can choose protocols to enable: SMB, NFS, or both. If the file server was initially deployed with SMB only, then NFS settings — including multiprotocol access — will not be available, because the system is not configured to handle NFS traffic. To fix this, the administrator would need to re-deploy or modify the file server to enable NFS.

Details:

The setting “Enable multiprotocol access for NFS clients” is only available if the File Server instance was deployed with both SMB and NFS protocols enabled. This option allows SMB and NFS clients to access the same share, which is useful for environments needing hybrid Windows/Linux access. If only SMB was selected during the initial deployment of the file server, then NFS-related options (including multiprotocol support) are not shown in the UI, leading to the behavior described in the question.

Data Lens is the right tool for monitoring and analyzing usage across all Nutanix Files deployments globally. Nutanix Data Lens provides a cloud-hosted analytics and monitoring service for Nutanix file servers, Isilon file servers, Nutanix object stores, and Amazon S3 object stores.
It centralizes data from all clusters connected to Nutanix Pulse, across multiple data centers, offering near-real-time analytics and alerts, even for large file servers with over 250 million files and 500 TB of storage. Unlike on-premises solutions, which are limited to local servers, Data Lens operates globally and independently of any specific Nutanix cluster. It enhances data visibility, detects security risks, monitors permissions, and supports ransomware protection, user auditing, and compliance.
With cloud resources, it scales without limits, managing an unlimited number of files and objects across your environment. https://portal.nutanix.com/page/documents/details?targetId=Data-Lens:dat-datalens-overview-c.html

In a highly secured environment, network restrictions (e.g., firewalls, ACLs, or isolated VLANs) can block inter-node communication. The error: “Fileserver preupgrade check failed with cause sub task poll time out” …strongly suggests that components within the File Server (FSVMs) cannot communicate with each other or with Prism Central to complete upgrade coordination steps. This typically indicates a connectivity issue.

Data Lens is the best ransomware prevention solution when the list of malicious file signatures to block is greater than 300. Data Lens supports over 5,000 blocked file signatures, which are updated automatically. File Analytics, the on-premises version, includes a list of common file names and extensions of known ransomware variants, but this list is likely smaller than Data Lens and may not contain all 300+ signatures.

For a four-node FSVM deployment: Client network: One IP address per FSVM is required for file share access and client communication. Since there are four FSVMs, four IPs are required. Storage network: Each FSVM requires one IP address for storage network communication. Additionally, one floating IP is needed for CVM-to-FSVM communication, leading to five IPs being necessary for the Storage network.
Thus, the correct answers are: 
C (Four available IP addresses on the Client network)
A (Five available IP addresses on the Storage network)

Time synchronization is critical in environments where authentication relies on Kerberos, such as when integrating Nutanix Files with Active Directory. Even small time differences can cause authentication failures. The best practice is to configure both systems (Files and AD) to use the same NTP servers. This ensures they remain in sync and eliminates the risk of drift-related issues in the future.

Nutanix Data Lens, which is part of Nutanix Files analytics and governance, requires secure communication to insights.nutanix.com, Nutanix‘s cloud telemetry service. This communication is done over port 443 (HTTPS). Therefore, this port must be allowed on any firewalls or proxies between the CVM or Prism Central and the internet to enable Data Lens functionality. https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000LJSWCA4

Prism Central provides a streamlined way to configure NTP across all managed clusters. This ensures consistency, improves accuracy, and simplifies management — making it the recommended approach for most environments.

At-rest encryption protects stored data, ensuring that sensitive information remains secure even if physical storage devices are compromised. Nutanix best practices prioritize data encryption for securing Volume Groups, which makes this the correct answer.

To meet the requirement of enabling shared access to a bucket while isolating internal and external users, the admin must
(1) configure directory services so that internal users are authenticated and grouped accordingly,
(2) generate access keys based on whether the user is from the directory or an email-based external consultant.
This setup allows differentiated access policies and enforcement of security boundaries.

Anomaly rules in File Analytics can trigger alerts for suspicious actions like mass deletes or access denials.

To manually add a signature to the ransomware block list in Nutanix Files, the administrator must download the existing block list as a CSV file, add the required signature, and upload the modified CSV back through the Files Console. This is the supported and correct process.

To deploy a new instance of Nutanix Files, the administrator should use the Files Console in Prism Central. This interface allows full lifecycle management of the Files service, including deployment, configuration, and monitoring.

Life Cycle Manager ensures that Acropolis Operating System (AOS) and the File Server Module are on compatible versions before installation or upgrade of Nutanix Files. These are the critical components for ensuring proper functionality and integration.

Nutanix File Analytics includes File Content Filtering capabilities starting with Files 3.6. It enables administrators to enforce data control by blocking uploads or access to specific file types, which is especially useful for ransomware prevention and policy enforcement.

Data Lens Audit Trails can be used to report on a specific user‘s activity within a Files environment1. Data Lens is a service that collects audit trails and analyzes them to help you meet compliance and governance objectives. To report on a specific user’s activity in Nutanix Files, the most appropriate tool is Data Lens Audit Trails. It allows administrators to: – Track file access by users, including reads, writes, and deletions. – Generate detailed reports showing user activities and interactions with specific files and directories. – Ensure compliance by monitoring and auditing user actions for security or regulatory requirements.

Distributed shares in Nutanix Files are designed to work in a multi-node environment to distribute the data across multiple nodes for redundancy, availability, and scalability. Since a single-node cluster does not meet this requirement, the administrator is unable to create a distributed share. If you are working with a single-node cluster, you will need to either convert it to a multi-node setup or use a local share instead.

Smart Tier is designed specifically to optimize storage by analyzing access patterns and offloading cold data to an object store (like Nutanix Objects or AWS S3). This ensures that only frequently accessed (hot) data remains on the high-performance Nutanix Files storage, which maximizes available space and lowers cost.

For a successful Objects deployment in Nutanix, one key configuration requirement is the setup of NTP servers on both Prism Element and Prism Central. This ensures that time is synchronized across the system, which is crucial for activities like logging, data consistency, and general operations. Without proper time synchronization, issues could arise in the object storage system.

Correct answer

The file server resides on a single node cluster

Correct: Distributed shares are not supported on single-node clusters. This functionality requires multiple nodes to distribute the data and metadata across FSVMs. If the file server is on a single node, the distributed share option is not presented.

The file server does not have the correct license

Incorrect: While licensing can affect some features, distributed share creation is not gated by a license type. The feature is tied more to architecture (multi-node) than licensing.

The cluster only has three nodes

Incorrect: Three nodes are sufficient to support distributed shares. Nutanix Files supports distributed shares as long as there are multiple nodes and the deployment requirements are met.

The cluster is configured with hybrid storage

Incorrect: Hybrid vs. all-flash storage configurations do not influence whether the distributed share option is available. This is unrelated to the share type configuration.

Details:

Distributed shares in Nutanix Files are designed to spread user and application load across multiple FSVMs for performance and redundancy. A single-node cluster cannot offer distribution, which is why the option to create a distributed share is hidden or unavailable. For this feature to be usable, the file server must reside on a cluster with at least two nodes to support the distribution of load and metadata coordination.

Smart Tier is Nutanix’s solution for automatically tiering data to the cloud object storage, such as AWS S3 or Azure Blob Storage, based on predefined policies. To configure Smart Tier, access and secret keys for the object store are mandatory. These keys are necessary for:
Authentication with the object storage.
Data movement between the on-prem Nutanix environment and the cloud.
Once the keys are provided, Smart Tier can seamlessly manage the movement of less-frequently accessed data to the object store, optimizing on-prem storage usage and cost.

When troubleshooting IOPS performance issues with Nutanix Volumes, especially when using iSCSI, the first component to inspect is the network bandwidth and quality between the Volume and the client system.
Here’s why:
Nutanix Volumes use iSCSI, a TCP/IP-based protocol, to present block storage to external clients. As a result, network performance directly impacts storage performance.
If the network is congested, experiencing high latency, or has packet loss, this can result in increased I/O latency and reduced IOPS throughput. Even if the underlying storage is healthy and not overutilized, poor network performance can make it appear slow from the client’s perspective.
TCP retransmissions, MTU mismatches, or even poor NIC configurations can throttle performance significantly.
Thus, before investigating the storage backend or replication settings, it‘s essential to validate the network path for bandwidth, jitter, and packet loss to determine whether the issue originates from outside the Nutanix cluster.

Nutanix Files supports modern, secure, and efficient protocols for file access: SMBv2, SMBv3, NFSv3, and NFSv4. These protocols provide necessary features like improved security (especially with SMBv3) and better performance for file-sharing operations in enterprise environments. Older and less secure protocols like SMBv1 and NFSv2 are deprecated and not supported for file access within Nutanix Files.

The issue in this scenario is that the file server is unable to resolve the domain name after an upgrade. The root cause is most likely related to DNS resolution problems, which can occur after system updates or changes.
1. DNS Entries for the Given Domain Name: The domain name should have valid DNS entries. A common problem might involve capitalization mismatches in the domain name, which could prevent the file server from correctly resolving the domain during post-upgrade operations.
2. DNS Server Addresses of the Domain Controllers: If the domain controllers‘ DNS server addresses are misconfigured or if the DNS servers do not have the correct entries for the Nutanix environment (such as prism-central.cluster.local), this will lead to failure in domain resolution. Ensuring that the DNS server responds within the expected time frame is essential for successful connectivity. 
Both of these steps are focused on ensuring that the domain name is resolvable and that the necessary DNS servers are accurately configured. This will address the connectivity issues post-upgrade.

Files Console Dashboard View

Incorrect: The Dashboard provides a high-level summary of the Files environment but does not present detailed metrics or per-share graphs such as open connections, number of files, or top shares by usage.

Files Console Data Management View

Incorrect: This view focuses on managing quotas, retention policies, and capacity planning. It is not intended for real-time performance or connection monitoring.

Files Console Shares View

Incorrect: The Shares view allows administrators to manage shares (create, edit, delete, permissions), but does not provide graphical monitoring or metrics like current connections or storage usage trends.

Correct answer

Files Console Monitoring View

Correct: The Monitoring View in the Files Console offers detailed graphs and analytics, including Storage Used, Open Connections, Number of Files, and Top Shares by Capacity or Connections. This is the appropriate section to investigate resource utilization issues.

Details:

The Monitoring View is the correct location to view real-time and historical metrics about Nutanix Files performance. It includes detailed graphs on usage, active connections, file counts, and the most active or storage-heavy shares. When troubleshooting performance or resource issues, this view gives administrators the visibility needed to diagnose and act on those problems.

When deploying Nutanix Objects, the following prerequisites are essential: 
Data Services IP (DSIP): This IP acts as the front-end endpoint for object storage access (S3).
DNS Configuration: Ensures proper resolution of internal cluster services and external APIs.
Microsegmentation is optional and used for advanced network segmentation (not a prerequisite).
AHV IPAM is supported; it doesn‘t need to be disabled — this was a misunderstanding. It can be enabled and used depending on your network configuration.

Before upgrading Object Manager or the Objects service, the MSP Controller must be upgraded. The MSP (Managed Service Provider) architecture in Nutanix Objects uses a control plane component called MSP Controller, which lives on Prism Central. This controller handles the lifecycle of Nutanix Object components. If MSP is not upgraded, Object Manager and other services may not be compatible with the new versions or might not show up for upgrade due to version mismatches. Thus, upgrading MSP is the required first step in the Nutanix Objects upgrade workflow.

Availability Zones

Incorrect: Availability Zones refer to isolated locations within a region designed for resilience and fault tolerance. However, the data protection method in question, as described, is more related to specific disaster recovery techniques and not the zoning of resources across a region.

NearSync

Incorrect: NearSync is a feature that offers near real-time data protection and replication with a recovery point objective (RPO) of 5 minutes. It is typically used for specific types of recovery, but it doesn’t necessarily match the method described in the question or exhibit.

Metro Availability

Incorrect: Metro Availability provides synchronous replication for disaster recovery in a metropolitan area, with a very low RPO. While it ensures high availability between two sites, it doesn’t fully align with the protection illustrated in the exhibit, which seems to be related to the more general disaster recovery and data protection mechanism.

Correct answer

Smart DR

Correct: Smart DR (Disaster Recovery) refers to Nutanix’s data protection solution that automates and optimizes disaster recovery processes. It ensures data is backed up and can be easily recovered across multiple sites, offering seamless failover and failback capabilities for a variety of workloads. This aligns with the protection shown in the exhibit, focusing on efficient disaster recovery and maintaining data integrity.

Details:

SmartDR (Smart Disaster Recovery) is the correct answer. SmartDR enables share-level, asynchronous replication between active Nutanix Files instances. It is managed through Prism Central, allowing administrators to define protection policies, schedules, and monitor replication jobs. In the active site, file shares are read-write, while shares in the standby site are read-only. These read-only shares can be used for backup purposes.

To maintain data integrity and availability during Nutanix Objects maintenance operations, pausing replication is a critical step. This prevents potential replication conflicts or data loss when one site or service is undergoing changes.

Verifying user permissions is the first step in troubleshooting access issues to Nutanix Object buckets.

Files can be upgraded effectively using LCM from either Prism Element or Prism Central. The recommended method involves upgrading both the File Server Management and Files Analytics through LCM.

File Analytics is the tool that allows administrators to create reports on file sizes and schedule them to be automatically generated on a regular basis, such as weekly. This helps with ongoing file management and ensures that administrators have up-to-date information regarding file usage and trends. The other options listed are related to managing and monitoring file shares but do not specifically provide the ability to automate the reporting of file sizes.

Nutanix Files uses a distributed share architecture to balance load and provide redundancy. When folders are created within such shares, certain actions (like renaming) may require management through the Nutanix Files MMC Snap-in, especially when naming conventions or metadata validation is enforced.
This ensures consistency and correctness in a distributed namespace environment that cannot be fully managed through native Windows Explorer or traditional Microsoft MMC tools.

Correct answer

Tiered File

Correct: The “X” on the icon in Windows File Explorer often indicates a tiered file that has the offline attribute set. This happens when Smart Tier is enabled in Nutanix Files, moving infrequently accessed (cold) data to object storage. Windows displays the “X” to denote that the file isn’t locally available for immediate access.

Corrupt ISO

Incorrect: This is unrelated to the Files UI or tiering. Corrupt ISOs would raise a different error, not show as an “X” on a file share.

Distributed shared file

Incorrect: This term refers to how data is managed across FSVMs. It does not impact the icon representation in Windows.

Share Disconnected File

Incorrect: A disconnected share usually results in an access error, not an “X” icon on specific files. The icon “X” is tied to file state (offline), not share connectivity.

Details:

When Smart Tier is enabled in Nutanix Files, files may be offloaded from the file server to object storage to save space. These files are marked with the offline attribute, and Windows File Explorer displays a gray “X” icon to represent that the file is not currently available locally (i.e., a tiered file).

The “X” on a Files share icon in Windows File Explorer indicates that the file has the offline attribute set. This commonly occurs with tiered files.

To enable Nutanix Data Lens, two key requirements must be met:
Pulse health monitoring must be enabled so telemetry and file system metadata can be securely sent to Nutanix Insights (Data Lens backend).
A valid MyNutanix account must be configured so users can access the Data Lens UI to review insights, security anomalies, and usage trends. No additional manual steps like credential linking or Data Services IP configuration are required for Data Lens to begin functioning.

Prism Element administrators (local Prism admin users) are authorized to deploy File Analytics. This is because the deployment is tied to the management of the local Nutanix cluster, which is handled through Prism Element.

The prerequisite for performing one-click hypervisor upgrades on a cluster hosting Files is to disable the anti-affinity rules on all File Server VMs (FSVMs).

When a share is protected for the first time using SSR (Self-Service Restore) in Nutanix Files, the system creates a local snapshot of that share. This snapshot represents the baseline point-in-time state of the share and allows for recovery operations such as restoring previous versions of files or folders directly from the snapshot.
SSR operates based on a scheduled policy, which includes:
Hourly snapshots – taken at the 0th minute of every hour
Daily snapshots – taken at midnight
Weekly snapshots – taken at Sunday midnight
Monthly snapshots – taken on the 1st of the month at midnight
These schedules are customizable based on the cluster’s time zone, and users can browse and restore from these snapshots as needed.
While replication can also be configured to move data to a remote site, this is a separate process from SSR. Replication involves transferring snapshots to a recovery site and is typically used for disaster recovery (DR) scenarios, but it does not initiate automatically when enabling SSR.

Smart Tiering in Nutanix Files automates the movement of cold (infrequently accessed) files from file servers to a low-cost, S3-compatible object store to optimize primary storage usage.
To manage this efficiently, Smart Tiering has strict file size boundaries:
Minimum File Size: 64 KiB — Files smaller than this are not considered for tiering, ensuring performance efficiency.
Maximum File Size: 5 TiB — This is the supported upper limit per file for Smart Tiering.
These constraints ensure optimal tiering behavior and prevent issues with extremely small or very large files that might be inefficient or unsupported in tiered storage.

Before upgrading Nutanix Files or creating a file server, the Files Manager (FSM) on Prism Central must first be upgraded to a compatible version.
Why?
Files Manager (FSM) is the core management component of Nutanix Files within Prism Central.
It handles configuration, lifecycle operations, and upgrade orchestration for file servers and associated services.
The correct upgrade sequence is:
1. Upgrade Files Manager (FSM) on Prism Central.
2. Upgrade File Servers (FSVMs) on Prism Element.
3. Upgrade File Analytics, if used.
Skipping this order or using an outdated FSM may result in:
Incompatibility errors.
Inability to deploy or manage file servers.

File Analytics is a Nutanix Unified Storage feature that provides deep visibility into how your file services are being used, including user activity, file types, usage patterns, and security insights.
When deploying File Analytics, the network requirement is that it must use the Client-side network.
Here‘s why:
The Client-side network is the interface exposed to end-users and external systems.
File Analytics needs access to user data, access logs, and other metadata — all of which are accessed over the Client-side network.
This network ensures proper communication between File Analytics, the File Servers, and the users or systems generating activity on the shares.

Workload optimization for Nutanix Files is based on the file type and how files are accessed, either randomly or sequentially. This optimization started with Files 3.7, which introduced the ability to configure shares based on the size and access pattern of the files.
Key Considerations:
Random Access for small files (less than 128 KB) provides the best performance for workloads that require frequent access to many small files.
Sequential Access for large files (greater than 1 MB) provides optimal performance for workloads dealing with large, sequentially accessed files, such as media files or large backups.
This distinction allows Nutanix Files to optimize the underlying storage for the specific characteristics of the data, improving performance for both small and large file access patterns.

When scaling Nutanix Files (FSVMs), the following needs to be addressed:  –
Client IP addresses: Each FSVM requires one Client IP address. Since you are adding two FSVMs, you will need two additional Client IPs.
Storage IP addresses: Each FSVM also requires one Storage IP address for data communication. Therefore, two additional Storage IPs are needed for the new FSVMs.
In this case, scaling from four FSVMs to six requires 2 additional Client IPs and 2 additional Storage IPs.

The best way to monitor a Files environment for suspicious activities such as mass deletions or access denials is to deploy the Files Analytics VM and configure anomaly rules. This will allow the administrator to set up specific rules to detect unusual behaviors and receive alerts when such activities occur.
This method offers a comprehensive and tailored approach to monitoring file system activities for security and compliance purposes.

For a Microsoft Server Failover Cluster, shared block storage is essential, and this can be provided using Volume Groups within Nutanix. The Volume Group can be attached to multiple VMs and a bare metal server to ensure resiliency and failover capabilities.
This shared block storage will allow for the cluster nodes to have access to the same storage, ensuring that if one node fails, another can take over without data loss or downtime.

Nutanix Data Lens relies on unique identifiers and telemetry data tied to the original file server deployment. Cloning a file server results in duplicated identifiers and unsupported configurations, which prevent Data Lens from functioning properly. This limitation is documented, and cloned file servers are explicitly unsupported for Data Lens integration.

Accurate sizing depends on performance needs, object access rates, and storage growth expectations.

Within Data Lens, you can monitor these two audit trails: Client IPs and Files. Data Lens has an Audit Trails view that allows you to look up operation data for a specific user, file, folder, or client IP. The Audit Trails view includes Files, Folders, Users, and Client IP options. You can use the search bar to specify the entity for the audit (user, folder, file, or client IP), and the results table will present details for entities that match the search criteria. Clicking the entity name (or client IP number) will provide details for the target entity1. Data Lens also provides data auditing (Who is accessing what data?).

The metric used when sizing a Files deployment based on performance requirements is SMB concurrent connections.  When sizing for capacity and performance, consider factors like the number of virtual central processing units (vCPUs) and memory needed for each Files Storage Virtual Machine (FSVM).  Each FSVM requires a minimum of 4 vCPUs and 12GB memory. 
For example, a three FSVM deployment needs 12 vCPUs and 36GB memory.  Depending on the workload, each FSVM might need more vCPUs and memory.  The Nutanix Files sizing guide provides more information.

The cerebro service is not running on all CVMs within the target cluster

Incorrect: The cerebro service on the target cluster may impact management functions, but this specific alert refers to an issue with the container on the target cluster, not the cerebro service. The cerebro service is not directly involved in causing the issue described in this alert.

The container does not exist or is marked for removal on the source cluster

Incorrect: The alert pertains to a target cluster issue, not the source cluster. While issues on the source cluster could cause problems, the alert refers to the absence of the container or its removal status on the target cluster, not the source.

The cerebro service is not running on all CVMs within the source cluster

Incorrect: The cerebro service on the source cluster would affect replication, but this alert is specific to the target cluster and the container status there. So, this is not the correct cause of the issue described in the alert.

Correct answer

The container does not exist or is marked for removal on the target cluster

Correct: The alert indicates that the container on the target cluster is either missing or marked for removal. The container is necessary for synchronous protection of the Volume Group (VG), and without it, the replication cannot succeed, leading to the alert. This is the cause of the A130370 error.

Details:

The A130370 – VgSyncRepContainerNotFound alert occurs when there is an issue related to the container on the target cluster. This alert specifically indicates that the container, which is necessary for synchronous protection of the Volume Group (VG), is either missing or has been marked for removal on the target cluster. As a result, the replication process cannot proceed, and the protection of the VG is not possible. This issue is typically tied to misconfigurations or administrative actions that unintentionally mark the container for removal or delete it, which leads to the failure in synchronous replication. To resolve this, the administrator needs to verify the container’s status on the target cluster and ensure that it exists and is not marked for removal.

The WORM policy is designed to prevent deletion or modification of data for a specified period, making it critical for regulatory compliance and data protection. In this case, the audit failure occurred because data meant to be retained for 3 years was only protected for 1 year, due to the existing WORM policy. To resolve the compliance failure and ensure that no data is deleted prematurely, the administrator must modify the WORM policy to match the 3-year retention requirement.