Question 730The datacom engineering team at a government service campus after a monitored link change reviews this independent fictional networking case: A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. The team applies this remedy: Introduce a correctly designed iBGP route reflector cluster with appropriate clients and redundancy. Which observation would directly demonstrate that this specific issue is resolved? All clients learn the intended prefixes and remain connected after a reflector failover Session source addresses match loopbacks and both peers establish consistently The EVPN address-family neighbor state and advertised route types appear as expected EVPN control-plane entries retain unique per-origin VPN identifiers and remote paths coexist ExplanationCorrect Answer A:All clients learn the intended prefixes and remain connected after a reflector failover. This is a directly observable check for the proposed correction: Introduce a correctly designed iBGP route reflector cluster with appropriate clients and redundancy. The particular failure being investigated is: A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Incorrect Answers B:Session source addresses match loopbacks and both peers establish consistently. That result could validate a repair when two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses. Here, a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution; route reflection replaces full-mesh iBGP peering while preserving loop-prevention attributes. C:An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. The EVPN address-family neighbor state and advertised route types appear as expected. This observation does not prove the correction for the reported defect: A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Introduce a correctly designed iBGP route reflector cluster with appropriate clients and redundancy. D:EVPN control-plane entries retain unique per-origin VPN identifiers and remote paths coexist. That result could validate a repair when two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. Here, a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution; partial iBGP distribution can hide routes from only some leaf devices.
Question 731The datacom engineering team at a distribution warehouse group during a simulated failover test reviews this independent fictional networking case: A migration team treats controller-based network provisioning and SD-WAN overlay path selection as identical capabilities and omits path-performance validation. A proposed remedy is: Define underlay provisioning and SD-WAN overlay policy separately and verify application steering under link degradation. Which technical principle most directly supports this remedy? Enterprise campus hierarchy and data-center fabrics serve different failure and security domains that require controlled interconnection Physical interface state alone cannot detect all remote next-hop failures A VLAN pool can distribute WLAN clients across logical broadcast domains when pool and DHCP design are coherent SDN-oriented control automation and SD-WAN application-aware path control can complement each other but solve different problems ExplanationCorrect Answer D:SDN-oriented control automation and SD-WAN application-aware path control can complement each other but solve different problems. This directly explains why the corrective operation is appropriate: Define underlay provisioning and SD-WAN overlay policy separately and verify application steering under link degradation. The observed acceptance evidence should be: A staged migration test shows correct policy provisioning and overlay failover when the preferred WAN path degrades. Incorrect Answers A: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. The current condition differs: A migration team treats controller-based network provisioning and SD-WAN overlay path selection as identical capabilities and omits path-performance validation. SDN-oriented control automation and SD-WAN application-aware path control can complement each other but solve different problems. B:A static backup path remains inactive while the primary next hop fails beyond a locally Up interface. Physical interface state alone cannot detect all remote next-hop failures. The current condition differs: A migration team treats controller-based network provisioning and SD-WAN overlay path selection as identical capabilities and omits path-performance validation. Define underlay provisioning and SD-WAN overlay policy separately and verify application steering under link degradation. C:One SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space. A VLAN pool can distribute WLAN clients across logical broadcast domains when pool and DHCP design are coherent. The current condition differs: A migration team treats controller-based network provisioning and SD-WAN overlay path selection as identical capabilities and omits path-performance validation. A staged migration test shows correct policy provisioning and overlay failover when the preferred WAN path degrades.
Question 732The datacom engineering team at an agricultural equipment distributor after an incident review reviews this independent fictional networking case: OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection. If this issue remains unresolved, what immediate availability or security risk follows most directly? Incorrect group placement can create duplicate gateway ownership or unreachable hosts Slow liveness detection can extend avoidable black-hole duration after link failure Failure beyond the local link can strand static-route traffic indefinitely Local gateway survival without uplink tracking can blackhole an entire user VLAN ExplanationCorrect Answer B:Slow liveness detection can extend avoidable black-hole duration after link failure. Leaving the exact fault unresolved means: OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection. The intended response is: Enable supported BFD tracking for the OSPF adjacency and validate timer compatibility. Incorrect Answers A:Incorrect group placement can create duplicate gateway ownership or unreachable hosts. That consequence could follow when two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error. Here, OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection; BFD provides rapid bidirectional failure detection to subscribed routing protocols. C:A static backup path remains inactive while the primary next hop fails beyond a locally Up interface. In that situation, failure beyond the local link can strand static-route traffic indefinitely. Here instead, OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection. Enable supported BFD tracking for the OSPF adjacency and validate timer compatibility. D:When a VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational, local gateway survival without uplink tracking can blackhole an entire user VLAN. The present failure is different: OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection. During a planned circuit interruption, BFD detects failure and routing reconverges within the operational target.
Question 733The datacom engineering team at a regional newspaper publisher after an incident review reviews this independent fictional networking case: A permitted application remains blocked when crossing the Huawei firewall because the zone pairing and rule match conditions are incorrect. Which corrective engineering action most directly addresses this problem? Restrict management access to approved administrative source networks and enforce strong authentication Deploy appropriate ARP spoofing protection based on trusted bindings and switch capabilities Assign the service interfaces and routes to the intended VRFs and audit any explicit route leaking Review source/destination zone membership and adjust a narrowly scoped security-policy rule ExplanationCorrect Answer D:Review source/destination zone membership and adjust a narrowly scoped security-policy rule. This is the specific action that addresses the fictional fault: A permitted application remains blocked when crossing the Huawei firewall because the zone pairing and rule match conditions are incorrect. The governing technical reason is: Stateful firewalls evaluate sessions against zone-aware policies before permitting new flows. Verify by checking: Policy hit counters and session logs confirm only the approved application flow is allowed. Incorrect Answers A: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 permitted application remains blocked when crossing the Huawei firewall because the zone pairing and rule match conditions are incorrect. Stateful firewalls evaluate sessions against zone-aware policies before permitting new flows. B:An attacker on a user VLAN advertises the gateway's IPv4 address with a forged MAC and steals nearby sessions. This is where deploying appropriate ARP spoofing protection based on trusted bindings and switch capabilities would help. By contrast, a permitted application remains blocked when crossing the Huawei firewall because the zone pairing and rule match conditions are incorrect. Review source/destination zone membership and adjust a narrowly scoped security-policy rule. C:When traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance, assigning the service interfaces and routes to the intended VRFs and auditing any explicit route leaking could be appropriate. Here, a permitted application remains blocked when crossing the Huawei firewall because the zone pairing and rule match conditions are incorrect. Policy hit counters and session logs confirm only the approved application flow is allowed.
Question 734The datacom engineering team at a regional telecommunications carrier during a controlled network cutover reviews this independent fictional networking case: Two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error. The team applies this remedy: Correct VRRP group placement and virtual IPv4 address on the intended broadcast domain. Which observation would directly demonstrate that this specific issue is resolved? An injected upstream failure withdraws the primary route and backup traffic succeeds During a planned circuit interruption, BFD detects failure and routing reconverges within the operational target The static route is active and its recursive next hop resolves to an operational interface Matching gateway interfaces negotiate one Master and user devices reach the correct virtual address ExplanationCorrect Answer D:Matching gateway interfaces negotiate one Master and user devices reach the correct virtual address. This is a directly observable check for the proposed correction: Correct VRRP group placement and virtual IPv4 address on the intended broadcast domain. The particular failure being investigated is: Two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error. Incorrect Answers A:When a static backup path remains inactive while the primary next hop fails beyond a locally Up interface, a result such as this is useful: An injected upstream failure withdraws the primary route and backup traffic succeeds. For the reported fault, two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error; a VRRP group represents a virtual gateway within a specific local layer-2 segment. B: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: Two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error. Correct VRRP group placement and virtual IPv4 address on the intended broadcast domain. C: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, two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error; incorrect group placement can create duplicate gateway ownership or unreachable hosts.
Question 735The datacom engineering team at an engineering consultancy during a controlled network cutover reviews this independent fictional networking case: Newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries. Which corrective engineering action most directly addresses this problem? Compare candidate prefixes and remove the unintended more-specific route before changing global route preferences Inspect interface and forwarding-plane readiness, then restore the failed forwarding-table synchronization before accepting traffic Provide a resolvable route to the next hop or replace it with the verified directly reachable next hop Reorder and narrow the matching conditions so explicit permitted prefixes are evaluated before the general deny ExplanationCorrect Answer B:Inspect interface and forwarding-plane readiness, then restore the failed forwarding-table synchronization before accepting traffic. This is the specific action that addresses the fictional fault: Newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries. The governing technical reason is: A healthy control plane does not prove that hardware forwarding entries are programmed in the data plane. Verify by checking: Forwarding entries are present on the line card and a test flow traverses the intended interface. Incorrect Answers A:When a branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router, comparing candidate prefixes and removing the unintended more-specific route before changing global route preferences could be appropriate. Here, newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries. A healthy control plane does not prove that hardware forwarding entries are programmed in the data plane. C:When a static route is configured to a next-hop address that is absent from the local routing table and never becomes active, providing a resolvable route to the next hop or replace it with the verified directly reachable next hop could be appropriate. Here, newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries. Inspect interface and forwarding-plane readiness, then restore the failed forwarding-table synchronization before accepting traffic. D:A new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad. Reordering and narrow the matching conditions so explicit permitted prefixes are evaluated before the general deny can respond to that condition, but it would not correct the reported fault: Newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries. Forwarding entries are present on the line card and a test flow traverses the intended interface.
Question 736The datacom engineering team at an air-cargo logistics operator during a network security audit reviews this independent fictional networking case: Two directly connected OSPF routers see each other in packets but never establish a neighbor because their Hello and Dead timers differ. A proposed remedy is: Align Hello and Dead timers on the shared OSPF segment and repeat adjacency checks. Which technical principle most directly supports this remedy? OSPF shortest-path selection uses cumulative interface cost, not real-time measured bandwidth by itself OSPF routing exchanges must pass consistent authentication checks before neighbor state can advance OSPF adjacency establishment requires compatible hello parameters on the neighbor-facing interfaces DR and BDR election on broadcast networks is influenced by configured interface priority and is not a direct lowest-cost path election ExplanationCorrect Answer C:OSPF adjacency establishment requires compatible hello parameters on the neighbor-facing interfaces. This directly explains why the corrective operation is appropriate: Align Hello and Dead timers on the shared OSPF segment and repeat adjacency checks. The observed acceptance evidence should be: Both routers progress to Full adjacency and neighbor timer diagnostics agree. Incorrect Answers A:When after an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed, OSPF shortest-path selection uses cumulative interface cost, not real-time measured bandwidth by itself. By contrast, two directly connected OSPF routers see each other in packets but never establish a neighbor because their Hello and Dead timers differ; OSPF adjacency establishment requires compatible hello parameters on the neighbor-facing interfaces. B:OSPF routing exchanges must pass consistent authentication checks before neighbor state can advance. That principle is relevant when an OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. Here, two directly connected OSPF routers see each other in packets but never establish a neighbor because their Hello and Dead timers differ; align Hello and Dead timers on the shared OSPF segment and repeat adjacency checks. D:DR and BDR election on broadcast networks is influenced by configured interface priority and is not a direct lowest-cost path election. That principle is relevant when a shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. Here, two directly connected OSPF routers see each other in packets but never establish a neighbor because their Hello and Dead timers differ; both routers progress to Full adjacency and neighbor timer diagnostics agree.
Question 737The 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. Which corrective engineering action most directly addresses this problem? Reestablish a contiguous backbone design and use any supported temporary virtual link only with documented constraints 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 A:Reestablish a contiguous backbone design and use any supported temporary virtual link only with documented constraints. This is the specific action that addresses the fictional fault: Two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. The governing technical reason is: OSPF interarea routing depends on backbone connectivity through area 0. Verify by checking: ABRs display correct backbone reachability and previously missing interarea routes appear. Incorrect Answers B:An engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. Validating stub-area configuration and ensure the ABR advertises the intended default route into the area can respond to that condition, but it would not correct 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: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: 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:When a user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance, marking host-facing interfaces passive while still advertising their connected subnet through the intended OSPF process could be appropriate. Here, two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. ABRs display correct backbone reachability and previously missing interarea routes appear.
Question 738The 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. 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? External route views show the intended prepended announcement and measured ingress path changes when supported Exported BGP routes contain only the authorized prefix and mask set EVPN control-plane entries retain unique per-origin VPN identifiers and remote paths coexist All clients learn the intended prefixes and remain connected after a reflector failover ExplanationCorrect Answer B: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: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. 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. Prefix lists and route policies should enforce precise permitted address and mask ranges at external boundaries. C:EVPN control-plane entries retain unique per-origin VPN identifiers and remote paths coexist. That result could validate a repair when two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. Here, 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: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, 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 739The datacom engineering team at a hospital imaging provider during a controlled network cutover reviews this independent fictional networking case: Newly moved office endpoints cannot receive IPv4 leases because their DHCP server is across a routed interface without a relay. Which corrective engineering action most directly addresses this problem? Use supported SNMPv3 authentication/privacy and authorize specific management targets Configure DHCP relay on the correct client-facing interface and verify reachability to the DHCP server Inspect interface and forwarding-plane readiness, then restore the failed forwarding-table synchronization before accepting traffic Verify the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover ExplanationCorrect Answer B:Configure DHCP relay on the correct client-facing interface and verify reachability to the DHCP server. This is the specific action that addresses the fictional fault: Newly moved office endpoints cannot receive IPv4 leases because their DHCP server is across a routed interface without a relay. The governing technical reason is: DHCP broadcast discovery normally requires relay handling when the server is in another IP subnet. Verify by checking: Discover/offer/request/ack exchange completes and clients receive correct scopes and gateways. Incorrect Answers A:An enterprise polls infrastructure over legacy unauthenticated SNMP and risks exposing operational data across shared networks. This is where using supported SNMPv3 authentication/privacy and authorizing specific management targets would help. By contrast, newly moved office endpoints cannot receive IPv4 leases because their DHCP server is across a routed interface without a relay. DHCP broadcast discovery normally requires relay handling when the server is in another IP subnet. C:When newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries, inspecting interface and forwarding-plane readiness, then restore the failed forwarding-table synchronization before accepting traffic could be appropriate. Here, newly moved office endpoints cannot receive IPv4 leases because their DHCP server is across a routed interface without a relay. Configure DHCP relay on the correct client-facing interface and verify reachability to the DHCP server. D: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, newly moved office endpoints cannot receive IPv4 leases because their DHCP server is across a routed interface without a relay. Discover/offer/request/ack exchange completes and clients receive correct scopes and gateways.
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.