Cisco 300-420 Exam Dumps, Practice Test Questions

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: Use a legitimately allocated private or global prefix at the remote site and reserve IPv4 link-local for local-only communication.

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 a legitimately allocated private or global prefix at the remote site and reserve IPv4 link-local for local-only communication.

That option concerns a separate design case: A campus plans IPv6 addressing with one /64 shared between two routed VLAN interfaces in different buildings. The relevant control here is: Use a legitimately allocated private or global prefix at the remote site and reserve IPv4 link-local for local-only communication.

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: Simplify path preference at domain boundaries and choose intended transit points based on actual traffic flows.

That option concerns a separate design case: A routed-access campus needs equal-cost forwarding to two distribution routers while keeping each VLAN local to one wiring closet. The relevant control here is: Simplify path preference at domain boundaries and choose intended transit points based on actual traffic flows.

That option concerns a separate design case: Two intercampus routers redistribute OSPF and EIGRP in both directions, making route origin hard to track. The relevant control here is: Simplify path preference at domain boundaries and choose intended transit points based on actual traffic flows.

That option concerns a separate design case: A regional healthcare group wants routed site separation within a provider-managed private WAN without building its own full mesh of tunnels. The relevant control here is: Evaluate a provider Layer 2 VPN or Ethernet virtual circuit with explicit loop, MTU and broadcast containment design.

That option concerns a separate design case: Two enterprise buildings use separate Metro Ethernet UNI ports, yet their operators assume the provider will preserve any configured customer VLAN ID. The relevant control here is: Evaluate a provider Layer 2 VPN or Ethernet virtual circuit with explicit loop, MTU and broadcast containment design.

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: Evaluate a provider Layer 2 VPN or Ethernet virtual circuit with explicit loop, MTU and broadcast containment design.

That option concerns a separate design case: A standards group needs an interoperable interface model but mistakenly calls every IETF YANG module an OpenConfig model. The relevant control here is: Use a periodic telemetry subscription at a measured cadence suitable for trending and capacity planning.

That option concerns a separate design case: A security operations service needs authoritative interface state changes, not a dashboard that replays stale telemetry after collector failure. The relevant control here is: Use a periodic telemetry subscription at a measured cadence suitable for trending and capacity planning.

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 a periodic telemetry subscription at a measured cadence suitable for trending and capacity planning.

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: Use link-aware QoS policy to update shaping and class allocations for the reduced-capacity backup transport.

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: Use link-aware QoS policy to update shaping and class allocations for the reduced-capacity backup transport.

That option concerns a separate design case: Network management of a branch uses a VPN over its sole primary WAN, and the organization reports no way to diagnose a provider outage. The relevant control here is: Use link-aware QoS policy to update shaping and class allocations for the reduced-capacity backup transport.

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: Use a topology appropriate to business resilience requirements, such as a structured regional core with redundant distribution paths.

That option concerns a separate design case: Fabric edge nodes encapsulate packets, but the underlay path MTU is too small for added VXLAN overhead. The relevant control here is: Use a topology appropriate to business resilience requirements, such as a structured regional core with redundant distribution paths.

That option concerns a separate design case: A campus has a fabric border but its external firewall cannot distinguish multiple endpoint VNs leaving the fabric. The relevant control here is: Use a topology appropriate to business resilience requirements, such as a structured regional core with redundant distribution paths.

That option concerns a separate design case: A security design requires authenticating OSPF control packets on shared routed links, but only one neighbor has authentication enabled. The relevant control here is: Choose the appropriate stub-area variant or redesign to preserve required interarea summaries.

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: Choose the appropriate stub-area variant or redesign to preserve required interarea summaries.

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: Choose the appropriate stub-area variant or redesign to preserve required interarea summaries.

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: Evaluate a Metro Ethernet service with committed bandwidth, fault demarcation and suitable Ethernet handoff.

That option concerns a separate design case: A retail design directs all cloud SaaS traffic through headquarters even though local internet breakout is allowed and latency is poor. The relevant control here is: Evaluate a Metro Ethernet service with committed bandwidth, fault demarcation and suitable Ethernet handoff.

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: Evaluate a Metro Ethernet service with committed bandwidth, fault demarcation and suitable Ethernet handoff.

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: Use validated application classification or more precise traffic identity instead of assuming TCP port 443 defines one service.

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: Use validated application classification or more precise traffic identity instead of assuming TCP port 443 defines one service.

That option concerns a separate design case: A campus QoS policy gives low priority to routing keepalives and network monitoring, and routing adjacencies flap during congestion. The relevant control here is: Use validated application classification or more precise traffic identity instead of assuming TCP port 443 defines one service.

That option concerns a separate design case: Two access switches uplink to a distribution pair; the architecture stretches one port channel across chassis without verifying multi-chassis support. The relevant control here is: Provide independent power infrastructure for each redundant network node and validate dual-path resilience.

That option concerns a separate design case: A campus access layer spans large broadcast domains for print discovery despite an architecture target of small local VLANs. The relevant control here is: Provide independent power infrastructure for each redundant network node and validate dual-path resilience.

That option concerns a separate design case: A routed-access campus needs equal-cost forwarding to two distribution routers while keeping each VLAN local to one wiring closet. The relevant control here is: Provide independent power infrastructure for each redundant network node and validate dual-path resilience.

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: Configure an appropriate EIGRP stub design on the branch while allowing its locally connected routes to reach the hubs.

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: Configure an appropriate EIGRP stub design on the branch while allowing its locally connected routes to reach the hubs.

That option concerns a separate design case: An EIGRP core has routes stuck active after one WAN path fails and queries spread into many remote sites. The relevant control here is: Configure an appropriate EIGRP stub design on the branch while allowing its locally connected routes to reach the hubs.