Question 270The 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. If this issue remains unresolved, what immediate availability or security risk follows most directly? A fragmented OSPF backbone can split route exchange between otherwise healthy areas Active routing hellos on user ports expand an unnecessary adjacency attack surface An unresolved area mismatch isolates prefixes even when IP reachability across the segment works Over-aggregation can turn an ABR into a black hole for withdrawn subnets ExplanationCorrect Answer C:An unresolved area mismatch isolates prefixes even when IP reachability across the segment works. Leaving the exact fault unresolved means: 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. The intended response is: Correct the interface area assignment after confirming the intended area boundary. Incorrect Answers A:Two nonbackbone OSPF areas were connected without a valid area 0 path and interarea routes are inconsistent. In that situation, a fragmented OSPF backbone can split route exchange between otherwise healthy areas. Here instead, 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. B:Active routing hellos on user ports expand an unnecessary adjacency attack surface. That risk belongs to a separate condition: A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. 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:When an area border router advertises a broad summary that includes subnets withdrawn after a site closure, over-aggregation can turn an ABR into a black hole for withdrawn subnets. The present failure is different: 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.
Question 271The datacom engineering team at an energy distribution business while tracing a degraded application flow reviews this independent fictional networking case: A campus authentication server becomes unreachable and network admins cannot access devices during an outage. If this issue remains unresolved, what immediate availability or security risk follows most directly? A missing fallback can prevent safe restoration during an identity infrastructure incident A superficially Up IKE session can conceal complete loss of protected service traffic Unrestricted routing peers can inject false reachability and disrupt a network segment Improper routing-instance assignment can expose one customer's traffic to another ExplanationCorrect Answer A:A missing fallback can prevent safe restoration during an identity infrastructure incident. Leaving the exact fault unresolved means: A campus authentication server becomes unreachable and network admins cannot access devices during an outage. The intended response is: Test and configure a properly controlled emergency local access method consistent with AAA policy. Incorrect Answers B:A superficially Up IKE session can conceal complete loss of protected service traffic. That risk belongs to a separate condition: Two VPN gateways establish IKE but fail to pass the intended private subnet because their phase-two traffic selectors do not agree. 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:Unrestricted routing peers can inject false reachability and disrupt a network segment. That risk belongs to a separate condition: A provider-facing interface accepts unexpected routing-control connections from an unapproved adjacent host. Here, 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. For energy distribution business while tracing a degraded application flow, the acceptance test should show that a controlled AAA outage allows an approved emergency operator and audit records document the session. D:Improper routing-instance assignment can expose one customer's traffic to another. That risk belongs to a separate condition: Traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance. Here, 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 272The datacom engineering team at a maritime terminal after a monitored link change reviews this independent fictional networking case: A provider-facing interface accepts unexpected routing-control connections from an unapproved adjacent host. If this issue remains unresolved, what immediate availability or security risk follows most directly? A missing fallback can prevent safe restoration during an identity infrastructure incident A NAT-only repair can leave return traffic asymmetric and business sessions broken Improper routing-instance assignment can expose one customer's traffic to another Unrestricted routing peers can inject false reachability and disrupt a network segment ExplanationCorrect Answer D:Unrestricted routing peers can inject false reachability and disrupt a network segment. Leaving the exact fault unresolved means: A provider-facing interface accepts unexpected routing-control connections from an unapproved adjacent host. The intended response is: Restrict protocol peers and apply appropriate routing authentication or control-plane filtering. Incorrect Answers A:A campus authentication server becomes unreachable and network admins cannot access devices during an outage. In that situation, a missing fallback can prevent safe restoration during an identity infrastructure incident. Here instead, 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. B:A NAT-only repair can leave return traffic asymmetric and business sessions broken. That consequence could follow when a firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. Here, a provider-facing interface accepts unexpected routing-control connections from an unapproved adjacent host; restrict protocol peers and apply appropriate routing authentication or control-plane filtering. C:Traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance. In that situation, improper routing-instance assignment can expose one customer's traffic to another. Here instead, a provider-facing interface accepts unexpected routing-control connections from an unapproved adjacent host. Unauthorized control attempts are rejected while approved peers remain stable.
Question 273The datacom engineering team at a public water utility during a topology consistency review reviews this independent fictional networking case: A wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller. Which corrective engineering action most directly addresses this problem? Configure supported AC discovery and high-availability mechanisms, then test controller failure Correct NAC authorization attributes and dynamic VLAN/role mapping for each identity category Review the WLAN VLAN pool mapping and rebalance supported client distribution with consistent DHCP scopes Replan channel assignments and transmit power based on measured co-channel contention ExplanationCorrect Answer A:Configure supported AC discovery and high-availability mechanisms, then test controller failure. This is the specific action that addresses the fictional fault: A wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller. The governing technical reason is: Central WLAN control architectures require planned control-plane redundancy and AP recovery behavior. Verify by checking: APs register with the standby controller and client services recover within the documented bound. Incorrect Answers B:Correcting NAC authorization attributes and dynamic VLAN/role mapping for each identity category is relevant when guest devices receive an internal employee VLAN after 802.1X authorization results are mapped incorrectly by WLAN policy. It does not resolve this case: 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. C:When one SSID assigns most devices to a single client VLAN while remaining VLAN-pool ranges have unused address space, reviewing the WLAN VLAN pool mapping and rebalance supported client distribution with consistent DHCP scopes could be appropriate. Here, a wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller. Configure supported AC discovery and high-availability mechanisms, then test controller failure. D:A large lecture hall experiences low Wi-Fi throughput even with strong signal because neighboring AP radios overlap excessively on busy channels. Replanning channel assignments and transmit power based on measured co-channel contention can respond to that condition, but it would not correct the reported fault: A wireless controller outage disconnects all thin APs because they were provisioned without a reachable standby controller. APs register with the standby controller and client services recover within the documented bound.
Question 274The datacom engineering team at an insurance processing company while validating change-control evidence reviews this independent fictional networking case: An ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. A proposed remedy is: Apply appropriately scoped external prefix summarization at the originating ASBR. Which technical principle most directly supports this remedy? ASBR route aggregation reduces external advertisements without replacing ordinary ABR interarea summarization NSSA uses Type-7 external LSAs inside its area and relies on translation at an appropriate border device Standard stub areas suppress Type-5 external LSAs and normally rely on an ABR-provided default for external reachability ABR summaries reduce LSDB size but overbroad summaries can attract packets for nonexistent destinations ExplanationCorrect Answer A:ASBR route aggregation reduces external advertisements without replacing ordinary ABR interarea summarization. This directly explains why the corrective operation is appropriate: Apply appropriately scoped external prefix summarization at the originating ASBR. The observed acceptance evidence should be: Remote OSPF routers receive the summary and reach all intended attached external subnets. Incorrect Answers B:An NSSA branch redistributes a local static route that fails to appear as expected outside the NSSA. NSSA uses Type-7 external LSAs inside its area and relies on translation at an appropriate border device. The current condition differs: An ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. ASBR route aggregation reduces external advertisements without replacing ordinary ABR interarea summarization. C:When 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. By contrast, an ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables; apply appropriately scoped external prefix summarization at the originating ASBR. D:ABR summaries reduce LSDB size but overbroad summaries can attract packets for nonexistent destinations. That rule governs a different situation: An area border router advertises a broad summary that includes subnets withdrawn after a site closure. Here, an ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. Remote OSPF routers receive the summary and reach all intended attached external subnets.
Question 275The datacom engineering team at an energy distribution business while tracing a degraded application flow reviews this independent fictional networking case: A border router tags specific prefixes but the provider does not apply the expected regional no-export treatment. If this issue remains unresolved, what immediate availability or security risk follows most directly? Untested community handling can leak routes outside an intended operational boundary Incomplete understanding of attribute order leads to ineffective and potentially disruptive policy changes Diagnosing BGP policy before basic transport can prolong an otherwise simple outage Partial iBGP distribution can hide routes from only some leaf devices ExplanationCorrect Answer A:Untested community handling can leak routes outside an intended operational boundary. Leaving the exact fault unresolved means: A border router tags specific prefixes but the provider does not apply the expected regional no-export treatment. The intended response is: Validate the community value, propagation policy, and provider-supported meaning before relying on it. Incorrect Answers B:Incomplete understanding of attribute order leads to ineffective and potentially disruptive policy changes. That consequence could follow when operators expect a shortest AS path to win, but a less direct path retains higher locally configured preference. Here, a border router tags specific prefixes but the provider does not apply the expected regional no-export treatment; BGP communities convey policy intent but require receiving-network policy to interpret them. C:Diagnosing BGP policy before basic transport can prolong an otherwise simple outage. That consequence could follow when a BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. Here, a border router tags specific prefixes but the provider does not apply the expected regional no-export treatment; validate the community value, propagation policy, and provider-supported meaning before relying on it. D:Partial iBGP distribution can hide routes from only some leaf devices. That risk belongs to a separate condition: A growing datacenter iBGP full mesh becomes operationally difficult and newly added peers lack complete route distribution. Here, a border router tags specific prefixes but the provider does not apply the expected regional no-export treatment; adjacent peers show the expected communities and external advertisements are scoped as contracted.
Question 276The datacom engineering team at a public university consortium during a network security audit 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? BGP neighbor identity must align with the configured source and destination transport addresses Prefix lists and route policies should enforce precise permitted address and mask ranges at external boundaries BGP runs over TCP and needs successful IP transport to its configured peer endpoint Higher LOCAL_PREF is preferred within an autonomous system and is normally not passed to eBGP neighbors ExplanationCorrect Answer D: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 A:BGP neighbor identity must align with the configured source and destination transport addresses. That rule governs a different situation: Two iBGP speakers configured with loopback neighbor addresses send sessions from unexpected physical interface addresses. Here, 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. B: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. 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. C:When a BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table, BGP runs over TCP and needs successful IP transport to its configured peer endpoint. By contrast, 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 277The datacom engineering team at a pharmaceutical testing firm after a planned hardware refresh reviews this independent fictional networking case: IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. 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 Mixed metric interpretation can produce route divergence and unstable path choices Early transit selection can blackhole traffic during control-plane recovery ExplanationCorrect Answer A:Incorrect assumptions about IP reachability can mask unformed IS-IS adjacencies. Leaving the exact fault unresolved means: IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. The intended response is: Verify physical MTU, CLNS frame transport and IS-IS padding support along the circuit. Incorrect Answers B:Stale link-state information can create asymmetric paths and packet loss. That risk belongs to a separate condition: Core routers disagree about an IS-IS route after a node restart because LSP versions and flooding state have not synchronized. Here, IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass; IS-IS uses link-layer CLNS protocol exchanges that may fail despite healthy IPv4 user traffic. C:Mixed metric interpretation can produce route divergence and unstable path choices. That consequence could follow when a new core route using a large IS-IS metric is interpreted inconsistently where devices use incompatible metric styles. Here, IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass; verify physical MTU, CLNS frame transport and IS-IS padding support along the circuit. D:When a router recovering from reboot begins attracting transit traffic before its route state is ready, early transit selection can blackhole traffic during control-plane recovery. The present failure is different: IS-IS neighbor connectivity is inconsistent across a transport that filters oversized protocol packets while data pings still pass. IS-IS hellos and LSP floods succeed and the remote LSDB converges.
Question 278The datacom engineering team at a retail banking network as part of an acceptance test reviews this independent fictional networking case: A BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. If this issue remains unresolved, what immediate availability or security risk follows most directly? Incorrect MED assumptions can cause uneven interconnect load and unpredictable ingress A valid-looking iBGP route may be unusable when the external next hop is unresolved Diagnosing BGP policy before basic transport can prolong an otherwise simple outage An unrestricted export policy may leak internal infrastructure addresses beyond the organization ExplanationCorrect Answer C:Diagnosing BGP policy before basic transport can prolong an otherwise simple outage. Leaving the exact fault unresolved means: A BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. The intended response is: Restore transport IP reachability to the neighbor before changing BGP route policies. Incorrect Answers A:When two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned, incorrect MED assumptions can cause uneven interconnect load and unpredictable ingress. The present failure is different: A BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. BGP runs over TCP and needs successful IP transport to its configured peer endpoint. B:An iBGP peer learns external prefixes but cannot install them because the original eBGP next hop is not reachable internally. In that situation, a valid-looking iBGP route may be unusable when the external next hop is unresolved. Here instead, a BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. Restore transport IP reachability to the neighbor before changing BGP route policies. D:An unrestricted export policy may leak internal infrastructure addresses beyond the organization. That risk belongs to a separate condition: An accidental /32 internal loopback is advertised to an Internet transit peer due to an overbroad export filter. Here, a BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table; TCP port 179 connectivity works and the peer progresses to Established.
Question 279The datacom engineering team at a financial clearing service during a network security audit reviews this independent fictional networking case: Two redistribution points repeatedly re-inject learned routes between OSPF and another IGP and churn route entries. Which corrective engineering action most directly addresses this problem? Align ingress marking and MQC traffic-classifier matching before adjusting queue parameters Tag redistributed routes and deny re-entry of the marked route class at the opposite redistribution point Constrain ge/le mask-length ranges and test boundary prefix acceptance Reorder and narrow the matching conditions so explicit permitted prefixes are evaluated before the general deny ExplanationCorrect Answer B:Tag redistributed routes and deny re-entry of the marked route class at the opposite redistribution point. This is the specific action that addresses the fictional fault: Two redistribution points repeatedly re-inject learned routes between OSPF and another IGP and churn route entries. The governing technical reason is: Route tagging and matching can prevent feedback when multiple dynamic-routing redistribution points exist. Verify by checking: Route advertisements stop oscillating and correct original route sources remain stable. Incorrect Answers A:When a voice QoS class remains at zero matches because the classifier checks a DSCP value that the access edge never assigns, aligning ingress marking and MQC traffic-classifier matching before adjusting queue parameters could be appropriate. Here, 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. C: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 can respond to that condition, but it would not correct the reported fault: Two redistribution points repeatedly re-inject learned routes between OSPF and another IGP and churn route entries. Tag redistributed routes and deny re-entry of the marked route class at the opposite redistribution point. D: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, 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.
Question 280The 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. The team applies this remedy: Validate NAT rule matching and the effective route lookup for the translated flow. Which observation would directly demonstrate that this specific issue is resolved? A controlled AAA outage allows an approved emergency operator and audit records document the session Forged ARP updates are blocked and legitimate ARP resolution continues for approved endpoints Guest-originated SSH probes are rejected while approved administrative access continues Session/NAT records and bidirectional traces show the intended translated tuple and next hop ExplanationCorrect Answer D:Session/NAT records and bidirectional traces show the intended translated tuple and next hop. This is a directly observable check for the proposed correction: Validate NAT rule matching and the effective route lookup for the translated flow. The particular failure being investigated is: A firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. Incorrect Answers A:When a campus authentication server becomes unreachable and network admins cannot access devices during an outage, a result such as this is useful: A controlled AAA outage allows an approved emergency operator and audit records document the session. For the reported fault, 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:When an attacker on a user VLAN advertises the gateway's IPv4 address with a forged MAC and steals nearby sessions, a result such as this is useful: Forged ARP updates are blocked and legitimate ARP resolution continues for approved endpoints. For the reported fault, 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. C:Guest-originated SSH probes are rejected while approved administrative access continues. This check belongs to a router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. The actual defect is different: A firewall's translated address leaves through the wrong outbound interface because the post-translation route lookup points to an unexpected gateway. A NAT-only repair can leave return traffic asymmetric and business sessions broken.