Home > Articles

ARP and RARP

  • Print
  • + Share This
This chapter is from the book

Exam Prep Questions

Question 1

Which of the following is the ethernet broadcast address used in ARP and RARP requests?

  1. 255.255.255.255

  2. 08:00:20:11:aa:01

  3. ff:ff:ff:ff:ff:ff

  4. 224.0.0.0

Answer C is correct. ff:ff:ff:ff:ff:ff is the ethernet broadcast address used in ARP and RARP requests. Answer A is incorrect because this represents a netmask. Answer B is incorrect because this is an example of a specific ethernet address that would identify a single interface. Answer D is incorrect because this represents an IP address used for multicast messages.

Question 2

Which of the following describes the function of ARP?

  1. It is used to map a 32-bit IP address to a 48-bit ethernet address.

  2. It is used to map a 48-bit ethernet address to a 32-bit IP address.

  3. It is used to map a 32-bit ethernet address to a 48-bit IP address.

  4. It is used to map a 48-bit IP address to a 32-bit ethernet address.

Answer A is correct. ARP maps a 32-bit IP address to a 48-bit ethernet address. Answer B is incorrect because this describes the function of RARP, not ARP. Answers C and D are incorrect because an ethernet address is 48 bits long and an IP address is 32 bits long. These answers identify the incorrect lengths.

Question 3

Which of the following describes the function of RARP?

  1. It is used to map a 32-bit IP address to a 48-bit ethernet address.

  2. It is used to map a 48-bit ethernet address to a 32-bit IP address.

  3. It is used to map a 32-bit ethernet address to a 48-bit IP address.

  4. It is used to map a 48-bit IP address to a 32-bit ethernet address.

Answer B is correct. RARP maps a 48-bit ethernet address to a 32-bit IP address. Answer A is incorrect because this describes the function of ARP, not RARP. Answers C and D are incorrect because an ethernet address is 48 bits long and an IP address is 32 bits long. These answers identify the wrong lengths.

Question 4

Which of the following configuration files are consulted by the RARP daemon? Choose 2.

  1. /etc/inet/netmasks

  2. /etc/inet/hosts

  3. /etc/ethers

  4. /etc/inetd.conf

  5. /etc/bootparams

Answers B and C are correct. /etc/inet/hosts and /etc/ethers are the configuration files consulted by the RARP daemon. Answer A is incorrect because /etc/inet/netmasks is used to associate IPv4 network masks with IPv4 network numbers. Answer D is incorrect because /etc/inetd.conf is the configuration file for the inetd daemon, which is the Internet services daemon. Answer E is incorrect because /etc/bootparams contains client boot information.

Question 5

In the Solaris 9 operating environment, in.rarpd is started at boot time by which startup script?

  1. /etc/rc3.d/S15nfs.server

  2. /etc/rc3.d/S16boot.server

  3. /etc/rc2.d/S73nfs.client

  4. /etc/rc2.d/S69inet

Answer B is correct. /etc/rc3.d/S16boot.server is the startup script. Answer A is incorrect because this script was used to start in.rarpd prior to Solaris 9. Answer C is incorrect because this script is used to startup the NFS client functionality. Answer D is incorrect because this script carries out the second phase of TCP/IP configuration during the system startup process.

Question 6

Which option of the in.rarpd command enables you to obtain additional debug messages?

  1. -a

  2. -d

  3. -s

  4. -f

Answer B is correct. -d is the debug option. Answer A is incorrect because this option is used by default to start in.rarpd on all ethernet interfaces. Answer C is incorrect because the -s option is not valid for in.rarpd—it is an option for the arp command to add an ARP entry to the cache. Answer D is incorrect because -f is not valid for in.rarpd—it is an option for the arp command to add multiple entries from a file to the ARP cache.

Question 7

You are trying to boot a custom JumpStart client, but get the following message repeatedly on the console when the boot process starts:

Timeout waiting for ARP/RARP packet

What could be the possible cause? Choose 2.

  1. The in.rarpd daemon is not running on the server that is expected to reply to the RARP request.

  2. The inetd daemon is not running on the server that is expected to reply to the RARP request.

  3. The client's ethernet address has been entered incorrectly or is not present in /etc/ethers on the server.

  4. The client's ethernet address is not present in the ARP cache.

Answers A and C are correct because the two causes could be that the in.rarpd daemon is not running on the server that is expected to reply to the RARP request, or the client's Ethernet address has been entered incorrectly or is not present in /etc/ethers on the server. Answer B is incorrect because this daemon does not have any effect on RARP requests. Answer D is incorrect because the ARP cache stores responses from ARP requests and does not affect RARP requests.

  • + Share This
  • 🔖 Save To Your Account