2V0-31.23 · Question #45
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…
The correct answer is B. To support a clustered deployment, an external load balancer must be configured. D. To enable users to log in using their on-premises Active Directory credentials, Workspace ONE. 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…
Question
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.)
Options
- ATo enable users to log in using their on-premises Active Directory credentials, at least one
- BTo support a clustered deployment, an external load balancer must be configured.
- CTo support a clustered deployment, the embedded load balancer must be configured.
- DTo enable users to log in using their on-premises Active Directory credentials, Workspace ONE
- ETo use Workflow-based extensibility, a standalone VMware Aria Automation Orchestrator
How the community answered
(44 responses)- A5% (2)
- B75% (33)
- C7% (3)
- E14% (6)
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.
Topics
Community Discussion
No community discussion yet for this question.