Cisco 300-420 Exam Dumps, Practice Test Questions

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 explicit route tags, prefix filtering, and redistribution boundaries to block feedback loops.

That option concerns a separate design case: A BGP operator attempts to influence routes within one AS by changing the weight attribute only on one edge router. The relevant control here is: Use explicit route tags, prefix filtering, and redistribution boundaries to block feedback loops.

That option concerns a separate design case: A remote branch uses an OSPF stub area but a design change introduces an ASBR that must redistribute external routes within it. The relevant control here is: Use explicit route tags, prefix filtering, and redistribution boundaries to block feedback loops.

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: Preserve a supported link and endpoint power/wake capability along the intended WoL packet delivery path.

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: Preserve a supported link and endpoint power/wake capability along the intended WoL packet delivery path.

That option concerns a separate design case: A routed campus uses DHCP snooping on access switches but marks every endpoint port trusted for convenience. The relevant control here is: Preserve a supported link and endpoint power/wake capability along the intended WoL packet delivery path.

That option concerns a separate design case: A dual-carrier WAN design changes to backup but automatically switches back on every momentary primary heartbeat recovery. The relevant control here is: Select an appropriate private APN, outbound-initiated overlay, or routable-address service depending on carrier capabilities.

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: Select an appropriate private APN, outbound-initiated overlay, or routable-address service depending on carrier capabilities.

That option concerns a separate design case: A WAN team assumes DWDM wavelength multiplexing itself supplies packet-level route isolation between tenants. The relevant control here is: Select an appropriate private APN, outbound-initiated overlay, or routable-address service depending on carrier capabilities.

That option concerns a separate design case: A campus designs priority queues only on the access switch but ignores a congested upstream WAN edge. The relevant control here is: Establish an explicit QoS trust boundary that remarks or rejects unauthorized markings at ingress.

That option concerns a separate design case: A WAN provider accepts only three traffic classes but headquarters configures eight local DSCP queues and assumes all survive the handoff. The relevant control here is: Establish an explicit QoS trust boundary that remarks or rejects unauthorized markings at ingress.

That option concerns a separate design case: A campus firewall isolates management VRFs but its shared-services route leaking exports all loopbacks to the guest VRF. The relevant control here is: Establish an explicit QoS trust boundary that remarks or rejects unauthorized markings at ingress.

That option concerns a separate design case: A development team consumes a managed runtime that deploys application code without administering underlying servers and calls it raw IaaS. The relevant control here is: Use the supported gNMI service transported over gRPC with device capability and identity verification.

That option concerns a separate design case: An automation team expects NETCONF transactions over SSH to behave like stateless HTTP GET calls with no session or lock semantics. The relevant control here is: Use the supported gNMI service transported over gRPC with device capability and identity verification.

That option concerns a separate design case: A controller issues RESTCONF PATCH to many routers but treats HTTP 200 from a reverse proxy login page as proof that config was changed. The relevant control here is: Use the supported gNMI service transported over gRPC with device capability and identity verification.

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: Align compatible OSPF network type, timers, authentication and neighbor discovery model for that link.

That option concerns a separate design case: A branch OSPF design selects a totally stubby area but an application requires type-3 interarea routes rather than only the default. The relevant control here is: Align compatible OSPF network type, timers, authentication and neighbor discovery model for that link.

That option concerns a separate design case: An OSPF deployment puts all 600 remote access switches into area 0 and floods changes to every site. The relevant control here is: Align compatible OSPF network type, timers, authentication and neighbor discovery model for that link.

That option concerns a separate design case: Two tenants use 10.0.0.0/8 addressing and share the same campus core but require separate routing and firewall policies. The relevant control here is: Design VRF-aware border handoffs or supported segmentation-preserving transit consistent with the policy boundary.

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: Design VRF-aware border handoffs or supported segmentation-preserving transit consistent with the policy boundary.

That option concerns a separate design case: A fabric control-plane node becomes unavailable and endpoint mobility updates stop at one campus site. The relevant control here is: Design VRF-aware border handoffs or supported segmentation-preserving transit consistent with the policy boundary.

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: Pair shaping with explicit class-based queuing and suitable real-time priority policy.

That option concerns a separate design case: Two business units share one management VLAN with unrestricted access to each other's routers. The relevant control here is: Pair shaping with explicit class-based queuing and suitable real-time priority policy.

That option concerns a separate design case: A network architect assumes assigning DSCP CS6 to user browsing guarantees faster internet service from a provider that resets all DSCP. The relevant control here is: Pair shaping with explicit class-based queuing and suitable real-time priority policy.

That option concerns a separate design case: A new SD-WAN site has a single edge appliance and single underlay yet is approved as redundant because controllers run in different data centers. The relevant control here is: Evaluate DWDM wavelength services with optics, reach, dispersion and protection appropriate to the fiber plant.

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: Evaluate DWDM wavelength services with optics, reach, dispersion and protection appropriate to the fiber plant.

That option concerns a separate design case: Backup 5G is installed at a factory but its data plan and APN firewall rules block VPN establishment after primary fiber failure. The relevant control here is: Evaluate DWDM wavelength services with optics, reach, dispersion and protection appropriate to the fiber plant.

That option concerns a separate design case: A building has two independent distribution switches but hosts use the physical IP of one switch as their default gateway. The relevant control here is: Choose a supported redundant supervisor or logical chassis abstraction with explicitly documented switchover behavior.

That option concerns a separate design case: A routed campus uses DHCP snooping on access switches but marks every endpoint port trusted for convenience. The relevant control here is: Choose a supported redundant supervisor or logical chassis abstraction with explicitly documented switchover behavior.

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: Choose a supported redundant supervisor or logical chassis abstraction with explicitly documented switchover behavior.

That option concerns a separate design case: An OSPF redistribution boundary introduces the same connected subnet from two ASBRs, resulting in inconsistent egress selection. The relevant control here is: Evaluate an NSSA design and associated ABR external-route translation rather than a plain stub area.

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: Evaluate an NSSA design and associated ABR external-route translation rather than a plain stub area.

That option concerns a separate design case: An OSPF deployment puts all 600 remote access switches into area 0 and floods changes to every site. The relevant control here is: Evaluate an NSSA design and associated ABR external-route translation rather than a plain stub area.