An administrator has performed an AOS upgrade, but noticed that the compression on containers is not happening. What is the delay before compression begins on the Files container?
30 minutes
60 minutes
12 hours
24 hours
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.”
Which error logs should the administrator be reviewing to determine why the relates service is down?
Solver.log
Arithmos.ERROR
Cerebro.ERROR
Tcpkill.log
The error log that the administrator should review to determine why the relay service is down is Cerebro.ERROR. Cerebro is a service that runs on each FSVM and provides relay functionality for Data Lens. Relay service is responsible for collecting metadata and statistics from FSVMs and sending them to Data Lens via HTTPS. If Cerebro.ERROR log shows any errors or exceptions related to relay service, it can indicate that relay service is down or not functioning properly. References: Nutanix Files Administration Guide, page 23; Nutanix Data Lens User Guide
An administrator is tasked with creating an Objects store with the following settings:
• Medium Performance (around 10,000 requests per second)
• 10 TiB capacity
• Versioning disabled
• Hosted on an AHV cluster
immediately after creation, the administrator is asked to change the name of Objects store
Who will the administrator achieve this request?
Enable versioning and then rename the Object store, disable versioning
The Objects store can only be renamed if hosted on ESXI.
Delete and recreate a new Objects store with the updated name
The administrator can achieve this request by deleting and recreating a new Objects store with the updated name. Objects is a feature that allows users to create and manage object storage clusters on a Nutanix cluster. Objects clusters can provide S3-compatible access to buckets and objects for various applications and users. Objects clusters can be created and configured in Prism Central. However, once an Objects cluster is created, its name cannot be changed or edited. Therefore, the only way to change the name of an Objects cluster is to delete the existing cluster and create a new cluster with the updated name. References: Nutanix Objects User Guide, page 9; Nutanix Objects Solution Guide, page 8
Which two platform are currently supported for Smart Tiering? (Choose two.)
Google Cloud Storage
AWS Standard
Wasabi
Azure Blob
The two platforms that are currently supported for Smart Tiering are AWS Standard and Azure Blob. Smart Tiering is a feature that allows administrators to tier data from Files to cloud storage based on file age, file size, and file type. Smart Tiering can help reduce the storage cost and optimize the performance of Files. Smart Tiering currently supports AWS Standard and Azure Blob as the cloud storage platforms, and more platforms will be added in the future. References: Nutanix Files Administration Guide, page 99; Nutanix Files Solution Guide, page 11
After migrating to Files for a company's user home directories, the administrator started receiving complaints that accessing certain files results in long wait times before the file is even opened or an access denied error message after four minutes. Upon further investigation, the administrator has determined that the files in question are very large audio and video files. Which two actions should the administrator take to mitigate this issue? (Choose two.)
Add the extensions of the affected file types to the ICAP's Exclude File Types field in the ICAP settings for the Files cluster.
Uncheck the "Block access to files if scan cannot be completed (recommended)" option in the ICAP settings for the Files cluster.
Enable the "Scan on Write" option and increase resources for the ICAP server.
Enable the "Scan on Read" option and decrease resources for the ICAP server.
Nutanix Files, part of Nutanix Unified Storage (NUS), is being used for user home directories, and users are experiencing delays or access denied errors when accessing large audio and video files. The issue is related to the integration with an ICAP (Internet Content Adaptation Protocol) server, which Nutanix Files uses to scan files for security (e.g., antivirus, malware detection). The delays and errors suggest that the ICAP server is struggling to scan these large files, causing timeouts or access issues.
Understanding the Issue:
ICAP Integration: Nutanix Files can integrate with an ICAP server to scan files for threats. By default, files are scanned on read and write operations, and if a scan cannot be completed (e.g., due to timeouts), access may be blocked.
Large Audio/Video Files: These files are typically very large (e.g., GBs in size), and scanning them can take significant time, especially if the ICAP server is under-resourced or the network latency is high.
Four-Minute Timeout: The “access denied” error after four minutes suggests a timeout in the ICAP scan process, likely because the ICAP server cannot complete the scan within the default timeout period (often 240 seconds or 4 minutes).
Long Wait Times: The wait times before opening files indicate that the ICAP server is scanning the files on read, causing delays for users.
Analysis of Options:
Option A (Add the extensions of the affected file types to the ICAP's Exclude File Types field in the ICAP settings for the Files cluster): Correct. Nutanix Files allows administrators to exclude certain file types from ICAP scanning by adding their extensions (e.g., .mp4, .wav) to the “Exclude File Types” field in the ICAP settings. Large audio and video files are often safe and do not need to be scanned (e.g., they are less likely to contain malware), and excluding them prevents the ICAP server from attempting to scan them, eliminating delays and timeout errors.
Option B (Uncheck the "Block access to files if scan cannot be completed (recommended)" option in the ICAP settings for the Files cluster): Correct. By default, Nutanix Files blocks access to files if the ICAP scan cannot be completed within the timeout period (e.g., 4 minutes), resulting in the “access denied” error. Unchecking this option allows access to files even if the scan fails or times out, mitigating the access denied issue for large files while still attempting to scan them. This is a recommended mitigation when scans are causing access issues, though it slightly reduces security by allowing access to un-scanned files.
Option C (Enable the "Scan on Write" option and increase resources for the ICAP server): Incorrect. The “Scan on Write” option is already enabled by default in Nutanix Files ICAP settings, as it ensures files are scanned when written to the share. Increasing resources for the ICAP server might help with scanning performance, but it does not directly address the issue of large files causing timeouts on read operations, and it requires additional infrastructure changes that may not be feasible. The issue is primarily with read access delays, not write operations.
Option D (Enable the "Scan on Read" option and decrease resources for the ICAP server): Incorrect. The “Scan on Read” option is also enabled by default in Nutanix Files ICAP settings, and it is the root cause of the delays—scanning large files on read causes long wait times. Decreasing resources for the ICAP server would exacerbate the issue by further slowing down scans, leading to more timeouts and errors.
Selected Actions:
A: Excluding audio and video file extensions from ICAP scanning prevents the server from attempting to scan large files, eliminating delays and timeouts for these file types.
B: Disabling the “Block access” option ensures that users can access files even if the ICAP scan times out, mitigating the “access denied” error after four minutes.
Why These Actions?
Excluding File Types (A): Large audio and video files are often safe and do not need scanning, and excluding them avoids the performance bottleneck caused by the ICAP server, directly addressing the long wait times.
Disabling Block Access (B): The four-minute timeout leading to “access denied” errors is due to the ICAP scan failing to complete. Allowing access despite scan failures ensures users can still open files, though it requires careful consideration of security risks (e.g., ensuring excluded file types are safe).
Combining these actions provides a comprehensive solution: excluding file types prevents unnecessary scans, and disabling the block ensures access during edge cases where scans might still occur.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Administration Guide (available on the Nutanix Portal):
“To mitigate performance issues with ICAP scanning for large files (e.g., audio, video), add the extensions of affected file types to the ‘Exclude File Types’ field in the ICAP settings for the Files cluster. Additionally, to prevent ‘access denied’ errors due to scan timeouts, uncheck the ‘Block access to files if scan cannot be completed (recommended)’ option, allowing access to files even if the scan fails.”
What is the minimum number of AHV nodes in a cluster required to use Objects?
1
2
3
5
Nutanix Objects, part of Nutanix Unified Storage (NUS), provides S3-compatible object storage and is deployed as a set of Object Store Service VMs on a Nutanix cluster running AHV (or ESXi). The minimum number of nodes required for an Objects deployment ensures high availability and fault tolerance.
Analysis of Options:
Option A (1): Incorrect. A single-node cluster does not meet the minimum requirements for Nutanix Objects, as it cannot provide the necessary fault tolerance and high availability. Objects requires at least three nodes to distribute Object Store Service VMs and ensure data redundancy.
Option B (2): Incorrect. A two-node cluster also does not meet the minimum requirements for Objects. Nutanix requires at least three nodes to ensure that the Object Store Service VMs can be distributed across nodes and maintain availability in case of a node failure.
Option C (3): Correct. Nutanix Objects requires a minimum of three AHV nodes in a cluster to deploy and operate. This ensures that the Object Store Service VMs (typically three or more) can be distributed across nodes, providing high availability and fault tolerance. A three-node cluster is the minimum configuration for Objects to ensure data redundancy and resilience.
Option D (5): Incorrect. While a five-node cluster can certainly support Objects, it exceeds the minimum requirement. Nutanix specifies that three nodes are sufficient for a basic Objects deployment, making five nodes unnecessary for the minimum requirement.
Why Option C?
Nutanix Objects requires at least three nodes to ensure high availability, fault tolerance, and data redundancy. This allows the Object Store Service VMs to be distributed across nodes, ensuring that the service remains available even if a node fails. Three nodes is the minimum cluster size specified by Nutanix for deploying Objects.
Exact Extract from Nutanix Documentation:
From the Nutanix Objects Deployment Guide (available on the Nutanix Portal):
“Nutanix Objects requires a minimum of three AHV nodes in a cluster to ensure high availability and fault tolerance. This allows the Object Store Service VMs to be distributed across nodes, providing redundancy and ensuring service availability in case of a node failure.”
Which prerequisite is required to deploy Objects on AHV or ESXi?
Prism Central version is 5.17.1 or later
Port 9440 is accessible on both PE and PC
Valid SSL Certificate
Nutanix STARTER License
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.”
An administrator wants to provide security against ransomware attacks in Files. The administrator wants to configure the environment to scan files for ransomware in real time and provide notification in the event of a ransomware attack. Which component should the administrator use to meet this requirement?
Protection Domain
File Analytics
Syslog Server
Files Console
Nutanix Files, part of Nutanix Unified Storage (NUS), can be protected against ransomware attacks using integrated tools. The administrator’s requirement to scan files for ransomware in real time and provide notifications involves a component that can monitor file activity, detect anomalies, and alert administrators.
Analysis of Options:
Option A (Protection Domain): Incorrect. Protection Domains in Nutanix are used for disaster recovery (DR) of VMs and Volume Groups, not for ransomware protection in Nutanix Files. Files uses replication policies (e.g., NearSync) for DR, and Protection Domains are not relevant for real-time ransomware scanning or notifications.
Option B (File Analytics): Correct. Nutanix File Analytics, integrated with Nutanix Files, provides real-time monitoring and anomaly detection for ransomware protection. It scans file activity, uses machine learning to detect unusual patterns (e.g., mass file deletions, encryption), and sends notifications to administrators in the event of a potential ransomware attack. This meets the requirement for real-time scanning and notification (as seen in Question 7, where anomaly alerts were configured in File Analytics).
Option C (Syslog Server): Incorrect. A Syslog Server can receive logs from Nutanix Files (as noted in Question 9), including alerts, but it is not a component that scans files for ransomware in real time. It is a passive logging tool and does not provide active ransomware detection or notification capabilities.
Option D (Files Console): Incorrect. The Files Console is the management interface for Nutanix Files, used for configuring shares, FSVMs, and policies. While it can display alerts, it does not perform real-time ransomware scanning or detection—that functionality is provided by File Analytics.
Why Option B?
File Analytics is specifically designed for data analytics and security in Nutanix Files, including real-time ransomware detection. It monitors file operations, detects anomalies indicative of ransomware (e.g., rapid file modifications, deletions), and sends notifications to administrators, meeting the requirement for real-time scanning and alerts.
Exact Extract from Nutanix Documentation:
From the Nutanix File Analytics Administration Guide (available on the Nutanix Portal):
“Nutanix File Analytics provides real-time protection against ransomware by monitoring file operations and detecting anomalies, such as rapid file modifications or deletions. In the event of a potential ransomware attack, File Analytics sends notifications to administrators, allowing for quick response and mitigation.”
What is the most efficient way of enabling users to restore their files without administrator intervention in multiple Files shares?
Click Enable next to the name of the share in Manage Recovery Settings from Data Lens.
Click Enable Self Service Restore in the Edit wizard for each share in Shares tab from Files Console.
Assign the same Category to all FSVMs and adding that Category to a single Protection Policy in PC.
Add all FSVMs to a Consistency Group within a single asynchronous Protection Domain in PE.
Nutanix Files allows users to restore their files from the snapshots taken by the protection policy. A protection policy is a set of rules that defines how often snapshots are taken, how long they are retained, and where they are replicated. A protection policy can be applied to one or more file shares. To enable users to restore their files without administrator intervention, the administrator must enable the Self Service Restore option for each share in the Files Console. This option adds a hidden folder named .snapshot in each share, which contains all the snapshots taken by the protection policy. Users can access this folder and browse the snapshots to find and restore their files. The administrator can also configure the permissions and quota for the .snapshot folder. References: Nutanix Files Administration Guide, page 75; Nutanix Files Self-Service Restore Guide
Nutanix Files, part of Nutanix Unified Storage (NUS), provides a Self-Service Restore (SSR) feature that allows end users to recover their files without administrator intervention. This feature is particularly useful for SMB shares, enabling users to access previous versions of files or folders directly from their Windows clients (e.g., via the "Previous Versions" tab in File Explorer).
The most efficient way to enable Self-Service Restore for multiple Files shares is to configure it at the share level within the Files Console. According to the Nutanix Files Administration Guide, the Self-Service Restore option can be enabled for each share individually through the Shares tab in the Files Console. While this requires enabling the setting for each share, it is the most direct and supported method for enabling SSR across multiple shares, as it does not involve external tools like Data Lens or complex configurations like Protection Policies or Consistency Groups.
Option A: Correct. Enabling Self-Service Restore in the Edit wizard for each share via the Shares tab in the Files Console is the standard method. It allows users to restore files directly without administrator intervention. While it requires configuring each share individually, it is efficient for a small to moderate number of shares and aligns with Nutanix’s recommended approach.
Option B: Incorrect. Nutanix Data Lens is a service for data governance, analytics, and ransomware protection, not for managing Self-Service Restore settings. Data Lens focuses on scanning shares for anomalies and providing recovery points, but it does not have a direct option to enable SSR for shares.
Option C: Incorrect. Assigning Categories to FSVMs and linking them to a Protection Policy in Prism Central is related to VM or resource protection (e.g., snapshots or replication), not to enabling user-driven file restoration for Files shares.
Option D: Incorrect. Consistency Groups and Protection Domains in Prism Element are used for data protection and disaster recovery (e.g., asynchronous replication), not for enabling Self-Service Restore for end users.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Administration Guide (available on the Nutanix Portal):
“Self-Service Restore allows end users to recover files and folders from SMB shares without administrator intervention. To enable Self-Service Restore, navigate to the Shares tab in the Files Console, select a share, and click Edit. In the Edit wizard, check the ‘Enable Self Service Restore’ option. This must be configured for each share individually.”
Additional Notes:
While enabling SSR for each share individually (option A) may seem less efficient for a very large number of shares, Nutanix does not currently provide a bulk configuration option for SSR in the Files Console. Automation via APIs could be an alternative for large-scale deployments, but this is not mentioned in the question’s options.
The question emphasizes “most efficient,” and option A is the most straightforward and officially supported method per the documentation.
An administrator needs to ensure maximum performance, throughput, and redundancy for the company’s Oracle RAC on Linux implementation, while using the native method for securing workloads.
Which configuration meets these requirements?
Flies with a distributed share and ABE
Files with a general purpose share and File Blocking
Volumes with MPIO and a single vDisk
Volumes with CHAP and multiple vDisks
Volumes is a feature that allows users to create and manage block storage devices (volume groups) on a Nutanix cluster. Volume groups can be accessed by external hosts using the iSCSI protocol. To ensure maximum performance, throughput, and redundancy for Oracle RAC on Linux implementation, while using the native method for securing workloads, the recommended configuration is to use Volumes with MPIO (Multipath I/O) and a single vDisk (virtual disk). MPIO is a technique that allows multiple paths between an iSCSI initiator and an iSCSI target, which improves performance and availability. A single vDisk is a logical unit number (LUN) that can be assigned to multiple hosts in a volume group, which simplifies management and reduces overhead. References: Nutanix Volumes Administration Guide, page 13; Nutanix Volumes Best Practices Guide
