Nutanix Updated NCP-MCI-7.5 Exam Questions and Answers by winter

Nutanix documentation for enabling Marketplace in Prism Central explicitly states that a unique data services IP address (DSIP) must be configured on the Prism Element cluster that hosts Prism Central. This is a hard prerequisite for Marketplace enablement and application deployment workflows. In exam terms, the presence of DSIP is not optional convenience; it is a setup requirement Nutanix calls out directly before Marketplace can be used. ( Nutanix )

The other answers are not Marketplace prerequisites in the same direct sense. SMTP is useful for email notifications, LDAP for external authentication, and LACP for network design, but none of those is the documented enabling requirement for Marketplace. Nutanix separates platform application management prerequisites from general infrastructure best practices, and DSIP falls into the former category. So when the exam asks what must already be in place on the Prism Element cluster before enabling Marketplace, the correct answer is A: Data services IP must be configured. ( Nutanix )

The question is asking for the best balance of capacity efficiency, fault tolerance, and cost control. Nutanix documentation explains that erasure coding is the storage-efficiency mechanism that increases usable capacity by using parity instead of full-copy replication overhead, making it a strong fit when data is relatively cold or infrequently modified. Nutanix also documents that erasure coding requires a minimum of six nodes when using replication factor 3, which corresponds to Fault Tolerance 2 designs. That makes Erasure Coding with six nodes the correct answer.

Deduplication is valuable for certain duplicate-heavy data sets such as VDI or repeated blocks, but the question emphasizes business-critical cold data and a tight budget. In that context, erasure coding provides the more directly documented capacity-efficiency benefit. The five-node options are eliminated by Nutanix’s minimum-node requirement for RF3 erasure coding. Since FT2 implies the higher fault-tolerance design and Nutanix requires six nodes for EC with RF3, A is the correct answer.

Incrementing rx_crc_errors usually point to a Layer 1 or physical-path problem, not a CPU or memory issue. CRC errors mean frames are arriving corrupted, and the most common reasons are a faulty cable, damaged transceiver, bad port, or another physical medium issue between the AHV host and the switch. Because the CRC counter is specifically increasing while other counters like missed, FIFO, and general rx errors remain low, this strongly suggests corruption during transmission rather than host overload. That makes B the correct answer.

A duplex mismatch can cause broader link-performance problems, but the pattern of steadily rising CRC errors is much more classically tied to bad physical media. MTU issues usually show fragmentation or packet-handling problems, not CRC corruption itself. CPU saturation does not create on-the-wire checksum corruption. In Nutanix troubleshooting, when CRC counters rise repeatedly, the correct operational response is to inspect and swap the cable or optics, verify switch-port health, and test the NIC path physically. So B is the strongest technical match.

Nutanix documentation for enabling load balancing of vDisks in a volume group states that vDisk load balancing is enabled by default for volume groups attached to VMs by using a Data Services IP address. That is the exact behavior this question asks about: how to make load balancing happen by default rather than managing it manually each time. Therefore D is the correct answer. ( portal.nutanix.com , portal.nutanix.com )

The other answers may relate to supported limits or guest best practices, but they do not describe the default-enablement mechanism. Nutanix intentionally ties this behavior to the DSIP-based attachment model, which simplifies pathing and discovery while automatically enabling the balancing behavior. So for a study guide aligned to Nutanix docs, D is the authentic answer.