LFCS Storage Management Practice Question
An administrator is configuring an NFS server and wants to export /srv/data to a specific client, 192.168.10.25, with read-write access, while ensuring that the client's root user is mapped to the anonymous user for security. Which entry should be placed in /etc/exports?
⚠ Common exam trap
Many candidates confuse root_squash with no_root_squash, or using a wildcard that opens the export to all clients instead of restricting it to the specified host.
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
✓
/srv/data 192.168.10.25(rw,root_squash)
The correct export entry must specify the exact client, grant read-write access, and enable root squashing. The entry /srv/data 192.168.10.25(rw,root_squash) accomplishes all three requirements. root_squash is the default, but explicitly including it ensures the security policy is applied even if defaults change.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
/srv/data 192.168.10.25(rw,no_root_squash)
Why it's wrong here
no_root_squash allows the client's root user to have root privileges on the exported filesystem, which is a significant security risk. The scenario explicitly requires mapping root to the anonymous user, so this option does the opposite. While it grants read-write access, it fails the security requirement.
- ✗
/srv/data *(rw,root_squash)
Why it's wrong here
The asterisk wildcard allows all clients to mount the export, not just the specified 192.168.10.25. This violates the requirement to restrict access to a specific client. While the options rw and root_squash are correct, the overly broad client specification makes this entry insecure and incorrect for the scenario.
- ✗
/srv/data 192.168.10.25(ro,root_squash)
Why it's wrong here
The ro option exports the filesystem as read-only, which contradicts the requirement for read-write access. Although root_squash is correctly applied, the client would not be able to write to /srv/data. This option fails the read-write requirement.
- ✓
/srv/data 192.168.10.25(rw,root_squash)
Why this is correct
This entry grants read-write access to the specified client and enables root_squash, which maps the client's root user to the anonymous user (typically nobody). This is the default behavior in many NFS implementations, but explicitly specifying it ensures security. It correctly restricts access to the single client and applies the required root squashing.
Go deeper
Related to this question
About these practice questions
Courseiva writes every LFCS question from scratch — 406 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 Linux Foundation exam blueprint
This LFCS practice question is part of Courseiva's free Linux Foundation 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 LFCS exam.