Cisco 300-420 Exam Dumps, Practice Test Questions

That option concerns a separate design case: An access switch's BPDU Guard disables a legitimate downstream bridge, and the network team proposes disabling Guard on every port. The relevant control here is: Calculate worst-case powered-device class demand, switch power supply budget, and redundancy headroom.

That option concerns a separate design case: A guest workstation port can learn hundreds of source MAC addresses because an unmanaged mini-switch is connected behind it. The relevant control here is: Calculate worst-case powered-device class demand, switch power supply budget, and redundancy headroom.

That option concerns a separate design case: An attacker plugs an unmanaged switch into a lobby edge port and advertises superior STP BPDUs, changing the root topology. The relevant control here is: Calculate worst-case powered-device class demand, switch power supply budget, and redundancy headroom.

That option concerns a separate design case: A service provider backbone runs IS-IS level-1 only across multiple areas, and distant branch routers cannot obtain interarea routes. The relevant control here is: Align IS-IS area addresses for L1 neighbor formation or use supported level-2 adjacency where the topology requires interarea routing.

That option concerns a separate design case: A remote office assigns clients addresses from 169.254.0.0/16 and expects them to be reachable through a routed WAN. The relevant control here is: Align IS-IS area addresses for L1 neighbor formation or use supported level-2 adjacency where the topology requires interarea routing.

That option concerns a separate design case: A network uses IS-IS with dual distribution routers and wants predictable traffic away from a low-bandwidth backup path. The relevant control here is: Align IS-IS area addresses for L1 neighbor formation or use supported level-2 adjacency where the topology requires interarea routing.

That option concerns a separate design case: A 20-Mbps backup link replaces a 200-Mbps primary WAN but the shaper keeps its 200-Mbps limit after failover. The relevant control here is: Provide independent telemetry or out-of-band access appropriate to site criticality and budget.

That option concerns a separate design case: A provider's remote OOB management path is only 2 Mbps, while the network team sends continuous uncompressed telemetry streams at 5 Mbps. The relevant control here is: Provide independent telemetry or out-of-band access appropriate to site criticality and budget.

That option concerns a separate design case: A new multicast source uses group 232.1.1.1 but the client sends only (*,G) membership instead of a source-specific join. The relevant control here is: Provide independent telemetry or out-of-band access appropriate to site criticality and budget.

That option concerns a separate design case: A manufacturing WAN requires multicast distribution but the SD-WAN overlay has only validated unicast OMP reachability. The relevant control here is: Use GRE for appropriate multiprotocol encapsulation and add IPsec separately if confidentiality is required.

That option concerns a separate design case: A network wants a hub-and-spoke topology for finance traffic but allows any-to-any policy for all service VPNs. The relevant control here is: Use GRE for appropriate multiprotocol encapsulation and add IPsec separately if confidentiality is required.

That option concerns a separate design case: A financial organization leases a transparent point-to-point Ethernet service but requires independent routing at each site. The relevant control here is: Use GRE for appropriate multiprotocol encapsulation and add IPsec separately if confidentiality is required.

That option concerns a separate design case: A Cisco-only controller needs platform-specific wireless policies that are not represented by the organization's standard OpenConfig model. The relevant control here is: Distinguish IETF standards-track models from OpenConfig community models and vendor-native schema ownership.

That option concerns a separate design case: A support dashboard needs regular CPU and interface-rate samples even when values remain unchanged. The relevant control here is: Distinguish IETF standards-track models from OpenConfig community models and vendor-native schema ownership.

That option concerns a separate design case: An alerting system needs immediate notice of interface administrative status changes but only polls every five minutes. The relevant control here is: Distinguish IETF standards-track models from OpenConfig community models and vendor-native schema ownership.

That option concerns a separate design case: A site cutover retains a withdrawn /24 under an unchanged /20 campus summary and traffic follows an obsolete transit path. The relevant control here is: Size the entire routed underlay MTU for supported encapsulated payloads rather than only endpoint Ethernet frames.

