Free NCP-MCI-6-10 Practice Test

For Common Access Card (CAC) or any smart card authentication to be functional in Nutanix Prism, the system must be able to verify that the client certificate has not been revoked. This is a mandatory security check. Prism uses either a Certificate Revocation List (CRL) or the Online Certificate Status Protocol (OCSP) for this purpose. If a valid SSL certificate is uploaded but the corresponding CRL is not configured, Prism has no way to check the certificate's revocation status. As a security measure, the authentication process will fail, leading to the exact symptoms described in the question.

B. RSA key size is incorrect. An incorrect or non-compliant RSA key size would likely cause the certificate to be rejected during the upload process or be flagged as invalid by the system.
C. Online Certificate Status Protocol (OCSP) is not enabled. This is an alternative revocation method to CRL. While its absence would also cause failure if it were the intended method, a missing CRL configuration is an equally direct and potential cause.
D. Signature Algorithm is incorrect. An unsupported signature algorithm would likely result in the certificate being considered invalid upon upload, which contradicts the scenario where it "appears to be valid."

1. Nutanix Prism Central Guide (pc-2024.1), Security Management > Configuring Authentication > Configuring Smart Card Authentication: "When you enable smart card authentication, you must also configure a Certificate Revocation List (CRL) or Online Certificate Status Protocol (OCSP) service. Prism Central uses the CRL or OCSP service to check the revocation status of the smart card certificates." This statement confirms that configuring a revocation method like CRL is a required step.

2. Nutanix Security Guide (Version 6.5), Implementing Security Measures > Implementing CAC/Smartcard Authentication, page 63: "Nutanix supports two methods for checking certificate revocation status: Certificate Revocation Lists (CRLs) and Online Certificate Status Protocol (OCSP). You must configure one of these two methods for authentication to succeed." This explicitly states that one of the methods is mandatory for successful authentication.

3. Nutanix University, Nutanix Certified Professional (NCP) 6.5 Study Guide, Module 5: Security, Section: User Authentication: The courseware details the steps for configuring different authentication types, including smart cards. It emphasizes the requirement to configure a CA certificate chain and a corresponding revocation checking method (CRL or OCSP) for the authentication to be operational. The failure to configure the revocation check is a common reason for authentication failure.

To guarantee a transactionally consistent backup for a multi-tier application (e.g., an application with a database VM and a web server VM), all virtual machines that constitute the application must be placed within a single Consistency Group (CG). When an application-consistent snapshot is triggered for this CG, Nutanix uses the Nutanix Guest Tools (NGT) to coordinate with the Volume Shadow Copy Service (VSS) on each Windows VM simultaneously. This process quiesces the applications across all VMs at the same moment, ensuring that the entire application can be restored to a single, valid point-in-time without data corruption or logical inconsistencies between the application tiers.

B. Configure one consistency group for each VM. This would create separate, uncoordinated snapshots for each VM, resulting in a crash-consistent state between VMs, not an application-consistent state for the entire application.
C. Select application consistent snapshot checkbox in consistency group settings only. This action is necessary but insufficient. The primary requirement is to correctly group the application's VMs first; otherwise, the snapshot will not be consistent across the application.
D. Ensure that Windows VMs have in-guest mounted VHDX disks. Nutanix application-consistent snapshots operate on virtual disks (vDisks) attached to the VM at the hypervisor level, not on file-based virtual disks like VHDX mounted within the guest OS.

1. Nutanix Data Protection and Recovery with Prism Element Guide (AOS 6.5):

Section: Asynchronous Replication > Creating a Consistency Group for VMs

Content: "To ensure consistency for applications that run on multiple VMs, add all the VMs that the application runs on to the same consistency group." This directly validates that all VMs for a single application must be in one CG.

2. Nutanix University: Nutanix Certified Professional (NCP) - Multicloud Infrastructure 6.5 Courseware:

Module: Data Protection

Content: The courseware explains that a Consistency Group is used to group VMs that belong to the same application to take a single, application-consistent snapshot of the entire group. It emphasizes that for multi-VM applications, this grouping is essential for a valid recovery point.

3. Nutanix Prism Element Web Console Guide (AOS 6.5):

Section: Data Protection and Recovery > Requirements for VSS Snapshots

Content: The documentation lists requirements for VSS-based snapshots, which include having NGT installed and using supported disk types (SCSI or IDE). It does not list support for in-guest mounted disk files like VHDX, invalidating that option.

The lcmops.out log file is the primary log for all Life Cycle Manager (LCM) operations. It contains detailed, step-by-step information about the LCM workflow, including inventory collection, pre-checks, and the actual upgrade process. The errors shown in the exhibit are failures during the pre-check phase of an LCM update. Therefore, lcmops.out is the most appropriate and direct source for investigating the root cause of these specific failures related to vCenter connectivity.

