Question 30The datacom engineering team at a sports event venue during a topology consistency review reviews this independent fictional networking case: An IS-IS adjacency drops after only one of two core routers receives a new authentication key. The team applies this remedy: Coordinate IS-IS authentication and key rollover across the peer link. Which observation would directly demonstrate that this specific issue is resolved? Peers converge to the same current LSP sequence and the affected route becomes stable The peer adjacency is Up at the intended level and corresponding LSPs exchange IS-IS hellos and LSP floods succeed and the remote LSDB converges Authentication failures cease and level-appropriate neighbor state returns Up ExplanationCorrect Answer D:Authentication failures cease and level-appropriate neighbor state returns Up. This is a directly observable check for the proposed correction: Coordinate IS-IS authentication and key rollover across the peer link. The particular failure being investigated is: An IS-IS adjacency drops after only one of two core routers receives a new authentication key. Incorrect Answers A:Core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. Peers converge to the same current LSP sequence and the affected route becomes stable. This observation does not prove the correction for the reported defect: An IS-IS adjacency drops after only one of two core routers receives a new authentication key. IS-IS protocol authentication must match across neighbor exchanges to maintain trusted adjacencies. B:When a transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2, a result such as this is useful: The peer adjacency is Up at the intended level and corresponding LSPs exchange. For the reported fault, an IS-IS adjacency drops after only one of two core routers receives a new authentication key; coordinate IS-IS authentication and key rollover across the peer link. C:IS-IS hellos and LSP floods succeed and the remote LSDB converges. This check belongs to IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. The actual defect is different: An IS-IS adjacency drops after only one of two core routers receives a new authentication key. Split key deployment can sever a core routing domain even when the circuit is physically healthy.
Question 31The datacom engineering team at a distribution warehouse group during a simulated failover test reviews this independent fictional networking case: Two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree. If this issue remains unresolved, what immediate availability or security risk follows most directly? Unrestricted routing peers can inject false reachability and disrupt a network segment A NAT-only repair can leave return traffic asymmetric and business sessions broken A superficially Up IKE session can conceal complete loss of protected service traffic Improper routing-instance assignment can expose one customer's traffic to another ExplanationCorrect Answer C:A superficially Up IKE session can conceal complete loss of protected service traffic. Leaving the exact fault unresolved means: Two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree. The intended response is: Align the protected subnet selectors and routing for the authorized tunnel traffic. Incorrect Answers A:Unrestricted routing peers can inject false reachability and disrupt a network segment. That consequence could follow when a provider-facing interface accepts unexpected routing-control connections from an unapproved adjacent host. Here, two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree; IPsec security associations must cover compatible protected flows even when IKE negotiation is successful. B:A firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. In that situation, a NAT-only repair can leave return traffic asymmetric and business sessions broken. Here instead, two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree. Align the protected subnet selectors and routing for the authorized tunnel traffic. D:Traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance. In that situation, improper routing-instance assignment can expose one customer's traffic to another. Here instead, two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree. Tunnel SA counters increase for the approved subnet and remote application traffic succeeds.
Question 32The datacom engineering team at a regional newspaper publisher after an incident review reviews this independent fictional networking case: A security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. A proposed remedy is: Place the filter on the correct ingress or egress direction based on the observed packet path. Which technical principle most directly supports this remedy? QoS markings can be rewritten at domain boundaries; end-to-end class treatment requires consistent mapping ACL matching is evaluated at the attachment point and direction, not according to a rule's descriptive name Redistribution can cross routing trust boundaries and must specify which routes are authorized to cross Policing enforces a rate by remarking or dropping excess traffic, whereas shaping buffers excess bursts for later transmission ExplanationCorrect Answer B:ACL matching is evaluated at the attachment point and direction, not according to a rule's descriptive name. This directly explains why the corrective operation is appropriate: Place the filter on the correct ingress or egress direction based on the observed packet path. The observed acceptance evidence should be: Counters increment for prohibited guest probes and approved management flows remain permitted. Incorrect Answers A:When 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. By contrast, a security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets; ACL matching is evaluated at the attachment point and direction, not according to a rule's descriptive name. C:A border router injects internal transit and management prefixes into external BGP due to unrestricted redistribution. Redistribution can cross routing trust boundaries and must specify which routes are authorized to cross. The current condition differs: A security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. Place the filter on the correct ingress or egress direction based on the observed packet path. D:Policing enforces a rate by remarking or dropping excess traffic, whereas shaping buffers excess bursts for later transmission. That rule governs a different situation: A WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. Here, a security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. Counters increment for prohibited guest probes and approved management flows remain permitted.
Question 33The datacom engineering team at an e-commerce fulfillment center while validating change-control evidence reviews this independent fictional networking case: A user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port. If this issue remains unresolved, what immediate availability or security risk follows most directly? Split-brain ownership can cause MAC flaps and severe layer-2 instability Accidental region borders reduce planned load sharing and may alter blocked ports Unprotected edge ports can introduce layer-2 loops that overwhelm shared broadcast segments Misaligned instance mappings can strand a subset of VLANs while others work ExplanationCorrect Answer C:Unprotected edge ports can introduce layer-2 loops that overwhelm shared broadcast segments. Leaving the exact fault unresolved means: A user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port. The intended response is: Apply supported BPDU protection at legitimate edge ports and investigate the unexpected bridge connection. Incorrect Answers A:A campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services. In that situation, split-brain ownership can cause MAC flaps and severe layer-2 instability. Here instead, 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. B:Accidental region borders reduce planned load sharing and may alter blocked ports. That consequence could follow when two switches intended in one MSTP region behave as if separated by a regional boundary after an unnoticed configuration edit. Here, a user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port; apply supported BPDU protection at legitimate edge ports and investigate the unexpected bridge connection. D: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 user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port; a received BPDU triggers the configured protective response and no loop appears.
Question 34The datacom engineering team at a retail banking network as part of an acceptance test reviews this independent fictional networking case: A BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. Which corrective engineering action most directly addresses this problem? Set an appropriate maximum-prefix threshold and test the negotiated recovery behavior Restore transport IP reachability to the neighbor before changing BGP route policies Enable and validate the correct EVPN address-family capability and policy on both peers Introduce a correctly designed iBGP route reflector cluster with appropriate clients and redundancy ExplanationCorrect Answer B:Restore transport IP reachability to the neighbor before changing BGP route policies. This is the specific action that addresses the fictional fault: A BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. The governing technical reason is: BGP runs over TCP and needs successful IP transport to its configured peer endpoint. Verify by checking: TCP port 179 connectivity works and the peer progresses to Established. Incorrect Answers A:A provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. This is where setting an appropriate maximum-prefix threshold and testing the negotiated recovery behavior would help. By contrast, 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. C:An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. This is where enabling and validating the correct EVPN address-family capability and policy on both peers would help. By contrast, a BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. Restore transport IP reachability to the neighbor before changing BGP route policies. D:Introducing a correctly designed iBGP route reflector cluster with appropriate clients and redundancy is relevant when a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. It does not resolve this case: A BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. TCP port 179 connectivity works and the peer progresses to Established.
Question 35The datacom engineering team at an engineering consultancy during a controlled network cutover reviews this independent fictional networking case: Two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. The team applies this remedy: Assign route distinguishers suitable for creating unique originating VPN route identifiers. 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 Captures and received-route diagnostics show the cyclic update rejected without route churn EVPN control-plane entries retain unique per-origin VPN identifiers and remote paths coexist Exported BGP routes contain only the authorized prefix and mask set ExplanationCorrect Answer C:EVPN control-plane entries retain unique per-origin VPN identifiers and remote paths coexist. This is a directly observable check for the proposed correction: Assign route distinguishers suitable for creating unique originating VPN route identifiers. The particular failure being investigated is: Two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. 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: Two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. Route distinguishers distinguish otherwise identical VPN address advertisements; they do not themselves control import permission. B: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 EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly; assign route distinguishers suitable for creating unique originating VPN route identifiers. D: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. This observation does not prove the correction for the reported defect: Two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. Duplicate route identifiers can obscure independent EVPN path advertisements.
Question 36The datacom engineering team at a government service campus after a monitored link change reviews this independent fictional networking case: An enterprise polls infrastructure over legacy unauthenticated SNMP and risks exposing operational data across shared networks. A proposed remedy is: Use supported SNMPv3 authentication/privacy and authorize specific management targets. Which technical principle most directly supports this remedy? Network management polling should use authenticated and encrypted protocol settings when sensitive telemetry is exposed DHCP broadcast discovery normally requires relay handling when the server is in another IP subnet On broadcast IS-IS circuits the DIS originates a pseudonode LSP and its election follows IS-IS priority rules Central WLAN control architectures require planned control-plane redundancy and AP recovery behavior ExplanationCorrect Answer A:Network management polling should use authenticated and encrypted protocol settings when sensitive telemetry is exposed. This directly explains why the corrective operation is appropriate: Use supported SNMPv3 authentication/privacy and authorize specific management targets. The observed acceptance evidence should be: Approved collectors receive data with validated SNMPv3 security and unauthenticated polls are rejected. Incorrect Answers B:DHCP broadcast discovery normally requires relay handling when the server is in another IP subnet. That rule governs a different situation: Newly moved office endpoints cannot receive IPv4 leases because their DHCP server is across a routed interface without a relay. Here, an enterprise polls infrastructure over legacy unauthenticated SNMP and risks exposing operational data across shared networks. Network management polling should use authenticated and encrypted protocol settings when sensitive telemetry is exposed. C:On broadcast IS-IS circuits the DIS originates a pseudonode LSP and its election follows IS-IS priority rules. That principle is relevant when a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. Here, an enterprise polls infrastructure over legacy unauthenticated SNMP and risks exposing operational data across shared networks; use supported SNMPv3 authentication/privacy and authorize specific management targets. D:Central WLAN control architectures require planned control-plane redundancy and AP recovery behavior. That rule governs a different situation: A wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller. Here, an enterprise polls infrastructure over legacy unauthenticated SNMP and risks exposing operational data across shared networks. Approved collectors receive data with validated SNMPv3 security and unauthenticated polls are rejected.
Question 37The datacom engineering team at an energy distribution business while tracing a degraded application flow reviews this independent fictional networking case: A campus authentication server becomes unreachable and network admins cannot access devices during an outage. A proposed remedy is: Test and configure a properly controlled emergency local access method consistent with AAA policy. Which technical principle most directly supports this remedy? IPsec security associations must cover compatible protected flows even when IKE negotiation is successful VRFs provide separate routing tables, and cross-VRF reachability must be deliberately controlled NAT changes packet addressing, but traffic still requires a correct routed egress and return path Centralized AAA improves accountability, but managed fallback must preserve both resilience and least privilege ExplanationCorrect Answer D:Centralized AAA improves accountability, but managed fallback must preserve both resilience and least privilege. This directly explains why the corrective operation is appropriate: Test and configure a properly controlled emergency local access method consistent with AAA policy. The observed acceptance evidence should be: A controlled AAA outage allows an approved emergency operator and audit records document the session. Incorrect Answers A:IPsec security associations must cover compatible protected flows even when IKE negotiation is successful. That principle is relevant when two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree. Here, a campus authentication server becomes unreachable and network admins cannot access devices during an outage; centralized AAA improves accountability, but managed fallback must preserve both resilience and least privilege. B:When traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance, VRFs provide separate routing tables, and cross-VRF reachability must be deliberately controlled. By contrast, a campus authentication server becomes unreachable and network admins cannot access devices during an outage; test and configure a properly controlled emergency local access method consistent with AAA policy. C:A firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. NAT changes packet addressing, but traffic still requires a correct routed egress and return path. The current condition differs: A campus authentication server becomes unreachable and network admins cannot access devices during an outage. A controlled AAA outage allows an approved emergency operator and audit records document the session.
Question 38The datacom engineering team at a library district network after a planned hardware refresh reviews this independent fictional networking case: A static route is configured to a next-hop address that is absent from the local routing table and never becomes active. Which corrective engineering action most directly addresses this problem? Provide a resolvable route to the next hop or replace it with the verified directly reachable next hop Inspect interface and forwarding-plane readiness, then restore the failed forwarding-table synchronization before accepting traffic Compare candidate prefixes and remove the unintended more-specific route before changing global route preferences Use supported BFD or remote path tracking to withdraw the unusable static next hop ExplanationCorrect Answer A:Provide a resolvable route to the next hop or replace it with the verified directly reachable next hop. This is the specific action that addresses the fictional fault: A static route is configured to a next-hop address that is absent from the local routing table and never becomes active. The governing technical reason is: A static route depending on recursive resolution cannot forward when its next-hop recursion fails. Verify by checking: The static route is active and its recursive next hop resolves to an operational interface. Incorrect Answers B:Inspecting interface and forwarding-plane readiness, then restore the failed forwarding-table synchronization before accepting traffic is relevant when newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries. It does not resolve this case: A static route is configured to a next-hop address that is absent from the local routing table and never becomes active. A static route depending on recursive resolution cannot forward when its next-hop recursion fails. C:Comparing candidate prefixes and removing the unintended more-specific route before changing global route preferences is relevant when a branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. It does not resolve this case: A static route is configured to a next-hop address that is absent from the local routing table and never becomes active. Provide a resolvable route to the next hop or replace it with the verified directly reachable next hop. D:Using supported BFD or remote path tracking to withdraw the unusable static next hop is relevant when a static backup path remains inactive while the primary next hop fails beyond a locally Up interface. It does not resolve this case: A static route is configured to a next-hop address that is absent from the local routing table and never becomes active. The static route is active and its recursive next hop resolves to an operational interface.
Question 39The datacom engineering team at an airport facilities team while tracing a degraded application flow reviews this independent fictional networking case: A backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. If this issue remains unresolved, what immediate availability or security risk follows most directly? Unplanned Master placement may steer client traffic over a less reliable exit Stale gateway MAC learning can prolong an otherwise successful VRRP switchover Failure beyond the local link can strand static-route traffic indefinitely Slow liveness detection can extend avoidable black-hole duration after link failure ExplanationCorrect Answer A:Unplanned Master placement may steer client traffic over a less reliable exit. Leaving the exact fault unresolved means: A backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. The intended response is: Set and document appropriate VRRP priorities and supported preemption behavior. Incorrect Answers B:When a host keeps sending traffic to the old gateway's MAC after a VRRP switchover because the access LAN fails to update its neighbor cache, stale gateway MAC learning can prolong an otherwise successful VRRP switchover. The present failure is different: A backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. VRRP Master election is priority based subject to ownership and preemption rules. C:Failure beyond the local link can strand static-route traffic indefinitely. That consequence could follow when a static backup path remains inactive while the primary next hop fails beyond a locally Up interface. Here, a backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy; set and document appropriate VRRP priorities and supported preemption behavior. D:Slow liveness detection can extend avoidable black-hole duration after link failure. That risk belongs to a separate condition: OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection. Here, a backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy; the planned primary device owns the virtual gateway after recovery and failover still works.
Question 40The datacom engineering team at a cloud hosting provider after an incident review 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? The best BGP route resolves to a live next hop and data-plane probes succeed after reconvergence All clients learn the intended prefixes and remain connected after a reflector failover Captures and received-route diagnostics show the cyclic update rejected without route churn The BGP neighbor is Established and its accepted prefixes match the approved provider list ExplanationCorrect Answer A: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 B:All clients learn the intended prefixes and remain connected after a reflector failover. This check belongs to a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. 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. BGP route eligibility depends on resolvable next hops and a functioning forwarding path. C: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, 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. D:The BGP neighbor is Established and its accepted prefixes match the approved provider list. That result could validate a repair when an edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS. Here, 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.