That option concerns a separate design case: In a planned SD-Access fabric, border nodes can reach edge loopbacks but endpoints fail because the team placed user subnets into the underlay instead of overlay VRFs. The relevant control here is: Size the entire routed underlay MTU for supported encapsulated payloads rather than only endpoint Ethernet frames.

That option concerns a separate design case: Users roam between wired fabric edge switches but their identity assignments change with switch port, breaking microsegmentation. The relevant control here is: Size the entire routed underlay MTU for supported encapsulated payloads rather than only endpoint Ethernet frames.

That option concerns a separate design case: A router receives two EIGRP routes for a prefix with different metrics and the design team wants deterministic failover. The relevant control here is: Use local preference or another AS-wide BGP policy rather than relying on locally significant weight.

That option concerns a separate design case: A branch EIGRP router advertises remote routes back into its hub and occasionally becomes a transit path between hubs. The relevant control here is: Use local preference or another AS-wide BGP policy rather than relying on locally significant weight.

That option concerns a separate design case: Branch A and B redistribute external BGP into OSPF, then advertise resulting routes back into BGP at the opposite edge. The relevant control here is: Use local preference or another AS-wide BGP policy rather than relying on locally significant weight.

That option concerns a separate design case: A branch uses IPsec overlay on broadband with 1400-byte effective MTU, but an application sends 1500-byte DF-set packets and stalls. The relevant control here is: Use the SD-WAN control-plane and key distribution capabilities appropriate to the supported solution.

That option concerns a separate design case: A WAN edge has hundreds of VPN prefixes and growing TLOC paths; an all-to-all overlay approaches its platform session capacity. The relevant control here is: Use the SD-WAN control-plane and key distribution capabilities appropriate to the supported solution.

That option concerns a separate design case: A video conference SD-WAN policy accepts tunnels with 1% packet loss but ignores sustained jitter above application tolerance. The relevant control here is: Use the SD-WAN control-plane and key distribution capabilities appropriate to the supported solution.

That option concerns a separate design case: A provider's remote OOB management path is only 2 Mbps, while the network team sends continuous uncompressed telemetry streams at 5 Mbps. The relevant control here is: Remap backup traffic to a less-preferred class and protect media queues for their intended applications.

That option concerns a separate design case: Two sites use different DSCP mappings for the same video stream and one class is downgraded at the carrier boundary. The relevant control here is: Remap backup traffic to a less-preferred class and protect media queues for their intended applications.

That option concerns a separate design case: A campus uses DSCP EF for voice signaling, voice media, and backup traffic, causing priority queue overload. The relevant control here is: Remap backup traffic to a less-preferred class and protect media queues for their intended applications.

That option concerns a separate design case: A branch aggregation point has both IS-IS and OSPF neighbors with multiple equal-cost exits; traffic unexpectedly hairpins through a data center. The relevant control here is: Apply selective redistribution, tagging and route filtering at clearly defined protocol boundaries.

That option concerns a separate design case: Campus routers detect a fiber break only after long OSPF dead timers, missing a strict voice recovery target. The relevant control here is: Apply selective redistribution, tagging and route filtering at clearly defined protocol boundaries.

That option concerns a separate design case: A new campus design requires maintaining service during both one uplink failure and one planned software upgrade. The relevant control here is: Apply selective redistribution, tagging and route filtering at clearly defined protocol boundaries.

That option concerns a separate design case: An organization needs to reach an IPv6 island over a provider network that carries IPv4 only for the next year. The relevant control here is: Allocate nonoverlapping hierarchical IPv4 blocks by region and site, reserving summary boundaries and documenting any unavoidable VRF isolation.

That option concerns a separate design case: An edge router receives a full BGP table where the security policy allows only the provider's approved default. The relevant control here is: Allocate nonoverlapping hierarchical IPv4 blocks by region and site, reserving summary boundaries and documenting any unavoidable VRF isolation.

This alternative is aimed at a different design constraint: A provider delegation contains 2001:db8:4200::/48 and the design requires 256 independent /64 LANs across 16 branches. The relevant control for this case is: Allocate nonoverlapping hierarchical IPv4 blocks by region and site, reserving summary boundaries and documenting any unavoidable VRF isolation.