Question 370The datacom engineering team at a university research campus while tracing a degraded application flow reviews this independent fictional networking case: A shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. Which corrective engineering action most directly addresses this problem? Mark host-facing interfaces passive while still advertising their connected subnet through the intended OSPF process Tighten the configured summary to reachable address blocks and test interarea destinations 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 C:Set OSPF interface priorities to favor a stable distribution router and perform a planned election transition. This is the specific action that addresses the fictional fault: A shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. The governing technical reason is: DR and BDR election on broadcast networks is influenced by configured interface priority and is not a direct lowest-cost path election. Verify by checking: The designated router role moves to the planned stable device and all segment peers remain Full. Incorrect Answers A:Marking host-facing interfaces passive while still advertising their connected subnet through the intended OSPF process is relevant when a user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. It does not resolve this case: A shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. DR and BDR election on broadcast networks is influenced by configured interface priority and is not a direct lowest-cost path election. B:When an area border router advertises a broad summary that includes subnets withdrawn after a site closure, tightening the configured summary to reachable address blocks and testing interarea destinations could be appropriate. Here, a shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. Set OSPF interface priorities to favor a stable distribution router and perform a planned election transition. D:One router continues advertising a failed transit link because the local interface reports Up while an intermediate transport component is down. Restoring accurate failure detection and re-originate the affected OSPF topology information can respond to that condition, but it would not correct the reported fault: A shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. The designated router role moves to the planned stable device and all segment peers remain Full.
Question 371The datacom engineering team at a retail banking network as part of an acceptance test reviews this independent fictional networking case: Policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. The team applies this remedy: Add health-aware policy-path handling or withdraw the policy on next-hop failure. Which observation would directly demonstrate that this specific issue is resolved? Route advertisements stop oscillating and correct original route sources remain stable Bidirectional trace confirms both directions traverse a consistent stateful inspection path Both switches report the same region identity and expected instance topology Policy test traffic fails over to the approved inspection path and maintains documented controls ExplanationCorrect Answer D:Policy test traffic fails over to the approved inspection path and maintains documented controls. This is a directly observable check for the proposed correction: Add health-aware policy-path handling or withdraw the policy on next-hop failure. The particular failure being investigated is: Policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. Incorrect Answers A:When two redistribution points repeatedly re-inject learned routes between OSPF and another IGP and churn route entries, a result such as this is useful: Route advertisements stop oscillating and correct original route sources remain stable. For the reported fault, policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path; PBR intentionally overrides ordinary routing and can therefore preserve a failed forwarding decision. B:Bidirectional trace confirms both directions traverse a consistent stateful inspection path. This check belongs to a stateful firewall intermittently drops responses after equal-cost routing spreads the forward and return flows across unrelated inspection nodes. The actual defect is different: Policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. Add health-aware policy-path handling or withdraw the policy on next-hop failure. C:Both switches report the same region identity and expected instance topology. This check belongs to two switches intended in one MSTP region behave as if separated by a regional boundary after an unnoticed configuration edit. The actual defect is different: Policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. An unchecked PBR next hop can isolate selected users while general connectivity appears normal.
Question 372The datacom engineering team at a distribution warehouse group during a simulated failover test reviews this independent fictional networking case: Two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree. The team applies this remedy: Align the protected subnet selectors and routing for the authorized tunnel traffic. Which observation would directly demonstrate that this specific issue is resolved? Each tenant sees only approved VRF routes and prohibited cross-tenant probes fail Guest-originated SSH probes are rejected while approved administrative access continues Tunnel SA counters increase for the approved subnet and remote application traffic succeeds Unauthorized control attempts are rejected while approved peers remain stable ExplanationCorrect Answer C:Tunnel SA counters increase for the approved subnet and remote application traffic succeeds. This is a directly observable check for the proposed correction: Align the protected subnet selectors and routing for the authorized tunnel traffic. The particular failure being investigated is: Two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree. Incorrect Answers A:When traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance, a result such as this is useful: Each tenant sees only approved VRF routes and prohibited cross-tenant probes fail. For the reported fault, two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree; IPsec security associations must cover compatible protected flows even when IKE negotiation is successful. B:Guest-originated SSH probes are rejected while approved administrative access continues. This check belongs to a router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. The actual defect is different: Two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree. Align the protected subnet selectors and routing for the authorized tunnel traffic. D:Unauthorized control attempts are rejected while approved peers remain stable. This check belongs to a provider-facing interface accepts unexpected routing-control connections from an unapproved adjacent host. The actual defect is different: Two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree. A superficially Up IKE session can conceal complete loss of protected service traffic.
Question 373The datacom engineering team at a pharmaceutical testing firm after a planned hardware refresh 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. Which corrective engineering action most directly addresses this problem? Verify physical MTU, CLNS frame transport and IS-IS padding support along the circuit Compare sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization 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 ExplanationCorrect Answer A:Verify physical MTU, CLNS frame transport and IS-IS padding support along the circuit. This is the specific action that addresses the fictional fault: IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. The governing technical reason is: IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic. Verify by checking: IS-IS hellos and LSP floods succeed and the remote LSDB converges. Incorrect Answers B:When core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized, comparing sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization could be appropriate. 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. C:Coordinating IS-IS authentication and key rollover across the peer link is relevant when an IS-IS adjacency drops after only one of two core routers receives a new authentication key. It does not resolve this case: 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. D:A LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. Tuning IS-IS DIS priority on the shared LAN and validating neighbor continuity after a planned election can respond to that condition, but it would not correct the reported fault: 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 374The datacom engineering team at a call center outsourcer after a planned hardware refresh reviews this independent fictional networking case: An engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. Which corrective engineering action most directly addresses this problem? Restore accurate failure detection and re-originate the affected OSPF topology information Validate stub-area configuration and ensure the ABR advertises the intended default route into the area 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 ExplanationCorrect Answer B:Validate stub-area configuration and ensure the ABR advertises the intended default route into the area. This is the specific action that addresses the fictional fault: An engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. The governing technical reason is: Standard stub areas suppress Type-5 external LSAs and normally rely on an ABR-provided default for external reachability. Verify by checking: The ABR default route appears in the stub area and external destinations remain reachable. Incorrect Answers A:One router continues advertising a failed transit link because the local interface reports Up while an intermediate transport component is down. Restoring accurate failure detection and re-originate the affected OSPF topology information can respond to that condition, but it would not correct the reported fault: An engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. Standard stub areas suppress Type-5 external LSAs and normally rely on an ABR-provided default for external reachability. C: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, an engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. Validate stub-area configuration and ensure the ABR advertises the intended default route into the area. D:Aligning the totally stub area behavior at the ABR and verifying the intended default-based forwarding is relevant when branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. It does not resolve this case: An engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. The ABR default route appears in the stub area and external destinations remain reachable.
Question 375The datacom engineering team at a regional health network during a controlled network cutover reviews this independent fictional networking case: A provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. If this issue remains unresolved, what immediate availability or security risk follows most directly? An eBGP AS mismatch blocks external route exchange at the edge A visible BGP prefix can still hide a black hole if forwarding recursion is stale An unconstrained update surge can exhaust control-plane capacity and disrupt unrelated services Partial iBGP distribution can hide routes from only some leaf devices ExplanationCorrect Answer C:An unconstrained update surge can exhaust control-plane capacity and disrupt unrelated services. Leaving the exact fault unresolved means: A provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. The intended response is: Set an appropriate maximum-prefix threshold and test the negotiated recovery behavior. Incorrect Answers A:An edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS. In that situation, an eBGP AS mismatch blocks external route exchange at the edge. Here instead, a provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. Prefix-limit controls can bound routing state growth when a neighbor violates expected route scale. B:A visible BGP prefix can still hide a black hole if forwarding recursion is stale. That consequence could follow when a BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. Here, a provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set; set an appropriate maximum-prefix threshold and test the negotiated recovery behavior. D:Partial iBGP distribution can hide routes from only some leaf devices. That consequence could follow when a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Here, a provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set; the limit activates predictably in staging and the router protects its route memory during an oversized update.
Question 376The 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. The team applies this remedy: Coordinate the configured authentication mode and active key material at both ends of the link. Which observation would directly demonstrate that this specific issue is resolved? Authentication error counters stop increasing and a new Full adjacency is established Remote OSPF routers receive the summary and reach all intended attached external subnets Packet captures show no OSPF Hellos on the host VLAN while the prefix remains in OSPF routes ABRs display correct backbone reachability and previously missing interarea routes appear ExplanationCorrect Answer A:Authentication error counters stop increasing and a new Full adjacency is established. This is a directly observable check for the proposed correction: Coordinate the configured authentication mode and active key material at both ends of the link. The particular failure being investigated is: An OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. Incorrect Answers B:An ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. Remote OSPF routers receive the summary and reach all intended attached external subnets. This observation does not prove the correction for the reported defect: 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:A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. Packet captures show no OSPF Hellos on the host VLAN while the prefix remains in OSPF routes. This observation does not prove the correction for the reported defect: 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:When two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent, a result such as this is useful: ABRs display correct backbone reachability and previously missing interarea routes appear. For the reported fault, an OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only; an asymmetric key rollover can create an avoidable routing outage during routine security maintenance.
Question 377The datacom engineering team at a maritime terminal after a monitored link change reviews this independent fictional networking case: A campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services. The team applies this remedy: Restore dual-active detection or an approved split-brain suppression mechanism and test isolation behavior. Which observation would directly demonstrate that this specific issue is resolved? Controlled heartbeat loss leaves only one authorized active forwarding role with no duplicate gateway responses The alternate link transitions to forwarding after a controlled primary failure without sustained loop The intended distribution switch is root and port roles converge as planned Region digest and per-VLAN instance port roles match at the neighbors ExplanationCorrect Answer A:Controlled heartbeat loss leaves only one authorized active forwarding role with no duplicate gateway responses. This is a directly observable check for the proposed correction: Restore dual-active detection or an approved split-brain suppression mechanism and test isolation behavior. The particular failure being investigated is: A campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services. Incorrect Answers B:A redundant access uplink stays blocked even after the active link fails because the switch has not converged its port roles correctly. The alternate link transitions to forwarding after a controlled primary failure without sustained loop. This observation does not prove the correction for the reported defect: A campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services. Cluster heartbeat failures require independent mechanisms to avoid concurrent active ownership of the same logical service. C:A low-capacity access switch becomes the spanning-tree root because its bridge priority was left lower than the distribution pair. The intended distribution switch is root and port roles converge as planned. This observation does not prove the correction for the reported defect: A campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services. Restore dual-active detection or an approved split-brain suppression mechanism and test isolation behavior. D:Region digest and per-VLAN instance port roles match at the neighbors. This check belongs to traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. The actual defect is different: A campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services. Split-brain ownership can cause MAC flaps and severe layer-2 instability.
Question 378The datacom engineering team at a library district network after a planned hardware refresh reviews this independent fictional networking case: A new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. If this issue remains unresolved, what immediate availability or security risk follows most directly? Split key deployment can sever a core routing domain even when the circuit is physically healthy Incorrect assumptions about IP reachability can mask unformed IS-IS adjacencies Early transit selection can blackhole traffic during control-plane recovery Mixed metric interpretation can produce route divergence and unstable path choices ExplanationCorrect Answer D:Mixed metric interpretation can produce route divergence and unstable path choices. Leaving the exact fault unresolved means: A new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. The intended response is: Align a supported wide-metric style before deploying the higher-cost topology. Incorrect Answers A:Split key deployment can sever a core routing domain even when the circuit is physically healthy. That consequence could follow when an IS-IS adjacency drops after only one of two core routers receives a new authentication key. Here, a new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles; IS-IS metric encoding capability must be consistent enough for all participating routers to calculate intended paths. B:When IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass, incorrect assumptions about IP reachability can mask unformed IS-IS adjacencies. The present failure is different: A new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. Align a supported wide-metric style before deploying the higher-cost topology. C:Early transit selection can blackhole traffic during control-plane recovery. That risk belongs to a separate condition: A router recovering from reboot begins attracting transit traffic before its route state is ready. Here, a new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles; each participating router reports the intended metric and selects consistent next hops.
Question 379The 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. Which corrective engineering action most directly addresses this problem? Align VLAN-to-instance mappings and regional parameters across the MST region Apply supported BPDU protection at legitimate edge ports and investigate the unexpected bridge connection Rebalance cross-member uplinks and validate supported stack switchover and master recovery Set deliberate RSTP root and backup-root bridge priorities on stable distribution switches ExplanationCorrect Answer B:Apply supported BPDU protection at legitimate edge ports and investigate the unexpected bridge connection. This is the specific action that addresses the fictional fault: A user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port. The governing technical reason is: Edge-port fast transition should not make unauthorized bridge participation safe. Verify by checking: A received BPDU triggers the configured protective response and no loop appears. Incorrect Answers A:When traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances, aligning VLAN-to-instance mappings and regional parameters across the MST region could be appropriate. Here, 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:When a stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed, rebalancing cross-member uplinks and validating supported stack switchover and master recovery could be appropriate. Here, 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:A low-capacity access switch becomes the spanning-tree root because its bridge priority was left lower than the distribution pair. This is where setting deliberate RSTP root and backup-root bridge priorities on stable distribution switches would help. 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 380The datacom engineering team at a cross-border logistics provider after a monitored link change reviews this independent fictional networking case: A new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. Which corrective engineering action most directly addresses this problem? Set compatible IS-IS circuit levels consistent with the core design Apply a controlled IS-IS overload period during startup and remove it after routing readiness Align a supported wide-metric style before deploying the higher-cost topology Compare sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization ExplanationCorrect Answer C:Align a supported wide-metric style before deploying the higher-cost topology. This is the specific action that addresses the fictional fault: A new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. The governing technical reason is: IS-IS metric encoding capability must be consistent enough for all participating routers to calculate intended paths. Verify by checking: Each participating router reports the intended metric and selects consistent next hops. Incorrect Answers A: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 new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. IS-IS metric encoding capability must be consistent enough for all participating routers to calculate intended paths. B:A router recovering from reboot begins attracting transit traffic before its route state is ready. This is where applying a controlled IS-IS overload period during startup and removing it after routing readiness would help. By contrast, a new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. Align a supported wide-metric style before deploying the higher-cost topology. D:When core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized, comparing sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization could be appropriate. Here, a new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. Each participating router reports the intended metric and selects consistent next hops.