vRealize Automation Event Broker: Troubleshooting Workflow Failure

A.

vRealize Automation (vRA) is a cloud automation platform that enables the automation of infrastructure and application provisioning, management, and delivery. vRealize Orchestrator (vRO) is a workflow engine that allows you to automate tasks in a variety of environments, including vRA.

When an event is triggered in vRA, it can be processed by the vRA Event Broker service, which then generates a message that is sent to vRO for processing. If the vRO workflow for the event fails, it means that the workflow did not complete successfully and may have encountered errors during processing.

The expected behavior of the vRA request generating this event depends on the type of event and the workflow that failed. In general, a non-blocking event means that the vRA request is not blocked by the event, and it can continue to run even if the event processing fails.

Therefore, the answer to the question is C: The vRA request will stay In progress. This means that the request will continue to run even though the workflow for the event failed. The failed event processing will not impact the status of the request, and it will continue to run until it completes or encounters an error.

It is important to note that this behavior may vary depending on the specific configuration of the vRA environment and the workflows involved. In some cases, the vRA request may fail if the event processing fails, or it may disappear from the Requests tab if it encounters an error. Therefore, it is important to diagnose the root cause of the vRO workflow failure to determine the impact on the vRA request.