The answer is thick provisioned eager zeroed VMDK. This is correct because the descriptor file shows createType="vmfs" with a single extent referencing a "flat.vmdk" file, which is the standard naming convention for a thick virtual disk on VMFS storage. Unlike thin disks, which use createType="vmfsThin", or RDMs, which use createType="vmfsRaw" and point to a device mapping, this descriptor confirms a fully allocated disk with all blocks zeroed at creation. On the VMware Certified Professional Data Center Virtualization VCP-DCV exam, this type of question tests your ability to read a VMDK descriptor file and distinguish between provisioning types—a common trap is confusing a flat.vmdk with an RDM or thin disk. Remember the memory tip: "flat means fat" to recall that flat.vmdk always indicates a thick eager zeroed disk on VMFS.
VCP-DCV Configure and Manage vSphere Storage Practice Question
This VCP-DCV practice question tests your understanding of configure and manage vsphere storage. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Refer to the exhibit.
Output from vmkfstools command:
vmkfstools -V /vmfs/volumes/datastore1/vm1/vm1.vmdk
Disk descriptor file: /vmfs/volumes/datastore1/vm1/vm1.vmdk
# Disk DescriptorFile
version=1
CID=12345678
parentCID=ffffffff
createType="vmfs"
# Extent description
RW 1048576000 VMFS "vm1-flat.vmdk"
# The Disk Data Base
#DDB
The VM is using a virtual mode RDM? (Based on the descriptor, is this a virtual RDM?)
Refer to the exhibit. What type of virtual disk is represented by this descriptor file?
Refer to the exhibit.
Output from vmkfstools command:
vmkfstools -V /vmfs/volumes/datastore1/vm1/vm1.vmdk
Disk descriptor file: /vmfs/volumes/datastore1/vm1/vm1.vmdk
# Disk DescriptorFile
version=1
CID=12345678
parentCID=ffffffff
createType="vmfs"
# Extent description
RW 1048576000 VMFS "vm1-flat.vmdk"
# The Disk Data Base
#DDB
The VM is using a virtual mode RDM? (Based on the descriptor, is this a virtual RDM?)
A
Thin provisioned VMDK
Why wrong: Incorrect: Thin disks have createType="vmfsThin".
B
Thick provisioned eager zeroed VMDK
Correct: The descriptor shows a flat.vmdk file with 'vmfs' type, typical of a thick disk.
C
Sparse disk with multiple extents
Why wrong: Incorrect: There is only one extent, and it's not sparse.
D
Physical mode RDM
Why wrong: Incorrect: The descriptor does not indicate an RDM (no "Raw" type).
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Thick provisioned eager zeroed VMDK
The descriptor shows createType="vmfs" and a single extent with a "flat.vmdk" file. This is a standard thick virtual disk on VMFS, not an RDM. An RDM would have createType="vmfsRaw" or "vmfsRawDeviceMap" and reference a device. Option A is incorrect because it is not an RDM. Option C is incorrect because thin would show createType="vmfsThin". Option D is incorrect because there is only one extent.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Thin provisioned VMDK
Why it's wrong here
Incorrect: Thin disks have createType="vmfsThin".
✓
Thick provisioned eager zeroed VMDK
Why this is correct
Correct: The descriptor shows a flat.vmdk file with 'vmfs' type, typical of a thick disk.
Related concept
Read the scenario before looking for a memorised answer.
✗
Sparse disk with multiple extents
Why it's wrong here
Incorrect: There is only one extent, and it's not sparse.
✗
Physical mode RDM
Why it's wrong here
Incorrect: The descriptor does not indicate an RDM (no "Raw" type).
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the VCP-DCV exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which VCP-DCV exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Configure and Manage vSphere Storage — This question tests Configure and Manage vSphere Storage — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Thick provisioned eager zeroed VMDK — The descriptor shows createType="vmfs" and a single extent with a "flat.vmdk" file. This is a standard thick virtual disk on VMFS, not an RDM. An RDM would have createType="vmfsRaw" or "vmfsRawDeviceMap" and reference a device. Option A is incorrect because it is not an RDM. Option C is incorrect because thin would show createType="vmfsThin". Option D is incorrect because there is only one extent.
What should I do if I get this VCP-DCV question wrong?
Identify which VCP-DCV exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.