Nutanix documentation confirms that a Prism Element cluster can be registered with only one Prism Central at a time, so option B is false. Nutanix also documents support for deploying multiple Prism Central instances on the same Prism Element cluster, so option A is false as well. The presence of a dedicated Nutanix doc for deploying multiple Prism Central instances on one PE cluster directly disproves option A. ( Nutanix Portal ) That leaves C and D. Nutanix documentation does not position Marketplace as the standard mechanism described in this context for deploying additional Prism Central instances. By contrast, Nutanix clearly documents registration and unregistration workflows, including the fact that clusters can be unregistered when no longer needed and later registered again. Since a cluster can only be attached to one Prism Central at a time, repeating register/unregister operations is a valid administrative action in supported workflows.
Therefore D is the best valid statement among the given options. This question is mostly testing whether you know the difference between deployment support and registration exclusivity. Multiple PC instances may exist on the cluster, but registration to management is still one-at-a-time. ( Nutanix Portal )

Nutanix documentation states that the default erasure coding window for write-cold data is seven days. That means newly written or recently modified data is not immediately converted into erasure-coded stripes. If there was a large increase in data usage over a weekend, the administrator might not yet see the expected space savings because the new data has not aged long enough to fall within the EC processing window. That is why D is the correct answer.
This is a timing question more than a configuration question. The issue is not that EC has failed or deactivated automatically; it is that the data may still be considered too "hot" for the erasure-coding policy to process under the default window. DSIP and Prism Central health are irrelevant to whether EC space savings appear on a storage container. Nutanix separates the eligibility window from the fact that EC is enabled. Therefore, after a sudden growth event, lower-than-expected savings are best explained by the default erasure coding window settings, which is option D.

In Prism Central behavioral learning and VM efficiency views, Nutanix defines an over-provisioned VM as one that is oversized and wasting resources that are not actually needed. If a VM is consistently using less than half of what has been allocated, it is a classic over-provisioning signal: the VM has more CPU and/or memory assigned than its real workload profile requires. ( Nutanix Portal ) The wrong options each represent a different operational pattern. An inactive VM is largely idle. A constrained VM lacks sufficient resources and typically shows signs of pressure, contention, or poor performance. A bully VM consumes disproportionate resources and can negatively affect neighbors. None of those fit the scenario of consistently low utilization relative to allocated sizing. Nutanix includes these VM efficiency categories so administrators can right-size workloads and reclaim capacity before buying more infrastructure. In a resource planning exercise, identifying over-provisioned VMs is especially important because right-sizing them can delay expansion and improve overall efficiency. That is why D is the correct classification. ( Nutanix Portal )

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 documentation for creating a storage container with Replication Factor 1 shows the workflow in the Prism Element web console. The official steps begin with logging on to Prism Element, navigating to storage, and creating the RF1-enabled container there. This makes A the correct answer.
This question is really about administrative scope. RF1 is a specialized storage-container setting that is managed at the cluster level, and Nutanix documents it in Prism Element rather than Marketplace or Self- Service. Prism Central can manage many cluster-wide resources, but the specific documented RF1 container- creation workflow is rooted in Prism Element. For exam prep, when a question asks which interface is required to create an RF1 container, the safe and documentation-aligned answer is Prism Element. Therefore A is the authentic Nutanix answer.