LPIC-2 Network Client Management Practice Test 1 — 15 Questions

Question 1

A system administrator needs to configure a Linux client to use a specific DNS server for a particular domain. Which file should be modified to achieve this?

Accepted Answer

Edit /etc/resolv.conf. The /etc/resolv.conf file is the primary configuration file for DNS resolution on Linux systems. It allows specifying DNS servers (nameserver entries) and search domains, and can be configured to use a specific DNS server for a particular domain by adding a 'domain' or 'search' directive along with the appropriate nameserver. This file is read by the resolver library (glibc) during DNS lookups.

Answer

Edit /etc/hosts

Answer

Edit /etc/networks

Answer

Edit /etc/nsswitch.conf

Question 2

A Linux client is unable to resolve hostnames for external domains but can ping internal hosts by IP. The /etc/resolv.conf file is correctly configured with a valid DNS server. What is the most likely cause?

Accepted Answer

The search domain in /etc/resolv.conf is incorrect, causing the resolver to append an inappropriate domain to queries.. When a search domain is incorrectly configured in /etc/resolv.conf, the resolver appends that domain to single-label hostnames before querying the DNS server. For external fully qualified domain names (FQDNs), this can cause the resolver to send queries like 'externaldomain.com.incorrect.domain' instead of the intended domain, leading to resolution failures. Since internal IPs are reachable (bypassing DNS) and the DNS server itself is valid, the issue is most likely the resolver's domain search behavior.

Answer

The /etc/hosts file contains an entry that overrides the DNS resolution for external domains.

Answer

The nmblookup service is not running.

Answer

The /etc/nsswitch.conf file is missing the 'dns' service in the 'hosts' line.

Question 3

An administrator needs to configure a Linux client to automatically obtain an IP address from a DHCP server but also ensure that the client uses a specific static DNS server (8.8.8.8) regardless of the DHCP-provided DNS. Which configuration should be applied?

Accepted Answer

Add 'supersede domain-name-servers 8.8.8.8;' to /etc/dhcp/dhclient.conf. The `supersede` directive in `/etc/dhcp/dhclient.conf` forces the DHCP client to replace any DNS server addresses received from the DHCP server with the specified value (8.8.8.8). This ensures the client uses the static DNS server regardless of what the DHCP server offers, while still obtaining its IP address dynamically.

Answer

Add 'append domain-name-servers 8.8.8.8;' to /etc/dhcp/dhclient.conf

Answer

Edit /etc/sysconfig/network-scripts/ifcfg-eth0 and set PEERDNS=no and DNS1=8.8.8.8

Answer

Add 'prepend domain-name-servers 8.8.8.8;' to /etc/dhcp/dhclient.conf

Question 4

A Linux client is experiencing slow name resolution. The /etc/nsswitch.conf file has the line 'hosts: files dns'. The /etc/hosts file contains many entries. What is the most effective way to improve resolution speed?

Accepted Answer

Change the nsswitch.conf line to 'hosts: dns files'. The current order 'hosts: files dns' causes the resolver to check the entire /etc/hosts file first for every query, which is slow when the file contains many entries. Reversing the order to 'hosts: dns files' makes the resolver query DNS first, which is typically faster for most lookups, and only falls back to the local file if DNS fails. This directly addresses the bottleneck without requiring additional services or data removal.

Answer

Increase the DNS timeout in /etc/resolv.conf

Answer

Install and configure nscd (Name Service Cache Daemon)

Answer

Remove all entries from /etc/hosts except localhost

Question 5

Which file is used by the NetworkManager daemon to store connection profiles on a Linux system?

Accepted Answer

/etc/NetworkManager/system-connections/. NetworkManager stores per-connection profiles in the `/etc/NetworkManager/system-connections/` directory. Each profile is a keyfile (`.nmconnection` file) containing connection parameters such as SSID, security settings, and IP configuration. When NetworkManager starts or a connection is modified, it reads and writes these files to persist network configurations across reboots.

Answer

/etc/sysconfig/network-scripts/

Answer

/etc/netctl/

Answer

/etc/systemd/network/

Question 6

A Linux client is configured with two network interfaces: eth0 (connected to the internet) and eth1 (connected to a private LAN). The default route is set to eth0. The client can access the internet but cannot access hosts on the private LAN. What is the most likely cause?

