Question 740The datacom engineering team at an agricultural equipment distributor after an incident review reviews this independent fictional networking case: An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. Which corrective engineering action most directly addresses this problem? Repair next-hop recursion and underlying IGP convergence, not just the BGP session Assign route distinguishers suitable for creating unique originating VPN route identifiers Review the upstream's MED handling and advertise the intended metric on comparable links Enable and validate the correct EVPN address-family capability and policy on both peers ExplanationCorrect Answer D:Enable and validate the correct EVPN address-family capability and policy on both peers. This is the specific action that addresses the fictional fault: An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. The governing technical reason is: A base BGP TCP session does not imply that every MP-BGP address family is negotiated and active. Verify by checking: The EVPN address-family neighbor state and advertised route types appear as expected. Incorrect Answers A:Repairing next-hop recursion and underlying IGP convergence, not just the BGP session is relevant when a BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. It does not resolve this case: An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. A base BGP TCP session does not imply that every MP-BGP address family is negotiated and active. B:Two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. This is where assigning route distinguishers suitable for creating unique originating VPN route identifiers would help. By contrast, an EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. Enable and validate the correct EVPN address-family capability and policy on both peers. C: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 can respond to that condition, but it would not correct the reported fault: 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.
Question 741The datacom engineering team at a regional telecommunications carrier during a controlled network cutover reviews this independent fictional networking case: A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. 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 Inbound traffic may continue on an unwanted provider if external policy is not validated A visible BGP prefix can still hide a black hole if forwarding recursion is stale ExplanationCorrect Answer B:Partial iBGP distribution can hide routes from only some leaf devices. Leaving the exact fault unresolved means: A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. The intended response is: Introduce a correctly designed iBGP route reflector cluster with appropriate clients and redundancy. Incorrect Answers A:An iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally. In that situation, a valid-looking iBGP route may be unusable when the external next hop is unresolved. Here instead, 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 enterprise wants to influence how some external networks enter its secondary ISP, but it changes local preference inside its own AS instead. In that situation, inbound traffic may continue on an unwanted provider if external policy is not validated. Here instead, 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:A visible BGP prefix can still hide a black hole if forwarding recursion is stale. That consequence could follow when a BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. Here, a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution; all clients learn the intended prefixes and remain connected after a reflector failover.
Question 742The datacom engineering team at an e-commerce fulfillment center while validating change-control evidence reviews this independent fictional networking case: A router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. If this issue remains unresolved, what immediate availability or security risk follows most directly? A missing fallback can prevent safe restoration during an identity infrastructure incident Unrestricted routing peers can inject false reachability and disrupt a network segment Unrestricted management access increases credential-attack surface and potential device compromise Blanket permissive workarounds can open lateral movement paths between restricted zones ExplanationCorrect Answer C:Unrestricted management access increases credential-attack surface and potential device compromise. Leaving the exact fault unresolved means: A router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. The intended response is: Restrict management access to approved administrative source networks and enforce strong authentication. Incorrect Answers A:When a campus authentication server becomes unreachable and network admins cannot access devices during an outage, a missing fallback can prevent safe restoration during an identity infrastructure incident. The present failure is different: A router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. Management-plane reachability should be separately controlled from transit forwarding permissions. B:A provider-facing interface accepts unexpected routing-control connections from an unapproved adjacent host. In that situation, unrestricted routing peers can inject false reachability and disrupt a network segment. Here instead, a router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. Restrict management access to approved administrative source networks and enforce strong authentication. D:When a permitted application remains blocked when crossing the Huawei firewall because the zone pairing and rule match conditions are incorrect, blanket permissive workarounds can open lateral movement paths between restricted zones. The present failure is different: A router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. Guest-originated SSH probes are rejected while approved administrative access continues.
Question 743The datacom engineering team at a regional newspaper publisher after an incident review 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 ABR default route appears in the stub area and external destinations remain reachable Route choice matches documented exit intent when internal path costs differ The relevant LSA changes, SPF runs, and the affected route moves to a healthy alternate Both routers progress to Full adjacency and neighbor timer diagnostics agree ExplanationCorrect Answer A: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 B:Route choice matches documented exit intent when internal path costs differ. This check belongs to a remote site incorrectly chooses an external OSPF route that ignores material internal distance to competing exit points. 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. Standard stub areas suppress Type-5 external LSAs and normally rely on an ABR-provided default for external reachability. C:The relevant LSA changes, SPF runs, and the affected route moves to a healthy alternate. That result could validate a repair when one router continues advertising a failed transit link because the local interface reports Up while an intermediate transport component is down. Here, 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. D:When two directly connected OSPF routers see each other in packets but never establish a neighbor because their Hello and Dead timers differ, a result such as this is useful: Both routers progress to Full adjacency and neighbor timer diagnostics agree. For the reported fault, 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 744The datacom engineering team at a film production studio as part of an acceptance test reviews this independent fictional networking case: Two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. The team applies this remedy: Reestablish a contiguous backbone design and use any supported temporary virtual link only with documented constraints. Which observation would directly demonstrate that this specific issue is resolved? ABRs display correct backbone reachability and previously missing interarea routes appear Interarea advertisements cover only approved reachable blocks and traced flows reach valid hosts Both routers progress to Full adjacency and neighbor timer diagnostics agree The ABR default route appears in the stub area and external destinations remain reachable ExplanationCorrect Answer A:ABRs display correct backbone reachability and previously missing interarea routes appear. This is a directly observable check for the proposed correction: Reestablish a contiguous backbone design and use any supported temporary virtual link only with documented constraints. The particular failure being investigated is: Two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. Incorrect Answers B:When an area border router advertises a broad summary that includes subnets withdrawn after a site closure, a result such as this is useful: Interarea advertisements cover only approved reachable blocks and traced flows reach valid hosts. For the reported fault, two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent; OSPF interarea routing depends on backbone connectivity through area 0. C:Both routers progress to Full adjacency and neighbor timer diagnostics agree. This check belongs to two directly connected OSPF routers see each other in packets but never establish a neighbor because their Hello and Dead timers differ. The actual defect is different: Two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. Reestablish a contiguous backbone design and use any supported temporary virtual link only with documented constraints. D:The ABR default route appears in the stub area and external destinations remain reachable. This check belongs to an engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. The actual defect is different: Two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. A fragmented OSPF backbone can split route exchange between otherwise healthy areas.
Question 745The datacom engineering team at a film production studio as part of an acceptance test reviews this independent fictional networking case: A client changes IP address during normal intra-campus roaming because neighboring APs anchor it to incompatible service VLANs. If this issue remains unresolved, what immediate availability or security risk follows most directly? Incorrect access-role mapping can provide guest devices unrestricted internal reachability Uncorrected RF contention can undermine a high-density WLAN despite healthy AP links Stale link-state information can create asymmetric paths and packet loss Unexpected address changes can reset voice and real-time application sessions ExplanationCorrect Answer D:Unexpected address changes can reset voice and real-time application sessions. Leaving the exact fault unresolved means: A client changes IP address during normal intra-campus roaming because neighboring APs anchor it to incompatible service VLANs. The intended response is: Harmonize mobility-domain forwarding and VLAN/anchor design so approved roams preserve intended IP connectivity. Incorrect Answers A:Guest devices receive an internal employee VLAN after 802.1X authorization results are mapped incorrectly by WLAN policy. In that situation, incorrect access-role mapping can provide guest devices unrestricted internal reachability. Here instead, a client changes IP address during normal intra-campus roaming because neighboring APs anchor it to incompatible service VLANs. Session continuity during roaming depends on consistent mobility and client addressing behavior. For film production studio as part of an acceptance test, the acceptance test should show that a mobility test keeps the expected address and established application sessions while moving across APs. B:Uncorrected RF contention can undermine a high-density WLAN despite healthy AP links. That risk belongs to a separate condition: A large lecture hall experiences low Wi-Fi throughput even with strong signal because neighboring AP radios overlap excessively on busy channels. Here, a client changes IP address during normal intra-campus roaming because neighboring APs anchor it to incompatible service VLANs; harmonize mobility-domain forwarding and VLAN/anchor design so approved roams preserve intended IP connectivity. C:Core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. In that situation, stale link-state information can create asymmetric paths and packet loss. Here instead, a client changes IP address during normal intra-campus roaming because neighboring APs anchor it to incompatible service VLANs. A mobility test keeps the expected address and established application sessions while moving across APs.
Question 746The datacom engineering team at an air-cargo logistics operator during a network security audit reviews this independent fictional networking case: A BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. The team applies this remedy: Repair next-hop recursion and underlying IGP convergence, not just the BGP session. Which observation would directly demonstrate that this specific issue is resolved? Session source addresses match loopbacks and both peers establish consistently Captures and received-route diagnostics show the cyclic update rejected without route churn Adjacent peers show the expected communities and external advertisements are scoped as contracted The best BGP route resolves to a live next hop and data-plane probes succeed after reconvergence ExplanationCorrect Answer D:The best BGP route resolves to a live next hop and data-plane probes succeed after reconvergence. This is a directly observable check for the proposed correction: Repair next-hop recursion and underlying IGP convergence, not just the BGP session. The particular failure being investigated is: A BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. Incorrect Answers A:When two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses, a result such as this is useful: Session source addresses match loopbacks and both peers establish consistently. For the reported fault, a BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link; BGP route eligibility depends on resolvable next hops and a functioning forwarding path. B: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. This observation does not prove the correction for the reported defect: A BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. Repair next-hop recursion and underlying IGP convergence, not just the BGP session. C:Adjacent peers show the expected communities and external advertisements are scoped as contracted. This check belongs to a border router tags specific prefixes but the provider does not apply the expected regional no-export treatment. The actual defect is different: A BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. A visible BGP prefix can still hide a black hole if forwarding recursion is stale.
Question 747The 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. The team applies this remedy: Review the upstream's MED handling and advertise the intended metric on comparable links. Which observation would directly demonstrate that this specific issue is resolved? The upstream reports intended MED attributes and observed ingress tracks the agreed policy 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 The best BGP route resolves to a live next hop and data-plane probes succeed after reconvergence ExplanationCorrect Answer A:The upstream reports intended MED attributes and observed ingress tracks the agreed policy. This is a directly observable check for the proposed correction: Review the upstream's MED handling and advertise the intended metric on comparable links. The particular failure being investigated is: Two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned. Incorrect Answers B:When operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference, a result such as this is useful: Best-path diagnostics show the winning attribute and route selection matches intent. For the reported fault, 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. C:When an iBGP route reflected through overlapping clusters returns toward its originator unexpectedly, a result such as this is useful: Captures and received-route diagnostics show the cyclic update rejected without route churn. For the reported fault, 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:A BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. The best BGP route resolves to a live next hop and data-plane probes succeed after reconvergence. This observation does not prove the correction for the reported defect: Two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned. Incorrect MED assumptions can cause uneven interconnect load and unpredictable ingress.
Question 748The datacom engineering team at a payment-processing provider after a monitored link change reviews this independent fictional networking case: Two replacement servers are configured with the same IPv6 address and one fails to bring the address online. The team applies this remedy: Resolve duplicate addressing and verify Neighbor Discovery duplicate-address-detection behavior. Which observation would directly demonstrate that this specific issue is resolved? The route installs with the expected interface and reachability probes succeed Clients form valid unique global addresses and default routes from the expected RA source Client associations spread across permitted VLANs and each receives an address from its own correct scope The conflicting address is removed and DAD completes without duplicate notifications ExplanationCorrect Answer D:The conflicting address is removed and DAD completes without duplicate notifications. This is a directly observable check for the proposed correction: Resolve duplicate addressing and verify Neighbor Discovery duplicate-address-detection behavior. The particular failure being investigated is: Two replacement servers are configured with the same IPv6 address and one fails to bring the address online. Incorrect Answers A:The route installs with the expected interface and reachability probes succeed. This check belongs to an IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly. The actual defect is different: Two replacement servers are configured with the same IPv6 address and one fails to bring the address online. IPv6 DAD uses neighbor solicitation to detect duplicate addresses before regular use. B:Clients form valid unique global addresses and default routes from the expected RA source. That result could validate a repair when clients on a new IPv6 VLAN fail to obtain global addresses because router advertisements lack the intended autonomous prefix information. Here, two replacement servers are configured with the same IPv6 address and one fails to bring the address online; resolve duplicate addressing and verify Neighbor Discovery duplicate-address-detection behavior. C:Client associations spread across permitted VLANs and each receives an address from its own correct scope. That result could validate a repair when one SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space. Here, two replacement servers are configured with the same IPv6 address and one fails to bring the address online; duplicate IPv6 addresses create intermittent black holes and service identity confusion.
Question 749The datacom engineering team at a library district network after a planned hardware refresh reviews this independent fictional networking case: An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. A proposed remedy is: Enable and validate the correct EVPN address-family capability and policy on both peers. Which technical principle most directly supports this remedy? BGP best-path attributes are evaluated in a defined order; shorter AS_PATH is not always the first deciding factor A base BGP TCP session does not imply that every MP-BGP address family is negotiated and active BGP runs over TCP and needs successful IP transport to its configured peer endpoint BGP neighbor identity must align with the configured source and destination transport addresses ExplanationCorrect Answer B:A base BGP TCP session does not imply that every MP-BGP address family is negotiated and active. This directly explains why the corrective operation is appropriate: Enable and validate the correct EVPN address-family capability and policy on both peers. The observed acceptance evidence should be: The EVPN address-family neighbor state and advertised route types appear as expected. Incorrect Answers A:BGP best-path attributes are evaluated in a defined order; shorter AS_PATH is not always the first deciding factor. That rule governs a different situation: Operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. Here, an EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. A base BGP TCP session does not imply that every MP-BGP address family is negotiated and active. C:A BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. BGP runs over TCP and needs successful IP transport to its configured peer endpoint. The current condition differs: An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. Enable and validate the correct EVPN address-family capability and policy on both peers. D:BGP neighbor identity must align with the configured source and destination transport addresses. That principle is relevant when two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses. Here, 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.
Question 750The datacom engineering team at an industrial safety organization during a simulated failover 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. A proposed remedy is: Align ingress marking and MQC traffic-classifier matching before adjusting queue parameters. Which technical principle most directly supports this remedy? A prefix-list entry's address and mask-length matching must both reflect the authorization boundary Sequential route-policy matches can terminate evaluation and make later rules unreachable Queue behavior depends on packets being correctly classified by actual header fields at the enforcement point Redistribution can cross routing trust boundaries and must specify which routes are authorized to cross ExplanationCorrect Answer C:Queue behavior depends on packets being correctly classified by actual header fields at the enforcement point. This directly explains why the corrective operation is appropriate: Align ingress marking and MQC traffic-classifier matching before adjusting queue parameters. The observed acceptance evidence should be: Classifier counters rise for real voice flows and the intended behavior is applied. Incorrect Answers A:A prefix-list entry's address and mask-length matching must both reflect the authorization boundary. That rule governs a different situation: A routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes. Here, 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:Sequential route-policy matches can terminate evaluation and make later rules unreachable. That principle is relevant when a new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad. Here, 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. D:Redistribution can cross routing trust boundaries and must specify which routes are authorized to cross. That rule governs a different situation: A border router injects internal transit and management prefixes into external BGP due to unrestricted redistribution. Here, 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.