- Home
- Server Administration
- LPIC-2 Linux Engineer 202
36.
What file would you edit to ensure that Linux can map usernames to UID values when you
reconfigure Linux to use a Windows domain controller for user authentication?
- A./etc/nsswitch.conf
- B./etc/passwd
- C./etc/pam.d/winbind
- D./etc/winbind/conf
- Answer & Explanation
- Report
Answer : [D]
Explanation :
Explanation :
The Name Service Switch (NSS) is responsible for mapping usernames to user ID (UID) values, and NSS's configuration file is /etc/nsswitch.conf . Thus, you would edit this file (making option A correct) to ensure that usernames and UID values are correctly linked when you change the authentication system. Ordinarily, this mapping appears in /etc/ passwd , but since the question explicitly states that the computer has been reconfigured to use a Windows domain controller, option B is incorrect. The files in options C and D are both fictitious, although the name of the service that authenticates against Windows domain controllers is Winbind. |
37.
Your login server is using PAM and you want to limit users'access to system resources.
Which configuration file will you need to edit?
- A./etc/limits.conf
- B./etc/pam/limits.conf
- C./etc/security/limits.conf
- D./etc/security/pam/limits.conf
- Answer & Explanation
- Report
Answer : [C]
Explanation :
Explanation :
The /etc/security/limits.conf file holds the configuration settings that will allow you to limit users'access, making option C correct. Options A, B, and D do not give the correct path to this file. |
38.
What is the purpose of the session PAM management group?
- A.It sets up the environment for a login session and cleans up when the user logs out.
- B.It performs authentication based on a username and password or perhaps some other criteria, such as a biometric scan.
- C.It validates or denies a login based on non - authentication data, such as an IP address.
- D.It changes the password when the user requests a password change.
- Answer & Explanation
- Report
Answer : [A]
Explanation :
Explanation :
Option A correctly describes the function of the session management group and so is correct. Options B, C, and D describe the functions of the auth , account , and password management groups, respectively, and so are incorrect answers. |
39.
What can be said about how usernames are mapped to user IDs, based on the following
lines from the NSS configuration file?
passwd: compat ldap
shadow: compat ldap
group: compat ldap
passwd: compat ldap
shadow: compat ldap
group: compat ldap
- A.LDAP is called in compatibility mode.
- B.LDAP is used after local files.
- C.The computer uses LDAP accounts only.
- D.Nothing can be concluded from these lines alone.
- Answer & Explanation
- Report
Answer : [B]
Explanation :
Explanation :
The order of entries in the NSS configuration file ( /etc/nsswitch.conf ) determines the order in which username/UID mappings are carried out. Since the compat entry typically refers to local account databases and ldap refers to an LDAP server, the effect is that the local account database will be consulted first, followed by an LDAP server, making option B correct. This configuration does not set a “ compatibility mode ” for LDAP access, contrary to option A. If option C were correct, there would be no compat entries on any of the lines; ldap would be used alone. Because option B is correct, option D cannot be correct. |
40.
A server/computer combination appears in both hosts.allow and hosts.deny . What's the
result of this configuration when TCP Wrappers runs?
- A.TCP Wrappers refuses to run and logs an error in /var/log/messages .
- B.The system's administrator is paged to decide whether to allow access.
- C.hosts.deny takes precedence; the client is denied access to the server.
- D.hosts.allow takes precedence; the client is granted access to the server.
- Answer & Explanation
- Report
Answer : [D]
Explanation :
Explanation :
TCP Wrappers uses this feature to allow you to override broad denials by adding more specific explicit access permissions to hosts.allow , as when setting a default deny policy ( ALL : ALL ) in hosts.deny . |