Free NCP-EUC Practice Test Questions and Answers (2026)

Prism Central’s Capacity > Rightsizing view lists “Over-Provisioned VMs”, where memory demand is consistently lower than configured. This report lets the administrator confirm wasted RAM across many desktops without opening each VM.

A – Task Manager must be checked per VM and cannot provide cluster-wide insight. C – NCC health checks are infrastructure diagnostics; they do not analyse VM-level memory utilisation. D – Capacity Runway summarises overall cluster growth trends, not individual VM memory usage.

1. Nutanix Prism Central Guide v.2023.1, “Rightsizing VMs – Over-Provisioned List”, p. 141.

2. Nutanix Capacity Planning Tech Note, TN-2210, p. 7, “Use the over-provisioned VM report to reclaim idle CPU or memory.”

The browser displays a "Your connection is not private" error because the name used in the URL (the DNS name) does not match any of the names listed in the SSL certificate's Subject Alternative Name (SAN) field. When a certificate is created, it must include all FQDNs and IP addresses that will be used to access the service. Since the connection works via IP address but fails via the DNS name, it indicates the certificate is valid in other respects but is missing the specific DNS name in its SAN list, causing a name mismatch error.

A. This browser doesn't trust the issuing Certificate Authority: If the Certificate Authority (CA) were untrusted, the error would also occur when connecting via the IP address, as the same certificate is used.
B. Certificate was only applied to one PCVM: In a scale-out Prism Central cluster, the SSL certificate is automatically synchronized and applied to all PCVMs.
D. This browser is not supported: An unsupported browser might cause rendering or functional issues, but it would not cause a standard SSL certificate name mismatch error like the one shown.

1. Nutanix. (2023). Prism Central Guide v6.7. Section: Installing an SSL Certificate. "When generating a Certificate Signing Request (CSR), you must include the FQDN of the Prism Central VM cluster and the IP address of each PCVM in the Subject Alternative Name (SAN) field."

2. Nutanix University. (2023). Nutanix Security Administration. Section: Certificate Management. "A common cause for browser certificate warnings is a mismatch between the hostname in the URL and the names present in the certificate's SAN field. Ensure all access methods (FQDN, IPs) are included."

During Nutanix LCM maintenance, a host is placed into maintenance mode. If Horizon provisioning remains enabled (Option D), it will continue to attempt to create new desktops. If the host in maintenance mode contains a critical component for cloning, such as a replica VM for Linked Clones or a parent VM for Instant Clones (Option C), the provisioning task will fail because that resource is temporarily unavailable. Therefore, both are direct causes of the issue.

A. LCM didn't inventory the environment successfully before starting maintenance. An LCM inventory failure would typically prevent the maintenance operation from starting, not cause provisioning errors during the process.
B. The cluster is experiencing high CPU/memory load, causing provisioning issues. While high load can cause provisioning failures, the specific context of LCM maintenance points to a host's unavailability as the direct cause.

1. Nutanix End User Computing Design Guide, Chapter: Operationalizing Horizon on Nutanix, Section: Maintenance and Updates. "Before performing maintenance on the Nutanix cluster, such as Nutanix software or firmware updates with LCM, we recommend disabling provisioning for the desktop pools in the Horizon Connection Server."

2. Omnissa (VMware) Horizon Documentation, Document: Setting Up Virtual Desktops in Horizon, Section: Creating and Managing Instant-Clone Desktop Pools. The documentation explains the role of parent VMs on each host, implying that if a host is unavailable, new clones cannot be created on it.

The error message "The length of the string exceeds the value set on the maxJsonLength property" indicates that the Nutanix AHV Plugin for Citrix is trying to process a list of snapshots that is too large for its default configuration. This was a known limitation in older versions of the plugin when encountering a high number of snapshots in the cluster (nearly 5,000 in this case). Upgrading the plugin to a more recent version resolves this issue, as the limit was increased in subsequent releases to accommodate larger environments.

B. Downgrading the plugin would likely re-introduce or perpetuate the limitation, not resolve it.
C. Uninstalling and re-installing the same version of the plugin will not change the underlying code or its inherent limitations.
D. The problem is caused by too many snapshots; therefore, increasing the number of snapshots would only worsen the issue.

1. Nutanix Support Portal, KB-8751: "MCS: "maxJsonLength" error when creating or editing a catalog". This knowledge base article directly identifies the problem and states the resolution is to "Upgrade the Nutanix AHV plugin for Citrix (aka MCS plugin) to version 2.7.0 or newer."

2. Nutanix AHV Plugin for Citrix Release Notes (v2.7.0): "Fixed an issue where catalog creation or update might fail if the cluster has a large number of snapshots (over 4,000)." This confirms the fix is included in newer versions.

