LFCS Question #635: Real Exam Question with Answer & Explanation

Question

How can the risk of UID/GID inconsistencies be avoided across UNIX/Linux systems that are sharing information over protocols other than SMB/CIFS (eg: NFS)?

Options

• ASpecify a common LDAP idmap backend in smb.conf.
• BSpecify a common Kerberos realm in smb.conf.
• CSpecify a common domain name in smb.conf.
• DSpecify a common password server in smb.conf.
• ESpecify a common winbind id range in smb.conf.

Explanation

This question addresses how to achieve UID/GID consistency across UNIX/Linux systems when sharing information via protocols like NFS, which is critical for consistent access control and permissions.

Common mistakes.

• B. Specifying a common Kerberos realm primarily provides centralized authentication and single sign-on, but does not inherently guarantee consistent UID/GID mapping across all systems for file sharing.
• C. A common domain name primarily aids in network naming resolution but does not directly provide centralized UID/GID mapping to prevent inconsistencies.
• D. Specifying a common password server (like NIS) provides centralized user authentication, but LDAP offers a more robust and flexible solution for centralized ID mapping for both users and groups.
• E. Specifying a common Winbind ID range in smb.conf is for Samba's internal ID mapping within a Windows domain context and does not directly solve UID/GID inconsistencies for native UNIX services like NFS.

Concept tested. Centralized UID/GID management for UNIX/Linux

Reference. https://www.samba.org/samba/docs/current/manpages/smb.conf.5.html

No community discussion yet for this question.