A university network has 800 IP addresses in its DHCP pool but 4,000 student laptops registered. Under what condition can DHCP still serve all students without running out of addresses?
AIt cannot — a DHCP pool must always have more addresses than registered devices
BOnly if leases are set to be permanent so addresses are never recycled
CAs long as no more than 800 laptops are connected simultaneously and leases expire between sessions
DOnly if each device is assigned a static reservation outside the dynamic pool
The lease mechanism is precisely what makes this work. DHCP addresses are loaned, not permanently assigned. When a laptop disconnects and its lease expires (or it releases the address), that address returns to the pool for the next device. A pool of 800 can serve 4,000 devices over a day as long as the concurrent connection count stays below 800. This is the fundamental scalability insight of DHCP: address reuse over time means the pool can be much smaller than the total device population.
Question 2 Multiple Choice
An administrator needs to change the DNS server address for all 2,000 devices on a DHCP-managed network. What is the correct approach?
AManually update the DNS setting on each of the 2,000 devices
BUpdate the DNS server address in the DHCP server configuration; devices will pick up the change at next lease renewal
CSend a broadcast message to all devices instructing them to request a new lease immediately
DThe change cannot be made remotely — each device controls its own DNS settings
Centralized configuration delivery is one of DHCP's core operational benefits. The DHCP server stores DNS server addresses as options that are included in every DHCP Acknowledge message. An administrator updates the configuration in one place — the server — and every client receives the new value automatically when it renews its lease. This eliminates the error-prone alternative of visiting each device individually. The entire enterprise-scale configuration management benefit of DHCP flows from this centralization.
Question 3 True / False
When a DHCP client first joins a network and has no IP address, it sends its initial Discover message directly to the DHCP server's known IP address.
TTrue
FFalse
Answer: False
A new client has no IP address and — critically — no knowledge of the DHCP server's address. It therefore broadcasts the DHCP Discover message to 255.255.255.255 (limited broadcast), which reaches all devices on the local network segment. The server hears this broadcast and responds. Using broadcast is the only option available to an unconfigured device. This is why the DORA sequence begins with a broadcast even though later communication (unicast renewal at half-lease) can be targeted directly at the known server.
Question 4 True / False
When a DHCP lease expires without the client renewing, the IP address is returned to the pool and becomes available for assignment to another device.
TTrue
FFalse
Answer: True
Lease expiration is the recycling mechanism that gives DHCP its scalability. If a device is carried off the network, powered down, or simply stops responding, the server does not hold that address indefinitely — it marks it available after the lease duration ends. The client that wants to keep its address must renew before expiry (typically at 50% of lease duration). This automatic recycling means addresses are not wasted on absent devices, and the pool can serve far more total devices than its size might suggest.
Question 5 Short Answer
Why is the lease mechanism essential to DHCP's scalability, rather than simply permanently assigning IP addresses to devices?
Think about your answer, then reveal below.
Model answer: Permanent assignment would require as many IP addresses as there are devices that will ever connect — far exceeding the pool. The lease mechanism allows addresses to be recycled: when a device leaves the network (intentionally or through lease expiry), its address returns to the pool and can be reassigned to the next device that joins. A pool of N addresses can serve many more than N total devices, as long as concurrent connections stay within the pool size. Without leasing, every address would be consumed as soon as a device connected, and the pool would be exhausted quickly.
The lease duration is a design parameter that trades responsiveness against overhead. Short leases (minutes) recycle addresses quickly but generate frequent DHCP traffic. Long leases (days) reduce server load but tie up addresses from devices that have long since disconnected. The typical 8–24 hour lease balances these concerns for enterprise environments, while home routers often use 24-hour leases because address exhaustion is rare.