A. genesis.out: This log tracks the status of the Genesis process, which manages the state (start/stop) of other cluster services. It does not contain operational details of LCM pre-checks.
C. 1cmwget.out: This log file specifically records the progress and errors related to downloading LCM software and firmware bundles. It is not relevant to pre-checks that validate the cluster's state.
D. catalog.out: This log is associated with the Prism Catalog service, which is used for managing virtual machine images. It is unrelated to the hardware and software updates performed by LCM.

1. Nutanix Life Cycle Manager Guide v2.5, Troubleshooting LCM section: This guide details the logging for LCM. It specifies that LCM logs, including lcmops.out, are located in the /home/nutanix/data/logs/ directory on any CVM and are essential for troubleshooting operational failures.

2. Nutanix Support Portal, KB 3777 - NCC Health Check: logbaycheck: This knowledge base article, while focused on the Logbay collector, lists key log files for troubleshooting. It identifies lcmops.out as a critical log for diagnosing issues with the Life Cycle Manager.

3. Nutanix University, Nutanix Cluster Administration (NCA) 6.5 courseware, Module 8: Cluster Management and Monitoring: The courseware explains that for troubleshooting specific Nutanix features like LCM, it is crucial to examine the logs corresponding to that service. It identifies lcmops.out as the log for LCM operations.

To create a storage container with a specific maximum capacity on a Nutanix cluster, an administrator uses Prism Element. The "Advertised Capacity" setting within the storage container configuration is used to define this maximum size limit. When this value is set, Prism generates alerts if the container's usage approaches the configured limit, effectively capping its usable space. The other specified settings, such as Replication Factor, compression, and deduplication, are also configured during this creation process within Prism Element.

B. This option is incomplete. While the task is performed in Prism Element, this answer fails to specify how the 100 GiB capacity limit is configured.
C. This option is incorrect because "Reserved Capacity" guarantees a minimum amount of storage for the container from the storage pool; it does not set a maximum size limit.
D. This option is incomplete and less direct. It does not specify how the capacity limit is set, and Prism Element is the primary interface for single-cluster management tasks.

1. Nutanix Prism Element Web Console Guide (AOS 6.5), Section: Creating a Storage Container:

The guide details the procedure for creating a storage container using the Prism Element web console. In the "Advanced Settings" section, it explicitly defines the Advertised Capacity field: "Enter the maximum storage size that this storage container can use from the storage pool." This confirms it is the correct setting for limiting capacity.

2. Nutanix University - Nutanix Hybrid Cloud Fundamentals Courseware, Module: Storage Management:

This courseware explains that "Advertised Capacity" is a logical space limit set on a storage container. It contrasts this with "Reserved Capacity," which is used to guarantee a specific amount of physical space for critical workloads, reinforcing the correct use of each setting.

3. Nutanix Bible, Section: Storage Containers:

This resource clarifies the distinction between storage container settings. It describes Advertised Capacity (also known as max capacity) as the method to set a soft limit on the container size, which aligns with the administrator's requirement to set a "Maximum storage capacity."

Creating a VM template is a standard lifecycle operation supported for virtual machines running on a Nutanix cluster. A VM having its virtual disks located on a container with Replication Factor 2 (RF2) is a common and fully supported configuration. RF2 is a data redundancy setting and does not impose any restrictions on creating VM templates. The other options listed describe specific scenarios where template creation is explicitly disallowed to maintain system integrity or data protection consistency.

A. A VM that is part of a Protection Domain cannot be converted to a template. This restriction prevents potential inconsistencies with the disaster recovery configuration.
B. System-level VMs, such as agent VMs (e.g., Nutanix Files) or the Prism Central VM itself, are managed appliances and cannot be converted into templates to ensure their stability and proper function.
D. The native "Clone to VM Template" feature within the Nutanix Prism interface is available only for VMs running on the AHV hypervisor. For ESXi, template management is performed through VMware vCenter.

1. Nutanix University - Nutanix Hybrid Cloud Fundamentals Courseware: The course material on VM Management details the prerequisites and limitations for creating VM templates on AHV, explicitly mentioning that VMs in protection domains are not supported.

2. Nutanix Prism Web Console Guide (for AHV), AOS 6.5: In the "VM Management (AHV)" section, under "Cloning a VM to a Template," the guide lists limitations. It states, "You cannot create a template from a VM that is part of a protection domain" and "You cannot create a template from an agent VM or a Prism Central VM." The entire feature description is within the context of the AHV hypervisor, implicitly excluding ESXi from this Prism-native workflow.

3. Nutanix Bible, Section "AHV VM Management": This resource, authored by a Nutanix Technical Marketing Engineer and widely used as a reference, explains that the "Clone to Template" functionality is a feature of AHV managed through Prism. It does not list the container's replication factor as a limitation, confirming that standard configurations like RF2 are supported.

