Cisco 300-420 Exam Dumps, Practice Test Questions

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.

That option concerns a separate design case: A company wants to expose IPv6 resources to a partner with IPv4-only routing and assumes dual stack at headquarters solves the partner boundary. The relevant control here is: Assess supported inbound traffic engineering such as scoped AS-path prepending or provider communities, recognizing remote-AS policy discretion.

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: Assess supported inbound traffic engineering such as scoped AS-path prepending or provider communities, recognizing remote-AS policy discretion.

That option concerns a separate design case: A company accepts routes from a newly merged BGP AS without maximum-prefix limits, and the peer mistakenly sends hundreds of thousands of prefixes. The relevant control here is: Assess supported inbound traffic engineering such as scoped AS-path prepending or provider communities, recognizing remote-AS policy discretion.

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: Align DMVPN phase/design, NHRP mappings and redirect/shortcut behavior with the intended topology.

That option concerns a separate design case: An organization needs any-to-any group-encrypted private WAN traffic but the new design proposes a traditional hub-and-spoke IPsec overlay with hub hairpins. The relevant control here is: Align DMVPN phase/design, NHRP mappings and redirect/shortcut behavior with the intended topology.

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: Align DMVPN phase/design, NHRP mappings and redirect/shortcut behavior with the intended topology.

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: Use appropriately sampled or on-change model-driven telemetry for the monitored signals, with a scalable receiver architecture.

That option concerns a separate design case: A global WAN telemetry system publishes a complete 10,000-interface snapshot every 100 ms although the target is only five-minute capacity planning. The relevant control here is: Use appropriately sampled or on-change model-driven telemetry for the monitored signals, with a scalable receiver architecture.

This offered choice, “Prefer a supported OpenConfig model for common telemetry and document device-specific augmentations where unavoidable”, addresses a separate concern. That option relates to this separate design case: A multivendor enterprise wants one consistent YANG representation for interface operational counters but each platform exposes vendor-specific native trees. It does not answer the current requirement.

That option concerns a separate design case: A branch policy gives every queue an equal share although its database synchronization is delaying emergency call signaling. The relevant control here is: Protect essential routing/control traffic within bounded QoS classes at actual bottlenecks.

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: Protect essential routing/control traffic within bounded QoS classes at actual bottlenecks.

That option concerns a separate design case: A branch QoS policy matches all TCP 443 traffic as video, including large software downloads. The relevant control here is: Protect essential routing/control traffic within bounded QoS classes at actual bottlenecks.

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: Design supported fabric wireless segmentation with dedicated VNs/SGTs and appropriate wireless control integration.

That option concerns a separate design case: A sensitive engineering VLAN needs to deny lateral guest traffic within one switched segment; existing router ACLs do not inspect intra-VLAN frames. The relevant control here is: Design supported fabric wireless segmentation with dedicated VNs/SGTs and appropriate wireless control integration.

That option concerns a separate design case: A wireless access-point refresh increases PoE needs above the available 802.3at class on older switches. The relevant control here is: Design supported fabric wireless segmentation with dedicated VNs/SGTs and appropriate wireless control integration.

That option concerns a separate design case: A merger requires two administrative BGP regions to appear as one external AS while reducing iBGP mesh size internally. The relevant control here is: Design redundant BGP route reflectors with consistent cluster IDs and reflector-client relationships.

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: Design redundant BGP route reflectors with consistent cluster IDs and reflector-client relationships.

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: Design redundant BGP route reflectors with consistent cluster IDs and reflector-client relationships.

That option concerns a separate design case: A network team manually builds static IPsec tunnels between every SD-WAN edge even though centralized overlay policy is available. The relevant control here is: Evaluate policy-controlled local internet breakout with appropriate security inspection and application path measurement.

That option concerns a separate design case: A site-to-site tunnel must protect financial payload confidentiality and integrity across the public internet. The relevant control here is: Evaluate policy-controlled local internet breakout with appropriate security inspection and application path measurement.

That option concerns a separate design case: A city campus needs a 10-Gbps local metro interconnect with SLA and carrier demarcation, but the proposed design assumes standard broadband internet guarantees. The relevant control here is: Evaluate policy-controlled local internet breakout with appropriate security inspection and application path measurement.

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: Combine trusted traffic classification and marking with a suitable egress priority queue and bandwidth admission design.

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: Combine trusted traffic classification and marking with a suitable egress priority queue and bandwidth admission design.

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: Combine trusted traffic classification and marking with a suitable egress priority queue and bandwidth admission design.

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: Honor the IS-IS overload-bit signaling and restore normal transit eligibility only when routing readiness is confirmed.

That option concerns a separate design case: An EIGRP deployment relies on a single aggregation router and an outage cuts off all downstream branches. The relevant control here is: Honor the IS-IS overload-bit signaling and restore normal transit eligibility only when routing readiness is confirmed.

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: Honor the IS-IS overload-bit signaling and restore normal transit eligibility only when routing readiness is confirmed.

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: Apply a supported edge/PortFast designation only to validated endpoint-facing interfaces.

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: Apply a supported edge/PortFast designation only to validated endpoint-facing interfaces.

That option concerns a separate design case: IP phones and cameras are scheduled for a new closet, but PoE budget is calculated only from the switch's total port count. The relevant control here is: Apply a supported edge/PortFast designation only to validated endpoint-facing interfaces.