Cisco
200-101 · Question #169
200-101 Question #169: Real Exam Question with Answer & Explanation
The correct answer is D: Branch(config-if)# ip address 192.168.10.30 255.255.255.240. When only some LAN users cannot reach the Internet, the root cause is an incorrectly sized subnet mask on the router's LAN interface that does not accommodate all 9 users.
Question
A router has been configured to provide the nine users on the branch office LAN with Internet access, as shown in the diagram. It is found that some of the users on the LAN cannot reach the Internet. Based on the topology and router output shown, which command should be issued on the router to correct the problem?
Options
- ABranch(config-if)# no shutdown
- BBranch(config-if)# duplex full
- CBranch(config-if)# no keepalive
- DBranch(config-if)# ip address 192.168.10.30 255.255.255.240
- EBranch(config-if)# bandwidth 100
- FBranch(config-if)# encapsulation 802.3
Explanation
When only some LAN users cannot reach the Internet, the root cause is an incorrectly sized subnet mask on the router's LAN interface that does not accommodate all 9 users.
Common mistakes.
- A. The 'no shutdown' command brings up an administratively disabled interface, but a partially working LAN where only some users are affected would not be in a fully shutdown state.
- B. Setting 'duplex full' addresses a duplex mismatch, which would degrade performance symmetrically across all users rather than blocking only a subset from reaching the Internet.
- C. Removing keepalives affects serial link stability and does not resolve a host addressing or subnet sizing problem on a LAN interface.
- E. The 'bandwidth' command adjusts the metric used by routing protocols for path selection and has no effect on actual traffic forwarding or user reachability.
- F. 802.3 encapsulation is not a valid 'encapsulation' argument for a standard Ethernet LAN interface in Cisco IOS and would not resolve a subnet addressing mismatch.
Concept tested. Router LAN interface IP addressing and subnet sizing
Community Discussion
No community discussion yet for this question.