Question 590The datacom engineering team at an agricultural equipment distributor after an incident review reviews this independent fictional networking case: A static route is configured to a next-hop address that is absent from the local routing table and never becomes active. A proposed remedy is: Provide a resolvable route to the next hop or replace it with the verified directly reachable next hop. Which technical principle most directly supports this remedy? A healthy control plane does not prove that hardware forwarding entries are programmed in the data plane A static route depending on recursive resolution cannot forward when its next-hop recursion fails Longest-prefix matching precedes route preference comparisons between routes of different mask lengths IGMP membership state is maintained by router queries and host reports rather than permanent discovery ExplanationCorrect Answer B:A static route depending on recursive resolution cannot forward when its next-hop recursion fails. This directly explains why the corrective operation is appropriate: Provide a resolvable route to the next hop or replace it with the verified directly reachable next hop. The observed acceptance evidence should be: The static route is active and its recursive next hop resolves to an operational interface. Incorrect Answers A:A healthy control plane does not prove that hardware forwarding entries are programmed in the data plane. That principle is relevant when newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries. Here, a static route is configured to a next-hop address that is absent from the local routing table and never becomes active; a static route depending on recursive resolution cannot forward when its next-hop recursion fails. C:When 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. By contrast, a static route is configured to a next-hop address that is absent from the local routing table and never becomes active; provide a resolvable route to the next hop or replace it with the verified directly reachable next hop. D:An access VLAN loses a multicast receiver after a quiet period because periodic IGMP membership updates never reach the upstream querier. IGMP membership state is maintained by router queries and host reports rather than permanent discovery. The current condition differs: A static route is configured to a next-hop address that is absent from the local routing table and never becomes active. The static route is active and its recursive next hop resolves to an operational interface.
Question 591The datacom engineering team at a municipal transport operator during a simulated failover test reviews this independent fictional networking case: One router continues advertising a failed transit link because the local interface reports Up while an intermediate transport component is down. If this issue remains unresolved, what immediate availability or security risk follows most directly? Persistently stale link state can redirect traffic into a dead transport segment Lack of controlled interarea aggregation increases flooding and update workload during access failures Unexamined external metric type can funnel outbound traffic toward a distant congested exit A fragmented OSPF backbone can split route exchange between otherwise healthy areas ExplanationCorrect Answer A:Persistently stale link state can redirect traffic into a dead transport segment. Leaving the exact fault unresolved means: One router continues advertising a failed transit link because the local interface reports Up while an intermediate transport component is down. The intended response is: Restore accurate failure detection and re-originate the affected OSPF topology information. Incorrect Answers B:When several closely related access prefixes create unnecessary interarea LSA churn because no ABR aggregation is applied, lack of controlled interarea aggregation increases flooding and update workload during access failures. The present failure is different: 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. C:Unexamined external metric type can funnel outbound traffic toward a distant congested exit. That risk belongs to a separate condition: A remote site incorrectly chooses an external OSPF route that ignores material internal distance to competing exit points. Here, one router continues advertising a failed transit link because the local interface reports Up while an intermediate transport component is down; restore accurate failure detection and re-originate the affected OSPF topology information. D:When two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent, a fragmented OSPF backbone can split route exchange between otherwise healthy areas. The present failure is different: One router continues advertising a failed transit link because the local interface reports Up while an intermediate transport component is down. The relevant LSA changes, SPF runs, and the affected route moves to a healthy alternate.
Question 592The datacom engineering team at a financial clearing service during a network security audit reviews this independent fictional networking case: An enterprise wants to influence how some external networks enter its secondary ISP, but it changes local preference inside its own AS instead. A proposed remedy is: Apply provider-approved AS_PATH prepending or another suitable inbound policy while recognizing remote policy precedence. Which technical principle most directly supports this remedy? BGP route eligibility depends on resolvable next hops and a functioning forwarding path A base BGP TCP session does not imply that every MP-BGP address family is negotiated and active EVPN route targets control which VPN routes a receiving instance is permitted to import AS_PATH attributes can influence external path selection but cannot guarantee behavior against other operators' policies ExplanationCorrect Answer D:AS_PATH attributes can influence external path selection but cannot guarantee behavior against other operators' policies. This directly explains why the corrective operation is appropriate: Apply provider-approved AS_PATH prepending or another suitable inbound policy while recognizing remote policy precedence. The observed acceptance evidence should be: External route views show the intended prepended announcement and measured ingress path changes when supported. Incorrect Answers A: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. The current condition differs: An enterprise wants to influence how some external networks enter its secondary ISP, but it changes local preference inside its own AS instead. AS_PATH attributes can influence external path selection but cannot guarantee behavior against other operators' policies. B:When an EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes, a base BGP TCP session does not imply that every MP-BGP address family is negotiated and active. By contrast, an enterprise wants to influence how some external networks enter its secondary ISP, but it changes local preference inside its own AS instead; apply provider-approved AS_PATH prepending or another suitable inbound policy while recognizing remote policy precedence. C:EVPN route targets control which VPN routes a receiving instance is permitted to import. That rule governs a different situation: Tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. Here, 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.
Question 593The datacom engineering team at an e-commerce fulfillment center while validating change-control evidence reviews this independent fictional networking case: Guest devices receive an internal employee VLAN after 802.1X authorization results are mapped incorrectly by WLAN policy. Which corrective engineering action most directly addresses this problem? Correct NAC authorization attributes and dynamic VLAN/role mapping for each identity category Replan channel assignments and transmit power based on measured co-channel contention Review the WLAN VLAN pool mapping and rebalance supported client distribution with consistent DHCP scopes Harmonize mobility-domain forwarding and VLAN/anchor design so approved roams preserve intended IP connectivity ExplanationCorrect Answer A:Correct NAC authorization attributes and dynamic VLAN/role mapping for each identity category. This is the specific action that addresses the fictional fault: Guest devices receive an internal employee VLAN after 802.1X authorization results are mapped incorrectly by WLAN policy. The governing technical reason is: WLAN access enforcement must combine authenticated identity with the corresponding least-privilege network role. Verify by checking: Guest trials land in isolated address space and employees retain intended access. Incorrect Answers B:When a large lecture hall experiences low Wi-Fi throughput even with strong signal because neighboring AP radios overlap excessively on busy channels, replanning channel assignments and transmit power based on measured co-channel contention could be appropriate. Here, guest devices receive an internal employee VLAN after 802.1X authorization results are mapped incorrectly by WLAN policy. WLAN access enforcement must combine authenticated identity with the corresponding least-privilege network role. C:One SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space. Reviewing the WLAN VLAN pool mapping and rebalance supported client distribution with consistent DHCP scopes can respond to that condition, but it would not correct the reported fault: Guest devices receive an internal employee VLAN after 802.1X authorization results are mapped incorrectly by WLAN policy. Correct NAC authorization attributes and dynamic VLAN/role mapping for each identity category. D:A client changes IP address during normal intra-campus roaming because neighboring APs anchor it to incompatible service VLANs. Harmonizing mobility-domain forwarding and VLAN/anchor design so approved roams preserve intended IP connectivity can respond to that condition, but it would not correct the reported fault: Guest devices receive an internal employee VLAN after 802.1X authorization results are mapped incorrectly by WLAN policy. Guest trials land in isolated address space and employees retain intended access.
Question 594The datacom engineering team at a retail banking network as part of an acceptance test 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 NSSA uses Type-7 external LSAs inside its area and relies on translation at an appropriate border device OSPF shortest-path selection uses cumulative interface cost, not real-time measured bandwidth by itself Aggregating interarea advertisements can reduce control-plane state but must not capture unreachable space 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: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 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:OSPF shortest-path selection uses cumulative interface cost, not real-time measured bandwidth by itself. That principle is relevant when after an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed. 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: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: 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 595The datacom engineering team at a retail banking network as part of an acceptance test reviews this independent fictional networking case: A dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent. A proposed remedy is: Investigate PIM-DM neighbor/prune behavior and remove unnecessary dense-mode flooding where appropriate. Which technical principle most directly supports this remedy? PIM-SM uses an RP to build initial shared-tree reachability for ASM groups Source-specific multicast forwarding is tied to a particular source and group rather than RP-based ASM discovery Multicast RPF checks help prevent loops by accepting traffic from the interface on the expected source path PIM-DM initially floods and then prunes branches without receivers ExplanationCorrect Answer D:PIM-DM initially floods and then prunes branches without receivers. This directly explains why the corrective operation is appropriate: Investigate PIM-DM neighbor/prune behavior and remove unnecessary dense-mode flooding where appropriate. The observed acceptance evidence should be: The non-listener branch stops receiving the data after valid prune processing. Incorrect Answers A:PIM-SM uses an RP to build initial shared-tree reachability for ASM groups. That rule governs a different situation: A multicast source in a sparse-mode domain sends traffic but remote listeners receive nothing because the routers have inconsistent RP mappings. Here, a dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent. PIM-DM initially floods and then prunes branches without receivers. B:Source-specific multicast forwarding is tied to a particular source and group rather than RP-based ASM discovery. That principle is relevant when a receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. Here, a dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent; investigate PIM-DM neighbor/prune behavior and remove unnecessary dense-mode flooding where appropriate. C:When a multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded, multicast RPF checks help prevent loops by accepting traffic from the interface on the expected source path. By contrast, a dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent; the non-listener branch stops receiving the data after valid prune processing.
Question 596The datacom engineering team at an agricultural equipment distributor after an incident review reviews this independent fictional networking case: An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. If this issue remains unresolved, what immediate availability or security risk follows most directly? Missing local preference control can increase egress charges and path instability Misconfigured reflection can create route loops and unstable reachability Missing address-family negotiation leaves overlays unreachable despite a healthy BGP session Diagnosing BGP policy before basic transport can prolong an otherwise simple outage ExplanationCorrect Answer C:Missing address-family negotiation leaves overlays unreachable despite a healthy BGP session. Leaving the exact fault unresolved means: An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. The intended response is: Enable and validate the correct EVPN address-family capability and policy on both peers. Incorrect Answers A:When a multihomed autonomous system sends outbound traffic via a paid backup despite the intended primary exit, missing local preference control can increase egress charges and path instability. The present failure is different: An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. A base BGP TCP session does not imply that every MP-BGP address family is negotiated and active. B:An iBGP route reflected through overlapping clusters returns toward its originator unexpectedly. In that situation, misconfigured reflection can create route loops and unstable reachability. Here instead, an EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. Enable and validate the correct EVPN address-family capability and policy on both peers. D:Diagnosing BGP policy before basic transport can prolong an otherwise simple outage. That consequence could follow when a BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. Here, an EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes; the EVPN address-family neighbor state and advertised route types appear as expected.
Question 597The datacom engineering team at a cross-border logistics provider after a monitored link change 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? Configure the intended loopback update source and ensure loopback reachability across the IGP Restore transport IP reachability to the neighbor before changing BGP route policies Assign route distinguishers suitable for creating unique originating VPN route identifiers Apply next-hop-self on the appropriate border speaker or otherwise make the next hop legitimately reachable ExplanationCorrect Answer C: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 two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses, configuring the intended loopback update source and ensure loopback reachability across the IGP 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. B:A BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. This is where restoring transport IP reachability to the neighbor before changing BGP route policies would help. By contrast, 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:Applying next-hop-self on the appropriate border speaker or otherwise make the next hop legitimately reachable is relevant when an iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally. It does not resolve this case: 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 598The datacom engineering team at a public university consortium during a network security audit reviews this independent fictional networking case: An NSSA branch redistributes a local static route that fails to appear as expected outside the NSSA. Which corrective engineering action most directly addresses this problem? Correct the interface area assignment after confirming the intended area boundary Apply appropriately scoped external prefix summarization at the originating ASBR Check Type-7 external origination and ABR translation toward Type-5 reachability in the backbone Reestablish a contiguous backbone design and use any supported temporary virtual link only with documented constraints ExplanationCorrect Answer C:Check Type-7 external origination and ABR translation toward Type-5 reachability in the backbone. This is the specific action that addresses the fictional fault: An NSSA branch redistributes a local static route that fails to appear as expected outside the NSSA. The governing technical reason is: NSSA uses Type-7 external LSAs inside its area and relies on translation at an appropriate border device. Verify by checking: The redistributed prefix is present as Type-7 in the NSSA and appropriate external form beyond it. Incorrect Answers A: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. This is where correcting the interface area assignment after confirming the intended area boundary would help. By contrast, 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. B:Applying appropriately scoped external prefix summarization at the originating ASBR is relevant when an ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. It does not resolve this case: An NSSA branch redistributes a local static route that fails to appear as expected outside the NSSA. Check Type-7 external origination and ABR translation toward Type-5 reachability in the backbone. D: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 NSSA branch redistributes a local static route that fails to appear as expected outside the NSSA. The redistributed prefix is present as Type-7 in the NSSA and appropriate external form beyond it.
Question 599The datacom engineering team at an energy distribution business while tracing a degraded application flow 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. A proposed remedy is: Inspect RSTP role/state exchanges and fix the inconsistent neighbor port configuration. Which technical principle most directly supports this remedy? The spanning-tree root selection follows bridge identifier priority rather than physical hierarchy labels MSTP topology behavior is per instance and consistent VLAN mapping is necessary for predictable forwarding Stacking presents multiple switches as a logical system but failure domains still depend on physical member connectivity RSTP alternate ports are designed to become forwarding backups after topology changes ExplanationCorrect Answer D:RSTP alternate ports are designed to become forwarding backups after topology changes. This directly explains why the corrective operation is appropriate: Inspect RSTP role/state exchanges and fix the inconsistent neighbor port configuration. The observed acceptance evidence should be: The alternate link transitions to forwarding after a controlled primary failure without sustained loop. Incorrect Answers A:When a low-capacity access switch becomes the spanning-tree root because its bridge priority was left lower than the distribution pair, the spanning-tree root selection follows bridge identifier priority rather than physical hierarchy labels. By contrast, 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. B:When 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. By contrast, 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. C:Stacking presents multiple switches as a logical system but failure domains still depend on physical member connectivity. That rule governs a different situation: A stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed. Here, 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.
Question 600The datacom engineering team at a satellite ground station operator after an incident review reviews this independent fictional networking case: Branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. The team applies this remedy: Align the totally stub area behavior at the ABR and verify the intended default-based forwarding. Which observation would directly demonstrate that this specific issue is resolved? The ABR default route appears in the stub area and external destinations remain reachable The redistributed prefix is present as Type-7 in the NSSA and appropriate external form beyond it Remote OSPF routers receive the summary and reach all intended attached external subnets Branch route tables contain the intended default rather than the unexpected interarea prefixes ExplanationCorrect Answer D:Branch route tables contain the intended default rather than the unexpected interarea prefixes. This is a directly observable check for the proposed correction: Align the totally stub area behavior at the ABR and verify the intended default-based forwarding. The particular failure being investigated is: Branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. Incorrect Answers A:The ABR default route appears in the stub area and external destinations remain reachable. That result could validate a repair when an engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. Here, branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR; totally stubby configuration suppresses most interarea summaries while retaining the area default route. B:When an NSSA branch redistributes a local static route that fails to appear as expected outside the NSSA, a result such as this is useful: The redistributed prefix is present as Type-7 in the NSSA and appropriate external form beyond it. For the reported fault, branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR; align the totally stub area behavior at the ABR and verify the intended default-based forwarding. C: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, branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR; uncontrolled interarea route leakage increases route churn at constrained branch devices.