Cisco 300-610 Practice Test 12
Question 110
At a two-region enterprise VXLAN fabric, a post-incident design review focuses on preventing: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. 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 appliance HA, policy synchronization and bypass tests with each topology change.
- Track route and forwarding convergence after routing software upgrades.
- Maintain an orphan-port inventory with risk and recovery ownership.
- Test MAC mobility and gateway failover in change qualification.
Explanation
Correct Answer
B:The most relevant ongoing safeguard is: Track route and forwarding convergence after routing software upgrades. The risk it addresses is: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. This check is tied to the technical principle: Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links. The immediate correction remains: Validate redundant routing adjacencies and measured failover under realistic application traffic. Periodically validate the safeguard through two different observations. Measure route and forwarding convergence when one spine path is withdrawn Compare BFD or LACP failure notifications with packet-loss interval. The continuing acceptance target is: A single supported uplink failure stays within the service recovery target.
Incorrect Answers
A:This is a continuing control for service insertion in layer 2 domain; its underlying principle is: Layer 2 service insertion changes traffic path and bridge-loop domains; bypass, fail-open/fail-closed and redundant path design must be explicit. The recurring risk here is different: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A security appliance is inserted inline between two top-of-rack switches without defining loop prevention or failure bypass. The intended long-term acceptance condition remains: A single supported uplink failure stays within the service recovery target.
C:This is a continuing control for orphan port failure when vpc peer dies; its underlying principle is: An orphan device depends on one peer rather than the shared vPC downstream pair, creating a distinct single-switch failure domain. The recurring risk here is different: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. The intended long-term acceptance condition remains: A single supported uplink failure stays within the service recovery target.
D:This is a continuing control for endpoint mobility between racks; its underlying principle is: Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design. The recurring risk here is different: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The intended long-term acceptance condition remains: A single supported uplink failure stays within the service recovery target.
Question 111
At a 60-rack compute cluster, during a controlled design review, the team discovers: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?
- Assign approved tenant interfaces to separate VRFs with scoped inter-VRF policy.
- 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.
Explanation
Correct Answer
A:The relevant failure is: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The technical distinction is: VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts. The targeted correction is: Assign approved tenant interfaces to separate VRFs with scoped inter-VRF policy. Before changing the design, check two independent observations. Inspect per-VRF route tables and interface bindings Test one permitted and one forbidden cross-tenant flow. Accept the change only if: Each tenant uses overlapping subnets without unintended inter-tenant forwarding.
Incorrect Answers
B: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: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. Even a successful repair of the alternative would not establish the required result: Each tenant uses overlapping subnets without unintended inter-tenant forwarding. 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: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. Even a successful repair of the alternative would not establish the required result: Each tenant uses overlapping subnets without unintended inter-tenant forwarding. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
D: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: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. Even a successful repair of the alternative would not establish the required result: Each tenant uses overlapping subnets without unintended inter-tenant forwarding. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
Question 112
At a virtualized application data center, before changing the fabric, the team observes: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. 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 per-VRF route tables and interface bindings; test one permitted and one forbidden cross-tenant flow.
- 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.
- Measure FIB update time and packet loss; measure application reconnect and state restoration for the same fault.
Explanation
Correct Answer
A:The first observation is: Inspect per-VRF route tables and interface bindings The independent second observation is: Test one permitted and one forbidden cross-tenant flow. Together they test the proposed diagnosis of this incident: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The underlying technical principle is: VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts. If those checks confirm it, the appropriate next action is: Assign approved tenant interfaces to separate VRFs with scoped inter-VRF policy. The expected measurable result is: Each tenant uses overlapping subnets without unintended inter-tenant forwarding.
Incorrect Answers
B: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: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The discriminating observations here are: Inspect per-VRF route tables and interface bindings Test one permitted and one forbidden cross-tenant flow.
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: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The discriminating observations here are: Inspect per-VRF route tables and interface bindings Test one permitted and one forbidden cross-tenant flow.
D:These observations investigate fast underlay convergence versus slow applications; they would be useful if the symptoms were: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. That alternative rests on the principle: Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state. The question instead asks for evidence about: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The discriminating observations here are: Inspect per-VRF route tables and interface bindings Test one permitted and one forbidden cross-tenant flow.
Question 113
At an AI-training data-center pod, the data-center team needs to explain this behavior: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. 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.
- Routing protocol multipath selection has specific attributes and configuration prerequisites separate from physical availability.
- 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.
Explanation
Correct Answer
A:The controlling technical principle is: VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts. This matters because the reported design failure is: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The first diagnostic check is: Inspect per-VRF route tables and interface bindings The independent check is: Test one permitted and one forbidden cross-tenant flow. These facts support the targeted intervention: Assign approved tenant interfaces to separate VRFs with scoped inter-VRF policy. Confirm that the resulting design meets this condition: Each tenant uses overlapping subnets without unintended inter-tenant forwarding.
Incorrect Answers
B:The offered principle describes bgp ecmp multipath policy: Routing protocol multipath selection has specific attributes and configuration prerequisites separate from physical availability. That is useful for a distinct incident, such as: A leaf learns two equal-cost external routes but uses only one path because its BGP multipath policy is not enabled for that case. It does not account for the reported failure: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The governing principle in this situation is: VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts.
C: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: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The governing principle in this situation is: VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts.
D: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: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The governing principle in this situation is: VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts.
Question 114
At a regulated private-cloud campus, the team completed an authorized repair for: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?
- A control-plane restart causes a documented and acceptable data-plane disruption.
- Both directions of permitted sessions pass the intended inspection service.
- Each tenant uses overlapping subnets without unintended inter-tenant forwarding.
- Network forwarding and application recovery meet their separate declared objectives.
Explanation
Correct Answer
C:The relevant measurable success criterion is: Each tenant uses overlapping subnets without unintended inter-tenant forwarding. It addresses the original reported defect: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Inspect per-VRF route tables and interface bindings Test one permitted and one forbidden cross-tenant flow. The correction being evaluated is: Assign approved tenant interfaces to separate VRFs with scoped inter-VRF policy. The underlying reason that correction matters is: VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts.
Incorrect Answers
A: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: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The expected measurable outcome for the actual incident is: Each tenant uses overlapping subnets without unintended inter-tenant forwarding. A positive result for the other service would not prove this requirement is met.
B: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: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The expected measurable outcome for the actual incident is: Each tenant uses overlapping subnets without unintended inter-tenant forwarding. 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: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The expected measurable outcome for the actual incident is: Each tenant uses overlapping subnets without unintended inter-tenant forwarding. A positive result for the other service would not prove this requirement is met.
Question 115
At a dual-spine infrastructure project, the architecture standards group considers the recurring risk: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. 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.
- Periodically test stale-route cleanup after incomplete restart scenarios.
- Audit multipath settings after policy or ASN changes.
- Audit VRF mappings and route leaking during network provisioning.
Explanation
Correct Answer
D:The most relevant ongoing safeguard is: Audit VRF mappings and route leaking during network provisioning. The risk it addresses is: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. This check is tied to the technical principle: VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts. The immediate correction remains: Assign approved tenant interfaces to separate VRFs with scoped inter-VRF policy. Periodically validate the safeguard through two different observations. Inspect per-VRF route tables and interface bindings Test one permitted and one forbidden cross-tenant flow. The continuing acceptance target is: Each tenant uses overlapping subnets without unintended inter-tenant forwarding.
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: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. 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: Each tenant uses overlapping subnets without unintended inter-tenant forwarding.
B: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: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. 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: Each tenant uses overlapping subnets without unintended inter-tenant forwarding.
C: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: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. 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: Each tenant uses overlapping subnets without unintended inter-tenant forwarding.
Question 116
At a low-latency GPU workload fabric, a proposed deployment has this failure mode: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. 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.
- Choose an overlay mobility or renumbering strategy based on supported address advertisement semantics.
- Validate platform and neighbor support for graceful restart and NSF together with real failover packet impact.
Explanation
Correct Answer
D:The relevant failure is: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The technical distinction is: Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling. The targeted correction is: Validate platform and neighbor support for graceful restart and NSF together with real failover packet impact. Before changing the design, check two independent observations. Inspect negotiated graceful-restart capabilities Run an approved supervisor switchover while measuring retained forwarding and stale-route expiry. Accept the change only if: A control-plane restart causes a documented and acceptable data-plane disruption.
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 design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. Even a successful repair of the alternative would not establish the required result: A control-plane restart causes a documented and acceptable data-plane disruption. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
B: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: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. Even a successful repair of the alternative would not establish the required result: A control-plane restart causes a documented and acceptable data-plane disruption. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
C: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: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. Even a successful repair of the alternative would not establish the required result: A control-plane restart causes a documented and acceptable data-plane disruption. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
Question 117
At a two-region enterprise VXLAN fabric, the cause remains unconfirmed for this reported issue: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. 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?
- Trace five-tuple flows and reverse paths through service nodes; inspect connection-state synchronization and drop reasons after failover.
- Inspect per-VRF route tables and interface bindings; test one permitted and one forbidden cross-tenant flow.
- Inspect route ownership before and after relocation; validate default gateway, neighbor cache and remote ingress forwarding.
- Inspect negotiated graceful-restart capabilities; run an approved supervisor switchover while measuring retained forwarding and stale-route expiry.
Explanation
Correct Answer
D:The first observation is: Inspect negotiated graceful-restart capabilities The independent second observation is: Run an approved supervisor switchover while measuring retained forwarding and stale-route expiry. Together they test the proposed diagnosis of this incident: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The underlying technical principle is: Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling. If those checks confirm it, the appropriate next action is: Validate platform and neighbor support for graceful restart and NSF together with real failover packet impact. The expected measurable result is: A control-plane restart causes a documented and acceptable data-plane disruption.
Incorrect Answers
A: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 design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The discriminating observations here are: Inspect negotiated graceful-restart capabilities Run an approved supervisor switchover while measuring retained forwarding and stale-route expiry.
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: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The discriminating observations here are: Inspect negotiated graceful-restart capabilities Run an approved supervisor switchover while measuring retained forwarding and stale-route expiry.
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 design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The discriminating observations here are: Inspect negotiated graceful-restart capabilities Run an approved supervisor switchover while measuring retained forwarding and stale-route expiry.
Question 118
At a 60-rack compute cluster, a failure review must identify the central technical cause of: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?
- Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric.
- Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling.
- Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix.
- Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state.
Explanation
Correct Answer
B:The controlling technical principle is: Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling. This matters because the reported design failure is: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The first diagnostic check is: Inspect negotiated graceful-restart capabilities The independent check is: Run an approved supervisor switchover while measuring retained forwarding and stale-route expiry. These facts support the targeted intervention: Validate platform and neighbor support for graceful restart and NSF together with real failover packet impact. Confirm that the resulting design meets this condition: A control-plane restart causes a documented and acceptable data-plane disruption.
Incorrect Answers
A: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 design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The governing principle in this situation is: Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling.
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 design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The governing principle in this situation is: Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling.
D: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 design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The governing principle in this situation is: Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling.
Question 119
At a virtualized application data center, the service owner needs evidence of resolution for: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?
- Each tenant uses overlapping subnets without unintended inter-tenant forwarding.
- Traffic reaches the moved endpoint through supported current network routes.
- A control-plane restart causes a documented and acceptable data-plane disruption.
- Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes.
Explanation
Correct Answer
C:The relevant measurable success criterion is: A control-plane restart causes a documented and acceptable data-plane disruption. It addresses the original reported defect: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Inspect negotiated graceful-restart capabilities Run an approved supervisor switchover while measuring retained forwarding and stale-route expiry. The correction being evaluated is: Validate platform and neighbor support for graceful restart and NSF together with real failover packet impact. The underlying reason that correction matters is: Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling.
Incorrect Answers
A: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: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The expected measurable outcome for the actual incident is: A control-plane restart causes a documented and acceptable data-plane disruption. A positive result for the other service would not prove this requirement is met.
B: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: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The expected measurable outcome for the actual incident is: A control-plane restart causes a documented and acceptable data-plane disruption. A positive result for the other service would not prove this requirement is met.
D:This metric would help validate a correction to bgp ecmp multipath policy, rather than the original reported issue. The other issue 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. Here the defect to be resolved is: A design enables BGP graceful restart and assumes it will preserve all traffic after a route processor failover regardless of dataplane state. The expected measurable outcome for the actual incident is: A control-plane restart causes a documented and acceptable data-plane disruption. A positive result for the other service would not prove this requirement is met.
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.