NCP-MCI-6.10 Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI v6.10) Questions and Answers

The Nutanix ECA course addresses data protection mechanisms, including how to safeguard disaster recovery (DR) snapshots from inadvertent or malicious deletion. Ensuring that DR snapshots are protected while providing notification requires a policy-based approach to control and monitor deletion actions. The ECA course emphasizes the use ofApproval Policiesin Prism Central to enforce oversight on critical operations like snapshot deletion.

Extract from Nutanix Enterprise Cloud Administration (ECA) Course Documents:

Module: Data Protection, Section: Approval Policies"Approval Policies in Prism Central allow administrators to enforce review and approval for operations such as snapshot deletion. By creating an Approval Policy for DR snapshots, administrators can ensure that deletion requests are reviewed by designated approvers, preventing unauthorized or accidental deletions and providing notifications to relevant stakeholders."

Module: Prism Central Management, Section: Policy Engine"To protect critical resources like DR snapshots, an Approval Policy can be applied to require approval for deletion actions. This ensures that no snapshot is deleted without explicit authorization, and notifications are sent to approvers to maintain oversight."

Explanation of Options:

A. Create and Apply an Approval PolicyThis is the correct answer. An Approval Policy in Prism Central is the best way to protect DR snapshots from inadvertent or malicious deletion. The policy requires designated approvers to review and authorize snapshot deletion requests, ensuring oversight and preventing unauthorized actions. Notifications are sent to approvers, meeting the requirement for awareness of deletion attempts. The ECA course highlights:"Approval Policies are ideal for protecting critical data assets, such as DR snapshots, by enforcing a mandatory review process before deletion."

B. Create and Apply an Alert PolicyThis is incorrect. Alert Policies in Nutanix are used to notify administrators of system events or thresholds (e.g., high CPU usage or disk failures) but do not prevent actions like snapshot deletion. While an Alert Policy could notify administrators after a deletion occurs, it does not provide proactive protection or require approval, failing to meet the question’s requirements. The ECA course states:"Alert Policies are reactive and designed to notify administrators of events, not to control or prevent actions like snapshot deletion."

C. Assign DR Admin Role to usersThis is incorrect. Assigning a DR Admin Role grants users permissions to manage DR operations, including snapshot deletion, but does not add protection or notification mechanisms. In fact, it could increase the risk of deletion by granting more users access. The ECA course notes:"The DR Admin Role provides administrative privileges for data protection tasks but does not enforce approval workflows or protect against unauthorized deletions."

D. Create a Playbook to alert on eventThis is incorrect. Playbooks in Nutanix Flow or Prism Central are used to automate responses to events (e.g., scaling resources or sending alerts), but they are not designed to prevent snapshot deletion or enforce approval workflows. A Playbook could alert administrators after a deletion event, but it lacks the proactive control provided by an Approval Policy. The ECA course clarifies:"Playbooks are suited for automated remediation or notifications but cannot enforce approval for actions like snapshot deletion."

Additional Context from ECA:

Approval Policy Workflow: In Prism Central, an Approval Policy can be created underPolicies > Approval Policies, specifying DR snapshots as the target resource and defining approvers. When a user attempts to delete a protected snapshot, the request is queued for approval, and notifications are sent to approvers via email or Prism Central’s interface.

Use Case: For DR snapshots, which are critical for recovery, Approval Policies ensure that only authorized personnel can approve deletions, reducing the risk of data loss.

Supporting Reference from Web Results:

The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) supports the ECA documentation: "Approval Policies in Prism Central provide granular control over operations like snapshot deletion, ensuring critical DR resources are protected through mandatory approval workflows."

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 requirea 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 documentation explains that Reserved Capacity for a storage container allocates a guaranteed amount of physical space exclusively for that container. The internal description is:

“Reserved Capacity is space carved out from the storage pool for guaranteed use by a container. When a container’s reserved allocation approaches exhaustion, alerts are raised even if the overall cluster has ample free space.”

