The VCF 9.0 Automation and Orchestration Guide explains how Orchestrator integrates with VCF Automation to provide workflow-driven services such as Active Directory management.

Orchestrator Integration (B):The tenant must be connected to the dedicated Orchestrator instance rather than the embedded one. Documentation notes: “Each tenant can integrate with its own Orchestrator endpoint for workflow execution.”

AD Plugin Configuration (E):The Orchestrator Active Directory plugin must be configured against the development AD only, ensuring that the development team does not impact the production directory.

Publish Workflow (C):The AD user creation workflow must be published to the VCF Automation catalog using the Content Hub. Actions alone are insufficient; workflows are the full automation logic exposed to end users.

Custom Resource Object (F):To enable developers to create and destroy AD accounts, a Custom Resource object must be created in VCF Automation and mapped to the Orchestrator workflows. This provides lifecycle capabilities (create/destroy) in the self-service catalog.

Options A and D are incorrect because publishing only the “action” is not sufficient (workflows are required), and the plugin must not point to production AD. Option G is incorrect because the dedicated Orchestrator has already been deployed, so the embedded Orchestrator is not used.