cert
cert-1
cert-2

Pass Cisco 300-610 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
300-610 Exam - Verified By Experts
300-610 Premium File

300-610 Premium File

$69.99
$76.99
  • Premium File 350 Questions & Answers. Last Update: Nov 13, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 10 downloads in the last 7 days
block-screenshots
Cisco 300-610 Practice Test 14

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?

  1. Audit multipath settings after policy or ASN changes.
  2. Review routing ownership and anycast addresses during application migrations.
  3. Test path symmetry whenever ECMP or service appliance topology changes.
  4. 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.

Question 131

At a two-region enterprise VXLAN fabric, a proposed deployment has this failure mode: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?

  1. Validate BGP best-path and multipath eligibility before tuning ECMP load distribution.
  2. Assign approved tenant interfaces to separate VRFs with scoped inter-VRF policy.
  3. Choose an overlay mobility or renumbering strategy based on supported address advertisement semantics.
  4. Validate platform and neighbor support for graceful restart and NSF together with real failover packet impact.

Explanation

Correct Answer

C:

The relevant failure is: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The technical distinction is: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix. The targeted correction is: Choose an overlay mobility or renumbering strategy based on supported address advertisement semantics. Before changing the design, check two independent observations. Inspect route ownership before and after relocation Validate default gateway, neighbor cache and remote ingress forwarding. Accept the change only if: Traffic reaches the moved endpoint through supported current network routes.

Incorrect Answers

A:

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 container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. Even a successful repair of the alternative would not establish the required result: Traffic reaches the moved endpoint through supported current network routes. 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: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. Even a successful repair of the alternative would not establish the required result: Traffic reaches the moved endpoint through supported current network routes. 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: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. Even a successful repair of the alternative would not establish the required result: Traffic reaches the moved endpoint through supported current network routes. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

Question 132

At a 60-rack compute cluster, the cause remains unconfirmed for this reported issue: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. 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?

  1. Inspect route ownership before and after relocation; validate default gateway, neighbor cache and remote ingress forwarding.
  2. Inspect negotiated graceful-restart capabilities; run an approved supervisor switchover while measuring retained forwarding and stale-route expiry.
  3. Compare relevant BGP attributes and installed next hops; inspect hardware FIB ECMP groups during representative flows.
  4. Inspect per-VRF route tables and interface bindings; test one permitted and one forbidden cross-tenant flow.

Explanation

Correct Answer

A:

The first observation is: Inspect route ownership before and after relocation The independent second observation is: Validate default gateway, neighbor cache and remote ingress forwarding. Together they test the proposed diagnosis of this incident: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The underlying technical principle is: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix. If those checks confirm it, the appropriate next action is: Choose an overlay mobility or renumbering strategy based on supported address advertisement semantics. The expected measurable result is: Traffic reaches the moved endpoint through supported current network routes.

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: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The discriminating observations here are: Inspect route ownership before and after relocation Validate default gateway, neighbor cache and remote ingress forwarding.

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: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The discriminating observations here are: Inspect route ownership before and after relocation Validate default gateway, neighbor cache and remote ingress forwarding.

D:

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 container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The discriminating observations here are: Inspect route ownership before and after relocation Validate default gateway, neighbor cache and remote ingress forwarding.

Question 133

At a virtualized application data center, a failure review must identify the central technical cause of: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?

  1. Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric.
  2. VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts.
  3. Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state.
  4. Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix.

Explanation

Correct Answer

D:

The controlling technical principle is: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix. This matters because the reported design failure is: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The first diagnostic check is: Inspect route ownership before and after relocation The independent check is: Validate default gateway, neighbor cache and remote ingress forwarding. These facts support the targeted intervention: Choose an overlay mobility or renumbering strategy based on supported address advertisement semantics. Confirm that the resulting design meets this condition: Traffic reaches the moved endpoint through supported current network routes.

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 container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The governing principle in this situation is: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix.

B:

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: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The governing principle in this situation is: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix.

C:

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 container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The governing principle in this situation is: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix.

Question 134

