An administrator must create a VM with a specific IP address and provision it into a security group before it's powered on. What type of tasks would…

In Calm blueprints the Create life-cycle action is divided into two task phases.

• Pre-create tasks execute on the blueprint orchestrator before the VM object is instantiated, so they are ideal for reserving or assigning a fixed IP address.

• Post-create tasks run immediately after the VM has been instantiated but before the initial power-on. Because the VM now exists in Prism Central, these tasks can add the VM to a network security group (or make any other API call that requires the VM UUID) while still occurring prior to the first boot.

Using both Pre-create and Post-create tasks therefore fulfils the requirement to (1) set a specific IP and (2) place the VM in a security group before it is powered on.

A. Post-delete runs during the Delete action, not during provisioning; cannot affect a VM that is just being created.

B. While-loop is a control structure used inside tasks, not a life-cycle phase; it cannot substitute for actions that occur before VM power-on.

D. VM power-on tasks run after the VM is already booting; Post-delete belongs to the Delete action—neither helps with pre-boot configuration.

1. Nutanix Calm Administration Guide v6.5, “Lifecycle Actions → Create Action,” pp. 61-62: defines Pre-create and Post-create phases and their execution order.

2. Nutanix Prism Central 2023.1 LTS, Calm Concepts Guide, §3.2 “Task Execution Order,” para. 2-3: Post-create tasks execute “after VM instantiation and before first power-on.”

3. Nutanix University – Calm Design Courseware, Module 4 “Blueprint Tasks,” slide 18: “Use Pre-create for IP reservation; use Post-create to attach security policies prior to initial boot.”