NCP-US-V6-5 Nutanix Practice Questions

Nutanix Data Lens is a SaaS-based data governance and security service that requires its own subscription license, separate from the core Nutanix software licenses (like Pro or Ultimate) and the Nutanix Files license. Its features, such as global data visibility, ransomware protection, and smart tiering, are licensed based on the amount of data being managed.

For asynchronous replication schedules configured via Protection Domains in Prism Element or Prism Central, the minimum supported RPO is 60 minutes. To achieve lower RPOs like 15 minutes or near-synchronous replication, other technologies such as NearSync (down to 1 minute) or Metro Availability (RPO of 0) would be required.

Erasure Coding is a data protection method that increases storage efficiency. Instead of keeping multiple full copies of data (replication factor), it breaks data into fragments and calculates parity strips. This allows the cluster to tolerate node failures while consuming significantly less raw storage capacity. This is highly beneficial for large-scale Nutanix Objects deployments, which often store petabytes of data.

Nutanix Files relies on a directory service to map UNIX UIDs to user identities to enforce permissions. Even if the client's IP is allowed, if Files cannot find a valid user in AD/LDAP corresponding to the UID in the NFS request, it will deny permission. Since other clients work, the issue is likely specific to this user's identity configuration in the central directory, as shown in the diagram.

Nutanix rack awareness ensures that data replicas or erasure coding strips are placed across different physical racks. When combined with an appropriate Erasure Coding scheme (e.g., 8 data/4 parity), the cluster can tolerate the failure of up to 4 nodes. By making the cluster aware of the rack topology, the administrator ensures that a single rack failure will not take out all copies of a piece of data, thus meeting the high availability requirement.

File Analytics is the Nutanix solution designed for data security and governance. It includes a specific ransomware protection feature that uses a combination of file extension blocking (based on a curated list of signatures) and behavioral analysis to detect and block ransomware activity in real-time. SSR and snapshots are reactive recovery measures, not proactive blocking. File blocking is manual, and ICAP integration is for antivirus scanning, not behavioral analysis.

Nutanix Objects includes a built-in Identity and Access Management (IAM) service, similar to AWS IAM. This allows the creation of individual users, groups, and policies to enforce granular permissions on S3 buckets and objects. This is the correct way to achieve multi-tenancy and secure isolation on a single Objects cluster. Deploying separate clusters is inefficient, and sharing primary keys is a major security violation.

Smart Tiering is a feature of Nutanix Data Lens that allows administrators to create policies for automatically moving cold or inactive data from Nutanix Files to a compatible S3 target, such as Nutanix Objects or a public cloud provider. Policies are based on data age and access time, making it the ideal solution for this requirement. Smart DR is for disaster recovery, and File Analytics is for security auditing.

Flash Mode pins the Volume Group's data in the SSD tier of the Nutanix cluster, ensuring all I/O is served from the fastest storage layer. This significantly reduces latency and provides predictable high performance, which is critical for transactional databases.

Using multiple iSCSI initiators from the client (e.g., the database server) allows for load balancing across multiple CVMs that are hosting the iSCSI target. This, combined with MPIO, increases throughput and provides high availability by creating multiple paths for I/O.

The Nutanix Files deployment process automatically creates the required computer objects in Active Directory. The administrator provides a user account with sufficient permissions (e.g., rights to create computer objects in a specific OU), and the deployment workflow handles the object creation. Pre-creating the objects is not required and can cause deployment failures.