Cisco 300-610 Practice Test 13
Question 120
At an AI-training data-center pod, after correction, the team wants to prevent recurrence of: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?
- Periodically test stale-route cleanup after incomplete restart scenarios.
- Test path symmetry whenever ECMP or service appliance topology changes.
- Audit VRF mappings and route leaking during network provisioning.
- Include application traces in infrastructure convergence acceptance tests.
Explanation
Correct Answer
A:The most relevant ongoing safeguard is: Periodically test stale-route cleanup after incomplete restart scenarios. The risk it addresses is: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. This check is tied to the technical principle: Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling. The immediate correction remains: Validate platform and neighbor support for graceful restart and NSF together with real failover packet impact. Periodically validate the safeguard through two different observations. Inspect negotiated graceful-restart capabilities Run an approved supervisor switchover while measuring retained forwarding and stale-route expiry. The continuing acceptance target is: A control-plane restart causes a documented and acceptable data-plane disruption.
Incorrect Answers
B:This is a continuing control for active-active load balancer path symmetry; its underlying principle is: Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric. The recurring risk here is different: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The intended long-term acceptance condition remains: A control-plane restart causes a documented and acceptable data-plane disruption.
C:This is a continuing control for vrf-lite tenant isolation; its underlying principle is: VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts. The recurring risk here is different: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The intended long-term acceptance condition remains: A control-plane restart causes a documented and acceptable data-plane disruption.
D:This is a continuing control for fast underlay convergence versus slow applications; its underlying principle is: Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state. The recurring risk here is different: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The intended long-term acceptance condition remains: A control-plane restart causes a documented and acceptable data-plane disruption.
Question 121
At a regulated private-cloud campus, a design review reports the following issue: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?
- Choose an overlay mobility or renumbering strategy based on supported address advertisement semantics.
- Assign approved tenant interfaces to separate VRFs with scoped inter-VRF policy.
- Validate BGP best-path and multipath eligibility before tuning ECMP load distribution.
- Design symmetric service chains or approved state-sharing and route steering across both directions.
Explanation
Correct Answer
D:The relevant failure is: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The technical distinction is: Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric. The targeted correction is: Design symmetric service chains or approved state-sharing and route steering across both directions. Before changing the design, check two independent observations. Trace five-tuple flows and reverse paths through service nodes Inspect connection-state synchronization and drop reasons after failover. Accept the change only if: Both directions of permitted sessions pass the intended inspection service.
Incorrect Answers
A:This action targets ip mobility with stretched routed boundaries, where the mechanism is: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix. That is a separate condition from the problem in this question: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. Even a successful repair of the alternative would not establish the required result: Both directions of permitted sessions pass the intended inspection service. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
B:This action targets vrf-lite tenant isolation, where the mechanism is: VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts. That is a separate condition from the problem in this question: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. Even a successful repair of the alternative would not establish the required result: Both directions of permitted sessions pass the intended inspection service. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
C:This action targets bgp ecmp multipath policy, where the mechanism is: Routing protocol multipath selection has specific attributes and configuration prerequisites separate from physical availability. That is a separate condition from the problem in this question: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. Even a successful repair of the alternative would not establish the required result: Both directions of permitted sessions pass the intended inspection service. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
Question 122
At a dual-spine infrastructure project, two engineers propose competing diagnoses for this condition: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. Acceptance requires evidence from the running system, not just the saved design. Which pair of observations most directly tests the proposed diagnosis before a change?
- Inspect negotiated graceful-restart capabilities; run an approved supervisor switchover while measuring retained forwarding and stale-route expiry.
- Inspect per-VRF route tables and interface bindings; test one permitted and one forbidden cross-tenant flow.
- Compare relevant BGP attributes and installed next hops; inspect hardware FIB ECMP groups during representative flows.
- Trace five-tuple flows and reverse paths through service nodes; inspect connection-state synchronization and drop reasons after failover.
Explanation
Correct Answer
D:The first observation is: Trace five-tuple flows and reverse paths through service nodes The independent second observation is: Inspect connection-state synchronization and drop reasons after failover. Together they test the proposed diagnosis of this incident: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The underlying technical principle is: Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric. If those checks confirm it, the appropriate next action is: Design symmetric service chains or approved state-sharing and route steering across both directions. The expected measurable result is: Both directions of permitted sessions pass the intended inspection service.
Incorrect Answers
A:These observations investigate routing graceful restart dependency; they would be useful if the symptoms were: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. That alternative rests on the principle: Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling. The question instead asks for evidence about: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The discriminating observations here are: Trace five-tuple flows and reverse paths through service nodes Inspect connection-state synchronization and drop reasons after failover.
B:These observations investigate vrf-lite tenant isolation; they would be useful if the symptoms were: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. That alternative rests on the principle: VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts. The question instead asks for evidence about: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The discriminating observations here are: Trace five-tuple flows and reverse paths through service nodes Inspect connection-state synchronization and drop reasons after failover.
C:These observations investigate bgp ecmp multipath policy; they would be useful if the symptoms were: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. That alternative rests on the principle: Routing protocol multipath selection has specific attributes and configuration prerequisites separate from physical availability. The question instead asks for evidence about: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The discriminating observations here are: Trace five-tuple flows and reverse paths through service nodes Inspect connection-state synchronization and drop reasons after failover.
Question 123
At a low-latency GPU workload fabric, the design group challenges an assumption behind this issue: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?
- VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts.
- Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric.
- Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix.
- Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling.
Explanation
Correct Answer
B:The controlling technical principle is: Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric. This matters because the reported design failure is: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The first diagnostic check is: Trace five-tuple flows and reverse paths through service nodes The independent check is: Inspect connection-state synchronization and drop reasons after failover. These facts support the targeted intervention: Design symmetric service chains or approved state-sharing and route steering across both directions. Confirm that the resulting design meets this condition: Both directions of permitted sessions pass the intended inspection service.
Incorrect Answers
A:The offered principle describes vrf-lite tenant isolation: VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts. That is useful for a distinct incident, such as: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. It does not account for the reported failure: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The governing principle in this situation is: Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric.
C:The offered principle describes ip mobility with stretched routed boundaries: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix. That is useful for a distinct incident, such as: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. It does not account for the reported failure: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The governing principle in this situation is: Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric.
D:The offered principle describes routing graceful restart dependency: Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling. That is useful for a distinct incident, such as: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. It does not account for the reported failure: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The governing principle in this situation is: Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric.
Question 124
At a two-region enterprise VXLAN fabric, a change has been proposed for the following condition: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?
- Network forwarding and application recovery meet their separate declared objectives.
- Each tenant uses overlapping subnets without unintended inter-tenant forwarding.
- Traffic reaches the moved endpoint through supported current network routes.
- Both directions of permitted sessions pass the intended inspection service.
Explanation
Correct Answer
D:The relevant measurable success criterion is: Both directions of permitted sessions pass the intended inspection service. It addresses the original reported defect: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Trace five-tuple flows and reverse paths through service nodes Inspect connection-state synchronization and drop reasons after failover. The correction being evaluated is: Design symmetric service chains or approved state-sharing and route steering across both directions. The underlying reason that correction matters is: Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric.
Incorrect Answers
A:This metric would help validate a correction to fast underlay convergence versus slow applications, rather than the original reported issue. The other issue is: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. Here the defect to be resolved is: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The expected measurable outcome for the actual incident is: Both directions of permitted sessions pass the intended inspection service. A positive result for the other service would not prove this requirement is met.
B:This metric would help validate a correction to vrf-lite tenant isolation, rather than the original reported issue. The other issue is: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. Here the defect to be resolved is: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The expected measurable outcome for the actual incident is: Both directions of permitted sessions pass the intended inspection service. A positive result for the other service would not prove this requirement is met.
C:This metric would help validate a correction to ip mobility with stretched routed boundaries, rather than the original reported issue. The other issue is: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. Here the defect to be resolved is: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The expected measurable outcome for the actual incident is: Both directions of permitted sessions pass the intended inspection service. A positive result for the other service would not prove this requirement is met.
Question 125
At a 60-rack compute cluster, a post-incident design review focuses on preventing: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?
- Review routing ownership and anycast addresses during application migrations.
- Audit VRF mappings and route leaking during network provisioning.
- Test path symmetry whenever ECMP or service appliance topology changes.
- Audit multipath settings after policy or ASN changes.
Explanation
Correct Answer
C:The most relevant ongoing safeguard is: Test path symmetry whenever ECMP or service appliance topology changes. The risk it addresses is: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. This check is tied to the technical principle: Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric. The immediate correction remains: Design symmetric service chains or approved state-sharing and route steering across both directions. Periodically validate the safeguard through two different observations. Trace five-tuple flows and reverse paths through service nodes Inspect connection-state synchronization and drop reasons after failover. The continuing acceptance target is: Both directions of permitted sessions pass the intended inspection service.
Incorrect Answers
A:This is a continuing control for ip mobility with stretched routed boundaries; its underlying principle is: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix. The recurring risk here is different: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The intended long-term acceptance condition remains: Both directions of permitted sessions pass the intended inspection service.
B:This is a continuing control for vrf-lite tenant isolation; its underlying principle is: VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts. The recurring risk here is different: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The intended long-term acceptance condition remains: Both directions of permitted sessions pass the intended inspection service.
D:This is a continuing control for bgp ecmp multipath policy; its underlying principle is: Routing protocol multipath selection has specific attributes and configuration prerequisites separate from physical availability. The recurring risk here is different: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The intended long-term acceptance condition remains: Both directions of permitted sessions pass the intended inspection service.
Question 126
At a virtualized application data center, during a controlled design review, the team discovers: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?
- Set separate fabric convergence and service availability SLOs and investigate both during fault tests.
- Validate BGP best-path and multipath eligibility before tuning ECMP load distribution.
- Validate platform and neighbor support for graceful restart and NSF together with real failover packet impact.
- Design symmetric service chains or approved state-sharing and route steering across both directions.
Explanation
Correct Answer
B:The relevant failure is: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The technical distinction is: Routing protocol multipath selection has specific attributes and configuration prerequisites separate from physical availability. The targeted correction is: Validate BGP best-path and multipath eligibility before tuning ECMP load distribution. Before changing the design, check two independent observations. Compare relevant BGP attributes and installed next hops Inspect hardware FIB ECMP groups during representative flows. Accept the change only if: Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes.
Incorrect Answers
A:This action targets fast underlay convergence versus slow applications, where the mechanism is: Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state. That is a separate condition from the problem in this question: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. Even a successful repair of the alternative would not establish the required result: Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
C:This action targets routing graceful restart dependency, where the mechanism is: Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling. That is a separate condition from the problem in this question: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. Even a successful repair of the alternative would not establish the required result: Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
D:This action targets active-active load balancer path symmetry, where the mechanism is: Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric. That is a separate condition from the problem in this question: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. Even a successful repair of the alternative would not establish the required result: Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
Question 127
At an AI-training data-center pod, before changing the fabric, the team observes: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. Acceptance requires evidence from the running system, not just the saved design. Which pair of observations most directly tests the proposed diagnosis before a change?
- Inspect negotiated graceful-restart capabilities; run an approved supervisor switchover while measuring retained forwarding and stale-route expiry.
- Compare relevant BGP attributes and installed next hops; inspect hardware FIB ECMP groups during representative flows.
- Inspect route ownership before and after relocation; validate default gateway, neighbor cache and remote ingress forwarding.
- Trace five-tuple flows and reverse paths through service nodes; inspect connection-state synchronization and drop reasons after failover.
Explanation
Correct Answer
B:The first observation is: Compare relevant BGP attributes and installed next hops The independent second observation is: Inspect hardware FIB ECMP groups during representative flows. Together they test the proposed diagnosis of this incident: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The underlying technical principle is: Routing protocol multipath selection has specific attributes and configuration prerequisites separate from physical availability. If those checks confirm it, the appropriate next action is: Validate BGP best-path and multipath eligibility before tuning ECMP load distribution. The expected measurable result is: Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes.
Incorrect Answers
A:These observations investigate routing graceful restart dependency; they would be useful if the symptoms were: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. That alternative rests on the principle: Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling. The question instead asks for evidence about: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The discriminating observations here are: Compare relevant BGP attributes and installed next hops Inspect hardware FIB ECMP groups during representative flows.
C:These observations investigate ip mobility with stretched routed boundaries; they would be useful if the symptoms were: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. That alternative rests on the principle: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix. The question instead asks for evidence about: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The discriminating observations here are: Compare relevant BGP attributes and installed next hops Inspect hardware FIB ECMP groups during representative flows.
D:These observations investigate active-active load balancer path symmetry; they would be useful if the symptoms were: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. That alternative rests on the principle: Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric. The question instead asks for evidence about: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The discriminating observations here are: Compare relevant BGP attributes and installed next hops Inspect hardware FIB ECMP groups during representative flows.
Question 128
At a regulated private-cloud campus, the data-center team needs to explain this behavior: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?
- Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state.
- Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric.
- Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix.
- Routing protocol multipath selection has specific attributes and configuration prerequisites separate from physical availability.
Explanation
Correct Answer
D:The controlling technical principle is: Routing protocol multipath selection has specific attributes and configuration prerequisites separate from physical availability. This matters because the reported design failure is: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The first diagnostic check is: Compare relevant BGP attributes and installed next hops The independent check is: Inspect hardware FIB ECMP groups during representative flows. These facts support the targeted intervention: Validate BGP best-path and multipath eligibility before tuning ECMP load distribution. Confirm that the resulting design meets this condition: Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes.
Incorrect Answers
A:The offered principle describes fast underlay convergence versus slow applications: Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state. That is useful for a distinct incident, such as: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. It does not account for the reported failure: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The governing principle in this situation is: Routing protocol multipath selection has specific attributes and configuration prerequisites separate from physical availability.
B:The offered principle describes active-active load balancer path symmetry: Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric. That is useful for a distinct incident, such as: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. It does not account for the reported failure: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The governing principle in this situation is: Routing protocol multipath selection has specific attributes and configuration prerequisites separate from physical availability.
C:The offered principle describes ip mobility with stretched routed boundaries: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix. That is useful for a distinct incident, such as: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. It does not account for the reported failure: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The governing principle in this situation is: Routing protocol multipath selection has specific attributes and configuration prerequisites separate from physical availability.
Question 129
At a dual-spine infrastructure project, the team completed an authorized repair for: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?
- Both directions of permitted sessions pass the intended inspection service.
- Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes.
- A control-plane restart causes a documented and acceptable data-plane disruption.
- Network forwarding and application recovery meet their separate declared objectives.
Explanation
Correct Answer
B:The relevant measurable success criterion is: Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes. It addresses the original reported defect: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Compare relevant BGP attributes and installed next hops Inspect hardware FIB ECMP groups during representative flows. The correction being evaluated is: Validate BGP best-path and multipath eligibility before tuning ECMP load distribution. The underlying reason that correction matters is: Routing protocol multipath selection has specific attributes and configuration prerequisites separate from physical availability.
Incorrect Answers
A:This metric would help validate a correction to active-active load balancer path symmetry, rather than the original reported issue. The other issue is: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. Here the defect to be resolved is: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The expected measurable outcome for the actual incident is: Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes. A positive result for the other service would not prove this requirement is met.
C:This metric would help validate a correction to routing graceful restart dependency, rather than the original reported issue. The other issue is: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. Here the defect to be resolved is: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The expected measurable outcome for the actual incident is: Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes. A positive result for the other service would not prove this requirement is met.
D:This metric would help validate a correction to fast underlay convergence versus slow applications, rather than the original reported issue. The other issue is: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. Here the defect to be resolved is: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The expected measurable outcome for the actual incident is: Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes. A positive result for the other service would not prove this requirement is met.
Question 130
At a low-latency GPU workload fabric, the architecture standards group considers the recurring risk: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?
- Audit multipath settings after policy or ASN changes.
- Review routing ownership and anycast addresses during application migrations.
- Test path symmetry whenever ECMP or service appliance topology changes.
- Periodically test stale-route cleanup after incomplete restart scenarios.
Explanation
Correct Answer
A:The most relevant ongoing safeguard is: Audit multipath settings after policy or ASN changes. The risk it addresses is: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. This check is tied to the technical principle: Routing protocol multipath selection has specific attributes and configuration prerequisites separate from physical availability. The immediate correction remains: Validate BGP best-path and multipath eligibility before tuning ECMP load distribution. Periodically validate the safeguard through two different observations. Compare relevant BGP attributes and installed next hops Inspect hardware FIB ECMP groups during representative flows. The continuing acceptance target is: Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes.
Incorrect Answers
B:This is a continuing control for ip mobility with stretched routed boundaries; its underlying principle is: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix. The recurring risk here is different: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The intended long-term acceptance condition remains: Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes.
C:This is a continuing control for active-active load balancer path symmetry; its underlying principle is: Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric. The recurring risk here is different: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The intended long-term acceptance condition remains: Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes.
D:This is a continuing control for routing graceful restart dependency; its underlying principle is: Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling. The recurring risk here is different: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The intended long-term acceptance condition remains: Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes.