Free LPI 102-500 Actual Exam Questions - Question 15 Discussion

It’s A because it directs where to find system info like hosts, not just LDAP.

Option A, because it specifies system info sources, not just LDAP or service startup.

A/C? While A covers the general purpose well, C is just a subset since LDAP is one of the possible services nsswitch.conf can reference. So it’s more about configuring the lookup order, not just LDAP itself.

Just adding that B and D can be ruled out pretty easily since port configs are nowhere near nsswitch.conf, and service startup is handled elsewhere. C is tempting because LDAP is part of what nsswitch can configure, but it’s too specific—nsswitch.conf controls multiple databases, not just LDAP. So A makes the most sense as it describes the broader function of directing where the system looks for info like user passwords and hostnames.

A/C? I know C talks about LDAP which is related but too narrow since nsswitch.conf covers more than just LDAP. A covers all system info lookups, so it makes more sense overall.

It’s A. The file basically tells the system which sources to check first when it needs info like user accounts or hostname resolution. B is off because port numbers are usually in /etc/services, not nsswitch.conf. C isn’t right since LDAP setup is more complex and handled elsewhere, though nsswitch can include LDAP as a source. D doesn’t make sense because service startup is managed by systemd or init scripts, not by nsswitch.conf. This file is really about lookup order for various system databases.

D imo, B, C, and D don't fit because nsswitch.conf doesn't handle network ports, LDAP config alone, or service startup settings. It’s mainly about where to look up system data like users and hosts.

Probably A. The file definitely controls where the system looks up info like hosts and users, but it also covers other databases like networks and protocols, so “system information” seems broad enough here. B and C are more specific to protocols and LDAP, which nsswitch.conf doesn’t directly handle. D is off since the file’s not about enabling services at boot, but about lookup order for system info. So A fits best overall.

A makes sense since it controls how the system looks up info like hosts, users, groups.

It’s A because it tells the system where to search for user, host, and group info.

A vs C? I agree with going for A since nsswitch.conf sets the lookup sources for system info, including users and hosts. C is more about actual LDAP server setup, not the lookup order itself. B and D don’t fit at all since ports and startup services aren’t handled here. The file is really about telling the system where to check for info, so A makes the most sense.

A/C? While A feels right since nsswitch.conf handles system info lookups, it’s not about LDAP config specifically, so C is off. Definitely not about ports or service startup like B or D.

It’s A because nsswitch.conf defines lookup order for system databases, not service startup.

Option A is the best fit here. nsswitch.conf tells the system where to find info like users and hosts, not about starting network services or defining port numbers. So B, C, and D don’t really match.

A nsswitch.conf configures the order and location for various system database lookups like users, hosts, and groups. It definitely doesn’t control network services startup, so D can be ruled out easily.

A. nsswitch.conf definitely isn’t about network ports or boot services, so B and D are out. It also doesn’t configure LDAP itself, just tells the system where to check for info like users, groups, hosts, etc. So it’s broader than just LDAP but still about system databases, which matches A pretty well.

Maybe A, it decides where to find user and host info, not network ports.

Option A, since it sets lookup sources for user and host info system-wide.

A vs C? I’m pretty sure it’s not C because LDAP is just one possible source, and nsswitch.conf actually tells the system which sources to use for info like users and hosts. So it’s more about where to look rather than configuring LDAP itself. That makes A a better fit here.

Maybe A, it decides where system info like users and hosts come from.