Question 430The datacom engineering team at a retail banking network as part of an acceptance test 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. Which corrective engineering action most directly addresses this problem? Apply appropriate traffic shaping at the controlled egress and verify contracted rate behavior Align ingress marking and MQC traffic-classifier matching before adjusting queue parameters Restore symmetric service-chain routing or a supported state-sharing design Add health-aware policy-path handling or withdraw the policy on next-hop failure ExplanationCorrect Answer D:Add health-aware policy-path handling or withdraw the policy on next-hop failure. This is the specific action that addresses the fictional fault: Policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. The governing technical reason is: PBR intentionally overrides ordinary routing and can therefore preserve a failed forwarding decision. Verify by checking: Policy test traffic fails over to the approved inspection path and maintains documented controls. Incorrect Answers A:Applying appropriate traffic shaping at the controlled egress and verifying contracted rate behavior is relevant when a WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. It does not resolve this case: 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. B:A voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns. This is where aligning ingress marking and MQC traffic-classifier matching before adjusting queue parameters would help. By contrast, 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. C:A stateful firewall intermittently drops responses after equal-cost routing spreads the forward and return flows across unrelated inspection nodes. Restoring symmetric service-chain routing or a supported state-sharing design can respond to that condition, but it would not correct the reported fault: 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 431The datacom engineering team at a health laboratory network after a planned hardware refresh 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? Verify and correct both configured local and peer autonomous system identities Audit reflector topology and preserve the standard ORIGINATOR_ID and CLUSTER_LIST loop controls Apply next-hop-self on the appropriate border speaker or otherwise make the next hop legitimately reachable Assign route distinguishers suitable for creating unique originating VPN route identifiers 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:An edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS. Verifying and correcting both configured local and peer autonomous system identities 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:Auditing reflector topology and preserving the standard ORIGINATOR_ID and CLUSTER_LIST loop controls is relevant when an iBGP route reflected through overlapping clusters returns toward its originator unexpectedly. 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. Apply next-hop-self on the appropriate border speaker or otherwise make the next hop legitimately reachable. D:When two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly, assigning route distinguishers suitable for creating unique originating VPN route identifiers could be appropriate. Here, 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 432The datacom engineering team at a library district network after a planned hardware refresh 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. If this issue remains unresolved, what immediate availability or security risk follows most directly? Failed RPF can interrupt multicast while unicast service tests still succeed A missing prune wastes bandwidth across links with no subscribed receivers Expired host state can cause intermittent multicast loss without underlying link failures Misapplied ASM behavior can select an unintended stream source and undermine access expectations ExplanationCorrect Answer A:Failed RPF can interrupt multicast while unicast service tests still succeed. Leaving the exact fault unresolved means: A multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. The intended response is: Verify the multicast RPF route and correct source reachability or appropriate multicast routing state. Incorrect Answers B:When a dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent, a missing prune wastes bandwidth across links with no subscribed receivers. The present failure is different: 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:When an access VLAN loses a multicast receiver after a quiet period because periodic IGMP membership updates never reach the upstream querier, expired host state can cause intermittent multicast loss without underlying link failures. The present failure is different: 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:A receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. In that situation, misapplied ASM behavior can select an unintended stream source and undermine access expectations. Here instead, 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.
Question 433The datacom engineering team at a pharmaceutical testing firm after a planned hardware refresh reviews this independent fictional networking case: Tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. Which corrective engineering action most directly addresses this problem? Repair next-hop recursion and underlying IGP convergence, not just the BGP session Correct matching export and import route-target policy for the tenant instance Review the upstream's MED handling and advertise the intended metric on comparable links Set an appropriate maximum-prefix threshold and test the negotiated recovery behavior ExplanationCorrect Answer B:Correct matching export and import route-target policy for the tenant instance. This is the specific action that addresses the fictional fault: Tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. The governing technical reason is: EVPN route targets control which VPN routes a receiving instance is permitted to import. Verify by checking: The target instance imports only matching tenant routes and no unrelated VRF routes appear. Incorrect Answers A:A BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. This is where repairing next-hop recursion and underlying IGP convergence, not just the BGP session would help. By contrast, 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. C:When two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned, reviewing the upstream's MED handling and advertise the intended metric on comparable links could be appropriate. Here, tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. Correct matching export and import route-target policy for the tenant instance. D:Setting an appropriate maximum-prefix threshold and testing the negotiated recovery behavior is relevant when a provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. It does not resolve this case: 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.
Question 434The 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. If this issue remains unresolved, what immediate availability or security risk follows most directly? Diagnosing BGP policy before basic transport can prolong an otherwise simple outage An unrestricted export policy may leak internal infrastructure addresses beyond the organization Untested community handling can leak routes outside an intended operational boundary Duplicate route identifiers can obscure independent EVPN path advertisements ExplanationCorrect Answer B:An unrestricted export policy may leak internal infrastructure addresses beyond the organization. Leaving the exact fault unresolved means: An accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. The intended response is: Apply explicit prefix-length-aware export policy limited to authorized aggregate space. Incorrect Answers A:When a BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table, diagnosing BGP policy before basic transport can prolong an otherwise simple outage. The present failure is different: 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:When a border router tags specific prefixes but the provider does not apply the expected regional no-export treatment, untested community handling can leak routes outside an intended operational boundary. The present failure is different: 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:Duplicate route identifiers can obscure independent EVPN path advertisements. That risk belongs to a separate condition: Two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. Here, 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 435The datacom engineering team at an agricultural equipment distributor after an incident review reviews this independent fictional networking case: An access VLAN loses a multicast receiver after a quiet period because periodic IGMP membership updates never reach the upstream querier. Which corrective engineering action most directly addresses this problem? Verify the multicast RPF route and correct source reachability or appropriate multicast routing state Repair IGMP query/reply processing and verify membership refresh timers Apply appropriate multicast boundary and scope controls for the group range Investigate PIM-DM neighbor/prune behavior and remove unnecessary dense-mode flooding where appropriate ExplanationCorrect Answer B:Repair IGMP query/reply processing and verify membership refresh timers. This is the specific action that addresses the fictional fault: An access VLAN loses a multicast receiver after a quiet period because periodic IGMP membership updates never reach the upstream querier. The governing technical reason is: IGMP membership state is maintained by router queries and host reports rather than permanent discovery. Verify by checking: Membership remains active across multiple query intervals and the receiver continues playback. Incorrect Answers A:When a multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded, verifying the multicast RPF route and correcting source reachability or appropriate multicast routing state could be appropriate. Here, an access VLAN loses a multicast receiver after a quiet period because periodic IGMP membership updates never reach the upstream querier. IGMP membership state is maintained by router queries and host reports rather than permanent discovery. C:A training-video multicast group begins leaking beyond its approved distribution region after a transport upgrade. Applying appropriate multicast boundary and scope controls for the group range can respond to that condition, but it would not correct the reported fault: An access VLAN loses a multicast receiver after a quiet period because periodic IGMP membership updates never reach the upstream querier. Repair IGMP query/reply processing and verify membership refresh timers. D:A dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent. This is where investigating PIM-DM neighbor/prune behavior and removing unnecessary dense-mode flooding where appropriate would help. By contrast, an access VLAN loses a multicast receiver after a quiet period because periodic IGMP membership updates never reach the upstream querier. Membership remains active across multiple query intervals and the receiver continues playback.
Question 436The datacom engineering team at a nationwide retail chain during a simulated failover 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. The team applies this remedy: Reconcile MST region name, revision and VLAN-instance mapping across the devices. Which observation would directly demonstrate that this specific issue is resolved? The alternate link transitions to forwarding after a controlled primary failure without sustained loop A received BPDU triggers the configured protective response and no loop appears Both switches report the same region identity and expected instance topology Controlled heartbeat loss leaves only one authorized active forwarding role with no duplicate gateway responses ExplanationCorrect Answer C:Both switches report the same region identity and expected instance topology. This is a directly observable check for the proposed correction: Reconcile MST region name, revision and VLAN-instance mapping across the devices. The particular failure being investigated is: Two switches intended in one MSTP region behave as if separated by a regional boundary after an unnoticed configuration edit. Incorrect Answers A: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. This observation does not prove the correction for the reported defect: 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:When a user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port, a result such as this is useful: A received BPDU triggers the configured protective response and no loop appears. For 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. D:Controlled heartbeat loss leaves only one authorized active forwarding role with no duplicate gateway responses. This check belongs to a campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services. The actual defect is different: 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.
Question 437The datacom engineering team at a film production studio as part of an acceptance test 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. A proposed remedy is: Align VLAN-to-instance mappings and regional parameters across the MST region. Which technical principle most directly supports this remedy? RSTP alternate ports are designed to become forwarding backups after topology changes MSTP topology behavior is per instance and consistent VLAN mapping is necessary for predictable forwarding The spanning-tree root selection follows bridge identifier priority rather than physical hierarchy labels Edge-port fast transition should not make unauthorized bridge participation safe ExplanationCorrect Answer B:MSTP topology behavior is per instance and consistent VLAN mapping is necessary for predictable forwarding. This directly explains why the corrective operation is appropriate: Align VLAN-to-instance mappings and regional parameters across the MST region. The observed acceptance evidence should be: Region digest and per-VLAN instance port roles match at the neighbors. Incorrect Answers A:RSTP alternate ports are designed to become forwarding backups after topology changes. That principle is relevant when a redundant access uplink stays blocked even after the active link fails because the switch has not converged its port roles correctly. Here, 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:The spanning-tree root selection follows bridge identifier priority rather than physical hierarchy labels. That principle is relevant when a low-capacity access switch becomes the spanning-tree root because its bridge priority was left lower than the distribution pair. Here, 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 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. The current condition differs: 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 438The datacom engineering team at a cloud hosting provider after an incident review reviews this independent fictional networking case: IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. Which corrective engineering action most directly addresses this problem? Verify physical MTU, CLNS frame transport and IS-IS padding support along the circuit Set compatible IS-IS circuit levels consistent with the core design Tune IS-IS DIS priority on the shared LAN and validate neighbor continuity after a planned election Compare sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization ExplanationCorrect Answer A:Verify physical MTU, CLNS frame transport and IS-IS padding support along the circuit. This is the specific action that addresses the fictional fault: IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. The governing technical reason is: IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic. Verify by checking: IS-IS hellos and LSP floods succeed and the remote LSDB converges. Incorrect Answers B: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 can respond to that condition, but it would not correct the reported fault: IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic. 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: IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. Verify physical MTU, CLNS frame transport and IS-IS padding support along the circuit. D:Core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. This is where comparing sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization would help. By contrast, IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. IS-IS hellos and LSP floods succeed and the remote LSDB converges.
Question 439The datacom engineering team at a call center outsourcer after a planned hardware refresh reviews this independent fictional networking case: An iBGP route reflected through overlapping clusters returns toward its originator unexpectedly. If this issue remains unresolved, what immediate availability or security risk follows most directly? A valid-looking iBGP route may be unusable when the external next hop is unresolved Partial iBGP distribution can hide routes from only some leaf devices Misconfigured reflection can create route loops and unstable reachability Uncontrolled source interface selection causes intermittent neighbor resets after link changes ExplanationCorrect Answer C:Misconfigured reflection can create route loops and unstable reachability. Leaving the exact fault unresolved means: An iBGP route reflected through overlapping clusters returns toward its originator unexpectedly. The intended response is: Audit reflector topology and preserve the standard ORIGINATOR_ID and CLUSTER_LIST loop controls. Incorrect Answers A:A valid-looking iBGP route may be unusable when the external next hop is unresolved. That consequence could follow when an iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally. Here, an iBGP route reflected through overlapping clusters returns toward its originator unexpectedly; route reflection loop-prevention attributes prevent readvertising a route into a cycle. B:Partial iBGP distribution can hide routes from only some leaf devices. That consequence could follow when a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Here, an iBGP route reflected through overlapping clusters returns toward its originator unexpectedly; audit reflector topology and preserve the standard ORIGINATOR_ID and CLUSTER_LIST loop controls. D:Uncontrolled source interface selection causes intermittent neighbor resets after link changes. That consequence could follow when two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses. Here, an iBGP route reflected through overlapping clusters returns toward its originator unexpectedly; captures and received-route diagnostics show the cyclic update rejected without route churn.
Question 440The datacom engineering team at a consumer electronics manufacturer as part of an acceptance test reviews this independent fictional networking case: A proposed campus core directly bridges user VLANs into a data-center compute fabric without a clear routing and security boundary. The team applies this remedy: Separate campus access/distribution responsibilities from data-center service segments with explicitly routed and protected boundaries. Which observation would directly demonstrate that this specific issue is resolved? A staged migration test shows correct policy provisioning and overlay failover when the preferred WAN path degrades A controlled member failure leaves dual-homed access services reachable and stack roles recover An architectural test shows isolated broadcast domains and approved routed application flows across the boundary Internal BGP best routes select the contracted primary exit and fail over when unavailable ExplanationCorrect Answer C:An architectural test shows isolated broadcast domains and approved routed application flows across the boundary. This is a directly observable check for the proposed correction: Separate campus access/distribution responsibilities from data-center service segments with explicitly routed and protected boundaries. The particular failure being investigated is: A proposed campus core directly bridges user VLANs into a data-center compute fabric without a clear routing and security boundary. Incorrect Answers A:When a migration team treats controller-based network provisioning and SD-WAN overlay path selection as identical capabilities and omits path-performance validation, a result such as this is useful: A staged migration test shows correct policy provisioning and overlay failover when the preferred WAN path degrades. For the reported fault, a proposed campus core directly bridges user VLANs into a data-center compute fabric without a clear routing and security boundary; enterprise campus hierarchy and data-center fabrics serve different failure and security domains that require controlled interconnection. B:A stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed. A controlled member failure leaves dual-homed access services reachable and stack roles recover. This observation does not prove the correction for the reported defect: A proposed campus core directly bridges user VLANs into a data-center compute fabric without a clear routing and security boundary. Separate campus access/distribution responsibilities from data-center service segments with explicitly routed and protected boundaries. D:When a multihomed autonomous system sends outbound traffic via a paid backup despite the intended primary exit, a result such as this is useful: Internal BGP best routes select the contracted primary exit and fail over when unavailable. For the reported fault, a proposed campus core directly bridges user VLANs into a data-center compute fabric without a clear routing and security boundary; unbounded layer-2 expansion amplifies faults and weakens inter-segment security separation.