Cisco 300-610 Practice Test 11
Question 100
At a regulated private-cloud campus, the architecture standards group considers the recurring risk: A data center leaf-spine design extends all VLANs over a traditional loop-prone Layer 2 core and expects STP to use all parallel spine links. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?
- Maintain an orphan-port inventory with risk and recovery ownership.
- Document which application segments truly require Layer 2 mobility.
- Test MAC mobility and gateway failover in change qualification.
- Validate member-level hot spots when workload flow count changes.
Explanation
Correct Answer
B:The most relevant ongoing safeguard is: Document which application segments truly require Layer 2 mobility. The risk it addresses is: A data center leaf-spine design extends all VLANs over a traditional loop-prone Layer 2 core and expects STP to use all parallel spine links. This check is tied to the technical principle: A routed leaf-spine underlay or supported VXLAN EVPN overlay avoids depending on a spanning tree to select one path across the entire fabric. The immediate correction remains: Select a routed underlay plus a deliberate overlay where Layer 2 extension is required, not unrestricted fabric-wide bridging. Periodically validate the safeguard through two different observations. Inspect whether spine links form routed adjacencies or bridging loops Review VLAN reachability and ECMP path utilization across the fabric. The continuing acceptance target is: Parallel spine capacity is usable without uncontrolled Layer 2 loop propagation.
Incorrect Answers
A: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: A data center leaf-spine design extends all VLANs over a traditional loop-prone Layer 2 core and expects STP to use all parallel spine links. 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: Parallel spine capacity is usable without uncontrolled Layer 2 loop propagation.
C: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: A data center leaf-spine design extends all VLANs over a traditional loop-prone Layer 2 core and expects STP to use all parallel spine links. 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: Parallel spine capacity is usable without uncontrolled Layer 2 loop propagation.
D:This is a continuing control for lacp hashing and a single large flow; its underlying principle is: LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links. The recurring risk here is different: A data center leaf-spine design extends all VLANs over a traditional loop-prone Layer 2 core and expects STP to use all parallel spine links. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A 2x25G port-channel is selected to carry a single 40G backup flow, assuming the flow will be striped evenly across both member links. The intended long-term acceptance condition remains: Parallel spine capacity is usable without uncontrolled Layer 2 loop propagation.
Question 101
At a dual-spine infrastructure project, a proposed deployment has this failure mode: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?
- Validate redundant routing adjacencies and measured failover under realistic application traffic.
- Design an approved distributed gateway and overlay extension aligned with mobility limits and MAC scale.
- Size an individual link for maximum elephant-flow requirements or distribute the workload across multiple eligible flows.
- Select a routed underlay plus a deliberate overlay where Layer 2 extension is required, not unrestricted fabric-wide bridging.
Explanation
Correct Answer
B:The relevant failure is: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The technical distinction is: Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design. The targeted correction is: Design an approved distributed gateway and overlay extension aligned with mobility limits and MAC scale. Before changing the design, check two independent observations. Inspect endpoint IP/MAC and default-gateway identity before and after a move Observe remote MAC or EVPN route updates during migration. Accept the change only if: The workload maintains intended IP reachability through the rack move.
Incorrect Answers
A:This action targets access leaf convergence design, where the mechanism is: Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links. That is a separate condition from the problem in this question: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. Even a successful repair of the alternative would not establish the required result: The workload maintains intended IP reachability through the rack move. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
C:This action targets lacp hashing and a single large flow, where the mechanism is: LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links. That is a separate condition from the problem in this question: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. Even a successful repair of the alternative would not establish the required result: The workload maintains intended IP reachability through the rack move. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
D:This action targets spanning-tree reliance in leaf-spine, where the mechanism is: A routed leaf-spine underlay or supported VXLAN EVPN overlay avoids depending on a spanning tree to select one path across the entire fabric. That is a separate condition from the problem in this question: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. Even a successful repair of the alternative would not establish the required result: The workload maintains intended IP reachability through the rack move. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
Question 102
At a low-latency GPU workload fabric, the cause remains unconfirmed for this reported issue: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. 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?
- Measure route and forwarding convergence when one spine path is withdrawn; compare BFD or LACP failure notifications with packet-loss interval.
- Inspect endpoint IP/MAC and default-gateway identity before and after a move; observe remote MAC or EVPN route updates during migration.
- Inspect whether spine links form routed adjacencies or bridging loops; review VLAN reachability and ECMP path utilization across the fabric.
- Inspect individual member utilization during a single-flow test; confirm the platform's actual LACP load-balancing hash inputs.
Explanation
Correct Answer
B:The first observation is: Inspect endpoint IP/MAC and default-gateway identity before and after a move The independent second observation is: Observe remote MAC or EVPN route updates during migration. Together they test the proposed diagnosis of this incident: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The underlying technical principle is: Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design. If those checks confirm it, the appropriate next action is: Design an approved distributed gateway and overlay extension aligned with mobility limits and MAC scale. The expected measurable result is: The workload maintains intended IP reachability through the rack move.
Incorrect Answers
A:These observations investigate access leaf convergence design; they would be useful if the symptoms were: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. That alternative rests on the principle: Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links. The question instead asks for evidence about: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The discriminating observations here are: Inspect endpoint IP/MAC and default-gateway identity before and after a move Observe remote MAC or EVPN route updates during migration.
C:These observations investigate spanning-tree reliance in leaf-spine; they would be useful if the symptoms were: A data center leaf-spine design extends all VLANs over a traditional loop-prone Layer 2 core and expects STP to use all parallel spine links. That alternative rests on the principle: A routed leaf-spine underlay or supported VXLAN EVPN overlay avoids depending on a spanning tree to select one path across the entire fabric. The question instead asks for evidence about: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The discriminating observations here are: Inspect endpoint IP/MAC and default-gateway identity before and after a move Observe remote MAC or EVPN route updates during migration.
D:These observations investigate lacp hashing and a single large flow; they would be useful if the symptoms were: A 2x25G port-channel is selected to carry a single 40G backup flow, assuming the flow will be striped evenly across both member links. That alternative rests on the principle: LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links. The question instead asks for evidence about: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The discriminating observations here are: Inspect endpoint IP/MAC and default-gateway identity before and after a move Observe remote MAC or EVPN route updates during migration.
Question 103
At a two-region enterprise VXLAN fabric, a failure review must identify the central technical cause of: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?
- LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links.
- Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design.
- Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links.
- A routed leaf-spine underlay or supported VXLAN EVPN overlay avoids depending on a spanning tree to select one path across the entire fabric.
Explanation
Correct Answer
B:The controlling technical principle is: Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design. This matters because the reported design failure is: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The first diagnostic check is: Inspect endpoint IP/MAC and default-gateway identity before and after a move The independent check is: Observe remote MAC or EVPN route updates during migration. These facts support the targeted intervention: Design an approved distributed gateway and overlay extension aligned with mobility limits and MAC scale. Confirm that the resulting design meets this condition: The workload maintains intended IP reachability through the rack move.
Incorrect Answers
A:The offered principle describes lacp hashing and a single large flow: LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links. That is useful for a distinct incident, such as: A 2x25G port-channel is selected to carry a single 40G backup flow, assuming the flow will be striped evenly across both member links. It does not account for the reported failure: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The governing principle in this situation is: Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design.
C:The offered principle describes access leaf convergence design: Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links. That is useful for a distinct incident, such as: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. It does not account for the reported failure: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The governing principle in this situation is: Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design.
D:The offered principle describes spanning-tree reliance in leaf-spine: A routed leaf-spine underlay or supported VXLAN EVPN overlay avoids depending on a spanning tree to select one path across the entire fabric. That is useful for a distinct incident, such as: A data center leaf-spine design extends all VLANs over a traditional loop-prone Layer 2 core and expects STP to use all parallel spine links. It does not account for the reported failure: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The governing principle in this situation is: Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design.
Question 104
At a 60-rack compute cluster, the service owner needs evidence of resolution for: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?
- Both uplinks carry the intended VLANs with deterministic redundancy.
- A single supported uplink failure stays within the service recovery target.
- The workload maintains intended IP reachability through the rack move.
- The critical service has an explicit recovery path for a single peer outage.
Explanation
Correct Answer
C:The relevant measurable success criterion is: The workload maintains intended IP reachability through the rack move. It addresses the original reported defect: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Inspect endpoint IP/MAC and default-gateway identity before and after a move Observe remote MAC or EVPN route updates during migration. The correction being evaluated is: Design an approved distributed gateway and overlay extension aligned with mobility limits and MAC scale. The underlying reason that correction matters is: Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design.
Incorrect Answers
A:This metric would help validate a correction to dual-homed server vpc consistency, rather than the original reported issue. The other issue is: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. Here the defect to be resolved is: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The expected measurable outcome for the actual incident is: The workload maintains intended IP reachability through the rack move. A positive result for the other service would not prove this requirement is met.
B:This metric would help validate a correction to access leaf convergence design, rather than the original reported issue. The other issue is: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. Here the defect to be resolved is: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The expected measurable outcome for the actual incident is: The workload maintains intended IP reachability through the rack move. A positive result for the other service would not prove this requirement is met.
D:This metric would help validate a correction to orphan port failure when vpc peer dies, rather than the original reported issue. The other issue is: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. Here the defect to be resolved is: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The expected measurable outcome for the actual incident is: The workload maintains intended IP reachability through the rack move. A positive result for the other service would not prove this requirement is met.
Question 105
At a virtualized application data center, after correction, the team wants to prevent recurrence of: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. 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 critical vPC consistency parameters after peer upgrades or access changes.
- Review appliance HA, policy synchronization and bypass tests with each topology change.
- Document which application segments truly require Layer 2 mobility.
- Test MAC mobility and gateway failover in change qualification.
Explanation
Correct Answer
D:The most relevant ongoing safeguard is: Test MAC mobility and gateway failover in change qualification. The risk it addresses is: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. This check is tied to the technical principle: Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design. The immediate correction remains: Design an approved distributed gateway and overlay extension aligned with mobility limits and MAC scale. Periodically validate the safeguard through two different observations. Inspect endpoint IP/MAC and default-gateway identity before and after a move Observe remote MAC or EVPN route updates during migration. The continuing acceptance target is: The workload maintains intended IP reachability through the rack move.
Incorrect Answers
A:This is a continuing control for dual-homed server vpc consistency; its underlying principle is: vPC peers present a coordinated port-channel to a downstream device; matching member, VLAN and peer-keepalive conditions remain important. The recurring risk here is different: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The intended long-term acceptance condition remains: The workload maintains intended IP reachability through the rack move.
B: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: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. 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: The workload maintains intended IP reachability through the rack move.
C:This is a continuing control for spanning-tree reliance in leaf-spine; its underlying principle is: A routed leaf-spine underlay or supported VXLAN EVPN overlay avoids depending on a spanning tree to select one path across the entire fabric. The recurring risk here is different: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A data center leaf-spine design extends all VLANs over a traditional loop-prone Layer 2 core and expects STP to use all parallel spine links. The intended long-term acceptance condition remains: The workload maintains intended IP reachability through the rack move.
Question 106
At an AI-training data-center pod, a design review reports the following issue: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?
- Design an approved distributed gateway and overlay extension aligned with mobility limits and MAC scale.
- Select a routed underlay plus a deliberate overlay where Layer 2 extension is required, not unrestricted fabric-wide bridging.
- Validate redundant routing adjacencies and measured failover under realistic application traffic.
- Align the downstream LACP and both vPC peer configurations under the supported dual-homing design.
Explanation
Correct Answer
C:The relevant failure is: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The technical distinction is: Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links. The targeted correction is: Validate redundant routing adjacencies and measured failover under realistic application traffic. Before changing the design, check two independent observations. Measure route and forwarding convergence when one spine path is withdrawn Compare BFD or LACP failure notifications with packet-loss interval. Accept the change only if: A single supported uplink failure stays within the service recovery target.
Incorrect Answers
A:This action targets endpoint mobility between racks, where the mechanism is: Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design. That is a separate condition from the problem in this question: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. Even a successful repair of the alternative would not establish the required result: A single supported uplink failure stays within the service recovery target. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
B:This action targets spanning-tree reliance in leaf-spine, where the mechanism is: A routed leaf-spine underlay or supported VXLAN EVPN overlay avoids depending on a spanning tree to select one path across the entire fabric. That is a separate condition from the problem in this question: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. Even a successful repair of the alternative would not establish the required result: A single supported uplink failure stays within the service recovery target. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
D:This action targets dual-homed server vpc consistency, where the mechanism is: vPC peers present a coordinated port-channel to a downstream device; matching member, VLAN and peer-keepalive conditions remain important. That is a separate condition from the problem in this question: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. Even a successful repair of the alternative would not establish the required result: A single supported uplink failure stays within the service recovery target. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
Question 107
At a regulated private-cloud campus, two engineers propose competing diagnoses for this condition: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. 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 vPC consistency and suspended-member reasons; verify LACP partner and allowed VLANs on both paths.
- Measure route and forwarding convergence when one spine path is withdrawn; compare BFD or LACP failure notifications with packet-loss interval.
- Map appliance ports to each vPC member; test loss of the attached peer in a maintenance window.
- Trace bridged traffic through the appliance and both leaf paths; simulate an approved appliance outage and inspect forwarding state.
Explanation
Correct Answer
B:The first observation is: Measure route and forwarding convergence when one spine path is withdrawn The independent second observation is: Compare BFD or LACP failure notifications with packet-loss interval. Together they test the proposed diagnosis of this incident: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The underlying technical principle is: Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links. If those checks confirm it, the appropriate next action is: Validate redundant routing adjacencies and measured failover under realistic application traffic. The expected measurable result is: A single supported uplink failure stays within the service recovery target.
Incorrect Answers
A:These observations investigate dual-homed server vpc consistency; they would be useful if the symptoms were: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. That alternative rests on the principle: vPC peers present a coordinated port-channel to a downstream device; matching member, VLAN and peer-keepalive conditions remain important. The question instead asks for evidence about: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The discriminating observations here are: Measure route and forwarding convergence when one spine path is withdrawn Compare BFD or LACP failure notifications with packet-loss interval.
C:These observations investigate orphan port failure when vpc peer dies; they would be useful if the symptoms were: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. That alternative rests on the principle: An orphan device depends on one peer rather than the shared vPC downstream pair, creating a distinct single-switch failure domain. The question instead asks for evidence about: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The discriminating observations here are: Measure route and forwarding convergence when one spine path is withdrawn Compare BFD or LACP failure notifications with packet-loss interval.
D:These observations investigate service insertion in layer 2 domain; they would be useful if the symptoms were: A security appliance is inserted inline between two top-of-rack switches without defining loop prevention or failure bypass. That alternative rests on the principle: Layer 2 service insertion changes traffic path and bridge-loop domains; bypass, fail-open/fail-closed and redundant path design must be explicit. The question instead asks for evidence about: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The discriminating observations here are: Measure route and forwarding convergence when one spine path is withdrawn Compare BFD or LACP failure notifications with packet-loss interval.
Question 108
At a dual-spine infrastructure project, the design group challenges an assumption behind this issue: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?
- Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design.
- Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links.
- Layer 2 service insertion changes traffic path and bridge-loop domains; bypass, fail-open/fail-closed and redundant path design must be explicit.
- A routed leaf-spine underlay or supported VXLAN EVPN overlay avoids depending on a spanning tree to select one path across the entire fabric.
Explanation
Correct Answer
B:The controlling technical principle is: Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links. This matters because the reported design failure is: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The first diagnostic check is: Measure route and forwarding convergence when one spine path is withdrawn The independent check is: Compare BFD or LACP failure notifications with packet-loss interval. These facts support the targeted intervention: Validate redundant routing adjacencies and measured failover under realistic application traffic. Confirm that the resulting design meets this condition: A single supported uplink failure stays within the service recovery target.
Incorrect Answers
A:The offered principle describes endpoint mobility between racks: Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design. That is useful for a distinct incident, such as: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. It does not account for the reported failure: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The governing principle in this situation is: Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links.
C:The offered principle describes service insertion in layer 2 domain: Layer 2 service insertion changes traffic path and bridge-loop domains; bypass, fail-open/fail-closed and redundant path design must be explicit. That is useful for a distinct incident, such as: A security appliance is inserted inline between two top-of-rack switches without defining loop prevention or failure bypass. It does not account for the reported failure: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The governing principle in this situation is: Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links.
D:The offered principle describes spanning-tree reliance in leaf-spine: A routed leaf-spine underlay or supported VXLAN EVPN overlay avoids depending on a spanning tree to select one path across the entire fabric. That is useful for a distinct incident, such as: A data center leaf-spine design extends all VLANs over a traditional loop-prone Layer 2 core and expects STP to use all parallel spine links. It does not account for the reported failure: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The governing principle in this situation is: Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links.
Question 109
At a low-latency GPU workload fabric, a change has been proposed for the following condition: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?
- Both uplinks carry the intended VLANs with deterministic redundancy.
- The critical service has an explicit recovery path for a single peer outage.
- A single supported uplink failure stays within the service recovery target.
- Permitted traffic follows required inspection while preventing uncontrolled bridging loops.
Explanation
Correct Answer
C:The relevant measurable success criterion is: A single supported uplink failure stays within the service recovery target. It addresses the original reported defect: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Measure route and forwarding convergence when one spine path is withdrawn Compare BFD or LACP failure notifications with packet-loss interval. The correction being evaluated is: Validate redundant routing adjacencies and measured failover under realistic application traffic. The underlying reason that correction matters is: Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links.
Incorrect Answers
A:This metric would help validate a correction to dual-homed server vpc consistency, rather than the original reported issue. The other issue is: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. Here the defect to be resolved is: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The expected measurable outcome for the actual incident is: A single supported uplink failure stays within the service recovery target. A positive result for the other service would not prove this requirement is met.
B:This metric would help validate a correction to orphan port failure when vpc peer dies, rather than the original reported issue. The other issue is: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. Here the defect to be resolved is: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The expected measurable outcome for the actual incident is: A single supported uplink failure stays within the service recovery target. A positive result for the other service would not prove this requirement is met.
D:This metric would help validate a correction to service insertion in layer 2 domain, rather than the original reported issue. The other issue is: A security appliance is inserted inline between two top-of-rack switches without defining loop prevention or failure bypass. Here the defect to be resolved is: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The expected measurable outcome for the actual incident is: A single supported uplink failure stays within the service recovery target. A positive result for the other service would not prove this requirement is met.
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.