When a DHCP IP address conflict occurs on a network, what should normally happen to resolve the conflict correctly?

Introduction / Context:
Dynamic Host Configuration Protocol (DHCP) is used to assign IP addresses automatically to devices on a network. IP conflicts occur when two devices end up with the same IP address, causing network communication problems. This question examines who or what is responsible for resolving such conflicts in a reliable way.

Given Data / Assumptions:

We are considering a DHCP environment where at least one device has an IP address conflict.
A conflict means two hosts are using the same IP address at the same time.
The goal is to choose the realistic method to correct the conflict.

Concept / Approach:
When a DHCP server detects or is informed of an IP conflict, it typically marks the conflicting address as bad and stops assigning it. However, eliminating the conflict often requires an administrator to check static assignments, DHCP reservations, and scopes on the server. Proxy ARP and gratuitous ARP help detect conflicts by checking whether an address is already in use, but they do not automatically fix core configuration mistakes. Ultimately, the proper fix is to remove overlapping static addresses, adjust scopes, or correct misconfigurations on the DHCP server and clients.

Step-by-Step Solution:
Step 1: Recognize that an IP conflict is a configuration or assignment error, not simply a transient network event.Step 2: Recall that DHCP servers can detect conflicts but may not be able to fully repair misconfigured static addresses.Step 3: Understand that tools like gratuitous ARP help in detection rather than in complete conflict resolution.Step 4: Conclude that an administrator must investigate and manually fix the source of the conflict in DHCP scopes or static settings.

Verification / Alternative check:
As a check, consider what happens if two devices are configured statically with the same IP. No DHCP server can automatically change these addresses without human intervention. Even when DHCP is used, an overlapping static assignment must be corrected manually. This thought experiment confirms that an administrator must be involved in resolving the underlying configuration problem, rather than relying on automatic ARP or DHCP behavior alone.

Why Other Options Are Wrong:
Option A is wrong because Proxy ARP is used for specific routing scenarios and does not fix IP conflicts by reconfiguring host addresses.
Option B is wrong because a gratuitous ARP can help detect an IP already in use, but it does not permanently fix a conflict across all devices.
Option D is wrong because DHCP servers do not always automatically reassign new addresses to both conflicting hosts, especially if static addresses are involved or if one device is not using DHCP.

Common Pitfalls:
Many learners assume that DHCP automates everything and that conflicts will always resolve themselves. In practice, administrators must design non overlapping address scopes and avoid manually assigning addresses that conflict with DHCP pools. Another pitfall is to overestimate the role of ARP in fixing configuration errors. ARP can reveal conflicts but cannot change IP addresses on its own.

Final Answer:
The administrator must fix the conflict manually at the DHCP server or in static assignments.