Reiko wants to use Dynamic Host configuration protocol (DHCP) to automatically configure the
100 client machines on her network. Ten of these machines are running Linux, and she wants
them to have static IP addresses. The other 90 machines are Windows workstations, which do not
need static IP addresses. Which is the best strategy for Reiko to configure the DHCP server?

A.
Use manual allocation for all machines

B.
Use dynamic allocation for all machines

C.
Use manual allocation for the Linux machines, and use dynamic allocation for the Windows
machines

D.
Use manual allocation for the Linux machines, and use manual allocation for the Windows
machines

Explanation:
Since the Linux machines require static addresses, those machines must be configured with an IP
address. If DHCP is to still be involved in the process for Linux, then those static addresses must
be assigned to each machine using a reservation. Usually, a manual allocation will mean going to
the Linux machine and hardcoding the IP address. For the Windows clients, all that needs to be
done is make them DHCP clients. If the Linux machines are not set up as reservations, then the
DHCP scope will not have (or exclude) the addresses used in the Linux machines.
Incorrect Answers:
A: The use of manual allocation for all machines would mean that DHCP is not required at all. This
essentially means static IP addresses for all nodes. In order to support that environment under
DHCP, every node would require a reservation, which is excessive work. The benefits of using
DHCP in this environment would be small.
B: The only way to use dynamic allocation on all machines is to use reservations for the Linux
addresses. However, this would be assumed and reading too much into the question. Without
reservations, you can’t have static IP addresses in the scope range.
D: If manual allocation is used on the Windows machines, then a DHCP server is not required,
and you lose the benefits of having DHCP on the network.