An architect is tasked with providing an automated solution for deploying and managing vSphere virtual machines (VMs). The users who deploy the vSphere machines must be able to review the VM's…

Question

Options

• ADeploy vRealize Automation and configure it to display vRealize Operations health badges
• BDeploy vRealize Automation and provide the users Read-only access to vRealize Operations for
• CDeploy vRealize Automation with a Resource Action that allows for pulling health information
• DDeploy vRealize Orchestrator for deployment and management of the vSphere VMs and provide

• A
  77% (27)
• B
  14% (5)
• C
  3% (1)
• D
  6% (2)

Explanation

Option A is correct because vRealize Automation (vRA) natively integrates with vRealize Operations (vROps) to display health badges directly within the vRA interface - users see VM health status without ever needing access to vROps itself, which perfectly satisfies least privilege.

Why the distractors fail:

• B violates least privilege by granting users direct Read-only access to vROps as a separate system, exposing far more data than just their VMs' health.
• C is overly complex - building a custom Resource Action to pull health data is unnecessary engineering when native health badge integration already exists out of the box.
• D misidentifies the right tool; vRealize Orchestrator (vRO) is a workflow/automation engine, not a self-service deployment portal. vRA is the correct platform for user-facing VM deployment with built-in health visibility.

Memory tip: Think "badges = built-in, zero extra access." Health badges let vRA surface vROps data inside the same portal users already use - no second login, no extra permissions, least privilege preserved.

No community discussion yet for this question.