Question 720The datacom engineering team at a call center outsourcer after a planned hardware refresh reviews this independent fictional networking case: An engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. The team applies this remedy: Validate stub-area configuration and ensure the ABR advertises the intended default route into the area. 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 Remote OSPF routers receive the summary and reach all intended attached external subnets Branch route tables contain the intended default rather than the unexpected interarea prefixes The ABR default route appears in the stub area and external destinations remain reachable ExplanationCorrect Answer D:The ABR default route appears in the stub area and external destinations remain reachable. This is a directly observable check for the proposed correction: Validate stub-area configuration and ensure the ABR advertises the intended default route into the area. The particular failure being investigated is: An engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. Incorrect Answers A: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: 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. B:Remote OSPF routers receive the summary and reach all intended attached external subnets. This check belongs to an ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. The actual defect is different: An engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. Validate stub-area configuration and ensure the ABR advertises the intended default route into the area. C:Branch route tables contain the intended default rather than the unexpected interarea prefixes. That result could validate a repair when branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. Here, an engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault; incorrect assumptions about stub behavior can lead to unnecessary area redesign or missing external access.
Question 721The datacom engineering team at a regional health network during a controlled network cutover 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. The team applies this remedy: Assign the service interfaces and routes to the intended VRFs and audit any explicit route leaking. Which observation would directly demonstrate that this specific issue is resolved? Tunnel SA counters increase for the approved subnet and remote application traffic succeeds Session/NAT records and bidirectional traces show the intended translated tuple and next hop Guest-originated SSH probes are rejected while approved administrative access continues Each tenant sees only approved VRF routes and prohibited cross-tenant probes fail ExplanationCorrect Answer D:Each tenant sees only approved VRF routes and prohibited cross-tenant probes fail. This is a directly observable check for the proposed correction: Assign the service interfaces and routes to the intended VRFs and audit any explicit route leaking. The particular failure being investigated is: Traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance. Incorrect Answers A:Two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree. Tunnel SA counters increase for the approved subnet and remote application traffic succeeds. This observation does not prove the correction for the reported defect: 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. B:A firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. Session/NAT records and bidirectional traces show the intended translated tuple and next hop. This observation does not prove the correction for the reported defect: 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. C:When a router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign, a result such as this is useful: Guest-originated SSH probes are rejected while approved administrative access continues. For the reported fault, traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance; improper routing-instance assignment can expose one customer's traffic to another.
Question 722The 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. Which corrective engineering action most directly addresses this problem? Set compatible IS-IS circuit levels consistent with the core design Align the IS-IS area portion of the NET or revise the intended L1/L2 boundary Tune IS-IS DIS priority on the shared LAN and validate neighbor continuity after a planned election Apply a controlled IS-IS overload period during startup and remove it after routing readiness ExplanationCorrect Answer B:Align the IS-IS area portion of the NET or revise the intended L1/L2 boundary. This is the specific action that addresses the fictional fault: Two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses. The governing technical reason is: Level-1 IS-IS neighbors must belong to a compatible area while Level-2 can connect areas. Verify by checking: L1 neighbor state establishes and the expected area routes appear. Incorrect Answers A:When a transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2, setting compatible IS-IS circuit levels consistent with the core design could be appropriate. Here, 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. C:Tuning IS-IS DIS priority on the shared LAN and validating neighbor continuity after a planned election is relevant when a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. It does not resolve this case: 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:When a router recovering from reboot begins attracting transit traffic before its route state is ready, applying a controlled IS-IS overload period during startup and removing it after routing readiness could be appropriate. 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 723The datacom engineering team at a university research campus while tracing a degraded application flow reviews this independent fictional networking case: Policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. If this issue remains unresolved, what immediate availability or security risk follows most directly? Misplaced filters allow an unintended trust-boundary crossing without visible policy errors An unchecked PBR next hop can isolate selected users while general connectivity appears normal The wrong QoS mechanism causes avoidable burst packet loss and user-visible media glitches Broad redistribution can expose internal topology and destabilize edge routing ExplanationCorrect Answer B:An unchecked PBR next hop can isolate selected users while general connectivity appears normal. Leaving the exact fault unresolved means: Policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. The intended response is: Add health-aware policy-path handling or withdraw the policy on next-hop failure. Incorrect Answers A:Misplaced filters allow an unintended trust-boundary crossing without visible policy errors. That risk belongs to a separate condition: A security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. Here, policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path; PBR intentionally overrides ordinary routing and can therefore preserve a failed forwarding decision. C:A WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. In that situation, the wrong QoS mechanism causes avoidable burst packet loss and user-visible media glitches. Here instead, policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. Add health-aware policy-path handling or withdraw the policy on next-hop failure. D:Broad redistribution can expose internal topology and destabilize edge routing. That consequence could follow when a border router injects internal transit and management prefixes into external BGP due to unrestricted redistribution. Here, policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path; policy test traffic fails over to the approved inspection path and maintains documented controls.
Question 724The 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. The team applies this remedy: Apply next-hop-self on the appropriate border speaker or otherwise make the next hop legitimately reachable. Which observation would directly demonstrate that this specific issue is resolved? The EVPN address-family neighbor state and advertised route types appear as expected The target instance imports only matching tenant routes and no unrelated VRF routes appear All clients learn the intended prefixes and remain connected after a reflector failover The iBGP route becomes eligible and its next hop resolves through the IGP ExplanationCorrect Answer D:The iBGP route becomes eligible and its next hop resolves through the IGP. This is a directly observable check for the proposed correction: Apply next-hop-self on the appropriate border speaker or otherwise make the next hop legitimately reachable. The particular failure being investigated is: An iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally. Incorrect Answers A:When an EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes, a result such as this is useful: The EVPN address-family neighbor state and advertised route types appear as expected. For 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: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. This observation does not prove the correction for the reported defect: 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. C:All clients learn the intended prefixes and remain connected after a reflector failover. This check belongs to a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. The actual defect is different: An iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally. A valid-looking iBGP route may be unusable when the external next hop is unresolved.
Question 725The datacom engineering team at an energy distribution business while tracing a degraded application flow reviews this independent fictional networking case: A large lecture hall experiences low Wi-Fi throughput even with strong signal because neighboring AP radios overlap excessively on busy channels. A proposed remedy is: Replan channel assignments and transmit power based on measured co-channel contention. Which technical principle most directly supports this remedy? WLAN access enforcement must combine authenticated identity with the corresponding least-privilege network role Central WLAN control architectures require planned control-plane redundancy and AP recovery behavior Strong RSSI does not guarantee throughput; overlapping airtime competition reduces usable capacity RSTP alternate ports are designed to become forwarding backups after topology changes ExplanationCorrect Answer C:Strong RSSI does not guarantee throughput; overlapping airtime competition reduces usable capacity. This directly explains why the corrective operation is appropriate: Replan channel assignments and transmit power based on measured co-channel contention. The observed acceptance evidence should be: Spectrum survey and client test show lower channel utilization and higher effective throughput. Incorrect Answers A: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 large lecture hall experiences low Wi-Fi throughput even with strong signal because neighboring AP radios overlap excessively on busy channels. Strong RSSI does not guarantee throughput; overlapping airtime competition reduces usable capacity. 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 large lecture hall experiences low Wi-Fi throughput even with strong signal because neighboring AP radios overlap excessively on busy channels. Replan channel assignments and transmit power based on measured co-channel contention. D:RSTP alternate ports are designed to become forwarding backups after topology changes. That rule governs a different situation: A redundant access uplink stays blocked even after the active link fails because the switch has not converged its port roles correctly. Here, a large lecture hall experiences low Wi-Fi throughput even with strong signal because neighboring AP radios overlap excessively on busy channels. Spectrum survey and client test show lower channel utilization and higher effective throughput.
Question 726The datacom engineering team at a sports event venue during a topology consistency review reviews this independent fictional networking case: A routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes. Which corrective engineering action most directly addresses this problem? Constrain ge/le mask-length ranges and test boundary prefix acceptance Apply a narrowly matched import/export route policy during protocol redistribution Place the filter on the correct ingress or egress direction based on the observed packet path Add health-aware policy-path handling or withdraw the policy on next-hop failure ExplanationCorrect Answer A:Constrain ge/le mask-length ranges and test boundary prefix acceptance. This is the specific action that addresses the fictional fault: A routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes. The governing technical reason is: A prefix-list entry's address and mask-length matching must both reflect the authorization boundary. Verify by checking: Tests accept the approved /24 and reject longer unauthorized prefixes. Incorrect Answers B:A border router injects internal transit and management prefixes into external BGP due to unrestricted redistribution. Applying a narrowly matched import/export route policy during protocol redistribution can respond to that condition, but it would not correct the reported fault: A routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes. A prefix-list entry's address and mask-length matching must both reflect the authorization boundary. C:A security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. Placing the filter on the correct ingress or egress direction based on the observed packet path can respond to that condition, but it would not correct the reported fault: A routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes. Constrain ge/le mask-length ranges and test boundary prefix acceptance. D:Policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. Adding health-aware policy-path handling or withdraw the policy on next-hop failure can respond to that condition, but it would not correct the reported fault: A routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes. Tests accept the approved /24 and reject longer unauthorized prefixes.
Question 727The datacom engineering team at a warehouse automation provider during a topology consistency review reviews this independent fictional networking case: A new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad. The team applies this remedy: Reorder and narrow the matching conditions so explicit permitted prefixes are evaluated before the general deny. Which observation would directly demonstrate that this specific issue is resolved? Capture on both sides confirms expected DSCP values and queue counters reflect the correct class Matched-rule counters and received-route sets show only intended prefixes accepted Burst loss decreases while sustained throughput remains within the agreed service rate Classifier counters rise for real voice flows and the intended behavior is applied ExplanationCorrect Answer B:Matched-rule counters and received-route sets show only intended prefixes accepted. This is a directly observable check for the proposed correction: Reorder and narrow the matching conditions so explicit permitted prefixes are evaluated before the general deny. The particular failure being investigated is: A new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad. Incorrect Answers A:Capture on both sides confirms expected DSCP values and queue counters reflect the correct class. That result could validate a repair when delay-sensitive packets leave the campus with voice markings but are remarked to best-effort at a trusted border. Here, a new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad; sequential route-policy matches can terminate evaluation and make later rules unreachable. C:Burst loss decreases while sustained throughput remains within the agreed service rate. This check belongs to a WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. The actual defect is different: A new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad. Reorder and narrow the matching conditions so explicit permitted prefixes are evaluated before the general deny. D:Classifier counters rise for real voice flows and the intended behavior is applied. That result could validate a repair when a voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns. Here, a new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad; broad early deny rules can remove reachable customer networks with no physical fault.
Question 728The datacom engineering team at a wholesale market association while tracing a degraded application flow reviews this independent fictional networking case: Traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. If this issue remains unresolved, what immediate availability or security risk follows most directly? Accidental region borders reduce planned load sharing and may alter blocked ports Misaligned instance mappings can strand a subset of VLANs while others work Single-member attachment can defeat apparent logical redundancy An unintended root can redirect traffic through a fragile uplink and amplify outages ExplanationCorrect Answer B:Misaligned instance mappings can strand a subset of VLANs while others work. Leaving the exact fault unresolved means: Traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. The intended response is: Align VLAN-to-instance mappings and regional parameters across the MST region. Incorrect Answers A:When two switches intended in one MSTP region behave as if separated by a regional boundary after an unnoticed configuration edit, accidental region borders reduce planned load sharing and may alter blocked ports. The present failure is different: Traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. MSTP topology behavior is per instance and consistent VLAN mapping is necessary for predictable forwarding. C:When a stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed, single-member attachment can defeat apparent logical redundancy. The present failure is different: Traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. Align VLAN-to-instance mappings and regional parameters across the MST region. D:A low-capacity access switch becomes the spanning-tree root because its bridge priority was left lower than the distribution pair. In that situation, an unintended root can redirect traffic through a fragile uplink and amplify outages. Here instead, traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. Region digest and per-VLAN instance port roles match at the neighbors.
Question 729The datacom engineering team at a municipal transport operator during a simulated failover test reviews this independent fictional networking case: A WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. The team applies this remedy: Apply appropriate traffic shaping at the controlled egress and verify contracted rate behavior. Which observation would directly demonstrate that this specific issue is resolved? Burst loss decreases while sustained throughput remains within the agreed service rate The BGP advertisement list excludes internal infrastructure prefixes while approved service routes remain Classifier counters rise for real voice flows and the intended behavior is applied Policy test traffic fails over to the approved inspection path and maintains documented controls ExplanationCorrect Answer A:Burst loss decreases while sustained throughput remains within the agreed service rate. This is a directly observable check for the proposed correction: Apply appropriate traffic shaping at the controlled egress and verify contracted rate behavior. The particular failure being investigated is: A WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. Incorrect Answers B:The BGP advertisement list excludes internal infrastructure prefixes while approved service routes remain. This check belongs to a border router injects internal transit and management prefixes into external BGP due to unrestricted redistribution. The actual defect is different: A WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. Policing enforces a rate by remarking or dropping excess traffic, whereas shaping buffers excess bursts for later transmission. C:When a voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns, a result such as this is useful: Classifier counters rise for real voice flows and the intended behavior is applied. For the reported fault, a WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective; apply appropriate traffic shaping at the controlled egress and verify contracted rate behavior. D:Policy test traffic fails over to the approved inspection path and maintains documented controls. This check belongs to policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. The actual defect is different: A WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. The wrong QoS mechanism causes avoidable burst packet loss and user-visible media glitches. For municipal transport operator during a simulated failover test, the acceptance test should show that burst loss decreases while sustained throughput remains within the agreed service rate.
Question 730The datacom engineering team at a government service campus after a monitored link change reviews this independent fictional networking case: A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. The team applies this remedy: Introduce a correctly designed iBGP route reflector cluster with appropriate clients and redundancy. Which observation would directly demonstrate that this specific issue is resolved? All clients learn the intended prefixes and remain connected after a reflector failover Session source addresses match loopbacks and both peers establish consistently The EVPN address-family neighbor state and advertised route types appear as expected EVPN control-plane entries retain unique per-origin VPN identifiers and remote paths coexist ExplanationCorrect Answer A:All clients learn the intended prefixes and remain connected after a reflector failover. This is a directly observable check for the proposed correction: Introduce a correctly designed iBGP route reflector cluster with appropriate clients and redundancy. The particular failure being investigated is: A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Incorrect Answers B:Session source addresses match loopbacks and both peers establish consistently. That result could validate a repair when two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses. Here, a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution; route reflection replaces full-mesh iBGP peering while preserving loop-prevention attributes. C:An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. The EVPN address-family neighbor state and advertised route types appear as expected. This observation does not prove the correction for the reported defect: A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Introduce a correctly designed iBGP route reflector cluster with appropriate clients and redundancy. D:EVPN control-plane entries retain unique per-origin VPN identifiers and remote paths coexist. That result could validate a repair when two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. Here, a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution; partial iBGP distribution can hide routes from only some leaf devices.