An operator has been tasked with powering on a single virtual machine that has been onboarded, along with a number of additional virtual machines, into a single deployment within vRealize…

Oszkar V.Jun 27, 2026

A and E are correct because vRealize Automation is the system of record for onboarded deployments, and Power On is exposed as a Day 2 action there, either at the deployment level (A) or scoped to the individual VM resource within that deployment (E). Log Insight is a log analytics tool with no power management actions, and while vRealize Operations can trigger some actions, it is not the authoritative control plane for VMs onboarded through vRA and would not surface the Day 2 action catalog you need here.

Henrike J.Jun 26, 2026

A and E are correct. In vRealize Automation, Day 2 actions like Power On can be triggered at either the deployment level (option A) or at the individual resource/VM level within that deployment (option E), and both paths exist natively in the vRA interface for onboarded machines. The other options reference vRealize Log Insight, which has no power management capability, and vRealize Operations, which is a monitoring tool and does not expose Day 2 lifecycle actions for vRA-managed workloads.

Mateus R.Jun 20, 2026

Which tool actually owns the deployment, vRA or vROps?

Carlos M.Jun 26, 2026

A and E are correct. In vRA, Day 2 actions like Power On can be run at either the deployment level (which lets you pick which resource to act on) or directly on the specific VM resource within that deployment, so both paths get you there without leaving the vRA console.

Hiroshi T.Jun 1, 2026

I kept second-guessing myself on D because vRealize Operations does surface VM power actions through its integration layer, but the exam blueprint is explicit that Day 2 actions on onboarded resources are managed through vRealize Automation, not vROps. Once I re-read the vRA 8.x documentation on onboarding blueprints and deployment-level Day 2 actions, it clicked that A and E are correct because you can target either the deployment as a whole or the individual VM resource within vRA to invoke Power On as a Day 2 action, and nothing in the other tools qualifies under the official onboarding workflow.

Ola B.Jun 26, 2026

The tricky part here is that A says "deployment" and E says "virtual machine," and both are valid paths in vRA because you can trigger the Power On Day 2 action at either the deployment level or the individual resource level within that deployment. D is the classic trap since vRealize Operations does let you power on VMs in some configurations, but the machine was onboarded into vRA, so that is where you manage it.

Prof. SaraJun 16, 2026

I initially flagged D as a lock because vRealize Operations does surface power state controls and I conflated monitoring-layer actions with actual Day 2 execution authority, but once I remembered that Day 2 actions live in vRA and can be scoped to either the whole deployment or a single resource within it, A and E clicked immediately as the only two that put you in the right tool with the right action type.

Imani T.Jun 26, 2026

B has to be in the mix because vRealize Log Insight gives you direct visibility into the VM's operational state and the Power On action is right there once you locate the resource, no need to go hunting through a whole deployment just to touch one machine. I've seen this workflow come up in lab practice and it makes sense operationally when you're scoped to a single VM rather than acting on the entire deployment umbrella.

Grigory K.Jun 6, 2026

D and E. D works because vROps lets you power on individual VMs directly.