Differences Between Blocking and Non-Blocking Events
Question
What are two differences between blocking and non-blocking events? (Choose two.)
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.AB.
http://pubs.vmware.com/vrealize-automation-72/topic/com.vmware.ICbase/PDF/vrealize_automation_extensibility_migration.pdfBlocking and non-blocking events are two different ways to handle events in vRealize Orchestrator workflows.
- Blocking Events:
Blocking events are synchronous in nature, which means that the event execution blocks the rest of the code until it has completed. In other words, when an event is triggered, the code waits until the event execution is complete before proceeding to the next step.
Here are the differences between blocking and non-blocking events:
A. The return values from the vRealize Orchestrator workflow will be processed in blocking events and NOT in non-blocking events.
This is because the execution of a blocking event is not complete until the event handler has finished executing. Once the event handler has finished executing, the workflow continues with the next step, processing the return values.
B. vRealize Orchestrator workflows run in sequence, per request in blocking events and parallel in non-blocking events.
This means that in a blocking event, the workflow will run sequentially, processing one request at a time. On the other hand, in a non-blocking event, the workflow will run in parallel, processing multiple requests at the same time.
- Non-Blocking Events:
Non-blocking events are asynchronous in nature, which means that the event execution does not block the rest of the code. In other words, when an event is triggered, the code continues to execute while the event handler executes in the background.
C. If vRealize Orchestrator workflow fails, both blocking and non-blocking events will fail.
This is because the failure of a workflow is an exceptional case that needs to be handled in both blocking and non-blocking events. If a workflow fails, it should stop processing requests and inform the user of the error.
D. If vRealize Orchestrator workflow fails, blocking events will continue and non-blocking events will fail.
This is not true. If a workflow fails in a blocking event, the workflow will stop processing requests and inform the user of the error. Similarly, if a workflow fails in a non-blocking event, the workflow will stop processing requests and inform the user of the error.
