An administrator is attempting to power on a virtual machine, but the task is hanging at 95%. What three scenarios best explain why this problem is happening? (Choose three.)

vSphere will pause the power-on sequence at 95% if it needs to ask the administrator a question (for example, whether a VM was moved or copied) and will not proceed until an answer is provided via the vSphere Client.

If another task is already running against the same VM or a component it depends on (such as a snapshot operation or a reconfigure task), the power-on task will be queued or blocked, causing it to appear stuck.

When HA admission control is enabled, vSphere enforces a policy that sufficient cluster resources must be reserved to guarantee failover; if powering on the VM would violate this policy, the task will be blocked at nearly complete.

Loss of storage access would cause the power-on task to fail outright with a storage-related error rather than hanging at 95%, because the VM files would be inaccessible from the start.

Resource contention causes scheduling delays or performance degradation but does not produce a task hang at a specific percentage; the task would either queue, fail with an insufficient resources error, or eventually complete.