For performance-sensitive workloads like End-User Computing (EUC), the optimal configuration is to set the host's power management policy to "High Performance". This setting prevents the CPU from entering lower power states (C-states) or reducing its clock frequency (P-states). This ensures that CPU resources are immediately available at maximum speed when a user interacts with their desktop, providing a consistently responsive experience and minimizing latency, which is critical in VDI environments.

A. CPU and Memory shares set to high: While beneficial during contention, this is a VM-level setting and less foundational than the host's power management policy for overall performance.
B. Memory reservation at 50% and local swap files: Reserving memory is generally not recommended for VDI as it reduces VM density and can complicate High Availability (HA) calculations.
D. Memory overcommit set to disabled: While disabling memory overcommit is a strong best practice for VDI, setting the host power policy to high performance is a more fundamental prerequisite for all performance workloads.

1. Nutanix University, "Nutanix End User Computing Design" course materials, Module on "Nutanix Platform and Architecture". The course emphasizes setting BIOS power settings to "High Performance" as a foundational step for EUC deployments.

2. Nutanix Best Practices Guide, "Citrix Virtual Apps and Desktops on Nutanix" (BP-2073), Section "Nutanix Storage", Subsection "Host and Cluster Settings". The guide explicitly states: "Set the power management policy on all Nutanix hosts to High Performance."

To install and run Windows 11 on a Nutanix AHV VM, several prerequisites must be met at the VM configuration level. These include enabling UEFI firmware, Secure Boot, and attaching a virtual Trusted Platform Module (vTPM). These are mandatory requirements enforced by the Windows 11 installer. Credential Guard, while a powerful security feature that leverages virtualization-based security (VBS) and is supported on AHV, is not a mandatory prerequisite for installing or running the Windows 11 operating system. It is an optional feature that can be enabled within the OS after installation.

A. vTPM: Windows 11 requires a TPM 2.0 device for security features and installation. AHV provides this through a configurable vTPM, making it a mandatory requirement.
B. UEFI: Windows 11 requires the VM to be configured with UEFI firmware instead of the legacy BIOS. This is a non-negotiable installation requirement.
D. Secure Boot: This is a security standard required by Windows 11 to ensure the boot process is secure. It must be enabled in the VM's UEFI settings.

1. Nutanix AHV Administration Guide (v. 6.5), "VM Management" > "Creating a VM (AHV)" > "Support for Virtual Trusted Platform Module". The guide explicitly lists UEFI, Secure Boot, and vTPM as requirements for Windows 11 VMs.

2. Microsoft Corporation, "Windows 11 System Requirements". Official Microsoft documentation lists TPM 2.0, UEFI, and Secure Boot capability as minimum system requirements for the OS. Credential Guard is documented as a feature, not an installation prerequisite.

Role-Based Access Control (RBAC) is the security paradigm designed to assign permissions to users based on their roles within an organization. In Prism Central, an administrator can create custom roles with specific privileges (e.g., view-only, VM management) and assign these roles to Active Directory groups that correspond to departments. This ensures that users only have the permissions necessary to perform their job functions, directly fulfilling the requirement to set permissions based on department and enhancing security by adhering to the principle of least privilege.

A. Creation of a single local user for each department: This creates shared accounts, which is a poor security practice as it eliminates individual accountability and complicates auditing.
B. Securing traffic by through Network Segmentation: This controls network traffic flow between VMs (east-west security) but does not manage user permissions for system administration.
C. Cluster Lockdown through PC: This feature restricts direct access to CVMs via SSH, enhancing cluster security at the node level, not at the user/role management level.

1. Nutanix Prism Central Guide (pc-2022.9), Chapter: "Security Management", Section: "Role-Based Access Control". This section details how to create roles and assign them to users or groups to control access to entities.

2. Nutanix University. (2023). Nutanix End User Computing Administration (EUCAD) Courseware. Module: "Securing and Hardening EUC". This courseware explains that RBAC in Prism Central is the primary method for delegating administrative tasks based on organizational structure.

To enable Secure Boot on an AHV guest VM, the VM must be configured to use UEFI firmware instead of the legacy BIOS. When you select UEFI boot for a VM in Prism, the underlying virtual machine hardware model is automatically set to q35, as the i440fx (legacy) machine type does not support UEFI. While vTPM is a related security feature, Secure Boot is fundamentally dependent on the UEFI firmware and the corresponding q35 machine type.

