Question 410The 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. A proposed remedy is: Align a supported wide-metric style before deploying the higher-cost topology. Which technical principle most directly supports this remedy? IS-IS metric encoding capability must be consistent enough for all participating routers to calculate intended paths IS-IS adjacencies require at least one common enabled routing level IS-IS protocol authentication must match across neighbor exchanges to maintain trusted adjacencies The IS-IS overload bit discourages transit use of an incompletely initialized router ExplanationCorrect Answer A:IS-IS metric encoding capability must be consistent enough for all participating routers to calculate intended paths. This directly explains why the corrective operation is appropriate: Align a supported wide-metric style before deploying the higher-cost topology. The observed acceptance evidence should be: Each participating router reports the intended metric and selects consistent next hops. Incorrect Answers B:A transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2. IS-IS adjacencies require at least one common enabled routing level. The current condition differs: 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. C:When 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. 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:The IS-IS overload bit discourages transit use of an incompletely initialized router. That principle is relevant when 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 411The datacom engineering team at a university hospital during a network security audit reviews this independent fictional networking case: A static backup path remains inactive while the primary next hop fails beyond a locally Up interface. Which corrective engineering action most directly addresses this problem? Enable supported BFD tracking for the OSPF adjacency and validate timer compatibility Track external-uplink health and reduce VRRP priority enough for the healthy backup to take over Use supported BFD or remote path tracking to withdraw the unusable static next hop Check supported BFD modes and mutually acceptable timer negotiation before coupling routing failover ExplanationCorrect Answer C:Use supported BFD or remote path tracking to withdraw the unusable static next hop. This is the specific action that addresses the fictional fault: A static backup path remains inactive while the primary next hop fails beyond a locally Up interface. The governing technical reason is: Physical interface state alone cannot detect all remote next-hop failures. Verify by checking: An injected upstream failure withdraws the primary route and backup traffic succeeds. Incorrect Answers A:When OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection, enabling supported BFD tracking for the OSPF adjacency and validating timer compatibility could be appropriate. 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 VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational. Tracking external-uplink health and reduce VRRP priority enough for the healthy backup to take over can respond to that condition, but it would not correct the reported fault: 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:When two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior, checking supported BFD modes and mutually acceptable timer negotiation before coupling routing failover could be appropriate. 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 412The datacom engineering team at an automotive parts manufacturer as part of an acceptance 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. A proposed remedy is: Recalculate and set appropriate OSPF costs for the changed link while documenting routing intent. Which technical principle most directly supports this remedy? DR and BDR election on broadcast networks is influenced by configured interface priority and is not a direct lowest-cost path election OSPF shortest-path selection uses cumulative interface cost, not real-time measured bandwidth by itself OSPF E1 includes internal cost to the ASBR whereas E2 primarily compares the advertised external cost Aggregating interarea advertisements can reduce control-plane state but must not capture unreachable space ExplanationCorrect Answer B:OSPF shortest-path selection uses cumulative interface cost, not real-time measured bandwidth by itself. This directly explains why the corrective operation is appropriate: Recalculate and set appropriate OSPF costs for the changed link while documenting routing intent. The observed acceptance evidence should be: SPF routing to the remote prefix favors the intended link and converges after the change. 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. DR and BDR election on broadcast networks is influenced by configured interface priority and is not a direct lowest-cost path election. The current condition differs: 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:A remote site incorrectly chooses an external OSPF route that ignores material internal distance to competing exit points. OSPF E1 includes internal cost to the ASBR whereas E2 primarily compares the advertised external cost. The current condition differs: 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:Several closely related access prefixes create unnecessary interarea LSA churn because no ABR aggregation is applied. Aggregating interarea advertisements can reduce control-plane state but must not capture unreachable space. The current condition differs: 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 413The datacom engineering team at a hospital imaging provider during a controlled network cutover reviews this independent fictional networking case: A receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. If this issue remains unresolved, what immediate availability or security risk follows most directly? Unbounded distribution may waste WAN capacity and expose internal streams Group delivery becomes erratic when receiver membership is allowed to age silently Misapplied ASM behavior can select an unintended stream source and undermine access expectations Uncontrolled multicast flooding consumes bandwidth and can overload unrelated endpoints ExplanationCorrect Answer C:Misapplied ASM behavior can select an unintended stream source and undermine access expectations. Leaving the exact fault unresolved means: A receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. The intended response is: Configure compatible SSM group ranges and source-aware membership signalling. Incorrect Answers A:Unbounded distribution may waste WAN capacity and expose internal streams. That consequence could follow when a training-video multicast group begins leaking beyond its approved distribution region after a transport upgrade. Here, a receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state; source-specific multicast forwarding is tied to a particular source and group rather than RP-based ASM discovery. B:When a VLAN with multicast hosts has no functioning IGMP querier after its original gateway moves away, group delivery becomes erratic when receiver membership is allowed to age silently. The present failure is different: A receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. Configure compatible SSM group ranges and source-aware membership signalling. D:A switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built. In that situation, uncontrolled multicast flooding consumes bandwidth and can overload unrelated endpoints. Here instead, a receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. The receiver joins the intended source/group pair and cannot accidentally switch to a different sender.
Question 414The 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. A proposed remedy is: Set OSPF interface priorities to favor a stable distribution router and perform a planned election transition. Which technical principle most directly supports this remedy? DR and BDR election on broadcast networks is influenced by configured interface priority and is not a direct lowest-cost path election OSPF interarea routing depends on backbone connectivity through area 0 A passive OSPF interface can advertise its prefix without attempting routing adjacencies on that link ASBR route aggregation reduces external advertisements without replacing ordinary ABR interarea summarization ExplanationCorrect Answer A:DR and BDR election on broadcast networks is influenced by configured interface priority and is not a direct lowest-cost path election. This directly explains why the corrective operation is appropriate: Set OSPF interface priorities to favor a stable distribution router and perform a planned election transition. The observed acceptance evidence should be: The designated router role moves to the planned stable device and all segment peers remain Full. Incorrect Answers B:OSPF interarea routing depends on backbone connectivity through area 0. That rule governs a different situation: Two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. Here, 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. C:A passive OSPF interface can advertise its prefix without attempting routing adjacencies on that link. That rule governs a different situation: A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. 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:When an ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables, ASBR route aggregation reduces external advertisements without replacing ordinary ABR interarea summarization. By contrast, 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 415The 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. 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 An asymmetric key rollover can create an avoidable routing outage during routine security maintenance A partial OSPF exchange leaves inconsistent topology knowledge and traffic black holes ExplanationCorrect Answer A:Incorrect assumptions about stub behavior can lead to unnecessary area redesign or missing external access. Leaving the exact fault unresolved means: An engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. The intended response is: Validate stub-area configuration and ensure the ABR advertises the intended default route into the area. Incorrect Answers B:Incorrect static metrics cause chronic congestion while faster paths remain idle. That consequence could follow when after an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed. Here, 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:An OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. In that situation, an asymmetric key rollover can create an avoidable routing outage during routine security maintenance. Here instead, 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:When OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change, a partial OSPF exchange leaves inconsistent topology knowledge and traffic black holes. The present failure is different: 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 416The datacom engineering team at a wholesale market association while tracing a degraded application flow reviews this independent fictional networking case: Traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. Which corrective engineering action most directly addresses this problem? Align VLAN-to-instance mappings and regional parameters across the MST region 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 Inspect RSTP role/state exchanges and fix the inconsistent neighbor port configuration ExplanationCorrect Answer A:Align VLAN-to-instance mappings and regional parameters across the MST region. This is the specific action that addresses the fictional fault: Traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. The governing technical reason is: MSTP topology behavior is per instance and consistent VLAN mapping is necessary for predictable forwarding. Verify by checking: Region digest and per-VLAN instance port roles match at the neighbors. Incorrect Answers B: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 can respond to that condition, but it would not correct the reported fault: Traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. MSTP topology behavior is per instance and consistent VLAN mapping is necessary for predictable forwarding. C:When a low-capacity access switch becomes the spanning-tree root because its bridge priority was left lower than the distribution pair, setting deliberate RSTP root and backup-root bridge priorities on stable distribution switches could be appropriate. Here, traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. Align VLAN-to-instance mappings and regional parameters across the MST region. D:A redundant access uplink stays blocked even after the active link fails because the switch has not converged its port roles correctly. This is where inspecting RSTP role/state exchanges and fixing the inconsistent neighbor port configuration would help. By contrast, traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. Region digest and per-VLAN instance port roles match at the neighbors.
Question 417The datacom engineering team at an engineering consultancy during a controlled network cutover reviews this independent fictional networking case: Two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. Which corrective engineering action most directly addresses this problem? Apply explicit prefix-length-aware export policy limited to authorized aggregate space Assign route distinguishers suitable for creating unique originating VPN route identifiers Enable and validate the correct EVPN address-family capability and policy on both peers Verify and correct both configured local and peer autonomous system identities ExplanationCorrect Answer B:Assign route distinguishers suitable for creating unique originating VPN route identifiers. This is the specific action that addresses the fictional fault: Two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. The governing technical reason is: Route distinguishers distinguish otherwise identical VPN address advertisements; they do not themselves control import permission. Verify by checking: EVPN control-plane entries retain unique per-origin VPN identifiers and remote paths coexist. Incorrect Answers A: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, two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. Route distinguishers distinguish otherwise identical VPN address advertisements; they do not themselves control import permission. C:An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. Enabling and validating the correct EVPN address-family capability and policy on both peers can respond to that condition, but it would not correct the reported fault: Two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. Assign route distinguishers suitable for creating unique originating VPN route identifiers. D:An edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS. This is where verifying and correcting both configured local and peer autonomous system identities would help. By contrast, two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. EVPN control-plane entries retain unique per-origin VPN identifiers and remote paths coexist.
Question 418The datacom engineering team at a hospital imaging provider during a controlled network cutover reviews this independent fictional networking case: Two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses. If this issue remains unresolved, what immediate availability or security risk follows most directly? A valid-looking iBGP route may be unusable when the external next hop is unresolved An unrestricted export policy may leak internal infrastructure addresses beyond the organization Partial iBGP distribution can hide routes from only some leaf devices Uncontrolled source interface selection causes intermittent neighbor resets after link changes ExplanationCorrect Answer D:Uncontrolled source interface selection causes intermittent neighbor resets after link changes. Leaving the exact fault unresolved means: Two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses. The intended response is: Configure the intended loopback update source and ensure loopback reachability across the IGP. Incorrect Answers A:A valid-looking iBGP route may be unusable when the external next hop is unresolved. That risk belongs to a separate condition: An iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally. Here, two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses; BGP neighbor identity must align with the configured source and destination transport addresses. B:An unrestricted export policy may leak internal infrastructure addresses beyond the organization. That consequence could follow when an accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. Here, two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses; configure the intended loopback update source and ensure loopback reachability across the IGP. 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, two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses. Session source addresses match loopbacks and both peers establish consistently.
Question 419The datacom engineering team at a consumer electronics manufacturer as part of an acceptance test reviews this independent fictional networking case: A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. The team applies this remedy: Mark host-facing interfaces passive while still advertising their connected subnet through the intended OSPF process. Which observation would directly demonstrate that this specific issue is resolved? Remote OSPF routers receive the summary and reach all intended attached external subnets Database description exchange completes and the OSPF neighbor reaches Full state Packet captures show no OSPF Hellos on the host VLAN while the prefix remains in OSPF routes Interarea advertisements cover only approved reachable blocks and traced flows reach valid hosts ExplanationCorrect Answer C:Packet captures show no OSPF Hellos on the host VLAN while the prefix remains in OSPF routes. This is a directly observable check for the proposed correction: Mark host-facing interfaces passive while still advertising their connected subnet through the intended OSPF process. The particular failure being investigated is: A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. Incorrect Answers A:When an ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables, a result such as this is useful: Remote OSPF routers receive the summary and reach all intended attached external subnets. For the reported fault, a user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance; a passive OSPF interface can advertise its prefix without attempting routing adjacencies on that link. B:Database description exchange completes and the OSPF neighbor reaches Full state. This check belongs to OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change. The actual defect is different: A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. Mark host-facing interfaces passive while still advertising their connected subnet through the intended OSPF process. D:Interarea advertisements cover only approved reachable blocks and traced flows reach valid hosts. This check belongs to an area border router advertises a broad summary that includes subnets withdrawn after a site closure. The actual defect is different: A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. Active routing hellos on user ports expand an unnecessary adjacency attack surface.
Question 420The datacom engineering team at an engineering consultancy during a controlled network cutover reviews this independent fictional networking case: A stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed. 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 Restore dual-active detection or an approved split-brain suppression mechanism and test isolation behavior Rebalance cross-member uplinks and validate supported stack switchover and master recovery ExplanationCorrect Answer D:Rebalance cross-member uplinks and validate supported stack switchover and master recovery. This is the specific action that addresses the fictional fault: A stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed. The governing technical reason is: Stacking presents multiple switches as a logical system but failure domains still depend on physical member connectivity. Verify by checking: A controlled member failure leaves dual-homed access services reachable and stack roles recover. Incorrect Answers A: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 can respond to that condition, but it would not correct the reported fault: A stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed. Stacking presents multiple switches as a logical system but failure domains still depend on physical member connectivity. B:A user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port. Applying supported BPDU protection at legitimate edge ports and investigate the unexpected bridge connection can respond to that condition, but it would not correct the reported fault: A stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed. Rebalance cross-member uplinks and validate supported stack switchover and master recovery. C:When a campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services, restoring dual-active detection or an approved split-brain suppression mechanism and testing isolation behavior could be appropriate. Here, a stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed. A controlled member failure leaves dual-homed access services reachable and stack roles recover.