Nutanix Certified Professional - Multicloud Infrastructure v7.5 (NCP-MCI-v7.5)

✅ Option D (Correct)

Reasoning: The NCC ec_enablement_check explicitly recommends enabling erasure coding on both the SelfServiceContainer (26% savings) and default-container203943 (22% savings). VDI workloads, particularly base images, are excellent candidates for erasure coding due to their static nature, allowing significant space savings without performance impact.

❌ Why the other choices are incorrect:

• Option A is incorrect: Enabling EC on only one container ignores the recommendation and potential space savings on the other identified container.
• Option B is incorrect: VDI workloads, especially boot images, are typically write-once, read-many, making them suitable for erasure coding to optimize storage. Ignoring the recommendation contradicts best practices.
• Option C is incorrect: NCC INFO recommendations with specific savings are generally robust and not intermittent. The best course of action is to act on the valid recommendation, not simply re-run the check.

When a VM's password for CHAP authentication to a Volume Group (VG) is rotated, the corresponding CHAP secret configured on the VG for that initiator must also be updated. While the Protection Policy replicates the updated VG configuration (including the new CHAP secret) to the recovery site, the Recovery Plan orchestrates the failover. Any change impacting the failover process, such as new credentials that might require specific post-recovery actions (e.g., re-configuring the VM's iSCSI initiator, running scripts), necessitates updating the Recovery Plan to ensure the VM successfully re-establishes connectivity to the VG using the new password on the DR site.

✅ Option B (Correct)
Reasoning: The error "Cluster needs at least 5 usable nodes" indicates the cluster is operating with Replication Factor 3 (RF3), which requires a minimum of 5 nodes. To remove a node while maintaining RF3 without disruption, a replacement node must be added first. This ensures the cluster always has 5 or more active nodes, allowing the old node to be safely removed.
❌ Why the other choices are incorrect:

• Option A is incorrect: Changing the cluster Replication Factor (RF) is not a direct setting and would entail changing RF on storage containers. Reducing RF to RF2 (from RF3) lowers data protection, which is typically undesirable for SQL VMs, and isn't the primary solution for maintaining cluster size.
• Option C is incorrect: Changing the storage containers RF to RF2 would allow node removal with fewer nodes, but it sacrifices data resilience. For critical SQL VMs, maintaining RF3 is usually paramount, making this an unsuitable solution to the node count error.
• Option D is incorrect: Shutting down the CVM and using ncli to force removal bypasses critical safety checks. This method does not address the cluster's underlying requirement for 5 usable nodes to maintain RF3 and could lead to data unavailability or a severely degraded cluster state.

When reverting a VM in Prism Central, the recovery point restores the VM's disk and configuration state. However, metadata like categories and ownership are external attributes managed by Prism Central. These attributes are associated with the current VM entity and are not part of the recovery point content; therefore, they remain preserved at their latest state.

✅ Option C (Correct)Reasoning: Allowing a single host IP with a 255.255.255.255 netmask (/32 CIDR) is the most secure and precise method to grant NFS access to a specific external host for a temporary data migration. This adheres to the principle of least privilege, limiting exposure only to the required system and simplifying removal post-migration.❌ Why the other choices are incorrect:Option A is incorrect: Enabling user authentication without an allowlist provides no host-level restriction, which is less secure for a temporary, specific host requirement.Option B is incorrect: Using a container as a general-purpose NFS share is vague and does not address the crucial aspect of controlling specific host access for a temporary need.Option D is incorrect: Allowing an entire subnet grants broader access than necessary for a single external host, violating the principle of least privilege and increasing the security risk.

To achieve replication from a source storage container ('Marketing') to a differently named destination storage container ('Backups'), 'vStore mapping' (also known as storage container mapping) must be configured. This explicitly directs the replicated data to the desired target storage container at the remote site, ensuring proper data placement and organization.

✅ Option C (Correct)

Reasoning: A single Prism Element cluster can only be registered to one Prism Central instance at a time. While a Prism Element cluster can host multiple Prism Central virtual machines (i.e., multiple instances can be deployed as VMs on it), it can only be actively managed by a single Prism Central instance through registration. This is a fundamental architectural constraint.

❌ Why the other choices are incorrect:

• Option A is incorrect: Installing (deploying the VMs for) multiple Prism Central instances on a single Prism Element cluster is technically supported. The constraint is on registration, not deployment of the VMs.
• Option B is incorrect: While it is possible to register and unregister a Prism Element cluster with Prism Central multiple times, this statement does not address the core architectural limitation regarding simultaneously registered instances, which is central to the question's premise of having multiple instances.
• Option D is incorrect: Prism Central instances are deployed from an image (e.g., OVA/QCOW2) or via specific deployment workflows, not typically from the Nutanix Marketplace, which is primarily for applications running on the platform.

To deploy a new VM with Secure Boot enabled for a UEFI boot configuration, the administrator should use a SCSI bus type for the virtual disk. Nutanix AHV strongly recommends VirtIO SCSI for optimal performance and compatibility with modern operating systems and features like UEFI and Secure Boot. The VirtIO ISO provides necessary drivers for VirtIO SCSI controllers, which are essential for a performant and compliant setup.

New Nutanix storage containers are configured with inline compression by default. This method applies compression as data is written, ensuring immediate space savings. There is no delay for inline compression, making the effective delay 0 minutes. Post-process compression is an alternative option, but not the default setting upon creation.

✅ Option D (Correct)
Reasoning: The "Alerts Matching Criteria" trigger in Nutanix Prism Central playbooks is specifically designed to filter alerts based on properties such as impact type, severity, and keywords. This approach satisfies the requirement to trigger remediation for any alert matching a defined performance pattern (e.g., impact type, severity, keyword) while being resilient to changes in specific alert policy names or IDs. It directly addresses the need to avoid unrelated non-performance alerts.

❌ Why the other choices are incorrect:
* Option A is incorrect: An Event trigger responds to specific events, which are more granular than alerts. While events contribute to alerts, triggering directly on events might not align with the 'alert policy' and 'performance pattern' criteria for remediation, which typically respond to aggregated or threshold-breaching conditions defined as alerts.
* Option B is incorrect: A Webhook trigger requires an external system to detect incidents and initiate the playbook. The requirement implies using Prism Central's native capabilities for alert detection and remediation, making an external system an unnecessary layer of complexity and not the most direct solution.
* Option C is incorrect: Configuring an Alert trigger to a single, specific alert policy directly contradicts the problem statement that alert policy names and IDs change. This configuration would break whenever the policy changes, failing to meet the requirement for a robust solution.