Question 1easymultiple choice
Read the full DNS explanation →LPIC-2 Network Client Management • Complete Question Bank
Complete LPIC-2 Network Client Management question bank — all 0 questions with answers and detailed explanations.
Refer to the exhibit. Output of `tcpdump -i eth0 port 67 or port 68`: ``` 13:10:05.123456 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:1a:2b:3c:4d:5e, length 300 13:10:05.123789 IP 192.168.1.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300 ```
Refer to the exhibit. Contents of /etc/resolv.conf: ``` nameserver 192.168.1.1 search example.com ```
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?
Refer to the exhibit. ``` # nmcli device show eth0 GENERAL.DEVICE: eth0 GENERAL.TYPE: ethernet GENERAL.HWADDR: 00:1A:2B:3C:4D:5E GENERAL.MTU: 1500 GENERAL.STATE: 100 (connected) GENERAL.CONNECTION: MyConnection WIRED-PROPERTIES.CARRIER: on IP4.ADDRESS[1]: 192.168.1.100/24 IP4.GATEWAY: 192.168.1.1 IP4.DNS[1]: 8.8.8.8 IP4.DNS[2]: 8.8.4.4 ```
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag a concept onto its matching description — or click a concept then click the description.
Stateless protocol with 64-bit file handles
Stateful protocol with integrated locking and security
Adds parallel NFS (pNFS) for scalability
Adds server-side copy and sparse file support
Uses Remote Direct Memory Access for low latency
Refer to the exhibit.
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.10 192.168.1.100;
option routers 192.168.1.1;
option domain-name-servers 8.8.8.8;
}
subnet 192.168.2.0 netmask 255.255.255.0 {
range 192.168.2.10 192.168.2.100;
option routers 192.168.2.1;
option domain-name-servers 8.8.4.4;
}Refer to the exhibit. # /etc/nsswitch.conf passwd: files ldap shadow: files ldap group: files ldap hosts: files dns
Refer to the exhibit. # cat /etc/exports /data 192.168.1.0/24(rw,no_root_squash,async)
Refer to the exhibit.
lease {
interface "eth0";
fixed-address 192.168.1.100;
option subnet-mask 255.255.255.0;
option routers 192.168.1.1;
option domain-name-servers 192.168.1.10,8.8.8.8;
renew 2 2025/03/25 10:00:00;
rebind 2 2025/03/25 12:00:00;
expire 2 2025/03/25 14:00:00;
}Refer to the exhibit. passwd: files ldap group: files ldap shadow: files ldap netgroup: ldap
Refer to the exhibit. server:/export/data on /mnt/data type nfs4 (rw,noatime,vers=4.2,rsize=1048576,wsize=1048576,hard,sec=sys)
Refer to the exhibit. Exhibit: ``` # /etc/ldap.conf base dc=example,dc=com uri ldap://ldap.example.com ldap_version 3 pam_filter objectclass=posixAccount pam_password md5 nss_base_passwd dc=example,dc=com nss_base_shadow dc=example,dc=com nss_base_group dc=example,dc=com ```
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.100 192.168.1.200;
}
subnet 192.168.2.0 netmask 255.255.255.0 {
range 192.168.2.100 192.168.2.200;
}
host special {
hardware ethernet 08:00:27:ab:cd:ef;
fixed-address 192.168.2.10;
}