Question 220The datacom engineering team at a government service campus after a monitored link change reviews this independent fictional networking case: A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Which corrective engineering action most directly addresses this problem? Restore transport IP reachability to the neighbor before changing BGP route policies Apply explicit prefix-length-aware export policy limited to authorized aggregate space Introduce a correctly designed iBGP route reflector cluster with appropriate clients and redundancy Apply next-hop-self on the appropriate border speaker or otherwise make the next hop legitimately reachable ExplanationCorrect Answer C:Introduce a correctly designed iBGP route reflector cluster with appropriate clients and redundancy. This is the specific action that addresses the fictional fault: A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. The governing technical reason is: Route reflection replaces full-mesh iBGP peering while preserving loop-prevention attributes. Verify by checking: All clients learn the intended prefixes and remain connected after a reflector failover. Incorrect Answers A:Restoring transport IP reachability to the neighbor before changing BGP route policies is relevant when a BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. It does not resolve this case: A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Route reflection replaces full-mesh iBGP peering while preserving loop-prevention attributes. B:When an accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter, applying explicit prefix-length-aware export policy limited to authorized aggregate space could be appropriate. Here, a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Introduce a correctly designed iBGP route reflector cluster with appropriate clients and redundancy. D:An iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally. Applying next-hop-self on the appropriate border speaker or otherwise make the next hop legitimately reachable can respond to that condition, but it would not correct the reported fault: A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. All clients learn the intended prefixes and remain connected after a reflector failover.
Question 221The datacom engineering team at a university hospital during a network security audit reviews this independent fictional networking case: A router recovering from reboot begins attracting transit traffic before its route state is ready. The team applies this remedy: Apply a controlled IS-IS overload period during startup and remove it after routing readiness. Which observation would directly demonstrate that this specific issue is resolved? Each participating router reports the intended metric and selects consistent next hops Traces avoid the recovering node until readiness and return afterward without loss The intended stable router becomes DIS and the pseudonode LSP refreshes correctly Peers converge to the same current LSP sequence and the affected route becomes stable ExplanationCorrect Answer B:Traces avoid the recovering node until readiness and return afterward without loss. This is a directly observable check for the proposed correction: Apply a controlled IS-IS overload period during startup and remove it after routing readiness. The particular failure being investigated is: A router recovering from reboot begins attracting transit traffic before its route state is ready. Incorrect Answers A:Each participating router reports the intended metric and selects consistent next hops. That result could validate a repair when a new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. Here, a router recovering from reboot begins attracting transit traffic before its route state is ready; the IS-IS overload bit discourages transit use of an incompletely initialized router. C:When a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn, a result such as this is useful: The intended stable router becomes DIS and the pseudonode LSP refreshes correctly. For the reported fault, a router recovering from reboot begins attracting transit traffic before its route state is ready; apply a controlled IS-IS overload period during startup and remove it after routing readiness. D:Core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. Peers converge to the same current LSP sequence and the affected route becomes stable. This observation does not prove the correction for the reported defect: A router recovering from reboot begins attracting transit traffic before its route state is ready. Early transit selection can blackhole traffic during control-plane recovery.
Question 222The datacom engineering team at a cloud hosting provider after an incident review reviews this independent fictional networking case: IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. A proposed remedy is: Verify physical MTU, CLNS frame transport and IS-IS padding support along the circuit. Which technical principle most directly supports this remedy? IS-IS link-state consistency depends on reliable LSP version synchronization within each level IS-IS metric encoding capability must be consistent enough for all participating routers to calculate intended paths IS-IS protocol authentication must match across neighbor exchanges to maintain trusted adjacencies IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic ExplanationCorrect Answer D:IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic. This directly explains why the corrective operation is appropriate: Verify physical MTU, CLNS frame transport and IS-IS padding support along the circuit. The observed acceptance evidence should be: IS-IS hellos and LSP floods succeed and the remote LSDB converges. Incorrect Answers A:IS-IS link-state consistency depends on reliable LSP version synchronization within each level. That rule governs a different situation: Core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. Here, IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic. B:IS-IS metric encoding capability must be consistent enough for all participating routers to calculate intended paths. That principle is relevant when a new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. Here, IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass; verify physical MTU, CLNS frame transport and IS-IS padding support along the circuit. C:An IS-IS adjacency drops after only one of two core routers receives a new authentication key. IS-IS protocol authentication must match across neighbor exchanges to maintain trusted adjacencies. The current condition differs: IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. IS-IS hellos and LSP floods succeed and the remote LSDB converges.
Question 223The datacom engineering team at a cloud hosting provider after an incident review reviews this independent fictional networking case: A high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling. A proposed remedy is: Tune BFD intervals and multiplier for supported device and transport capabilities. Which technical principle most directly supports this remedy? Failure detection speed must be balanced against scheduling jitter and false-positive risk BFD session state depends on interoperable mode and timing negotiation between peers BFD provides rapid bidirectional failure detection to subscribed routing protocols VRRP continuity depends on end hosts and switches forwarding toward the current virtual gateway owner ExplanationCorrect Answer A:Failure detection speed must be balanced against scheduling jitter and false-positive risk. This directly explains why the corrective operation is appropriate: Tune BFD intervals and multiplier for supported device and transport capabilities. The observed acceptance evidence should be: BFD remains stable under expected CPU load and still detects real test failures within requirement. Incorrect Answers B:Two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior. BFD session state depends on interoperable mode and timing negotiation between peers. The current condition differs: A high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling. Failure detection speed must be balanced against scheduling jitter and false-positive risk. C:BFD provides rapid bidirectional failure detection to subscribed routing protocols. That principle is relevant when OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection. Here, a high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling; tune BFD intervals and multiplier for supported device and transport capabilities. D:A host keeps sending traffic to the old gateway's MAC after a VRRP switchover because the access LAN fails to update its neighbor cache. VRRP continuity depends on end hosts and switches forwarding toward the current virtual gateway owner. The current condition differs: A high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling. BFD remains stable under expected CPU load and still detects real test failures within requirement.
Question 224The datacom engineering team at a hospital imaging provider during a controlled network cutover reviews this independent fictional networking case: Newly moved office endpoints cannot receive IPv4 leases because their DHCP server is across a routed interface without a relay. A proposed remedy is: Configure DHCP relay on the correct client-facing interface and verify reachability to the DHCP server. Which technical principle most directly supports this remedy? Network management polling should use authenticated and encrypted protocol settings when sensitive telemetry is exposed Source-specific multicast forwarding is tied to a particular source and group rather than RP-based ASM discovery IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic DHCP broadcast discovery normally requires relay handling when the server is in another IP subnet ExplanationCorrect Answer D:DHCP broadcast discovery normally requires relay handling when the server is in another IP subnet. This directly explains why the corrective operation is appropriate: Configure DHCP relay on the correct client-facing interface and verify reachability to the DHCP server. The observed acceptance evidence should be: Discover/offer/request/ack exchange completes and clients receive correct scopes and gateways. Incorrect Answers A:Network management polling should use authenticated and encrypted protocol settings when sensitive telemetry is exposed. That rule governs a different situation: An enterprise polls infrastructure over legacy unauthenticated SNMP and risks exposing operational data across shared networks. Here, newly moved office endpoints cannot receive IPv4 leases because their DHCP server is across a routed interface without a relay. DHCP broadcast discovery normally requires relay handling when the server is in another IP subnet. B:Source-specific multicast forwarding is tied to a particular source and group rather than RP-based ASM discovery. That rule governs a different situation: A receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. Here, newly moved office endpoints cannot receive IPv4 leases because their DHCP server is across a routed interface without a relay. Configure DHCP relay on the correct client-facing interface and verify reachability to the DHCP server. C:IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic. That principle is relevant when IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. Here, newly moved office endpoints cannot receive IPv4 leases because their DHCP server is across a routed interface without a relay; discover/offer/request/ack exchange completes and clients receive correct scopes and gateways.
Question 225The datacom engineering team at an agricultural equipment distributor after an incident review reviews this independent fictional networking case: A router recovering from reboot begins attracting transit traffic before its route state is ready. Which corrective engineering action most directly addresses this problem? Verify physical MTU, CLNS frame transport and IS-IS padding support along the circuit Align the IS-IS area portion of the NET or revise the intended L1/L2 boundary Apply a controlled IS-IS overload period during startup and remove it after routing readiness Set compatible IS-IS circuit levels consistent with the core design ExplanationCorrect Answer C:Apply a controlled IS-IS overload period during startup and remove it after routing readiness. This is the specific action that addresses the fictional fault: A router recovering from reboot begins attracting transit traffic before its route state is ready. The governing technical reason is: The IS-IS overload bit discourages transit use of an incompletely initialized router. Verify by checking: Traces avoid the recovering node until readiness and return afterward without loss. Incorrect Answers A:IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. This is where verifying physical MTU, CLNS frame transport and IS-IS padding support along the circuit would help. By contrast, a router recovering from reboot begins attracting transit traffic before its route state is ready. The IS-IS overload bit discourages transit use of an incompletely initialized router. B:Two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses. This is where aligning the IS-IS area portion of the NET or revise the intended L1/L2 boundary would help. By contrast, a router recovering from reboot begins attracting transit traffic before its route state is ready. Apply a controlled IS-IS overload period during startup and remove it after routing readiness. D:Setting compatible IS-IS circuit levels consistent with the core design is relevant when a transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2. It does not resolve this case: A router recovering from reboot begins attracting transit traffic before its route state is ready. Traces avoid the recovering node until readiness and return afterward without loss.
Question 226The datacom engineering team at a financial clearing service during a network security audit reviews this independent fictional networking case: Branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. Which corrective engineering action most directly addresses this problem? Introduce an accurate ABR area range after verifying all component prefixes and forwarding outcomes Coordinate the configured authentication mode and active key material at both ends of the link Align the totally stub area behavior at the ABR and verify the intended default-based forwarding Check Type-7 external origination and ABR translation toward Type-5 reachability in the backbone ExplanationCorrect Answer C:Align the totally stub area behavior at the ABR and verify the intended default-based forwarding. This is the specific action that addresses the fictional fault: Branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. The governing technical reason is: Totally stubby configuration suppresses most interarea summaries while retaining the area default route. Verify by checking: Branch route tables contain the intended default rather than the unexpected interarea prefixes. Incorrect Answers A:Introducing an accurate ABR area range after verifying all component prefixes and forwarding outcomes is relevant when several closely related access prefixes create unnecessary interarea LSA churn because no ABR aggregation is applied. It does not resolve this case: Branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. Totally stubby configuration suppresses most interarea summaries while retaining the area default route. B:When an OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only, coordinating the configured authentication mode and active key material at both ends of the link could be appropriate. Here, branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. Align the totally stub area behavior at the ABR and verify the intended default-based forwarding. D:An NSSA branch redistributes a local static route that fails to appear as expected outside the NSSA. This is where checking Type-7 external origination and ABR translation toward Type-5 reachability in the backbone would help. By contrast, branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. Branch route tables contain the intended default rather than the unexpected interarea prefixes.
Question 227The datacom engineering team at an air-cargo logistics operator during a network security audit reviews this independent fictional networking case: A high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling. If this issue remains unresolved, what immediate availability or security risk follows most directly? Unplanned Master placement may steer client traffic over a less reliable exit Incorrect group placement can create duplicate gateway ownership or unreachable hosts Oversensitive BFD can cause route flapping on healthy circuits Slow liveness detection can extend avoidable black-hole duration after link failure ExplanationCorrect Answer C:Oversensitive BFD can cause route flapping on healthy circuits. Leaving the exact fault unresolved means: A high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling. The intended response is: Tune BFD intervals and multiplier for supported device and transport capabilities. Incorrect Answers A:Unplanned Master placement may steer client traffic over a less reliable exit. That risk belongs to a separate condition: A backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. Here, a high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling; failure detection speed must be balanced against scheduling jitter and false-positive risk. B:Incorrect group placement can create duplicate gateway ownership or unreachable hosts. That consequence could follow when two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error. Here, a high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling; tune BFD intervals and multiplier for supported device and transport capabilities. D:Slow liveness detection can extend avoidable black-hole duration after link failure. That risk belongs to a separate condition: OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection. Here, a high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling; BFD remains stable under expected CPU load and still detects real test failures within requirement.
Question 228The datacom engineering team at a library district network after a planned hardware refresh reviews this independent fictional networking case: An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. If this issue remains unresolved, what immediate availability or security risk follows most directly? Missing local preference control can increase egress charges and path instability Missing address-family negotiation leaves overlays unreachable despite a healthy BGP session Partial iBGP distribution can hide routes from only some leaf devices An eBGP AS mismatch blocks external route exchange at the edge ExplanationCorrect Answer B:Missing address-family negotiation leaves overlays unreachable despite a healthy BGP session. Leaving the exact fault unresolved means: An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. The intended response is: Enable and validate the correct EVPN address-family capability and policy on both peers. Incorrect Answers A:A multihomed autonomous system sends outbound traffic via a paid backup despite the intended primary exit. In that situation, missing local preference control can increase egress charges and path instability. Here instead, an EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. A base BGP TCP session does not imply that every MP-BGP address family is negotiated and active. C:A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. In that situation, partial iBGP distribution can hide routes from only some leaf devices. Here instead, an EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. Enable and validate the correct EVPN address-family capability and policy on both peers. D:When an edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS, an eBGP AS mismatch blocks external route exchange at the edge. The present failure is different: An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. The EVPN address-family neighbor state and advertised route types appear as expected.
Question 229The datacom engineering team at a hospital imaging provider during a controlled network cutover reviews this independent fictional networking case: An area border router advertises a broad summary that includes subnets withdrawn after a site closure. Which corrective engineering action most directly addresses this problem? Set OSPF interface priorities to favor a stable distribution router and perform a planned election transition Recalculate and set appropriate OSPF costs for the changed link while documenting routing intent Evaluate E1 versus E2 external metric behavior and configure the intended metric type consistently Tighten the configured summary to reachable address blocks and test interarea destinations ExplanationCorrect Answer D:Tighten the configured summary to reachable address blocks and test interarea destinations. This is the specific action that addresses the fictional fault: An area border router advertises a broad summary that includes subnets withdrawn after a site closure. The governing technical reason is: ABR summaries reduce LSDB size but overbroad summaries can attract packets for nonexistent destinations. Verify by checking: Interarea advertisements cover only approved reachable blocks and traced flows reach valid hosts. Incorrect Answers A:A shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. This is where setting OSPF interface priorities to favor a stable distribution router and performing a planned election transition would help. By contrast, an area border router advertises a broad summary that includes subnets withdrawn after a site closure. ABR summaries reduce LSDB size but overbroad summaries can attract packets for nonexistent destinations. B:When after an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed, recalculating and set appropriate OSPF costs for the changed link while documenting routing intent could be appropriate. Here, an area border router advertises a broad summary that includes subnets withdrawn after a site closure. Tighten the configured summary to reachable address blocks and test interarea destinations. C:Evaluating E1 versus E2 external metric behavior and configuring the intended metric type consistently is relevant when a remote site incorrectly chooses an external OSPF route that ignores material internal distance to competing exit points. It does not resolve this case: An area border router advertises a broad summary that includes subnets withdrawn after a site closure. Interarea advertisements cover only approved reachable blocks and traced flows reach valid hosts.
Question 230The datacom engineering team at a library district network after a planned hardware refresh reviews this independent fictional networking case: A static route is configured to a next-hop address that is absent from the local routing table and never becomes active. A proposed remedy is: Provide a resolvable route to the next hop or replace it with the verified directly reachable next hop. Which technical principle most directly supports this remedy? Longest-prefix matching precedes route preference comparisons between routes of different mask lengths A static route depending on recursive resolution cannot forward when its next-hop recursion fails A healthy control plane does not prove that hardware forwarding entries are programmed in the data plane IS-IS adjacencies require at least one common enabled routing level ExplanationCorrect Answer B:A static route depending on recursive resolution cannot forward when its next-hop recursion fails. This directly explains why the corrective operation is appropriate: Provide a resolvable route to the next hop or replace it with the verified directly reachable next hop. The observed acceptance evidence should be: The static route is active and its recursive next hop resolves to an operational interface. Incorrect Answers A:Longest-prefix matching precedes route preference comparisons between routes of different mask lengths. That principle is relevant when a branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. Here, a static route is configured to a next-hop address that is absent from the local routing table and never becomes active; a static route depending on recursive resolution cannot forward when its next-hop recursion fails. C:A healthy control plane does not prove that hardware forwarding entries are programmed in the data plane. That principle is relevant when newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries. Here, a static route is configured to a next-hop address that is absent from the local routing table and never becomes active; provide a resolvable route to the next hop or replace it with the verified directly reachable next hop. D:IS-IS adjacencies require at least one common enabled routing level. That principle is relevant when a transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2. Here, a static route is configured to a next-hop address that is absent from the local routing table and never becomes active; the static route is active and its recursive next hop resolves to an operational interface.