Network Client Management →easyMultiple ChoiceObjective-mapped

LPIC-2 Network Client Management Practice Question

Exhibit

Refer to the exhibit.

# cat /etc/exports
/data    192.168.1.0/24(rw,no_root_squash,async)

A client mounts the export with 'mount -t nfs server:/data /mnt/data' and root on the client can write files. Which option in /etc/exports allows root to retain its privileges?

⚠ Common exam trap

Candidates often confuse 'rw' (which enables write access) with the ability to retain root privileges, not realizing that root_squash is a separate, default mechanism that overrides rw for UID 0.

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

✓

no_root_squash

(no_root_squash) is correct because it prevents the NFS server from mapping the client's root user (UID 0) to the anonymous 'nobody' user. By default, NFS exports use root_squash, which maps root to an unprivileged user for security. With no_root_squash, the client's root retains UID 0 on the server, allowing write access to files owned by root on the export.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
root_squash
Why it's wrong here
This would map root to nobody, preventing write to root-owned files.
✓
no_root_squash
Why this is correct
Root squashing is disabled, so root retains UID 0.
✗
rw
Why it's wrong here
Allows read-write, but not root privileges.
✗
async
Why it's wrong here
Affects write performance, not root mapping.

Go deeper

LPIC-2 Network Client Management Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question