Question 170The datacom engineering team at an industrial safety organization during a simulated failover test reviews this independent fictional networking case: A receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. 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 Persistent shared-tree detours can congest core links and degrade streaming performance Misapplied ASM behavior can select an unintended stream source and undermine access expectations Uncontrolled multicast flooding consumes bandwidth and can overload unrelated endpoints ExplanationCorrect Answer C:Misapplied ASM behavior can select an unintended stream source and undermine access expectations. Leaving the exact fault unresolved means: A receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. The intended response is: Configure compatible SSM group ranges and source-aware membership signalling. Incorrect Answers A:When an access VLAN loses a multicast receiver after a quiet period because periodic IGMP membership updates never reach the upstream querier, expired host state can cause intermittent multicast loss without underlying link failures. The present failure is different: A receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. Source-specific multicast forwarding is tied to a particular source and group rather than RP-based ASM discovery. B:Persistent shared-tree detours can congest core links and degrade streaming performance. That risk belongs to a separate condition: A distant receiver continues using a long shared tree after a short direct source path is available and capacity is strained. Here, a receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state; configure compatible SSM group ranges and source-aware membership signalling. D:Uncontrolled multicast flooding consumes bandwidth and can overload unrelated endpoints. That risk belongs to a separate condition: A switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built. Here, a receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state; the receiver joins the intended source/group pair and cannot accidentally switch to a different sender.
Question 171The datacom engineering team at a wholesale market association while tracing a degraded application flow 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 Poor VLAN-pool design can exhaust one DHCP subnet and block new wireless clients Unexpected address changes can reset voice and real-time application sessions Uncorrected RF contention can undermine a high-density WLAN despite healthy AP links ExplanationCorrect Answer C: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. B:Poor VLAN-pool design can exhaust one DHCP subnet and block new wireless clients. That risk belongs to a separate condition: One SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space. 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. D:Uncorrected RF contention can undermine a high-density WLAN despite healthy AP links. That consequence could follow when 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; a mobility test keeps the expected address and established application sessions while moving across APs.
Question 172The datacom engineering team at an automotive parts manufacturer as part of an acceptance test reviews this independent fictional networking case: 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. A proposed remedy is: Verify the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover. Which technical principle most directly supports this remedy? BFD session state depends on interoperable mode and timing negotiation between peers BFD provides rapid bidirectional failure detection to subscribed routing protocols A VRRP group represents a virtual gateway within a specific local layer-2 segment VRRP continuity depends on end hosts and switches forwarding toward the current virtual gateway owner ExplanationCorrect Answer D:VRRP continuity depends on end hosts and switches forwarding toward the current virtual gateway owner. This directly explains why the corrective operation is appropriate: Verify the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover. The observed acceptance evidence should be: Host neighbor tables resolve to the expected virtual MAC and sessions recover after failover. Incorrect Answers A:BFD session state depends on interoperable mode and timing negotiation between peers. That rule governs a different situation: Two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior. Here, 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. VRRP continuity depends on end hosts and switches forwarding toward the current virtual gateway owner. B: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. The current condition differs: 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. Verify the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover. C:A VRRP group represents a virtual gateway within a specific local layer-2 segment. That rule governs a different situation: Two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error. Here, 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. Host neighbor tables resolve to the expected virtual MAC and sessions recover after failover.
Question 173The datacom engineering team at a municipal transport operator during a simulated failover test reviews this independent fictional networking case: A WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. Which corrective engineering action most directly addresses this problem? Add health-aware policy-path handling or withdraw the policy on next-hop failure Tag redistributed routes and deny re-entry of the marked route class at the opposite redistribution point Apply appropriate traffic shaping at the controlled egress and verify contracted rate behavior Constrain ge/le mask-length ranges and test boundary prefix acceptance ExplanationCorrect Answer C:Apply appropriate traffic shaping at the controlled egress and verify contracted rate behavior. This is the specific action that addresses the fictional fault: A WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. The governing technical reason is: Policing enforces a rate by remarking or dropping excess traffic, whereas shaping buffers excess bursts for later transmission. Verify by checking: Burst loss decreases while sustained throughput remains within the agreed service rate. Incorrect Answers A:Policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. This is where adding health-aware policy-path handling or withdraw the policy on next-hop failure would help. By contrast, a WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. Policing enforces a rate by remarking or dropping excess traffic, whereas shaping buffers excess bursts for later transmission. B:Two redistribution points repeatedly re-inject learned routes between OSPF and another IGP and churn route entries. This is where tagging redistributed routes and deny re-entry of the marked route class at the opposite redistribution point would help. By contrast, a WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. Apply appropriate traffic shaping at the controlled egress and verify contracted rate behavior. D:Constraining ge/le mask-length ranges and testing boundary prefix acceptance is relevant when a routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes. It does not resolve this case: A WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. Burst loss decreases while sustained throughput remains within the agreed service rate.
Question 174The datacom engineering team at a university research campus while tracing a degraded application flow reviews this independent fictional networking case: Core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. Which corrective engineering action most directly addresses this problem? Set compatible IS-IS circuit levels consistent with the core design Compare sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization Align the IS-IS area portion of the NET or revise the intended L1/L2 boundary Tune IS-IS DIS priority on the shared LAN and validate neighbor continuity after a planned election ExplanationCorrect Answer B:Compare sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization. This is the specific action that addresses the fictional fault: Core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. The governing technical reason is: IS-IS link-state consistency depends on reliable LSP version synchronization within each level. Verify by checking: Peers converge to the same current LSP sequence and the affected route becomes stable. Incorrect Answers A:When a transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2, setting compatible IS-IS circuit levels consistent with the core design could be appropriate. Here, core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. IS-IS link-state consistency depends on reliable LSP version synchronization within each level. C:Aligning the IS-IS area portion of the NET or revise the intended L1/L2 boundary is relevant when two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses. It does not resolve this case: Core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. Compare sequence numbers and lifetime state, then restore proper CSNP/PSNP-driven LSP synchronization. D:Tuning IS-IS DIS priority on the shared LAN and validating neighbor continuity after a planned election is relevant when a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. It does not resolve this case: 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.
Question 175The datacom engineering team at a satellite ground station operator after an incident review reviews this independent fictional networking case: An IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly. Which corrective engineering action most directly addresses this problem? Resolve duplicate addressing and verify Neighbor Discovery duplicate-address-detection behavior Correct router advertisement prefix and flags for the chosen IPv6 addressing design Specify the appropriate egress interface with the link-local next hop and verify neighbor discovery Mark host-facing interfaces passive while still advertising their connected subnet through the intended OSPF process ExplanationCorrect Answer C:Specify the appropriate egress interface with the link-local next hop and verify neighbor discovery. This is the specific action that addresses the fictional fault: An IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly. The governing technical reason is: IPv6 link-local addresses are interface scoped and may require egress context for next-hop resolution. Verify by checking: The route installs with the expected interface and reachability probes succeed. Incorrect Answers A:When two replacement servers are configured with the same IPv6 address and one fails to bring the address online, resolving duplicate addressing and verifying Neighbor Discovery duplicate-address-detection behavior could be appropriate. Here, an IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly. IPv6 link-local addresses are interface scoped and may require egress context for next-hop resolution. B:Correcting router advertisement prefix and flags for the chosen IPv6 addressing design is relevant when clients on a new IPv6 VLAN fail to obtain global addresses because router advertisements lack the intended autonomous prefix information. It does not resolve this case: An IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly. Specify the appropriate egress interface with the link-local next hop and verify neighbor discovery. 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, an IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly. The route installs with the expected interface and reachability probes succeed.
Question 176The datacom engineering team at a cloud hosting provider after an incident review 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? SPF can only remove unusable paths promptly after their topology state is correctly detected and flooded OSPF adjacency establishment requires compatible hello parameters on the neighbor-facing interfaces ABR summaries reduce LSDB size but overbroad summaries can attract packets for nonexistent destinations MTU incompatibility can disrupt OSPF database description negotiation and leave neighbors partially adjacent ExplanationCorrect Answer B: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:One router continues advertising a failed transit link because the local interface reports Up while an intermediate transport component is down. SPF can only remove unusable paths promptly after their topology state is correctly detected and flooded. The current condition differs: 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. C:ABR summaries reduce LSDB size but overbroad summaries can attract packets for nonexistent destinations. That rule governs a different situation: An area border router advertises a broad summary that includes subnets withdrawn after a site closure. 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:MTU incompatibility can disrupt OSPF database description negotiation and leave neighbors partially adjacent. That rule governs a different situation: OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change. 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 177The datacom engineering team at a hospital imaging provider during a controlled network cutover reviews this independent fictional networking case: A receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. Which corrective engineering action most directly addresses this problem? Verify the multicast RPF route and correct source reachability or appropriate multicast routing state Validate PIM-SM source-specific shortest-path switching and the unicast route toward the source Configure compatible SSM group ranges and source-aware membership signalling Repair IGMP query/reply processing and verify membership refresh timers ExplanationCorrect Answer C:Configure compatible SSM group ranges and source-aware membership signalling. This is the specific action that addresses the fictional fault: A receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. The governing technical reason is: Source-specific multicast forwarding is tied to a particular source and group rather than RP-based ASM discovery. Verify by checking: The receiver joins the intended source/group pair and cannot accidentally switch to a different sender. Incorrect Answers A:Verifying the multicast RPF route and correcting source reachability or appropriate multicast routing state is relevant when a multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. It does not resolve this case: A receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. Source-specific multicast forwarding is tied to a particular source and group rather than RP-based ASM discovery. B: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 receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. Configure compatible SSM group ranges and source-aware membership signalling. D:An access VLAN loses a multicast receiver after a quiet period because periodic IGMP membership updates never reach the upstream querier. This is where repairing IGMP query/reply processing and verifying membership refresh timers would help. By contrast, a receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. The receiver joins the intended source/group pair and cannot accidentally switch to a different sender.
Question 178The datacom engineering team at a health laboratory network after a planned hardware refresh reviews this independent fictional networking case: An IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly. The team applies this remedy: Specify the appropriate egress interface with the link-local next hop and verify neighbor discovery. Which observation would directly demonstrate that this specific issue is resolved? Clients form valid unique global addresses and default routes from the expected RA source The route installs with the expected interface and reachability probes succeed The conflicting address is removed and DAD completes without duplicate notifications Each tenant sees only approved VRF routes and prohibited cross-tenant probes fail ExplanationCorrect Answer B:The route installs with the expected interface and reachability probes succeed. This is a directly observable check for the proposed correction: Specify the appropriate egress interface with the link-local next hop and verify neighbor discovery. The particular failure being investigated is: An IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly. Incorrect Answers A: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, an IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly; IPv6 link-local addresses are interface scoped and may require egress context for next-hop resolution. C:The conflicting address is removed and DAD completes without duplicate notifications. That result could validate a repair when two replacement servers are configured with the same IPv6 address and one fails to bring the address online. Here, an IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly; specify the appropriate egress interface with the link-local next hop and verify neighbor discovery. D:Each tenant sees only approved VRF routes and prohibited cross-tenant probes fail. That result could validate a repair when traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance. Here, an IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly; ambiguous link-local next hops can make IPv6 forwarding fail despite apparently valid prefixes.
Question 179The datacom engineering team at an engineering consultancy during a controlled network cutover reviews this independent fictional networking case: An attacker on a user VLAN advertises the gateway's IPv4 address with a forged MAC and steals nearby sessions. The team applies this remedy: Deploy appropriate ARP spoofing protection based on trusted bindings and switch capabilities. Which observation would directly demonstrate that this specific issue is resolved? Forged ARP updates are blocked and legitimate ARP resolution continues for approved endpoints Guest-originated SSH probes are rejected while approved administrative access continues Unauthorized control attempts are rejected while approved peers remain stable Session/NAT records and bidirectional traces show the intended translated tuple and next hop ExplanationCorrect Answer A:Forged ARP updates are blocked and legitimate ARP resolution continues for approved endpoints. This is a directly observable check for the proposed correction: Deploy appropriate ARP spoofing protection based on trusted bindings and switch capabilities. The particular failure being investigated is: An attacker on a user VLAN advertises the gateway's IPv4 address with a forged MAC and steals nearby sessions. Incorrect Answers B:Guest-originated SSH probes are rejected while approved administrative access continues. That result could validate a repair when a router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. Here, an attacker on a user VLAN advertises the gateway's IPv4 address with a forged MAC and steals nearby sessions; layer-2 address validation can prevent untrusted hosts from impersonating a local gateway. C:Unauthorized control attempts are rejected while approved peers remain stable. This check belongs to a provider-facing interface accepts unexpected routing-control connections from an unapproved adjacent host. The actual defect is different: An attacker on a user VLAN advertises the gateway's IPv4 address with a forged MAC and steals nearby sessions. Deploy appropriate ARP spoofing protection based on trusted bindings and switch capabilities. D:A firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. Session/NAT records and bidirectional traces show the intended translated tuple and next hop. This observation does not prove the correction for the reported defect: An attacker on a user VLAN advertises the gateway's IPv4 address with a forged MAC and steals nearby sessions. Unchecked gateway impersonation enables local traffic interception and session compromise.
Question 180The 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. 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? iBGP commonly preserves next-hop information, so learned routes require resolvable next hops Prefix-limit controls can bound routing state growth when a neighbor violates expected route scale A base BGP TCP session does not imply that every MP-BGP address family is negotiated and active Higher LOCAL_PREF is preferred within an autonomous system and is normally not passed to eBGP neighbors ExplanationCorrect Answer C: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:When an iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally, iBGP commonly preserves next-hop information, so learned routes require resolvable next hops. By contrast, 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:Prefix-limit controls can bound routing state growth when a neighbor violates expected route scale. That rule governs a different situation: A provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. Here, 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:When a multihomed autonomous system sends outbound traffic via a paid backup despite the intended primary exit, higher LOCAL_PREF is preferred within an autonomous system and is normally not passed to eBGP neighbors. By contrast, 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.