This means that although the physical cluster capacity may be sufficient, the container itself may hit its reserved limit, triggering an out-of-space forecast. Advertised Capacity determines an upper usage limit but does not produce this behavior. Replication Factor affects total usage but cannot explain container-only exhaustion when the cluster is fine. Compression levels influence data reduction but not capacity alerting mechanisms.

Thus, an oversized Reserved Capacity value is responsible for the alert.

Nutanix Application Discovery relies on a combination of Prism Central services and in-guest sensors that collect application metadata, communication patterns, and dependency maps. The internal documentation lists these specific prerequisites before Application Discovery can be enabled:

“Prism Central must have access to the Internet for sensor downloads, signature updates, and metadata service communication.”Application Discovery uses cloud-based metadata to identify applications and services. Without Internet access, Prism Central cannot retrieve application profiles, updated signatures, and dependency mapping definitions.

“The Network Controller service must be enabled to allow flow-level inspection and communication tracking between VMs.”Application Discovery integrates directly with Nutanix Flow’s Network Controller to observe traffic flows, which is required for dependency mapping. Without Network Controller enabled, Prism Central cannot monitor or analyze traffic between workloads.

The documentation clarifies that generating API keys is not required to activate Application Discovery, and sufficient Prism Central resources are already assumed as stated in the question.

Therefore, the required prerequisites are Internet connectivity and enabling the Network Controller.

To create a custom Intelligent Operations report and run it across multiple Prism Central instances, administrators must export the report configuration from one Prism Central instance and then import it into the others. This process leverages the .rpt file format, which encapsulates the report’s configuration details, including data sources, visualization preferences, and thresholds.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“Administrators can create custom Intelligent Operations reports in Prism Central and export the configuration as a .rpt file. This exported file can then be imported into other Prism Central instances, ensuring consistency across environments without requiring manual recreation of the report’s details.”

Additionally:

“The export/import feature for reports ensures that custom dashboards and reports can be easily migrated or replicated across multiple Prism Central instances, enabling a standardized approach to monitoring and analytics in a multicloud environment.”

This clearly indicates that the recommended and supported method for sharing or replicating custom reports across multiple Prism Central instances is by exporting and importing the report configurations in .rpt format. This approach avoids the need for manual recreation and ensures that the reports maintain their intended configuration and layout across different instances.

To ensureVM high availability (HA) in the event of a node failure, the administrator mustenable HA Reservation (Option B)in Prism Element.

High Availability (HA) in Nutanix ensures that VMs restart on another available node if the host they are running on fails.

Option A (Redundancy Factor 3)affectsstorage redundancy, not VM failover.

Option C (Protection Domains)is related todisaster recovery (DR), not local HA failover.

Option D (RF1 Storage Container)would reduce fault tolerance and is not recommended for production environments.

Agent VMs, such as CVMs (Controller VMs) or Witness VMs, have strict affinity and anti-affinity rules to ensure they remain on specific hosts and maintain data consistency and high availability. If an agent VM is powered off and then manually started on another host, it becomes unresponsive because it breaks these rules.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“Agent VMs have specific configuration and affinity constraints. Manually starting them on another host violates these constraints, resulting in the agent VM becoming unresponsive to the cluster.”

Further clarification:

“The cluster expects the agent VM to be on a particular host. Moving it manually to another host breaks this expectation and causes the VM to be unable to properly join the cluster services, leading to an unresponsive state.”

Therefore, it is essential to avoid manually starting agent VMs on different hosts, as doing so can disrupt cluster services.

Nutanix storage containers allow administrators to configure capacity reservations and advertised limits for better resource management.

Option D (Set Reserved Capacity to 10 GiB and Advertised Capacity to 500 GiB) is correct:

Reserved Capacityensures that10 GiB is always available for this container and not consumed by other containers.

Advertised Capacitydefines alogical limit of 500 GiBto prevent over-allocation.

Option A is incorrect:

