NCP-MCA · Question #83
An administrator has noticed an increasing number of inactive VMS being left powered on within the environment over the course of OS migrations, using Playbooks, which two Actions should the…
The correct answer is A. Assign the VMS to an Inactive:VM Category as an Action. C. Trigger Playbook on Alert with the Inactive VM Alert Policy. The administrator should assign the VMs to an Inactive:VM category as an action and trigger a playbook on alert with the Inactive VM alert policy. By doing this, they can create a custom category to group and identify the inactive VMs and use a custom alert policy to trigger a…
Question
An administrator has noticed an increasing number of inactive VMS being left powered on within the environment over the course of OS migrations, using Playbooks, which two Actions should the administrator use to start documenting which VMS are marked as inactive to take future Automated actions on? (Choose two.)
Options
- AAssign the VMS to an Inactive:VM Category as an Action.
- BTrigger Playbook on Powered Off VM for all applicable VMS.
- CTrigger Playbook on Alert with the Inactive VM Alert Policy.
- DSend an Email with the Source Entity Name Parameter in the body.
How the community answered
(35 responses)- A77% (27)
- B9% (3)
- D14% (5)
Explanation
The administrator should assign the VMs to an Inactive:VM category as an action and trigger a playbook on alert with the Inactive VM alert policy. By doing this, they can create a custom category to group and identify the inactive VMs and use a custom alert policy to trigger a playbook that can perform automated actions on them, such as powering them off, deleting them, or sending notifications. This is based on the general practices in managing VMs in a multicloud environment, as well as the specific features and requirements of Nutanix X-Play and Nutanix
Topics
Community Discussion
No community discussion yet for this question.