In preparation for a vRealize Automation distributed deployment, the administrator clones a Windows template to create the required IaaS servers. During the installation, the vRealize Automation…

Question

Options

• ALeverage existing VMware Identity Manager for authentication
• BIntegrate with on-premises vRealize Operations
• CSupport for provisioning workloads to on-premises infrastructure
• DLicense key is not required
• ESupport for on-premises vRealize Orchestrator instance(s)

• A
  82% (23)
• C
  11% (3)
• D
  4% (1)
• E
  4% (1)

Explanation

A and B are correct because vRealize Automation on-premises can natively integrate with an existing on-premises VMware Identity Manager (vIDM) for SSO/authentication (A), and directly connect to an on-premises vRealize Operations Manager instance for cost and performance data (B). These integrations rely on local infrastructure that vRA Cloud cannot directly control or replace.

Why the distractors are wrong:

• C is wrong because vRA Cloud also supports provisioning to on-premises infrastructure via cloud proxy appliances - it's not exclusive to the on-premises product.
• D is wrong and actually backwards: on-premises vRA does require a license key; it's vRA Cloud (subscription model) that avoids traditional license keys.
• E is wrong because vRA Cloud also supports connecting to on-premises vRealize Orchestrator instances through the Cloud Extensibility Proxy - again, not an exclusive advantage.

Memory tip: Think of the on-premises advantages as "what already lives in your datacenter" - if you have existing vIDM and vROps servers on-premises, only the on-premises vRA edition plugs into them natively. When you see "cloud also does it," eliminate the choice.

No community discussion yet for this question.