Question 480The datacom engineering team at an energy distribution business while tracing a degraded application flow reviews this independent fictional networking case: An ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. Which corrective engineering action most directly addresses this problem? Coordinate the configured authentication mode and active key material at both ends of the link Tighten the configured summary to reachable address blocks and test interarea destinations Check Type-7 external origination and ABR translation toward Type-5 reachability in the backbone Apply appropriately scoped external prefix summarization at the originating ASBR ExplanationCorrect Answer D:Apply appropriately scoped external prefix summarization at the originating ASBR. This is the specific action that addresses the fictional fault: An ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. The governing technical reason is: ASBR route aggregation reduces external advertisements without replacing ordinary ABR interarea summarization. Verify by checking: Remote OSPF routers receive the summary and reach all intended attached external subnets. Incorrect Answers A:An OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. This is where coordinating the configured authentication mode and active key material at both ends of the link would help. By contrast, 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. B:An area border router advertises a broad summary that includes subnets withdrawn after a site closure. This is where tightening the configured summary to reachable address blocks and testing interarea destinations would help. By contrast, an ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. Apply appropriately scoped external prefix summarization at the originating ASBR. C: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, 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.
Question 481The datacom engineering team at a government service campus after a monitored link change reviews this independent fictional networking case: A remote site incorrectly chooses an external OSPF route that ignores material internal distance to competing exit points. A proposed remedy is: Evaluate E1 versus E2 external metric behavior and configure the intended metric type consistently. Which technical principle most directly supports this remedy? NSSA uses Type-7 external LSAs inside its area and relies on translation at an appropriate border device OSPF E1 includes internal cost to the ASBR whereas E2 primarily compares the advertised external cost DR and BDR election on broadcast networks is influenced by configured interface priority and is not a direct lowest-cost path election OSPF adjacency establishment requires compatible hello parameters on the neighbor-facing interfaces ExplanationCorrect Answer B:OSPF E1 includes internal cost to the ASBR whereas E2 primarily compares the advertised external cost. This directly explains why the corrective operation is appropriate: Evaluate E1 versus E2 external metric behavior and configure the intended metric type consistently. The observed acceptance evidence should be: Route choice matches documented exit intent when internal path costs differ. Incorrect Answers A:When an NSSA branch redistributes a local static route that fails to appear as expected outside the NSSA, NSSA uses Type-7 external LSAs inside its area and relies on translation at an appropriate border device. By contrast, 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. C:When 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. By contrast, a remote site incorrectly chooses an external OSPF route that ignores material internal distance to competing exit points; evaluate E1 versus E2 external metric behavior and configure the intended metric type consistently. D:When two directly connected OSPF routers see each other in packets but never establish a neighbor because their Hello and Dead timers differ, OSPF adjacency establishment requires compatible hello parameters on the neighbor-facing interfaces. By contrast, a remote site incorrectly chooses an external OSPF route that ignores material internal distance to competing exit points; route choice matches documented exit intent when internal path costs differ.
Question 482The 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. A proposed remedy is: Validate stub-area configuration and ensure the ABR advertises the intended default route into the area. Which technical principle most directly supports this remedy? ABR summaries reduce LSDB size but overbroad summaries can attract packets for nonexistent destinations NSSA uses Type-7 external LSAs inside its area and relies on translation at an appropriate border device Standard stub areas suppress Type-5 external LSAs and normally rely on an ABR-provided default for external reachability SPF can only remove unusable paths promptly after their topology state is correctly detected and flooded ExplanationCorrect Answer C:Standard stub areas suppress Type-5 external LSAs and normally rely on an ABR-provided default for external reachability. This directly explains why the corrective operation is appropriate: Validate stub-area configuration and ensure the ABR advertises the intended default route into the area. The observed acceptance evidence should be: The ABR default route appears in the stub area and external destinations remain reachable. Incorrect Answers A: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. The current condition differs: 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. B:NSSA uses Type-7 external LSAs inside its area and relies on translation at an appropriate border device. That rule governs a different situation: An NSSA branch redistributes a local static route that fails to appear as expected outside the NSSA. 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:One router continues advertising a failed transit link because the local interface reports Up while an intermediate transport component is down. SPF can only remove unusable paths promptly after their topology state is correctly detected and flooded. The current condition differs: 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 483The datacom engineering team at a maritime terminal after a monitored link change reviews this independent fictional networking case: A branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. Which corrective engineering action most directly addresses this problem? Compare candidate prefixes and remove the unintended more-specific route before changing global route preferences Provide a resolvable route to the next hop or replace it with the verified directly reachable next hop Inspect interface and forwarding-plane readiness, then restore the failed forwarding-table synchronization before accepting traffic Apply appropriately scoped external prefix summarization at the originating ASBR ExplanationCorrect Answer A:Compare candidate prefixes and remove the unintended more-specific route before changing global route preferences. This is the specific action that addresses the fictional fault: A branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. The governing technical reason is: Longest-prefix matching precedes route preference comparisons between routes of different mask lengths. Verify by checking: The routing table and packet-path trace select the intended prefix and next hop. Incorrect Answers B:A static route is configured to a next-hop address that is absent from the local routing table and never becomes active. This is where providing a resolvable route to the next hop or replace it with the verified directly reachable next hop would help. By contrast, a branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. Longest-prefix matching precedes route preference comparisons between routes of different mask lengths. C:Newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries. Inspecting interface and forwarding-plane readiness, then restore the failed forwarding-table synchronization before accepting traffic can respond to that condition, but it would not correct the reported fault: A branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. Compare candidate prefixes and remove the unintended more-specific route before changing global route preferences. For maritime terminal after a monitored link change, the acceptance test should show that the routing table and packet-path trace select the intended prefix and next hop. D:An ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. Applying appropriately scoped external prefix summarization at the originating ASBR can respond to that condition, but it would not correct the reported fault: A branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. The routing table and packet-path trace select the intended prefix and next hop.
Question 484The datacom engineering team at a sports event venue during a topology consistency review reviews this independent fictional networking case: An IS-IS adjacency drops after only one of two core routers receives a new authentication key. A proposed remedy is: Coordinate IS-IS authentication and key rollover across the peer link. Which technical principle most directly supports this remedy? IS-IS protocol authentication must match across neighbor exchanges to maintain trusted adjacencies On broadcast IS-IS circuits the DIS originates a pseudonode LSP and its election follows IS-IS priority rules IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic Level-1 IS-IS neighbors must belong to a compatible area while Level-2 can connect areas ExplanationCorrect Answer A:IS-IS protocol authentication must match across neighbor exchanges to maintain trusted adjacencies. This directly explains why the corrective operation is appropriate: Coordinate IS-IS authentication and key rollover across the peer link. The observed acceptance evidence should be: Authentication failures cease and level-appropriate neighbor state returns Up. Incorrect Answers B: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. The current condition differs: 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. C: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, an IS-IS adjacency drops after only one of two core routers receives a new authentication key; coordinate IS-IS authentication and key rollover across the peer link. D:Level-1 IS-IS neighbors must belong to a compatible area while Level-2 can connect areas. That principle is relevant when two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses. Here, an IS-IS adjacency drops after only one of two core routers receives a new authentication key; authentication failures cease and level-appropriate neighbor state returns Up.
Question 485The datacom engineering team at a public water utility during a topology consistency review reviews this independent fictional networking case: A firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. If this issue remains unresolved, what immediate availability or security risk follows most directly? A superficially Up IKE session can conceal complete loss of protected service traffic A NAT-only repair can leave return traffic asymmetric and business sessions broken Improper routing-instance assignment can expose one customer's traffic to another A missing fallback can prevent safe restoration during an identity infrastructure incident ExplanationCorrect Answer B:A NAT-only repair can leave return traffic asymmetric and business sessions broken. Leaving the exact fault unresolved means: A firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. The intended response is: Validate NAT rule matching and the effective route lookup for the translated flow. Incorrect Answers A:When 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. The present failure is different: A firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. NAT changes packet addressing, but traffic still requires a correct routed egress and return path. C:When traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance, improper routing-instance assignment can expose one customer's traffic to another. The present failure is different: A firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. Validate NAT rule matching and the effective route lookup for the translated flow. D:A missing fallback can prevent safe restoration during an identity infrastructure incident. That risk belongs to a separate condition: A campus authentication server becomes unreachable and network admins cannot access devices during an outage. Here, a firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway; session/NAT records and bidirectional traces show the intended translated tuple and next hop.
Question 486The datacom engineering team at an airport facilities team while tracing a degraded application flow reviews this independent fictional networking case: OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change. The team applies this remedy: Reconcile the actual link MTU and OSPF database exchange compatibility before retransmitting LSAs. Which observation would directly demonstrate that this specific issue is resolved? Authentication error counters stop increasing and a new Full adjacency is established Database description exchange completes and the OSPF neighbor reaches Full state Neighbor state reaches Full and the link appears in both area LSDB views SPF routing to the remote prefix favors the intended link and converges after the change ExplanationCorrect Answer B:Database description exchange completes and the OSPF neighbor reaches Full state. This is a directly observable check for the proposed correction: Reconcile the actual link MTU and OSPF database exchange compatibility before retransmitting LSAs. The particular failure being investigated is: OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change. Incorrect Answers A: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. This observation does not prove the correction for the reported defect: OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change. MTU incompatibility can disrupt OSPF database description negotiation and leave neighbors partially adjacent. C:Neighbor state reaches Full and the link appears in both area LSDB views. That result could validate a repair when two routers on the same Ethernet segment remain stuck without OSPF adjacency because one interface belongs to area 0 and the other to area 10. Here, OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change; reconcile the actual link MTU and OSPF database exchange compatibility before retransmitting LSAs. D:SPF routing to the remote prefix favors the intended link and converges after the change. That result could validate a repair when after an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed. Here, 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.
Question 487The datacom engineering team at an insurance processing company while validating change-control evidence reviews this independent fictional networking case: A redundant access uplink stays blocked even after the active link fails because the switch has not converged its port roles correctly. The team applies this remedy: Inspect RSTP role/state exchanges and fix the inconsistent neighbor port configuration. Which observation would directly demonstrate that this specific issue is resolved? 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 A controlled member failure leaves dual-homed access services reachable and stack roles recover Controlled heartbeat loss leaves only one authorized active forwarding role with no duplicate gateway responses ExplanationCorrect Answer A:The alternate link transitions to forwarding after a controlled primary failure without sustained loop. This is a directly observable check for the proposed correction: Inspect RSTP role/state exchanges and fix the inconsistent neighbor port configuration. The particular failure being investigated is: A redundant access uplink stays blocked even after the active link fails because the switch has not converged its port roles correctly. Incorrect Answers B:The intended distribution switch is root and port roles converge as planned. That result could validate a repair when a low-capacity access switch becomes the spanning-tree root because its bridge priority was left lower than the distribution pair. Here, 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. C:A controlled member failure leaves dual-homed access services reachable and stack roles recover. This check belongs to a stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed. The actual defect is different: A redundant access uplink stays blocked even after the active link fails because the switch has not converged its port roles correctly. Inspect RSTP role/state exchanges and fix the inconsistent neighbor port configuration. D:A campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services. Controlled heartbeat loss leaves only one authorized active forwarding role with no duplicate gateway responses. This observation does not prove the correction for the reported defect: A redundant access uplink stays blocked even after the active link fails because the switch has not converged its port roles correctly. Failure of rapid transition turns redundant cabling into an outage rather than resilience.
Question 488The datacom engineering team at a pharmaceutical testing firm after a planned hardware refresh reviews this independent fictional networking case: A branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. The team applies this remedy: Compare candidate prefixes and remove the unintended more-specific route before changing global route preferences. Which observation would directly demonstrate that this specific issue is resolved? The static route is active and its recursive next hop resolves to an operational interface Forwarding entries are present on the line card and a test flow traverses the intended interface The routing table and packet-path trace select the intended prefix and next hop A mobility test keeps the expected address and established application sessions while moving across APs ExplanationCorrect Answer C:The routing table and packet-path trace select the intended prefix and next hop. This is a directly observable check for the proposed correction: Compare candidate prefixes and remove the unintended more-specific route before changing global route preferences. The particular failure being investigated is: A branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. Incorrect Answers A:The static route is active and its recursive next hop resolves to an operational interface. This check belongs to a static route is configured to a next-hop address that is absent from the local routing table and never becomes active. The actual defect is different: A branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. Longest-prefix matching precedes route preference comparisons between routes of different mask lengths. B:When newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries, a result such as this is useful: Forwarding entries are present on the line card and a test flow traverses the intended interface. For the reported fault, a branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router; compare candidate prefixes and remove the unintended more-specific route before changing global route preferences. D:When a client changes IP address during normal intra-campus roaming because neighboring APs anchor it to incompatible service VLANs, a result such as this is useful: A mobility test keeps the expected address and established application sessions while moving across APs. For the reported fault, a branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router; a stray specific route can silently bypass the preferred security inspection path.
Question 489The datacom engineering team at a research instrumentation firm while validating change-control evidence reviews this independent fictional networking case: A switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built. A proposed remedy is: Enable and validate snooping with an operative querier and approved multicast router ports. Which technical principle most directly supports this remedy? IGMP snooping limits layer-2 forwarding to listeners when it learns accurate group-to-port membership Multicast RPF checks help prevent loops by accepting traffic from the interface on the expected source path PIM-SM can transition from a shared tree to a source-specific tree when route and policy permit Without a querier, snooping membership tables can age out even while hosts remain attached ExplanationCorrect Answer A:IGMP snooping limits layer-2 forwarding to listeners when it learns accurate group-to-port membership. This directly explains why the corrective operation is appropriate: Enable and validate snooping with an operative querier and approved multicast router ports. The observed acceptance evidence should be: Only subscribed access ports receive the feed and the multicast router port remains operational. Incorrect Answers B:Multicast RPF checks help prevent loops by accepting traffic from the interface on the expected source path. That rule governs a different situation: A multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. Here, a switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built. IGMP snooping limits layer-2 forwarding to listeners when it learns accurate group-to-port membership. C:PIM-SM can transition from a shared tree to a source-specific tree when route and policy permit. That principle is relevant when a distant receiver continues using a long shared tree after a short direct source path is available and capacity is strained. Here, a switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built; enable and validate snooping with an operative querier and approved multicast router ports. D:Without a querier, snooping membership tables can age out even while hosts remain attached. That rule governs a different situation: A VLAN with multicast hosts has no functioning IGMP querier after its original gateway moves away. Here, a switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built. Only subscribed access ports receive the feed and the multicast router port remains operational.
Question 490The 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. The team applies this remedy: Use supported BFD or remote path tracking to withdraw the unusable static next hop. Which observation would directly demonstrate that this specific issue is resolved? The planned primary device owns the virtual gateway after recovery and failover still works Both peers display Up state and a controlled liveness fault produces a consistent Down event An injected upstream failure withdraws the primary route and backup traffic succeeds Host neighbor tables resolve to the expected virtual MAC and sessions recover after failover ExplanationCorrect Answer C:An injected upstream failure withdraws the primary route and backup traffic succeeds. This is a directly observable check for the proposed correction: Use supported BFD or remote path tracking to withdraw the unusable static next hop. The particular failure being investigated is: A static backup path remains inactive while the primary next hop fails beyond a locally Up interface. Incorrect Answers A:When a backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy, a result such as this is useful: The planned primary device owns the virtual gateway after recovery and failover still works. For the reported fault, 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:When two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior, a result such as this is useful: Both peers display Up state and a controlled liveness fault produces a consistent Down event. For 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 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, a result such as this is useful: Host neighbor tables resolve to the expected virtual MAC and sessions recover after failover. For the reported fault, a static backup path remains inactive while the primary next hop fails beyond a locally Up interface; failure beyond the local link can strand static-route traffic indefinitely.