Question 320The datacom engineering team at a distribution warehouse group during a simulated failover test reviews this independent fictional networking case: An accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. The team applies this remedy: Apply explicit prefix-length-aware export policy limited to authorized aggregate space. Which observation would directly demonstrate that this specific issue is resolved? The upstream reports intended MED attributes and observed ingress tracks the agreed policy The EVPN address-family neighbor state and advertised route types appear as expected The iBGP route becomes eligible and its next hop resolves through the IGP Exported BGP routes contain only the authorized prefix and mask set ExplanationCorrect Answer D:Exported BGP routes contain only the authorized prefix and mask set. This is a directly observable check for the proposed correction: Apply explicit prefix-length-aware export policy limited to authorized aggregate space. The particular failure being investigated is: An accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. Incorrect Answers A:When two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned, a result such as this is useful: The upstream reports intended MED attributes and observed ingress tracks the agreed policy. For the reported fault, an accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter; prefix lists and route policies should enforce precise permitted address and mask ranges at external boundaries. B: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: An accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. Apply explicit prefix-length-aware export policy limited to authorized aggregate space. C:When an iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally, a result such as this is useful: The iBGP route becomes eligible and its next hop resolves through the IGP. For the reported fault, an accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter; an unrestricted export policy may leak internal infrastructure addresses beyond the organization.
Question 321The datacom engineering team at a film production studio as part of an acceptance test reviews this independent fictional networking case: An accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. Which corrective engineering action most directly addresses this problem? Apply explicit prefix-length-aware export policy limited to authorized aggregate space Inspect the BGP best-path decision sequence and correct the higher-priority policy attribute before modifying AS_PATH Apply provider-approved AS_PATH prepending or another suitable inbound policy while recognizing remote policy precedence Apply a consistent BGP LOCAL_PREF policy to favor the primary exit for internal peers ExplanationCorrect Answer A:Apply explicit prefix-length-aware export policy limited to authorized aggregate space. This is the specific action that addresses the fictional fault: An accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. The governing technical reason is: Prefix lists and route policies should enforce precise permitted address and mask ranges at external boundaries. Verify by checking: Exported BGP routes contain only the authorized prefix and mask set. Incorrect Answers B:Operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. This is where inspecting the BGP best-path decision sequence and correcting the higher-priority policy attribute before modifying AS_PATH would help. By contrast, an accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. Prefix lists and route policies should enforce precise permitted address and mask ranges at external boundaries. C:An enterprise wants to influence how some external networks enter its secondary ISP, but it changes local preference inside its own AS instead. This is where applying provider-approved AS_PATH prepending or another suitable inbound policy while recognizing remote policy precedence would help. By contrast, an accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. Apply explicit prefix-length-aware export policy limited to authorized aggregate space. D:A multihomed autonomous system sends outbound traffic via a paid backup despite the intended primary exit. This is where applying a consistent BGP LOCAL_PREF policy to favor the primary exit for internal peers would help. By contrast, an accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. Exported BGP routes contain only the authorized prefix and mask set.
Question 322The datacom engineering team at a financial clearing service during a network security audit reviews this independent fictional networking case: An enterprise wants to influence how some external networks enter its secondary ISP, but it changes local preference inside its own AS instead. Which corrective engineering action most directly addresses this problem? Apply a consistent BGP LOCAL_PREF policy to favor the primary exit for internal peers Audit reflector topology and preserve the standard ORIGINATOR_ID and CLUSTER_LIST loop controls Apply provider-approved AS_PATH prepending or another suitable inbound policy while recognizing remote policy precedence Introduce a correctly designed iBGP route reflector cluster with appropriate clients and redundancy ExplanationCorrect Answer C:Apply provider-approved AS_PATH prepending or another suitable inbound policy while recognizing remote policy precedence. This is the specific action that addresses the fictional fault: An enterprise wants to influence how some external networks enter its secondary ISP, but it changes local preference inside its own AS instead. The governing technical reason is: AS_PATH attributes can influence external path selection but cannot guarantee behavior against other operators' policies. Verify by checking: External route views show the intended prepended announcement and measured ingress path changes when supported. Incorrect Answers A:When 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 could be appropriate. Here, an enterprise wants to influence how some external networks enter its secondary ISP, but it changes local preference inside its own AS instead. AS_PATH attributes can influence external path selection but cannot guarantee behavior against other operators' policies. B:An iBGP route reflected through overlapping clusters returns toward its originator unexpectedly. Auditing reflector topology and preserving the standard ORIGINATOR_ID and CLUSTER_LIST loop controls can respond to that condition, but it would not correct the reported fault: An enterprise wants to influence how some external networks enter its secondary ISP, but it changes local preference inside its own AS instead. Apply provider-approved AS_PATH prepending or another suitable inbound policy while recognizing remote policy precedence. D:Introducing a correctly designed iBGP route reflector cluster with appropriate clients and redundancy is relevant when a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. It does not resolve this case: An enterprise wants to influence how some external networks enter its secondary ISP, but it changes local preference inside its own AS instead. External route views show the intended prepended announcement and measured ingress path changes when supported.
Question 323The datacom engineering team at a local rail transit network while validating change-control evidence reviews this independent fictional networking case: A multicast source in a sparse-mode domain sends traffic but remote listeners receive nothing because the routers have inconsistent RP mappings. A proposed remedy is: Configure a consistent appropriate rendezvous point mapping and inspect source registration paths. Which technical principle most directly supports this remedy? IGMP membership state is maintained by router queries and host reports rather than permanent discovery PIM-DM initially floods and then prunes branches without receivers Multicast RPF checks help prevent loops by accepting traffic from the interface on the expected source path PIM-SM uses an RP to build initial shared-tree reachability for ASM groups ExplanationCorrect Answer D:PIM-SM uses an RP to build initial shared-tree reachability for ASM groups. This directly explains why the corrective operation is appropriate: Configure a consistent appropriate rendezvous point mapping and inspect source registration paths. The observed acceptance evidence should be: RP mappings agree and receivers establish expected PIM joins with working source traffic. Incorrect Answers A: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 multicast source in a sparse-mode domain sends traffic but remote listeners receive nothing because the routers have inconsistent RP mappings. PIM-SM uses an RP to build initial shared-tree reachability for ASM groups. B:PIM-DM initially floods and then prunes branches without receivers. That rule governs a different situation: A dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent. Here, a multicast source in a sparse-mode domain sends traffic but remote listeners receive nothing because the routers have inconsistent RP mappings. Configure a consistent appropriate rendezvous point mapping and inspect source registration paths. C: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. The current condition differs: A multicast source in a sparse-mode domain sends traffic but remote listeners receive nothing because the routers have inconsistent RP mappings. RP mappings agree and receivers establish expected PIM joins with working source traffic.
Question 324The datacom engineering team at an insurance processing company while validating change-control evidence reviews this independent fictional networking case: A redundant access uplink stays blocked even after the active link fails because the switch has not converged its port roles correctly. If this issue remains unresolved, what immediate availability or security risk follows most directly? An unintended root can redirect traffic through a fragile uplink and amplify outages Accidental region borders reduce planned load sharing and may alter blocked ports Failure of rapid transition turns redundant cabling into an outage rather than resilience Unprotected edge ports can introduce layer-2 loops that overwhelm shared broadcast segments ExplanationCorrect Answer C:Failure of rapid transition turns redundant cabling into an outage rather than resilience. Leaving the exact fault unresolved means: A redundant access uplink stays blocked even after the active link fails because the switch has not converged its port roles correctly. The intended response is: Inspect RSTP role/state exchanges and fix the inconsistent neighbor port configuration. Incorrect Answers A:When a low-capacity access switch becomes the spanning-tree root because its bridge priority was left lower than the distribution pair, an unintended root can redirect traffic through a fragile uplink and amplify outages. The present failure is different: A redundant access uplink stays blocked even after the active link fails because the switch has not converged its port roles correctly. RSTP alternate ports are designed to become forwarding backups after topology changes. B:Accidental region borders reduce planned load sharing and may alter blocked ports. That consequence could follow when two switches intended in one MSTP region behave as if separated by a regional boundary after an unnoticed configuration edit. Here, a redundant access uplink stays blocked even after the active link fails because the switch has not converged its port roles correctly; inspect RSTP role/state exchanges and fix the inconsistent neighbor port configuration. D:Unprotected edge ports can introduce layer-2 loops that overwhelm shared broadcast segments. That risk belongs to a separate condition: A user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port. Here, a redundant access uplink stays blocked even after the active link fails because the switch has not converged its port roles correctly; the alternate link transitions to forwarding after a controlled primary failure without sustained loop.
Question 325The datacom engineering team at an automotive parts manufacturer as part of an acceptance test reviews this independent fictional networking case: A distant receiver continues using a long shared tree after a short direct source path is available and capacity is strained. The team applies this remedy: Validate PIM-SM source-specific shortest-path switching and the unicast route toward the source. Which observation would directly demonstrate that this specific issue is resolved? The receiver joins the intended source/group pair and cannot accidentally switch to a different sender RPF diagnostics name the arriving interface as valid and the downstream stream resumes The non-listener branch stops receiving the data after valid prune processing The multicast route table reflects an intended source-specific incoming interface and latency improves ExplanationCorrect Answer D:The multicast route table reflects an intended source-specific incoming interface and latency improves. This is a directly observable check for the proposed correction: Validate PIM-SM source-specific shortest-path switching and the unicast route toward the source. The particular failure being investigated is: A distant receiver continues using a long shared tree after a short direct source path is available and capacity is strained. Incorrect Answers A:The receiver joins the intended source/group pair and cannot accidentally switch to a different sender. That result could validate a repair when a receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. Here, a distant receiver continues using a long shared tree after a short direct source path is available and capacity is strained; PIM-SM can transition from a shared tree to a source-specific tree when route and policy permit. B:A multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. RPF diagnostics name the arriving interface as valid and the downstream stream resumes. This observation does not prove the correction for the reported defect: A distant receiver continues using a long shared tree after a short direct source path is available and capacity is strained. Validate PIM-SM source-specific shortest-path switching and the unicast route toward the source. C:The non-listener branch stops receiving the data after valid prune processing. That result could validate a repair when a dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent. Here, a distant receiver continues using a long shared tree after a short direct source path is available and capacity is strained; persistent shared-tree detours can congest core links and degrade streaming performance.
Question 326The datacom engineering team at an airport facilities team while tracing a degraded application flow 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? During a planned circuit interruption, BFD detects failure and routing reconverges within the operational target The planned primary device owns the virtual gateway after recovery and failover still works Both peers display Up state and a controlled liveness fault produces a consistent Down event The static route is active and its recursive next hop resolves to an operational interface ExplanationCorrect Answer B: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:During a planned circuit interruption, BFD detects failure and routing reconverges within the operational target. This check belongs to OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection. The actual defect is different: 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:Two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior. Both peers display Up state and a controlled liveness fault produces a consistent Down event. 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:The static route is active and its recursive next hop resolves to an operational interface. That result could validate a repair when a static route is configured to a next-hop address that is absent from the local routing table and never becomes active. Here, 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 327The datacom engineering team at a cloud hosting provider after an incident review 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? Check supported BFD modes and mutually acceptable timer negotiation before coupling routing failover Verify the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover Enable supported BFD tracking for the OSPF adjacency and validate timer compatibility Tune BFD intervals and multiplier for supported device and transport capabilities ExplanationCorrect Answer D: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:Checking supported BFD modes and mutually acceptable timer negotiation before coupling routing failover is relevant when two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior. It does not resolve this case: 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:When a host keeps sending traffic to the old gateway's MAC after a VRRP switchover because the access LAN fails to update its neighbor cache, verifying the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover could be appropriate. Here, 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. C: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 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 328The datacom engineering team at an automotive parts manufacturer as part of an acceptance test reviews this independent fictional networking case: A voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns. If this issue remains unresolved, what immediate availability or security risk follows most directly? Redistribution feedback can create loops, unstable metrics, and widespread convergence churn Unnoticed remarking causes traffic to lose its intended service priority across domains Broad redistribution can expose internal topology and destabilize edge routing Misclassified real-time traffic may be dropped despite an apparently configured priority queue ExplanationCorrect Answer D:Misclassified real-time traffic may be dropped despite an apparently configured priority queue. Leaving the exact fault unresolved means: A voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns. The intended response is: Align ingress marking and MQC traffic-classifier matching before adjusting queue parameters. Incorrect Answers A:When two redistribution points repeatedly re-inject learned routes between OSPF and another IGP and churn route entries, redistribution feedback can create loops, unstable metrics, and widespread convergence churn. The present failure is different: 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. B:When delay-sensitive packets leave the campus with voice markings but are remarked to best-effort at a trusted border, unnoticed remarking causes traffic to lose its intended service priority across domains. The present failure is different: A voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns. Align ingress marking and MQC traffic-classifier matching before adjusting queue parameters. C:A border router injects internal transit and management prefixes into external BGP due to unrestricted redistribution. In that situation, broad redistribution can expose internal topology and destabilize edge routing. Here instead, a voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns. Classifier counters rise for real voice flows and the intended behavior is applied.
Question 329The datacom engineering team at a public water utility during a topology consistency review reviews this independent fictional networking case: A firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. Which corrective engineering action most directly addresses this problem? Align the protected subnet selectors and routing for the authorized tunnel traffic Restrict management access to approved administrative source networks and enforce strong authentication Diagnose session creation and asymmetric paths instead of opening unrestricted reverse policies Validate NAT rule matching and the effective route lookup for the translated flow ExplanationCorrect Answer D:Validate NAT rule matching and the effective route lookup for the translated flow. This is the specific action that addresses the fictional fault: A firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. The governing technical reason is: NAT changes packet addressing, but traffic still requires a correct routed egress and return path. Verify by checking: Session/NAT records and bidirectional traces show the intended translated tuple and next hop. Incorrect Answers A:When two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree, aligning the protected subnet selectors and routing for the authorized tunnel traffic could be appropriate. Here, a firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. NAT changes packet addressing, but traffic still requires a correct routed egress and return path. B:A router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. This is where restricting management access to approved administrative source networks and enforcing strong authentication would help. By contrast, a firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. Validate NAT rule matching and the effective route lookup for the translated flow. C:Diagnosing session creation and asymmetric paths instead of opening unrestricted reverse policies is relevant when an administrator adds broad reverse-direction allow rules to fix response packets that should already match a healthy established session. It does not resolve this case: 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.
Question 330The datacom engineering team at a maritime terminal after a monitored link change reviews this independent fictional networking case: A transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2. The team applies this remedy: Set compatible IS-IS circuit levels consistent with the core design. Which observation would directly demonstrate that this specific issue is resolved? Authentication failures cease and level-appropriate neighbor state returns Up Each participating router reports the intended metric and selects consistent next hops The intended stable router becomes DIS and the pseudonode LSP refreshes correctly The peer adjacency is Up at the intended level and corresponding LSPs exchange ExplanationCorrect Answer D:The peer adjacency is Up at the intended level and corresponding LSPs exchange. This is a directly observable check for the proposed correction: Set compatible IS-IS circuit levels consistent with the core design. The particular failure being investigated is: A transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2. Incorrect Answers A:Authentication failures cease and level-appropriate neighbor state returns Up. That result could validate a repair when an IS-IS adjacency drops after only one of two core routers receives a new authentication key. Here, 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. B:Each participating router reports the intended metric and selects consistent next hops. This check belongs to a new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. The actual defect is different: A transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2. Set compatible IS-IS circuit levels consistent with the core design. C: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. This observation does not prove the correction for the reported defect: A transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2. Level mismatches can isolate the core despite both routers advertising IS-IS globally.