Which statement best describes the difference between DHCP and SLAAC in IP addressing?

Which statement best describes the difference between DHCP and SLAAC in IP addressing?

• A. DHCP uses MAC address filtering; SLAAC uses DNS.
• B. DHCP and SLAAC both require a server.
• C. DHCP assigns addresses from a configured pool; SLAAC allows devices to configure addresses themselves without a server.
• D. DHCP is IPv6-only; SLAAC is IPv4-only.

Answer: (C)

The main idea here is how devices obtain IP addresses and who or what is involved in giving them those addresses. DHCP provides addresses from a centralized pool managed by a server, leasing them to clients. SLAAC, used with IPv6, lets devices configure their own addresses based on information advertised by routers (the network prefix), without a dedicated server assigning the address. That’s why this option is the best: it captures the essence that DHCP uses a pool from a server, while SLAAC enables self-configuration without a server for the address itself (though other IPv6 settings can be learned differently, and DHCPv6 can be used for additional configuration). For context, in IPv4 networks DHCP is common for distributing addresses and other settings like gateway and DNS. In IPv6, SLAAC allows a host to generate its own address using the advertised prefix, typically forming an address from the prefix and an interface identifier, with an option to pair with DHCPv6 for extra information. The other statements don’t fit because: one mixes up roles like DNS or MAC filtering with address assignment; another claims both require a server, which SLAAC does not for the address itself; and the last wrongly assigns IPv4 and IPv6 limitations to DHCP and SLAAC.

The main idea here is how devices obtain IP addresses and who or what is involved in giving them those addresses. DHCP provides addresses from a centralized pool managed by a server, leasing them to clients. SLAAC, used with IPv6, lets devices configure their own addresses based on information advertised by routers (the network prefix), without a dedicated server assigning the address.

That’s why this option is the best: it captures the essence that DHCP uses a pool from a server, while SLAAC enables self-configuration without a server for the address itself (though other IPv6 settings can be learned differently, and DHCPv6 can be used for additional configuration).

For context, in IPv4 networks DHCP is common for distributing addresses and other settings like gateway and DNS. In IPv6, SLAAC allows a host to generate its own address using the advertised prefix, typically forming an address from the prefix and an interface identifier, with an option to pair with DHCPv6 for extra information.

The other statements don’t fit because: one mixes up roles like DNS or MAC filtering with address assignment; another claims both require a server, which SLAAC does not for the address itself; and the last wrongly assigns IPv4 and IPv6 limitations to DHCP and SLAAC.