Question 120The datacom engineering team at a research instrumentation firm while validating change-control evidence reviews this independent fictional networking case: A backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. Which corrective engineering action most directly addresses this problem? Verify the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover Set and document appropriate VRRP priorities and supported preemption behavior Track external-uplink health and reduce VRRP priority enough for the healthy backup to take over Enable supported BFD tracking for the OSPF adjacency and validate timer compatibility ExplanationCorrect Answer B:Set and document appropriate VRRP priorities and supported preemption behavior. This is the specific action that addresses the fictional fault: A backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. The governing technical reason is: VRRP Master election is priority based subject to ownership and preemption rules. Verify by checking: The planned primary device owns the virtual gateway after recovery and failover still works. Incorrect Answers A: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. Verifying the virtual gateway MAC behavior and gratuitous ARP handling during VRRP failover can respond to that condition, but it would not correct the reported fault: 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. C:When a VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational, tracking external-uplink health and reduce VRRP priority enough for the healthy backup to take over could be appropriate. Here, a backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. Set and document appropriate VRRP priorities and supported preemption behavior. D:When OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection, enabling supported BFD tracking for the OSPF adjacency and validating timer compatibility could be appropriate. Here, a backup gateway becomes VRRP Master after an unrelated restart despite the primary router being healthy. The planned primary device owns the virtual gateway after recovery and failover still works.
Question 121The datacom engineering team at a retail banking network as part of an acceptance test reviews this independent fictional networking case: A dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent. Which corrective engineering action most directly addresses this problem? Apply appropriate multicast boundary and scope controls for the group range Configure compatible SSM group ranges and source-aware membership signalling Configure a consistent appropriate rendezvous point mapping and inspect source registration paths Investigate PIM-DM neighbor/prune behavior and remove unnecessary dense-mode flooding where appropriate ExplanationCorrect Answer D:Investigate PIM-DM neighbor/prune behavior and remove unnecessary dense-mode flooding where appropriate. This is the specific action that addresses the fictional fault: A dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent. The governing technical reason is: PIM-DM initially floods and then prunes branches without receivers. Verify by checking: The non-listener branch stops receiving the data after valid prune processing. Incorrect Answers A: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 can respond to that condition, but it would not correct the reported fault: 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. B: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 dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent. Investigate PIM-DM neighbor/prune behavior and remove unnecessary dense-mode flooding where appropriate. C:When a multicast source in a sparse-mode domain sends traffic but remote listeners receive nothing because the routers have inconsistent RP mappings, configuring a consistent appropriate rendezvous point mapping and inspecting source registration paths could be appropriate. Here, a dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent. The non-listener branch stops receiving the data after valid prune processing.
Question 122The datacom engineering team at a university research campus while tracing a degraded application flow 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. If this issue remains unresolved, what immediate availability or security risk follows most directly? Incorrect static metrics cause chronic congestion while faster paths remain idle Unplanned DR placement increases disruption when a fragile access node fails A hidden timer mismatch leaves the intended routing adjacency unavailable after every restart Lack of controlled interarea aggregation increases flooding and update workload during access failures ExplanationCorrect Answer B:Unplanned DR placement increases disruption when a fragile access node fails. Leaving the exact fault unresolved means: A shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node. The intended response is: Set OSPF interface priorities to favor a stable distribution router and perform a planned election transition. Incorrect Answers A:After an uplink upgrade, OSPF still prefers a slower backup circuit because interface reference bandwidth and explicit cost settings were not reviewed. In that situation, incorrect static metrics cause chronic congestion while faster paths remain idle. Here instead, 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:When two directly connected OSPF routers see each other in packets but never establish a neighbor because their Hello and Dead timers differ, a hidden timer mismatch leaves the intended routing adjacency unavailable after every restart. The present failure is different: 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:Lack of controlled interarea aggregation increases flooding and update workload during access failures. That consequence could follow when several closely related access prefixes create unnecessary interarea LSA churn because no ABR aggregation is applied. Here, a shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node; the designated router role moves to the planned stable device and all segment peers remain Full.
Question 123The datacom engineering team at an engineering consultancy during a controlled network cutover 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. The team applies this remedy: Define underlay provisioning and SD-WAN overlay policy separately and verify application steering under link degradation. Which observation would directly demonstrate that this specific issue is resolved? An architectural test shows isolated broadcast domains and approved routed application flows across the boundary Branch route tables contain the intended default rather than the unexpected interarea prefixes Tunnel SA counters increase for the approved subnet and remote application traffic succeeds A staged migration test shows correct policy provisioning and overlay failover when the preferred WAN path degrades ExplanationCorrect Answer D:A staged migration test shows correct policy provisioning and overlay failover when the preferred WAN path degrades. This is a directly observable check for the proposed correction: Define underlay provisioning and SD-WAN overlay policy separately and verify application steering under link degradation. The particular failure being investigated is: A migration team treats controller-based network provisioning and SD-WAN overlay path selection as identical capabilities and omits path-performance validation. Incorrect Answers A:A proposed campus core directly bridges user VLANs into a data-center compute fabric without a clear routing and security boundary. An architectural test shows isolated broadcast domains and approved routed application flows across the boundary. This observation does not prove the correction for the reported defect: 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:Branch route tables contain the intended default rather than the unexpected interarea prefixes. That result could validate a repair when branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. Here, 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:Tunnel SA counters increase for the approved subnet and remote application traffic succeeds. That result could validate a repair when two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree. Here, a migration team treats controller-based network provisioning and SD-WAN overlay path selection as identical capabilities and omits path-performance validation; conflating control orchestration with data-path steering can leave critical applications on poor WAN links.
Question 124The datacom engineering team at a library district network after a planned hardware refresh reviews this independent fictional networking case: OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection. 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 An unverified BFD session provides no rapid failure protection to the routing design Stale gateway MAC learning can prolong an otherwise successful VRRP switchover Slow liveness detection can extend avoidable black-hole duration after link failure ExplanationCorrect Answer D:Slow liveness detection can extend avoidable black-hole duration after link failure. Leaving the exact fault unresolved means: OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection. The intended response is: Enable supported BFD tracking for the OSPF adjacency and validate timer compatibility. Incorrect Answers A:Incorrect group placement can create duplicate gateway ownership or unreachable hosts. That risk belongs to a separate condition: Two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error. Here, 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. B:When two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior, an unverified BFD session provides no rapid failure protection to the routing design. The present failure is different: OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection. Enable supported BFD tracking for the OSPF adjacency and validate timer compatibility. C: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, stale gateway MAC learning can prolong an otherwise successful VRRP switchover. The present failure is different: OSPF retains a dead WAN next hop for too long because default neighbor dead timers dominate failure detection. During a planned circuit interruption, BFD detects failure and routing reconverges within the operational target.
Question 125The 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. The team applies this remedy: Align ingress marking and MQC traffic-classifier matching before adjusting queue parameters. Which observation would directly demonstrate that this specific issue is resolved? Bidirectional trace confirms both directions traverse a consistent stateful inspection path Tests accept the approved /24 and reject longer unauthorized prefixes Classifier counters rise for real voice flows and the intended behavior is applied Counters increment for prohibited guest probes and approved management flows remain permitted ExplanationCorrect Answer C:Classifier counters rise for real voice flows and the intended behavior is applied. This is a directly observable check for the proposed correction: Align ingress marking and MQC traffic-classifier matching before adjusting queue parameters. The particular failure being investigated is: A voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns. Incorrect Answers A:Bidirectional trace confirms both directions traverse a consistent stateful inspection path. That result could validate a repair when a stateful firewall intermittently drops responses after equal-cost routing spreads the forward and return flows across unrelated inspection nodes. 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:A routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes. Tests accept the approved /24 and reject longer unauthorized prefixes. This observation does not prove the correction for the reported defect: 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:Counters increment for prohibited guest probes and approved management flows remain permitted. That result could validate a repair when a security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. Here, a voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns; misclassified real-time traffic may be dropped despite an apparently configured priority queue.
Question 126The datacom engineering team at a film production studio as part of an acceptance test reviews this independent fictional networking case: Traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. The team applies this remedy: Align VLAN-to-instance mappings and regional parameters across the MST region. Which observation would directly demonstrate that this specific issue is resolved? The intended distribution switch is root and port roles converge as planned A controlled member failure leaves dual-homed access services reachable and stack roles recover Region digest and per-VLAN instance port roles match at the neighbors A received BPDU triggers the configured protective response and no loop appears ExplanationCorrect Answer C:Region digest and per-VLAN instance port roles match at the neighbors. This is a directly observable check for the proposed correction: Align VLAN-to-instance mappings and regional parameters across the MST region. The particular failure being investigated is: Traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. Incorrect Answers A:When a low-capacity access switch becomes the spanning-tree root because its bridge priority was left lower than the distribution pair, a result such as this is useful: The intended distribution switch is root and port roles converge as planned. For the reported fault, traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances; MSTP topology behavior is per instance and consistent VLAN mapping is necessary for predictable forwarding. B:A stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed. A controlled member failure leaves dual-homed access services reachable and stack roles recover. This observation does not prove the correction for the reported defect: Traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. Align VLAN-to-instance mappings and regional parameters across the MST region. D:When a user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port, a result such as this is useful: A received BPDU triggers the configured protective response and no loop appears. For the reported fault, traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances; misaligned instance mappings can strand a subset of VLANs while others work.
Question 127The datacom engineering team at an insurance processing company while validating change-control evidence reviews this independent fictional networking case: A firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. A proposed remedy is: Validate NAT rule matching and the effective route lookup for the translated flow. Which technical principle most directly supports this remedy? IPsec security associations must cover compatible protected flows even when IKE negotiation is successful Management-plane reachability should be separately controlled from transit forwarding permissions NAT changes packet addressing, but traffic still requires a correct routed egress and return path Routing control channels should be limited to trusted neighbors independently of ordinary forwarding ExplanationCorrect Answer C:NAT changes packet addressing, but traffic still requires a correct routed egress and return path. This directly explains why the corrective operation is appropriate: Validate NAT rule matching and the effective route lookup for the translated flow. The observed acceptance evidence should be: Session/NAT records and bidirectional traces show the intended translated tuple and next hop. Incorrect Answers A:Two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree. IPsec security associations must cover compatible protected flows even when IKE negotiation is successful. The current condition differs: A firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. NAT changes packet addressing, but traffic still requires a correct routed egress and return path. B:Management-plane reachability should be separately controlled from transit forwarding permissions. That rule governs a different situation: A router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. Here, a firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. Validate NAT rule matching and the effective route lookup for the translated flow. D:When a provider-facing interface accepts unexpected routing-control connections from an unapproved adjacent host, routing control channels should be limited to trusted neighbors independently of ordinary forwarding. By contrast, 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.
Question 128The datacom engineering team at a public water utility during a topology consistency review reviews this independent fictional networking case: A low-capacity access switch becomes the spanning-tree root because its bridge priority was left lower than the distribution pair. Which corrective engineering action most directly addresses this problem? Apply supported BPDU protection at legitimate edge ports and investigate the unexpected bridge connection Align VLAN-to-instance mappings and regional parameters across the MST region Set deliberate RSTP root and backup-root bridge priorities on stable distribution switches Restore dual-active detection or an approved split-brain suppression mechanism and test isolation behavior ExplanationCorrect Answer C:Set deliberate RSTP root and backup-root bridge priorities on stable distribution switches. This is the specific action that addresses the fictional fault: A low-capacity access switch becomes the spanning-tree root because its bridge priority was left lower than the distribution pair. The governing technical reason is: The spanning-tree root selection follows bridge identifier priority rather than physical hierarchy labels. Verify by checking: The intended distribution switch is root and port roles converge as planned. Incorrect Answers A:A user connects a small unmanaged switch that begins forwarding bridge protocol frames into an edge-designated campus port. Applying supported BPDU protection at legitimate edge ports and investigate the unexpected bridge connection can respond to that condition, but it would not correct the reported fault: A low-capacity access switch becomes the spanning-tree root because its bridge priority was left lower than the distribution pair. The spanning-tree root selection follows bridge identifier priority rather than physical hierarchy labels. B:Traffic in one VLAN follows an unexpected blocked trunk because adjacent switches assign that VLAN to different MST instances. Aligning VLAN-to-instance mappings and regional parameters across the MST region can respond to that condition, but it would not correct the reported fault: A low-capacity access switch becomes the spanning-tree root because its bridge priority was left lower than the distribution pair. Set deliberate RSTP root and backup-root bridge priorities on stable distribution switches. D:A campus switch cluster loses its inter-chassis heartbeat and both nodes attempt to remain active on shared services. Restoring dual-active detection or an approved split-brain suppression mechanism and testing isolation behavior can respond to that condition, but it would not correct the reported fault: A low-capacity access switch becomes the spanning-tree root because its bridge priority was left lower than the distribution pair. The intended distribution switch is root and port roles converge as planned.
Question 129The datacom engineering team at a government service campus after a monitored link change 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. The team applies this remedy: Correct router advertisement prefix and flags for the chosen IPv6 addressing design. Which observation would directly demonstrate that this specific issue is resolved? The conflicting address is removed and DAD completes without duplicate notifications The route installs with the expected interface and reachability probes succeed Clients form valid unique global addresses and default routes from the expected RA source Route advertisements stop oscillating and correct original route sources remain stable ExplanationCorrect Answer C:Clients form valid unique global addresses and default routes from the expected RA source. This is a directly observable check for the proposed correction: Correct router advertisement prefix and flags for the chosen IPv6 addressing design. The particular failure being investigated is: Clients on a new IPv6 VLAN fail to obtain global addresses because router advertisements lack the intended autonomous prefix information. Incorrect Answers A: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, 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:The route installs with the expected interface and reachability probes succeed. That result could validate a repair 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; correct router advertisement prefix and flags for the chosen IPv6 addressing design. D:When two redistribution points repeatedly re-inject learned routes between OSPF and another IGP and churn route entries, a result such as this is useful: Route advertisements stop oscillating and correct original route sources remain stable. For the reported fault, clients on a new IPv6 VLAN fail to obtain global addresses because router advertisements lack the intended autonomous prefix information; broken RA configuration leaves clients with only link-local reachability.
Question 130The datacom engineering team at a nationwide retail chain during a simulated failover test reviews this independent fictional networking case: A proposed campus core directly bridges user VLANs into a data-center compute fabric without a clear routing and security boundary. A proposed remedy is: Separate campus access/distribution responsibilities from data-center service segments with explicitly routed and protected boundaries. Which technical principle most directly supports this remedy? SDN-oriented control automation and SD-WAN application-aware path control can complement each other but solve different problems Enterprise campus hierarchy and data-center fabrics serve different failure and security domains that require controlled interconnection A prefix-list entry's address and mask-length matching must both reflect the authorization boundary Aggregating interarea advertisements can reduce control-plane state but must not capture unreachable space ExplanationCorrect Answer B:Enterprise campus hierarchy and data-center fabrics serve different failure and security domains that require controlled interconnection. This directly explains why the corrective operation is appropriate: Separate campus access/distribution responsibilities from data-center service segments with explicitly routed and protected boundaries. The observed acceptance evidence should be: An architectural test shows isolated broadcast domains and approved routed application flows across the boundary. Incorrect Answers A:SDN-oriented control automation and SD-WAN application-aware path control can complement each other but solve different problems. That principle is relevant when a migration team treats controller-based network provisioning and SD-WAN overlay path selection as identical capabilities and omits path-performance validation. Here, a proposed campus core directly bridges user VLANs into a data-center compute fabric without a clear routing and security boundary; enterprise campus hierarchy and data-center fabrics serve different failure and security domains that require controlled interconnection. C:A routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes. A prefix-list entry's address and mask-length matching must both reflect the authorization boundary. The current condition differs: A proposed campus core directly bridges user VLANs into a data-center compute fabric without a clear routing and security boundary. Separate campus access/distribution responsibilities from data-center service segments with explicitly routed and protected boundaries. D:Aggregating interarea advertisements can reduce control-plane state but must not capture unreachable space. That principle is relevant when several closely related access prefixes create unnecessary interarea LSA churn because no ABR aggregation is applied. Here, a proposed campus core directly bridges user VLANs into a data-center compute fabric without a clear routing and security boundary; an architectural test shows isolated broadcast domains and approved routed application flows across the boundary.