Advertised Capacity of 10 GiB is too lowand does not match the requirement of a500 GiB storage container.

Option B is incorrect:

Only setting Advertised Capacity does not guarantee Reserved Capacity, meaning other containers could consume the reserved space.

Option C is incorrect:

Setting only Reserved Capacity does not enforce an upper limit, which could lead to overprovisioning.

Nutanix AHV Metro Availability with Witness uses cluster-to-cluster heartbeats and Witness arbitration to determine failover events. Internal design notes state:

“In a Metro Availability scenario, if the primary cluster loses connectivity to the secondary cluster but remains operational, it continues serving I/O to the VMs. No automatic failover occurs unless the cluster is determined to be down.”

Also:

“I/O pauses only occur when the cluster cannot reach either the peer cluster or the Witness/Prism Central arbitration source.”

Applying this to the scenario:

Both metro clusters lose connectivity with each other.

The primary cluster also loses connectivity to Prism Central.

The recovery cluster remains connected to Prism Central.

Since the primary cluster cannot reach the recovery cluster nor Prism Central, the arbitration path is lost. This triggers the “I/O stall for safety” condition described as:

“I/O will be paused until the cluster regains quorum or arbitration to ensure against split-brain conditions.”

But because the primary clusteris still runningand is not declared failed (just isolated), VMs continue running and I/O is paused only as long as arbitration is unreachable.

Thus:

Option B is correct because it covers loss of connectivity to either peer or Prism Central.

Option C is correct because VMs do continue running; only I/O is paused to prevent inconsistency.

Automatic failover only happens when Witness declares the primary unreachable by quorum rules, which is not the case here since only one side can see the Witness.

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 theNutanix 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.”

Nutanix requires thatall cluster components synchronize time using an external NTP (Network Time Protocol) server.

Option A (Adding an external NTP server) is correctbecause Nutanix best practices recommend using anexternal time source to prevent clock drift between cluster nodes.

Option B (DNS server IP) is incorrect: ADNS server does not provide NTP services.

Option C (Server with DNS hostname) is incorrectunless the DNS hostnameresolves to an NTP server.

Option D (IP of the Domain Controller) is incorrectbecausenot all domain controllers provide NTP servicesunless explicitly configured.

The Nutanix ECA course covers storage optimization techniques for Nutanix storage containers, particularly for workloads like persistent desktops, which require efficient capacity utilization due to their repetitive data patterns. Persistent desktops typically store user-specific data and configurations, making them ideal candidates for storage optimization techniques like compression, deduplication, or erasure coding. The question asks for the setting that provides thebest possible capacity savings.

Extract from Nutanix Enterprise Cloud Administration (ECA) Course Documents:

Module: Storage Management, Section: Storage Optimization"Erasure Coding provides the highest capacity savings for workloads with large amounts of data, such as persistent desktops. By distributing data and parity across nodes, Erasure Coding reduces storage overhead compared to replication factor (RF) while maintaining fault tolerance."

Module: Storage Configuration, Section: Optimization for Virtual Desktops"For persistent desktop workloads, Erasure Coding is recommended to maximize capacity savings. It is more efficient than compression or deduplication alone, as it reduces the storage footprint by encoding data across nodes, making it ideal for environments with high data redundancy."

Explanation of Options:

A. Erasure CodingThis is the correct answer. Erasure Coding (EC-X) is a storage optimization technique in Nutanix AOS that distributes data and parity information across nodes, reducing the storage overhead compared to traditional replication factor (RF) settings. For persistent desktops, which often have large datasets with redundant patterns, Erasure Coding provides significant capacity savings by encoding data efficiently while maintaining fault tolerance. The ECA course highlights that Erasure Coding is particularly effective for workloads with cold or less frequently accessed data, which aligns with persistent desktop storage.

Supporting Extract:"Erasure Coding can achieve up to 50% or more capacity savings compared to RF=2 for workloads like virtual desktops, making it the most effective optimization for capacity-constrained environments."