Accepted Answer

There is no route to the private subnet via eth1.. Without a route to the private subnet via eth1, the client has no way to forward packets destined for the private LAN out of eth1. The default route via eth0 only handles traffic for destinations not explicitly matched by other routes; if the private subnet is not in the routing table, packets to that subnet will be sent to the default gateway (internet) and fail. The `ip route` command would show the missing entry, and adding a static route (e.g., `ip route add 192.168.1.0/24 dev eth1`) resolves the issue.

Answer

A firewall on the client is blocking ICMP packets on eth1.

Answer

The eth1 interface is not configured with an IP address.

Answer

The eth1 interface is not receiving a DHCP lease.

Question 7

An administrator wants to ensure that a Linux client sends all DNS queries to a specific DNS server without relying on DHCP-provided DNS servers. Which configuration files should be modified?

Accepted Answer

Edit /etc/dhcp/dhclient.conf to add 'supersede domain-name-servers <desired IP>;'. The dhclient.conf file allows an administrator to override DHCP-provided DNS servers using the 'supersede' directive. This forces the DHCP client to ignore the DNS servers received from the DHCP server and instead use the manually specified DNS server when writing /etc/resolv.conf. This is a standard method for controlling DNS resolution on systems using dhclient.

Answer

Configure NetworkManager to ignore DNS from DHCP and set the DNS manually in the connection profile

Answer

Edit /etc/sysconfig/network-scripts/ifcfg-eth0 and set PEERDNS=no and DNS1=<desired IP>

Answer

Edit /etc/resolv.conf and set the nameserver to the desired IP

Question 8

Which TWO commands can be used to display the current DNS resolver configuration on a Linux system? (Select TWO.)

Accepted Answer

nmcli dev show. The `nmcli dev show` command displays network device details managed by NetworkManager, including DNS configuration. The `resolvectl status` command shows the current DNS resolver state for systemd-resolved. These two commands provide the actual current resolver configuration. The `cat /etc/resolv.conf` file may be manually edited or dynamically generated and does not necessarily reflect the current resolver state on systems using systemd-resolved or NetworkManager.

Answer

dig localhost

Answer

nslookup

Answer

cat /etc/resolv.conf

Question 9

Which THREE conditions can cause a Linux DHCP client to fail to obtain an IP address? (Select THREE.)

Accepted Answer

A firewall on the client is blocking UDP port 67 (DHCP server).. A client-side firewall blocking UDP port 67 prevents the DHCP client from receiving DHCPOFFER and DHCPACK messages from the server. DHCP uses UDP ports 67 (server) and 68 (client); blocking port 67 on the client disrupts inbound server responses, causing the client to fail to obtain an IP address.

Answer

The DHCP server is configured with a different subnet than the client's broadcast domain.

Answer

The client interface is configured with a static IP address.

Question 10

Which TWO configuration files are commonly used to specify DNS resolver settings on a Linux system? (Select TWO.)

Accepted Answer

/etc/systemd/resolved.conf. /etc/systemd/resolved.conf is the configuration file for systemd-resolved, a service that manages DNS resolution on modern Linux systems. Option C is correct because /etc/resolv.conf is the traditional configuration file for specifying DNS resolver settings, including nameserver addresses and search domains, and is still widely used.

Answer

/etc/nsswitch.conf

Answer

/etc/dhcp/dhclient.conf

Answer

/etc/hosts

Question 11

Refer to the exhibit. The output shows a DHCP exchange between a client (MAC 00:1a:2b:3c:4d:5e) and a server (192.168.1.1). The client is not obtaining an IP address. What is the most likely reason?

Accepted Answer

The client's /etc/dhcp/dhclient.conf contains a 'reject' statement that rejects offers from this server.. The DHCP client can be configured with a 'reject' statement in /etc/dhcp/dhclient.conf to ignore offers from specific servers. In this scenario, the client sends a DHCPDISCOVER, receives a DHCPOFFER from 192.168.1.1, but then does not proceed to DHCPREQUEST, indicating the offer was rejected locally. This matches the behavior of a reject rule, which causes the client to discard the offer without further communication.

Answer

The DHCP server did not receive the client's request.

Answer

The DHCP server is not reachable from the client.

