Question 200The datacom engineering team at a sports event venue during a topology consistency review reviews this independent fictional networking case: A VLAN with multicast hosts has no functioning IGMP querier after its original gateway moves away. The team applies this remedy: Enable a proper querier in the receiver VLAN and validate IGMP state maintenance. Which observation would directly demonstrate that this specific issue is resolved? Receivers inside scope join successfully while test receivers outside it receive no multicast payload Only subscribed access ports receive the feed and the multicast router port remains operational Periodic general queries are seen and switch membership entries remain refreshed The non-listener branch stops receiving the data after valid prune processing ExplanationCorrect Answer C:Periodic general queries are seen and switch membership entries remain refreshed. This is a directly observable check for the proposed correction: Enable a proper querier in the receiver VLAN and validate IGMP state maintenance. The particular failure being investigated is: A VLAN with multicast hosts has no functioning IGMP querier after its original gateway moves away. Incorrect Answers A:When a training-video multicast group begins leaking beyond its approved distribution region after a transport upgrade, a result such as this is useful: Receivers inside scope join successfully while test receivers outside it receive no multicast payload. For the reported fault, a VLAN with multicast hosts has no functioning IGMP querier after its original gateway moves away; without a querier, snooping membership tables can age out even while hosts remain attached. B:Only subscribed access ports receive the feed and the multicast router port remains operational. This check belongs to a switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built. The actual defect is different: A VLAN with multicast hosts has no functioning IGMP querier after its original gateway moves away. Enable a proper querier in the receiver VLAN and validate IGMP state maintenance. D:When a dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent, a result such as this is useful: The non-listener branch stops receiving the data after valid prune processing. For the reported fault, a VLAN with multicast hosts has no functioning IGMP querier after its original gateway moves away; group delivery becomes erratic when receiver membership is allowed to age silently.
Question 201The datacom engineering team at a municipal transport operator during a simulated failover 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? Apply explicit prefix-length-aware export policy limited to authorized aggregate space Repair next-hop recursion and underlying IGP convergence, not just the BGP session Audit reflector topology and preserve the standard ORIGINATOR_ID and CLUSTER_LIST loop controls Restore transport IP reachability to the neighbor before changing BGP route policies ExplanationCorrect Answer D: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:An accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. This is where applying explicit prefix-length-aware export policy limited to authorized aggregate space 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. B: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: 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. C:When an iBGP route reflected through overlapping clusters returns toward its originator unexpectedly, auditing reflector topology and preserving the standard ORIGINATOR_ID and CLUSTER_LIST loop controls could be appropriate. Here, 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 202The datacom engineering team at an industrial safety organization during a simulated failover test reviews this independent fictional networking case: After an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed. Which corrective engineering action most directly addresses this problem? Apply appropriately scoped external prefix summarization at the originating ASBR Mark host-facing interfaces passive while still advertising their connected subnet through the intended OSPF process Validate stub-area configuration and ensure the ABR advertises the intended default route into the area Recalculate and set appropriate OSPF costs for the changed link while documenting routing intent ExplanationCorrect Answer D:Recalculate and set appropriate OSPF costs for the changed link while documenting routing intent. This is the specific action that addresses the fictional fault: After an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed. The governing technical reason is: OSPF shortest-path selection uses cumulative interface cost, not real-time measured bandwidth by itself. Verify by checking: SPF routing to the remote prefix favors the intended link and converges after the change. Incorrect Answers A:Applying appropriately scoped external prefix summarization at the originating ASBR is relevant when an ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. It does not resolve this case: 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. B: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 can respond to that condition, but it would not correct the reported fault: After an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed. Recalculate and set appropriate OSPF costs for the changed link while documenting routing intent. C:An engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. This is where validating stub-area configuration and ensure the ABR advertises the intended default route into the area would help. By contrast, after an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed. SPF routing to the remote prefix favors the intended link and converges after the change.
Question 203The datacom engineering team at a nationwide retail chain during a simulated failover test reviews this independent fictional networking case: A provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. Which corrective engineering action most directly addresses this problem? Assign route distinguishers suitable for creating unique originating VPN route identifiers Introduce a correctly designed iBGP route reflector cluster with appropriate clients and redundancy Set an appropriate maximum-prefix threshold and test the negotiated recovery behavior Apply provider-approved AS_PATH prepending or another suitable inbound policy while recognizing remote policy precedence ExplanationCorrect Answer C:Set an appropriate maximum-prefix threshold and test the negotiated recovery behavior. This is the specific action that addresses the fictional fault: A provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. The governing technical reason is: Prefix-limit controls can bound routing state growth when a neighbor violates expected route scale. Verify by checking: The limit activates predictably in staging and the router protects its route memory during an oversized update. Incorrect Answers A:Two EVPN leaf devices originate indistinguishable VPN NLRI because the service route identifiers were copied incorrectly. Assigning route distinguishers suitable for creating unique originating VPN route identifiers can respond to that condition, but it would not correct the reported fault: A provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. Prefix-limit controls can bound routing state growth when a neighbor violates expected route scale. B:A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. This is where introducing a correctly designed iBGP route reflector cluster with appropriate clients and redundancy would help. By contrast, a provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. Set an appropriate maximum-prefix threshold and test the negotiated recovery behavior. For nationwide retail chain during a simulated failover test, the acceptance test should show that the limit activates predictably in staging and the router protects its route memory during an oversized update. D:An enterprise wants to influence how some external networks enter its secondary ISP, but it changes local preference inside its own AS instead. This is where applying provider-approved AS_PATH prepending or another suitable inbound policy while recognizing remote policy precedence would help. By contrast, a provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. The limit activates predictably in staging and the router protects its route memory during an oversized update.
Question 204The datacom engineering team at an automotive parts manufacturer as part of an acceptance test reviews this independent fictional networking case: An edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS. The team applies this remedy: Verify and correct both configured local and peer autonomous system identities. Which observation would directly demonstrate that this specific issue is resolved? The upstream reports intended MED attributes and observed ingress tracks the agreed policy Internal BGP best routes select the contracted primary exit and fail over when unavailable External route views show the intended prepended announcement and measured ingress path changes when supported The BGP neighbor is Established and its accepted prefixes match the approved provider list ExplanationCorrect Answer D:The BGP neighbor is Established and its accepted prefixes match the approved provider list. This is a directly observable check for the proposed correction: Verify and correct both configured local and peer autonomous system identities. The particular failure being investigated is: An edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS. Incorrect Answers A:When two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned, a result such as this is useful: The upstream reports intended MED attributes and observed ingress tracks the agreed policy. For the reported fault, an edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS; eBGP session establishment validates the expected remote AS during OPEN negotiation. B:A multihomed autonomous system sends outbound traffic via a paid backup despite the intended primary exit. Internal BGP best routes select the contracted primary exit and fail over when unavailable. This observation does not prove the correction for the reported defect: An edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS. Verify and correct both configured local and peer autonomous system identities. C: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 edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS. An eBGP AS mismatch blocks external route exchange at the edge.
Question 205The datacom engineering team at a cross-border logistics provider after a monitored link change reviews this independent fictional networking case: A multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. Which corrective engineering action most directly addresses this problem? Apply appropriate multicast boundary and scope controls for the group range Repair IGMP query/reply processing and verify membership refresh timers Configure compatible SSM group ranges and source-aware membership signalling Verify the multicast RPF route and correct source reachability or appropriate multicast routing state ExplanationCorrect Answer D:Verify the multicast RPF route and correct source reachability or appropriate multicast routing state. This is the specific action that addresses the fictional fault: A multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. The governing technical reason is: Multicast RPF checks help prevent loops by accepting traffic from the interface on the expected source path. Verify by checking: RPF diagnostics name the arriving interface as valid and the downstream stream resumes. Incorrect Answers A:When a training-video multicast group begins leaking beyond its approved distribution region after a transport upgrade, applying appropriate multicast boundary and scope controls for the group range could be appropriate. Here, a multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. Multicast RPF checks help prevent loops by accepting traffic from the interface on the expected source path. B: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 can respond to that condition, but it would not correct the reported fault: A multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. Verify the multicast RPF route and correct source reachability or appropriate multicast routing state. C:When a receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state, configuring compatible SSM group ranges and source-aware membership signalling could be appropriate. Here, a multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. RPF diagnostics name the arriving interface as valid and the downstream stream resumes.
Question 206The datacom engineering team at a regional telecommunications carrier during a controlled network cutover 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? Apply appropriate traffic shaping at the controlled egress and verify contracted rate behavior Apply a narrowly matched import/export route policy during protocol redistribution Constrain ge/le mask-length ranges and test boundary prefix acceptance Align ingress marking and MQC traffic-classifier matching before adjusting queue parameters ExplanationCorrect Answer A: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 B:A border router injects internal transit and management prefixes into external BGP due to unrestricted redistribution. This is where applying a narrowly matched import/export route policy during protocol redistribution 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. C:A routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes. Constraining ge/le mask-length ranges and testing boundary prefix acceptance can respond to that condition, but it would not correct the reported fault: 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:A voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns. This is where aligning ingress marking and MQC traffic-classifier matching before adjusting queue parameters would help. By contrast, 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 207The 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. 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 Stale gateway MAC learning can prolong an otherwise successful VRRP switchover Unplanned Master placement may steer client traffic over a less reliable exit Unaggregated external advertisements can magnify flaps across the routing domain ExplanationCorrect Answer B:Stale gateway MAC learning can prolong an otherwise successful VRRP switchover. Leaving the exact fault unresolved means: 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. The intended response is: Verify the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover. 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, 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. C:Unplanned Master placement may steer client traffic over a less reliable exit. That risk belongs to a separate condition: A backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. 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; verify the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover. D:An ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. In that situation, unaggregated external advertisements can magnify flaps across the routing domain. Here instead, 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 208The datacom engineering team at a university research campus while tracing a degraded application flow reviews this independent fictional networking case: Policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. Which corrective engineering action most directly addresses this problem? Align ingress marking and MQC traffic-classifier matching before adjusting queue parameters Tag redistributed routes and deny re-entry of the marked route class at the opposite redistribution point Add health-aware policy-path handling or withdraw the policy on next-hop failure Apply appropriate traffic shaping at the controlled egress and verify contracted rate behavior ExplanationCorrect Answer C:Add health-aware policy-path handling or withdraw the policy on next-hop failure. This is the specific action that addresses the fictional fault: Policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. The governing technical reason is: PBR intentionally overrides ordinary routing and can therefore preserve a failed forwarding decision. Verify by checking: Policy test traffic fails over to the approved inspection path and maintains documented controls. Incorrect Answers A:When a voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns, aligning ingress marking and MQC traffic-classifier matching before adjusting queue parameters could be appropriate. Here, policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. PBR intentionally overrides ordinary routing and can therefore preserve a failed forwarding decision. B:When two redistribution points repeatedly re-inject learned routes between OSPF and another IGP and churn route entries, tagging redistributed routes and deny re-entry of the marked route class at the opposite redistribution point could be appropriate. Here, policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. Add health-aware policy-path handling or withdraw the policy on next-hop failure. D:When a WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective, applying appropriate traffic shaping at the controlled egress and verifying contracted rate behavior could be appropriate. Here, policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. Policy test traffic fails over to the approved inspection path and maintains documented controls.
Question 209The datacom engineering team at a cloud hosting provider after an incident review reviews this independent fictional networking case: IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. If this issue remains unresolved, what immediate availability or security risk follows most directly? Incorrect assumptions about IP reachability can mask unformed IS-IS adjacencies Repeated DIS transitions produce unnecessary topology recalculations Level mismatches can isolate the core despite both routers advertising IS-IS globally Mixed metric interpretation can produce route divergence and unstable path choices ExplanationCorrect Answer A:Incorrect assumptions about IP reachability can mask unformed IS-IS adjacencies. Leaving the exact fault unresolved means: IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. The intended response is: Verify physical MTU, CLNS frame transport and IS-IS padding support along the circuit. Incorrect Answers B:Repeated DIS transitions produce unnecessary topology recalculations. That consequence could follow when a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. Here, IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass; IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic. C:Level mismatches can isolate the core despite both routers advertising IS-IS globally. That risk belongs to a separate condition: A transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2. Here, IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass; verify physical MTU, CLNS frame transport and IS-IS padding support along the circuit. D:Mixed metric interpretation can produce route divergence and unstable path choices. That consequence could follow when a new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. Here, IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass; IS-IS hellos and LSP floods succeed and the remote LSDB converges.
Question 210The datacom engineering team at an air-cargo logistics operator during a network security audit reviews this independent fictional networking case: A high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling. The team applies this remedy: Tune BFD intervals and multiplier for supported device and transport capabilities. Which observation would directly demonstrate that this specific issue is resolved? Primary uplink failure transfers Master to the router with valid outbound reachability Matching gateway interfaces negotiate one Master and user devices reach the correct virtual address During a planned circuit interruption, BFD detects failure and routing reconverges within the operational target BFD remains stable under expected CPU load and still detects real test failures within requirement ExplanationCorrect Answer D:BFD remains stable under expected CPU load and still detects real test failures within requirement. This is a directly observable check for the proposed correction: Tune BFD intervals and multiplier for supported device and transport capabilities. The particular failure being investigated is: A high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling. Incorrect Answers A:Primary uplink failure transfers Master to the router with valid outbound reachability. This check belongs to a VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational. The actual defect is different: A high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling. Failure detection speed must be balanced against scheduling jitter and false-positive risk. B:Matching gateway interfaces negotiate one Master and user devices reach the correct virtual address. That result could validate a repair when two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error. Here, a high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling; tune BFD intervals and multiplier for supported device and transport capabilities. C:During a planned circuit interruption, BFD detects failure and routing reconverges within the operational target. That result could validate a repair when OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection. Here, a high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling; oversensitive BFD can cause route flapping on healthy circuits.