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.)
Suggested Answer: B, D
Get Premium 2V0-31.23 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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.
24 comments · newest first
HI
Hildegarde
3 days ago
I think A and B are the right choices. Makes sense for AD integration.
CL
Clay
8 days ago
I disagree with B), I thought you could use the embedded load balancer too.
KA
Katie
13 days ago
D) is a must if you're using Workspace ONE Access.
MA
Magnolia
18 days ago
Wait, is C) really a thing? That sounds odd.
DE
Deonna
23 days ago
I think B) is the way to go for clustered setups.
DE
Deeanna
28 days ago
A) is definitely a requirement for on-prem AD login.
CR
Cristen
1 month ago
C) seems unnecessary, why not just use an external load balancer?
AN
Antione
1 month ago
D) is correct, you need Workspace ONE for AD integration.
LU
Ludivina
1 month ago
Wait, can you really use an embedded load balancer? Sounds odd.
MA
Markus
2 months ago
I think B) is the way to go for clustered setups.
TY
Tyisha
2 months ago
A) is definitely a requirement for on-prem AD login.
TE
Tegan
2 months ago
C) seems unnecessary, why not just use an external load balancer?
YU
Yun
2 months ago
D) is correct, you need Workspace ONE for AD integration.
EL
Ellen
2 months ago
Wait, can you really use an embedded load balancer? Sounds odd.
ID
Idella
2 months ago
I think B) is the way to go for clustered setups.
OL
Ollie
3 months ago
A) is definitely a requirement for on-prem AD login.
AN
Anglea
3 months ago
I definitely remember that a standalone Orchestrator appliance is needed for workflow extensibility, but I’m not clear on the other options.
AL
Alishia
3 months ago
I feel like the embedded load balancer option was discussed in class, but I can't recall if it applies to both versions or just one.
PE
Pedro
3 months ago
I think I practiced a question similar to this, and it mentioned that Workspace ONE Access is crucial for AD logins. Could that be the right choice?
VI
Viola
3 months ago
I remember something about needing an external load balancer for clustered deployments, but I'm not sure if that's specific to VMware Aria Automation or SaaS.
PO
Portia
4 months ago
I definitely remember that a standalone Orchestrator appliance is needed for workflow extensibility, but I’m not clear on how that fits into the overall architecture differences.
LE
Lemuel
4 months ago
I feel like the embedded load balancer was mentioned in our study materials, but I can't remember if it was for Aria Automation or the SaaS version.
ST
Stephaine
4 months ago
I think I practiced a question that mentioned Workspace ONE Access for AD logins. It might be related to option D, but I can't recall the details.
MA
Marylin
5 months ago
I remember something about needing an external load balancer for clustered deployments, but I'm not sure if it's specific to Aria Automation or SaaS.