Question 650The datacom engineering team at a local rail transit network while validating change-control evidence reviews this independent fictional networking case: An OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. Which corrective engineering action most directly addresses this problem? Reestablish a contiguous backbone design and use any supported temporary virtual link only with documented constraints Coordinate the configured authentication mode and active key material at both ends of the link Set OSPF interface priorities to favor a stable distribution router and perform a planned election transition Restore accurate failure detection and re-originate the affected OSPF topology information ExplanationCorrect Answer B:Coordinate the configured authentication mode and active key material at both ends of the link. This is the specific action that addresses the fictional fault: An OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. The governing technical reason is: OSPF routing exchanges must pass consistent authentication checks before neighbor state can advance. Verify by checking: Authentication error counters stop increasing and a new Full adjacency is established. Incorrect Answers A:Reestablishing a contiguous backbone design and using any supported temporary virtual link only with documented constraints is relevant when two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. It does not resolve this case: An OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. OSPF routing exchanges must pass consistent authentication checks before neighbor state can advance. C:When a shared broadcast VLAN has an unsuitable router elected as Designated Router, causing unnecessary control-plane dependence on an access-edge node, setting OSPF interface priorities to favor a stable distribution router and performing a planned election transition could be appropriate. Here, an OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. Coordinate the configured authentication mode and active key material at both ends of the link. D:One router continues advertising a failed transit link because the local interface reports Up while an intermediate transport component is down. This is where restoring accurate failure detection and re-originate the affected OSPF topology information would help. By contrast, an OSPF adjacency stops forming after a scheduled authentication-key rotation on one end only. Authentication error counters stop increasing and a new Full adjacency is established.
Question 651The datacom engineering team at an automotive parts manufacturer as part of an acceptance 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? Classifier counters rise for real voice flows and the intended behavior is applied Burst loss decreases while sustained throughput remains within the agreed service rate Policy test traffic fails over to the approved inspection path and maintains documented controls Route advertisements stop oscillating and correct original route sources remain stable ExplanationCorrect Answer A: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 B:When a WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective, a result such as this is useful: Burst loss decreases while sustained throughput remains within the agreed service rate. For the reported fault, 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. C: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. 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:Two redistribution points repeatedly re-inject learned routes between OSPF and another IGP and churn route entries. Route advertisements stop oscillating and correct original route sources remain stable. 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. Misclassified real-time traffic may be dropped despite an apparently configured priority queue.
Question 652The datacom engineering team at an air-cargo logistics operator during a network security audit reviews this independent fictional networking case: An IS-IS adjacency drops after only one of two core routers receives a new authentication key. A proposed remedy is: Coordinate IS-IS authentication and key rollover across the peer link. Which technical principle most directly supports this remedy? IS-IS link-state consistency depends on reliable LSP version synchronization within each level IS-IS protocol authentication must match across neighbor exchanges to maintain trusted adjacencies Level-1 IS-IS neighbors must belong to a compatible area while Level-2 can connect areas The IS-IS overload bit discourages transit use of an incompletely initialized router ExplanationCorrect Answer B:IS-IS protocol authentication must match across neighbor exchanges to maintain trusted adjacencies. This directly explains why the corrective operation is appropriate: Coordinate IS-IS authentication and key rollover across the peer link. The observed acceptance evidence should be: Authentication failures cease and level-appropriate neighbor state returns Up. Incorrect Answers A:Core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. IS-IS link-state consistency depends on reliable LSP version synchronization within each level. The current condition differs: An IS-IS adjacency drops after only one of two core routers receives a new authentication key. IS-IS protocol authentication must match across neighbor exchanges to maintain trusted adjacencies. C:When 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. By contrast, an IS-IS adjacency drops after only one of two core routers receives a new authentication key; coordinate IS-IS authentication and key rollover across the peer link. D:The IS-IS overload bit discourages transit use of an incompletely initialized router. That principle is relevant when a router recovering from reboot begins attracting transit traffic before its route state is ready. Here, an IS-IS adjacency drops after only one of two core routers receives a new authentication key; authentication failures cease and level-appropriate neighbor state returns Up.
Question 653The datacom engineering team at a call center outsourcer after a planned hardware refresh reviews this independent fictional networking case: A security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. A proposed remedy is: Place the filter on the correct ingress or egress direction based on the observed packet path. Which technical principle most directly supports this remedy? Sequential route-policy matches can terminate evaluation and make later rules unreachable Policing enforces a rate by remarking or dropping excess traffic, whereas shaping buffers excess bursts for later transmission Route tagging and matching can prevent feedback when multiple dynamic-routing redistribution points exist ACL matching is evaluated at the attachment point and direction, not according to a rule's descriptive name ExplanationCorrect Answer D:ACL matching is evaluated at the attachment point and direction, not according to a rule's descriptive name. This directly explains why the corrective operation is appropriate: Place the filter on the correct ingress or egress direction based on the observed packet path. The observed acceptance evidence should be: Counters increment for prohibited guest probes and approved management flows remain permitted. Incorrect Answers A:Sequential route-policy matches can terminate evaluation and make later rules unreachable. That rule governs a different situation: A new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad. Here, a security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. ACL matching is evaluated at the attachment point and direction, not according to a rule's descriptive name. B: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. The current condition differs: A security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. Place the filter on the correct ingress or egress direction based on the observed packet path. C:Two redistribution points repeatedly re-inject learned routes between OSPF and another IGP and churn route entries. Route tagging and matching can prevent feedback when multiple dynamic-routing redistribution points exist. The current condition differs: A security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. Counters increment for prohibited guest probes and approved management flows remain permitted.
Question 654The datacom engineering team at an e-commerce fulfillment center while validating change-control evidence reviews this independent fictional networking case: A router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. Which corrective engineering action most directly addresses this problem? Review source/destination zone membership and adjust a narrowly scoped security-policy rule Diagnose session creation and asymmetric paths instead of opening unrestricted reverse policies Restrict protocol peers and apply appropriate routing authentication or control-plane filtering Restrict management access to approved administrative source networks and enforce strong authentication ExplanationCorrect Answer D:Restrict management access to approved administrative source networks and enforce strong authentication. This is the specific action that addresses the fictional fault: A router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. The governing technical reason is: Management-plane reachability should be separately controlled from transit forwarding permissions. Verify by checking: Guest-originated SSH probes are rejected while approved administrative access continues. Incorrect Answers A:A permitted application remains blocked when crossing the Huawei firewall because the zone pairing and rule match conditions are incorrect. Reviewing source/destination zone membership and adjust a narrowly scoped security-policy rule can respond to that condition, but it would not correct the reported fault: A router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. Management-plane reachability should be separately controlled from transit forwarding permissions. B:An administrator adds broad reverse-direction allow rules to fix response packets that should already match a healthy established session. Diagnosing session creation and asymmetric paths instead of opening unrestricted reverse policies can respond to that condition, but it would not correct the reported fault: A router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. Restrict management access to approved administrative source networks and enforce strong authentication. C:A provider-facing interface accepts unexpected routing-control connections from an unapproved adjacent host. This is where restricting protocol peers and applying appropriate routing authentication or control-plane filtering would help. By contrast, a router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. Guest-originated SSH probes are rejected while approved administrative access continues.
Question 655The datacom engineering team at a payment-processing provider after a monitored link change reviews this independent fictional networking case: Delay-sensitive packets leave the campus with voice markings but are remarked to best-effort at a trusted border. The team applies this remedy: Define QoS trust boundaries and explicitly preserve authorized DSCP mappings across the interconnect. Which observation would directly demonstrate that this specific issue is resolved? Policy test traffic fails over to the approved inspection path and maintains documented controls Capture on both sides confirms expected DSCP values and queue counters reflect the correct class The BGP advertisement list excludes internal infrastructure prefixes while approved service routes remain Burst loss decreases while sustained throughput remains within the agreed service rate ExplanationCorrect Answer B:Capture on both sides confirms expected DSCP values and queue counters reflect the correct class. This is a directly observable check for the proposed correction: Define QoS trust boundaries and explicitly preserve authorized DSCP mappings across the interconnect. The particular failure being investigated is: Delay-sensitive packets leave the campus with voice markings but are remarked to best-effort at a trusted border. Incorrect Answers A: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. This observation does not prove the correction for the reported defect: Delay-sensitive packets leave the campus with voice markings but are remarked to best-effort at a trusted border. QoS markings can be rewritten at domain boundaries; end-to-end class treatment requires consistent mapping. C:A border router injects internal transit and management prefixes into external BGP due to unrestricted redistribution. The BGP advertisement list excludes internal infrastructure prefixes while approved service routes remain. This observation does not prove the correction for the reported defect: Delay-sensitive packets leave the campus with voice markings but are remarked to best-effort at a trusted border. Define QoS trust boundaries and explicitly preserve authorized DSCP mappings across the interconnect. D:When a WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective, a result such as this is useful: Burst loss decreases while sustained throughput remains within the agreed service rate. For the reported fault, delay-sensitive packets leave the campus with voice markings but are remarked to best-effort at a trusted border; unnoticed remarking causes traffic to lose its intended service priority across domains.
Question 656The 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. Which corrective engineering action most directly addresses this problem? Correct matching export and import route-target policy for the tenant instance Review the upstream's MED handling and advertise the intended metric on comparable links Verify and correct both configured local and peer autonomous system identities Validate the community value, propagation policy, and provider-supported meaning before relying on it ExplanationCorrect Answer C:Verify and correct both configured local and peer autonomous system identities. This is the specific action that addresses the fictional fault: An edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS. The governing technical reason is: eBGP session establishment validates the expected remote AS during OPEN negotiation. Verify by checking: The BGP neighbor is Established and its accepted prefixes match the approved provider list. Incorrect Answers A:Tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. This is where correcting matching export and import route-target policy for the tenant instance would help. By contrast, 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:Reviewing the upstream's MED handling and advertise the intended metric on comparable links is relevant when two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned. It does not resolve this case: 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. D:Validating the community value, propagation policy, and provider-supported meaning before relying on it is relevant when a border router tags specific prefixes but the provider does not apply the expected regional no-export treatment. It does not resolve this case: An edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS. The BGP neighbor is Established and its accepted prefixes match the approved provider list.
Question 657The datacom engineering team at a call center outsourcer after a planned hardware refresh reviews this independent fictional networking case: One SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space. If this issue remains unresolved, what immediate availability or security risk follows most directly? Uncorrected RF contention can undermine a high-density WLAN despite healthy AP links Slow roaming can make warehouse voice and location services unusable Unexpected address changes can reset voice and real-time application sessions Poor VLAN-pool design can exhaust one DHCP subnet and block new wireless clients ExplanationCorrect Answer D:Poor VLAN-pool design can exhaust one DHCP subnet and block new wireless clients. Leaving the exact fault unresolved means: One SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space. The intended response is: Review the WLAN VLAN pool mapping and rebalance supported client distribution with consistent DHCP scopes. Incorrect Answers A:When a large lecture hall experiences low Wi-Fi throughput even with strong signal because neighboring AP radios overlap excessively on busy channels, uncorrected RF contention can undermine a high-density WLAN despite healthy AP links. The present failure is different: One SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space. A VLAN pool can distribute WLAN clients across logical broadcast domains when pool and DHCP design are coherent. B:When voice handsets suffer several seconds of audio interruption after moving between APs because full authentication runs on every transition, slow roaming can make warehouse voice and location services unusable. The present failure is different: One SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space. Review the WLAN VLAN pool mapping and rebalance supported client distribution with consistent DHCP scopes. C:Unexpected address changes can reset voice and real-time application sessions. That consequence could follow when a client changes IP address during normal intra-campus roaming because neighboring APs anchor it to incompatible service VLANs. Here, one SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space; client associations spread across permitted VLANs and each receives an address from its own correct scope.
Question 658The datacom engineering team at a regional newspaper publisher after an incident review reviews this independent fictional networking case: A security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. 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 Place the filter on the correct ingress or egress direction based on the observed packet path Constrain ge/le mask-length ranges and test boundary prefix acceptance ExplanationCorrect Answer C:Place the filter on the correct ingress or egress direction based on the observed packet path. This is the specific action that addresses the fictional fault: A security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. The governing technical reason is: ACL matching is evaluated at the attachment point and direction, not according to a rule's descriptive name. Verify by checking: Counters increment for prohibited guest probes and approved management flows remain permitted. Incorrect Answers A: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 can respond to that condition, but it would not correct the reported fault: A security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. ACL matching is evaluated at the attachment point and direction, not according to a rule's descriptive name. B:A new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad. This is where reordering and narrow the matching conditions so explicit permitted prefixes are evaluated before the general deny would help. By contrast, a security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. Place the filter on the correct ingress or egress direction based on the observed packet path. D:A routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes. This is where constraining ge/le mask-length ranges and testing boundary prefix acceptance would help. By contrast, a security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. Counters increment for prohibited guest probes and approved management flows remain permitted.
Question 659The datacom engineering team at a regional newspaper publisher after an incident review reviews this independent fictional networking case: One SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space. A proposed remedy is: Review the WLAN VLAN pool mapping and rebalance supported client distribution with consistent DHCP scopes. Which technical principle most directly supports this remedy? Central WLAN control architectures require planned control-plane redundancy and AP recovery behavior A VLAN pool can distribute WLAN clients across logical broadcast domains when pool and DHCP design are coherent A roaming design should reduce reconnection overhead without bypassing authorized identity checks WLAN access enforcement must combine authenticated identity with the corresponding least-privilege network role ExplanationCorrect Answer B:A VLAN pool can distribute WLAN clients across logical broadcast domains when pool and DHCP design are coherent. This directly explains why the corrective operation is appropriate: Review the WLAN VLAN pool mapping and rebalance supported client distribution with consistent DHCP scopes. The observed acceptance evidence should be: Client associations spread across permitted VLANs and each receives an address from its own correct scope. Incorrect Answers A:A wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller. Central WLAN control architectures require planned control-plane redundancy and AP recovery behavior. The current condition differs: One SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space. A VLAN pool can distribute WLAN clients across logical broadcast domains when pool and DHCP design are coherent. C:A roaming design should reduce reconnection overhead without bypassing authorized identity checks. That principle is relevant when voice handsets suffer several seconds of audio interruption after moving between APs because full authentication runs on every transition. Here, one SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space; review the WLAN VLAN pool mapping and rebalance supported client distribution with consistent DHCP scopes. D:When guest devices receive an internal employee VLAN after 802.1X authorization results are mapped incorrectly by WLAN policy, WLAN access enforcement must combine authenticated identity with the corresponding least-privilege network role. By contrast, one SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space; client associations spread across permitted VLANs and each receives an address from its own correct scope.
Question 660The datacom engineering team at a municipal transport operator during a simulated failover 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? Enable a proper querier in the receiver VLAN and validate IGMP state maintenance Investigate PIM-DM neighbor/prune behavior and remove unnecessary dense-mode flooding where appropriate Validate PIM-SM source-specific shortest-path switching and the unicast route toward the source Configure a consistent appropriate rendezvous point mapping and inspect source registration paths ExplanationCorrect Answer B: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:Enabling a proper querier in the receiver VLAN and validating IGMP state maintenance is relevant when a VLAN with multicast hosts has no functioning IGMP querier after its original gateway moves away. It does not resolve this case: 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. C:Validating PIM-SM source-specific shortest-path switching and the unicast route toward the source is relevant when a distant receiver continues using a long shared tree after a short direct source path is available and capacity is strained. 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. D: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. For municipal transport operator during a simulated failover test, the acceptance test should show that the non-listener branch stops receiving the data after valid prune processing.