Question 570The datacom engineering team at a financial clearing service during a network security audit reviews this independent fictional networking case: An administrator adds broad reverse-direction allow rules to fix response packets that should already match a healthy established session. A proposed remedy is: Diagnose session creation and asymmetric paths instead of opening unrestricted reverse policies. Which technical principle most directly supports this remedy? Stateful session tracking can permit legitimate return traffic according to an established flow's state Layer-2 address validation can prevent untrusted hosts from impersonating a local gateway IPsec security associations must cover compatible protected flows even when IKE negotiation is successful Centralized AAA improves accountability, but managed fallback must preserve both resilience and least privilege ExplanationCorrect Answer A:Stateful session tracking can permit legitimate return traffic according to an established flow's state. This directly explains why the corrective operation is appropriate: Diagnose session creation and asymmetric paths instead of opening unrestricted reverse policies. The observed acceptance evidence should be: Session state is present for the initiator and replies pass without extra broad allow rules. Incorrect Answers B:Layer-2 address validation can prevent untrusted hosts from impersonating a local gateway. That principle is relevant when an attacker on a user VLAN advertises the gateway's IPv4 address with a forged MAC and steals nearby sessions. Here, an administrator adds broad reverse-direction allow rules to fix response packets that should already match a healthy established session; stateful session tracking can permit legitimate return traffic according to an established flow's state. C:When 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. By contrast, an administrator adds broad reverse-direction allow rules to fix response packets that should already match a healthy established session; diagnose session creation and asymmetric paths instead of opening unrestricted reverse policies. D: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. The current condition differs: An administrator adds broad reverse-direction allow rules to fix response packets that should already match a healthy established session. Session state is present for the initiator and replies pass without extra broad allow rules.
Question 571The datacom engineering team at a cross-border logistics provider after a monitored link change reviews this independent fictional networking case: A multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. A proposed remedy is: Verify the multicast RPF route and correct source reachability or appropriate multicast routing state. Which technical principle most directly supports this remedy? Multicast RPF checks help prevent loops by accepting traffic from the interface on the expected source path PIM-DM initially floods and then prunes branches without receivers IGMP membership state is maintained by router queries and host reports rather than permanent discovery IGMP snooping limits layer-2 forwarding to listeners when it learns accurate group-to-port membership ExplanationCorrect Answer A:Multicast RPF checks help prevent loops by accepting traffic from the interface on the expected source path. This directly explains why the corrective operation is appropriate: Verify the multicast RPF route and correct source reachability or appropriate multicast routing state. The observed acceptance evidence should be: RPF diagnostics name the arriving interface as valid and the downstream stream resumes. Incorrect Answers B:PIM-DM initially floods and then prunes branches without receivers. That rule governs a different situation: A dense-mode multicast flow floods a branch that has no interested receivers because prune state is absent. Here, a multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. Multicast RPF checks help prevent loops by accepting traffic from the interface on the expected source path. C:IGMP membership state is maintained by router queries and host reports rather than permanent discovery. That principle is relevant when an access VLAN loses a multicast receiver after a quiet period because periodic IGMP membership updates never reach the upstream querier. Here, a multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded; verify the multicast RPF route and correct source reachability or appropriate multicast routing state. D:A switch floods a high-rate multicast feed to all access ports because no reliable IGMP snooping membership table was built. IGMP snooping limits layer-2 forwarding to listeners when it learns accurate group-to-port membership. The current condition differs: A multicast stream reaches a router from an interface other than its unicast reverse path toward the source and is discarded. RPF diagnostics name the arriving interface as valid and the downstream stream resumes.
Question 572The datacom engineering team at a cloud hosting provider after an incident review reviews this independent fictional networking case: A BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. A proposed remedy is: Repair next-hop recursion and underlying IGP convergence, not just the BGP session. Which technical principle most directly supports this remedy? Route reflection loop-prevention attributes prevent readvertising a route into a cycle BGP runs over TCP and needs successful IP transport to its configured peer endpoint BGP communities convey policy intent but require receiving-network policy to interpret them BGP route eligibility depends on resolvable next hops and a functioning forwarding path ExplanationCorrect Answer D:BGP route eligibility depends on resolvable next hops and a functioning forwarding path. This directly explains why the corrective operation is appropriate: Repair next-hop recursion and underlying IGP convergence, not just the BGP session. The observed acceptance evidence should be: The best BGP route resolves to a live next hop and data-plane probes succeed after reconvergence. Incorrect Answers A:An iBGP route reflected through overlapping clusters returns toward its originator unexpectedly. Route reflection loop-prevention attributes prevent readvertising a route into a cycle. The current condition differs: A BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. BGP route eligibility depends on resolvable next hops and a functioning forwarding path. B:BGP runs over TCP and needs successful IP transport to its configured peer endpoint. That principle is relevant when a BGP session never reaches TCP Established because the peer address is not reachable in the underlay routing table. Here, a BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link; repair next-hop recursion and underlying IGP convergence, not just the BGP session. C:BGP communities convey policy intent but require receiving-network policy to interpret them. That rule governs a different situation: A border router tags specific prefixes but the provider does not apply the expected regional no-export treatment. Here, a BGP-learned route remains visible but is rejected from the forwarding table because its next hop resolves to a failed IGP link. The best BGP route resolves to a live next hop and data-plane probes succeed after reconvergence.
Question 573The datacom engineering team at a health laboratory network after a planned hardware refresh reviews this independent fictional networking case: An IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly. A proposed remedy is: Specify the appropriate egress interface with the link-local next hop and verify neighbor discovery. Which technical principle most directly supports this remedy? IPv6 link-local addresses are interface scoped and may require egress context for next-hop resolution SLAAC relies on received router advertisement prefix information and associated address configuration flags IPv6 DAD uses neighbor solicitation to detect duplicate addresses before regular use Redistribution can cross routing trust boundaries and must specify which routes are authorized to cross ExplanationCorrect Answer A:IPv6 link-local addresses are interface scoped and may require egress context for next-hop resolution. This directly explains why the corrective operation is appropriate: Specify the appropriate egress interface with the link-local next hop and verify neighbor discovery. The observed acceptance evidence should be: The route installs with the expected interface and reachability probes succeed. Incorrect Answers B:When 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. By contrast, an IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly; IPv6 link-local addresses are interface scoped and may require egress context for next-hop resolution. C:When two replacement servers are configured with the same IPv6 address and one fails to bring the address online, IPv6 DAD uses neighbor solicitation to detect duplicate addresses before regular use. By contrast, an IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly; specify the appropriate egress interface with the link-local next hop and verify neighbor discovery. D:When 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. By contrast, an IPv6 static route uses a link-local next hop without a meaningful outgoing-interface scope and fails to install correctly; the route installs with the expected interface and reachability probes succeed.
Question 574The datacom engineering team at a maritime terminal after a monitored link change reviews this independent fictional networking case: Tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. The team applies this remedy: Correct matching export and import route-target policy for the tenant instance. Which observation would directly demonstrate that this specific issue is resolved? The upstream reports intended MED attributes and observed ingress tracks the agreed policy The EVPN address-family neighbor state and advertised route types appear as expected Adjacent peers show the expected communities and external advertisements are scoped as contracted The target instance imports only matching tenant routes and no unrelated VRF routes appear ExplanationCorrect Answer D:The target instance imports only matching tenant routes and no unrelated VRF routes appear. This is a directly observable check for the proposed correction: Correct matching export and import route-target policy for the tenant instance. The particular failure being investigated is: Tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. Incorrect Answers A:Two routes from the same upstream AS choose an undesired interconnect because MED values are not consistently planned. The upstream reports intended MED attributes and observed ingress tracks the agreed policy. This observation does not prove the correction for the reported defect: 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. B:The EVPN address-family neighbor state and advertised route types appear as expected. That result could validate a repair when an EVPN BGP session is Established for IPv4 unicast, yet the remote leaf receives no EVPN control-plane routes. Here, tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance; correct matching export and import route-target policy for the tenant instance. C:Adjacent peers show the expected communities and external advertisements are scoped as contracted. This check belongs to a border router tags specific prefixes but the provider does not apply the expected regional no-export treatment. The actual defect is different: Tenant route advertisements reach the EVPN route reflector but are missing from the intended remote virtual instance. Route target errors can isolate a tenant or leak routes into the wrong routing instance.
Question 575The datacom engineering team at a nationwide retail chain during a simulated failover test reviews this independent fictional networking case: A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. If this issue remains unresolved, what immediate availability or security risk follows most directly? Unexamined external metric type can funnel outbound traffic toward a distant congested exit Unaggregated external advertisements can magnify flaps across the routing domain Active routing hellos on user ports expand an unnecessary adjacency attack surface Incorrect assumptions about stub behavior can lead to unnecessary area redesign or missing external access ExplanationCorrect Answer C:Active routing hellos on user ports expand an unnecessary adjacency attack surface. Leaving the exact fault unresolved means: A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. The intended response is: Mark host-facing interfaces passive while still advertising their connected subnet through the intended OSPF process. Incorrect Answers A:A remote site incorrectly chooses an external OSPF route that ignores material internal distance to competing exit points. In that situation, unexamined external metric type can funnel outbound traffic toward a distant congested exit. Here instead, a user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. A passive OSPF interface can advertise its prefix without attempting routing adjacencies on that link. B:An ASBR emits hundreds of connected external prefixes individually and overwhelms branch route tables. In that situation, unaggregated external advertisements can magnify flaps across the routing domain. Here instead, a user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. Mark host-facing interfaces passive while still advertising their connected subnet through the intended OSPF process. D:When an engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault, incorrect assumptions about stub behavior can lead to unnecessary area redesign or missing external access. The present failure is different: A user-facing VLAN unnecessarily sends OSPF Hello packets and briefly forms a neighbor with an unauthorized test appliance. Packet captures show no OSPF Hellos on the host VLAN while the prefix remains in OSPF routes.
Question 576The datacom engineering team at an airport facilities team while tracing a degraded application flow reviews this independent fictional networking case: A border router injects internal transit and management prefixes into external BGP due to unrestricted redistribution. A proposed remedy is: Apply a narrowly matched import/export route policy during protocol redistribution. Which technical principle most directly supports this remedy? Route tagging and matching can prevent feedback when multiple dynamic-routing redistribution points exist QoS markings can be rewritten at domain boundaries; end-to-end class treatment requires consistent mapping A prefix-list entry's address and mask-length matching must both reflect the authorization boundary Redistribution can cross routing trust boundaries and must specify which routes are authorized to cross ExplanationCorrect Answer D:Redistribution can cross routing trust boundaries and must specify which routes are authorized to cross. This directly explains why the corrective operation is appropriate: Apply a narrowly matched import/export route policy during protocol redistribution. The observed acceptance evidence should be: The BGP advertisement list excludes internal infrastructure prefixes while approved service routes remain. Incorrect Answers A:Route tagging and matching can prevent feedback when multiple dynamic-routing redistribution points exist. That principle is relevant when two redistribution points repeatedly re-inject learned routes between OSPF and another IGP and churn route entries. 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:QoS markings can be rewritten at domain boundaries; end-to-end class treatment requires consistent mapping. That principle is relevant when delay-sensitive packets leave the campus with voice markings but are remarked to best-effort at a trusted border. Here, 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. 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 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 577The datacom engineering team at a pharmaceutical testing firm after a planned hardware refresh 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? Unrestricted management access increases credential-attack surface and potential device compromise Unrestricted routing peers can inject false reachability and disrupt a network segment Improper routing-instance assignment can expose one customer's traffic to another An overbroad mask range can enable unauthorized deaggregation and route leaks ExplanationCorrect Answer B: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:Unrestricted management access increases credential-attack surface and potential device compromise. That risk belongs to a separate condition: A router's SSH management listener is reachable from an untrusted guest subnet after a VLAN redesign. Here, 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. C:When traffic from two tenants reaches each other after an access service is mistakenly placed in a shared routing instance, improper routing-instance assignment can expose one customer's traffic to another. The present failure is different: 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. D:An overbroad mask range can enable unauthorized deaggregation and route leaks. That risk belongs to a separate condition: A routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes. Here, 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 578The datacom engineering team at a retail banking network as part of an acceptance test reviews this independent fictional networking case: A VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational. A proposed remedy is: Track external-uplink health and reduce VRRP priority enough for the healthy backup to take over. Which technical principle most directly supports this remedy? A VRRP group represents a virtual gateway within a specific local layer-2 segment VRRP continuity depends on end hosts and switches forwarding toward the current virtual gateway owner Virtual gateway availability must account for upstream path health, not just local gateway interface state BFD session state depends on interoperable mode and timing negotiation between peers ExplanationCorrect Answer C:Virtual gateway availability must account for upstream path health, not just local gateway interface state. This directly explains why the corrective operation is appropriate: Track external-uplink health and reduce VRRP priority enough for the healthy backup to take over. The observed acceptance evidence should be: Primary uplink failure transfers Master to the router with valid outbound reachability. Incorrect Answers A:A VRRP group represents a virtual gateway within a specific local layer-2 segment. That rule governs a different situation: Two gateway routers advertise the same virtual router ID on different VLANs due to a template copy error. Here, a VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational. Virtual gateway availability must account for upstream path health, not just local gateway interface state. B: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, VRRP continuity depends on end hosts and switches forwarding toward the current virtual gateway owner. By contrast, a VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational; track external-uplink health and reduce VRRP priority enough for the healthy backup to take over. D:When two vendors' routers never bring BFD Up because one side uses unsupported or incompatible negotiated timing behavior, BFD session state depends on interoperable mode and timing negotiation between peers. By contrast, a VRRP Master loses its external uplink but keeps serving clients because only its local VLAN interface remains operational; primary uplink failure transfers Master to the router with valid outbound reachability.
Question 579The datacom engineering team at a payment-processing provider after a monitored link change reviews this independent fictional networking case: An area border router advertises a broad summary that includes subnets withdrawn after a site closure. The team applies this remedy: Tighten the configured summary to reachable address blocks and test interarea destinations. Which observation would directly demonstrate that this specific issue is resolved? Interarea advertisements cover only approved reachable blocks and traced flows reach valid hosts The ABR default route appears in the stub area and external destinations remain reachable Database description exchange completes and the OSPF neighbor reaches Full state Route choice matches documented exit intent when internal path costs differ ExplanationCorrect Answer A:Interarea advertisements cover only approved reachable blocks and traced flows reach valid hosts. This is a directly observable check for the proposed correction: Tighten the configured summary to reachable address blocks and test interarea destinations. The particular failure being investigated is: An area border router advertises a broad summary that includes subnets withdrawn after a site closure. Incorrect Answers B:The ABR default route appears in the stub area and external destinations remain reachable. This check belongs to an engineer expects Type-5 external LSAs inside an OSPF stub area and mistakes their absence for a routing fault. The actual defect is different: An area border router advertises a broad summary that includes subnets withdrawn after a site closure. ABR summaries reduce LSDB size but overbroad summaries can attract packets for nonexistent destinations. C:When OSPF neighbors repeatedly stall in ExStart or Exchange after a tunnel MTU change, a result such as this is useful: Database description exchange completes and the OSPF neighbor reaches Full state. For the reported fault, an area border router advertises a broad summary that includes subnets withdrawn after a site closure; tighten the configured summary to reachable address blocks and test interarea destinations. D:Route choice matches documented exit intent when internal path costs differ. That result could validate a repair when a remote site incorrectly chooses an external OSPF route that ignores material internal distance to competing exit points. Here, 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.
Question 580The datacom engineering team at a local rail transit network while validating change-control evidence reviews this independent fictional networking case: A routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes. If this issue remains unresolved, what immediate availability or security risk follows most directly? An overbroad mask range can enable unauthorized deaggregation and route leaks Misplaced filters allow an unintended trust-boundary crossing without visible policy errors Broad early deny rules can remove reachable customer networks with no physical fault An unchecked PBR next hop can isolate selected users while general connectivity appears normal ExplanationCorrect Answer A:An overbroad mask range can enable unauthorized deaggregation and route leaks. Leaving the exact fault unresolved means: A routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes. The intended response is: Constrain ge/le mask-length ranges and test boundary prefix acceptance. Incorrect Answers B:Misplaced filters allow an unintended trust-boundary crossing without visible policy errors. That risk belongs to a separate condition: A security ACL intended to block guest-to-management traffic is applied outbound on the wrong interface and never matches those packets. Here, 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. C:Broad early deny rules can remove reachable customer networks with no physical fault. That risk belongs to a separate condition: A new route-policy reject rule unintentionally blocks all later permitted customer prefixes because the rule order is too broad. Here, a routing filter intended to allow a /24 aggregate accidentally allows unauthorized /25 and /32 subprefixes; constrain ge/le mask-length ranges and test boundary prefix acceptance. D:An unchecked PBR next hop can isolate selected users while general connectivity appears normal. That risk belongs to a separate condition: Policy-based routing forces finance traffic through an unavailable inspection appliance even though the regular route table has a valid path. Here, 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. For local rail transit network while validating change-control evidence, the acceptance test should show that tests accept the approved /24 and reject longer unauthorized prefixes.