Free Practice Questions for Nutanix NCP-US Exam

According to File Auditing and Analytics for your Nutanix Files Enterprise Cloud1, File Analytics is a feature that captures real-time user audit data and file metadata for Nutanix Files environments. It allows you to create custom reports based on various criteria such as file type, size, owner, access time, etc.

According to Nutanix Files 3.8 and File Analytics 3.0 | Nutanix Community2, File Analytics allows you to add new file categories based on custom file extensions such as .zyx or .zzz. You can then use File Distribution View to see a collapsed view of space usage, number of files, and changes within a given time frame for each file category.

Therefore, if the administrator needs to analyze data created by a custom application that uses custom-built file extensions such as .zyx or .zzz, they can add a new file category in File Analytics and use File Distribution View to provide the required information.

According to the Nutanix Unified Storage (NCP-US) v6 documentation, when a node fails in a 3-node cluster, the FSVM (File Server Virtual Machine) will automatically restart on one of the remaining nodes. The remaining nodes will handle the storage traffic without requiring any user intervention.

https://portal.nutanix.com/page/documents/solutions/details?targetId=NVD-2151-Unified-Storage:high-availability-at-the-nutanix-files-level.html

According to Nutanix documentation on unified storage (NCP-US) v6, Lifecycle policies enable administrators to ensure that objects in a bucket expire after a certain period of time. You can set rules to automate the transition of objects to different storage classes or to expire them altogether. This feature helps to manage storage costs by reducing the need to manually manage data retention policies for individual objects in a bucket.

Lifecycle policies allow you to define rules for automatically deleting or archiving objects in a bucket after a certain period of time1. This feature can help you reduce storage costs and manage data retention.

Creating a Files distributed share with multi-protocol access would allow for easy and efficient transfer of log files between the Linux collector package and the Windows application. This would provide simplicity in terms of configuration and management, and would also ensure that the log files are stored in a distributed and highly available manner, making it easier to access them as and when required.

, Files is a software-defined scale-out file storage solution that provides a single namespace for unstructured data2. Files supports both SMB and NFS protocols, which means you can access the same share from both Linux and Windows machines3. This would provide the best performance and simplicity for your log collector package and analysis application.

 According to Nutanix documentation on unified storage (NCP-US) v6, to automatically delete backups older than one year, an administrator should modify the existing bucket lifecycle policy to set the expiration period to one year. Lifecycle policies enable administrators to automate the transition of objects to different storage classes and to expire them altogether. In this scenario, modifying the existing bucket lifecycle policy to shorten the expiration period to one year will ensure that backups older than one year are automatically deleted to free up space in the cluster.

https://portal.nutanix.com/page/documents/details?targetId=Objects-v3_1:v31-lifecycle-policies-rule-c.html

According to Nutanix Objects User Guide1, an object store is a logical grouping of buckets that share a common namespace and configuration settings. A bucket is a container for objects that can be accessed by authorized applications and users using S3-compatible APIs.

Objects Storage provides a simple and scalable S3 compatible storage tier on top of your Nutanix AOS platform2. There is no limit on objects per bucket3, but there is a limit on the total capacity of an object store that can be configured during its creation or modified later4.

Therefore, if an object store is shared with multiple users, it is possible that other users have written to the buckets in the object store and consumed its assigned capacity limit.

The garbage collection process is performed by Curator, a service that runs on Nutanix clusters and is responsible for cleaning up unused data and reclaiming space12. Curator scans run periodically in the background and can be monitored from Prism2.

https://next.nutanix.com/how-it-works-22/ncc-health-check-garbage-egroups-39097

The administrator should avoid allocating over half the RAM on a host to a FSVM because the FSVM would cross NUMA node boundaries (option A).

NUMA (Non-Uniform Memory Access) is a memory architecture that divides the system memory into multiple regions that are assigned to different processors or cores.

If a FSVM crosses NUMA node boundaries, it will have to access memory from different regions, which will result in higher latency and lower performance for file operations.

To avoid this issue, the administrator should ensure that the FSVM memory allocation is within a single NUMA node boundary.

SSR allows users to restore their own files without the assistance of administrators1. It can be enabled on a share level by using a PowerShell script1.