Question 790The datacom engineering team at a financial clearing service during a network security audit reviews this independent fictional networking case: Voice handsets suffer several seconds of audio interruption after moving between APs because full authentication runs on every transition. A proposed remedy is: Validate client and controller support for appropriate fast-transition roaming mechanisms. 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 Strong RSSI does not guarantee throughput; overlapping airtime competition reduces usable capacity A roaming design should reduce reconnection overhead without bypassing authorized identity checks Prefix-limit controls can bound routing state growth when a neighbor violates expected route scale ExplanationCorrect Answer C:A roaming design should reduce reconnection overhead without bypassing authorized identity checks. This directly explains why the corrective operation is appropriate: Validate client and controller support for appropriate fast-transition roaming mechanisms. The observed acceptance evidence should be: Controlled mobility tests show successful secure reauthentication with acceptable call interruption. 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: Voice handsets suffer several seconds of audio interruption after moving between APs because full authentication runs on every transition. A roaming design should reduce reconnection overhead without bypassing authorized identity checks. B:Strong RSSI does not guarantee throughput; overlapping airtime competition reduces usable capacity. That rule governs a different situation: A large lecture hall experiences low Wi-Fi throughput even with strong signal because neighboring AP radios overlap excessively on busy channels. Here, voice handsets suffer several seconds of audio interruption after moving between APs because full authentication runs on every transition. Validate client and controller support for appropriate fast-transition roaming mechanisms. D:Prefix-limit controls can bound routing state growth when a neighbor violates expected route scale. That principle is relevant when a provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. Here, voice handsets suffer several seconds of audio interruption after moving between APs because full authentication runs on every transition; controlled mobility tests show successful secure reauthentication with acceptable call interruption.
Question 791The datacom engineering team at a satellite ground station operator after an incident review reviews this independent fictional networking case: An IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly. A proposed remedy is: Specify the appropriate egress interface with the link-local next hop and verify neighbor discovery. Which technical principle most directly supports this remedy? IPv6 link-local addresses are interface scoped and may require egress context for next-hop resolution SLAAC relies on received router advertisement prefix information and associated address configuration flags IPv6 DAD uses neighbor solicitation to detect duplicate addresses before regular use OSPF routing exchanges must pass consistent authentication checks before neighbor state can advance ExplanationCorrect Answer A:IPv6 link-local addresses are interface scoped and may require egress context for next-hop resolution. This directly explains why the corrective operation is appropriate: Specify the appropriate egress interface with the link-local next hop and verify neighbor discovery. The observed acceptance evidence should be: The route installs with the expected interface and reachability probes succeed. Incorrect Answers B:SLAAC relies on received router advertisement prefix information and associated address configuration flags. That principle is relevant when clients on a new IPv6 VLAN fail to obtain global addresses because router advertisements lack the intended autonomous prefix information. Here, an IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly; IPv6 link-local addresses are interface scoped and may require egress context for next-hop resolution. C:Two replacement servers are configured with the same IPv6 address and one fails to bring the address online. IPv6 DAD uses neighbor solicitation to detect duplicate addresses before regular use. The current condition differs: An IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly. Specify the appropriate egress interface with the link-local next hop and verify neighbor discovery. D:When an OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only, OSPF routing exchanges must pass consistent authentication checks before neighbor state can advance. By contrast, an IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly; the route installs with the expected interface and reachability probes succeed.
Question 792The datacom engineering team at a maritime terminal after a monitored link change reviews this independent fictional networking case: A campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services. Which corrective engineering action most directly addresses this problem? Restore dual-active detection or an approved split-brain suppression mechanism and test isolation behavior 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 Reconcile MST region name, revision and VLAN-instance mapping across the devices ExplanationCorrect Answer A:Restore dual-active detection or an approved split-brain suppression mechanism and test isolation behavior. This is the specific action that addresses the fictional fault: A campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services. The governing technical reason is: Cluster heartbeat failures require independent mechanisms to avoid concurrent active ownership of the same logical service. Verify by checking: Controlled heartbeat loss leaves only one authorized active forwarding role with no duplicate gateway responses. Incorrect Answers B:Setting deliberate RSTP root and backup-root bridge priorities on stable distribution switches is relevant when a low-capacity access switch becomes the spanning-tree root because its bridge priority was left lower than the distribution pair. It does not resolve this case: A campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services. Cluster heartbeat failures require independent mechanisms to avoid concurrent active ownership of the same logical service. For maritime terminal after a monitored link change, the acceptance test should show that controlled heartbeat loss leaves only one authorized active forwarding role with no duplicate gateway responses. C: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, a campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services. Restore dual-active detection or an approved split-brain suppression mechanism and test isolation behavior. D:When two switches intended in one MSTP region behave as if separated by a regional boundary after an unnoticed configuration edit, reconciling MST region name, revision and VLAN-instance mapping across the devices could be appropriate. Here, 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.
Question 793The 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. If this issue remains unresolved, what immediate availability or security risk follows most directly? Mixed metric interpretation can produce route divergence and unstable path choices Repeated DIS transitions produce unnecessary topology recalculations Split key deployment can sever a core routing domain even when the circuit is physically healthy Early transit selection can blackhole traffic during control-plane recovery ExplanationCorrect Answer A:Mixed metric interpretation can produce route divergence and unstable path choices. Leaving the exact fault unresolved means: A new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. The intended response is: Align a supported wide-metric style before deploying the higher-cost topology. Incorrect Answers B:When a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn, repeated DIS transitions produce unnecessary topology recalculations. The present failure is different: 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:Split key deployment can sever a core routing domain even when the circuit is physically healthy. That consequence could follow when an IS-IS adjacency drops after only one of two core routers receives a new authentication key. Here, a new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles; align a supported wide-metric style before deploying the higher-cost topology. D:Early transit selection can blackhole traffic during control-plane recovery. That consequence could follow 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 794The 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. Which corrective engineering action most directly addresses this problem? Coordinate IS-IS authentication and key rollover across the peer link Align a supported wide-metric style before deploying the higher-cost topology Align the IS-IS area portion of the NET or revise the intended L1/L2 boundary Compare sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization ExplanationCorrect Answer D:Compare sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization. This is the specific action that addresses the fictional fault: Core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. The governing technical reason is: IS-IS link-state consistency depends on reliable LSP version synchronization within each level. Verify by checking: Peers converge to the same current LSP sequence and the affected route becomes stable. Incorrect Answers A:Coordinating IS-IS authentication and key rollover across the peer link is relevant when an IS-IS adjacency drops after only one of two core routers receives a new authentication key. It does not resolve this case: 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. B:When a new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles, aligning a supported wide-metric style before deploying the higher-cost topology could be appropriate. 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. C:When two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses, aligning the IS-IS area portion of the NET or revise the intended L1/L2 boundary could be appropriate. 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 795The datacom engineering team at an agricultural equipment distributor after an incident review reviews this independent fictional networking case: A router recovering from reboot begins attracting transit traffic before its route state is ready. A proposed remedy is: Apply a controlled IS-IS overload period during startup and remove it after routing readiness. 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 adjacencies require at least one common enabled routing level IS-IS metric encoding capability must be consistent enough for all participating routers to calculate intended paths The IS-IS overload bit discourages transit use of an incompletely initialized router ExplanationCorrect Answer D:The IS-IS overload bit discourages transit use of an incompletely initialized router. This directly explains why the corrective operation is appropriate: Apply a controlled IS-IS overload period during startup and remove it after routing readiness. The observed acceptance evidence should be: Traces avoid the recovering node until readiness and return afterward without loss. 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, a router recovering from reboot begins attracting transit traffic before its route state is ready; the IS-IS overload bit discourages transit use of an incompletely initialized router. B:When 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. By contrast, a router recovering from reboot begins attracting transit traffic before its route state is ready; apply a controlled IS-IS overload period during startup and remove it after routing readiness. C:When 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. By contrast, a router recovering from reboot begins attracting transit traffic before its route state is ready; traces avoid the recovering node until readiness and return afterward without loss.
Question 796The datacom engineering team at a government service campus after a monitored link change reviews this independent fictional networking case: An enterprise polls infrastructure over legacy unauthenticated SNMP and risks exposing operational data across shared networks. The team applies this remedy: Use supported SNMPv3 authentication/privacy and authorize specific management targets. Which observation would directly demonstrate that this specific issue is resolved? Discover/offer/request/ack exchange completes and clients receive correct scopes and gateways Approved collectors receive data with validated SNMPv3 security and unauthenticated polls are rejected SPF routing to the remote prefix favors the intended link and converges after the change Route advertisements stop oscillating and correct original route sources remain stable ExplanationCorrect Answer B:Approved collectors receive data with validated SNMPv3 security and unauthenticated polls are rejected. This is a directly observable check for the proposed correction: Use supported SNMPv3 authentication/privacy and authorize specific management targets. The particular failure being investigated is: An enterprise polls infrastructure over legacy unauthenticated SNMP and risks exposing operational data across shared networks. Incorrect Answers A:Discover/offer/request/ack exchange completes and clients receive correct scopes and gateways. That result could validate a repair when newly moved office endpoints cannot receive IPv4 leases because their DHCP server is across a routed interface without a relay. Here, an enterprise polls infrastructure over legacy unauthenticated SNMP and risks exposing operational data across shared networks; network management polling should use authenticated and encrypted protocol settings when sensitive telemetry is exposed. C: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, an enterprise polls infrastructure over legacy unauthenticated SNMP and risks exposing operational data across shared networks; use supported SNMPv3 authentication/privacy and authorize specific management targets. D:Two redistribution points repeatedly re-inject learned routes between OSPF and another IGP and churn route entries. Route advertisements stop oscillating and correct original route sources remain stable. This observation does not prove the correction for the reported defect: An enterprise polls infrastructure over legacy unauthenticated SNMP and risks exposing operational data across shared networks. Insecure polling can leak topology and configuration metadata to untrusted observers.
Question 797The datacom engineering team at an air-cargo logistics operator during a network security audit reviews this independent fictional networking case: A BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. If this issue remains unresolved, what immediate availability or security risk follows most directly? A visible BGP prefix can still hide a black hole if forwarding recursion is stale Incomplete understanding of attribute order leads to ineffective and potentially disruptive policy changes Inbound traffic may continue on an unwanted provider if external policy is not validated An unconstrained update surge can exhaust control-plane capacity and disrupt unrelated services ExplanationCorrect Answer A:A visible BGP prefix can still hide a black hole if forwarding recursion is stale. Leaving the exact fault unresolved means: A BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. The intended response is: Repair next-hop recursion and underlying IGP convergence, not just the BGP session. Incorrect Answers B:Incomplete understanding of attribute order leads to ineffective and potentially disruptive policy changes. That consequence could follow when operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. Here, 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. C:Inbound traffic may continue on an unwanted provider if external policy is not validated. That consequence could follow when an enterprise wants to influence how some external networks enter its secondary ISP, but it changes local preference inside its own AS instead. Here, a BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link; repair next-hop recursion and underlying IGP convergence, not just the BGP session. D:An unconstrained update surge can exhaust control-plane capacity and disrupt unrelated services. That risk belongs to a separate condition: A provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. Here, a BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link; the best BGP route resolves to a live next hop and data-plane probes succeed after reconvergence.
Question 798The 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. If this issue remains unresolved, what immediate availability or security risk follows most directly? Control-plane reachability can conceal production packet loss until the forwarding pipeline is verified Unresolved recursive next hops create a persistent black hole despite syntactically valid configuration A stray specific route can silently bypass the preferred security inspection path Unexpected address changes can reset voice and real-time application sessions ExplanationCorrect Answer C:A stray specific route can silently bypass the preferred security inspection path. Leaving the exact fault unresolved means: A branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. The intended response is: Compare candidate prefixes and remove the unintended more-specific route before changing global route preferences. Incorrect Answers A:Control-plane reachability can conceal production packet loss until the forwarding pipeline is verified. That risk belongs to a separate condition: Newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries. Here, 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:A static route is configured to a next-hop address that is absent from the local routing table and never becomes active. In that situation, unresolved recursive next hops create a persistent black hole despite syntactically valid configuration. Here instead, 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, unexpected address changes can reset voice and real-time application sessions. The present failure is different: 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 799The datacom engineering team at a nationwide retail chain during a simulated failover test reviews this independent fictional networking case: A provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. The team applies this remedy: Set an appropriate maximum-prefix threshold and test the negotiated recovery behavior. Which observation would directly demonstrate that this specific issue is resolved? The target instance imports only matching tenant routes and no unrelated VRF routes appear The limit activates predictably in staging and the router protects its route memory during an oversized update Adjacent peers show the expected communities and external advertisements are scoped as contracted Exported BGP routes contain only the authorized prefix and mask set ExplanationCorrect Answer B:The limit activates predictably in staging and the router protects its route memory during an oversized update. This is a directly observable check for the proposed correction: Set an appropriate maximum-prefix threshold and test the negotiated recovery behavior. The particular failure being investigated is: A provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. Incorrect Answers A:When tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance, a result such as this is useful: The target instance imports only matching tenant routes and no unrelated VRF routes appear. For the reported fault, a provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set; prefix-limit controls can bound routing state growth when a neighbor violates expected route scale. C:Adjacent peers show the expected communities and external advertisements are scoped as contracted. This check belongs to a border router tags specific prefixes but the provider does not apply the expected regional no-export treatment. The actual defect is different: A provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. Set an appropriate maximum-prefix threshold and test the negotiated recovery behavior. D:Exported BGP routes contain only the authorized prefix and mask set. This check belongs to an accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. The actual defect is different: A provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. An unconstrained update surge can exhaust control-plane capacity and disrupt unrelated services.
Question 800The datacom engineering team at a research instrumentation firm while validating change-control evidence 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? The IS-IS overload bit discourages transit use of an incompletely initialized router On broadcast IS-IS circuits the DIS originates a pseudonode LSP and its election follows IS-IS priority rules IS-IS metric encoding capability must be consistent enough for all participating routers to calculate intended paths Queue behavior depends on packets being correctly classified by actual header fields at the enforcement point ExplanationCorrect Answer B: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 A:A router recovering from reboot begins attracting transit traffic before its route state is ready. The IS-IS overload bit discourages transit use of an incompletely initialized router. 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 metric encoding capability must be consistent enough for all participating routers to calculate intended paths. That rule governs a different situation: A new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. 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 a voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns, queue behavior depends on packets being correctly classified by actual header fields at the enforcement point. 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.