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
  75% (41)
• C
  7% (4)
• D
  13% (7)
• E
  5% (3)

Explanation

A and B are correct because on-premises vRealize Automation uniquely enables deep integration with your existing on-premises VMware stack. Specifically, on-prem vRA can leverage your existing VMware Identity Manager (vIDM) deployment for authentication (A), which vRA Cloud cannot use since it relies on VMware Cloud Services for identity. Similarly, on-prem vRA offers tighter, native integration with an on-premises vRealize Operations instance (B) for workload analytics and cost management, which is more constrained in the cloud model.

Why the distractors are wrong:

• C is incorrect because vRA Cloud also supports provisioning to on-premises infrastructure via cloud proxy connectors - it's not exclusive to on-prem.
• D is backwards - on-premises vRA requires license keys; it's actually vRA Cloud that operates on a subscription model without traditional license keys.
• E is incorrect because vRA Cloud can also connect to on-premises vRealize Orchestrator instances through a cloud extensibility proxy, so this is not an exclusive on-prem advantage.

Memory tip: Think "on-prem vRA = trust your existing on-prem tools." The two advantages are about reusing what you already have deployed - your identity provider (vIDM) and your monitoring platform (vROps). If the answer sounds like something the cloud version can also do (like provisioning on-prem workloads via a proxy), it's a trap.

No community discussion yet for this question.