At an AI-training data-center pod, the service owner needs evidence of resolution for: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?

  1. Eligible alternate paths enter forwarding without selecting unrelated or unequal policy routes.
  2. A control-plane restart causes a documented and acceptable data-plane disruption.
  3. Traffic reaches the moved endpoint through supported current network routes.
  4. Network forwarding and application recovery meet their separate declared objectives.

Explanation

Correct Answer

C:

The relevant measurable success criterion is: Traffic reaches the moved endpoint through supported current network routes. It addresses the original reported defect: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Inspect route ownership before and after relocation Validate default gateway, neighbor cache and remote ingress forwarding. The correction being evaluated is: Choose an overlay mobility or renumbering strategy based on supported address advertisement semantics. The underlying reason that correction matters is: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix.

Incorrect Answers

A:

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 container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The expected measurable outcome for the actual incident is: Traffic reaches the moved endpoint through supported current network routes. A positive result for the other service would not prove this requirement is met.

B:

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 container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The expected measurable outcome for the actual incident is: Traffic reaches the moved endpoint through supported current network 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 container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The expected measurable outcome for the actual incident is: Traffic reaches the moved endpoint through supported current network routes. A positive result for the other service would not prove this requirement is met.

Question 135

At a regulated private-cloud campus, after correction, the team wants to prevent recurrence of: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?

  1. Audit VRF mappings and route leaking during network provisioning.
  2. Review routing ownership and anycast addresses during application migrations.
  3. Periodically test stale-route cleanup after incomplete restart scenarios.
  4. Include application traces in infrastructure convergence acceptance tests.

Explanation

Correct Answer

B:

The most relevant ongoing safeguard is: Review routing ownership and anycast addresses during application migrations. The risk it addresses is: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. This check is tied to the technical principle: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix. The immediate correction remains: Choose an overlay mobility or renumbering strategy based on supported address advertisement semantics. Periodically validate the safeguard through two different observations. Inspect route ownership before and after relocation Validate default gateway, neighbor cache and remote ingress forwarding. The continuing acceptance target is: Traffic reaches the moved endpoint through supported current network routes.

Incorrect Answers

A:

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 container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. 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: Traffic reaches the moved endpoint through supported current network routes.

C:

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 container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. 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: Traffic reaches the moved endpoint through supported current network routes.

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 container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. 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: Traffic reaches the moved endpoint through supported current network routes.

Question 136

At a dual-spine infrastructure project, a design review reports the following issue: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?

  1. Choose an overlay mobility or renumbering strategy based on supported address advertisement semantics.
  2. Design symmetric service chains or approved state-sharing and route steering across both directions.
  3. Validate BGP best-path and multipath eligibility before tuning ECMP load distribution.
  4. Set separate fabric convergence and service availability SLOs and investigate both during fault tests.

Explanation

Correct Answer

D:

The relevant failure is: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The technical distinction is: Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state. The targeted correction is: Set separate fabric convergence and service availability SLOs and investigate both during fault tests. Before changing the design, check two independent observations. Measure FIB update time and packet loss Measure application reconnect and state restoration for the same fault. Accept the change only if: Network forwarding and application recovery meet their separate declared objectives.

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: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. Even a successful repair of the alternative would not establish the required result: Network forwarding and application recovery meet their separate declared objectives. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

B:

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 data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. Even a successful repair of the alternative would not establish the required result: Network forwarding and application recovery meet their separate declared objectives. 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: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. Even a successful repair of the alternative would not establish the required result: Network forwarding and application recovery meet their separate declared objectives. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

Question 137

At a low-latency GPU workload fabric, two engineers propose competing diagnoses for this condition: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. 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?

  1. Compare relevant BGP attributes and installed next hops; inspect hardware FIB ECMP groups during representative flows.
  2. Measure FIB update time and packet loss; measure application reconnect and state restoration for the same fault.
  3. Inspect route ownership before and after relocation; validate default gateway, neighbor cache and remote ingress forwarding.
  4. Inspect per-VRF route tables and interface bindings; test one permitted and one forbidden cross-tenant flow.

Explanation

Correct Answer

B:

