200-301 — Frequently Asked Questions

A host route exists only when a /32 entry is explicitly installed in the routing table. Here the table shows 10.10.13.0/25, a subnet, so it is a network route covering the destination.

Routers use the default route only when no other entry matches the destination. The 10.10.13.0/25 OSPF route matches and is more specific, so longest-prefix match wins.

10.10.13.0/25 covers only 10.10.13.0 through 10.10.13.127, so Host A's address 10.10.13.214 falls outside it and this entry never matches.

A /29 block is 8 addresses: network 10.10.13.208, usable .209–.214, broadcast .215. Since .214 is the last usable host, it belongs to this subnet.

Input errors is an aggregate counter that includes CRC, frame, overrun, and ignore errors, so any CRC error automatically raises it too.

Runts and giants count frames that violate the 64/1518-byte size limits; an FCS failure can occur on a frame of normal size.

A /21 mask is 255.255.248.0, so the block size is 8 in the third octet. 172.28.224.0 is the network and 172.28.231.255 the broadcast, making the usable range 172.28.224.1-172.28.231.254.

A /29 has 3 host bits, giving 8 addresses total; 172.28.228.144 is the network and .151 is the broadcast. Subtracting both leaves 6 usable hosts from .145 to .150.

In 10.2.1.0/30 the addresses are network .0, hosts .1 and .2, and broadcast .3, so .3 cannot be assigned to an interface.

No, both use 255.255.255.248, which is a /29 mask giving eight addresses, not the /30 required.

No Cisco PoE feature disconnects a device for under-drawing power; unused allocation simply remains available. PoE monitoring only reacts when a port exceeds its administrative power maximum, triggering syslog and err-disabled.

Option A describes PoE monitoring and policing, not classification override itself, which makes the switch ignore the PD's reported class and allocate a fixed amount. It is still the only option stating a true PoE behavior, so it is the intended answer.

EUI-64 is the very process that builds the interface ID from the MAC address. Disabling it removes the MAC-derived ID, so no MAC-based global unicast address would be created.

No. Stateful DHCPv6 assigns addresses from a server pool, and the interface ID does not need to match the MAC address, so it does not satisfy the question's requirement.

The design must fit the largest floor: Floor 2 has 29 users, and a /28 provides only 14 usable hosts, so every floor needs at least a /27 (30 usable).

A /26 offers just 62 usable hosts, which is below the 103-user total, so the smallest summary that holds all four /27 subnets is 192.168.0.0/25.

Because all 8 floors share ONE subnet, so the subnet must hold up to 320 addresses at once. A /25 gives only 126 usable hosts, so it would exhaust after roughly three floors.

Both would connect the office, but 255.255.0.0 (/16) reserves 65,534 usable hosts when only about 320 are needed. The /23 wastes nothing unnecessary, which is what "use address space efficiently" asks for.

On a real Cisco device you would assign the first usable address, 192.168.0.1/23. Every option here lists the network ID, so the intended discriminator is the subnet mask, and only B has the correct one.

The exhibit already confirms a single-mode fiber path with matching long-reach optics at both sites, so the cable/media options are disproven by the output; only the reliability counter shows an actual fault.

Reliability is a 255-based scale where 255/255 means error-free delivery; a value like 166/255 indicates frames are being dropped or errored, typically from incrementing input or CRC errors.

Connecting servers and clients to a network is done by an intermediate device such as a switch; the endpoint is the server or client itself.

Forwarding traffic between VLANs requires a Layer 3 switch or router — devices that carry traffic between endpoints, not endpoints themselves.

It is a common use, but it is narrower than the RFC 7519 definition. JWTs carry any claims — roles, expiry, issuer — so 'securely exchange information' is the accurate general description.

No. A standard JWT payload is Base64URL-encoded and digitally signed (JWS), so it can be read by anyone holding it. Encryption only occurs if the JWE structure is deliberately used.

192.168.10.2 is in the clients' own subnet, so no relay is needed or possible — a same-subnet DHCP server is reached by broadcast. The helper address must be the remote DHCP server, 192.168.20.2.

192.168.20.1 is the gateway address of the server subnet, not the DHCP server itself. ip helper-address must point to the unicast address of the device that actually answers DHCP requests.

Catalyst switches can hash Layer 3 fields in hardware, and Cisco's WLC best-practices note recommends source-destination IP for more even distribution across many clients.

Hashing on source-destination IP keeps each client-to-controller flow on one link, preserving frame order while balancing aggregate traffic across the bundle.

Centralizing management tasks implies a controller-based or SDN architecture. A traditionally managed network is administered device-by-device, so centralized automation would change its management model rather than reduce costs within it.

Adding staff increases labor costs directly, which contradicts the goal of reducing maintenance costs. Cost-reduction answers on this exam virtually always involve automation or tooling, not more headcount.

The two switch-facing ports land on routed interfaces, which stop Layer 2 broadcast propagation, so no loop needs breaking. The design fails earlier because the router rejects two interfaces in one subnet.

Yes. Cisco IOS rejects a second interface address that falls inside an already-used subnet with an "% ... overlaps

A Layer 2 switch forwards Ethernet frames using MAC addresses within the same broadcast domain or VLAN. It never inspects IP addresses, so it cannot route between two different networks.

"Packet" refers to a Layer 3 PDU carrying IP addresses, and only a router processes packets. Switches work with frames at Layer 2, making the router the only device that can verify IPs and forward between subnets.