Question 110The datacom engineering team at a research instrumentation firm while validating change-control evidence 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? Interarea advertisements cover only approved reachable blocks and traced flows reach valid hosts Database description exchange completes and the OSPF neighbor reaches Full state The redistributed prefix is present as Type-7 in the NSSA and appropriate external form beyond it The designated router role moves to the planned stable device and all segment peers remain Full 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:When an area border router advertises a broad summary that includes subnets withdrawn after a site closure, a result such as this is useful: Interarea advertisements cover only approved reachable blocks and traced flows reach valid hosts. For the reported fault, 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: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. This observation does not prove the correction for the reported defect: 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:The designated router role moves to the planned stable device and all segment peers remain Full. That result could validate a repair when a shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. 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 111The datacom engineering team at a cross-border logistics provider after a monitored link change reviews this independent fictional networking case: A multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. The team applies this remedy: Verify the multicast RPF route and correct source reachability or appropriate multicast routing state. Which observation would directly demonstrate that this specific issue is resolved? RPF diagnostics name the arriving interface as valid and the downstream stream resumes Only subscribed access ports receive the feed and the multicast router port remains operational The multicast route table reflects an intended source-specific incoming interface and latency improves Membership remains active across multiple query intervals and the receiver continues playback ExplanationCorrect Answer A:RPF diagnostics name the arriving interface as valid and the downstream stream resumes. This is a directly observable check for the proposed correction: Verify the multicast RPF route and correct source reachability or appropriate multicast routing state. The particular failure being investigated is: A multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. Incorrect Answers B:When a switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built, a result such as this is useful: Only subscribed access ports receive the feed and the multicast router port remains operational. For the reported fault, 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. C:A distant receiver continues using a long shared tree after a short direct source path is available and capacity is strained. The multicast route table reflects an intended source-specific incoming interface and latency improves. This observation does not prove the correction for the reported defect: A multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. Verify the multicast RPF route and correct source reachability or appropriate multicast routing state. D:When an access VLAN loses a multicast receiver after a quiet period because periodic IGMP membership updates never reach the upstream querier, a result such as this is useful: Membership remains active across multiple query intervals and the receiver continues playback. For the reported fault, a multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded; failed RPF can interrupt multicast while unicast service tests still succeed.
Question 112The datacom engineering team at a municipal emergency dispatch center during a topology consistency review reviews this independent fictional networking case: A user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port. Which corrective engineering action most directly addresses this problem? Reconcile MST region name, revision and VLAN-instance mapping across the devices Set deliberate RSTP root and backup-root bridge priorities on stable distribution switches Apply supported BPDU protection at legitimate edge ports and investigate the unexpected bridge connection Rebalance cross-member uplinks and validate supported stack switchover and master recovery ExplanationCorrect Answer C:Apply supported BPDU protection at legitimate edge ports and investigate the unexpected bridge connection. This is the specific action that addresses the fictional fault: A user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port. The governing technical reason is: Edge-port fast transition should not make unauthorized bridge participation safe. Verify by checking: A received BPDU triggers the configured protective response and no loop appears. Incorrect Answers A:Reconciling MST region name, revision and VLAN-instance mapping across the devices is relevant when two switches intended in one MSTP region behave as if separated by a regional boundary after an unnoticed configuration edit. It does not resolve this case: 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. 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 user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port. Apply supported BPDU protection at legitimate edge ports and investigate the unexpected bridge connection. D:A stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed. This is where rebalancing cross-member uplinks and validating supported stack switchover and master recovery would help. By contrast, a user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port. A received BPDU triggers the configured protective response and no loop appears.
Question 113The datacom engineering team at a public water utility during a topology consistency review reviews this independent fictional networking case: Two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned. A proposed remedy is: Review the upstream's MED handling and advertise the intended metric on comparable links. Which technical principle most directly supports this remedy? Prefix-limit controls can bound routing state growth when a neighbor violates expected route scale EVPN route targets control which VPN routes a receiving instance is permitted to import Higher LOCAL_PREF is preferred within an autonomous system and is normally not passed to eBGP neighbors MED is a suggestion about preferred entry into a neighboring AS and its comparison is policy dependent ExplanationCorrect Answer D:MED is a suggestion about preferred entry into a neighboring AS and its comparison is policy dependent. This directly explains why the corrective operation is appropriate: Review the upstream's MED handling and advertise the intended metric on comparable links. The observed acceptance evidence should be: The upstream reports intended MED attributes and observed ingress tracks the agreed policy. Incorrect Answers A:When 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. By contrast, two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned; MED is a suggestion about preferred entry into a neighboring AS and its comparison is policy dependent. B:When 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. By contrast, two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned; review the upstream's MED handling and advertise the intended metric on comparable links. C:When a multihomed autonomous system sends outbound traffic via a paid backup despite the intended primary exit, higher LOCAL_PREF is preferred within an autonomous system and is normally not passed to eBGP neighbors. By contrast, two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned; the upstream reports intended MED attributes and observed ingress tracks the agreed policy.
Question 114The datacom engineering team at an air-cargo logistics operator during a network security audit reviews this independent fictional networking case: A high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling. Which corrective engineering action most directly addresses this problem? Track external-uplink health and reduce VRRP priority enough for the healthy backup to take over Use supported BFD or remote path tracking to withdraw the unusable static next hop Tune BFD intervals and multiplier for supported device and transport capabilities Correct VRRP group placement and virtual IPv4 address on the intended broadcast domain ExplanationCorrect Answer C:Tune BFD intervals and multiplier for supported device and transport capabilities. This is the specific action that addresses the fictional fault: A high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling. The governing technical reason is: Failure detection speed must be balanced against scheduling jitter and false-positive risk. Verify by checking: BFD remains stable under expected CPU load and still detects real test failures within requirement. Incorrect Answers A:A VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational. Tracking external-uplink health and reduce VRRP priority enough for the healthy backup to take over can respond to that condition, but it would not correct the reported fault: A high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling. Failure detection speed must be balanced against scheduling jitter and false-positive risk. B:A static backup path remains inactive while the primary next hop fails beyond a locally Up interface. This is where using supported BFD or remote path tracking to withdraw the unusable static next hop would help. By contrast, a high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling. Tune BFD intervals and multiplier for supported device and transport capabilities. D:Two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error. This is where correcting VRRP group placement and virtual IPv4 address on the intended broadcast domain would help. By contrast, a high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling. BFD remains stable under expected CPU load and still detects real test failures within requirement.
Question 115The datacom engineering team at a public university consortium during a network security audit reviews this independent fictional networking case: A wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller. The team applies this remedy: Configure supported AC discovery and high-availability mechanisms, then test controller failure. Which observation would directly demonstrate that this specific issue is resolved? Guest trials land in isolated address space and employees retain intended access APs register with the standby controller and client services recover within the documented bound A mobility test keeps the expected address and established application sessions while moving across APs Client associations spread across permitted VLANs and each receives an address from its own correct scope ExplanationCorrect Answer B:APs register with the standby controller and client services recover within the documented bound. This is a directly observable check for the proposed correction: Configure supported AC discovery and high-availability mechanisms, then test controller failure. The particular failure being investigated is: A wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller. Incorrect Answers A:When guest devices receive an internal employee VLAN after 802.1X authorization results are mapped incorrectly by WLAN policy, a result such as this is useful: Guest trials land in isolated address space and employees retain intended access. For the reported fault, 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. C:A mobility test keeps the expected address and established application sessions while moving across APs. That result could validate a repair when a client changes IP address during normal intra-campus roaming because neighboring APs anchor it to incompatible service VLANs. Here, a wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller; configure supported AC discovery and high-availability mechanisms, then test controller failure. D:When one SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space, a result such as this is useful: Client associations spread across permitted VLANs and each receives an address from its own correct scope. For the reported fault, a wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller; controller single points of failure can disrupt an entire campus WLAN.
Question 116The 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. Which corrective engineering action most directly addresses this problem? 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 Rebalance cross-member uplinks and validate supported stack switchover and master recovery Reconcile MST region name, revision and VLAN-instance mapping across the devices ExplanationCorrect Answer D:Reconcile MST region name, revision and VLAN-instance mapping across the devices. This is the specific action that addresses the fictional fault: Two switches intended in one MSTP region behave as if separated by a regional boundary after an unnoticed configuration edit. The governing technical reason is: MSTP region equivalence depends on a matching region configuration identifier, not just physical adjacency. Verify by checking: Both switches report the same region identity and expected instance topology. Incorrect Answers A: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: 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:A redundant access uplink stays blocked even after the active link fails because the switch has not converged its port roles correctly. Inspecting RSTP role/state exchanges and fixing the inconsistent neighbor port configuration can respond to that condition, but it would not correct the reported fault: 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. C:When a stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed, rebalancing cross-member uplinks and validating supported stack switchover and master recovery could be appropriate. 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 117The datacom engineering team at a call center outsourcer after a planned hardware refresh reviews this independent fictional networking case: Two replacement servers are configured with the same IPv6 address and one fails to bring the address online. A proposed remedy is: Resolve duplicate addressing and verify Neighbor Discovery duplicate-address-detection behavior. 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 Standard stub areas suppress Type-5 external LSAs and normally rely on an ABR-provided default for external reachability ExplanationCorrect Answer C:IPv6 DAD uses neighbor solicitation to detect duplicate addresses before regular use. This directly explains why the corrective operation is appropriate: Resolve duplicate addressing and verify Neighbor Discovery duplicate-address-detection behavior. The observed acceptance evidence should be: The conflicting address is removed and DAD completes without duplicate notifications. Incorrect Answers A:IPv6 link-local addresses are interface scoped and may require egress context for next-hop resolution. That principle is relevant when an IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly. Here, 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. B:When clients on a new IPv6 VLAN fail to obtain global addresses because router advertisements lack the intended autonomous prefix information, SLAAC relies on received router advertisement prefix information and associated address configuration flags. By contrast, two replacement servers are configured with the same IPv6 address and one fails to bring the address online; resolve duplicate addressing and verify Neighbor Discovery duplicate-address-detection behavior. D: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. The current condition differs: Two replacement servers are configured with the same IPv6 address and one fails to bring the address online. The conflicting address is removed and DAD completes without duplicate notifications.
Question 118The 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. The team applies this remedy: Check Type-7 external origination and ABR translation toward Type-5 reachability in the backbone. 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 Route choice matches documented exit intent when internal path costs differ Authentication error counters stop increasing and a new Full adjacency is established ExplanationCorrect Answer B:The redistributed prefix is present as Type-7 in the NSSA and appropriate external form beyond it. This is a directly observable check for the proposed correction: Check Type-7 external origination and ABR translation toward Type-5 reachability in the backbone. The particular failure being investigated is: An NSSA branch redistributes a local static route that fails to appear as expected outside the NSSA. Incorrect Answers A:When an engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault, a result such as this is useful: The ABR default route appears in the stub area and external destinations remain reachable. For the reported fault, 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. C:Route choice matches documented exit intent when internal path costs differ. This check belongs to a remote site incorrectly chooses an external OSPF route that ignores material internal distance to competing exit points. The actual defect is different: 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:Authentication error counters stop increasing and a new Full adjacency is established. This check belongs to an OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. The actual defect is different: An NSSA branch redistributes a local static route that fails to appear as expected outside the NSSA. Missing NSSA translation hides branch routes from the rest of the autonomous system.
Question 119The datacom engineering team at a research instrumentation firm while validating change-control evidence reviews this independent fictional networking case: A backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. The team applies this remedy: Set and document appropriate VRRP priorities and supported preemption behavior. Which observation would directly demonstrate that this specific issue is resolved? Matching gateway interfaces negotiate one Master and user devices reach the correct virtual address Host neighbor tables resolve to the expected virtual MAC and sessions recover after failover The planned primary device owns the virtual gateway after recovery and failover still works Primary uplink failure transfers Master to the router with valid outbound reachability ExplanationCorrect Answer C:The planned primary device owns the virtual gateway after recovery and failover still works. This is a directly observable check for the proposed correction: Set and document appropriate VRRP priorities and supported preemption behavior. The particular failure being investigated is: A backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. Incorrect Answers A:Matching gateway interfaces negotiate one Master and user devices reach the correct virtual address. That result could validate a repair when two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error. Here, a backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy; VRRP Master election is priority based subject to ownership and preemption rules. B: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. Host neighbor tables resolve to the expected virtual MAC and sessions recover after failover. This observation does not prove the correction for the reported defect: A backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. Set and document appropriate VRRP priorities and supported preemption behavior. D:When a VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational, a result such as this is useful: Primary uplink failure transfers Master to the router with valid outbound reachability. For the reported fault, a backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy; unplanned Master placement may steer client traffic over a less reliable exit.
Question 120The datacom engineering team at a research instrumentation firm while validating change-control evidence reviews this independent fictional networking case: A backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. Which corrective engineering action most directly addresses this problem? Verify the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover Set and document appropriate VRRP priorities and supported preemption behavior Track external-uplink health and reduce VRRP priority enough for the healthy backup to take over Enable supported BFD tracking for the OSPF adjacency and validate timer compatibility ExplanationCorrect Answer B:Set and document appropriate VRRP priorities and supported preemption behavior. This is the specific action that addresses the fictional fault: A backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. The governing technical reason is: VRRP Master election is priority based subject to ownership and preemption rules. Verify by checking: The planned primary device owns the virtual gateway after recovery and failover still works. Incorrect Answers A: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. Verifying the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover can respond to that condition, but it would not correct the reported fault: A backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. VRRP Master election is priority based subject to ownership and preemption rules. C:When a VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational, tracking external-uplink health and reduce VRRP priority enough for the healthy backup to take over could be appropriate. Here, a backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. Set and document appropriate VRRP priorities and supported preemption behavior. D:When OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection, enabling supported BFD tracking for the OSPF adjacency and validating timer compatibility could be appropriate. Here, a backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. The planned primary device owns the virtual gateway after recovery and failover still works.