200-301 Refer to the Exhibit Practice Questions

Explanation: The output shows an inconsistency between the two switches. On SW2, the port-channel appears up and the member interfaces are marked with `(P)`, which means they are participating in the bundle. On SW1, the port-channel is shown as `Po1(SD)` and the member links are marked `(I)`, indicating they are stand-alone and not bundled. In simple terms, SW2 thinks the team is formed, but SW1 has not actually joined the links into the team. That tells you the problem is not a protocol mismatch, because both sides are using LACP. The interpretation question is really about reading the state flags correctly.

Explanation: The route used will be the route with the longest matching prefix. In practical terms, 10.60.4.17 falls inside the /28 route shown, and that is more specific than the broader /24 and /16 alternatives. Because specificity comes first, the /28 route wins. This is a clean route-table interpretation problem that mirrors actual exam-style thinking very closely.

Explanation: The most likely required action is to correct the AP's Layer 3 reachability toward the controller, starting with its default gateway. In practical terms, the AP has an IP address in one subnet but a gateway in another. That mismatch prevents correct off-subnet communication to the controller even though the Ethernet link is up. Fixing local Layer 3 reachability is the most direct next step. This is a realistic controller-based WLAN support problem because the controller works for other APs, so the fault is likely local to this AP's network path.

Explanation: The static route is preferred because both routes describe the same destination prefix and the static route has the lower administrative distance. In practical terms, longest-prefix match does not break the tie because the prefixes are equal. The router then compares source trust, and static routing wins over RIP by default. This is a core route-selection concept and a very exam-relevant comparison.

Explanation: PAT is not working correctly because the inside and outside NAT roles are reversed on the interfaces. In practical terms, the private LAN-facing interface should be marked as inside, and the public-facing WAN interface should be marked as outside. In the exhibit, the router has those roles backwards, so translation logic is applied in the wrong direction. This is a very realistic NAT troubleshooting item because the configuration is close to correct and the failure comes from one directional mistake.