Free Nutanix NCP-MCI-7.5 Practice Exam with Questions & Answers | Set: 2

Nutanix documentation states that when you perform an LCM inventory, Life Cycle Manager first checks and updates its own framework before presenting other upgrade options. Nutanix’s guidance for framework updates and recommended upgrade order repeatedly references Perform Inventory as the step that ensures the system discovers and updates the LCM framework itself. That is why A is the correct answer when the goal is specifically to guarantee LCM is upgraded to the latest version. ( Nutanix )

The other actions may be valid parts of broader maintenance, but they do not ensure the LCM framework itself is brought to the latest version. Upgrading AHV or AOS addresses platform components, not the LCM service logic. Running NCC is good pre-upgrade hygiene, but it is not the mechanism that causes LCM to update. Nutanix intentionally ties framework currency to the inventory process, so the correct operational answer is to perform an inventory first. ( Nutanix )

Nutanix Flow Network Security provides built-in Quarantine category values, including Strict and Forensic. Nutanix documentation states that Strict blocks all inbound and outbound traffic, while Forensic is specifically intended for situations where you want to quarantine the VM but still allow connectivity for forensic access. The documentation also notes that you can configure the allow behavior for forensic mode, which is exactly what this incident-response scenario requires. Therefore A is the correct answer.

This is a strong example of why built-in categories matter operationally. The organization wants a change that can be applied quickly during an incident and does not require redesigning existing policies. Assigning the VM to the Quarantine: Forensic category accomplishes both goals: it uses an existing system-defined control and preserves investigator access. Strict mode would over-isolate the VM and block the forensic tooling too. Thus the most authentic Nutanix response is A.

Here the uploaded answer key says B, but the current Nutanix documentation for post-restoration considerations says that after restoring Prism Central, administrators should reset the credentials, and it explicitly lists that as a post-restore action. The same Nutanix page also mentions other follow-up tasks such as reconfiguring the proxy server or FQDN if needed, but resetting credentials is directly named as a required post-restoration consideration. Because the question asks what should be done once Prism Central is restored, the most documentation-faithful answer is D. Reset the credentials. ( Nutanix Portal )

The confusion probably comes from related Nutanix guidance that after a restore, some services may continue with self-signed certificates or rotate certificates as part of Microservices Infrastructure behavior. That can make certificate replacement necessary in some environments, but it is not the clearest universal immediate post-restore action documented in the restoration considerations. By contrast, reset the credentials is explicitly listed in the post-restoration guidance. So for an authentic study guide grounded in Nutanix docs rather than only the source key, D is the correct answer. ( Nutanix Portal )

The key clue is the mismatch between the VM being slow under memory overcommit and the guest OS pagefile usage remaining low. If the guest itself were under strong memory pressure, you would expect higher pagefile or swap-file activity inside the OS. Instead, the symptoms suggest memory reclamation is happening outside the guest, which points to hypervisor swapping. In Nutanix AHV terms, that means the platform is reclaiming memory at the virtualization layer, causing performance degradation even though the guest does not show heavy internal paging. Therefore C is the most likely cause.

The distractors are weaker. “CVM swapping” would indicate pressure in the storage/control path VM, not necessarily this guest’s memory experience. Ballooning and swapping are not mutually exclusive, and the question’s evidence does not specifically prove ballooning is disabled. This is a troubleshooting pattern-recognition question: slow VM, full memory use, low guest pagefile use, and overcommit enabled usually indicates the hypervisor is swapping, so C is the best answer.

In Nutanix Elastic VM Storage and shared-storage workflows, the container used across clusters must be created as a Shared storage container. Nutanix documentation for storage container management and container creation in Prism Central explicitly references Creating a Shared Storage Container and Creating a VM with Shared Storage from another HCI Cluster. If the container is not defined as Shared, it will not be eligible for the remote-storage VM placement workflow, so it will not appear as a valid target in the dropdown. ( Nutanix Portal )

The distractors are there to pull attention toward naming and capacity details, but those are not the gating requirement for remote shared-storage presentation. A reservation setting affects capacity planning, not whether the container is exposed as a remote shared-storage option. Hyphens in names and the specific length shown are not the documented reason the container would be absent from this workflow. Nutanix treats shared cross-cluster storage as a specific container type and workflow. Therefore, if the remote container is missing during provisioning, the most likely explanation is that the container type was not configured as Shared. ( Nutanix Portal )

Nutanix documentation on capacity reservation explains that a storage container can reserve a portion of storage so that a minimum amount of capacity remains available for that specific container. When reservations are configured, one container may retain protected usable space while other containers in the same storage pool can run out of usable capacity first, even though the pool still shows free space overall. That exactly matches the scenario in the question, which is why C is the correct answer. ( Nutanix )

This is a subtle storage-administration concept. The question is not saying the pool itself is full; it says all but one container are out of space while the single pool still has free space. That pattern is much more consistent with reservation policy than with hardware failure. Failed nodes or drives would usually surface additional health symptoms and would not neatly explain one container still having preserved capacity while the others are exhausted. Nutanix intentionally allows reservation for predictable capacity control, and that is the feature responsible here. Hence A, B, and D are distractors, while C is correct. ( Nutanix )

Nutanix DR documentation for volume groups distinguishes replication types by RPO range. Nutanix documents Asynchronous Replication as the model for 1 hour or more RPO, while NearSync covers 1 minute to 15 minutes, and synchronous/Metro designs target near-zero or zero-RPO behavior with tighter latency expectations. Since the requirement here is 1 hour and the clusters are in different geographic regions, Asynchronous is the correct fit. That makes D the right answer.

The geography in the question is also a clue. Synchronous and Metro Availability are usually associated with low-latency links and more demanding network requirements, which are not implied by “different geographic regions.” NearSync is too aggressive for a 1-hour target and is documented for much shorter RPO windows. Nutanix’s own replication taxonomy places 1 hour or more squarely in the Asynchronous category, so D is the authentic answer.

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 )

Nutanix documents Logbay as the preferred and supported mechanism for efficient platform log collection. The AHV administration guide states that you can use Logbay only after the CVM is installed on the node or the AHV compute node has been added to the cluster, which directly matches the wording in option A. Nutanix’s web-console guidance also points administrators toward Logbay as the preferred collection method rather than relying only on manual UI collection.

The other options describe tools or behaviors that do not match Nutanix’s documented collection path for this scenario. Panacea is not the standard answer for supported cluster log-bundle collection in the way described. Storage policy reports are not substitutes for host/CVM diagnostic logs, and ADS does not function as an automatic diagnostic bundle exporter for arbitrary contention events. Because the question asks for both the supported approach and a key prerequisite, Logbay with the documented availability condition is the most precise Nutanix answer. Therefore A is correct.

Nutanix Self-Service and NCM documentation explains that approval policies are built around defined conditions and approvers, and those policies are part of the broader Policy Engine capability. Nutanix further documents that the Policy Engine is included in NCM and provides the governance framework for conditions-based approvals before deployment actions proceed. Since the question asks specifically about defining conditions and approvers that must be satisfied before deployment, the correct enabling component is Policy Engine.

Marketplace can host deployable items, but it does not by itself provide the approval-governance mechanism being asked about. Nutanix Central and Power Monitor are unrelated to approval workflows. The wording in the question almost mirrors Nutanix’s own approval-policy description, which is why the intended answer is clear. To enforce conditional approvals before provisioning or deployment actions, administrators use Policy Engine. Therefore A is the authentic answer.