vSphere HA Datastore Heartbeat Configuration
A small business runs a small vSphere environment with a single ESXi host (Host-A) and a VCSA on a separate host. The company is concerned about single points of failure for the ESXi host. They have a budget to purchase a second identical ESXi host (Host-B) and want to ensure that VMs can be restarted automatically if Host-A fails. They also want to be able to perform maintenance on Host-A without VM downtime. They have a shared storage array (iSCSI) that both hosts can access. The administrator decides to create a vSphere cluster with HA and DRS. However, after adding both hosts to the cluster and enabling HA, the administrator notices that the cluster does not have a shared datastore accessible by both hosts that serves as the HA heartbeat. Which action should the administrator take to enable HA?
Quick Answer
The answer is to configure the existing iSCSI datastore as a heartbeat datastore for HA. This is correct because vSphere HA uses datastore heartbeats as a secondary mechanism to detect host failures when the management network is isolated or unreliable; without a shared datastore designated for heartbeat, HA cannot properly distinguish between a host failure and a network partition. On the VCP-DCV exam, this scenario tests your understanding that HA requires either a shared datastore for heartbeat or a fully functional management network—and that existing shared storage, like iSCSI, can be leveraged without additional licensing. A common trap is assuming vSAN or a separate vCenter is needed, but the key is that datastore heartbeat configuration is a simple cluster setting. Memory tip: think of the heartbeat datastore as the “pulse check” for HA—if the network goes silent, the storage still talks.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure the existing iSCSI datastore as a heartbeat datastore for HA
The administrator needs to enable HA in the cluster. The issue is that the cluster lacks a shared datastore that can serve as the HA heartbeat. The existing iSCSI storage is shared between both hosts. In vSphere HA, datastore heartbeats are used in addition to network heartbeats to detect host failures. By configuring the existing iSCSI datastore as a heartbeat datastore, HA can function properly. Option A is incorrect because a second vCenter Server does not provide HA heartbeat functionality and is unnecessary for this issue. Option B is incorrect because local VMFS datastores are not shared, so they cannot be used for HA heartbeats. Option C is incorrect because vSAN would require additional licensing and configuration, and the question already states there is shared iSCSI storage available. Therefore, the correct action is to configure the existing iSCSI datastore as a heartbeat datastore for HA.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Install a second vCenter Server to provide redundancy
Why it's wrong here
vCenter HA is separate; HA cluster can work without multiple vCenters.
- ✗
Create a VMFS datastore on each host's local storage and enable HA
Why it's wrong here
Local datastores are not shared, so HA cannot use them for heartbeat.
- ✗
Deploy a vSAN cluster using local disks on both hosts
Why it's wrong here
Deploying vSAN is incorrect because the scenario explicitly states the company already possesses a shared iSCSI storage array accessible by both hosts. The issue is not a lack of shared storage, but rather the configuration of an existing shared datastore for the HA heartbeat. vSAN would create a new shared storage layer from local disks, which is redundant given the existing array. However, vSAN is a powerful solution for creating shared storage directly from host local disks, making it ideal for scenarios where dedicated shared storage hardware is unavailable or not desired, providing the necessary shared datastore for HA and DRS.
- ✓
Configure the existing iSCSI datastore as a heartbeat datastore for HA
Why this is correct
The iSCSI datastore is shared; HA can use it for heartbeat signaling.
Go deeper
Related to this question
About these practice questions
This VCP-DCV question is part of Courseiva's 498-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on VCP-DCV
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which TWO of the following are characteristics of vSphere High Availability (HA) heartbeat networks? (Choose two.)
medium- ✓ A.Datastore heartbeats can be used as a secondary heartbeat mechanism.
- B.A separate physical network is required for HA heartbeats.
- ✓ C.The management network is the primary heartbeat network.
- D.The default isolation address is the vCenter Server IP address.
- E.Heartbeats are sent over the VM network to avoid interference with management traffic.
Why A: Datastore heartbeats serve as a secondary heartbeat mechanism in vSphere HA. When the primary management network heartbeat fails, the host checks datastore heartbeats to determine whether it is isolated or has suffered a network partition. This prevents unnecessary VM restarts when the management network is temporarily unavailable but the host is still connected to shared storage.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This VCP-DCV practice question is part of Courseiva's free VMware certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the VCP-DCV exam.