Broadcom-VMware
2V0-622 · Question #140
2V0-622 Question #140: Real Exam Question with Answer & Explanation
The correct answer is A: The NFS server on which the datastore resides is down.. When df -h reports 0 bytes for an NFS datastore, it indicates ESXi cannot communicate with the NFS server and therefore cannot retrieve capacity metadata.
Question
An administrator uses the df -h command and notices that an NFS datastore is reporting a capacity of 0 Bytes. What condition would cause this to occur?
Options
- AThe NFS server on which the datastore resides is down.
- BThe datastore was mounted as Read/Write.
- CThe datastore was mounted as Read-Only.
- DThe datastore was created with NFS version 4.1.
Explanation
When df -h reports 0 bytes for an NFS datastore, it indicates ESXi cannot communicate with the NFS server and therefore cannot retrieve capacity metadata.
Common mistakes.
- B. Mounting an NFS datastore as Read/Write is the standard configuration and has no impact on capacity reporting - ESXi can query filesystem size regardless of write permissions.
- C. A Read-Only NFS mount restricts write access but does not prevent ESXi from querying the server for capacity statistics, so size would still be reported correctly.
- D. NFS version 4.1 is a fully supported protocol in vSphere and does not inherently cause capacity to report as 0 - connectivity loss, not protocol version, is the cause of this symptom.
Concept tested. NFS datastore capacity reporting and server availability
Community Discussion
No community discussion yet for this question.