Nutanix documentation for Protection Policies supports protecting entities by category, which is the most scalable and administratively efficient method when many current and future VMs share the same RPO requirement. By assigning the marketing VMs to a category and then associating that category with the policy, the administrator avoids one-by-one maintenance and also ensures new VMs can inherit protection simply by category assignment. ( Nutanix Portal )

This is exactly the kind of pattern Nutanix encourages across Prism Central: use categories for dynamic grouping and policy application. Adding each VM individually works, but it is not the easiest or most maintainable approach for a large VM set. Templates are not the unit used here for attaching data protection to running workloads. A category-based protection model gives consistency, scale, and easier future operations, particularly when teams like Marketing may continuously create or receive new VMs. Since the question asks for the easiest way, the category-based workflow in option A is the cleanest answer and aligns directly with official Nutanix policy design. ( Nutanix Portal )

The requirement is not to keep the mission-critical VMs together or apart from each other; it is to prevent them from running on a specific set of older hosts. In Nutanix Prism Central policy terms, that is a VM-Host Anti-Affinity Policy. Anti-affinity at the VM-host level allows administrators to mark selected hosts as unsuitable targets for selected VMs, which is exactly what the scenario requires. Therefore C is the correct answer.

The distractors all target the wrong relationship. VM-VM affinity and anti-affinity control how VMs are placed relative to other VMs, not whether they can run on particular hosts. VM-Host Affinity would express a positive preference or requirement to run on a chosen host group, but the question is framed negatively: the VMs must never run on the older hosts. Nutanix’s policy model supports this exact exclusion use case through VM-Host Anti-Affinity. In a long refresh delay scenario, this is the safest operational control to keep sensitive workloads off weaker or undesirable hardware without removing those hosts from the cluster immediately. Therefore C is the authentic answer.

For database workloads, Nutanix documentation distinguishes between crash-consistent and application-consistent recovery points. If the Take App-Consistent Recovery Points option is not selected, the recovery point may capture storage in a crash-consistent state only. For transactional databases, that can lead to corruption, incomplete writes, or recovery issues after restore. Nutanix specifically documents that selecting the app-consistent option creates application-consistent recovery points; if you do not select it, the recovery points are crash-consistent. That makes D the most likely root cause. ( portal.nutanix.com , portal.nutanix.com )

The mention that NGT was checked is important because NGT participation is commonly part of quiesced and app-consistent protection workflows. A high RPO can increase data loss, but it does not by itself explain logical corruption inside the restored database. Category choice and roll-up schedule are also not the primary issue. Nutanix best practice for databases is to ensure application-consistent protection is enabled wherever supported. Therefore D is the correct answer.

Nutanix documentation for Erasure Coding is explicit: a cluster must have a minimum of four nodes to enable erasure coding, and for RF2 the minimum remains four nodes. Nutanix further explains that RF3 with erasure coding requires six nodes, which helps distinguish the two thresholds clearly for exam purposes. Since the question asks specifically about Replication Factor 2 and Erasure Coding, the minimum supported node count is 4. ( Nutanix )

This question is testing one of the most common node-count rules in Nutanix storage efficiency. A three-node cluster can provide RF2 storage, but that does not automatically mean erasure coding is available there. Erasure coding introduces its own resiliency and stripe-width requirements, and Nutanix sets the minimum at four nodes for RF2. The values 5 and 6 are distractors meant to confuse RF2 and RF3 rules. Because the official requirement is four nodes for RF2 EC, the correct answer is B. ( 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 documentation for Prism Central backup and restore repeatedly references NCM Self-Service as part of the Prism Central backup and recovery context. Nutanix specifically notes considerations for protecting and restoring NCM Self-Service-related entities when Prism Central is backed up and restored. That makes C the correct answer.

The other options do not fit the documented Prism Central backup scope in the same way. “Objects data” refers to data in the object store itself, not the platform service configuration protected as part of Prism Central backup workflows. LCM is a management service, but Nutanix does not present it as the answer to this specific question. “NUS” is not the documented backup-scope answer here. Since Nutanix explicitly calls out NCM Self-Service in PC backup and restore considerations, C is the authentic choice.