Question 340The datacom engineering team at a payment-processing provider after a monitored link change reviews this independent fictional networking case: An area border router advertises a broad summary that includes subnets withdrawn after a site closure. Which corrective engineering action most directly addresses this problem? Mark host-facing interfaces passive while still advertising their connected subnet through the intended OSPF process Align Hello and Dead timers on the shared OSPF segment and repeat adjacency checks Set OSPF interface priorities to favor a stable distribution router and perform a planned election transition Tighten the configured summary to reachable address blocks and test interarea destinations ExplanationCorrect Answer D:Tighten the configured summary to reachable address blocks and test interarea destinations. This is the specific action that addresses the fictional fault: An area border router advertises a broad summary that includes subnets withdrawn after a site closure. The governing technical reason is: ABR summaries reduce LSDB size but overbroad summaries can attract packets for nonexistent destinations. Verify by checking: Interarea advertisements cover only approved reachable blocks and traced flows reach valid hosts. Incorrect Answers A:A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. This is where marking host-facing interfaces passive while still advertising their connected subnet through the intended OSPF process would help. By contrast, an area border router advertises a broad summary that includes subnets withdrawn after a site closure. ABR summaries reduce LSDB size but overbroad summaries can attract packets for nonexistent destinations. B:Two directly connected OSPF routers see each other in packets but never establish a neighbor because their Hello and Dead timers differ. Aligning Hello and Dead timers on the shared OSPF segment and repeat adjacency checks can respond to that condition, but it would not correct the reported fault: An area border router advertises a broad summary that includes subnets withdrawn after a site closure. Tighten the configured summary to reachable address blocks and test interarea destinations. C:When a shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node, setting OSPF interface priorities to favor a stable distribution router and performing a planned election transition could be appropriate. Here, an area border router advertises a broad summary that includes subnets withdrawn after a site closure. Interarea advertisements cover only approved reachable blocks and traced flows reach valid hosts.
Question 341The datacom engineering team at a municipal emergency dispatch center during a topology consistency review 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. A proposed remedy is: Apply provider-approved AS_PATH prepending or another suitable inbound policy while recognizing remote policy precedence. Which technical principle most directly supports this remedy? eBGP session establishment validates the expected remote AS during OPEN negotiation Route reflection loop-prevention attributes prevent readvertising a route into a cycle MED is a suggestion about preferred entry into a neighboring AS and its comparison is policy dependent AS_PATH attributes can influence external path selection but cannot guarantee behavior against other operators' policies ExplanationCorrect Answer D:AS_PATH attributes can influence external path selection but cannot guarantee behavior against other operators' policies. This directly explains why the corrective operation is appropriate: Apply provider-approved AS_PATH prepending or another suitable inbound policy while recognizing remote policy precedence. The observed acceptance evidence should be: External route views show the intended prepended announcement and measured ingress path changes when supported. Incorrect Answers A:An edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS. eBGP session establishment validates the expected remote AS during OPEN negotiation. The current condition differs: 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:Route reflection loop-prevention attributes prevent readvertising a route into a cycle. That rule governs a different situation: An iBGP route reflected through overlapping clusters returns toward its originator unexpectedly. Here, 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. C:MED is a suggestion about preferred entry into a neighboring AS and its comparison is policy dependent. That rule governs a different situation: Two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned. Here, 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 342The 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. A proposed remedy is: Apply appropriate traffic shaping at the controlled egress and verify contracted rate behavior. Which technical principle most directly supports this remedy? Policing enforces a rate by remarking or dropping excess traffic, whereas shaping buffers excess bursts for later transmission PBR intentionally overrides ordinary routing and can therefore preserve a failed forwarding decision Route tagging and matching can prevent feedback when multiple dynamic-routing redistribution points exist Equal-cost routing can create direction asymmetry that violates an appliance's stateful session assumptions ExplanationCorrect Answer A:Policing enforces a rate by remarking or dropping excess traffic, whereas shaping buffers excess bursts for later transmission. This directly explains why the corrective operation is appropriate: Apply appropriate traffic shaping at the controlled egress and verify contracted rate behavior. The observed acceptance evidence should be: Burst loss decreases while sustained throughput remains within the agreed service rate. Incorrect Answers B:PBR intentionally overrides ordinary routing and can therefore preserve a failed forwarding decision. That rule governs a different situation: Policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. Here, 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 two redistribution points repeatedly re-inject learned routes between OSPF and another IGP and churn route entries, route tagging and matching can prevent feedback when multiple dynamic-routing redistribution points exist. By contrast, 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:When a stateful firewall intermittently drops responses after equal-cost routing spreads the forward and return flows across unrelated inspection nodes, equal-cost routing can create direction asymmetry that violates an appliance's stateful session assumptions. By contrast, a WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective; burst loss decreases while sustained throughput remains within the agreed service rate.
Question 343The 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. Which corrective engineering action most directly addresses this problem? Validate the community value, propagation policy, and provider-supported meaning before relying on it Assign route distinguishers suitable for creating unique originating VPN route identifiers Introduce a correctly designed iBGP route reflector cluster with appropriate clients and redundancy Inspect the BGP best-path decision sequence and correct the higher-priority policy attribute before modifying AS_PATH ExplanationCorrect Answer A:Validate the community value, propagation policy, and provider-supported meaning before relying on it. This is the specific action that addresses the fictional fault: A border router tags specific prefixes but the provider does not apply the expected regional no-export treatment. The governing technical reason is: BGP communities convey policy intent but require receiving-network policy to interpret them. Verify by checking: Adjacent peers show the expected communities and external advertisements are scoped as contracted. Incorrect Answers B: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, 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. C:When a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution, introducing a correctly designed iBGP route reflector cluster with appropriate clients and redundancy could be appropriate. Here, 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. D:Operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. Inspecting the BGP best-path decision sequence and correcting the higher-priority policy attribute before modifying AS_PATH can respond to that condition, but it would not correct the reported fault: 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 344The 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. The team applies this remedy: Correct matching export and import route-target policy for the tenant instance. Which observation would directly demonstrate that this specific issue is resolved? 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 Best-path diagnostics show the winning attribute and route selection matches intent Captures and received-route diagnostics show the cyclic update rejected without route churn ExplanationCorrect Answer A:The target instance imports only matching tenant routes and no unrelated VRF routes appear. This is a directly observable check for the proposed correction: Correct matching export and import route-target policy for the tenant instance. The particular failure being investigated is: Tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. Incorrect Answers B:All clients learn the intended prefixes and remain connected after a reflector failover. That result could validate a repair when a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Here, 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:Best-path diagnostics show the winning attribute and route selection matches intent. This check belongs to operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. The actual defect is different: 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:Captures and received-route diagnostics show the cyclic update rejected without route churn. That result could validate a repair when an iBGP route reflected through overlapping clusters returns toward its originator unexpectedly. Here, tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance; route target errors can isolate a tenant or leak routes into the wrong routing instance.
Question 345The datacom engineering team at a wholesale market association while tracing a degraded application flow reviews this independent fictional networking case: Operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. Which corrective engineering action most directly addresses this problem? Inspect the BGP best-path decision sequence and correct the higher-priority policy attribute before modifying AS_PATH Repair next-hop recursion and underlying IGP convergence, not just the BGP session Audit reflector topology and preserve the standard ORIGINATOR_ID and CLUSTER_LIST loop controls Restore transport IP reachability to the neighbor before changing BGP route policies ExplanationCorrect Answer A:Inspect the BGP best-path decision sequence and correct the higher-priority policy attribute before modifying AS_PATH. This is the specific action that addresses the fictional fault: Operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. The governing technical reason is: BGP best-path attributes are evaluated in a defined order; shorter AS_PATH is not always the first deciding factor. Verify by checking: Best-path diagnostics show the winning attribute and route selection matches intent. Incorrect Answers B: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, 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. C:An iBGP route reflected through overlapping clusters returns toward its originator unexpectedly. This is where auditing reflector topology and preserving the standard ORIGINATOR_ID and CLUSTER_LIST loop controls would help. By contrast, operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. Inspect the BGP best-path decision sequence and correct the higher-priority policy attribute before modifying AS_PATH. D:A BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. This is where restoring transport IP reachability to the neighbor before changing BGP route policies would help. By contrast, operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. Best-path diagnostics show the winning attribute and route selection matches intent.
Question 346The datacom engineering team at an energy distribution business while tracing a degraded application flow 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? Failure of rapid transition turns redundant cabling into an outage rather than resilience Split-brain ownership can cause MAC flaps and severe layer-2 instability Misaligned instance mappings can strand a subset of VLANs while others work Single-member attachment can defeat apparent logical redundancy ExplanationCorrect Answer A: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 B:Split-brain ownership can cause MAC flaps and severe layer-2 instability. That risk belongs to a separate condition: A campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services. Here, 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. C:Misaligned instance mappings can strand a subset of VLANs while others work. That risk belongs to a separate condition: Traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. 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:Single-member attachment can defeat apparent logical redundancy. That consequence could follow when a stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed. 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 347The datacom engineering team at a consumer electronics manufacturer as part of an acceptance test reviews this independent fictional networking case: A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. Which corrective engineering action most directly addresses this problem? Set OSPF interface priorities to favor a stable distribution router and perform a planned election transition Validate stub-area configuration and ensure the ABR advertises the intended default route into the area Align the totally stub area behavior at the ABR and verify the intended default-based forwarding Mark host-facing interfaces passive while still advertising their connected subnet through the intended OSPF process ExplanationCorrect Answer D:Mark host-facing interfaces passive while still advertising their connected subnet through the intended OSPF process. This is the specific action that addresses the fictional fault: A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. The governing technical reason is: A passive OSPF interface can advertise its prefix without attempting routing adjacencies on that link. Verify by checking: Packet captures show no OSPF Hellos on the host VLAN while the prefix remains in OSPF routes. Incorrect Answers A:A shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. Setting OSPF interface priorities to favor a stable distribution router and performing a planned election transition can respond to that condition, but it would not correct the reported fault: 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. B:An engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. This is where validating stub-area configuration and ensure the ABR advertises the intended default route into the area would help. By contrast, a user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. Mark host-facing interfaces passive while still advertising their connected subnet through the intended OSPF process. C:Aligning the totally stub area behavior at the ABR and verifying the intended default-based forwarding is relevant when branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. It does not resolve this case: A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. Packet captures show no OSPF Hellos on the host VLAN while the prefix remains in OSPF routes.
Question 348The datacom engineering team at an insurance processing company while validating change-control evidence reviews this independent fictional networking case: Two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned. A proposed remedy is: Review the upstream's MED handling and advertise the intended metric on comparable links. Which technical principle most directly supports this remedy? BGP neighbor identity must align with the configured source and destination transport addresses Route reflection replaces full-mesh iBGP peering while preserving loop-prevention attributes MED is a suggestion about preferred entry into a neighboring AS and its comparison is policy dependent EVPN route targets control which VPN routes a receiving instance is permitted to import ExplanationCorrect Answer C:MED is a suggestion about preferred entry into a neighboring AS and its comparison is policy dependent. This directly explains why the corrective operation is appropriate: Review the upstream's MED handling and advertise the intended metric on comparable links. The observed acceptance evidence should be: The upstream reports intended MED attributes and observed ingress tracks the agreed policy. Incorrect Answers A:When two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses, BGP neighbor identity must align with the configured source and destination transport addresses. By contrast, two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned; MED is a suggestion about preferred entry into a neighboring AS and its comparison is policy dependent. B:Route reflection replaces full-mesh iBGP peering while preserving loop-prevention attributes. That principle is relevant when a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Here, two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned; review the upstream's MED handling and advertise the intended metric on comparable links. D:EVPN route targets control which VPN routes a receiving instance is permitted to import. That rule governs a different situation: Tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. Here, two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned. The upstream reports intended MED attributes and observed ingress tracks the agreed policy.
Question 349The datacom engineering team at a payment-processing provider after a monitored link change reviews this independent fictional networking case: An iBGP route reflected through overlapping clusters returns toward its originator unexpectedly. A proposed remedy is: Audit reflector topology and preserve the standard ORIGINATOR_ID and CLUSTER_LIST loop controls. Which technical principle most directly supports this remedy? MED is a suggestion about preferred entry into a neighboring AS and its comparison is policy dependent Route reflection loop-prevention attributes prevent readvertising a route into a cycle BGP neighbor identity must align with the configured source and destination transport addresses EVPN route targets control which VPN routes a receiving instance is permitted to import ExplanationCorrect Answer B:Route reflection loop-prevention attributes prevent readvertising a route into a cycle. This directly explains why the corrective operation is appropriate: Audit reflector topology and preserve the standard ORIGINATOR_ID and CLUSTER_LIST loop controls. The observed acceptance evidence should be: Captures and received-route diagnostics show the cyclic update rejected without route churn. Incorrect Answers A:MED is a suggestion about preferred entry into a neighboring AS and its comparison is policy dependent. That rule governs a different situation: Two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned. 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. C:When two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses, BGP neighbor identity must align with the configured source and destination transport addresses. By contrast, 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:EVPN route targets control which VPN routes a receiving instance is permitted to import. That rule governs a different situation: Tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. 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 350The 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. A proposed remedy is: Add health-aware policy-path handling or withdraw the policy on next-hop failure. Which technical principle most directly supports this remedy? QoS markings can be rewritten at domain boundaries; end-to-end class treatment requires consistent mapping PBR intentionally overrides ordinary routing and can therefore preserve a failed forwarding decision Equal-cost routing can create direction asymmetry that violates an appliance's stateful session assumptions ACL matching is evaluated at the attachment point and direction, not according to a rule's descriptive name ExplanationCorrect Answer B:PBR intentionally overrides ordinary routing and can therefore preserve a failed forwarding decision. This directly explains why the corrective operation is appropriate: Add health-aware policy-path handling or withdraw the policy on next-hop failure. The observed acceptance evidence should be: Policy test traffic fails over to the approved inspection path and maintains documented controls. Incorrect Answers A:Delay-sensitive packets leave the campus with voice markings but are remarked to best-effort at a trusted border. QoS markings can be rewritten at domain boundaries; end-to-end class treatment requires consistent mapping. The current condition differs: 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:Equal-cost routing can create direction asymmetry that violates an appliance's stateful session assumptions. That principle is relevant when a stateful firewall intermittently drops responses after equal-cost routing spreads the forward and return flows across unrelated inspection nodes. Here, 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:ACL matching is evaluated at the attachment point and direction, not according to a rule's descriptive name. That rule governs a different situation: 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. Policy test traffic fails over to the approved inspection path and maintains documented controls.