NCP-MCI-7.5 Exam Dumps - Nutanix NCP-MCI Questions and Answers

The wording “security drift” points to SCMA rather than AIDE. In Nutanix security hardening guidance, SCMA scheduling is the control that determines how often SCMA runs, with schedule options such as hourly, daily, weekly, and monthly. That makes the SCMA schedule the setting that changes the cadence of security drift checking without changing the underlying controls themselves. ( Nutanix Portal )

AIDE is a file-integrity mechanism and has its own role, but the question is specifically asking about how often the platform checks for drift in a broader security-configuration sense. Changing the list of entities inspected or baseline enforcement behavior would alter scope or enforcement semantics, not merely frequency. The most direct administrative answer is to change the schedule for SCMA. From an exam perspective, Nutanix often separates what runs, how it is enforced, and when it runs into different settings. Here the requirement is only about “how often,” so option B is the precise match. ( Nutanix Portal )

Nutanix Volumes documentation explains that external iSCSI clients use the iSCSI Data Services IP address for target discovery and connection. Nutanix specifically documents creating or updating the ISCSI Data Services IP Address on the cluster as part of enabling access to Volumes. If that step is missing, an external initiator can fail to discover or connect to the volume group correctly. Therefore B is the correct answer.

The other options are unrelated to the direct connectivity requirement. Microservices Infrastructure and Prism Central registration are not the necessary cluster-side prerequisites for an external iSCSI connection. LDAP directory configuration is also not the primary dependency being tested here. The key Nutanix platform requirement is that the cluster exposes the Volumes service via the configured Data Services IP. Without that, the initiator connection workflow breaks. So B is the authentic answer.

Nutanix Prism Central documentation for cluster settings profiles includes support for adding both authenticated and unauthenticated NTP servers. In the AOS 7.0 and later generation, the UI and feature set include the fields required for authenticated NTP, such as Key ID and Key Hex. If those fields are not appearing, the most likely explanation is that the managed environment does not meet the required software version for authenticated NTP support in that settings-profile workflow. That is why AOS 7.0 or later is the correct answer. ( Nutanix )

The other answers do not align with the documented dependency. Microservices Infrastructure is unrelated to whether authenticated NTP fields are exposed. There is no requirement that authentication be configured first in Prism Element before it can exist in the settings profile. Changing authentication algorithm type does not explain why the fields are entirely absent to begin with. The version dependency is the decisive factor. Nutanix often exposes advanced configuration fields only when the target cluster capability supports them, so the lack of Key ID and Key Hex strongly indicates that the cluster software level is below the authenticated-NTP requirement. Therefore D is the best answer. ( Nutanix )

Nutanix documentation for Active Directory authentication in Prism Element states that the default LDAP port is 389, while port 636 is used for LDAPS, which provides encrypted LDAP traffic. Because the question explicitly says the administrator wants all traffic encrypted, the correct port is 636. That is the standard LDAPS answer and the one Nutanix documents directly.

The missing exhibit is not actually necessary to answer the question because the encryption requirement itself is enough. Ports 443 and 9440 are associated with web interfaces or management access, not LDAP directory authentication transport. Port 389 is unencrypted LDAP unless other mechanisms are layered on top. Nutanix’s own directory-authentication docs make the intended answer clear: use LDAPS on port 636. Therefore C is the authentic Nutanix answer.

When the requirement is to deploy multiple remote clusters efficiently from a central point, Nutanix’s intended tool is Foundation Central. Nutanix documentation describes Foundation Central as a way to manage several Foundation instances from a single pane of glass, allowing administrators to create clusters of remote nodes. That design matches the scenario perfectly: five newly purchased clusters, remote deployment, and a need for efficiency and centralized control. ( Nutanix Portal )

The other tools are more limited in scope. Foundation for Windows/Mac and a standalone Foundation VM are useful for imaging and cluster creation, but they do not provide the same centralized, multi-cluster orchestration model that Foundation Central provides. Phoenix ISO is a recovery or re-imaging tool and is not the normal answer for greenfield mass deployment. In short, this question is less about “which tool can build a cluster” and more about “which tool is purpose-built for remote, scaled deployment across many clusters.” Nutanix positions Foundation Central exactly for that use case, so B is the best answer. ( Nutanix Portal )

Nutanix documentation for log collection in Prism Central and related Logbay guidance supports collecting logs for a specific time range, which is exactly what this question requires to minimize noise and capture only the relevant 30-minute incident window. Nutanix also documents that when sending logs to Nutanix Support FTP, the administrator can enter a support case number, allowing the bundle to be attached to the case without manual repackaging. That makes D the strongest answer: use the alert details to identify the impacted entities and timestamps, collect the logs for that time window, and upload them using the support-case workflow. ( Nutanix Portal )

