The accounting department has been successfully utilizing Erasure Coding for a long time. During the weekend, there was a large increase in data usage. The administrator expected lower space usage on the storage container. What could be the cause of this low space savings?
A. Data Services IP is not configured
B. Erasure coding auto deactivated
C. Prism Central failure in the erasure coding cluster
D. Erasure coding window default settings
Explanation:
The low space savings after the sudden weekend increase in data usage is most likely due to the default Erasure Coding window setting of 7 days for write-cold data. According to Nutanix best practices, erasure coding effectiveness can be reduced on workloads that have many overwrites outside of the erasure coding window.
The erasure coding window determines how long data must remain "cold", meaning unmodified, before it is eligible to be erasure-coded. With a default window of seven days, any data written during the weekend spike would not be processed by erasure coding until it has remained unchanged for that full period.
Since erasure coding is an asynchronous background process, the space savings from the new data would not appear immediately.
This perfectly matches the scenario: the accounting department has been using erasure coding successfully for a long time, but a large influx of new data over a weekend would initially be stored with standard replication overhead until the erasure coding window elapses and the data becomes eligible for encoding.
The administrator's expectation of lower space usage immediately after the data increase is premature because the data must first become write-cold.
Why the Other Options Are Not Correct
Option A (Data Services IP is not configured)
Incorrect because the Data Services IP is used for services such as iSCSI access and Files, not for the core erasure coding functionality within a cluster. Its absence would not prevent erasure coding from operating on the local storage containers.
Option B (Erasure coding auto deactivated)
Incorrect because Nutanix does not automatically deactivate erasure coding based on data usage spikes. Erasure coding remains enabled on the storage container unless an administrator manually disables it or a specific documented issue occurs, such as data integrity concerns on certain AOS versions.
Option C (Prism Central failure in the erasure coding cluster)
Incorrect because erasure coding operates at the cluster level through the Curator service, not through Prism Central. A Prism Central failure would affect management and monitoring capabilities but would not stop the underlying erasure coding processes from running on the cluster.
What is the default compression setting when a new storage container is created in Prism Central?
A. Inline compression with a 0-minute delay
B. Post-process compression with a 60-minute delay
C. Post-process compression with a 0-minute delay
D. Inline compression with a 60-minute delay
Explanation:
When a new storage container is created in Prism Element or Prism Central, inline compression is enabled by default for all license tiers.
The compression delay is set to 0 minutes. This means data is compressed immediately as it is written, using inline compression.
Nutanix documentation explicitly states that when you create a new storage container, inline compression is enabled by default for all license tiers and is set to a delay of 0, compressing data immediately as it is written.
For comparison:
Post-process compression, when manually selected, is recommended with a 60-minute delay.
The default for a brand-new container is always Inline + 0-minute delay.
Why the other options are incorrect
B & C – Post-process compression
Post-process compression is not the default.
D – Inline compression with 60-minute delay
Inline compression is correct, but the default delay is 0 minutes, not 60.
References
Prism Element / Prism Central Web Console Guide – Compression and Creating a Storage Container
Nutanix Compression FAQ (KB-17546)
An administrator needs to give a user group access to resources from multiple clusters. Which action must be performed in Prism Central?
A. Configure Nutanix Projects
B. Enable Advanced Network Controller
C. Enable Micro Services Platform
D. Configure Availability Zone
Explanation:
In Nutanix Prism Central, Projects are the mechanism used to provide multi-cluster resource access to user groups.
Projects allow administrators to group resources such as VMs, networks, storage, and clusters and assign them to specific user groups.
This enables role-based access control (RBAC) across multiple clusters, ensuring that the user group can access and manage resources consistently.
Without configuring a Project, access would remain limited to individual clusters, which is inefficient for multi-cluster environments.
Other options are incorrect:
B. Enable Advanced Network Controller
Refers to networking features, not access control across clusters.
C. Enable Micro Services Platform
Related to Nutanix internal services, not user group resource access.
D. Configure Availability Zone
Used for disaster recovery and failover, not for granting user group access.
📖 Reference:
Nutanix NCP-MCI 7.5 Exam Guide — Domain 2.0: Managing Nutanix Clusters and Resources
Nutanix Documentation: Projects and Role-Based Access Control in Prism Central
An administrator receives intermittent “VM I/O latency” complaints from two application teams that share the same AHV cluster. In Prism Central, multiple performance-related alerts appear across the same 30 minute window, but only some VMs are impacted. The administrator needs to collect the most relevant platform logs for escalation, minimizing noise and ensuring the bundle covers the exact time window when the alert condition occurred. The organization also requires that the log bundle can be attached to a support case without manual repackaging. Which approach best satisfies the requirement?
A. Enable auto-resolve for the alert policy so the alert clears after the condition stops, then collect logs later if the alert returns.
B. Create a new custom alert policy with a stricter threshold so the alert triggers more consistently, then rely on the alert history instead of collecting logs.
C. Export the Alerts list to CSV (up to the export limit), then attach the CSV to the case as the primary diagnostic artifact for performance troubleshooting
D. In the alert details, identify impacted entities and timestamps, collect logs for the relevant time window, and upload the bundle using a case-number upload option
Explanation:
This approach best satisfies all the requirements: targeted log collection, accurate timestamps, minimal unnecessary data, and direct support-case submission.
The administrator should:
Open the relevant performance alerts in Prism Central.
Identify the impacted VMs and the timestamps when the alert conditions occurred.
Collect the relevant platform logs for the affected time window.
Upload the resulting log bundle using the support case number.
This ensures the diagnostic bundle covers the period when the VM I/O latency occurred and can be associated with the support case without manual repackaging.
Why are the other options incorrect?
A
Auto-resolving alerts does not collect the necessary diagnostic logs and may result in losing useful troubleshooting context.
B
Changing alert thresholds does not address the existing incident or provide the required diagnostic evidence.
C
An exported CSV contains alert information, but it does not replace the platform logs needed for performance troubleshooting.
D
Correct. It combines targeted log collection, precise time-window selection, and support-case upload.
Exam Tip
For Nutanix troubleshooting questions, distinguish between alert information and diagnostic logs.
Alert details help identify the affected entities and incident timeline.
Platform logs provide the underlying diagnostic information.
Case-number upload associates the collected bundle with the support case.
Key takeaway:
When a question emphasizes exact timestamps, relevant entities, minimal log noise, and direct case submission, choose D.
An administrator has noticed that a cluster consists of four Full-NVMe nodes. Which expansion path is supported?
A. Two Mixed SSD + NVMe nodes with 60 TiB each
B. One All NVMe node with 96 TiB RAW Capacity
C. Two Mixed NVMe + HDD nodes with 60 TiB each
D. One All SSD node with 96 TiB RAW Capacity
Explanation:
Nutanix cluster architecture and expansion rules dictate that all nodes within a storage pool must share the same storage media classification. Because the existing cluster consists of Full-NVMe nodes, it can only be expanded using compatible All-NVMe nodes.
Option B
Supported because it maintains the All-NVMe storage architecture of the cluster.
Options A, C, and D
These options involve mixing storage media types such as SSD, HDD, or mixed tiers that are incompatible with an existing pure Full-NVMe cluster deployment.
An administrator is trying to move an asynchronous PD workload from one cluster to another by taking advantage of PD-Based DR when an error message is displayed in Prism. Error updating protection domain. Protection domain is already active on source site "cluster name". Please trigger migrate from source site to activate the protection domain. What would cause this error to appear?
A. Must "Promote" the secondary site first before activating
B. Must "disable" first before trying to activate a PD
C. VMs must be migrated from the VM page instead of using DR
D. Trying to "activate" the PD while the primary cluster is reachable
Explanation:
This error occurs because the administrator is attempting to activate a Protection Domain on the target site while the source (primary) cluster is still online and accessible. The Nutanix documentation explicitly describes this exact scenario: when the source cluster is operational and reachable, clicking "Activate" on the destination cluster triggers the error message: "Error updating protection domain. Protection domain is already active on source site 'cluster name'. Please trigger migrate from source site to activate the protection domain."
The system enforces this behavior to prevent a split-brain situation where the same Protection Domain becomes active on two clusters simultaneously. Activation on the target site is only permitted during an unplanned failover (disaster recovery), where the source site is presumed down and unreachable.
For planned migrations where the source is still healthy, the administrator must use the Migrate function from the source site's Prism Element console instead. This safely handles the transition by powering off source VMs, creating a final snapshot, and then activating the Protection Domain on the target.
Why the Other Options Are Not Correct
Option A (Must "Promote" the secondary site first)
Incorrect because there is no "Promote" operation in Nutanix Protection Domain DR workflows. The correct operations are Activate for unplanned failover and Migrate for planned failover.
Option B (Must "disable" first before trying to activate)
Incorrect because deactivating the source Protection Domain is not a prerequisite for activation in a true disaster scenario. The error is specifically caused by the source being reachable and active.
Option C (VMs must be migrated from the VM page instead of using DR)
Incorrect because Nutanix Protection Domain-based DR does not use per-VM migration from the VM page. The entire Protection Domain is managed as a unit through the Data Protection interface.
Key Reference
Nutanix Prism Element Data Protection Guide confirms that the Activate action is intended for unplanned failover when the source site is down. When the source is reachable, the documented procedure is to use the Migrate function from the source site, which performs a controlled transition and marks the source Protection Domain as inactive before activating the target.
An administrator needs to temporarily allow an external host to mount a Nutanix storage container via NFS for a data migration. Which approach is recommended?
A. Use the container as a general-purpose NFS share.
B. Allow a single host IP with 255.255.255.255 netmask
C. Enable user authentication for NFS without allowlist
D. Allow the entire subnet to simplify future migrations
After scaling out Prism Central to improve resiliency, which additional configuration should an administrator complete?
A. Deploy the Witness service in a separate failure domain
B. Configure a Protection Domain to include all Prism Central VMs
C. Enable High Availability Reservations for Prism Element cluster
D. Set up VM-VM anti-affinity rules between Prism Central VMs
An administrator is tasked with configuring asynchronous replication between two Availability Zones (AZs) using a Protection Policy. Which requirement must be met to successfully configure asynchronous replication?
A. Storage container name of the protected entities must be identical on primary and recovery clusters.
B. Primary and recovery clusters must both be registered with a single Prism Central instance.
C. Round trip time (RTT) latency between the primary and recovery clusters must be less than 5 ms.
D. Primary and recovery clusters must be running the same version of Prism Central.
Which service is part of Prism Central backup?
A. NUS
B. Objects data
C. NCM Self-Service
D. LCM
An administrator manages a Nutanix cluster with software data-at-rest encryption enabled using an external KMS. Several VMs are configured with vTPM to support Windows BitLocker encryption. The administrator needs to perform a disaster recovery operation and restore the VMs on a different cluster. During the recovery, the administrator discovers that the encryption key backup file is unavailable. What is the expected outcome for the vTPM-enabled VMs?
A. The VMs will fail to start because BitLocker will not prompt for the recovery key on first boot.
B. The VMs will start successfully with a new vTPM device automatically attached during the restore process.
C. The VMs will fail to start successfully because the external KMS provides the vTPM keys directly to the new cluster.
D. The VMs will fail to start because the vTPM keys cannot be recovered without the backup file.
How many storage pools and storage containers are created during cluster creation?
A. Two pools, two containers
B. Two pools, three containers
C. One pool, three containers
D. One pool, two containers
| Page 3 out of 10 Pages |
| 234 |
| NCP-MCI-7.5 Practice Test Home |
Real-World Scenario Mastery: Our NCP-MCI-7.5 practice exam don't just test definitions. They present you with the same complex, scenario-based problems you'll encounter on the actual exam.
Strategic Weakness Identification: Each practice session reveals exactly where you stand. Discover which domains need more attention, before Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI) 7.5 exam day arrives.
Confidence Through Familiarity: There's no substitute for knowing what to expect. When you've worked through our comprehensive NCP-MCI-7.5 practice exam questions pool covering all topics, the real exam feels like just another practice session.
Copyright © All Rights Reserved