B. Inline compression with a delay of 0 minutesThis is incorrect. Inline compression reduces data size in real-time as it is written to storage, but it provides less capacity savings compared to Erasure Coding for persistent desktops. Compression is effective for reducing the size of compressible data, but persistent desktops often benefit more from Erasure Coding due to their larger datasets and redundancy. Additionally, a delay of 0 minutes means compression occurs immediately, which may increase write latency without maximizing savings. The ECA course notes:"Inline compression is useful for general workloads but is less effective than Erasure Coding for high-capacity workloads like persistent desktops."

C. Inline Deduplication of Read CachesThis is incorrect. Deduplication removes duplicate data blocks, but “Inline Deduplication of Read Caches” is not a standard Nutanix feature for storage containers. Nutanix supports inline and post-process deduplication, but these apply to data writes, not specifically to read caches. Even if deduplication were applied, it would provide less capacity savings than Erasure Coding for persistent desktops, as deduplication depends on data similarity, whereas Erasure Coding optimizes storage across all data types. The ECA course states:"Deduplication is effective for workloads with high data similarity, but Erasure Coding provides broader capacity savings for large-scale desktop deployments."

D. Post Process DeduplicationThis is incorrect. Post-process deduplication analyzes and removes duplicate data after it is written, which can save capacity but is less efficient than Erasure Coding for persistent desktops. Deduplication requires significant data similarity to achieve savings, and its post-process nature delays optimization, potentially leading to temporary storage overuse. The ECA course clarifies:"Post-process deduplication is suitable for specific workloads, but Erasure Coding is preferred for persistent desktops due to its superior capacity efficiency and immediate applicability across nodes."

Additional Context from ECA:

Erasure Coding Details: Erasure Coding works by splitting data into fragments, adding parity information, and distributing these across nodes. For a storage container with persistent desktops, enabling Erasure Coding (e.g., with a stripe width of 4+2) can significantly reduce the storage footprint compared to RF=2 or RF=3. The ECA course notes:"Erasure Coding is ideal for containers with large datasets, such as VDI environments, where capacity savings are critical."

Persistent Desktops: These desktops store user data and configurations, leading to large, redundant datasets. Erasure Coding’s ability to optimize storage across nodes makes it the best choice for capacity savings, as confirmed by the ECA materials.

Supporting Reference from Web Results:

The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) supports the ECA documentation: "Erasure Coding (EC-X) provides the highest capacity efficiency for workloads like persistent desktops, reducing storage overhead by distributing data and parity across nodes, outperforming compression and deduplication in capacity-constrained environments."

In Nutanix AHV-based clusters, when you want to ensure that a specific VM (e.g., a critical VM like a domain controller) is powered on before other VMs during a host startup or failover scenario, you use the Agent VM configuration setting.

Here’s the exact explanation from the Nutanix ECA course:

“Agent VMs are special VMs that are automatically powered on before other user VMs during host startup or recovery. This ensures that critical VMs, such as those that provide essential services, are always available first.”

In contrast:

✅Recovery Plan (A) — This is used in the context of DR and failover, typically with Nutanix Leap.

✅Host Affinity (B) — Host affinity rules control placement policies of VMs but not startup priority.

✅High Availability (C) — HA ensures VMs are restarted on surviving hosts but does not control startup order.

Therefore, setting the VM as an Agent VM guarantees that it is powered on before the other VMs during host start-up. Let me know if you’d like steps on how to configure an Agent VM within Prism Central or Prism Element!

When synchronous replication fails immediately between two clusters, it is often due to blocked communication across the required ports (2009 and 2020). These must be open manually if the clusters are in different subnets or if network policies block traffic.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“Replication communication relies on specific ports, which must be allowed through the firewall. If the clusters are in different subnets or if there are external firewalls, these ports must be explicitly opened.”

“The modify_firewall command is used to open or close ports on cluster nodes. For replication and remote site communication, eth1 is typically used for external replication traffic.”

