Free Nutanix NCP-EUC Practice Exam with Questions & Answers | Set: 5

This is because this option will allow the administrator to use Citrix Director to reset user profiles on a Nutanix Files share that provides high performance, scalability, and resilience3.

Citrix Profile Management is a solution that allows administrators to manage user profiles and settings across different devices and sessions12. Nutanix Files is a software-defined file storage solution that provides high performance and scalability for file data12. Nutanix Files supports all forms of profile management with efficient metadata caching techniques that optimize for faster VDI logon times12. Nutanix Files offers two types of shares: standard shares and distributed shares3. Standard shares are hosted on a single file server, while distributed shares are hosted on multiple file servers for load balancing and high availability3.

https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2079-Citrix-Virtual-Apps-and-Desktops:BP-2079-Citrix-Virtual-Apps-and-Desktops

Based on the given information, the administrator is deploying 1000 instant clone virtual desktops, 500 full clone virtual desktops, and 150 applications. To support these workloads, the Nutanix solution will need multiple storage containers.

According to the Nutanix Certified Professional - End User Computing (NCP-EUC) v6 guide, for VDI workloads, it is recommended to create a separate storage container for each type of desktop (e.g. instant clone, full clone) and another container for AppStacks. It is also recommended to have at least one container for metadata and one container for replicas.

Therefore, for this scenario, a total of 3 storage containers should be created:

One container for 1000 instant clone virtual desktops

One container for 500 full clone virtual desktops

One container for 150 applications delivered via AppStacks

So the answer is C. 3.

This issue is caused by the NVIDIA vGPU scheduling policy. On many NVIDIA GRID/vGPU architectures (prior to latest MIG capabilities), you cannot mix different vGPU profile sizes (e.g., 2Q and 4Q) on the same physical GPU.

Current State (Breadth Mode): The scheduler is likely distributing the "2Q" VMs evenly across all available GPUs. This means every physical GPU has at least one "2Q" profile active, "tainting" the GPU so it can only accept other "2Q" VMs.

The Fix (Depth Mode): By changing the allocation policy to Depth-First, the scheduler will fill up the first physical GPU with "2Q" VMs until it is full before moving to the next. This consolidates the "2Q" workloads onto fewer cards, leaving other physical GPUs completely empty. These empty GPUs can then accept the "4Q" profile type, allowing both profiles to co-exist on the same host (though on different physical cards).

The error code displayed in the exhibit, NET::ERR_CERT_AUTHORITY_INVALID, explicitly indicates that the browser does not trust the Certificate Authority (CA) that signed the SSL certificate presented by Prism Central.

According to the Nutanix Security Guide and Prism Central documentation regarding Security Certificate Management:

By default, Nutanix clusters and Prism Central use a self-signed certificate.

When an administrator accesses Prism via a web browser using these default certificates, the browser will display a security warning (such as "Your connection is not private") because the self-signed certificate authority is not in the browser's or operating system's Trusted Root Certification Authorities store.

To resolve this behavior, the administrator must either import the self-signed root certificate into the client's trusted store or replace the default certificate with one signed by a commercial or internal CA that the browser already trusts.

If the issue were related to the hostname missing (Option C), the error code would be NET::ERR_CERT_COMMON_NAME_INVALID. Since the error is specifically "Authority Invalid," the cause is the lack of trust in the issuer (CA).

In a Nutanix AHV cluster, resource management and Admission Control ensure that VMs are only powered on if there are sufficient physical resources (specifically Memory) available to back them.

A cluster designed to run an "average" of 800 VMs likely has its physical memory sized to accommodate that workload plus some buffer (HA). Attempting to power on 1400 VMs simultaneously (almost double the average load) on the same 6-node cluster will likely exhaust the available physical RAM. Once the cluster memory capacity is full, AHV will refuse to power on additional VMs, resulting in the state observed in Citrix Studio where many VMs remain off. Citrix network issues (Directory/Storefront) would typically result in registration failures or connection errors, not the inability of the hypervisor to power on the VM.

Frame is a cloud-native desktop-as-a-service platform that allows you to deliver virtual desktops and applications from any cloud. Frame supports multiple public clouds, such as AWS, Azure, GCP, and Alibaba Cloud2. You can bring your own public cloud account and use Frame to provision and manage your virtual desktops on demand.

Frame also supports Nutanix private cloud model running AHV, which is a native hypervisor for Nutanix Enterprise Cloud Platform. You can use Frame to deliver virtual desktops and applications from your own data center using Nutanix AHV clusters3. You can benefit from the simplicity, scalability, and performance of Nutanix hyperconverged infrastructure.

To achieve the requirement of bidirectional replication where a user can access their profile data locally at either site (Active-Active profile availability), the administrator should configure VDI Sync.

VDI Sync is a specialized configuration within the Nutanix Files ecosystem designed to synchronize User Profile directories across distributed file server instances. Unlike standard one-way Disaster Recovery (Smart DR) which is designed for failover, VDI Sync ensures that changes made to a profile at Site A are replicated to Site B, and vice-versa, allowing users to roam between physical locations while maintaining a consistent, local copy of their profile data.

ECC (Error Correcting Code) mode is a feature of some NVIDIA GPUs that provides error detection and correction for memory errors. However, ECC mode can interfere with vGPU functionality and prevent vGPU-enabled VMs from being created or started1. Therefore, two correct steps to resolve this issue are B (Disable ECC by running nvdia-smi -e 0) and D (Check if ECC Mode is turned on by running nvdia-smi -q | grep “ECC Mode” -A2).

https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000LKjOCAW

administrator can take to resolve the issue of performance for several full clone virtual desktops within Cluster01 by migrating them to Cluster02. 

a recovery plan is a set of steps that defines how to recover guest VMs from a disaster. A recovery plan can be used to migrate VMs between Nutanix clusters at the same or different availability zones1.

Nutanix AHV includes a native feature called VM High Availability (VMHA), which protects VMs in the event of a host failure (such as power loss).

When a host fails, the Acropolis High Availability service detects the failure. Built-in AHV policies automatically restart the affected VMs on the remaining healthy hosts in the cluster.

Live migration (Option D) is not possible because the host is already down (powered off), meaning the memory state cannot be transferred; the VMs must be restarted (booted) on new hosts. No manual policy creation (Option B) is required as this is a core default function of the AHV cluster, provided resources are available.