An administrator is configuring Self-Service and would like to create fundamental building blocks that help automate various processes within blueprints and runbooks. Where would the administrator create these automation building blocks?

In Calm-based Self-Service, an administrator first builds reusable automation components—called “library tasks”—and then drags them into blueprints or runbooks. These atomic tasks (Bash, PowerShell, Ansible, etc.) are created and stored in the Calm Library, making them centrally maintained and easily reused across multiple automations.

A. VAML – Calm blueprints are written in YAML/JSON, not “VAML,” and YAML is a format, not the location where tasks are created.
B. Projects – Provide multi-tenancy, RBAC and quotas; they do not store or create automation building blocks.
C. Tasks – A task is the building block itself, not the place where you create and manage them; that place is the Library.

1. Nutanix Calm 3.7 User Guide, “Using the Calm Library → Creating a Library Task,” pp. 55-57.

2. Nutanix Prism Central Self-Service Admin Guide v6.5, “Calm Library Components,” Section 4.1.

3. Nutanix University Courseware: NCP-MCA v6.5, Module “Automation & Orchestration,” slide 38 (“Library tasks are reusable building blocks added to blueprints/runbooks”).