Drag and Drop Question Your customer plans to use HPE OneView for VMware vCenter Server to deploy ESXi systems. They created a server profile template that they want to use in HPE OneView. Put the…

Question

Exhibit

Answer Area

Explanation

HPE OneView for VMware vCenter Server - ESXi Deployment Ordering

This question tests whether you understand the dependency chain between the integration, authentication, image prep, and deployment phases.

The Correct Order and Why

Step 1: Add vCenter Server to HPE OneView for VMware vCenter Server

This must be first because it establishes the foundational integration between the two platforms. HPE OneView for VMware vCenter Server is a plugin that bridges HPE hardware management with VMware's management layer. Until vCenter is registered with this plugin, neither side can communicate with the other - there is no context in which to perform any subsequent configuration.

Think of it as: you must open a channel before you can send anything through it.

Step 2: Add HPE OneView credentials to the vCenter Server and create OS Deployment Plan

Once the channel exists (Step 1), you need to authenticate across it. Adding HPE OneView credentials to vCenter allows the plugin to query and control HPE OneView resources (like the server profile template already created). The OS Deployment Plan is then created on top of this authenticated connection - it defines how new ESXi nodes will be provisioned (mapping the server profile template to a deployment workflow).

Common mistake: Trying to create the Deployment Plan before credentials are configured. The plan references HPE OneView resources, so the authenticated connection must exist first.

Step 3: Upload HPE-friendly ESXi image

The HPE-customized ESXi ISO (which includes HPE-specific drivers and management agents) is uploaded after the deployment plan exists because the image is a resource the plan will consume during deployment. The plan's structure is defined first; the image is then made available to fulfill it.

Common mistake: Assuming you can use a stock VMware ESXi ISO. HPE requires its own customized image to ensure driver compatibility and integration with iLO/OneView management.

Step 4: Deploy new ESXi systems using vCenter Server interface

This is always last. All prerequisites are now satisfied: the integration is live, credentials are configured, a deployment plan exists, and the image is staged. The administrator can now initiate bare-metal ESXi deployments directly from the vCenter UI, with HPE OneView orchestrating the underlying hardware configuration via the server profile template.

Common mistake: Expecting to deploy from the HPE OneView interface. The question specifically states the vCenter interface is used - this is the point of the integration: the VMware admin stays in their own tooling.

Dependency Chain Summary

vCenter registered → credentials + plan configured → image available → deploy

Each step creates a prerequisite for the next. You cannot skip or reorder without breaking the chain.

No community discussion yet for this question.