Pass Your Cisco 200-301 Exam Easy!

Shared administrative accounts erase individual accountability and do not verify that a physical visitor is approved for a wiring closet. Access must be controlled and traceable.

Making the entry code public undermines the security boundary and allows anyone viewing guest information to enter sensitive infrastructure areas.

Port security protects certain Layer 2 attachment risks but does not authorize physical contractor access. Disabling it broadly weakens endpoint control.

A broad aggregate may cover the destination but contains fewer specified bits. A valid host route wins the destination lookup even if the aggregate serves more networks.

Equal-cost multipath operates across equivalent next hops for the same prefix. A host and an aggregate prefix are not equal matches to this destination.

Administrative distance decides installation between candidate sources for the same prefix; it does not choose a broader route over a more-specific installed host entry.

Multicast groups begin ff00::/8. The fe80 prefix is unicast link-local, so creating a multicast distribution tree would not change its routing scope.

Unique-local addresses in fc00::/7 can be routed within an administrative domain. Link-local addresses are a different class, confined to their originating link.

Unique interface identifiers do not expand link-local scope. Even collision-free fe80 addresses require an interface-zone context on the local link and cannot serve as Internet-routing destinations.

Disabling spanning tree across the network removes protection against redundant Layer 2 links and is disproportionate to edge-host DHCP delay.

PortFast on a genuine interswitch link can skip necessary loop-prevention transitions and cause a bridging loop. It should be enabled only for verified edge attachment.

End hosts do not elect STP bridge roots merely by changing switch priority. The issue is forwarding delay on an edge interface.

SNMP polls structured management variables and is not equivalent to retaining a chronological local syslog buffer. Different monitoring mechanisms can coexist but answer different needs.

Console logging prints messages to the attached terminal, not necessarily to a durable in-memory history for later inspection when no console is connected.

Remote logging sends events to the syslog destination but does not preserve a separate local copy when connectivity fails. It cannot satisfy the stated offline local history requirement alone.

Management databases store configuration or telemetry, not a required real-time packet path for all Ethernet traffic. Sending traffic through text storage would not replace forwarding ASICs.

SNMP reads or sets management information and reports events. It does not forward production user packets as a replacement for the switch data plane.

SDN still depends on network links and routable underlays as appropriate. Centralized decisions do not remove the physical need for transport connectivity.

DNS is unrelated to Ethernet first-hop virtual router election and does not rewrite the packet's gateway after every failure.

Hosts are normally configured for the virtual address, not a changing pair of physical router gateway IPs. The redundancy protocol handles ownership.

Manual client reconfiguration defeats the first-hop redundancy objective. Backup master transition is meant to preserve one consistent next-hop identity.

Hiding an SSID does not secure association or encryption and leaves user traffic exposed on an open WLAN.

WEP remains cryptographically unsuitable regardless of passphrase length and does not supply SAE's authenticated password exchange.

WPA2 with TKIP retains an obsolete cipher and is not the newer SAE handshake requested by the security policy.

DNS records publish name-to-address mappings; they cannot create an active IPv6 address on a router interface or enable forwarding.

Link-local fe80 addresses provide same-link communication but are not the configured global-unicast /64 requested for routing outside the local segment.

IPv4 interface address commands and dotted masks do not parse an IPv6 literal. IPv6 has its own address configuration and prefix length syntax.

More frequent CDP messages increase, not reduce, the information revealed to a neighbor. This runs counter to the external exposure concern.

Renaming the hostname changes one advertised field but leaves CDP discovery active. The security requirement is to avoid advertising device details at all.

STP priority affects bridging role election and does not disable CDP advertisements or their TLV content on an interface.

Router names are not selection inputs for DR election. With unequal priority values, a name-based ordering is irrelevant.

Unlike an OSPF path cost, interface priority favors the higher configured value during DR selection. Priority 5 does not beat 20.

A priority-zero interface may participate in the segment but cannot be elected DR/BDR. Zero is an exclusion, not a highest rank.