An administrator wants to clean up inactive VMs using VM Efficiency in Nutanix. The business requires that VMs must be inactive for 120 days before deletion. A Playbook was created to delete Dead and Zombie VMs with a 99-day wait period after they are marked inactive. How long will have passed before these VMs are deleted? (Choose two.)

The total time before a VM is deleted is the sum of the initial detection period and the Playbook's wait period. In Nutanix VM Efficiency, the term "Dead VM" is commonly used for an "Inactive VM" (a VM powered off for a set time).
1. Detection Period: By default, a VM is flagged as "Inactive" or "Zombie" after 30 days of meeting the respective criteria (powered-off or idle).
2. Playbook Wait: The Playbook is configured with an additional 99-day wait period that begins after the VM is flagged. Therefore, the total time for both VM types is 30 days (default detection) + 99 days (Playbook wait) = 129 days. The 120-day business requirement is context, not the implemented outcome.

A. This is incorrect. The total time is the 30-day default detection period plus the 99-day Playbook wait, which equals 129 days, not 120.
D. This is incorrect. The total time is the 30-day default detection period plus the 99-day Playbook wait, which equals 129 days, not 120.

1. Nutanix Prism Central Guide v2023.3, Intelligent Operations > VM Efficiency Detection:

Zombie VMs: "A VM is identified as a zombie if it is powered on and has not had a vCPU, memory, or I/O usage for a specified number of days (30 days by default)."

Inactive VMs: "A VM is identified as inactive if it has been powered off for a specified number of days (30 days by default)." This confirms the default 30-day detection period for both types.

2. Nutanix University, Nutanix Certified Professional (NCP) - Multicloud Infrastructure 6.5 Study Guide, Chapter 10: Data Protection and Disaster Recovery > X-Play (Playbooks):

This section explains that a Playbook is initiated by a trigger, such as an alert. The "VM is Inactive" or "VM is Zombie" flag generates an alert that serves as the trigger. The actions within the Playbook, including any "Wait" period, execute sequentially after the trigger event. This confirms the additive nature of the timeline: Detection Period + Playbook Wait Period.