Question 630The datacom engineering team at a municipal emergency dispatch center during a topology consistency review reviews this independent fictional networking case: Several closely related access prefixes create unnecessary interarea LSA churn because no ABR aggregation is applied. The team applies this remedy: Introduce an accurate ABR area range after verifying all component prefixes and forwarding outcomes. Which observation would directly demonstrate that this specific issue is resolved? The backbone receives the intended summary and test routes to each component subnet succeed The redistributed prefix is present as Type-7 in the NSSA and appropriate external form beyond it ABRs display correct backbone reachability and previously missing interarea routes appear The ABR default route appears in the stub area and external destinations remain reachable ExplanationCorrect Answer A:The backbone receives the intended summary and test routes to each component subnet succeed. This is a directly observable check for the proposed correction: Introduce an accurate ABR area range after verifying all component prefixes and forwarding outcomes. The particular failure being investigated is: Several closely related access prefixes create unnecessary interarea LSA churn because no ABR aggregation is applied. Incorrect Answers B:The redistributed prefix is present as Type-7 in the NSSA and appropriate external form beyond it. That result could validate a repair when an NSSA branch redistributes a local static route that fails to appear as expected outside the NSSA. Here, 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. C:Two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. ABRs display correct backbone reachability and previously missing interarea routes appear. This observation does not prove the correction for the reported defect: Several closely related access prefixes create unnecessary interarea LSA churn because no ABR aggregation is applied. Introduce an accurate ABR area range after verifying all component prefixes and forwarding outcomes. D: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. This observation does not prove the correction for the reported defect: 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.
Question 631The datacom engineering team at a maritime terminal after a monitored link change reviews this independent fictional networking case: Tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. If this issue remains unresolved, what immediate availability or security risk follows most directly? Diagnosing BGP policy before basic transport can prolong an otherwise simple outage Incorrect MED assumptions can cause uneven interconnect load and unpredictable ingress Route target errors can isolate a tenant or leak routes into the wrong routing instance Missing address-family negotiation leaves overlays unreachable despite a healthy BGP session ExplanationCorrect Answer C:Route target errors can isolate a tenant or leak routes into the wrong routing instance. Leaving the exact fault unresolved means: Tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. The intended response is: Correct matching export and import route-target policy for the tenant instance. Incorrect Answers A:Diagnosing BGP policy before basic transport can prolong an otherwise simple outage. That risk belongs to a separate condition: A BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. Here, tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance; EVPN route targets control which VPN routes a receiving instance is permitted to import. B:Two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned. In that situation, incorrect MED assumptions can cause uneven interconnect load and unpredictable ingress. Here instead, tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. Correct matching export and import route-target policy for the tenant instance. D:Missing address-family negotiation leaves overlays unreachable despite a healthy BGP session. That risk belongs to a separate condition: An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. Here, tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance; the target instance imports only matching tenant routes and no unrelated VRF routes appear.
Question 632The datacom engineering team at a sports event venue during a topology consistency review reviews this independent fictional networking case: Two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior. Which corrective engineering action most directly addresses this problem? Check supported BFD modes and mutually acceptable timer negotiation before coupling routing failover Verify the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover Enable supported BFD tracking for the OSPF adjacency and validate timer compatibility Use supported BFD or remote path tracking to withdraw the unusable static next hop ExplanationCorrect Answer A:Check supported BFD modes and mutually acceptable timer negotiation before coupling routing failover. This is the specific action that addresses the fictional fault: Two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior. The governing technical reason is: BFD session state depends on interoperable mode and timing negotiation between peers. Verify by checking: Both peers display Up state and a controlled liveness fault produces a consistent Down event. Incorrect Answers B:Verifying the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover is relevant 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. It does not resolve this case: Two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior. BFD session state depends on interoperable mode and timing negotiation between peers. C: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 can respond to that condition, but it would not correct the reported fault: Two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior. Check supported BFD modes and mutually acceptable timer negotiation before coupling routing failover. D:A static backup path remains inactive while the primary next hop fails beyond a locally Up interface. Using supported BFD or remote path tracking to withdraw the unusable static next hop can respond to that condition, but it would not correct the reported fault: Two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior. Both peers display Up state and a controlled liveness fault produces a consistent Down event.
Question 633The 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. A proposed remedy is: Assign route distinguishers suitable for creating unique originating VPN route identifiers. Which technical principle most directly supports this remedy? Route distinguishers distinguish otherwise identical VPN address advertisements; they do not themselves control import permission A base BGP TCP session does not imply that every MP-BGP address family is negotiated and active Higher LOCAL_PREF is preferred within an autonomous system and is normally not passed to eBGP neighbors BGP best-path attributes are evaluated in a defined order; shorter AS_PATH is not always the first deciding factor ExplanationCorrect Answer A:Route distinguishers distinguish otherwise identical VPN address advertisements; they do not themselves control import permission. This directly explains why the corrective operation is appropriate: Assign route distinguishers suitable for creating unique originating VPN route identifiers. The observed acceptance evidence should be: EVPN control-plane entries retain unique per-origin VPN identifiers and remote paths coexist. Incorrect Answers 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, 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:Higher LOCAL_PREF is preferred within an autonomous system and is normally not passed to eBGP neighbors. That principle is relevant when a multihomed autonomous system sends outbound traffic via a paid backup despite the intended primary exit. Here, 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:BGP best-path attributes are evaluated in a defined order; shorter AS_PATH is not always the first deciding factor. That rule governs a different situation: Operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. Here, 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 634The datacom engineering team at a local rail transit network while validating change-control evidence reviews this independent fictional networking case: Core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. The team applies this remedy: Compare sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization. Which observation would directly demonstrate that this specific issue is resolved? Peers converge to the same current LSP sequence and the affected route becomes stable The intended stable router becomes DIS and the pseudonode LSP refreshes correctly IS-IS hellos and LSP floods succeed and the remote LSDB converges The peer adjacency is Up at the intended level and corresponding LSPs exchange ExplanationCorrect Answer A:Peers converge to the same current LSP sequence and the affected route becomes stable. This is a directly observable check for the proposed correction: Compare sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization. The particular failure being investigated is: Core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. Incorrect Answers B:When a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn, a result such as this is useful: The intended stable router becomes DIS and the pseudonode LSP refreshes correctly. For the reported fault, core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized; IS-IS link-state consistency depends on reliable LSP version synchronization within each level. C:When IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass, a result such as this is useful: IS-IS hellos and LSP floods succeed and the remote LSDB converges. For the reported fault, core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized; compare sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization. D:The peer adjacency is Up at the intended level and corresponding LSPs exchange. That result could validate a repair when a transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2. Here, core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized; stale link-state information can create asymmetric paths and packet loss.
Question 635The datacom engineering team at a wholesale market association while tracing a degraded application flow reviews this independent fictional networking case: A client changes IP address during normal intra-campus roaming because neighboring APs anchor it to incompatible service VLANs. A proposed remedy is: Harmonize mobility-domain forwarding and VLAN/anchor design so approved roams preserve intended IP connectivity. Which technical principle most directly supports this remedy? A VLAN pool can distribute WLAN clients across logical broadcast domains when pool and DHCP design are coherent Central WLAN control architectures require planned control-plane redundancy and AP recovery behavior Session continuity during roaming depends on consistent mobility and client addressing behavior WLAN access enforcement must combine authenticated identity with the corresponding least-privilege network role ExplanationCorrect Answer C:Session continuity during roaming depends on consistent mobility and client addressing behavior. This directly explains why the corrective operation is appropriate: Harmonize mobility-domain forwarding and VLAN/anchor design so approved roams preserve intended IP connectivity. The observed acceptance evidence should be: A mobility test keeps the expected address and established application sessions while moving across APs. Incorrect Answers A:One SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space. A VLAN pool can distribute WLAN clients across logical broadcast domains when pool and DHCP design are coherent. The current condition differs: A client changes IP address during normal intra-campus roaming because neighboring APs anchor it to incompatible service VLANs. Session continuity during roaming depends on consistent mobility and client addressing behavior. B:A wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller. Central WLAN control architectures require planned control-plane redundancy and AP recovery behavior. The current condition differs: A client changes IP address during normal intra-campus roaming because neighboring APs anchor it to incompatible service VLANs. Harmonize mobility-domain forwarding and VLAN/anchor design so approved roams preserve intended IP connectivity. D:WLAN access enforcement must combine authenticated identity with the corresponding least-privilege network role. That rule governs a different situation: Guest devices receive an internal employee VLAN after 802.1X authorization results are mapped incorrectly by WLAN policy. Here, a client changes IP address during normal intra-campus roaming because neighboring APs anchor it to incompatible service VLANs. A mobility test keeps the expected address and established application sessions while moving across APs.
Question 636The datacom engineering team at an engineering consultancy during a controlled network cutover reviews this independent fictional networking case: Two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses. A proposed remedy is: Align the IS-IS area portion of the NET or revise the intended L1/L2 boundary. Which technical principle most directly supports this remedy? On broadcast IS-IS circuits the DIS originates a pseudonode LSP and its election follows IS-IS priority rules IS-IS link-state consistency depends on reliable LSP version synchronization within each level Level-1 IS-IS neighbors must belong to a compatible area while Level-2 can connect areas The IS-IS overload bit discourages transit use of an incompletely initialized router ExplanationCorrect Answer C:Level-1 IS-IS neighbors must belong to a compatible area while Level-2 can connect areas. This directly explains why the corrective operation is appropriate: Align the IS-IS area portion of the NET or revise the intended L1/L2 boundary. The observed acceptance evidence should be: L1 neighbor state establishes and the expected area routes appear. Incorrect Answers A:When 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. By contrast, two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses; level-1 IS-IS neighbors must belong to a compatible area while Level-2 can connect areas. B:IS-IS link-state consistency depends on reliable LSP version synchronization within each level. That principle is relevant when core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. Here, two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses; align the IS-IS area portion of the NET or revise the intended L1/L2 boundary. 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, two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses; L1 neighbor state establishes and the expected area routes appear.
Question 637The datacom engineering team at a university research campus while tracing a degraded application flow reviews this independent fictional networking case: Core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. A proposed remedy is: Compare sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization. Which technical principle most directly supports this remedy? IS-IS protocol authentication must match across neighbor exchanges to maintain trusted adjacencies IS-IS link-state consistency depends on reliable LSP version synchronization within each level IS-IS adjacencies require at least one common enabled routing level IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic ExplanationCorrect Answer B:IS-IS link-state consistency depends on reliable LSP version synchronization within each level. This directly explains why the corrective operation is appropriate: Compare sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization. The observed acceptance evidence should be: Peers converge to the same current LSP sequence and the affected route becomes stable. Incorrect Answers A: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. The current condition differs: Core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. IS-IS link-state consistency depends on reliable LSP version synchronization within each level. C:IS-IS adjacencies require at least one common enabled routing level. That principle is relevant when a transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2. Here, core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized; compare sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization. D:IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic. That rule governs a different situation: IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. Here, core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. Peers converge to the same current LSP sequence and the affected route becomes stable.
Question 638The 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. A proposed remedy is: Inspect RSTP role/state exchanges and fix the inconsistent neighbor port configuration. Which technical principle most directly supports this remedy? Edge-port fast transition should not make unauthorized bridge participation safe MSTP region equivalence depends on a matching region configuration identifier, not just physical adjacency Cluster heartbeat failures require independent mechanisms to avoid concurrent active ownership of the same logical service 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: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. The current condition differs: 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:MSTP region equivalence depends on a matching region configuration identifier, not just physical adjacency. That rule governs a different situation: Two switches intended in one MSTP region behave as if separated by a regional boundary after an unnoticed configuration edit. Here, 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:Cluster heartbeat failures require independent mechanisms to avoid concurrent active ownership of the same logical service. That rule governs a different situation: A campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services. 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 639The datacom engineering team at a consumer electronics manufacturer as part of an acceptance test reviews this independent fictional networking case: Two switches intended in one MSTP region behave as if separated by a regional boundary after an unnoticed configuration edit. A proposed remedy is: Reconcile MST region name, revision and VLAN-instance mapping across the devices. Which technical principle most directly supports this remedy? 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 MSTP region equivalence depends on a matching region configuration identifier, not just physical adjacency Edge-port fast transition should not make unauthorized bridge participation safe ExplanationCorrect Answer C:MSTP region equivalence depends on a matching region configuration identifier, not just physical adjacency. This directly explains why the corrective operation is appropriate: Reconcile MST region name, revision and VLAN-instance mapping across the devices. The observed acceptance evidence should be: Both switches report the same region identity and expected instance topology. Incorrect Answers A:MSTP topology behavior is per instance and consistent VLAN mapping is necessary for predictable forwarding. That principle is relevant when traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. Here, two switches intended in one MSTP region behave as if separated by a regional boundary after an unnoticed configuration edit; MSTP region equivalence depends on a matching region configuration identifier, not just physical adjacency. B:Stacking presents multiple switches as a logical system but failure domains still depend on physical member connectivity. That principle is relevant when a stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed. Here, two switches intended in one MSTP region behave as if separated by a regional boundary after an unnoticed configuration edit; reconcile MST region name, revision and VLAN-instance mapping across the devices. D:Edge-port fast transition should not make unauthorized bridge participation safe. That rule governs a different situation: A user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port. Here, two switches intended in one MSTP region behave as if separated by a regional boundary after an unnoticed configuration edit. Both switches report the same region identity and expected instance topology.
Question 640The datacom engineering team at a warehouse automation provider during a topology consistency review reviews this independent fictional networking case: A LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. A proposed remedy is: Tune IS-IS DIS priority on the shared LAN and validate neighbor continuity after a planned election. Which technical principle most directly supports this remedy? On broadcast IS-IS circuits the DIS originates a pseudonode LSP and its election follows IS-IS priority rules Level-1 IS-IS neighbors must belong to a compatible area while Level-2 can connect areas IS-IS link-state consistency depends on reliable LSP version synchronization within each level IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic ExplanationCorrect Answer A:On broadcast IS-IS circuits the DIS originates a pseudonode LSP and its election follows IS-IS priority rules. This directly explains why the corrective operation is appropriate: Tune IS-IS DIS priority on the shared LAN and validate neighbor continuity after a planned election. The observed acceptance evidence should be: The intended stable router becomes DIS and the pseudonode LSP refreshes correctly. Incorrect Answers B:Two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses. Level-1 IS-IS neighbors must belong to a compatible area while Level-2 can connect areas. The current condition differs: A LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. On broadcast IS-IS circuits the DIS originates a pseudonode LSP and its election follows IS-IS priority rules. C:IS-IS link-state consistency depends on reliable LSP version synchronization within each level. That principle is relevant when core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. Here, a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn; tune IS-IS DIS priority on the shared LAN and validate neighbor continuity after a planned election. D:When IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass, IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic. By contrast, a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn; the intended stable router becomes DIS and the pseudonode LSP refreshes correctly.