PK0-005 Practice Question: Basics of IT Infrastructure and IT Project Management
A project manager is leading an initiative to virtualize 40 aging physical servers onto a new hypervisor cluster. The project sponsor asks how the team will ensure that a single physical host failure does not take down the virtual machines running on it. Which hypervisor feature should the project manager confirm is configured?
⚠ Common exam trap
Candidates often confuse DRS, which rebalances running workloads for performance, with HA, which actually restarts VMs after a host failure.
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
✓
High availability (HA)
The requirement is that a host failure must not take down its VMs, which is precisely what hypervisor high availability provides by restarting affected VMs on remaining cluster members. DRS, thin provisioning, and VLAN tagging improve balance, storage efficiency, or network segmentation respectively, but none of them recovers workloads after a physical host is lost, so they leave the single point of failure in place.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Distributed resource scheduler (DRS)
Why it's wrong here
DRS balances CPU and memory load by migrating running VMs between hosts, improving performance but not guaranteeing recovery after a host crash. It is an optimization capability, not a failover mechanism, so configuring it alone leaves the single-point-of-failure risk the sponsor raised unanswered. DRS may also depend on HA being enabled first, which the project manager should verify.
- ✓
High availability (HA)
Why this is correct
HA continuously monitors host health and restarts affected VMs on surviving cluster nodes when a host fails, directly meeting the sponsor's requirement. It relies on shared storage and cluster quorum so the VM's disk state remains reachable from the new host, which is why the project must also validate the storage layer and heartbeat network before declaring the requirement satisfied.
- ✗
Thin provisioning
Why it's wrong here
Thin provisioning allocates storage on demand rather than reserving the full virtual disk, which saves capacity but has no relationship to host failure recovery. A VM on a failed host is still unavailable regardless of how its storage was provisioned. This option addresses storage efficiency, not the availability requirement the sponsor described.
- ✗
Virtual switch VLAN tagging
Why it's wrong here
VLAN tagging on a virtual switch segments network traffic for isolation and security, but it does not detect or recover from a physical host outage. Tagging remains relevant to the design, yet it cannot restart a VM that was running on a failed server. The sponsor's question concerns failover, so network segmentation does not satisfy the requirement.
Visual reference
About these practice questions
Courseiva writes every PK0-005 question from scratch — 954 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This PK0-005 practice question is part of Courseiva's free CompTIA 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 PK0-005 exam.