vRealize Automation Request Failure in Default Life Cycle States

BCE.

Reference - https://pubs.vmware.com/vrealize-automation-72/topic/com.vmware.ICbase/PDF/vrealize-automation-72-extensibility.pdf (page 41)

vRealize Automation is a cloud management and automation platform that enables IT organizations to rapidly deploy and manage multi-vendor, multi-cloud infrastructures. It uses vRealize Orchestrator as its automation engine, which provides the ability to create custom workflows to automate IT processes.

When a user submits a request in vRealize Automation, the request goes through several Life Cycle states, which determine the status of the request and what actions need to be taken. If a vRealize Orchestrator workflow associated with a request fails, the request will fail by default in certain Life Cycle states.

The three Life Cycle states where the vRealize Automation request fails by default if the associated vRealize Orchestrator workflow fails are:

1. PRE BuildingMachine: This Life Cycle state occurs when vRealize Automation is creating a virtual machine based on the user's specifications. If the vRealize Orchestrator workflow that is responsible for building the machine fails, the request will fail by default.

2. PRE MachineProvisioned: This Life Cycle state occurs when the virtual machine has been successfully created and is being configured. If the vRealize Orchestrator workflow responsible for provisioning the machine fails, the request will fail by default.

3. PRE MachineActivated: This Life Cycle state occurs when the virtual machine is ready to be used. If the vRealize Orchestrator workflow responsible for activating the machine fails, the request will fail by default.

Therefore, options C, B, and D are the correct answers as they correspond to the states where the request will fail by default if the associated vRealize Orchestrator workflow fails. Options A and E are not correct because they do not correspond to the Life Cycle states where the request will fail by default.