Question 60The datacom engineering team at a consumer electronics manufacturer as part of an acceptance test reviews this independent fictional networking case: A campus authentication server becomes unreachable and network admins cannot access devices during an outage. A proposed remedy is: Test and configure a properly controlled emergency local access method consistent with AAA policy. Which technical principle most directly supports this remedy? Centralized AAA improves accountability, but managed fallback must preserve both resilience and least privilege NAT changes packet addressing, but traffic still requires a correct routed egress and return path Layer-2 address validation can prevent untrusted hosts from impersonating a local gateway VRFs provide separate routing tables, and cross-VRF reachability must be deliberately controlled ExplanationCorrect Answer A:Centralized AAA improves accountability, but managed fallback must preserve both resilience and least privilege. This directly explains why the corrective operation is appropriate: Test and configure a properly controlled emergency local access method consistent with AAA policy. The observed acceptance evidence should be: A controlled AAA outage allows an approved emergency operator and audit records document the session. Incorrect Answers B:NAT changes packet addressing, but traffic still requires a correct routed egress and return path. That rule governs a different situation: A firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. Here, a campus authentication server becomes unreachable and network admins cannot access devices during an outage. Centralized AAA improves accountability, but managed fallback must preserve both resilience and least privilege. C:When an attacker on a user VLAN advertises the gateway's IPv4 address with a forged MAC and steals nearby sessions, layer-2 address validation can prevent untrusted hosts from impersonating a local gateway. By contrast, a campus authentication server becomes unreachable and network admins cannot access devices during an outage; test and configure a properly controlled emergency local access method consistent with AAA policy. D:When traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance, VRFs provide separate routing tables, and cross-VRF reachability must be deliberately controlled. By contrast, a campus authentication server becomes unreachable and network admins cannot access devices during an outage; a controlled AAA outage allows an approved emergency operator and audit records document the session.
Question 61The 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. If this issue remains unresolved, what immediate availability or security risk follows most directly? Mixed metric interpretation can produce route divergence and unstable path choices Split key deployment can sever a core routing domain even when the circuit is physically healthy Incorrect assumptions about IP reachability can mask unformed IS-IS adjacencies Repeated DIS transitions produce unnecessary topology recalculations ExplanationCorrect Answer B:Split key deployment can sever a core routing domain even when the circuit is physically healthy. Leaving the exact fault unresolved means: An IS-IS adjacency drops after only one of two core routers receives a new authentication key. The intended response is: Coordinate IS-IS authentication and key rollover across the peer link. Incorrect Answers A:Mixed metric interpretation can produce route divergence and unstable path choices. That risk belongs to a separate condition: A new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. Here, 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:Incorrect assumptions about IP reachability can mask unformed IS-IS adjacencies. That consequence could follow when IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. Here, 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:When a LAN segment elects an unstable edge router as Designated Intermediate System, producing avoidable pseudonode churn, repeated DIS transitions produce unnecessary topology recalculations. The present failure is different: 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 62The datacom engineering team at a nationwide retail chain during a simulated failover test reviews this independent fictional networking case: A provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. A proposed remedy is: Set an appropriate maximum-prefix threshold and test the negotiated recovery behavior. Which technical principle most directly supports this remedy? BGP route eligibility depends on resolvable next hops and a functioning forwarding path Prefix-limit controls can bound routing state growth when a neighbor violates expected route scale A base BGP TCP session does not imply that every MP-BGP address family is negotiated and active Route reflection replaces full-mesh iBGP peering while preserving loop-prevention attributes ExplanationCorrect Answer B:Prefix-limit controls can bound routing state growth when a neighbor violates expected route scale. This directly explains why the corrective operation is appropriate: Set an appropriate maximum-prefix threshold and test the negotiated recovery behavior. The observed acceptance evidence should be: The limit activates predictably in staging and the router protects its route memory during an oversized update. Incorrect Answers A:BGP route eligibility depends on resolvable next hops and a functioning forwarding path. That rule governs a different situation: A BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. Here, a provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. Prefix-limit controls can bound routing state growth when a neighbor violates expected route scale. C:When an EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes, a base BGP TCP session does not imply that every MP-BGP address family is negotiated and active. By contrast, a provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set; set an appropriate maximum-prefix threshold and test the negotiated recovery behavior. D:Route reflection replaces full-mesh iBGP peering while preserving loop-prevention attributes. That rule governs a different situation: A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Here, a provider mistakenly sends a full Internet table to an edge peer designed for a small managed route set. The limit activates predictably in staging and the router protects its route memory during an oversized update.
Question 63The datacom engineering team at a research instrumentation firm while validating change-control evidence reviews this independent fictional networking case: A border router injects internal transit and management prefixes into external BGP due to unrestricted redistribution. Which corrective engineering action most directly addresses this problem? Constrain ge/le mask-length ranges and test boundary prefix acceptance Align ingress marking and MQC traffic-classifier matching before adjusting queue parameters Apply a narrowly matched import/export route policy during protocol redistribution Add health-aware policy-path handling or withdraw the policy on next-hop failure ExplanationCorrect Answer C:Apply a narrowly matched import/export route policy during protocol redistribution. This is the specific action that addresses the fictional fault: A border router injects internal transit and management prefixes into external BGP due to unrestricted redistribution. The governing technical reason is: Redistribution can cross routing trust boundaries and must specify which routes are authorized to cross. Verify by checking: The BGP advertisement list excludes internal infrastructure prefixes while approved service routes remain. Incorrect Answers A:When a routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes, constraining ge/le mask-length ranges and testing boundary prefix acceptance could be appropriate. Here, a border router injects internal transit and management prefixes into external BGP due to unrestricted redistribution. Redistribution can cross routing trust boundaries and must specify which routes are authorized to cross. B:Aligning ingress marking and MQC traffic-classifier matching before adjusting queue parameters is relevant when a voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns. It does not resolve this case: A border router injects internal transit and management prefixes into external BGP due to unrestricted redistribution. Apply a narrowly matched import/export route policy during protocol redistribution. D:When policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path, adding health-aware policy-path handling or withdraw the policy on next-hop failure could be appropriate. Here, 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.
Question 64The datacom engineering team at a regional newspaper publisher after an incident review reviews this independent fictional networking case: A multihomed autonomous system sends outbound traffic via a paid backup despite the intended primary exit. A proposed remedy is: Apply a consistent BGP LOCAL_PREF policy to favor the primary exit for internal peers. Which technical principle most directly supports this remedy? Higher LOCAL_PREF is preferred within an autonomous system and is normally not passed to eBGP neighbors A base BGP TCP session does not imply that every MP-BGP address family is negotiated and active EVPN route targets control which VPN routes a receiving instance is permitted to import eBGP session establishment validates the expected remote AS during OPEN negotiation ExplanationCorrect Answer A:Higher LOCAL_PREF is preferred within an autonomous system and is normally not passed to eBGP neighbors. This directly explains why the corrective operation is appropriate: Apply a consistent BGP LOCAL_PREF policy to favor the primary exit for internal peers. The observed acceptance evidence should be: Internal BGP best routes select the contracted primary exit and fail over when unavailable. Incorrect Answers B:An EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. A base BGP TCP session does not imply that every MP-BGP address family is negotiated and active. The current condition differs: A multihomed autonomous system sends outbound traffic via a paid backup despite the intended primary exit. Higher LOCAL_PREF is preferred within an autonomous system and is normally not passed to eBGP neighbors. C:Tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. EVPN route targets control which VPN routes a receiving instance is permitted to import. The current condition differs: A multihomed autonomous system sends outbound traffic via a paid backup despite the intended primary exit. Apply a consistent BGP LOCAL_PREF policy to favor the primary exit for internal peers. D:eBGP session establishment validates the expected remote AS during OPEN negotiation. That principle is relevant when an edge router repeatedly resets its eBGP session because the configured peer AS number differs from the provider's actual AS. Here, a multihomed autonomous system sends outbound traffic via a paid backup despite the intended primary exit; internal BGP best routes select the contracted primary exit and fail over when unavailable.
Question 65The datacom engineering team at an engineering consultancy during a controlled network cutover 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. A proposed remedy is: Inspect interface and forwarding-plane readiness, then restore the failed forwarding-table synchronization before accepting traffic. Which technical principle most directly supports this remedy? Longest-prefix matching precedes route preference comparisons between routes of different mask lengths A static route depending on recursive resolution cannot forward when its next-hop recursion fails Stacking presents multiple switches as a logical system but failure domains still depend on physical member connectivity A healthy control plane does not prove that hardware forwarding entries are programmed in the data plane ExplanationCorrect Answer D:A healthy control plane does not prove that hardware forwarding entries are programmed in the data plane. This directly explains why the corrective operation is appropriate: Inspect interface and forwarding-plane readiness, then restore the failed forwarding-table synchronization before accepting traffic. The observed acceptance evidence should be: Forwarding entries are present on the line card and a test flow traverses the intended interface. Incorrect Answers A:Longest-prefix matching precedes route preference comparisons between routes of different mask lengths. That principle is relevant when a branch sends payroll traffic to a backup path although a more-specific prefix was advertised through the primary router. 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. B:A static route is configured to a next-hop address that is absent from the local routing table and never becomes active. A static route depending on recursive resolution cannot forward when its next-hop recursion fails. The current condition differs: 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. C:Stacking presents multiple switches as a logical system but failure domains still depend on physical member connectivity. That rule governs a different situation: A stack member fails and connected access ports remain inaccessible because redundancy and member-level uplink placement were not reviewed. Here, 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 66The datacom engineering team at a hospital imaging provider during a controlled network cutover 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. A proposed remedy is: Define QoS trust boundaries and explicitly preserve authorized DSCP mappings across the interconnect. Which technical principle most directly supports this remedy? Policing enforces a rate by remarking or dropping excess traffic, whereas shaping buffers excess bursts for later transmission A prefix-list entry's address and mask-length matching must both reflect the authorization boundary Queue behavior depends on packets being correctly classified by actual header fields at the enforcement point QoS markings can be rewritten at domain boundaries; end-to-end class treatment requires consistent mapping ExplanationCorrect Answer D:QoS markings can be rewritten at domain boundaries; end-to-end class treatment requires consistent mapping. This directly explains why the corrective operation is appropriate: Define QoS trust boundaries and explicitly preserve authorized DSCP mappings across the interconnect. The observed acceptance evidence should be: Capture on both sides confirms expected DSCP values and queue counters reflect the correct class. Incorrect Answers A: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: 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. B: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: 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. C:Queue behavior depends on packets being correctly classified by actual header fields at the enforcement point. That rule governs a different situation: A voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns. Here, delay-sensitive packets leave the campus with voice markings but are remarked to best-effort at a trusted border. Capture on both sides confirms expected DSCP values and queue counters reflect the correct class.
Question 67The 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. A proposed remedy is: Reorder and narrow the matching conditions so explicit permitted prefixes are evaluated before the general deny. Which technical principle most directly supports this remedy? PBR intentionally overrides ordinary routing and can therefore preserve a failed forwarding decision Route tagging and matching can prevent feedback when multiple dynamic-routing redistribution points exist Policing enforces a rate by remarking or dropping excess traffic, whereas shaping buffers excess bursts for later transmission Sequential route-policy matches can terminate evaluation and make later rules unreachable ExplanationCorrect Answer D:Sequential route-policy matches can terminate evaluation and make later rules unreachable. This directly explains why the corrective operation is appropriate: Reorder and narrow the matching conditions so explicit permitted prefixes are evaluated before the general deny. The observed acceptance evidence should be: Matched-rule counters and received-route sets show only intended prefixes accepted. Incorrect Answers A:PBR intentionally overrides ordinary routing and can therefore preserve a failed forwarding decision. That rule governs a different situation: Policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. Here, 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. B:When 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. By contrast, 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. C:Policing enforces a rate by remarking or dropping excess traffic, whereas shaping buffers excess bursts for later transmission. That principle is relevant when a WAN service sees bursts dropped after an engineer enables policing where buffering and smoothing was the actual service objective. Here, 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 68The datacom engineering team at a payment-processing provider after a monitored link change reviews this independent fictional networking case: An iBGP route reflected through overlapping clusters returns toward its originator unexpectedly. If this issue remains unresolved, what immediate availability or security risk follows most directly? Uncontrolled source interface selection causes intermittent neighbor resets after link changes An unrestricted export policy may leak internal infrastructure addresses beyond the organization A visible BGP prefix can still hide a black hole if forwarding recursion is stale Misconfigured reflection can create route loops and unstable reachability ExplanationCorrect Answer D:Misconfigured reflection can create route loops and unstable reachability. Leaving the exact fault unresolved means: An iBGP route reflected through overlapping clusters returns toward its originator unexpectedly. The intended response is: Audit reflector topology and preserve the standard ORIGINATOR_ID and CLUSTER_LIST loop controls. Incorrect Answers A:When two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses, uncontrolled source interface selection causes intermittent neighbor resets after link changes. The present failure is different: An iBGP route reflected through overlapping clusters returns toward its originator unexpectedly. Route reflection loop-prevention attributes prevent readvertising a route into a cycle. B:An unrestricted export policy may leak internal infrastructure addresses beyond the organization. That consequence could follow when an accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. Here, an iBGP route reflected through overlapping clusters returns toward its originator unexpectedly; audit reflector topology and preserve the standard ORIGINATOR_ID and CLUSTER_LIST loop controls. C:A BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. In that situation, a visible BGP prefix can still hide a black hole if forwarding recursion is stale. Here instead, an iBGP route reflected through overlapping clusters returns toward its originator unexpectedly. Captures and received-route diagnostics show the cyclic update rejected without route churn.
Question 69The datacom engineering team at a regional health network during a controlled network cutover reviews this independent fictional networking case: A transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2. A proposed remedy is: Set compatible IS-IS circuit levels consistent with the core design. Which technical principle most directly supports this remedy? IS-IS metric encoding capability must be consistent enough for all participating routers to calculate intended paths IS-IS adjacencies require at least one common enabled routing level IS-IS link-state consistency depends on reliable LSP version synchronization within each level The IS-IS overload bit discourages transit use of an incompletely initialized router ExplanationCorrect Answer B:IS-IS adjacencies require at least one common enabled routing level. This directly explains why the corrective operation is appropriate: Set compatible IS-IS circuit levels consistent with the core design. The observed acceptance evidence should be: The peer adjacency is Up at the intended level and corresponding LSPs exchange. Incorrect Answers A:IS-IS metric encoding capability must be consistent enough for all participating routers to calculate intended paths. That principle is relevant when a new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. Here, a transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2; IS-IS adjacencies require at least one common enabled routing level. C:IS-IS link-state consistency depends on reliable LSP version synchronization within each level. That principle is relevant when core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. Here, a transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2; set compatible IS-IS circuit levels consistent with the core design. D:A router recovering from reboot begins attracting transit traffic before its route state is ready. The IS-IS overload bit discourages transit use of an incompletely initialized router. The current condition differs: A transit adjacency fails because one device allows only Level-1 while its peer is configured only for Level-2. The peer adjacency is Up at the intended level and corresponding LSPs exchange.
Question 70The datacom engineering team at a satellite ground station operator after an incident review reviews this independent fictional networking case: Branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. If this issue remains unresolved, what immediate availability or security risk follows most directly? Missing NSSA translation hides branch routes from the rest of the autonomous system An unresolved area mismatch isolates prefixes even when IP reachability across the segment works Active routing hellos on user ports expand an unnecessary adjacency attack surface Uncontrolled interarea route leakage increases route churn at constrained branch devices ExplanationCorrect Answer D:Uncontrolled interarea route leakage increases route churn at constrained branch devices. Leaving the exact fault unresolved means: Branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. The intended response is: Align the totally stub area behavior at the ABR and verify the intended default-based forwarding. Incorrect Answers A: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, branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR; totally stubby configuration suppresses most interarea summaries while retaining the area default route. B: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 unresolved area mismatch isolates prefixes even when IP reachability across the segment works. The present failure is different: Branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. Align the totally stub area behavior at the ABR and verify the intended default-based forwarding. C:A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. In that situation, active routing hellos on user ports expand an unnecessary adjacency attack surface. Here instead, branch routers in a totally stubby OSPF area receive interarea routes unexpectedly after a change on one ABR. Branch route tables contain the intended default rather than the unexpected interarea prefixes.