An administrator has been tasked in auditing the company's Configuration Management Database (CMDB) and notices that there are several entries for VMS that were previously decommissioned. Current VM…

Question

Options

• ACreation of Calm Tasks for each of the three steps added to Library and consumed inside of a
• BCreation of Calm Runbooks for each of the three steps added as Post VM Delete Task.
• CCreation of Calm Runbooks for each of the three Steps to the Library and consumed inside of a
• DCreation of Calm Runbooks for each of the three steps &added to the library end consumed
• ECreation of Calm Endpoint that includes all steps added 35 a Post VM Delete Task.

• A
  3% (1)
• B
  6% (2)
• C
  19% (6)
• D
  61% (19)
• E
  10% (3)

Explanation

Calm Runbooks are a way to automate workflows that span across multiple applications, services, or platforms. They can be used to perform actions such as provisioning, scaling, backup, restore, etc. Calm Runbooks can be added to the Library and reused in different Blueprints or Projects. A Post VM Delete Task is a special type of Task that is executed after a VM is deleted from a Blueprint. By creating Calm Runbooks for each of the manual steps required to decommission a VM, and adding them to the Library, the administrator can simplify the VM Decommission Process by consuming them inside of a Post VM Delete Task. This way, the application owners only need to delete the application from the Calm project, and the rest of the steps will be automated by the Runbooks.

No community discussion yet for this question.