Pass Your Cisco 200-301 Exam Easy!

A standard ACL can match source addresses but lacks extended protocol and destination-port conditions. It cannot express the required SSH-to-one-host restriction on its own.

Permitting all IP traffic from all sources is broader than the explicit SSH-only management requirement. TCP sequence numbers are not authorization policy and do not restrict the network origin.

SSH normally uses TCP port 22. Matching UDP 22 would not permit the specified SSH sessions, regardless of whether the source subnet is otherwise correct.

Reference bandwidth determines the cost computed for interface speeds, not the Hello/Dead values exchanged during neighbor formation. Changing it does not remove this explicit timer mismatch.

OSPF priority affects DR/BDR election on broadcast segments. It does not override required neighbor timer compatibility and cannot make mismatched Hello intervals acceptable.

Link costs can differ and still permit OSPF neighbors; they affect preferred routing paths after database exchange. Equalizing cost while retaining different timers leaves the adjacency problem.

IPv6 permits the double-colon abbreviation at most once, because otherwise the omitted hextet counts would be ambiguous. This answer contains two such abbreviations.

The ac hextet in the original is the final 16-bit field. Moving it into the third field changes the numeric address rather than merely abbreviating zero hextets.

Three consecutive colons are not legal IPv6 abbreviation syntax. Zero-compression uses exactly double-colon to represent the omitted run, not an extra separator.

Matching local settings by hand is not a controller-managed RF and security policy across many APs; drift and inconsistent changes remain.

Autonomous APs can provide wireless service independently, but configuring each separately does not deliver the centralized policy and RF-management goal for a large common deployment.

Monitoring-only inventory improves visibility but does not replace the centralized configuration/policy capability requested.

Local authentication can identify users, but unencrypted Telnet still exposes administrative traffic; configure SSH and VTY login together.

Telnet transmits authentication and session data without SSH encryption. A VTY configured for Telnet only does not satisfy the mandated encrypted remote-administration channel.

A console password protects physically attached sessions but does not create an SSH server or configure how the remote VTY lines authenticate. Remote access requires separate line and key settings.

GET is intended for retrieving resource representations without the specified creation side effect. Putting a JSON record in a GET request does not make it a compliant create operation.

HEAD obtains response headers without a response body and does not ordinarily create resources. It is useful for metadata checks, not for submitting a new device record.

DELETE removes or requests deletion of a resource; it is not the REST operation for allocating a new collection member. Using it could remove inventory data.

OSPF metric does not determine preference between identical-prefix static routes; their administrative distances do.

Two equal-distance static defaults may be installed for load sharing or chosen as equal candidates on supported platforms. That does not reliably enforce standby-only usage.

A lower administrative distance would make the backup preferred rather than dormant, reversing the specified primary/standby behavior. The distance must be higher than the primary route.

Turning off snooping would make DHCP work but removes the policy protection against rogue DHCP sources. The identified correction is an appropriate uplink trust designation.

Trusting all client-facing switchports opens the network to unauthorized DHCP offers and defeats a principal purpose of snooping. Only legitimate server paths should be trusted.

A DHCP relay is configured on a Layer 3 interface serving a client subnet, not on ordinary Layer 2 access ports. It does not resolve snooping dropping server replies on the uplink.

Static MAC table entries influence intra-VLAN frame delivery but do not route packets between VLAN interfaces or establish IP gateways for hosts in different subnets.

An access port normally belongs to one data VLAN and does not become an inter-VLAN router by blending VLAN membership. The IP networks still require a Layer 3 decision.

SVIs can be local gateways, but the switch still needs IP routing enabled and appropriate policy to forward between them.

A switch does not ordinarily infer an Ethernet access VLAN from an endpoint's IP address. VLAN membership is assigned as a port or authentication policy, not learned from subnet naming.

DHCP supplies IP configuration such as address, default gateway and DNS. It does not by itself reconfigure the switchport's access VLAN membership.

The absence of an access VLAN command does not convert an Ethernet switchport into a routed interface. Port mode and switch model settings determine Layer 2 versus Layer 3 behavior.

FHRP failover preserves the virtual gateway identity; a failed router’s individual interface IP does not migrate between devices.

Changing the virtual gateway address defeats the intended stable first-hop endpoint and can strand clients until reconfigured.

Reconfiguring every host's IP gateway would negate the purpose of a virtual first hop. The group keeps the gateway IP stable during active-router failover.