The Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI v6.10) (NCP-MCI-6.10)

The NCC alert indicates connectivity failure to the remote site. Resolving this involves confirming network connectivity and re-establishing the remote site configuration if necessary.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“The primary ports used for replication between clusters are 2009 (for Prism Element API) and 2020 (for data replication). Ensuring these ports are open and reachable is critical for remote site connectivity.”

Also:

“If the remote site has been re-imaged or reconfigured, it may have a new cluster incarnation ID. In such cases, the remote site configuration must be recreated to align with the current cluster information.”

Steps like checking ping with MTU 9000 (D) are not directly related to remote site connectivity for replication, and NAT configurations (B) are generally not recommended unless explicitly required.

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.

The Nutanix Enterprise Cloud Administration (ECA) course provides detailed guidance on managing images in a multicloud environment, particularly when administering multiple clusters across different geographic sites via a single Prism Central instance. The goal of optimizing image uploads to all locations involves ensuring efficient image availability, minimizing latency, and balancing storage and network resource usage. The ECA course emphasizes the use ofImage Placement Policiesto control how images are distributed and stored across clusters registered with Prism Central.

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

Module: Image Management, Section: Image Placement Policies " Prism Central allows administrators to manage images centrally for multiple clusters. Image Placement Policies define how images are distributed to clusters. A policy with Soft Enforcement ensures that images are uploaded to a preferred cluster and replicated to other clusters as needed, optimizing for network efficiency and availability while allowing flexibility if a target cluster is unavailable. "

Module: Prism Central Management, Section: Multi-Cluster Image Management " For environments with clusters at different geographic sites, an Image Placement Policy with Soft Enforcement is recommended to optimize image uploads. This policy allows Prism Central to select a primary cluster for image storage and replicate the image to other clusters based on demand, reducing unnecessary uploads while ensuring images are available where needed. "

Explanation of Options:

A. Image Placement Policy with Soft EnforcementThis is the correct answer. The ECA course highlights that anImage Placement Policy with Soft Enforcementis designed to optimize image distribution in multi-cluster environments, especially across geographic sites. With Soft Enforcement, Prism Central uploads the image to a designated cluster (e.g., the closest or most available) and replicates it to other clusters as needed, based on workload requirements or VM deployment demands. This approach minimizes redundant uploads, reduces network congestion, and ensures images are available efficiently across sites. The " soft " aspect allows flexibility—if a target cluster is offline or has insufficient storage, Prism Central can select an alternative cluster, ensuring operational continuity.

Supporting Extract: " Soft Enforcement allows Prism Central to prioritize a primary cluster for image storage but permits fallback to other clusters if the primary is unavailable, optimizing upload efficiency and image availability across multiple sites. "

B. Custom Image Upload RoleThis is incorrect. The ECA course does not define a " Custom Image Upload Role " as a feature in Prism Central for optimizing image uploads. While Prism Central supports role-based access control (RBAC) for managing permissions, including image management, these roles govern who can upload or manage images, not how images are distributed or optimized across clusters. The ECA materials state: " RBAC in Prism Central allows administrators to assign permissions for image management, but it does not influence the placement or optimization of image uploads. " This option is irrelevant to the question’s focus on optimizing image distribution.

C. Bandwidth Throttling PolicyThis is incorrect. While bandwidth throttling can regulate network usage during data transfers (e.g., during replication or migration), it does not directly optimize image uploads for availability or efficiency across multiple clusters. The ECA course mentions bandwidth throttling in the context of data protection and replication: " Bandwidth Throttling Policies can be applied to replication schedules to manage network usage, but they are not used for image placement or upload optimization in Prism Central. " Throttling could even slow down image distribution, counteracting the goal of optimization, especially in a multi-site scenario.

D. Image Placement Policy with Hard EnforcementThis is incorrect. AnImage Placement Policy with Hard Enforcementstrictly mandates that images be uploaded to specific clusters as defined in the policy. If the designated cluster is unavailable (e.g., due to network issues, storage constraints, or downtime), the upload fails, which can disrupt operations in a multi-site environment. The ECA course notes: " Hard Enforcement ensures images are only stored on specified clusters, but this can lead to upload failures if the target cluster is offline or lacks capacity, making it less suitable for geographically distributed environments. " This rigidity makes Hard Enforcement less optimal compared to Soft Enforcement, which provides flexibility and ensures image availability.

Additional Context from ECA:

Image Management Workflow: The ECA course explains that Prism Central’s Image Service centralizes image management for all registered clusters. When an image is uploaded, the Image Placement Policy determines where it is stored and how it is replicated. For geographically dispersed clusters, Soft Enforcement balances efficiency and availability by prioritizing a primary cluster (e.g., based on proximity or storage capacity) while allowing replication to other clusters as needed for VM provisioning or workload deployment.

Extract: " In multi-site deployments, Soft Enforcement optimizes image uploads by reducing redundant data transfers and ensuring images are accessible across clusters without requiring manual intervention. "

Practical Consideration: In a multi-site scenario, network latency and storage availability vary across clusters. Soft Enforcement allows Prism Central to adapt dynamically, ensuring images are uploaded to a viable cluster and replicated efficiently, which aligns with the goal of optimization.

Supporting Reference from Web Results:

The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) reinforces the ECA documentation: " Image Placement Policies in Prism Central streamline image management across clusters. Soft Enforcement is ideal for multi-site environments, as it allows flexible image placement and replication, ensuring efficient uploads and availability. " This confirms that Soft Enforcement is the recommended approach for optimizing image uploads in a multi-cluster, multi-site setup.

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. "

Dead VMs and Zombie VMs are different classifications of inactive VMs in Nutanix, and their deletion timelines depend on Playbook configuration.

Dead VMs→ Consideredinactive after 30 days, then must wait99 more daysbefore deletion.

Total time: 30 + 99 = 129 days.

(Option C is correct).

Zombie VMs→ Consideredinactive after 30 days, then must wait99 more daysbefore deletion.

Total time: 30 + 99 = 129 days.

(Option B is correct).

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.