Question 500The datacom engineering team at a cloud hosting provider after an incident review reviews this independent fictional networking case: A training-video multicast group begins leaking beyond its approved distribution region after a transport upgrade. If this issue remains unresolved, what immediate availability or security risk follows most directly? Expired host state can cause intermittent multicast loss without underlying link failures Failed RPF can interrupt multicast while unicast service tests still succeed Mismatched RPs can partition an otherwise connected multicast domain Unbounded distribution may waste WAN capacity and expose internal streams ExplanationCorrect Answer D:Unbounded distribution may waste WAN capacity and expose internal streams. Leaving the exact fault unresolved means: A training-video multicast group begins leaking beyond its approved distribution region after a transport upgrade. The intended response is: Apply appropriate multicast boundary and scope controls for the group range. Incorrect Answers A:An access VLAN loses a multicast receiver after a quiet period because periodic IGMP membership updates never reach the upstream querier. In that situation, expired host state can cause intermittent multicast loss without underlying link failures. Here instead, a training-video multicast group begins leaking beyond its approved distribution region after a transport upgrade. Multicast distribution should follow explicitly defined group membership and boundary policy, not blanket flooding. B:Failed RPF can interrupt multicast while unicast service tests still succeed. That risk belongs to a separate condition: A multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. Here, a training-video multicast group begins leaking beyond its approved distribution region after a transport upgrade; apply appropriate multicast boundary and scope controls for the group range. C:A multicast source in a sparse-mode domain sends traffic but remote listeners receive nothing because the routers have inconsistent RP mappings. In that situation, mismatched RPs can partition an otherwise connected multicast domain. Here instead, a training-video multicast group begins leaking beyond its approved distribution region after a transport upgrade. Receivers inside scope join successfully while test receivers outside it receive no multicast payload.
Question 501The datacom engineering team at an energy distribution business while tracing a degraded application flow reviews this independent fictional networking case: An ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. A proposed remedy is: Apply appropriately scoped external prefix summarization at the originating ASBR. Which technical principle most directly supports this remedy? ASBR route aggregation reduces external advertisements without replacing ordinary ABR interarea summarization OSPF interarea routing depends on backbone connectivity through area 0 Aggregating interarea advertisements can reduce control-plane state but must not capture unreachable space DR and BDR election on broadcast networks is influenced by configured interface priority and is not a direct lowest-cost path election ExplanationCorrect Answer A:ASBR route aggregation reduces external advertisements without replacing ordinary ABR interarea summarization. This directly explains why the corrective operation is appropriate: Apply appropriately scoped external prefix summarization at the originating ASBR. The observed acceptance evidence should be: Remote OSPF routers receive the summary and reach all intended attached external subnets. Incorrect Answers B:OSPF interarea routing depends on backbone connectivity through area 0. That rule governs a different situation: Two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. Here, an ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. ASBR route aggregation reduces external advertisements without replacing ordinary ABR interarea summarization. C:Several closely related access prefixes create unnecessary interarea LSA churn because no ABR aggregation is applied. Aggregating interarea advertisements can reduce control-plane state but must not capture unreachable space. The current condition differs: An ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. Apply appropriately scoped external prefix summarization at the originating ASBR. D:A shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. DR and BDR election on broadcast networks is influenced by configured interface priority and is not a direct lowest-cost path election. The current condition differs: An ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. Remote OSPF routers receive the summary and reach all intended attached external subnets.
Question 502The datacom engineering team at a local rail transit network while validating change-control evidence reviews this independent fictional networking case: A multicast source in a sparse-mode domain sends traffic but remote listeners receive nothing because the routers have inconsistent RP mappings. Which corrective engineering action most directly addresses this problem? Validate PIM-SM source-specific shortest-path switching and the unicast route toward the source Configure a consistent appropriate rendezvous point mapping and inspect source registration paths Verify the multicast RPF route and correct source reachability or appropriate multicast routing state Repair IGMP query/reply processing and verify membership refresh timers ExplanationCorrect Answer B:Configure a consistent appropriate rendezvous point mapping and inspect source registration paths. This is the specific action that addresses the fictional fault: A multicast source in a sparse-mode domain sends traffic but remote listeners receive nothing because the routers have inconsistent RP mappings. The governing technical reason is: PIM-SM uses an RP to build initial shared-tree reachability for ASM groups. Verify by checking: RP mappings agree and receivers establish expected PIM joins with working source traffic. Incorrect Answers A:A distant receiver continues using a long shared tree after a short direct source path is available and capacity is strained. This is where validating PIM-SM source-specific shortest-path switching and the unicast route toward the source would help. By contrast, a multicast source in a sparse-mode domain sends traffic but remote listeners receive nothing because the routers have inconsistent RP mappings. PIM-SM uses an RP to build initial shared-tree reachability for ASM groups. C:A multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. This is where verifying the multicast RPF route and correcting source reachability or appropriate multicast routing state would help. By contrast, a multicast source in a sparse-mode domain sends traffic but remote listeners receive nothing because the routers have inconsistent RP mappings. Configure a consistent appropriate rendezvous point mapping and inspect source registration paths. D:When an access VLAN loses a multicast receiver after a quiet period because periodic IGMP membership updates never reach the upstream querier, repairing IGMP query/reply processing and verifying membership refresh timers could be appropriate. Here, a multicast source in a sparse-mode domain sends traffic but remote listeners receive nothing because the routers have inconsistent RP mappings. RP mappings agree and receivers establish expected PIM joins with working source traffic.
Question 503The datacom engineering team at a warehouse automation provider during a topology consistency review reviews this independent fictional networking case: A static backup path remains inactive while the primary next hop fails beyond a locally Up interface. Which corrective engineering action most directly addresses this problem? Tune BFD intervals and multiplier for supported device and transport capabilities Check supported BFD modes and mutually acceptable timer negotiation before coupling routing failover Use supported BFD or remote path tracking to withdraw the unusable static next hop Verify the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover ExplanationCorrect Answer C:Use supported BFD or remote path tracking to withdraw the unusable static next hop. This is the specific action that addresses the fictional fault: A static backup path remains inactive while the primary next hop fails beyond a locally Up interface. The governing technical reason is: Physical interface state alone cannot detect all remote next-hop failures. Verify by checking: An injected upstream failure withdraws the primary route and backup traffic succeeds. Incorrect Answers A:When a high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling, tuning BFD intervals and multiplier for supported device and transport capabilities could be appropriate. Here, 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. B:When two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior, checking supported BFD modes and mutually acceptable timer negotiation before coupling routing failover could be appropriate. Here, a static backup path remains inactive while the primary next hop fails beyond a locally Up interface. Use supported BFD or remote path tracking to withdraw the unusable static next hop. D:Verifying the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover is relevant 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. It does not resolve this case: A static backup path remains inactive while the primary next hop fails beyond a locally Up interface. An injected upstream failure withdraws the primary route and backup traffic succeeds.
Question 504The datacom engineering team at an airport facilities team while tracing a degraded application flow reviews this independent fictional networking case: OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change. 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 Coordinate the configured authentication mode and active key material at both ends of the link Reconcile the actual link MTU and OSPF database exchange compatibility before retransmitting LSAs Tighten the configured summary to reachable address blocks and test interarea destinations ExplanationCorrect Answer C:Reconcile the actual link MTU and OSPF database exchange compatibility before retransmitting LSAs. This is the specific action that addresses the fictional fault: OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change. The governing technical reason is: MTU incompatibility can disrupt OSPF database description negotiation and leave neighbors partially adjacent. Verify by checking: Database description exchange completes and the OSPF neighbor reaches Full state. 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, OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change. MTU incompatibility can disrupt OSPF database description negotiation and leave neighbors partially adjacent. B:An OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. This is where coordinating the configured authentication mode and active key material at both ends of the link would help. By contrast, OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change. Reconcile the actual link MTU and OSPF database exchange compatibility before retransmitting LSAs. D:An area border router advertises a broad summary that includes subnets withdrawn after a site closure. This is where tightening the configured summary to reachable address blocks and testing interarea destinations would help. By contrast, OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change. Database description exchange completes and the OSPF neighbor reaches Full state.
Question 505The datacom engineering team at an agricultural equipment distributor after an incident review 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. The team applies this remedy: Provide a resolvable route to the next hop or replace it with the verified directly reachable next hop. Which observation would directly demonstrate that this specific issue is resolved? Forwarding entries are present on the line card and a test flow traverses the intended interface The routing table and packet-path trace select the intended prefix and next hop Session state is present for the initiator and replies pass without extra broad allow rules The static route is active and its recursive next hop resolves to an operational interface ExplanationCorrect Answer D:The static route is active and its recursive next hop resolves to an operational interface. This is a directly observable check for the proposed correction: Provide a resolvable route to the next hop or replace it with the verified directly reachable next hop. The particular failure being investigated is: A static route is configured to a next-hop address that is absent from the local routing table and never becomes active. Incorrect Answers A: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. This observation does not prove the correction for the reported defect: 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. B:The routing table and packet-path trace select the intended prefix and next hop. This check belongs to a branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. The actual defect is different: 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. C:Session state is present for the initiator and replies pass without extra broad allow rules. This check belongs to an administrator adds broad reverse-direction allow rules to fix response packets that should already match a healthy established session. The actual defect is different: A static route is configured to a next-hop address that is absent from the local routing table and never becomes active. Unresolved recursive next hops create a persistent black hole despite syntactically valid configuration.
Question 506The 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. The team applies this remedy: Restrict management access to approved administrative source networks and enforce strong authentication. Which observation would directly demonstrate that this specific issue is resolved? A controlled AAA outage allows an approved emergency operator and audit records document the session Guest-originated SSH probes are rejected while approved administrative access continues Each tenant sees only approved VRF routes and prohibited cross-tenant probes fail Forged ARP updates are blocked and legitimate ARP resolution continues for approved endpoints ExplanationCorrect Answer B:Guest-originated SSH probes are rejected while approved administrative access continues. This is a directly observable check for the proposed correction: Restrict management access to approved administrative source networks and enforce strong authentication. The particular failure being investigated is: A router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. Incorrect Answers A:A controlled AAA outage allows an approved emergency operator and audit records document the session. That result could validate a repair when a campus authentication server becomes unreachable and network admins cannot access devices during an outage. Here, 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. C:Each tenant sees only approved VRF routes and prohibited cross-tenant probes fail. This check belongs to traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance. The actual defect is different: 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:Forged ARP updates are blocked and legitimate ARP resolution continues for approved endpoints. That result could validate a repair when an attacker on a user VLAN advertises the gateway's IPv4 address with a forged MAC and steals nearby sessions. Here, a router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign; unrestricted management access increases credential-attack surface and potential device compromise.
Question 507The datacom engineering team at a call center outsourcer after a planned hardware refresh reviews this independent fictional networking case: One SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space. Which corrective engineering action most directly addresses this problem? Replan channel assignments and transmit power based on measured co-channel contention Harmonize mobility-domain forwarding and VLAN/anchor design so approved roams preserve intended IP connectivity Validate client and controller support for appropriate fast-transition roaming mechanisms Review the WLAN VLAN pool mapping and rebalance supported client distribution with consistent DHCP scopes ExplanationCorrect Answer D:Review the WLAN VLAN pool mapping and rebalance supported client distribution with consistent DHCP scopes. This is the specific action that addresses the fictional fault: One SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space. The governing technical reason is: A VLAN pool can distribute WLAN clients across logical broadcast domains when pool and DHCP design are coherent. Verify by checking: Client associations spread across permitted VLANs and each receives an address from its own correct scope. Incorrect Answers A:Replanning channel assignments and transmit power based on measured co-channel contention is relevant when a large lecture hall experiences low Wi-Fi throughput even with strong signal because neighboring AP radios overlap excessively on busy channels. It does not resolve this case: 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. B:A client changes IP address during normal intra-campus roaming because neighboring APs anchor it to incompatible service VLANs. This is where harmonizing mobility-domain forwarding and VLAN/anchor design so approved roams preserve intended IP connectivity would help. By contrast, one SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space. Review the WLAN VLAN pool mapping and rebalance supported client distribution with consistent DHCP scopes. C:When voice handsets suffer several seconds of audio interruption after moving between APs because full authentication runs on every transition, validating client and controller support for appropriate fast-transition roaming mechanisms could be appropriate. Here, one SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space. Client associations spread across permitted VLANs and each receives an address from its own correct scope.
Question 508The datacom engineering team at an insurance processing company while validating change-control evidence reviews this independent fictional networking case: An ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. The team applies this remedy: Apply appropriately scoped external prefix summarization at the originating ASBR. Which observation would directly demonstrate that this specific issue is resolved? SPF routing to the remote prefix favors the intended link and converges after the change The backbone receives the intended summary and test routes to each component subnet succeed Remote OSPF routers receive the summary and reach all intended attached external subnets Both routers progress to Full adjacency and neighbor timer diagnostics agree ExplanationCorrect Answer C:Remote OSPF routers receive the summary and reach all intended attached external subnets. This is a directly observable check for the proposed correction: Apply appropriately scoped external prefix summarization at the originating ASBR. The particular failure being investigated is: An ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. 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, a result such as this is useful: SPF routing to the remote prefix favors the intended link and converges after the change. For the reported fault, an ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables; ASBR route aggregation reduces external advertisements without replacing ordinary ABR interarea summarization. B:The backbone receives the intended summary and test routes to each component subnet succeed. This check belongs to several closely related access prefixes create unnecessary interarea LSA churn because no ABR aggregation is applied. The actual defect is different: An ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. Apply appropriately scoped external prefix summarization at the originating ASBR. D: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: An ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. Unaggregated external advertisements can magnify flaps across the routing domain.
Question 509The 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. Which corrective engineering action most directly addresses this problem? Enable supported BFD tracking for the OSPF adjacency and validate timer compatibility Correct VRRP group placement and virtual IPv4 address on the intended broadcast domain Use supported BFD or remote path tracking to withdraw the unusable static next hop Set and document appropriate VRRP priorities and supported preemption behavior ExplanationCorrect Answer B:Correct VRRP group placement and virtual IPv4 address on the intended broadcast domain. This is the specific action that addresses the fictional fault: Two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error. The governing technical reason is: A VRRP group represents a virtual gateway within a specific local layer-2 segment. Verify by checking: Matching gateway interfaces negotiate one Master and user devices reach the correct virtual address. Incorrect Answers A:When OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection, enabling supported BFD tracking for the OSPF adjacency and validating timer compatibility could be appropriate. Here, 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. C:When a static backup path remains inactive while the primary next hop fails beyond a locally Up interface, using supported BFD or remote path tracking to withdraw the unusable static next hop could be appropriate. Here, 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. D:A backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. This is where setting and documenting appropriate VRRP priorities and supported preemption behavior would help. By contrast, two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error. Matching gateway interfaces negotiate one Master and user devices reach the correct virtual address.
Question 510The datacom engineering team at an e-commerce fulfillment center while validating change-control evidence reviews this independent fictional networking case: Operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. The team applies this remedy: Inspect the BGP best-path decision sequence and correct the higher-priority policy attribute before modifying AS_PATH. Which observation would directly demonstrate that this specific issue is resolved? Session source addresses match loopbacks and both peers establish consistently Best-path diagnostics show the winning attribute and route selection matches intent 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:Best-path diagnostics show the winning attribute and route selection matches intent. This is a directly observable check for the proposed correction: Inspect the BGP best-path decision sequence and correct the higher-priority policy attribute before modifying AS_PATH. The particular failure being investigated is: Operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. Incorrect Answers A: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, 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:Two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. EVPN control-plane entries retain unique per-origin VPN identifiers and remote paths coexist. This observation does not prove the correction for the reported defect: 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 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. This observation does not prove the correction for the reported defect: Operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. Incomplete understanding of attribute order leads to ineffective and potentially disruptive policy changes.