Cisco 200-301 Exam Dumps, Practice Test Questions

The server-facing routed uplink does not receive the original client DHCPDISCOVER broadcast; an ip helper-address there will not relay that client-subnet request.

A read-only lease or interface display does not forward a client broadcast across the routed boundary.

Even with server routing in place, clients transmit link-local DHCP broadcasts that need a configured relay at the source segment if the DHCP server is off-subnet.

The ip address dhcp interface command makes the SVI itself a DHCP client instead of relaying DHCPDISCOVER for attached hosts.

The 10.50.0.255 address is the local /24 broadcast, not the remote server 10.70.0.10 required in the stated routed configuration.

An ip default-gateway setting does not create a DHCP relay agent; it cannot forward the client broadcast to the DHCP server.

The UDP service-port field identifies DHCP transport, not the original client-network context for pool selection.

DNS options convey resolver addresses; they are not the relay agent gateway address used by the server for scope selection.

The MAC can identify a client but does not by itself specify the VLAN subnet whose pool should be allocated.

The helper must be applied on the interface receiving the clients’ DHCP broadcasts, here SVI Vlan50.

DHCP client address acquisition is not the relay operation needed to forward VLAN 50 broadcasts to 10.70.0.10.

A different target would not forward client requests to the stated DHCP server.

DNS server list selection is unrelated to whether DHCP requests/offers can traverse the firewall.

Longer leases do not authorize UDP DHCP relay traffic through an interposed firewall.

The problem explicitly involves relay network paths and permitted DHCP traffic, not access VLAN misclassification.

UDP 67 is the DHCP server listening port, not the originating source port of an ordinary client request.

UDP 53 is used by DNS, not DHCPv4 address-assignment messages.

DHCPv4 uses UDP for the exchange; TCP ports 68/67 do not identify normal DHCP client traffic.

DNS settings do not show whether the provider DHCP server sent an address lease to the WAN client.

A relay field describes forwarded LAN client requests; this router’s WAN interface is the DHCP client itself.

Premature static addressing masks the client-exchange fault and may collide with an assigned ISP subnet.

The client broadcast arrives on interface Vlan20; the relay helper belongs on that client-facing gateway interface.

A DHCP client command requests an address for the router, not one on behalf of the VLAN 20 workstation.

Option 6 advertises DNS resolvers to clients, not where the router forwards DHCP requests.

A fresh discover may reproduce the wrong lease if the server’s scope mapping for giaddr is still incorrect.

Packet delivery is already successful; the issue is the wrong client subnet/scope association in relay information.

Native VLAN tagging is unrelated to mapping the DHCP relay’s client gateway field to the correct server address pool.

Lease lifetime does not unblock or route requests and replies between relay and server.

Adding an unverified route can create a black hole; first verify the actual routing and UDP policy paths.

Gateway option values do not establish that the firewall permits relayed DHCP packets on the network path.

Option 3 supplies routers/default gateways, not the DNS server list required for hostname resolution.

Option 51 tells the client how long it may retain the address but does not identify recursive resolvers.

Option 1 identifies the local mask and does not include the DNS resolver addresses.