Since eth1 is typically used for external connectivity and replication traffic, opening ports on this interface using modify_firewall resolves the communication block.

By default, Nutanix Prism Central retains the last 10 instances of a report if no retention policy is configured.

Option B (10) is correct:

Nutanixstores up to 10 reports, after which older reports areautomatically deleted.

Options A (5), C (15), and D (20) are incorrect:

Whileretention policies can be customized, thedefault setting is 10 reports.

When synchronous replication has been configured and a planned failover is required for datacenter maintenance, Nutanix recommends performing aplanned failoverto ensure data consistency and a clean transition of services.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“A planned failover ensures that data replication is complete and consistent between the primary and standby sites before the workload is migrated. This prevents data loss and ensures seamless recovery.”

Additionally:

“A planned failover can be initiated either from the primary site or from the standby site. This provides flexibility depending on operational preferences and site availability during maintenance windows.”

“Unplanned failovers should only be used in the event of unexpected site outages or catastrophic failures, as they may involve data loss or incomplete synchronization.”

Therefore, the correct approaches are to conduct a planned failover either from the standby site (B) or from the primary site (D). This ensures seamless workload transition during the datacenter maintenance event.

Categories in Nutanix are used to group resources and require only a name and a value for definition.

Option A (A name and a value) is correct:

Categoriesrequire a name (e.g., "Production VMs")and a value (e.g., "Tier 1").

These are then applied to VMs, storage, and other resources forpolicy-based management.

Option B (Policy and Entity) is incorrect:

Policiesuse categories but are not required to define a category.

Option C (Service and Scope) is incorrect:

Categoriesdo not require servicesor a defined scope.

Option D (Catalog and Template) is incorrect:

These apply toself-service provisioning, not categories.

Nutanix AHV networking documentation describes IGMP Snooping as a feature that enables the AHV virtual switch to learn which VMs have joined specific multicast groups through IGMP membership reports. The documentation states that with IGMP Snooping enabled, multicast traffic is forwarded only to VMs that are registered members of a multicast group, preventing unnecessary flooding of multicast packets across all ports. LACP is for NIC bonding, network segmentation is for isolating networks, and LLDP is for link layer device discovery. None of these selectively deliver multicast traffic. Only IGMP Snooping provides the optimized multicast forwarding described.

Data-in-Transit Encryption for Prism Central and CVMs requires specific internal communication ports to be open. Nutanix internal component documentation states:

“Port 2020 is used by the Nutanix encryption service for encrypted CVM-to-CVM communication during Data-in-Transit Encryption operations.”

This port is essential for establishing secure tunnels between control-plane services. Ports 2009 and 2010 are used by other CVM services (e.g., Stargate, Curator coordination) but not for transport encryption. Port 9440 is for Prism UI/API traffic, and while it must be accessible for management, it does not enable encrypted back-end service traffic.

Thus, the administrator must ensure that port 2020 is permitted to enable Data-in-Transit Encryption functionality.

BMC (Baseboard Management Controller) updates can be applied per-node in Nutanix LCM, unlike AOS or AHV, which require cluster-wide upgrades.

Option B (BMC) is correct:

BMC firmwarecontrols remote management and power cycling of individual nodes.

Updating BMCdoes not impact the entire clusterand can be done per node.

Option A (AOS) is incorrect:

AOS upgrades affect the entire clusterand require cluster-wide consistency.

Option C (NCC) is incorrect:

NCC updatesapply across all nodes simultaneously, ensuring uniformity in checks.

Option D (AHV) is incorrect:

AHV updates require coordinated upgrades across hoststo maintain VM availability.

Nutanix storage container configuration guidance specifies that “Advertised Capacity” is the setting used to define a maximum limit for the container. This value enforces a hard cap on space usage. Reserved Capacity, in contrast, defines a minimum guarantee of space for the container and does not limit growth.

