Following ticket consists of a problem description and existing configuration on the device.

Figure 1

Figure 2
Trouble Ticket Statement
Client 1 and Client 2 are not able to reach the WebServer at 209.65.200.241. Initial troubleshooting showsthat DSW1， DSW2 and all the routers are able to reach the WebServer
Cisco 642-832： Practice Exam
Configuration on R1
ip nat inside source list nat_pool interface Serial0/0/0/1 overload!
ip access-list standard nat_poolpermit 10.1.0.0!
interface Serial0/0/0/1
ip address 209.65.200.224 255.255.255.252
ip nat outside!
interfaceSerial0/0/0/0.12
ip address 10.1.1.1 255.255.255.252
ip nat inside
ip ospf message-digest-key 1 md5 TSHOOT
ip ospd authentication message-digest
On Which device is the fault condition located？（）

Following ticket consists of a problem description and existing configuration on the device.
Cisco 642-832： Practice Exam

Figure 1

Figure 2
Trouble Ticket Statement
Client 1 is able to ping 209.65.200.226 but not the Web Server at 209.65.200.241. Initial troubleshootingshows and R1 does not have any BGP routes. R1 also does not show any active
Cisco 642-832： Practice Exam
BGP neighbor
Configuration on R1
router bgp 65001
no synchronization
bgp log-neighbor-changes
network 209.65.200.224 mask 255.255.255.252
neighbor 209.56.200.226 remote-as 65002
no auto-summary
What is the solution of the fault condition？（）