Cisco 300-420 Exam Dumps, Practice Test Questions

That option concerns a separate design case: A fabric site needs a guest wireless SSID without extending the guest Layer 2 domain across the whole enterprise. The relevant control here is: Specify access switch PoE capabilities and power budget that support the APs' required negotiated power levels.

That option concerns a separate design case: A remote campus uses two distribution switches and requires nonstop gateway access during a planned supervisor replacement. The relevant control here is: Specify access switch PoE capabilities and power budget that support the APs' required negotiated power levels.

That option concerns a separate design case: An organization needs consistent segmentation across two SD-Access fabric sites connected by a routed MPLS service. The relevant control here is: Specify access switch PoE capabilities and power budget that support the APs' required negotiated power levels.

That option concerns a separate design case: A campus border is configured with two equal-cost external BGP paths but only one is installed for traffic forwarding. The relevant control here is: Apply a scoped outbound prefix filter that blocks private/internal routes from the external BGP adjacency.

That option concerns a separate design case: IS-IS adjacencies form between distribution switches, but all internal prefixes are redistributed from OSPF without loop prevention. The relevant control here is: Apply a scoped outbound prefix filter that blocks private/internal routes from the external BGP adjacency.

That option concerns a separate design case: A campus advertises a /18 summary into the WAN but has no route for one constituent /24 after a building is decommissioned. The relevant control here is: Apply a scoped outbound prefix filter that blocks private/internal routes from the external BGP adjacency.

That option concerns a separate design case: A telemetry receiver supports gRPC but cannot decode the device's gNMI JSON_IETF path data and classifies every update as malformed. The relevant control here is: Select subscription modes according to the actual leaf and device support, using periodic for counters when necessary.

That option concerns a separate design case: A fleet telemetry design streams all available operational leaves every second over a constrained management link. The relevant control here is: Select subscription modes according to the actual leaf and device support, using periodic for counters when necessary.

That option concerns a separate design case: A script writes `ietf-interfaces` fields to a platform supporting only a different module revision and receives an unknown-element error. The relevant control here is: Select subscription modes according to the actual leaf and device support, using periodic for counters when necessary.

That option concerns a separate design case: A lab requires a routed overlay carrying multicast between sites but encryption is not part of the GRE service itself. The relevant control here is: Separate optical multiplexing requirements from routing or Ethernet tenant segmentation carried over the wavelengths.

That option concerns a separate design case: A multisite SD-WAN deployment uses one manager for configuration and assumes manager reachability is necessary for every packet of user data. The relevant control here is: Separate optical multiplexing requirements from routing or Ethernet tenant segmentation carried over the wavelengths.

That option concerns a separate design case: An industrial site uses 4G LTE as primary WAN, and its routing team assumes public inbound addresses remain reachable through carrier-grade NAT. The relevant control here is: Separate optical multiplexing requirements from routing or Ethernet tenant segmentation carried over the wavelengths.

That option concerns a separate design case: A QoS controller marks all backup data DSCP AF41 while the provider honors it as a premium video class. The relevant control here is: Classify traffic by actual application need and reserve EF treatment for suitable expedited traffic.

That option concerns a separate design case: Video and voice both use one strict-priority queue, causing voice jitter when video surges. The relevant control here is: Classify traffic by actual application need and reserve EF treatment for suitable expedited traffic.

That option concerns a separate design case: A switch QoS scheduler guarantees 30% to backup traffic and 80% to voice under full congestion, exceeding possible link capacity. The relevant control here is: Classify traffic by actual application need and reserve EF treatment for suitable expedited traffic.

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: Correct VRRP group identity, priorities, advertisement reachability, and L2 path consistency.

That option concerns a separate design case: HSRP gateways remain reachable locally after their active router loses the only routed upstream uplink. The relevant control here is: Correct VRRP group identity, priorities, advertisement reachability, and L2 path consistency.

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: Correct VRRP group identity, priorities, advertisement reachability, and L2 path consistency.

That option concerns a separate design case: Two OSPF neighbors on a routed core link are stuck in EXSTART/EXCHANGE and one endpoint uses an incompatible MTU. The relevant control here is: Apply EIGRP summarization, stub boundaries, and reliable connectivity to limit query scope.

That option concerns a separate design case: An iBGP route reflector sees several candidate routes to the same destination but advertises only its best path to clients. The relevant control here is: Apply EIGRP summarization, stub boundaries, and reliable connectivity to limit query scope.

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: Apply EIGRP summarization, stub boundaries, and reliable connectivity to limit query scope.

That option concerns a separate design case: An SD-Access architect assumes the fabric's LISP control plane transports all user packets like a data-plane tunnel. The relevant control here is: Plan NSF graceful-restart interoperability with compatible neighbors and realistic convergence timeouts.

That option concerns a separate design case: A design extends SDA fabric across buildings on a WAN with 1500-byte MTU and assumes local campus performance will continue unchanged. The relevant control here is: Plan NSF graceful-restart interoperability with compatible neighbors and realistic convergence timeouts.

That option concerns a separate design case: A virtualized distribution pair uses one logical control plane and engineers assume it offers separate failure domains like two chassis in different buildings. The relevant control here is: Plan NSF graceful-restart interoperability with compatible neighbors and realistic convergence timeouts.

That option concerns a separate design case: A multicast source is reachable through an interface other than the one receiving the packet, but the router still forwards it to all receivers. The relevant control here is: Design reliable RP placement or supported RP redundancy with consistent mapping.

That option concerns a separate design case: A multicast network has active PIM neighbors but one edge switch suppresses IGMP reports after an access-layer topology change. The relevant control here is: Design reliable RP placement or supported RP redundancy with consistent mapping.

That option concerns a separate design case: Two independent PIM-SM domains each use local rendezvous points but remote sources must be discovered across the domains. The relevant control here is: Design reliable RP placement or supported RP redundancy with consistent mapping.

That option concerns a separate design case: An SD-WAN fabric routes guest traffic into the production VPN because a new edge reused the corporate service VPN identifier. The relevant control here is: Provide independent edge and transport paths when required; treat controller redundancy as a separate failure domain.

That option concerns a separate design case: A new WAN edge receives a bootstrap but its control connections fail because the certificate trust chain and organization name differ. The relevant control here is: Provide independent edge and transport paths when required; treat controller redundancy as a separate failure domain.

That option concerns a separate design case: Several data centers need high-capacity optical transport over metropolitan dark fiber without converting each tenant VLAN to an IP tunnel. The relevant control here is: Provide independent edge and transport paths when required; treat controller redundancy as a separate failure domain.

That option concerns a separate design case: A public safety campus requires independent operations from a corporate tenant even when both use the same distribution hardware. The relevant control here is: Use a supported multi-chassis EtherChannel or routed-access design to make redundancy active without a spanning-tree loop.

That option concerns a separate design case: A campus with several hundred VLANs uses one active HSRP gateway for all VLANs while another distribution router remains mostly idle. The relevant control here is: Use a supported multi-chassis EtherChannel or routed-access design to make redundancy active without a spanning-tree loop.

That option concerns a separate design case: A remote campus uses two distribution switches and requires nonstop gateway access during a planned supervisor replacement. The relevant control here is: Use a supported multi-chassis EtherChannel or routed-access design to make redundancy active without a spanning-tree loop.