By default, Nutanix Prism Central retains the last 10 instances of a report if no retention policy is configured.
Option B (10) is correct:
Nutanixstores up to 10 reports, after which older reports areautomatically deleted.
Options A (5), C (15), and D (20) are incorrect:
Whileretention policies can be customized, thedefault setting is 10 reports.
References:
Nutanix Prism Central Guide #Report Generation and Retention Policies
Nutanix KB #How Reports Are Stored and Managed in Prism Central

When configuring application-consistent snapshots in a Nutanix protection domain for applications such as SQL, Oracle, and Exchange, it is critical to group all related VMs in the same consistency group within the protection domain. This ensures that the snapshot captures a consistent state of the entire application stack.
From theNutanix Enterprise Cloud Administration (ECA)course materials:
"A consistency group ensures that snapshots across multiple VMs are taken at the same time, maintaining application consistency for distributed applications. This is especially important for multi-tiered applications like SQL, Oracle, and Exchange, where data integrity depends on coordinated snapshot creation." Additionally:
"For application-consistent snapshots, leverage guest tools or volume shadow copy services (VSS) in Windows to quiesce applications, and configure the consistency group to include all relevant VMs." By creating one consistency group for all VMs comprising an application, the administrator ensures that snapshots represent a consistent state across the application components.

RF3 (Replication Factor 3) clusters require sufficient reserved capacity to tolerate failures without data loss.
* Option C (Set Reserve Capacity for Failure to Auto Detect) is correct:
* Auto Detect dynamically calculates the necessary reserved spacebased on cluster size and RF settings.
* It ensures thatenough storage remains available in case of a node failure.
* Option A (Set Reserve Storage Capacity to 20%) is incorrect:
* The required storage reservationdepends on the number of nodes and RF level, not a fixed percentage.
* Option B (Set Reserve Capacity for Failure to None) is incorrect:
* Without reserved capacity,a node failure could lead to data unavailability.
* Option D (Set Reserve Memory Capacity to 20%) is incorrect:
* This setting applies toRAM, notstorage resiliency.
References:
Nutanix Bible #Understanding Replication Factor (RF) and Failure Planning Nutanix Prism Element Guide #Configuring Reserve Capacity for Cluster Resiliency Nutanix KB #How to Plan Capacity for RF3 Clusters

The Nutanix Life Cycle Manager (LCM) is designed to manage and automate firmware and software upgrades across Nutanix clusters. However, firmware upgrades via LCM are not supported for single-node clusters. This limitation is documented in the ECA course as well as in LCM's official release notes and guides.
From the Nutanix Enterprise Cloud Administration (ECA) course materials:
"LCM does not support performing firmware upgrades on single-node clusters. These clusters require manual upgrades, and LCM will not list any available firmware updates for them, regardless of the firmware revision state." The other options:
* A is incorrect; single-node clusters don't have this limitation specifically for "one-disk" firmware upgrades-it's a complete limitation for all firmware tasks in LCM.
* B is misleading; LCM is supported in general for Nutanix clusters, just not for firmware tasks in single- node clusters.
* D is incorrect because lack of internet connectivity would typically show an error related to download or connectivity issues, not complete absence of firmware updates.