Windows Defender Credential Guard is a Virtualization-Based Security (VBS) feature that isolates secrets to protect them from theft. A fundamental prerequisite for enabling VBS and Credential Guard on a guest virtual machine is the use of UEFI firmware. The current VM configuration specifies Legacy BIOS, which does not provide the necessary security architecture, such as Secure Boot, that VBS relies upon to create and protect the isolated LSA process. Therefore, the VM's firmware must be changed from Legacy BIOS to UEFI, and Secure Boot must be enabled to meet the requirements for Credential Guard.

A. Update vCPU to 8. VBS requires a minimum of 2 vCPUs. The existing configuration of 4 vCPUs is sufficient and does not need to be changed.
C. Use Windows Server 2022. Windows Server 2019 is a fully supported operating system for Windows Defender Credential Guard. An upgrade is not necessary.
D. Update Memory to 16GB. While VBS consumes a small amount of system memory, 8 GB of RAM is adequate for a Windows Server VM. There is no specific 16 GB requirement.

1. Nutanix AHV Administration Guide (AOS 6.5): In the "Security Management" section, under "Virtualization-Based Security (VBS) for Guest VMs," the guide states, "To enable VBS on a guest VM, ensure that the guest VM has UEFI firmware." This confirms the primary requirement for enabling features like Credential Guard on Nutanix AHV.

2. Microsoft Docs, "Manage Windows Defender Credential Guard": In the section "Hardware and software requirements," the documentation explicitly lists "UEFI, version 2.3.1 or later, with Secure Boot" as a mandatory firmware requirement. This applies to both physical and virtual machines.

3. Nutanix University, Nutanix Hybrid Cloud Fundamentals Course: The "AHV Virtual Machine Management" module explains that advanced security features, including vTPM and VBS, are only available for VMs configured with UEFI firmware, not Legacy BIOS.

The "Update Guest OS" feature, often referred to as updating an image in the Nutanix Prism interface, is designed specifically for maintaining VM templates. This process creates a temporary, writable virtual machine from the selected read-only template or image. An administrator can then power on this temporary VM, log in to the guest operating system, and apply necessary patches, updates, or software installations. Once the modifications are complete and the VM is powered off, the changes are saved back to the original image, and the temporary VM is automatically deleted. This ensures that future VMs deployed from this template will include the updates.

A. Create VM from Template: This action creates a new, independent, and persistent VM from a template. It does not modify or update the source template itself.
B. Complete Guest OS Update: This is the final step in the update workflow, used to finalize the changes and delete the temporary VM. It is not the feature that initiates the process.
C. Update Configuration: This feature is used to modify a VM's hardware specifications, such as vCPUs, memory, or disk sizes, not for patching the guest operating system.

1. Nutanix Prism Central Guide (pc-2022.9), Image Management > Updating an Image:

"When you update an image, Prism Central creates a VM and attaches a copy of the selected image file to the VM as a disk. You can then log on to the VM, install or update applications, and apply patches to the OS. After you have made the changes, you can complete the update process from the VM dashboard or the Images dashboard. When you complete the update process, Prism Central deletes the VM and updates the image." This quote directly describes the process mentioned in the question.

2. Nutanix University, Nutanix Hybrid Cloud Fundamentals Course, Module: VM Management:

The courseware explains that to update a 'golden image' or template, you use the update image workflow. This workflow temporarily converts the image to a VM for maintenance, such as OS patching, and then saves the changes back to the image, deleting the temporary VM. This aligns with the functionality described as "Update Guest OS".

In a scale-out Prism Central deployment, a native Virtual IP (VIP) provides high availability by ensuring that if the leader Prism Central VM fails, another VM takes over the VIP address. However, all traffic is directed to the single leader VM. Configuring an FQDN that resolves to an external load balancer provides the additional functionality of distributing UI and API requests across all available Prism Central VMs in the cluster. This distribution of traffic is load balancing, which improves performance and scalability by preventing any single VM from becoming a bottleneck.

B. Resiliency: The native Virtual IP already provides resiliency through an active-passive failover mechanism, so this is not an additional function.
C. Segmentation: Network segmentation is a security and network architecture concept, not a direct function provided by using an FQDN with a load balancer in this context.
D. SSL Certificate: SSL certificates can be applied directly to Prism Central for the VIP or configured on the load balancer for the FQDN; it is not a unique additional capability.

1. Nutanix Prism Central Guide (pc-2023.4), Section: Prism Central Administration > Expanding (Scaling Out) a Prism Central Instance. The guide states, "You can also configure an external load balancer to distribute the user requests among the Prism Central VMs. The load balancer provides a single FQDN for all the Prism Central VMs." This explicitly describes the function of load balancing.