Answer

The client's MAC address is not authorized on the DHCP server.

Question 12

Refer to the exhibit. A user on the client tries to ping 'server1' and gets an unknown host error. What is the most likely cause?

Accepted Answer

The DNS server has no record for 'server1.example.com'.. The error 'unknown host' indicates that the client's DNS resolution failed for the hostname 'server1'. Since the client likely uses a fully qualified domain name (FQDN) lookup or appends a search domain, the most common cause is that the DNS server does not have an A or AAAA record for 'server1.example.com'. Without a matching record, the resolver returns NXDOMAIN, leading to the 'unknown host' error.

Answer

The search domain is missing.

Answer

The DNS server IP is incorrect.

Answer

Only one nameserver is specified, causing a timeout.

Question 13

A company has a Linux client running Ubuntu 20.04 that is used by multiple developers. The client has two network interfaces: eth0 (connected to the corporate network with DHCP) and eth1 (connected to a test lab with static IP 192.168.100.10/24). The client needs to access both the internet (via eth0) and the lab network (192.168.100.0/24). The default gateway is 10.0.0.1 on eth0. The lab network has a server at 192.168.100.50 that provides DHCP for the lab devices, but the client's eth1 is statically configured. Recently, the client cannot reach the lab server at 192.168.100.50. The administrator checks the routing table and sees:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.0.0.1        0.0.0.0         UG    100    0        0 eth0
10.0.0.0        0.0.0.0         255.255.255.0   U     100    0        0 eth0
192.168.100.0   0.0.0.0         255.255.255.0   U     100    0        0 eth1

The administrator can ping 192.168.100.50 from the client. However, the lab server cannot ping the client. What is the most likely cause?

Accepted Answer

The client's firewall is blocking incoming ICMP echo requests.. The client can ping the lab server (192.168.100.50), proving that outbound traffic from the client to the lab network works correctly. However, the lab server cannot ping the client, which indicates that either the return traffic is blocked or the client does not have a route back to the server. Since the client's routing table shows a direct route to 192.168.100.0/24 via eth1, the issue is not a missing route; instead, the most likely cause is that the client's firewall (e.g., iptables or ufw) is blocking incoming ICMP Echo Requests (ping) on eth1, while allowing outbound traffic.

Answer

The lab server's default gateway is misconfigured.

Answer

The client has no route to the lab subnet.

Answer

The client's default gateway is misconfigured.

Question 14

A system administrator notices that a Linux client is unable to resolve hostnames after connecting to a new network. The client uses DHCP and the /etc/resolv.conf file contains only the loopback address 127.0.0.1. Which of the following is the most likely cause?

Accepted Answer

The client is configured to use a local DNS resolver such as systemd-resolved or dnsmasq.. When /etc/resolv.conf contains only 127.0.0.1, it typically indicates that a local DNS resolver (like systemd-resolved or dnsmasq) is running on the client. These resolvers bind to the loopback address and handle DNS queries locally, often forwarding them to upstream servers provided by DHCP. The client can still resolve hostnames if the local resolver is properly configured to use the DHCP-supplied DNS servers, so the presence of 127.0.0.1 alone does not imply a failure.

Answer

The DHCP server did not provide DNS server information.

Answer

The /etc/resolv.conf file is a symbolic link to /run/NetworkManager/resolv.conf.

Answer

The /etc/resolv.conf file is not being updated by the DHCP client.

Question 15

A Linux workstation must be configured to automatically mount an NFS share from server nfs.example.com:/exports/data at boot time. The share should be mounted with noexec and nosuid options. Which line should be added to /etc/fstab?

Accepted Answer

nfs.example.com:/exports/data /mnt/data nfs noexec,nosuid,_netdev 0 0. It specifies the NFS filesystem type, includes the required mount options (noexec, nosuid, _netdev), and uses the correct fstab format. The _netdev option is critical for network filesystems to ensure the system waits for network availability before attempting the mount at boot time.

Answer

nfs.example.com:/exports/data /mnt/data nfs noexec,nosuid 0 0

Answer

nfs.example.com:/exports/data /mnt/data auto noexec,nosuid,_netdev 0 0

Answer

nfs.example.com:/exports/data /mnt/data nfs4 noexec,nosuid 0 0