A. A CD-ROM drive is not a prerequisite for either vTPM or Secure Boot functionality; it is standard virtual hardware but unrelated to these security features.
C. Secure Boot is a feature of the UEFI specification and is not available with legacy BIOS firmware. Enabling it requires UEFI, not BIOS.
D. A vTPM is a virtualized device and does not require or use a physical hardware TPM on the host via pass-through.

1. Nutanix University. (2023). Nutanix Hybrid Cloud Fundamentals Course. Module: AHV Virtual Machine Management. "Secure Boot for guest VMs requires UEFI boot, which is supported on the q35 machine type."

2. Nutanix. (2023). AHV Administration Guide v6.7. Section: "VM Security Management" > "Creating a VM with UEFI Boot". The guide states, "To enable Secure Boot for a VM, you must configure the VM to use the UEFI firmware." The UI automatically selects the q35 machine type when UEFI is chosen.

For persistent VDI desktops, enabling all available data efficiency features—compression, deduplication, and Erasure Coding (EC-X)—provides the most optimized storage configuration. Inline compression and deduplication reduce the initial storage footprint of the OS, applications, and some user data. Over time, much of the data in a persistent desktop becomes "cold" or infrequently accessed. Erasure Coding is a post-process technology that is ideal for increasing capacity efficiency on this cold data without impacting the performance of "hot," actively used data. This combined approach maximizes usable storage capacity.

A. Disabling Erasure Coding misses a significant opportunity for post-process capacity savings on cold data common in persistent desktops.
B. Disabling deduplication is not optimal, as persistent desktops still share a common base OS and applications where deduplication provides value.
C. Disabling both deduplication and Erasure Coding leaves significant potential storage savings unrealized, leading to higher storage costs.

1. Nutanix. (2023). VMware Horizon on Nutanix Design Guide. Version 5.2. Section: Storage Design. Recommends enabling compression, deduplication, and Erasure Coding for persistent desktop pools.

2. Nutanix. (2023). Nutanix Bible by Steven Poitras. Section: Erasure Coding (EC-X). Describes EC-X as suitable for VDI workloads to increase storage efficiency on data that is no longer write-intensive.

3. Nutanix. (2022). Nutanix Tech Note TN-2033: Data Efficiency. Section: Erasure Coding. States that EC-X is a good fit for workloads with a mix of hot and cold data, such as persistent VDI.

The user complaints of settings not being retained and slow logins are classic symptoms of using local profiles with non-persistent desktops. A virtual disk-based profile solution, such as FSLogix Profile Containers or Citrix Profile Management, resolves these issues. This technology captures the entire user profile into a VHD(X) file stored on a network share. At login, this container is mounted to the desktop, providing fast access to a persistent profile. This ensures all application settings are retained between sessions and dramatically reduces login times.

A. Microsoft Roaming Profiles are an older technology known for causing profile corruption, data bloat, and the very slow login times the users are experiencing.
B. Incorporating user-specific application settings into the base image is not a scalable or practical solution, as it would require a unique image for each user.
D. Mandatory Profiles would prevent users from saving any changes to their profile, directly contradicting the goal of retaining application settings between sessions.

1. Nutanix End User Computing Design (May 2023), Section: Profile Management, Page 28. "For non-persistent desktops, we recommend using a profile management solution that redirects the user profile to a file share... FSLogix Profile Container is the leading solution."

2. Nutanix University, "NCP-EUC 6.5 Study Guide", Chapter 4: Optimizing the User Experience, Section: Profile Management. The guide discusses the benefits of container-based profiles for non-persistent VDI to ensure persistence and improve login performance.

The Citrix License Manager Daemon listens on TCP port 27000 by default. This port is required for inbound communication from Citrix products (e.g., Virtual Apps and Desktops Delivery Controllers) to the License Server to request and check out licenses. While other ports are used for management, port 27000 is the fundamental port for the core licensing service communication that must be open on any firewall between the product servers and the license server.

A. 59: This port is not a standard port used by any core Citrix Licensing services.
B. 3269: This port is used for secure access to a Microsoft Active Directory Global Catalog server (LDAPS), not Citrix Licensing.
C. 8083: This is the default port for the Web Services for Licensing, used for management consoles, not the primary license checkout process.

1. Citrix Product Documentation, "Licensing - System requirements," Communication ports section. The documentation explicitly lists "License Server port number: 27000" for the License Manager daemon.

Capacity Reservation is a Nutanix feature that guarantees a specified amount of storage capacity is always available within a storage container. By setting a capacity reservation, an administrator ensures that space cannot be consumed by other workloads, thin-provisioned virtual disks, or snapshots. This is the direct mechanism to ensure a container has sufficient space to accommodate a specific-sized workload, preventing out-of-space errors for critical applications or desktops.

