Nutanix Certified Professional (NCP) NCP-US-6.5 Book

The action that is required to allow the deletion of file server audit data in Data Lens is to update the data retention period. Data retention period is a setting that defines how long Data Lens keeps the file server audit data in its database. Data Lens collects and stores various metadata and statistics from file servers, such as file name, file type, file size, file owner, file operation, file access time, etc. Data Lens uses this data to generate reports and dashboards for file analytics and anomaly detection. The administrator can update the data retention period for each file server in Data Lens to control how long the audit data is kept before being deleted. References: Nutanix Files Administration Guide, page 98; Nutanix Data Lens User Guide

Audit data in Data Lens is managed by a retention period, after which the data is automatically deleted. To allow deletion of audit data (e.g., to free up space or comply with policies), the administrator must update the retention period to a shorter duration, triggering the deletion of data that exceeds the new period. This is the standard method for managing audit data lifecycle in Data Lens.

Exact Extract from Nutanix Documentation:

From the Nutanix Data Lens Administration Guide (available on the Nutanix Portal):

“Audit data in Data Lens is retained for a configurable retention period. To allow the deletion of file server audit data, update the data retention period in the Data Lens console or Prism Central settings. Reducing the retention period will cause older audit data to be deleted once it exceeds the new period.”

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 Data Lens, part of Nutanix Unified Storage (NUS), provides data governance, analytics, and ransomware protection for Nutanix Files. Enabling Data Lens involves setting up access to the Data Lens service, which is a cloud-based service hosted by Nutanix, and integrating it with the on-premises file server.

Analysis of Options:

Option A (In Prism, enable Pulse health monitoring): Incorrect. Pulse is a Nutanix feature that collects telemetry data for health monitoring and support, sending it to Nutanix Insights. While Pulse is recommended for overall cluster health, it is not a required step for enabling Data Lens. Data Lens operates independently of Pulse and focuses on file server analytics, not cluster health monitoring.

Option B (Configure a MyNutanix account to access the Data Lens console): Correct. Data Lens is a cloud-based service, and accessing its console requires a MyNutanix account. The administrator must configure the MyNutanix account credentials in Prism Central to enable Data Lens and access its features, such as the Data Lens dashboard for monitoring file server activity. This is a mandatory step to integrate with the cloud service.

Option C (Configure the Data Services IP in Prism Central): Incorrect. The Data Services IP is used for iSCSI traffic in Nutanix Volumes (as noted in Questions 25 and 31), not for Data Lens. Data Lens communicates with the Nutanix cloud (insights.nutanix.com) over the internet and does not require a Data Services IP configuration.

Option D (Add File Services VM admin credentials to a MyNutanix account): Correct. To enable Data Lens for a file server, the administrator must provide the File Services VM (FSVM) admin credentials, which are used to authenticate and integrate the file server with the Data Lens service. These credentials are added via the MyNutanix account configuration in Prism Central, allowing Data Lens to access the file server for monitoring and analytics.

Selected Steps:

B: Configuring a MyNutanix account is required to access the Data Lens console and enable the service.

D: Adding FSVM admin credentials to the MyNutanix account ensures that Data Lens can authenticate and monitor the file server.

Exact Extract from Nutanix Documentation:From the Nutanix Data Lens Administration Guide (available on the Nutanix Portal):

“To enable Data Lens, configure a MyNutanix account in Prism Central to access the Data Lens console. Additionally, add the File Services VM admin credentials to the MyNutanix account to allow Data Lens to authenticate with the file server and enable monitoring and analytics features.”

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.