A system administrator must mount a datastore to an ESXi host using NFSv4 with the NFS owner set to change/revoke access permissions. Which permission level must be applied to the NFS datastore?

Question

Options

• ARead/write, enable Root
• BRead-only, enable Root
• CRead-only
• DRead/write

• A
  82% (31)
• B
  5% (2)
• C
  11% (4)
• D
  3% (1)

Explanation

Option A is correct because mounting an NFS datastore on ESXi requires Read/Write access so the host can store and modify VM data, and Enable Root (no root squash) is required because ESXi connects to NFS as the root user - without this flag, the NFS server squashes root to an anonymous, unprivileged account, preventing the NFS owner from exercising change/revoke permission control.

Option B fails because Read-only prevents ESXi from writing VM files to the datastore, making it unusable for active workloads despite having Root enabled.

Option C fails on both counts - Read-only blocks write operations, and without Root enabled, the root identity is squashed, eliminating the owner's ability to manage access.

Option D fails because even though Read/Write is correct, omitting Root means the ESXi host's root-level NFS requests get remapped to an unprivileged user, breaking the permission management chain.

Memory tip: Think "RW + Root = Real control" - you need Read/Write to actually use the store, and Root enabled to preserve the owner's authority to revoke access. If Root is squashed, so is the owner's power.

No community discussion yet for this question.