A. Linked Clones: This technology saves storage space by sharing a common base disk; it does not reserve or guarantee available space within the container.
C. A Storage Pool: A storage pool is a group of physical disks. While a container resides in a pool, creating the pool itself does not reserve space for a specific container.
D. Thick Provisioning: This applies to individual virtual disks (VMDKs/VHDs), reserving their full size upon creation. It does not reserve space at the container level for a broader workload.

1. Nutanix Prism Web Console Guide (v6.5), "Main Dashboard > Storage Container Details > Updating a Storage Container". The guide explains the "Capacity Reservation" field: "Enter the amount of storage capacity (in GiB) to reserve on this storage container... This guarantees a minimum amount of storage is available for the container."

For non-persistent Machine Creation Services (MCS) workloads, individual virtual machines are disposable and created from a master image. Migrating these transient VMs is illogical and inefficient. The correct procedure is to prepare the master or base image on the source environment, replicate it to the target Nutanix cluster, and then use this replicated image to create a new machine catalog and provision new, non-persistent desktops on the Nutanix platform. This ensures a clean deployment using the new infrastructure's capabilities.

A. Nutanix Move is for migrating stateful, persistent VMs. It is not the appropriate tool for stateless, non-persistent desktops which are meant to be recreated.
B. MCS is a core Citrix technology that works with on-premises deployments on various hypervisors, including Nutanix AHV, as well as with Citrix Cloud.
D. Non-persistent workloads are commonly deployed on Nutanix. The migration strategy simply involves redeploying from a master image rather than migrating live VMs.

1. Nutanix University. (2023). Nutanix End User Computing Administration (NEUCA) Courseware. Module: Migrating EUC Workloads. The course describes the strategy for non-persistent VDI, which involves creating new catalogs from a master image on the target cluster.

2. Citrix Tech Zone. (2022). Citrix DaaS on Nutanix Cloud Platform. Reference Architecture, Section: Migration Strategy. "For non-persistent workloads, we recommend creating new machine catalogs and delivery groups in the new environment... Replicate the master images to the new environment."

A persistent VDI desktop provides each user with a dedicated virtual machine that retains all user settings, data, and user-installed applications between sessions. This model most closely mimics a traditional physical desktop, thereby minimizing application compatibility concerns and providing a familiar user experience. While it has more management overhead than non-persistent VDI, it is the best method for directly replacing a physical desktop where user personalization and application state are important.

A. Remote PC utilizes the user's existing physical desktop for remote access; it does not replace it with a virtual one.
B. Hosted Shared Desktops use a server OS, which can introduce application compatibility issues for software designed specifically for client operating systems.
C. Non-Persistent VDI resets the desktop to a pristine state at logoff, which does not meet the implicit requirement of a physical desktop replacement where user changes persist.

1. Nutanix. (2023). Nutanix End-User Computing Solutions. Section: "Desktop Types." This document describes persistent desktops as ideal for users who require a personalized environment, similar to a physical PC, including developers and power users.

2. Citrix. (2023). Citrix Virtual Apps and Desktops Handbook. Chapter 3: "VDI Models." The handbook explains that persistent desktops (personal desktops) are assigned to individual users and are best for knowledge workers who need to install their own applications.

3. Nutanix University. (2023). NCP-EUC 6.5 Study Guide. Section 2.1: "Differentiate between VDI desktop provisioning methods." The guide contrasts persistent VDI as a 1:1 user-to-desktop mapping that preserves changes, against non-persistent models.

Inline Erasure Coding (EC-X) is a data protection and space-saving technology that can be used in conjunction with other features like inline compression. While traditional redundancy factor (RF2/RF3) creates full data copies, EC-X uses parity calculations, which consumes significantly less storage space. For a persistent desktop, which has unique user data, EC-X provides space savings on data protection overhead regardless of the data content, making it a complementary technology to compression.

A. Storage Pools are logical groupings of physical disks and are a foundational element of storage configuration, not a space-saving technology itself.
C. Increased Redundancy Factor (e.g., moving from RF2 to RF3) consumes more storage space to provide higher data availability, it does not save space.
D. Capacity Deduplication is most effective on datasets with many duplicate blocks, like linked-clone VDI. It offers minimal benefit for persistent desktops with unique user data.

1. Nutanix AOS 6.5 Advanced Administration Guide, "Data Efficiency," Section: Erasure Coding (EC-X). This section details how EC-X provides space savings over replication-based redundancy factors and can be combined with compression and deduplication.

2. Nutanix Tech Note, "NTNX-1010: Data Efficiency," Section 2.2 Erasure Coding: "Erasure coding provides a space-efficient alternative to replication factor for data protection."