2. Nutanix Hybrid Cloud Reference Architecture, Section: Management Plane > Prism Central. The document clarifies the distinction: "For scale-out Prism Central deployments, you can use the built-in VIP for high availability or an external load balancer for both high availability and load balancing." This directly identifies load balancing as the additional capability.

3. Nutanix University, Nutanix Enterprise Cloud Administration (NCP-MCI) 6.5 Courseware, Module: Prism Central Administration, Section: Scaling Prism Central. The course material explains that while the VIP provides a floating IP for high availability, an external load balancer is used to distribute traffic across all nodes for improved performance, which is the definition of load balancing.

In a scale-out Prism Central deployment, a Virtual IP (VIP) provides high availability by creating a single, resilient management endpoint. If the Prism Central VM hosting the VIP fails, the VIP automatically fails over to another VM in the cluster. Configuring a Fully Qualified Domain Name (FQDN) with DNS round-robin to resolve to the individual IP addresses of all Prism Central VMs adds the benefit of load balancing. This distributes user interface and API requests across all nodes in the cluster, preventing any single VM from becoming a performance bottleneck and improving overall scalability.

B. Resiliency: The Virtual IP (VIP) itself is the primary mechanism for providing resiliency and high availability, making this not an additional function of the FQDN.
C. Segmentation: Network segmentation is a security and network architecture concept unrelated to the choice between a VIP and an FQDN for accessing Prism Central.
D. SSL Certificate: While an FQDN is the standard and best practice for issuing a trusted SSL certificate, the primary additional functionality in a multi-node, scale-out context is load balancing.

1. Nutanix Prism Central Guide (v2023.4):

Section: Load Balancing in a Scale-Out Deployment

Content: "For a scale-out Prism Central deployment, you can use a load balancer of your choice. You can also use domain name system (DNS) round-robin load balancing. The load balancer distributes the requests among the Prism Central VMs." This directly confirms that using a DNS-based FQDN provides load balancing.

2. Nutanix Prism Central Guide (v2023.4):

Section: Prism Central High Availability

Content: "A scale-out Prism Central deployment uses a virtual IP address (VIP) to provide a single endpoint for users and API clients. If a Prism Central VM becomes unavailable, the VIP address moves to another Prism Central VM in the instance..." This clarifies that the VIP's core function is resiliency, which is not the additional benefit sought by the question.

3. Nutanix University: Nutanix Hybrid Cloud Fundamentals Courseware:

Module: Prism Central Administration

Content: The courseware explains that while the VIP ensures high availability for the Prism Central service, scaling out requires a method to distribute the load. It specifies using an external load balancer or DNS round-robin with an FQDN as the method to achieve this traffic distribution across the multiple Prism Central instances.

Before migrating a VM or its vDisks to a different storage container, it is mandatory to remove the VM from any Protection Domain or Protection Policy. The Nutanix platform prohibits the migration of protected VMs to prevent inconsistencies in the data protection and disaster recovery configuration. The administrator must first unprotect the VM, perform the migration, and then re-apply the protection policy. This ensures the integrity of the snapshot and replication chain.

A. Validate network latency is below 5 milliseconds. This is a requirement for synchronous replication between sites (Metro Availability), not for a vDisk migration within the same cluster.
C. Verify Multichannel Support is enabled. SMB Multichannel is a performance feature for Nutanix Files (SMB shares) and is not relevant to the underlying block storage vDisk migration process.
D. Ensure storage optimization options match between storage containers. This is incorrect. Nutanix supports migrating vDisks between containers with different storage optimization settings (e.g., compression, deduplication). The data is transformed to match the destination container's policy during the migration.

1. Prism Web Console Guide (AOS 6.5), Chapter: VM Management, Section: Migrating a VM or vDisk to a Different Storage Container:

"You cannot migrate a VM that is part of a protection domain. To migrate a protected VM, you must first remove it from the protection domain, migrate the VM, and then add it back to the protection domain." This directly supports answer B.

"You can migrate vDisks between storage containers with different settings for storage optimization features (compression, deduplication, or erasure coding)." This directly refutes answer D.

2. Nutanix Metro Availability Witness Guide (Version 2.1), Chapter: Requirements and Recommendations, Section: Network Requirements:

"The round trip latency (RTT) between the Nutanix clusters at the two sites must be less than 5 milliseconds (ms) for synchronous replication." This confirms that the 5ms latency requirement is for inter-site synchronous replication, not intra-cluster operations, refuting answer A.

3. Nutanix Files User Guide (Version 4.4), Chapter: SMB Share Management, Section: SMB Share Properties:

"Enable multichannel: Select to enable SMB multichannel on the share. SMB multichannel allows clients to establish multiple network connections to a file server over a single network interface card (NIC) or multiple NICs." This shows that Multichannel is a Nutanix Files feature, making answer C irrelevant to the question's scenario.