NCP-MCI-6-10 Practice Questions

:

When configuring application-consistent snapshots in a Nutanix protection domain for applications

such as SQL, Oracle, and Exchange, it is critical to group all related VMs in the same consistency

group within the protection domain. This ensures that the snapshot captures a consistent state of the

entire application stack.

From the Nutanix Enterprise Cloud Administration (ECA) course materials:

“A consistency group ensures that snapshots across multiple VMs are taken at the same time,

maintaining application consistency for distributed applications. This is especially important for

multi-tiered applications like SQL, Oracle, and Exchange, where data integrity depends on

coordinated snapshot creation.”

Additionally:

“For application-consistent snapshots, leverage guest tools or volume shadow copy services (VSS) in

Windows to quiesce applications, and configure the consistency group to include all relevant VMs.”

By creating one consistency group for all VMs comprising an application, the administrator ensures

that snapshots represent a consistent state across the application components.

The LCM (Life Cycle Manager) precheck failures in this scenario indicate an inability to connect to

vCenter to validate ESXi-specific checks, such as LACP configuration, HA, and pinned VMs. The

appropriate log to analyze the details of the LCM precheck failures is the 1cm_ops.out log.

From the Nutanix Enterprise Cloud Administration (ECA) course materials:

“The 1cm_ops.out log file contains detailed output and error information related to LCM operations,

including prechecks, execution, and post-checks. This log is essential for troubleshooting LCM

framework failures and understanding the root cause of any issues preventing upgrades.”

When creating a storage container in Nutanix, the administrator must configure the correct capacity

settings:

Option A (Prism Element with Advertised Capacity of 100 GiB) is correct:

Advertised Capacity defines logical limits for the container (i.e., how much space it reports as

available).

Inline Compression can be enabled directly in Prism Element.

Option B (Create in Prism Element without Advertised Capacity) is incorrect:

Without specifying Advertised Capacity, the container may consume unlimited storage.

Option C (Create in Prism Central with Reserved Capacity) is incorrect:

Reserved Capacity applies to Quality of Service (QoS) policies, not storage limits.

Option D (Create in Prism Central without capacity limits) is incorrect:

Prism Central can manage storage but does not directly enforce RF1 and compression policies.

Nutanix Storage Management Guide → Creating and Managing Storage Containers

Nutanix Bible → Replication Factor (RF) and Data Optimization

Nutanix KB → Inline Compression Best Practices in Nutanix AOS

VM templates in Nutanix are supported only when the VM’s disks reside on storage containers

configured with Replication Factor 2 (RF2) or higher.

Option C (VM has disks on RF2 containers) is correct:

VM templates require a minimum RF2 for fault tolerance.

RF1 containers do not meet Nutanix best practices for VM templates.

Option A is incorrect:

VMs protected by Protection Domains can be cloned, but this is different from creating a VM

template.

Option B is incorrect:

Agent VMs (e.g., Witness VMs) or Prism Central cannot be used as VM templates.

Option D is incorrect:

Nutanix VM templates are natively supported on AHV, not ESXi.

Nutanix VM Management Guide → Creating and Managing VM Templates

Nutanix KB → Storage Requirements for VM Templates

Windows Defender Credential Guard requires UEFI firmware and Secure Boot to function properly.

Option B (Enable UEFI with Secure Boot) is correct:

Credential Guard requires a UEFI-based boot mode rather than Legacy BIOS.

Secure Boot ensures only trusted OS components load, reducing attack surface for credential theft.

Option A (Update vCPU to 8) is incorrect:

Increasing vCPUs does not impact Credential Guard compatibility.

Option C (Use Windows Server 2022) is incorrect:

Windows Server 2019 supports Credential Guard; upgrading to 2022 is not required.

Option D (Update Memory to 16GB) is incorrect:

Credential Guard has no minimum RAM requirement beyond general OS needs.

Microsoft Docs → Requirements for Windows Defender Credential Guard

Nutanix AHV VM Management Guide → Enabling Secure Boot & UEFI for Windows VMs

The Update Guest OS feature (Option D) in Nutanix allows administrators to apply patches and

updates to a VM template by creating a temporary VM instance for modification.

How It Works:

A temporary VM is deployed from the template.

Administrators apply updates to the OS.

Once complete, the changes are saved back to the template.

Option A (Create VM from Template) is incorrect:

This feature creates a new VM from an existing template but does not update the template itself.

Option B (Complete Guest OS Update) is incorrect:

There is no specific Nutanix feature named "Complete Guest OS Update."

Option C (Update Configuration) is incorrect:

Updates VM hardware and policies but not the OS.

Nutanix Prism Central → Managing VM Templates and Guest OS Updates

Nutanix Bible → OS Management and Updates in Nutanix Environments

Nutanix KB → How to Patch OS in a Nutanix VM Template

When using FQDN instead of a Virtual IP in a scale-out Prism Central deployment, Nutanix enables

load balancing across multiple Prism Central instances.

Option A (Load balancing) is correct because it ensures that requests are distributed among multiple

Prism Central nodes, improving performance and redundancy.

Option B (Resiliency) is incorrect because resiliency is achieved through HA and replication, not

through FQDN configuration.

Option C (Segmentation) is incorrect because network segmentation is handled at the VLAN or

security policy level.

Option D (SSL Certificate) is incorrect because SSL certificates can be applied regardless of whether

FQDN or Virtual IP is used.

Nutanix Prism Central Deployment Guide

Nutanix Best Practices for Scale-Out Prism Central

Nutanix Support KB: Configuring FQDN for Prism Central

In a scale-out Prism Central deployment, using an FQDN (Fully Qualified Domain Name) enables load

balancing across multiple Prism Central instances.

Option A (Load balancing) is correct:

When an FQDN is used, Nutanix automatically distributes traffic between multiple Prism Central

nodes, improving performance.

Option B (Resiliency) is incorrect:

Resiliency is achieved through cluster redundancy, not by using an FQDN.

Option C (Segmentation) is incorrect:

Segmentation relates to network isolation rather than FQDN-based load balancing.

Option D (SSL Certificate) is incorrect:

SSL certificates can be applied to both FQDN and Virtual IP configurations.

Nutanix Prism Central Guide → Configuring Scale-Out Deployment

Nutanix KB → How FQDN Enhances Load Balancing in Scale-Out Prism Central

: