Question 260The datacom engineering team at a cloud hosting provider after an incident review reviews this independent fictional networking case: A training-video multicast group begins leaking beyond its approved distribution region after a transport upgrade. A proposed remedy is: Apply appropriate multicast boundary and scope controls for the group range. Which technical principle most directly supports this remedy? Multicast distribution should follow explicitly defined group membership and boundary policy, not blanket flooding Multicast RPF checks help prevent loops by accepting traffic from the interface on the expected source path IGMP membership state is maintained by router queries and host reports rather than permanent discovery Without a querier, snooping membership tables can age out even while hosts remain attached ExplanationCorrect Answer A:Multicast distribution should follow explicitly defined group membership and boundary policy, not blanket flooding. This directly explains why the corrective operation is appropriate: Apply appropriate multicast boundary and scope controls for the group range. The observed acceptance evidence should be: Receivers inside scope join successfully while test receivers outside it receive no multicast payload. Incorrect Answers B:Multicast RPF checks help prevent loops by accepting traffic from the interface on the expected source path. That rule governs a different situation: A multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. Here, a training-video multicast group begins leaking beyond its approved distribution region after a transport upgrade. Multicast distribution should follow explicitly defined group membership and boundary policy, not blanket flooding. C:IGMP membership state is maintained by router queries and host reports rather than permanent discovery. That rule governs a different situation: An access VLAN loses a multicast receiver after a quiet period because periodic IGMP membership updates never reach the upstream querier. Here, a training-video multicast group begins leaking beyond its approved distribution region after a transport upgrade. Apply appropriate multicast boundary and scope controls for the group range. D:When a VLAN with multicast hosts has no functioning IGMP querier after its original gateway moves away, without a querier, snooping membership tables can age out even while hosts remain attached. By contrast, a training-video multicast group begins leaking beyond its approved distribution region after a transport upgrade; receivers inside scope join successfully while test receivers outside it receive no multicast payload.
Question 261The datacom engineering team at a cloud hosting provider after an incident review reviews this independent fictional networking case: Two directly connected OSPF routers see each other in packets but never establish a neighbor because their Hello and Dead timers differ. The team applies this remedy: Align Hello and Dead timers on the shared OSPF segment and repeat adjacency checks. Which observation would directly demonstrate that this specific issue is resolved? Both routers progress to Full adjacency and neighbor timer diagnostics agree Database description exchange completes and the OSPF neighbor reaches Full state SPF routing to the remote prefix favors the intended link and converges after the change The backbone receives the intended summary and test routes to each component subnet succeed ExplanationCorrect Answer A:Both routers progress to Full adjacency and neighbor timer diagnostics agree. This is a directly observable check for the proposed correction: Align Hello and Dead timers on the shared OSPF segment and repeat adjacency checks. The particular failure being investigated is: Two directly connected OSPF routers see each other in packets but never establish a neighbor because their Hello and Dead timers differ. Incorrect Answers B:OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change. Database description exchange completes and the OSPF neighbor reaches Full state. This observation does not prove the correction for the reported defect: Two directly connected OSPF routers see each other in packets but never establish a neighbor because their Hello and Dead timers differ. OSPF adjacency establishment requires compatible hello parameters on the neighbor-facing interfaces. C:SPF routing to the remote prefix favors the intended link and converges after the change. This check belongs to after an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed. The actual defect is different: Two directly connected OSPF routers see each other in packets but never establish a neighbor because their Hello and Dead timers differ. Align Hello and Dead timers on the shared OSPF segment and repeat adjacency checks. D:Several closely related access prefixes create unnecessary interarea LSA churn because no ABR aggregation is applied. The backbone receives the intended summary and test routes to each component subnet succeed. This observation does not prove the correction for the reported defect: Two directly connected OSPF routers see each other in packets but never establish a neighbor because their Hello and Dead timers differ. A hidden timer mismatch leaves the intended routing adjacency unavailable after every restart.
Question 262The datacom engineering team at a retail banking network as part of an acceptance test reviews this independent fictional networking case: A VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational. If this issue remains unresolved, what immediate availability or security risk follows most directly? Stale gateway MAC learning can prolong an otherwise successful VRRP switchover Local gateway survival without uplink tracking can blackhole an entire user VLAN Unplanned Master placement may steer client traffic over a less reliable exit Oversensitive BFD can cause route flapping on healthy circuits ExplanationCorrect Answer B:Local gateway survival without uplink tracking can blackhole an entire user VLAN. Leaving the exact fault unresolved means: A VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational. The intended response is: Track external-uplink health and reduce VRRP priority enough for the healthy backup to take over. 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. In that situation, stale gateway MAC learning can prolong an otherwise successful VRRP switchover. Here instead, a VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational. Virtual gateway availability must account for upstream path health, not just local gateway interface state. C:A backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. In that situation, unplanned Master placement may steer client traffic over a less reliable exit. Here instead, a VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational. Track external-uplink health and reduce VRRP priority enough for the healthy backup to take over. D:Oversensitive BFD can cause route flapping on healthy circuits. That consequence could follow when a high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling. Here, a VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational; primary uplink failure transfers Master to the router with valid outbound reachability.
Question 263The datacom engineering team at a university research campus while tracing a degraded application flow 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. The team applies this remedy: Set OSPF interface priorities to favor a stable distribution router and perform a planned election transition. Which observation would directly demonstrate that this specific issue is resolved? The designated router role moves to the planned stable device and all segment peers remain Full Neighbor state reaches Full and the link appears in both area LSDB views The relevant LSA changes, SPF runs, and the affected route moves to a healthy alternate Interarea advertisements cover only approved reachable blocks and traced flows reach valid hosts ExplanationCorrect Answer A:The designated router role moves to the planned stable device and all segment peers remain Full. This is a directly observable check for the proposed correction: Set OSPF interface priorities to favor a stable distribution router and perform a planned election transition. The particular failure being investigated is: A shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. Incorrect Answers B:Neighbor state reaches Full and the link appears in both area LSDB views. This check belongs to 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. The actual defect is different: 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:When one router continues advertising a failed transit link because the local interface reports Up while an intermediate transport component is down, a result such as this is useful: The relevant LSA changes, SPF runs, and the affected route moves to a healthy alternate. For the reported fault, 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:Interarea advertisements cover only approved reachable blocks and traced flows reach valid hosts. This check belongs to an area border router advertises a broad summary that includes subnets withdrawn after a site closure. The actual defect is different: A shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. Unplanned DR placement increases disruption when a fragile access node fails.
Question 264The datacom engineering team at a nationwide retail chain during a simulated failover test reviews this independent fictional networking case: Traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance. If this issue remains unresolved, what immediate availability or security risk follows most directly? Unrestricted management access increases credential-attack surface and potential device compromise Improper routing-instance assignment can expose one customer's traffic to another A missing fallback can prevent safe restoration during an identity infrastructure incident Overly broad reverse policy expands access while hiding the real session or routing fault ExplanationCorrect Answer B:Improper routing-instance assignment can expose one customer's traffic to another. Leaving the exact fault unresolved means: Traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance. The intended response is: Assign the service interfaces and routes to the intended VRFs and audit any explicit route leaking. Incorrect Answers A:Unrestricted management access increases credential-attack surface and potential device compromise. That consequence could follow when a router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. Here, traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance; VRFs provide separate routing tables, and cross-VRF reachability must be deliberately controlled. C:A campus authentication server becomes unreachable and network admins cannot access devices during an outage. In that situation, a missing fallback can prevent safe restoration during an identity infrastructure incident. Here instead, traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance. Assign the service interfaces and routes to the intended VRFs and audit any explicit route leaking. D:Overly broad reverse policy expands access while hiding the real session or routing fault. That consequence could follow when an administrator adds broad reverse-direction allow rules to fix response packets that should already match a healthy established session. Here, traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance; each tenant sees only approved VRF routes and prohibited cross-tenant probes fail.
Question 265The datacom engineering team at an energy distribution business while tracing a degraded application flow reviews this independent fictional networking case: A campus authentication server becomes unreachable and network admins cannot access devices during an outage. Which corrective engineering action most directly addresses this problem? Diagnose session creation and asymmetric paths instead of opening unrestricted reverse policies Test and configure a properly controlled emergency local access method consistent with AAA policy Review source/destination zone membership and adjust a narrowly scoped security-policy rule Restrict management access to approved administrative source networks and enforce strong authentication ExplanationCorrect Answer B:Test and configure a properly controlled emergency local access method consistent with AAA policy. This is the specific action that addresses the fictional fault: A campus authentication server becomes unreachable and network admins cannot access devices during an outage. The governing technical reason is: Centralized AAA improves accountability, but managed fallback must preserve both resilience and least privilege. Verify by checking: A controlled AAA outage allows an approved emergency operator and audit records document the session. Incorrect Answers A:An administrator adds broad reverse-direction allow rules to fix response packets that should already match a healthy established session. Diagnosing session creation and asymmetric paths instead of opening unrestricted reverse policies can respond to that condition, but it would not correct the reported fault: A campus authentication server becomes unreachable and network admins cannot access devices during an outage. Centralized AAA improves accountability, but managed fallback must preserve both resilience and least privilege. C:A permitted application remains blocked when crossing the Huawei firewall because the zone pairing and rule match conditions are incorrect. Reviewing source/destination zone membership and adjust a narrowly scoped security-policy rule can respond to that condition, but it would not correct the reported fault: A campus authentication server becomes unreachable and network admins cannot access devices during an outage. Test and configure a properly controlled emergency local access method consistent with AAA policy. D:When a router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign, restricting management access to approved administrative source networks and enforcing strong authentication could be appropriate. Here, a campus authentication server becomes unreachable and network admins cannot access devices during an outage. A controlled AAA outage allows an approved emergency operator and audit records document the session.
Question 266The 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. A proposed remedy is: Reconcile the actual link MTU and OSPF database exchange compatibility before retransmitting LSAs. Which technical principle most directly supports this remedy? An OSPF neighbor pair must agree on the area identity for the common link A passive OSPF interface can advertise its prefix without attempting routing adjacencies on that link OSPF routing exchanges must pass consistent authentication checks before neighbor state can advance MTU incompatibility can disrupt OSPF database description negotiation and leave neighbors partially adjacent ExplanationCorrect Answer D:MTU incompatibility can disrupt OSPF database description negotiation and leave neighbors partially adjacent. This directly explains why the corrective operation is appropriate: Reconcile the actual link MTU and OSPF database exchange compatibility before retransmitting LSAs. The observed acceptance evidence should be: Database description exchange completes and the OSPF neighbor reaches Full state. 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. An OSPF neighbor pair must agree on the area identity for the common link. The current condition differs: 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. B:When a user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance, a passive OSPF interface can advertise its prefix without attempting routing adjacencies on that link. By contrast, 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. C:OSPF routing exchanges must pass consistent authentication checks before neighbor state can advance. That principle is relevant when an OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. Here, OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change; database description exchange completes and the OSPF neighbor reaches Full state.
Question 267The datacom engineering team at a satellite ground station operator after an incident review reviews this independent fictional networking case: An iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally. Which corrective engineering action most directly addresses this problem? Apply a consistent BGP LOCAL_PREF policy to favor the primary exit for internal peers Apply explicit prefix-length-aware export policy limited to authorized aggregate space Apply next-hop-self on the appropriate border speaker or otherwise make the next hop legitimately reachable Configure the intended loopback update source and ensure loopback reachability across the IGP ExplanationCorrect Answer C:Apply next-hop-self on the appropriate border speaker or otherwise make the next hop legitimately reachable. This is the specific action that addresses the fictional fault: An iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally. The governing technical reason is: iBGP commonly preserves next-hop information, so learned routes require resolvable next hops. Verify by checking: The iBGP route becomes eligible and its next hop resolves through the IGP. Incorrect Answers A:A multihomed autonomous system sends outbound traffic via a paid backup despite the intended primary exit. Applying a consistent BGP LOCAL_PREF policy to favor the primary exit for internal peers can respond to that condition, but it would not correct the reported fault: An iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally. iBGP commonly preserves next-hop information, so learned routes require resolvable next hops. B:When an accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter, applying explicit prefix-length-aware export policy limited to authorized aggregate space could be appropriate. Here, an iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally. Apply next-hop-self on the appropriate border speaker or otherwise make the next hop legitimately reachable. D:Configuring the intended loopback update source and ensure loopback reachability across the IGP is relevant when two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses. It does not resolve this case: An iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally. The iBGP route becomes eligible and its next hop resolves through the IGP.
Question 268The 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. The team applies this remedy: Align a supported wide-metric style before deploying the higher-cost topology. Which observation would directly demonstrate that this specific issue is resolved? Each participating router reports the intended metric and selects consistent next hops Traces avoid the recovering node until readiness and return afterward without loss The intended stable router becomes DIS and the pseudonode LSP refreshes correctly L1 neighbor state establishes and the expected area routes appear ExplanationCorrect Answer A:Each participating router reports the intended metric and selects consistent next hops. This is a directly observable check for the proposed correction: Align a supported wide-metric style before deploying the higher-cost topology. The particular failure being investigated is: A new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. Incorrect Answers B:Traces avoid the recovering node until readiness and return afterward without loss. This check belongs to a router recovering from reboot begins attracting transit traffic before its route state is ready. The actual defect 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. For cross-border logistics provider after a monitored link change, the acceptance test should show that each participating router reports the intended metric and selects consistent next hops. C:The intended stable router becomes DIS and the pseudonode LSP refreshes correctly. That result could validate a repair when a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. 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: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. This observation does not prove the correction for the reported defect: A new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. Mixed metric interpretation can produce route divergence and unstable path choices.
Question 269The datacom engineering team at an energy distribution business while tracing a degraded application flow reviews this independent fictional networking case: A border router tags specific prefixes but the provider does not apply the expected regional no-export treatment. A proposed remedy is: Validate the community value, propagation policy, and provider-supported meaning before relying on it. Which technical principle most directly supports this remedy? Route distinguishers distinguish otherwise identical VPN address advertisements; they do not themselves control import permission BGP best-path attributes are evaluated in a defined order; shorter AS_PATH is not always the first deciding factor Route reflection replaces full-mesh iBGP peering while preserving loop-prevention attributes BGP communities convey policy intent but require receiving-network policy to interpret them ExplanationCorrect Answer D:BGP communities convey policy intent but require receiving-network policy to interpret them. This directly explains why the corrective operation is appropriate: Validate the community value, propagation policy, and provider-supported meaning before relying on it. The observed acceptance evidence should be: Adjacent peers show the expected communities and external advertisements are scoped as contracted. Incorrect Answers A: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. The current condition differs: A border router tags specific prefixes but the provider does not apply the expected regional no-export treatment. BGP communities convey policy intent but require receiving-network policy to interpret them. B:When operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference, BGP best-path attributes are evaluated in a defined order; shorter AS_PATH is not always the first deciding factor. By contrast, a border router tags specific prefixes but the provider does not apply the expected regional no-export treatment; validate the community value, propagation policy, and provider-supported meaning before relying on it. C:Route reflection replaces full-mesh iBGP peering while preserving loop-prevention attributes. That rule governs a different situation: A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Here, a border router tags specific prefixes but the provider does not apply the expected regional no-export treatment. Adjacent peers show the expected communities and external advertisements are scoped as contracted.
Question 270The datacom engineering team at a university hospital during a network security audit reviews this independent fictional networking case: 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. If this issue remains unresolved, what immediate availability or security risk follows most directly? A fragmented OSPF backbone can split route exchange between otherwise healthy areas Active routing hellos on user ports expand an unnecessary adjacency attack surface An unresolved area mismatch isolates prefixes even when IP reachability across the segment works Over-aggregation can turn an ABR into a black hole for withdrawn subnets ExplanationCorrect Answer C:An unresolved area mismatch isolates prefixes even when IP reachability across the segment works. Leaving the exact fault unresolved means: 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. The intended response is: Correct the interface area assignment after confirming the intended area boundary. Incorrect Answers A:Two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. In that situation, a fragmented OSPF backbone can split route exchange between otherwise healthy areas. Here instead, 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. An OSPF neighbor pair must agree on the area identity for the common link. B:Active routing hellos on user ports expand an unnecessary adjacency attack surface. That risk belongs to a separate condition: A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. Here, 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; correct the interface area assignment after confirming the intended area boundary. D:When an area border router advertises a broad summary that includes subnets withdrawn after a site closure, over-aggregation can turn an ABR into a black hole for withdrawn subnets. The present failure is different: 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. Neighbor state reaches Full and the link appears in both area LSDB views.