Which two architectural differences could the administrator choose when describing VMware Aria Automation?

An administrator has been asked to describe the differences between the architecture for VMware Aria Automation and VMware Aria Automation SaaS.

Which two architectural differences could the administrator choose when describing VMware Aria Automation? (Choose two.)
A . To enable users to log in using their on-premises Active Directory credentials, at least one Workspace ONE Access connector must be deployed.
B . To support a clustered deployment, an external load balancer must be configured.
C . To support a clustered deployment, the embedded load balancer must be configured.
D . To enable users to log in using their on-premises Active Directory credentials, Workspace ONE Access must be deployed.
E . To use Workflow-based extensibility, a standalone VMware Aria Automation Orchestrator appliance must be deployed.

View Answer

Answer: BD

Explanation:

Architectural differences between VMware Aria Automation and its SaaS counterpart: For on-premises deployments like VMware Aria Automation, using an external load balancer for clustered deployments (B) and deploying Workspace ONE Access for Active Directory integration (D) are common requirements. The SaaS version abstracts these complexities.