A customer has a requirement to register a resource with an external service during provisioning...

To satisfy the requirement that a registration task must not impact the success of the overall deployment, a Non-blocking event broker subscription must be used. In VCF Automation 9.0, a " Blocking " subscription pauses the provisioning process until the extensibility task completes, allowing the workflow to fail the deployment if the task returns an error. Conversely, a " Non-blocking " subscription operates asynchronously; the platform fires the event and immediately continues with the VM lifecycle regardless of the task ' s outcome. An Action-Based Extensibility (ABX) action is the ideal lightweight serverless function to execute this registration logic, as it can be easily configured to run in response to the event trigger without the overhead of a full orchestrator workflow. By combining these two, the administrator ensures that the external registration is attempted, and any successes or failures are handled purely within the context of that action and the external service, fulfilling the customer ' s logging and failure-tolerance requirements.