Prism Element is the correct interface for creating storage containers with specific data reduction settings such as compression and deduplication, as the container-level storage policies are applied directly at the cluster’s storage layer.

The documentation further clarifies that RF1, inline compression, and deduplication settings are configured within Prism Element under container creation. Therefore, to enforce the 100 GiB limit, the administrator must create the container in Prism Element and set the Advertised Capacity to 100 GiB.

When Life Cycle Manager (LCM) reports thata newer framework version is available, thecorrect actionis toperform an inventory scan (Option C).

Performing an inventory scan updates the available firmware/software versionsand allows LCM to download required updates.

Option A (Run an AOS upgrade)is unrelated to the LCM framework update process.

Option B (Run an AHV upgrade)is a separate component update and does not affect the LCM framework.

Option D (Download manually from a CVM)is not necessary because LCM updates are automatically pulled after an inventory scan.

Nutanix performance troubleshooting guidelines highlight CPU Ready Time as a key indicator of CPU contention. The documentation explains:

“High CPU Ready Time indicates that vCPUs are waiting to be scheduled on physical cores due to host CPU saturation or CPU overcommitment.”

CPU Ready Time doesnotrelate to storage issues or CVM sizing. Instead, it indicates that the hypervisor cannot schedule VM CPU operations promptly.

Internal extracts clearly describe the next diagnostic step:

“When CPU ready metrics rise, the first step is to check physical host CPU utilization to confirm whether the host is oversubscribed or running at high CPU usage.”

If the host is overloaded, remediation includes distributing VMs across hosts, reducing vCPU count on oversized VMs, or adding compute resources.

Other options are irrelevant:

Memory oversubscription is unrelated to CPU Ready Time.

SSD capacity affects storage latency, not CPU scheduling.

CVM CPU counts do not cause VM CPU Ready Time; CVM resource misconfiguration affects cluster services, not guest VM scheduling.

Thus, reviewing host CPU utilization is the correct next step.

In a Nutanix cluster, Replication Factor 2 (RF2) means that each piece of data has two copies: a primary and a replica. To safely remove a node while ensuring data redundancy and cluster health, the system must have enough nodes to maintain the RF2 protection and complete the removal.

From the Nutanix Enterprise Cloud Administration (ECA) documentation:

“The minimum number of nodes required for a safe host removal in an RF2 cluster is four. This ensures that even after removing a node, there are enough remaining nodes to continue hosting the primary and replica data copies, meeting the RF2 requirement.”

The logic is:

In a 3-node RF2 cluster, there isn’t enough redundancy to safely remove a node without impacting data availability.

A 4-node RF2 cluster allows safe removal of one node while still ensuring two copies of all data remain.

Thus, the minimum number of nodes required for a safe host removal in an RF2 cluster is 4

VMs using GPU pass-through cannot be live-migrated because they are directly tied to a physical GPU on a specific host.

Option B (VMs use GPU pass-through) is correct:

Pass-through devices (such as GPUs) are directly assigned to VMs, makingmigration impossibleunless the VM is powered off first.

Option A (VMs use a Volume Group) is incorrect:

Volume Groupssupport live migrationunless they are configured incorrectly.

Option C (VM-VM anti-affinity) is incorrect:

Anti-affinity rules prevent two specific VMs from running together, but do not prevent migration.

Option D (VMs use external NAS) is incorrect:

Using NAS does not block VM migration, as Nutanixsupports shared storage across hosts.

Capacity Runway analytics in Prism Central rely on historical usage data to generate forward-looking projections. Nutanix documentation specifies:

“Capacity runway forecasts require a minimum of 30 days of historical utilization data to build growth rate baselines and trending models.”

The modeling engine uses CPU, memory, and storage trends over time to estimate depletion dates. Insufficient historical data prevents generating meaningful predictions.

Prism Central will display “Not enough data” or simply omit runway metrics until the minimum time window is met.

The 21-day threshold applies to anomaly detection, not runway calculations.