The other options do not produce the right diagnostic artifact. Auto-resolve only affects alert state, not log quality. Tightening thresholds may generate more alerts, but it does not replace collecting platform logs. Exporting a CSV of alerts can help summarize incidents, but it is not the primary evidence Nutanix Support needs for performance troubleshooting. Nutanix’s supported model is very clear: identify the incident timing, collect the appropriate logs for that window, and upload the bundle in a support-compatible way. Therefore D is the authentic answer from a Nutanix troubleshooting workflow perspective. ( Nutanix Portal )

Nutanix does support exposing storage containers for hypervisor access patterns, but Nutanix also clearly recommends not using an AOS storage container as a general-purpose NFS or SMB share. For a temporary exception such as a migration host, the safer and more controlled approach is to whitelist only the exact host that needs access. Using a single host IP with a 255.255.255.255 netmask is the most restrictive option listed and follows the principle of least privilege. That reduces risk during the migration window and avoids broad, unnecessary exposure of the container to an entire subnet. ( Nutanix Portal )

This question is really about administration discipline, not just raw connectivity. Opening the whole subnet might be convenient, but it creates more attack surface and more chance of accidental mounting from unauthorized systems. Nutanix documentation steers administrators toward purpose-built file services, such as Nutanix Files, when they need true shared file access. Since this is only for a temporary migration, the best practice is a tightly scoped NFS allowlist entry for one external host. That makes B the strongest operational and security choice. ( Nutanix Portal )

Here the uploaded answer key says C, but official Nutanix documentation supports D. Nutanix documents that the Recycle Bin retains deleted VMs and volume groups for up to 24 hours by default, and space is not immediately reclaimed while those deleted entities are still being retained. Nutanix also provides a specific workflow to clear space used by the Recycle Bin immediately. That behavior matches the question perfectly: the VMs were deleted earlier today, yet space has not come back. The most likely reason is that the deleted VMs are still in the recycle bin. ( portal.nutanix.com , portal.nutanix.com , portal.nutanix.com )

The answer mentioning “Medusa once every 24 hours” is not the correct interpretation for this symptom. Nutanix’s documented retention mechanism is the recycle bin, not a once-daily reclaim cycle as the main reason space stays consumed immediately after deletion. So based on the official docs, D is the authentic answer.

Nutanix security documentation is clear that vTPM data includes crucial encryption keys and that those keys must be protected through the Nutanix-supported mechanisms. Nutanix also states that encryption keys must be backed up, and third-party-style backup approaches do not protect vTPM device data correctly. If the required key backup material is missing during recovery, the restored environment cannot reconstruct the vTPM-backed trust context for those VMs. In practical terms, that means the VMs cannot be started successfully in the expected protected state because the vTPM keys cannot be recovered without the backup file. That makes D the best answer. ( Nutanix Portal )

This is why Nutanix treats vTPM-enabled workloads as a special class in protection and recovery planning. The issue is not that a new blank vTPM can simply be attached during restore, and it is not that the external KMS alone automatically recreates the VM’s vTPM identity. The trust chain depends on the protected key material. Without that backup information, Windows BitLocker and other vTPM-dependent security features cannot be restored to their original usable state. So even though the environment uses an external KMS for software encryption, the Nutanix-documented principle still applies: without the necessary key backup, the vTPM-enabled VMs cannot be recovered successfully, which is exactly what option D states. ( Nutanix Portal )

Nutanix documentation specifically identifies deduplication as providing the greatest benefit for common data sets, and it explicitly calls out full-clone VDI workloads as one of the strongest matches. In a full-clone desktop environment, many virtual desktops contain highly similar operating-system files, application binaries, and repeated data blocks. Capacity deduplication is designed to eliminate those repeated blocks and therefore reduce the total physical storage consumed by the environment. This is exactly why Nutanix recommends deduplication for such use cases.

The other answers are less targeted. Thin provisioning is useful generally but is not the signature optimization for repeated-content VDI storage. Erasure coding is powerful for write-cold data and capacity efficiency, but it is not the primary answer Nutanix recommends for full-clone VDI patterns. “Post-process map reduce” is not the standard storage-efficiency answer expected in this context. For exam purposes, whenever Nutanix asks about full-clone VDI, the important association is with capacity deduplication, because that feature directly exploits the high block similarity across cloned desktops. Therefore B is the correct and most authentic answer.