Cisco Updated 200-301 Exam Questions and Answers by montgomery

HSRP gives hosts a resilient default gateway by using a virtual IP address shared by a group of routers. One router is elected active and forwards traffic sent to the virtual gateway; another router waits as standby and takes over if the active router fails. The hosts do not need to know which physical router is active. They continue to use the same default gateway address. That is the central first-hop redundancy model Cisco expects CCNA candidates to understand. HSRP does not synchronize full router configurations, and it does not make every router use the same physical interface address. It also does not inherently load-balance all gateway traffic; classic HSRP is active/standby per group, although designs can use multiple groups for load sharing. The predictable HSRP behaviors are election of active and standby routers, plus use of a shared virtual IP address as the LAN default gateway. Therefore, B and D are the valid choices.

PortFast is used on access ports that connect to end devices, not to other switches. Its practical effect is to reduce spanning-tree convergence delay for those edge ports. In normal 802.1D behavior, a port may pass through blocking, listening, and learning before it forwards frames. PortFast bypasses the listening and learning delay for a trusted edge connection and allows the port to enter forwarding quickly when the link comes up. Cisco CCNA 200-301 v1.1 places this under Network Access because it is a switching feature that directly affects host connectivity. The wording in the answer choices matters: PortFast does not enable BPDUs, and it does not put the port into the listening state. It also should not be treated as a loop-prevention feature by itself; if a switch is accidentally connected to a PortFast port, BPDU Guard is normally paired with it. The clean exam answer is that PortFast minimizes spanning-tree convergence time for access-facing ports.

In local AP mode, a lightweight access point builds CAPWAP connectivity to the wireless LAN controller and normally sends both control and client data traffic through the controller. Cisco commonly describes this as separate CAPWAP control and data tunnels. FlexConnect mode is different because it is designed for remote or branch deployments where the AP may locally switch client data traffic instead of backhauling it all through the WLC. That is why option C is wrong: with local switching, FlexConnect bridges traffic locally, not from the AP to the WLC. FlexConnect can also continue serving clients during a WAN or controller outage, depending on configuration and authentication method, so option B is wrong. Local mode does not turn the AP into an autonomous AP; it remains controller-based. Cisco CCNA 200-301 v1.1 Network Access expects the distinction between centralized WLC forwarding and branch-friendly FlexConnect operation. The clearly correct difference in the options is A.

R1 uses a network route, not a host route, floating static route, or default route. The destination host is 10.10.13.10/32, but the routing-table entry that matches it is the OSPF-learned network prefix 10.10.13.0/25. That prefix covers host addresses from 10.10.13.1 through 10.10.13.126, so the host address is included. A host route would be a /32 entry specifically for 10.10.13.10. A default route would be 0.0.0.0/0 and would be used only if no more specific route matched. A floating static route is a backup static route with a higher administrative distance; the exhibit shows an OSPF route being selected. Cisco CCNA v1.1 IP Connectivity emphasizes longest-prefix match and route-code interpretation. The router does not care that the destination is a single host; it forwards by the most specific matching route in the table. Here, that route is a network route.