Cisco 300-420 Exam Dumps, Practice Test Questions

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: Subdivide the /48 hierarchically by branch and VLAN, with unique /64s and aggregate boundaries that fit the delegation.

That option concerns a separate design case: A retailer adds 70 branches and reused 10.20.0.0/16 at several sites; the MPLS provider cannot distinguish the overlapping prefixes in the enterprise routing table. The relevant control here is: Subdivide the /48 hierarchically by branch and VLAN, with unique /64s and aggregate boundaries that fit the delegation.

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: Subdivide the /48 hierarchically by branch and VLAN, with unique /64s and aggregate boundaries that fit the delegation.

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: Build point-to-point routed access uplinks and use ECMP-capable IGP convergence at the access layer.

That option concerns a separate design case: A new MST campus region accidentally has a different VLAN-to-instance mapping on one distribution switch. The relevant control here is: Build point-to-point routed access uplinks and use ECMP-capable IGP convergence at the access layer.

That option concerns a separate design case: Two campus distribution routers each have a single power feed from the same rack PDU, yet the architecture counts them as separate fault domains. The relevant control here is: Build point-to-point routed access uplinks and use ECMP-capable IGP convergence at the access layer.

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: Evaluate a DMVPN hub/spoke design using NHRP registration and supported dynamic shortcut behavior.

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 DMVPN hub/spoke design using NHRP registration and supported dynamic shortcut behavior.

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: Evaluate a DMVPN hub/spoke design using NHRP registration and supported dynamic shortcut behavior.

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: Engineer a policer with an appropriate burst tolerance and separate real-time queue protection.

That option concerns a separate design case: A guest wireless SSID creates burst traffic exceeding its contracted share and disrupts campus applications. The relevant control here is: Engineer a policer with an appropriate burst tolerance and separate real-time queue protection.

That option concerns a separate design case: A design team calculates voice QoS bandwidth solely from codec payload bit rate and ignores RTP, IP and tunnel overhead. The relevant control here is: Engineer a policer with an appropriate burst tolerance and separate real-time queue protection.

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: Use a hierarchical IS-IS L1/L2 design and summarization at supported area boundaries where it fits topology.

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 a hierarchical IS-IS L1/L2 design and summarization at supported area boundaries where it fits topology.

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: Use a hierarchical IS-IS L1/L2 design and summarization at supported area boundaries where it fits topology.

That option concerns a separate design case: A company needs private predictable cloud connectivity to two regions but its design considers only commodity internet VPNs. The relevant control here is: Use an appropriate Cisco native YANG model for supported platform-specific configuration.

That option concerns a separate design case: A routing telemetry client assumes every operational counter supports on-change updates and receives no updates on one platform. The relevant control here is: Use an appropriate Cisco native YANG model for supported platform-specific configuration.

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 an appropriate Cisco native YANG model for supported platform-specific configuration.

That option concerns a separate design case: A distribution pair advertises the same summary at two locations, but one has a 100-Mbps backhaul and receives half of campus traffic. The relevant control here is: Update summary ownership and ensure discarded or absent specifics cannot mask the retired destination.

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: Update summary ownership and ensure discarded or absent specifics cannot mask the retired destination.

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: Update summary ownership and ensure discarded or absent specifics cannot mask the retired destination.

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: Give each route reflector a stable unique loopback/router ID and advertise reachability through the IGP.

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: Give each route reflector a stable unique loopback/router ID and advertise reachability through the IGP.

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: Give each route reflector a stable unique loopback/router ID and advertise reachability through the IGP.

That option concerns a separate design case: An enterprise edge allows a contracted 50-Mbps guest rate but users report voice degradation during microbursts despite the average staying under 50 Mbps. The relevant control here is: Police untrusted guest ingress traffic to an appropriate rate and violation action at the policy boundary.

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: Police untrusted guest ingress traffic to an appropriate rate and violation action at the policy boundary.

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: Police untrusted guest ingress traffic to an appropriate rate and violation action at the policy boundary.

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: Select a tunnel mechanism or supported IPsec profile that carries required multicast/routing traffic.

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: Select a tunnel mechanism or supported IPsec profile that carries required multicast/routing traffic.

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: Select a tunnel mechanism or supported IPsec profile that carries required multicast/routing traffic.

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 ECMP based on actual per-flow hashing and application sensitivity rather than guaranteed per-packet load balance.

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: Plan ECMP based on actual per-flow hashing and application sensitivity rather than guaranteed per-packet load balance.

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 ECMP based on actual per-flow hashing and application sensitivity rather than guaranteed per-packet load balance.