Nutanix Multicloud Infrastructure documentation explains that Recovery Plans and Protection Policies are designed to scale using Categories rather than per-VM assignments. Categories provide metadata that allows grouping of VMs by purpose, business unit, application tiers, boot order, and network requirements. The documentation states that Recovery Plans "consume categories so that VMs matching those categories are automatically included in the DR workflow." Categories also allow automatic updates so that when a VM is added, removed, or changed, the DR plan does not require modification. This method is specifically recommended for environments with numerous workloads and variable application tiers. Scripts, naming conventions, and static ratios do not provide the dynamic grouping and automation that categories provide.

To create a custom Intelligent Operations report and run it across multiple Prism Central instances, administrators must export the report configuration from one Prism Central instance and then import it into the others. This process leverages the .rpt file format, which encapsulates the report's configuration details, including data sources, visualization preferences, and thresholds.
From theNutanix Enterprise Cloud Administration (ECA)course materials:
"Administrators can create custom Intelligent Operations reports in Prism Central and export the configuration as a .rpt file. This exported file can then be imported into other Prism Central instances, ensuring consistency across environments without requiring manual recreation of the report's details." Additionally:
"The export/import feature for reports ensures that custom dashboards and reports can be easily migrated or replicated across multiple Prism Central instances, enabling a standardized approach to monitoring and analytics in a multicloud environment." This clearly indicates that the recommended and supported method for sharing or replicating custom reports across multiple Prism Central instances is by exporting and importing the report configurations in .rpt format.
This approach avoids the need for manual recreation and ensures that the reports maintain their intended configuration and layout across different instances.

The Nutanix ECA course provides guidance on performance monitoring and troubleshooting for VMs, including metrics to analyze when determining whether additional vCPUs are needed. The scenario involves a VM experiencing performance issues, with the cluster performing well overall, suggesting the issue is VM- specific.
Extract from Nutanix Enterprise Cloud Administration (ECA) Course Documents:
Module: Performance Monitoring, Section: VM Performance Metrics"To determine if a VM requires additional vCPUs, analyze VM CPU Usage and VM CPU Ready Time. High CPU Usage indicates the VM is under heavy load, while high CPU Ready Time suggests the VM is waiting for CPU resources, both justifying additional vCPUs." Module: Troubleshooting, Section: VM Performance Issues"When a VM experiences performance issues, VM CPU Usage and VM CPU Ready Time are critical metrics. CPU Usage shows demand, while CPU Ready Time indicates contention or scheduling delays, helping determine if more vCPUs are warranted." Explanation of Options:
A). VM CPU UsageThis is correct. VM CPU Usage measures the percentage of CPU resources the VM is consuming. High CPU Usage (e.g., consistently above 80-90%) indicates that the VM is under heavy load and may benefit from additional vCPUs to handle the workload. The ECA course emphasizes:"VM CPU Usage is the primary metric to assess whether a VM's CPU allocation is sufficient for its workload." B). VM CPU Ready TimeThis is correct. VM CPU Ready Time measures the time a VM is ready to run but waiting for CPU resources from the hypervisor due to contention or oversubscription. High CPU Ready Time (e.g., above 5-10%) suggests that the VM is not getting enough CPU cycles, and adding vCPUs could alleviate the issue. The ECA course notes:"High VM CPU Ready Time indicates CPU contention, often resolved by adding vCPUs or optimizing resource allocation." C). Host Memory Swap Out RateThis is incorrect. Host Memory Swap Out Rate indicates memory pressure on the host, causing memory pages to be swapped to disk. While this can affect VM performance, it is unrelated to CPU performance and does not justify adding vCPUs. The ECA course states:"Host Memory Swap Out Rate is relevant for memory-related issues, not CPU allocation decisions." D). Host CPU UsageThis is incorrect. Host CPU Usage measures the overall CPU utilization of the host, not the specific VM. Since the cluster is performing well overall, high Host CPU Usage is unlikely, and it does not directly indicate whether the VM needs more vCPUs. The ECA course clarifies:"Host CPU Usage is a cluster-wide metric and less relevant for diagnosing VM-specific CPU performance issues." Additional Context from ECA:
Performance Monitoring Tools: In Prism Element or Prism Central, VM CPU Usage and CPU Ready Time can be monitored underVM > Monitoror through dashboards. These metrics provide insight into the VM's CPU demand and contention.
Adding vCPUs: The ECA course advises caution when adding vCPUs, as over-allocation can increase CPU Ready Time due to scheduling overhead. However, if both CPU Usage and Ready Time are high, adding vCPUs is justified.
Supporting Reference from Web Results:
The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) supports:"For VM performance issues, analyze VM CPU Usage and CPU Ready Time to determine if additional vCPUs are needed, as these metrics directly indicate CPU demand and contention."

InNutanix Capacity Planning,Overall Runwayrepresents how long the cluster can support current and new workloads before resources are exhausted.
Even if the runway is below 365 days, the system considers the cluster to be in good shape if new workloads are sustainable (Option B).
Option A is incorrect: Storage runway alone is not the only factor; CPU and memory are equally important.
Option C is incorrect: The presence of recommended resources does not mean the cluster is in good shape.
Option D is incorrect: The target of 1 month affects projections but does not explain why the cluster is in good shape.
References:
Nutanix Prism Central # Capacity Runway and Planning
Nutanix Bible # Workload Placement and Cluster Sizing
Nutanix Support KB # Capacity Planning Best Practices