Question 640The datacom engineering team at a warehouse automation provider during a topology consistency review reviews this independent fictional networking case: A LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. A proposed remedy is: Tune IS-IS DIS priority on the shared LAN and validate neighbor continuity after a planned election. Which technical principle most directly supports this remedy? On broadcast IS-IS circuits the DIS originates a pseudonode LSP and its election follows IS-IS priority rules Level-1 IS-IS neighbors must belong to a compatible area while Level-2 can connect areas IS-IS link-state consistency depends on reliable LSP version synchronization within each level IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic ExplanationCorrect Answer A:On broadcast IS-IS circuits the DIS originates a pseudonode LSP and its election follows IS-IS priority rules. This directly explains why the corrective operation is appropriate: Tune IS-IS DIS priority on the shared LAN and validate neighbor continuity after a planned election. The observed acceptance evidence should be: The intended stable router becomes DIS and the pseudonode LSP refreshes correctly. Incorrect Answers B:Two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses. Level-1 IS-IS neighbors must belong to a compatible area while Level-2 can connect areas. The current condition differs: A LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. On broadcast IS-IS circuits the DIS originates a pseudonode LSP and its election follows IS-IS priority rules. C:IS-IS link-state consistency depends on reliable LSP version synchronization within each level. That principle is relevant when core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. Here, a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn; tune IS-IS DIS priority on the shared LAN and validate neighbor continuity after a planned election. D:When 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. By contrast, a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn; the intended stable router becomes DIS and the pseudonode LSP refreshes correctly.
Question 641The datacom engineering team at an e-commerce fulfillment center while validating change-control evidence reviews this independent fictional networking case: A user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port. A proposed remedy is: Apply supported BPDU protection at legitimate edge ports and investigate the unexpected bridge connection. Which technical principle most directly supports this remedy? Edge-port fast transition should not make unauthorized bridge participation safe RSTP alternate ports are designed to become forwarding backups after topology changes MSTP region equivalence depends on a matching region configuration identifier, not just physical adjacency Routing control channels should be limited to trusted neighbors independently of ordinary forwarding ExplanationCorrect Answer A:Edge-port fast transition should not make unauthorized bridge participation safe. This directly explains why the corrective operation is appropriate: Apply supported BPDU protection at legitimate edge ports and investigate the unexpected bridge connection. The observed acceptance evidence should be: A received BPDU triggers the configured protective response and no loop appears. Incorrect Answers B:When a redundant access uplink stays blocked even after the active link fails because the switch has not converged its port roles correctly, RSTP alternate ports are designed to become forwarding backups after topology changes. By contrast, a user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port; edge-port fast transition should not make unauthorized bridge participation safe. C:Two switches intended in one MSTP region behave as if separated by a regional boundary after an unnoticed configuration edit. MSTP region equivalence depends on a matching region configuration identifier, not just physical adjacency. The current condition differs: A user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port. Apply supported BPDU protection at legitimate edge ports and investigate the unexpected bridge connection. D:When a provider-facing interface accepts unexpected routing-control connections from an unapproved adjacent host, routing control channels should be limited to trusted neighbors independently of ordinary forwarding. By contrast, a user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port; a received BPDU triggers the configured protective response and no loop appears.
Question 642The datacom engineering team at a warehouse automation provider during a topology consistency review reviews this independent fictional networking case: A static backup path remains inactive while the primary next hop fails beyond a locally Up interface. A proposed remedy is: Use supported BFD or remote path tracking to withdraw the unusable static next hop. Which technical principle most directly supports this remedy? A VRRP group represents a virtual gateway within a specific local layer-2 segment VRRP continuity depends on end hosts and switches forwarding toward the current virtual gateway owner Physical interface state alone cannot detect all remote next-hop failures BGP best-path attributes are evaluated in a defined order; shorter AS_PATH is not always the first deciding factor ExplanationCorrect Answer C:Physical interface state alone cannot detect all remote next-hop failures. This directly explains why the corrective operation is appropriate: Use supported BFD or remote path tracking to withdraw the unusable static next hop. The observed acceptance evidence should be: An injected upstream failure withdraws the primary route and backup traffic succeeds. Incorrect Answers A:A VRRP group represents a virtual gateway within a specific local layer-2 segment. That rule governs a different situation: Two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error. Here, a static backup path remains inactive while the primary next hop fails beyond a locally Up interface. Physical interface state alone cannot detect all remote next-hop failures. B: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 static backup path remains inactive while the primary next hop fails beyond a locally Up interface. Use supported BFD or remote path tracking to withdraw the unusable static next hop. D:BGP best-path attributes are evaluated in a defined order; shorter AS_PATH is not always the first deciding factor. That rule governs a different situation: Operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. Here, a static backup path remains inactive while the primary next hop fails beyond a locally Up interface. An injected upstream failure withdraws the primary route and backup traffic succeeds.
Question 643The datacom engineering team at an airport facilities team while tracing a degraded application flow reviews this independent fictional networking case: An edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS. The team applies this remedy: Verify and correct both configured local and peer autonomous system identities. Which observation would directly demonstrate that this specific issue is resolved? The best BGP route resolves to a live next hop and data-plane probes succeed after reconvergence The BGP neighbor is Established and its accepted prefixes match the approved provider list External route views show the intended prepended announcement and measured ingress path changes when supported All clients learn the intended prefixes and remain connected after a reflector failover ExplanationCorrect Answer B:The BGP neighbor is Established and its accepted prefixes match the approved provider list. This is a directly observable check for the proposed correction: Verify and correct both configured local and peer autonomous system identities. The particular failure being investigated is: An edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS. Incorrect Answers A:When a BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link, a result such as this is useful: The best BGP route resolves to a live next hop and data-plane probes succeed after reconvergence. For the reported fault, an edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS; eBGP session establishment validates the expected remote AS during OPEN negotiation. C:An enterprise wants to influence how some external networks enter its secondary ISP, but it changes local preference inside its own AS instead. External route views show the intended prepended announcement and measured ingress path changes when supported. This observation does not prove the correction for the reported defect: An edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS. Verify and correct both configured local and peer autonomous system identities. D: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. This observation does not prove the correction for the reported defect: 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.
Question 644The datacom engineering team at an industrial safety organization during a simulated failover test reviews this independent fictional networking case: After an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed. If this issue remains unresolved, what immediate availability or security risk follows most directly? Incorrect assumptions about stub behavior can lead to unnecessary area redesign or missing external access Incorrect static metrics cause chronic congestion while faster paths remain idle Unplanned DR placement increases disruption when a fragile access node fails An asymmetric key rollover can create an avoidable routing outage during routine security maintenance ExplanationCorrect Answer B:Incorrect static metrics cause chronic congestion while faster paths remain idle. Leaving the exact fault unresolved means: After an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed. The intended response is: Recalculate and set appropriate OSPF costs for the changed link while documenting routing intent. Incorrect Answers A:An engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. In that situation, incorrect assumptions about stub behavior can lead to unnecessary area redesign or missing external access. Here instead, after an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed. OSPF shortest-path selection uses cumulative interface cost, not real-time measured bandwidth by itself. C:Unplanned DR placement increases disruption when a fragile access node fails. That risk belongs to a separate condition: A shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. Here, after an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed; recalculate and set appropriate OSPF costs for the changed link while documenting routing intent. D:An asymmetric key rollover can create an avoidable routing outage during routine security maintenance. That consequence could follow when an OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. Here, after an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed; SPF routing to the remote prefix favors the intended link and converges after the change.
Question 645The 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. If this issue remains unresolved, what immediate availability or security risk follows most directly? Incorrect group placement can create duplicate gateway ownership or unreachable hosts Local gateway survival without uplink tracking can blackhole an entire user VLAN Slow liveness detection can extend avoidable black-hole duration after link failure Oversensitive BFD can cause route flapping on healthy circuits ExplanationCorrect Answer D: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: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; failure detection speed must be balanced against scheduling jitter and false-positive risk. B:Local gateway survival without uplink tracking can blackhole an entire user VLAN. That risk belongs to a separate condition: A VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational. 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. C: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. For cloud hosting provider after an incident review, the acceptance test should show that BFD remains stable under expected CPU load and still detects real test failures within requirement.
Question 646The datacom engineering team at a public water utility during a topology consistency review reviews this independent fictional networking case: A wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller. If this issue remains unresolved, what immediate availability or security risk follows most directly? Controller single points of failure can disrupt an entire campus WLAN Uncorrected RF contention can undermine a high-density WLAN despite healthy AP links Unexpected address changes can reset voice and real-time application sessions Slow roaming can make warehouse voice and location services unusable ExplanationCorrect Answer A:Controller single points of failure can disrupt an entire campus WLAN. Leaving the exact fault unresolved means: A wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller. The intended response is: Configure supported AC discovery and high-availability mechanisms, then test controller failure. Incorrect Answers B:Uncorrected RF contention can undermine a high-density WLAN despite healthy AP links. That consequence could follow when a large lecture hall experiences low Wi-Fi throughput even with strong signal because neighboring AP radios overlap excessively on busy channels. Here, a wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller; central WLAN control architectures require planned control-plane redundancy and AP recovery behavior. C:Unexpected address changes can reset voice and real-time application sessions. That consequence could follow when a client changes IP address during normal intra-campus roaming because neighboring APs anchor it to incompatible service VLANs. Here, a wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller; configure supported AC discovery and high-availability mechanisms, then test controller failure. D:Slow roaming can make warehouse voice and location services unusable. That consequence could follow when voice handsets suffer several seconds of audio interruption after moving between APs because full authentication runs on every transition. Here, a wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller; APs register with the standby controller and client services recover within the documented bound. For public water utility during a topology consistency review, the acceptance test should show that APs register with the standby controller and client services recover within the documented bound.
Question 647The datacom engineering team at an insurance processing company while validating change-control evidence reviews this independent fictional networking case: Two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned. If this issue remains unresolved, what immediate availability or security risk follows most directly? Missing address-family negotiation leaves overlays unreachable despite a healthy BGP session Untested community handling can leak routes outside an intended operational boundary An eBGP AS mismatch blocks external route exchange at the edge Incorrect MED assumptions can cause uneven interconnect load and unpredictable ingress ExplanationCorrect Answer D:Incorrect MED assumptions can cause uneven interconnect load and unpredictable ingress. Leaving the exact fault unresolved means: Two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned. The intended response is: Review the upstream's MED handling and advertise the intended metric on comparable links. Incorrect Answers A:An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. In that situation, missing address-family negotiation leaves overlays unreachable despite a healthy BGP session. Here instead, two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned. MED is a suggestion about preferred entry into a neighboring AS and its comparison is policy dependent. B:Untested community handling can leak routes outside an intended operational boundary. That risk belongs to a separate condition: A border router tags specific prefixes but the provider does not apply the expected regional no-export treatment. Here, two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned; review the upstream's MED handling and advertise the intended metric on comparable links. C: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: Two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned. The upstream reports intended MED attributes and observed ingress tracks the agreed policy.
Question 648The datacom engineering team at a research instrumentation firm while validating change-control evidence reviews this independent fictional networking case: A LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. Which corrective engineering action most directly addresses this problem? Verify physical MTU, CLNS frame transport and IS-IS padding support along the circuit Coordinate IS-IS authentication and key rollover across the peer link Tune IS-IS DIS priority on the shared LAN and validate neighbor continuity after a planned election Repair IGMP query/reply processing and verify membership refresh timers ExplanationCorrect Answer C:Tune IS-IS DIS priority on the shared LAN and validate neighbor continuity after a planned election. This is the specific action that addresses the fictional fault: A LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. The governing technical reason is: On broadcast IS-IS circuits the DIS originates a pseudonode LSP and its election follows IS-IS priority rules. Verify by checking: The intended stable router becomes DIS and the pseudonode LSP refreshes correctly. Incorrect Answers A:IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. Verifying physical MTU, CLNS frame transport and IS-IS padding support along the circuit can respond to that condition, but it would not correct the reported fault: A LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. On broadcast IS-IS circuits the DIS originates a pseudonode LSP and its election follows IS-IS priority rules. B:When an IS-IS adjacency drops after only one of two core routers receives a new authentication key, coordinating IS-IS authentication and key rollover across the peer link could be appropriate. Here, a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. Tune IS-IS DIS priority on the shared LAN and validate neighbor continuity after a planned election. D:An access VLAN loses a multicast receiver after a quiet period because periodic IGMP membership updates never reach the upstream querier. This is where repairing IGMP query/reply processing and verifying membership refresh timers would help. By contrast, a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. The intended stable router becomes DIS and the pseudonode LSP refreshes correctly.
Question 649The datacom engineering team at a cloud hosting provider after an incident review reviews this independent fictional networking case: A BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. If this issue remains unresolved, what immediate availability or security risk follows most directly? A visible BGP prefix can still hide a black hole if forwarding recursion is stale Route target errors can isolate a tenant or leak routes into the wrong routing instance An unconstrained update surge can exhaust control-plane capacity and disrupt unrelated services Misconfigured reflection can create route loops and unstable reachability ExplanationCorrect Answer A:A visible BGP prefix can still hide a black hole if forwarding recursion is stale. Leaving the exact fault unresolved means: A BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. The intended response is: Repair next-hop recursion and underlying IGP convergence, not just the BGP session. Incorrect Answers B:Route target errors can isolate a tenant or leak routes into the wrong routing instance. That consequence could follow when tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. Here, a BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link; BGP route eligibility depends on resolvable next hops and a functioning forwarding path. C:A provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. In that situation, an unconstrained update surge can exhaust control-plane capacity and disrupt unrelated services. Here instead, a BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. Repair next-hop recursion and underlying IGP convergence, not just the BGP session. D:When an iBGP route reflected through overlapping clusters returns toward its originator unexpectedly, misconfigured reflection can create route loops and unstable reachability. The present failure is different: A BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. The best BGP route resolves to a live next hop and data-plane probes succeed after reconvergence.
Question 650The datacom engineering team at a local rail transit network while validating change-control evidence reviews this independent fictional networking case: An OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. Which corrective engineering action most directly addresses this problem? Reestablish a contiguous backbone design and use any supported temporary virtual link only with documented constraints Coordinate the configured authentication mode and active key material at both ends of the link Set OSPF interface priorities to favor a stable distribution router and perform a planned election transition Restore accurate failure detection and re-originate the affected OSPF topology information ExplanationCorrect Answer B:Coordinate the configured authentication mode and active key material at both ends of the link. This is the specific action that addresses the fictional fault: An OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. The governing technical reason is: OSPF routing exchanges must pass consistent authentication checks before neighbor state can advance. Verify by checking: Authentication error counters stop increasing and a new Full adjacency is established. Incorrect Answers A:Reestablishing a contiguous backbone design and using any supported temporary virtual link only with documented constraints is relevant when two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. It does not resolve this case: An OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. OSPF routing exchanges must pass consistent authentication checks before neighbor state can advance. C:When a shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node, setting OSPF interface priorities to favor a stable distribution router and performing a planned election transition could be appropriate. Here, an OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. Coordinate the configured authentication mode and active key material at both ends of the link. D:One router continues advertising a failed transit link because the local interface reports Up while an intermediate transport component is down. This is where restoring accurate failure detection and re-originate the affected OSPF topology information would help. By contrast, an OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. Authentication error counters stop increasing and a new Full adjacency is established.