Cisco 300-420 Exam Dumps, Practice Test Questions

That option concerns a separate design case: A switch must remotely wake office PCs overnight, but the access port powers down and the design assumes Wake-on-LAN works regardless of power state. The relevant control here is: Reclassify the specific supported bridge-facing port and retain edge protection elsewhere.

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: Reclassify the specific supported bridge-facing port and retain edge protection elsewhere.

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: Reclassify the specific supported bridge-facing port and retain edge protection elsewhere.

That option concerns a separate design case: A company wants most return traffic for its public prefix to enter ISP B rather than ISP A. The relevant control here is: Design an explicit IPv4/IPv6 translation or application-layer gateway at the interconnection boundary.

That option concerns a separate design case: A dual-stack enterprise BGP peer exchanges IPv4 NLRI but no IPv6 routes despite IPv6 addressing on the transport. The relevant control here is: Design an explicit IPv4/IPv6 translation or application-layer gateway at the interconnection boundary.

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: Design an explicit IPv4/IPv6 translation or application-layer gateway at the interconnection boundary.

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: Evaluate RESTCONF with its YANG-modeled REST resources and authorized HTTP operations.

That option concerns a separate design case: An NOC polls every router with SNMP once every ten minutes and misses 30-second interface utilization spikes. The relevant control here is: Evaluate RESTCONF with its YANG-modeled REST resources and authorized HTTP operations.

That option concerns a separate design case: A support dashboard needs regular CPU and interface-rate samples even when values remain unchanged. The relevant control here is: Evaluate RESTCONF with its YANG-modeled REST resources and authorized HTTP operations.

That option concerns a separate design case: Two sites use different DSCP mappings for the same video stream and one class is downgraded at the carrier boundary. The relevant control here is: Review RP placement and supported redundancy to reduce cross-WAN control-plane dependency.

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: Review RP placement and supported redundancy to reduce cross-WAN control-plane dependency.

That option concerns a separate design case: A design asks to smooth backup traffic to a slow WAN circuit but deploys a policer that simply drops excess packets. The relevant control here is: Review RP placement and supported redundancy to reduce cross-WAN control-plane dependency.

That option concerns a separate design case: A global business wants to connect its datacenter and branches on two different MPLS L3VPN providers with no accidental route leak between customers. The relevant control here is: Require physical route and carrier diversity, including demarcation and access-path audits.

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: Require physical route and carrier diversity, including demarcation and access-path audits.

That option concerns a separate design case: A small branch must use both Internet and private MPLS, and engineers assume the two underlays cannot coexist on one SD-WAN edge. The relevant control here is: Require physical route and carrier diversity, including demarcation and access-path audits.

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: Design endpoint identity and SGT policy consistently across fabric edges with appropriate authentication integration.

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: Design endpoint identity and SGT policy consistently across fabric edges with appropriate authentication integration.

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: Design endpoint identity and SGT policy consistently across fabric edges with appropriate authentication integration.

That option concerns a separate design case: A BGP customer has two provider uplinks and wants automatic loss-of-transport detection when the BGP session remains Established over a stale recursive path. The relevant control here is: Evaluate a managed IPv6-over-IPv4 tunnel overlay with endpoints, MTU and failure behavior explicitly designed.

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: Evaluate a managed IPv6-over-IPv4 tunnel overlay with endpoints, MTU and failure behavior explicitly designed.

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: Evaluate a managed IPv6-over-IPv4 tunnel overlay with endpoints, MTU and failure behavior explicitly designed.

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: Verify the designated RPF path used for each multicast source and align routed topology as needed.

That option concerns a separate design case: A source sends multicast through one router but users join from another site and no multicast routing is configured between them. The relevant control here is: Verify the designated RPF path used for each multicast source and align routed topology as needed.

That option concerns a separate design case: The RPF interface changes after a unicast route failover, but the multicast router retains stale upstream join state. The relevant control here is: Verify the designated RPF path used for each multicast source and align routed topology as needed.

That option concerns a separate design case: An enterprise's primary WAN circuit fails but BGP route withdrawal is delayed while the underlay interface remains up. The relevant control here is: Align IPsec proxy IDs or traffic selectors and routing across the tunnel to the approved prefixes.

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: Align IPsec proxy IDs or traffic selectors and routing across the tunnel to the approved prefixes.

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: Align IPsec proxy IDs or traffic selectors and routing across the tunnel to the approved prefixes.

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: Keep local VLAN boundaries and provide a scoped supported discovery relay or service registration alternative.

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: Keep local VLAN boundaries and provide a scoped supported discovery relay or service registration alternative.

That option concerns a separate design case: Multiple access switches connect to one distribution block through independent Layer 2 uplinks with a blocked redundant path. The relevant control here is: Keep local VLAN boundaries and provide a scoped supported discovery relay or service registration alternative.

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.