The first observation is: Measure FIB update time and packet loss The independent second observation is: Measure application reconnect and state restoration for the same fault. Together they test the proposed diagnosis of this incident: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The underlying technical principle is: Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state. If those checks confirm it, the appropriate next action is: Set separate fabric convergence and service availability SLOs and investigate both during fault tests. The expected measurable result is: Network forwarding and application recovery meet their separate declared objectives.

Incorrect Answers

A:

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: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The discriminating observations here are: Measure FIB update time and packet loss Measure application reconnect and state restoration for the same fault.

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 data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The discriminating observations here are: Measure FIB update time and packet loss Measure application reconnect and state restoration for the same fault.

D:

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 data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The discriminating observations here are: Measure FIB update time and packet loss Measure application reconnect and state restoration for the same fault.

Question 138

At a two-region enterprise VXLAN fabric, the design group challenges an assumption behind this issue: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?

  1. Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state.
  2. Graceful restart can preserve forwarding only when the participating devices maintain appropriate forwarding state and honor restart signalling.
  3. Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix.
  4. Routing protocol multipath selection has specific attributes and configuration prerequisites separate from physical availability.

Explanation

Correct Answer

A:

The controlling technical principle is: Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state. This matters because the reported design failure is: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The first diagnostic check is: Measure FIB update time and packet loss The independent check is: Measure application reconnect and state restoration for the same fault. These facts support the targeted intervention: Set separate fabric convergence and service availability SLOs and investigate both during fault tests. Confirm that the resulting design meets this condition: Network forwarding and application recovery meet their separate declared objectives.

Incorrect Answers

B:

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: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The governing principle in this situation is: Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state.

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 data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The governing principle in this situation is: Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state.

D:

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: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The governing principle in this situation is: Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state.

Question 139

At a 60-rack compute cluster, a change has been proposed for the following condition: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?

  1. Network forwarding and application recovery meet their separate declared objectives.
  2. Each tenant uses overlapping subnets without unintended inter-tenant forwarding.
  3. A control-plane restart causes a documented and acceptable data-plane disruption.
  4. Traffic reaches the moved endpoint through supported current network routes.

Explanation

Correct Answer

A:

The relevant measurable success criterion is: Network forwarding and application recovery meet their separate declared objectives. It addresses the original reported defect: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Measure FIB update time and packet loss Measure application reconnect and state restoration for the same fault. The correction being evaluated is: Set separate fabric convergence and service availability SLOs and investigate both during fault tests. The underlying reason that correction matters is: Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state.

Incorrect Answers

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: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The expected measurable outcome for the actual incident is: Network forwarding and application recovery meet their separate declared objectives. 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 data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The expected measurable outcome for the actual incident is: Network forwarding and application recovery meet their separate declared objectives. A positive result for the other service would not prove this requirement is met.

D:

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 data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The expected measurable outcome for the actual incident is: Network forwarding and application recovery meet their separate declared objectives. A positive result for the other service would not prove this requirement is met.

Question 140

At a virtualized application data center, a post-incident design review focuses on preventing: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?

  1. Include application traces in infrastructure convergence acceptance tests.
  2. Review routing ownership and anycast addresses during application migrations.
  3. Audit VRF mappings and route leaking during network provisioning.
  4. Test path symmetry whenever ECMP or service appliance topology changes.

Explanation

Correct Answer

A:

The most relevant ongoing safeguard is: Include application traces in infrastructure convergence acceptance tests. The risk it addresses is: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. This check is tied to the technical principle: Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state. The immediate correction remains: Set separate fabric convergence and service availability SLOs and investigate both during fault tests. Periodically validate the safeguard through two different observations. Measure FIB update time and packet loss Measure application reconnect and state restoration for the same fault. The continuing acceptance target is: Network forwarding and application recovery meet their separate declared objectives.

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 data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. 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: Network forwarding and application recovery meet their separate declared objectives.

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 data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. 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: Network forwarding and application recovery meet their separate declared objectives.

D:

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 data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. 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: Network forwarding and application recovery meet their separate declared objectives.

Designing Cisco Data Center Infrastructure for Traditional and AI Workloads (300-610) Practice Tests