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