Question 610The datacom engineering team at a warehouse automation provider during a topology consistency review reviews this independent fictional networking case: A new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad. Which corrective engineering action most directly addresses this problem? Tag redistributed routes and deny re-entry of the marked route class at the opposite redistribution point Reorder and narrow the matching conditions so explicit permitted prefixes are evaluated before the general deny Define QoS trust boundaries and explicitly preserve authorized DSCP mappings across the interconnect Add health-aware policy-path handling or withdraw the policy on next-hop failure ExplanationCorrect Answer B:Reorder and narrow the matching conditions so explicit permitted prefixes are evaluated before the general deny. This is the specific action that addresses the fictional fault: A new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad. The governing technical reason is: Sequential route-policy matches can terminate evaluation and make later rules unreachable. Verify by checking: Matched-rule counters and received-route sets show only intended prefixes accepted. Incorrect Answers A: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 new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad. Sequential route-policy matches can terminate evaluation and make later rules unreachable. C:When delay-sensitive packets leave the campus with voice markings but are remarked to best-effort at a trusted border, defining QoS trust boundaries and explicitly preserve authorized DSCP mappings across the interconnect could be appropriate. Here, a new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad. Reorder and narrow the matching conditions so explicit permitted prefixes are evaluated before the general deny. D: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 new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad. Matched-rule counters and received-route sets show only intended prefixes accepted.
Question 611The datacom engineering team at a wholesale market association while tracing a degraded application flow reviews this independent fictional networking case: Two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. If this issue remains unresolved, what immediate availability or security risk follows most directly? Uncontrolled interarea route leakage increases route churn at constrained branch devices A fragmented OSPF backbone can split route exchange between otherwise healthy areas Incorrect static metrics cause chronic congestion while faster paths remain idle Missing NSSA translation hides branch routes from the rest of the autonomous system ExplanationCorrect Answer B:A fragmented OSPF backbone can split route exchange between otherwise healthy areas. Leaving the exact fault unresolved means: Two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. The intended response is: Reestablish a contiguous backbone design and use any supported temporary virtual link only with documented constraints. Incorrect Answers A:Branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. In that situation, uncontrolled interarea route leakage increases route churn at constrained branch devices. Here instead, two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. OSPF interarea routing depends on backbone connectivity through area 0. C:Incorrect static metrics cause chronic congestion while faster paths remain idle. That risk belongs to a separate condition: After an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed. Here, two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent; reestablish a contiguous backbone design and use any supported temporary virtual link only with documented constraints. D:Missing NSSA translation hides branch routes from the rest of the autonomous system. That consequence could follow when an NSSA branch redistributes a local static route that fails to appear as expected outside the NSSA. Here, two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent; ABRs display correct backbone reachability and previously missing interarea routes appear.
Question 612The datacom engineering team at a distribution warehouse group during a simulated failover test reviews this independent fictional networking case: Two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses. The team applies this remedy: Align the IS-IS area portion of the NET or revise the intended L1/L2 boundary. Which observation would directly demonstrate that this specific issue is resolved? Authentication failures cease and level-appropriate neighbor state returns Up L1 neighbor state establishes and the expected area routes appear Each participating router reports the intended metric and selects consistent next hops The peer adjacency is Up at the intended level and corresponding LSPs exchange ExplanationCorrect Answer B:L1 neighbor state establishes and the expected area routes appear. This is a directly observable check for the proposed correction: Align the IS-IS area portion of the NET or revise the intended L1/L2 boundary. The particular failure being investigated is: Two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses. Incorrect Answers A:When an IS-IS adjacency drops after only one of two core routers receives a new authentication key, a result such as this is useful: Authentication failures cease and level-appropriate neighbor state returns Up. For the reported fault, two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses; level-1 IS-IS neighbors must belong to a compatible area while Level-2 can connect areas. C:A new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. Each participating router reports the intended metric and selects consistent next hops. This observation does not prove the correction for the reported defect: Two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses. Align the IS-IS area portion of the NET or revise the intended L1/L2 boundary. D:The peer adjacency is Up at the intended level and corresponding LSPs exchange. That result could validate a repair when a transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2. Here, two core routers intended for Level-1 adjacency have incompatible area identifiers in their NET addresses; a hidden area mismatch splits the Level-1 topology and removes internal routes.
Question 613The datacom engineering team at a health laboratory network after a planned hardware refresh reviews this independent fictional networking case: An enterprise polls infrastructure over legacy unauthenticated SNMP and risks exposing operational data across shared networks. The team applies this remedy: Use supported SNMPv3 authentication/privacy and authorize specific management targets. Which observation would directly demonstrate that this specific issue is resolved? Discover/offer/request/ack exchange completes and clients receive correct scopes and gateways Both peers display Up state and a controlled liveness fault produces a consistent Down event Only subscribed access ports receive the feed and the multicast router port remains operational Approved collectors receive data with validated SNMPv3 security and unauthenticated polls are rejected ExplanationCorrect Answer D:Approved collectors receive data with validated SNMPv3 security and unauthenticated polls are rejected. This is a directly observable check for the proposed correction: Use supported SNMPv3 authentication/privacy and authorize specific management targets. The particular failure being investigated is: An enterprise polls infrastructure over legacy unauthenticated SNMP and risks exposing operational data across shared networks. Incorrect Answers A:Newly moved office endpoints cannot receive IPv4 leases because their DHCP server is across a routed interface without a relay. Discover/offer/request/ack exchange completes and clients receive correct scopes and gateways. This observation does not prove the correction for the reported defect: 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. B:Both peers display Up state and a controlled liveness fault produces a consistent Down event. That result could validate a repair when two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior. 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. C:A switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built. Only subscribed access ports receive the feed and the multicast router port remains operational. This observation does not prove the correction for the reported defect: An enterprise polls infrastructure over legacy unauthenticated SNMP and risks exposing operational data across shared networks. Insecure polling can leak topology and configuration metadata to untrusted observers.
Question 614The datacom engineering team at a research instrumentation firm while validating change-control evidence reviews this independent fictional networking case: A switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built. Which corrective engineering action most directly addresses this problem? Configure compatible SSM group ranges and source-aware membership signalling Apply appropriate multicast boundary and scope controls for the group range Enable and validate snooping with an operative querier and approved multicast router ports Investigate PIM-DM neighbor/prune behavior and remove unnecessary dense-mode flooding where appropriate ExplanationCorrect Answer C:Enable and validate snooping with an operative querier and approved multicast router ports. This is the specific action that addresses the fictional fault: A switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built. The governing technical reason is: IGMP snooping limits layer-2 forwarding to listeners when it learns accurate group-to-port membership. Verify by checking: Only subscribed access ports receive the feed and the multicast router port remains operational. Incorrect Answers A: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 switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built. IGMP snooping limits layer-2 forwarding to listeners when it learns accurate group-to-port membership. B:A training-video multicast group begins leaking beyond its approved distribution region after a transport upgrade. This is where applying appropriate multicast boundary and scope controls for the group range would help. By contrast, a switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built. Enable and validate snooping with an operative querier and approved multicast router ports. D:A dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent. Investigating PIM-DM neighbor/prune behavior and removing unnecessary dense-mode flooding where appropriate can respond to that condition, but it would not correct the reported fault: A switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built. Only subscribed access ports receive the feed and the multicast router port remains operational.
Question 615The 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. A proposed remedy is: Tune BFD intervals and multiplier for supported device and transport capabilities. Which technical principle most directly supports this remedy? Failure detection speed must be balanced against scheduling jitter and false-positive risk VRRP Master election is priority based subject to ownership and preemption rules BFD session state depends on interoperable mode and timing negotiation between peers VRRP continuity depends on end hosts and switches forwarding toward the current virtual gateway owner ExplanationCorrect Answer A:Failure detection speed must be balanced against scheduling jitter and false-positive risk. This directly explains why the corrective operation is appropriate: Tune BFD intervals and multiplier for supported device and transport capabilities. The observed acceptance evidence should be: BFD remains stable under expected CPU load and still detects real test failures within requirement. Incorrect Answers B:When 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. By contrast, 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. C:When two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior, BFD session state depends on interoperable mode and timing negotiation between peers. By contrast, 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. D:VRRP continuity depends on end hosts and switches forwarding toward the current virtual gateway owner. That principle 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. Here, a high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling; BFD remains stable under expected CPU load and still detects real test failures within requirement.
Question 616The datacom engineering team at a cross-border logistics provider after a monitored link change reviews this independent fictional networking case: Newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries. If this issue remains unresolved, what immediate availability or security risk follows most directly? Control-plane reachability can conceal production packet loss until the forwarding pipeline is verified Unresolved recursive next hops create a persistent black hole despite syntactically valid configuration A stray specific route can silently bypass the preferred security inspection path The wrong QoS mechanism causes avoidable burst packet loss and user-visible media glitches ExplanationCorrect Answer A:Control-plane reachability can conceal production packet loss until the forwarding pipeline is verified. Leaving the exact fault unresolved means: Newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries. The intended response is: Inspect interface and forwarding-plane readiness, then restore the failed forwarding-table synchronization before accepting traffic. Incorrect Answers B:Unresolved recursive next hops create a persistent black hole despite syntactically valid configuration. That consequence could follow when a static route is configured to a next-hop address that is absent from the local routing table and never becomes active. Here, newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries; a healthy control plane does not prove that hardware forwarding entries are programmed in the data plane. C:A branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. In that situation, a stray specific route can silently bypass the preferred security inspection path. Here instead, newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries. Inspect interface and forwarding-plane readiness, then restore the failed forwarding-table synchronization before accepting traffic. D:A WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. In that situation, the wrong QoS mechanism causes avoidable burst packet loss and user-visible media glitches. Here instead, newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries. Forwarding entries are present on the line card and a test flow traverses the intended interface.
Question 617The datacom engineering team at a distribution warehouse group during a simulated failover test reviews this independent fictional networking case: A migration team treats controller-based network provisioning and SD-WAN overlay path selection as identical capabilities and omits path-performance validation. Which corrective engineering action most directly addresses this problem? Separate campus access/distribution responsibilities from data-center service segments with explicitly routed and protected boundaries Apply appropriate traffic shaping at the controlled egress and verify contracted rate behavior Validate the community value, propagation policy, and provider-supported meaning before relying on it Define underlay provisioning and SD-WAN overlay policy separately and verify application steering under link degradation ExplanationCorrect Answer D:Define underlay provisioning and SD-WAN overlay policy separately and verify application steering under link degradation. This is the specific action that addresses the fictional fault: A migration team treats controller-based network provisioning and SD-WAN overlay path selection as identical capabilities and omits path-performance validation. The governing technical reason is: SDN-oriented control automation and SD-WAN application-aware path control can complement each other but solve different problems. Verify by checking: A staged migration test shows correct policy provisioning and overlay failover when the preferred WAN path degrades. Incorrect Answers A:Separating campus access/distribution responsibilities from data-center service segments with explicitly routed and protected boundaries is relevant when a proposed campus core directly bridges user VLANs into a data-center compute fabric without a clear routing and security boundary. It does not resolve this case: A migration team treats controller-based network provisioning and SD-WAN overlay path selection as identical capabilities and omits path-performance validation. SDN-oriented control automation and SD-WAN application-aware path control can complement each other but solve different problems. B:Applying appropriate traffic shaping at the controlled egress and verifying contracted rate behavior is relevant when a WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. It does not resolve this case: A migration team treats controller-based network provisioning and SD-WAN overlay path selection as identical capabilities and omits path-performance validation. Define underlay provisioning and SD-WAN overlay policy separately and verify application steering under link degradation. C:A border router tags specific prefixes but the provider does not apply the expected regional no-export treatment. This is where validating the community value, propagation policy, and provider-supported meaning before relying on it would help. By contrast, a migration team treats controller-based network provisioning and SD-WAN overlay path selection as identical capabilities and omits path-performance validation. A staged migration test shows correct policy provisioning and overlay failover when the preferred WAN path degrades.
Question 618The datacom engineering team at an industrial safety organization during a simulated failover 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. Which corrective engineering action most directly addresses this problem? Verify the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover Tune BFD intervals and multiplier for supported device and transport capabilities Check supported BFD modes and mutually acceptable timer negotiation before coupling routing failover Enable and validate snooping with an operative querier and approved multicast router ports ExplanationCorrect Answer A:Verify the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover. This is the specific action that addresses the fictional fault: 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 governing technical reason is: VRRP continuity depends on end hosts and switches forwarding toward the current virtual gateway owner. Verify by checking: Host neighbor tables resolve to the expected virtual MAC and sessions recover after failover. Incorrect Answers B: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 can respond to that condition, but it would not correct the reported fault: 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: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 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:Enabling and validating snooping with an operative querier and approved multicast router ports is relevant when a switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built. It does not resolve this 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. Host neighbor tables resolve to the expected virtual MAC and sessions recover after failover.
Question 619The datacom engineering team at a maritime terminal after a monitored link change reviews this independent fictional networking case: A branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. The team applies this remedy: Compare candidate prefixes and remove the unintended more-specific route before changing global route preferences. Which observation would directly demonstrate that this specific issue is resolved? The static route is active and its recursive next hop resolves to an operational interface The routing table and packet-path trace select the intended prefix and next hop Forwarding entries are present on the line card and a test flow traverses the intended interface Database description exchange completes and the OSPF neighbor reaches Full state ExplanationCorrect Answer B:The routing table and packet-path trace select the intended prefix and next hop. This is a directly observable check for the proposed correction: Compare candidate prefixes and remove the unintended more-specific route before changing global route preferences. The particular failure being investigated is: A branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. Incorrect Answers A:The static route is active and its recursive next hop resolves to an operational interface. This check belongs to a static route is configured to a next-hop address that is absent from the local routing table and never becomes active. The actual defect is different: A branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. Longest-prefix matching precedes route preference comparisons between routes of different mask lengths. For maritime terminal after a monitored link change, the acceptance test should show that the routing table and packet-path trace select the intended prefix and next hop. C:When newly installed routers accept control sessions but transit packets fail because an upstream line card has not finished installing forwarding entries, a result such as this is useful: Forwarding entries are present on the line card and a test flow traverses the intended interface. For the reported fault, a branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router; compare candidate prefixes and remove the unintended more-specific route before changing global route preferences. For maritime terminal after a monitored link change, the acceptance test should show that the routing table and packet-path trace select the intended prefix and next hop. D:When OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change, a result such as this is useful: Database description exchange completes and the OSPF neighbor reaches Full state. For the reported fault, a branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router; a stray specific route can silently bypass the preferred security inspection path.
Question 620The datacom engineering team at a regional telecommunications carrier during a controlled network cutover reviews this independent fictional networking case: Clients on a new IPv6 VLAN fail to obtain global addresses because router advertisements lack the intended autonomous prefix information. A proposed remedy is: Correct router advertisement prefix and flags for the chosen IPv6 addressing design. Which technical principle most directly supports this remedy? IPv6 link-local addresses are interface scoped and may require egress context for next-hop resolution IPv6 DAD uses neighbor solicitation to detect duplicate addresses before regular use SLAAC relies on received router advertisement prefix information and associated address configuration flags An OSPF neighbor pair must agree on the area identity for the common link ExplanationCorrect Answer C:SLAAC relies on received router advertisement prefix information and associated address configuration flags. This directly explains why the corrective operation is appropriate: Correct router advertisement prefix and flags for the chosen IPv6 addressing design. The observed acceptance evidence should be: Clients form valid unique global addresses and default routes from the expected RA source. Incorrect Answers A:IPv6 link-local addresses are interface scoped and may require egress context for next-hop resolution. That principle is relevant when an IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly. Here, clients on a new IPv6 VLAN fail to obtain global addresses because router advertisements lack the intended autonomous prefix information; SLAAC relies on received router advertisement prefix information and associated address configuration flags. B:When two replacement servers are configured with the same IPv6 address and one fails to bring the address online, IPv6 DAD uses neighbor solicitation to detect duplicate addresses before regular use. By contrast, clients on a new IPv6 VLAN fail to obtain global addresses because router advertisements lack the intended autonomous prefix information; correct router advertisement prefix and flags for the chosen IPv6 addressing design. D:When two routers on the same Ethernet segment remain stuck without OSPF adjacency because one interface belongs to area 0 and the other to area 10, an OSPF neighbor pair must agree on the area identity for the common link. By contrast, clients on a new IPv6 VLAN fail to obtain global addresses because router advertisements lack the intended autonomous prefix information; clients form valid unique global addresses and default routes from the expected RA source.