An administrator has been tasked with automating the optimization of plays with the autopilot feature. What must the administrator be aware of before configuring autopilot?

Question

Options

• AAutopilot never waits for approvals.
• BAutopilot feature only applies to metric-based alerts as triggers.
• CAutopilot only applies to new playbooks.
• DAutopilot will only attempt to apply the playbook a single time

• A
  93% (28)
• C
  3% (1)
• D
  3% (1)

Explanation

Autopilot is a feature of Nutanix Calm that allows the administrator to automate the execution of playbooks based on predefined conditions or triggers. Autopilot can optimize the performance, availability, and cost of applications by applying the appropriate actions in response to events or metrics. Before configuring autopilot, the administrator must be aware of the following limitations: Autopilot never waits for approvals. This means that the administrator must ensure that the playbooks are tested and verified before enabling autopilot. Autopilot will execute the playbooks without any human intervention or confirmation. Autopilot feature only applies to metric-based alerts as triggers. This means that the administrator can only use metrics from the Nutanix Prism Central or the Nutanix Karbon clusters as the conditions for triggering the playbooks. Autopilot does not support other types of triggers such as schedules, webhooks, or manual triggers.

No community discussion yet for this question.