Question 750The datacom engineering team at an industrial safety organization during a simulated failover test reviews this independent fictional networking case: A voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns. A proposed remedy is: Align ingress marking and MQC traffic-classifier matching before adjusting queue parameters. Which technical principle most directly supports this remedy? A prefix-list entry's address and mask-length matching must both reflect the authorization boundary Sequential route-policy matches can terminate evaluation and make later rules unreachable Queue behavior depends on packets being correctly classified by actual header fields at the enforcement point Redistribution can cross routing trust boundaries and must specify which routes are authorized to cross ExplanationCorrect Answer C:Queue behavior depends on packets being correctly classified by actual header fields at the enforcement point. This directly explains why the corrective operation is appropriate: Align ingress marking and MQC traffic-classifier matching before adjusting queue parameters. The observed acceptance evidence should be: Classifier counters rise for real voice flows and the intended behavior is applied. Incorrect Answers A:A prefix-list entry's address and mask-length matching must both reflect the authorization boundary. That rule governs a different situation: A routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes. Here, a voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns. Queue behavior depends on packets being correctly classified by actual header fields at the enforcement point. B:Sequential route-policy matches can terminate evaluation and make later rules unreachable. That principle is relevant when a new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad. Here, a voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns; align ingress marking and MQC traffic-classifier matching before adjusting queue parameters. D:Redistribution can cross routing trust boundaries and must specify which routes are authorized to cross. That rule governs a different situation: A border router injects internal transit and management prefixes into external BGP due to unrestricted redistribution. Here, a voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns. Classifier counters rise for real voice flows and the intended behavior is applied.
Question 751The datacom engineering team at an automotive parts manufacturer as part of an acceptance test reviews this independent fictional networking case: A distant receiver continues using a long shared tree after a short direct source path is available and capacity is strained. Which corrective engineering action most directly addresses this problem? Validate PIM-SM source-specific shortest-path switching and the unicast route toward the source Investigate PIM-DM neighbor/prune behavior and remove unnecessary dense-mode flooding where appropriate Configure compatible SSM group ranges and source-aware membership signalling Repair IGMP query/reply processing and verify membership refresh timers ExplanationCorrect Answer A:Validate PIM-SM source-specific shortest-path switching and the unicast route toward the source. This is the specific action that addresses the fictional fault: A distant receiver continues using a long shared tree after a short direct source path is available and capacity is strained. The governing technical reason is: PIM-SM can transition from a shared tree to a source-specific tree when route and policy permit. Verify by checking: The multicast route table reflects an intended source-specific incoming interface and latency improves. Incorrect Answers B: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 distant receiver continues using a long shared tree after a short direct source path is available and capacity is strained. PIM-SM can transition from a shared tree to a source-specific tree when route and policy permit. C:Configuring compatible SSM group ranges and source-aware membership signalling is relevant when a receiver requests a specific-source multicast stream but the network treats its membership as ordinary any-source group state. It does not resolve this case: A distant receiver continues using a long shared tree after a short direct source path is available and capacity is strained. Validate PIM-SM source-specific shortest-path switching and the unicast route toward the source. D: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 distant receiver continues using a long shared tree after a short direct source path is available and capacity is strained. The multicast route table reflects an intended source-specific incoming interface and latency improves.
Question 752The datacom engineering team at a film production studio as part of an acceptance test reviews this independent fictional networking case: An accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. A proposed remedy is: Apply explicit prefix-length-aware export policy limited to authorized aggregate space. Which technical principle most directly supports this remedy? BGP neighbor identity must align with the configured source and destination transport addresses Prefix-limit controls can bound routing state growth when a neighbor violates expected route scale Route reflection replaces full-mesh iBGP peering while preserving loop-prevention attributes Prefix lists and route policies should enforce precise permitted address and mask ranges at external boundaries ExplanationCorrect Answer D:Prefix lists and route policies should enforce precise permitted address and mask ranges at external boundaries. This directly explains why the corrective operation is appropriate: Apply explicit prefix-length-aware export policy limited to authorized aggregate space. The observed acceptance evidence should be: Exported BGP routes contain only the authorized prefix and mask set. Incorrect Answers A:BGP neighbor identity must align with the configured source and destination transport addresses. That principle is relevant when two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses. Here, an accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter; prefix lists and route policies should enforce precise permitted address and mask ranges at external boundaries. B:Prefix-limit controls can bound routing state growth when a neighbor violates expected route scale. That principle is relevant when a provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. Here, an accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter; apply explicit prefix-length-aware export policy limited to authorized aggregate space. C:A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Route reflection replaces full-mesh iBGP peering while preserving loop-prevention attributes. The current condition differs: An accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. Exported BGP routes contain only the authorized prefix and mask set.
Question 753The datacom engineering team at a health laboratory network after a planned hardware refresh reviews this independent fictional networking case: An iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally. If this issue remains unresolved, what immediate availability or security risk follows most directly? Misconfigured reflection can create route loops and unstable reachability A visible BGP prefix can still hide a black hole if forwarding recursion is stale Incomplete understanding of attribute order leads to ineffective and potentially disruptive policy changes A valid-looking iBGP route may be unusable when the external next hop is unresolved ExplanationCorrect Answer D:A valid-looking iBGP route may be unusable when the external next hop is unresolved. Leaving the exact fault unresolved means: An iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally. The intended response is: Apply next-hop-self on the appropriate border speaker or otherwise make the next hop legitimately reachable. Incorrect Answers A:When an iBGP route reflected through overlapping clusters returns toward its originator unexpectedly, misconfigured reflection can create route loops and unstable reachability. The present failure is different: 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. B:A visible BGP prefix can still hide a black hole if forwarding recursion is stale. That consequence could follow when a BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. Here, an iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally; apply next-hop-self on the appropriate border speaker or otherwise make the next hop legitimately reachable. C:Incomplete understanding of attribute order leads to ineffective and potentially disruptive policy changes. That risk belongs to a separate condition: Operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. Here, an iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally; the iBGP route becomes eligible and its next hop resolves through the IGP.
Question 754The datacom engineering team at a research instrumentation firm while validating change-control evidence reviews this independent fictional networking case: A LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. 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 Stale link-state information can create asymmetric paths and packet loss Repeated DIS transitions produce unnecessary topology recalculations Split key deployment can sever a core routing domain even when the circuit is physically healthy ExplanationCorrect Answer C:Repeated DIS transitions produce unnecessary topology recalculations. Leaving the exact fault unresolved means: A LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. The intended response is: Tune IS-IS DIS priority on the shared LAN and validate neighbor continuity after a planned election. Incorrect Answers A:IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. In that situation, incorrect assumptions about IP reachability can mask unformed IS-IS adjacencies. Here instead, a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. On broadcast IS-IS circuits the DIS originates a pseudonode LSP and its election follows IS-IS priority rules. B:Stale link-state information can create asymmetric paths and packet loss. That consequence could follow when core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. Here, a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn; tune IS-IS DIS priority on the shared LAN and validate neighbor continuity after a planned election. D:When an IS-IS adjacency drops after only one of two core routers receives a new authentication key, split key deployment can sever a core routing domain even when the circuit is physically healthy. The present failure is different: A LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn. The intended stable router becomes DIS and the pseudonode LSP refreshes correctly.
Question 755The datacom engineering team at a retail banking network as part of an acceptance test reviews this independent fictional networking case: A shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. The team applies this remedy: Set OSPF interface priorities to favor a stable distribution router and perform a planned election transition. Which observation would directly demonstrate that this specific issue is resolved? ABRs display correct backbone reachability and previously missing interarea routes appear The designated router role moves to the planned stable device and all segment peers remain Full The redistributed prefix is present as Type-7 in the NSSA and appropriate external form beyond it Packet captures show no OSPF Hellos on the host VLAN while the prefix remains in OSPF routes ExplanationCorrect Answer B:The designated router role moves to the planned stable device and all segment peers remain Full. This is a directly observable check for the proposed correction: Set OSPF interface priorities to favor a stable distribution router and perform a planned election transition. The particular failure being investigated is: A shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. Incorrect Answers A: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. This observation does not prove the correction for the reported defect: 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. C:The redistributed prefix is present as Type-7 in the NSSA and appropriate external form beyond it. That result could validate a repair when an NSSA branch redistributes a local static route that fails to appear as expected outside the NSSA. Here, a shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node; set OSPF interface priorities to favor a stable distribution router and perform a planned election transition. D:A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. Packet captures show no OSPF Hellos on the host VLAN while the prefix remains in OSPF routes. This observation does not prove the correction for the reported defect: A shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. Unplanned DR placement increases disruption when a fragile access node fails.
Question 756The datacom engineering team at a wholesale market association while tracing a degraded application flow 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? Best-path diagnostics show the winning attribute and route selection matches intent Exported BGP routes contain only the authorized prefix and mask set All clients learn the intended prefixes and remain connected after a reflector failover Internal BGP best routes select the contracted primary exit and fail over when unavailable ExplanationCorrect Answer A: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 B:When an accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter, a result such as this is useful: Exported BGP routes contain only the authorized prefix and mask set. For the reported fault, 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:All clients learn the intended prefixes and remain connected after a reflector failover. That result could validate a repair when a growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Here, 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:Internal BGP best routes select the contracted primary exit and fail over when unavailable. That result could validate a repair when a multihomed autonomous system sends outbound traffic via a paid backup despite the intended primary exit. Here, 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.
Question 757The datacom engineering team at a pharmaceutical testing firm after a planned hardware refresh reviews this independent fictional networking case: A training-video multicast group begins leaking beyond its approved distribution region after a transport upgrade. A proposed remedy is: Apply appropriate multicast boundary and scope controls for the group range. Which technical principle most directly supports this remedy? IGMP membership state is maintained by router queries and host reports rather than permanent discovery Multicast distribution should follow explicitly defined group membership and boundary policy, not blanket flooding PIM-DM initially floods and then prunes branches without receivers Multicast RPF checks help prevent loops by accepting traffic from the interface on the expected source path ExplanationCorrect Answer B:Multicast distribution should follow explicitly defined group membership and boundary policy, not blanket flooding. This directly explains why the corrective operation is appropriate: Apply appropriate multicast boundary and scope controls for the group range. The observed acceptance evidence should be: Receivers inside scope join successfully while test receivers outside it receive no multicast payload. 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, IGMP membership state is maintained by router queries and host reports rather than permanent discovery. By contrast, 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. C:A dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent. PIM-DM initially floods and then prunes branches without receivers. The current condition differs: 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. D: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. The current condition differs: 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 758The datacom engineering team at a university hospital during a network security audit reviews this independent fictional networking case: A static backup path remains inactive while the primary next hop fails beyond a locally Up interface. If this issue remains unresolved, what immediate availability or security risk follows most directly? Failure beyond the local link can strand static-route traffic indefinitely Incorrect group placement can create duplicate gateway ownership or unreachable hosts Local gateway survival without uplink tracking can blackhole an entire user VLAN Oversensitive BFD can cause route flapping on healthy circuits ExplanationCorrect Answer A:Failure beyond the local link can strand static-route traffic indefinitely. Leaving the exact fault unresolved means: A static backup path remains inactive while the primary next hop fails beyond a locally Up interface. The intended response is: Use supported BFD or remote path tracking to withdraw the unusable static next hop. Incorrect Answers B:Two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error. In that situation, incorrect group placement can create duplicate gateway ownership or unreachable hosts. Here instead, 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. For university hospital during a network security audit, the acceptance test should show that an injected upstream failure withdraws the primary route and backup traffic succeeds. C:When a VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational, local gateway survival without uplink tracking can blackhole an entire user VLAN. The present failure is different: 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:Oversensitive BFD can cause route flapping on healthy circuits. That risk belongs to a separate condition: A high-load device repeatedly declares a healthy BFD session Down because its interval/multiplier settings are too aggressive for platform scheduling. Here, 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 759The datacom engineering team at a regional newspaper publisher after an incident review reviews this independent fictional networking case: An engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. A proposed remedy is: Validate stub-area configuration and ensure the ABR advertises the intended default route into the area. Which technical principle most directly supports this remedy? SPF can only remove unusable paths promptly after their topology state is correctly detected and flooded Aggregating interarea advertisements can reduce control-plane state but must not capture unreachable space Standard stub areas suppress Type-5 external LSAs and normally rely on an ABR-provided default for external reachability DR and BDR election on broadcast networks is influenced by configured interface priority and is not a direct lowest-cost path election ExplanationCorrect Answer C:Standard stub areas suppress Type-5 external LSAs and normally rely on an ABR-provided default for external reachability. This directly explains why the corrective operation is appropriate: Validate stub-area configuration and ensure the ABR advertises the intended default route into the area. The observed acceptance evidence should be: The ABR default route appears in the stub area and external destinations remain reachable. Incorrect Answers A:SPF can only remove unusable paths promptly after their topology state is correctly detected and flooded. That rule governs a different situation: One router continues advertising a failed transit link because the local interface reports Up while an intermediate transport component is down. Here, an engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. Standard stub areas suppress Type-5 external LSAs and normally rely on an ABR-provided default for external reachability. B: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 engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. Validate stub-area configuration and ensure the ABR advertises the intended default route into the area. 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 engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. The ABR default route appears in the stub area and external destinations remain reachable.
Question 760The datacom engineering team at a university hospital during a network security audit reviews this independent fictional networking case: 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. A proposed remedy is: Correct the interface area assignment after confirming the intended area boundary. Which technical principle most directly supports this remedy? An OSPF neighbor pair must agree on the area identity for the common link Aggregating interarea advertisements can reduce control-plane state but must not capture unreachable space OSPF shortest-path selection uses cumulative interface cost, not real-time measured bandwidth by itself OSPF adjacency establishment requires compatible hello parameters on the neighbor-facing interfaces ExplanationCorrect Answer A:An OSPF neighbor pair must agree on the area identity for the common link. This directly explains why the corrective operation is appropriate: Correct the interface area assignment after confirming the intended area boundary. The observed acceptance evidence should be: Neighbor state reaches Full and the link appears in both area LSDB views. Incorrect Answers B: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: 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. C:OSPF shortest-path selection uses cumulative interface cost, not real-time measured bandwidth by itself. That rule governs a different situation: After an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed. Here, 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. Correct the interface area assignment after confirming the intended area boundary. D:OSPF adjacency establishment requires compatible hello parameters on the neighbor-facing interfaces. That principle is relevant when two directly connected OSPF routers see each other in packets but never establish a neighbor because their Hello and Dead timers differ. Here, 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; neighbor state reaches Full and the link appears in both area LSDB views.