Directing users to malicious or spoofed hosts by providing attacker controlled gateway or DNS settings is the correct answer.

A rogue DHCP server can hand out network configuration parameters such as the default gateway and DNS servers. When a client accepts those values the attacker can route client traffic through malicious hosts or resolve names to attacker controlled IP addresses and intercept or manipulate connections.

This attack path allows credential harvesting phishing redirects and delivery of additional payloads because clients are unknowingly directed to attacker controlled systems rather than legitimate services.

Facilitating theft of personal data through interception of network traffic is not the best choice because it describes a possible outcome rather than the specific mechanism. A rogue DHCP server enables interception mainly by providing malicious gateway or DNS settings which is why the other option is more precise.

Assigning IP addresses that conflict and causing devices to lose network connectivity is incorrect because DHCP servers typically manage leases to avoid conflicts. While a poorly configured or malicious DHCP server might cause addressing problems the primary risk from a rogue DHCP is redirection through supplied gateways and DNS, not address conflicts.

Encrypting files across the network via a distributed ransomware attack is incorrect because DHCP simply provides network configuration and cannot itself execute or propagate file encryption. Ransomware requires an execution vector and payload delivery which are not actions performed by DHCP alone.

Full AWS Practitioner Certification Question