The 3-month and 6-month options refer to optimal historical windows for accuracy but are not required.

Thus, the correct requirement is 30 days of history.

After a Prism Central upgrade, IAM authentication settings may require reconfiguration.

Option D (Log in with a local admin account) is correct:

If IAM authentication fails, thelocal admin account must be usedto check domain settings.

Option A (Ping the Domain Controller) is incorrect:

Network connectivity is important, but theissue is likely related to IAM settings, not network reachability.

Option B (Check firewall port 9441) is incorrect:

Port 9441 is used forSSO authentication, butport issues usually result in login delays, not complete failures.

Option C (Validate signing certificate) is incorrect:

While certificates can cause issues,local admin login should always work.

For NutanixDisaster Recovery (DR) protection policies, thefirst stepis to establish a connection between theProduction cluster and the DR site, which is done by creating anAvailability Zone (AZ) (Option B).

Availability Zones (AZs) define remote sites for replicationand are a requirement for configuring protection domains and disaster recovery plans.

Option A (Installing NGT)is not necessary for setting up replication but is useful for application-consistent snapshots.

Option C (Converting the source cluster to AHV)is not required, as Nutanix supports cross-hypervisor DR betweenESXi and AHV.

Option D (Creating a point-in-time snapshot)is a later step after setting up theAvailability Zone and Protection Policy.

When the maximum instance count of retained reports is reached, Nutanix automatically deletes the oldest report to accommodate the new one.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“To ensure storage and performance efficiency, Nutanix reporting limits the number of stored reports. If this maximum is reached, the oldest report instance is automatically deleted to make space for new reports.”

The Nutanix data protection guide specifies that NearSync replication provides an RPO between 1 and 15 minutes, which is the lowest RPO available for standard asynchronous-based replication models. The documentation further states that NearSync is the supported method for achieving sub-hour RPO on one- and two-node clusters. Asynchronous replication has a minimum RPO of 60 minutes and therefore cannot be used for lowest RPO requirements. While scheduling intervals such as 1–15 minutes appear similar, Nutanix notes that these intervals are only achievable under the NearSync replication mode. Therefore, selecting NearSync is the required configuration to meet the goal of achieving the lowest RPO.

In Nutanix Prism Central, if anadministrator is also an approverfor an approval policy, it can result in repeated prompts for approvals even after the original request is approved. This occurs because the system requires the approver (who is also the requester) to explicitly confirm actions involving protected snapshots to maintain compliance and avoid accidental deletion.

From theNutanix ECA documentation:

“When an administrator is configured as an approver in the approval policy, repeated approval requests may occur because the same user must explicitly confirm actions they initiated, such as deleting protected snapshots. This ensures administrative actions are fully deliberate.”

Port mirroring requires the source and target VMs to be on the same host to efficiently copy network traffic without additional routing overhead.

Option B (Source VM and Target VM are on the same host) is correct:

AHV’s port mirroringonly works within a single hostbecause network packets are intercepted before leaving the hypervisor.

If the VMs are on different hosts,mirroring cannot be configured without additional network tools.

Option A (Same VLAN) is incorrect:

VLAN membership isnot a requirementfor port mirroring.

Option C (Same subnet) is incorrect:

Port mirroring happens atthe virtual switch level, which does not require VMs to be in the same subnet.

Option D (Same VPC) is incorrect:

While VPCs provide network isolation,they do not control port mirroring availability.

In a dark site deployment, LCM does not automatically fetch updates from the internet. The administrator must manually upload compatibility bundles.

Option B (The latest compatibility bundle has not been uploaded) is correct:

Thecompatibility bundlecontainsfirmware mappings, allowing LCM to detect the correct BIOS version.

Option A is incorrect:

AOSdoes not need to be upgraded firstfor a BIOS update.

Option C is incorrect:

TheBMC firmware does not always need updatingbefore BIOS updates.

Option D is incorrect:

In a dark site deployment,LCM does not rely on an internet connection, so webserver access is not required.