The implementations group has been using the test bed to do a ‘proof-of-concept’ that requires
both Client 1 and Client 2 to access the WEB Server at 209.65.200.241. After several changes to the
network addressing, routing schemes, DHCP services, NTP services, layer 2 connectivity, FHRP
services, and device security, a trouble ticket has been opened indicating that Client 1 cannot ping
the 209.65.200.241 address. Use the supported commands to isolate the cause of this fault and
answer the following question. What is the solution to the fault condition?
A.
Under the global configuration, delete the no ip dhcp use vrf connected command.
B.
Under the IP DHCP pool configuration, delete the default -router 10.2.1.254 command and enter
the default-router 10.1.4.5 command.
C.
Under the IP DHCP pool configuration, delete the network 10.2.1.0 255.255.255.0 command and
enter the network 10.1.4.0 255.255.255.0 command.
D.
Under the IP DHCP pool configuration, issue the no ip dhcp excluded-address 10.2.1.1 10.2.1.253
command and enter the ip dhcp excluded-address 10.2.1.1 10.2.1.2 command.
Explanation:
On R4 the DHCP IP address is not allowed for network 10.2.1.0/24 which clearly shows the problem
lies on R4 & the problem is with DHCP
you expect people to answer this WITHOUT the troubleshoot sim or even a network diagram and system output…seriouslY?