Cisco 300-610 Practice Test 9
Question 80
At a dual-spine infrastructure project, a post-incident design review focuses on preventing: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. 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.
- Document which application segments truly require Layer 2 mobility.
- Test MAC mobility and gateway failover in change qualification.
- Track route and forwarding convergence after routing software upgrades.
Explanation
Correct Answer
A:The most relevant ongoing safeguard is: Audit critical vPC consistency parameters after peer upgrades or access changes. The risk it addresses is: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. This check is tied to the technical principle: vPC peers present a coordinated port-channel to a downstream device; matching member, VLAN and peer-keepalive conditions remain important. The immediate correction remains: Align the downstream LACP and both vPC peer configurations under the supported dual-homing design. Periodically validate the safeguard through two different observations. Inspect vPC consistency and suspended-member reasons Verify LACP partner and allowed VLANs on both paths. The continuing acceptance target is: Both uplinks carry the intended VLANs with deterministic redundancy.
Incorrect Answers
B: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 host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. 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: Both uplinks carry the intended VLANs with deterministic redundancy.
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 host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. 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: Both uplinks carry the intended VLANs with deterministic redundancy.
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 host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. 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: Both uplinks carry the intended VLANs with deterministic redundancy.
Question 81
At a low-latency GPU workload fabric, during a controlled design review, the team discovers: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?
- 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.
- 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
C:The relevant failure is: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. The technical distinction is: An orphan device depends on one peer rather than the shared vPC downstream pair, creating a distinct single-switch failure domain. The targeted correction is: Identify orphan attachments and create an authorized resilient attachment or application-level failover plan. Before changing the design, check two independent observations. Map appliance ports to each vPC member Test loss of the attached peer in a maintenance window. Accept the change only if: The critical service has an explicit recovery path for a single peer outage.
Incorrect Answers
A:This action targets service insertion in layer 2 domain, where the mechanism is: 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 a separate condition from the problem in this question: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. Even a successful repair of the alternative would not establish the required result: The critical service has an explicit recovery path for a single peer outage. 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 legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. Even a successful repair of the alternative would not establish the required result: The critical service has an explicit recovery path for a single peer outage. 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: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. Even a successful repair of the alternative would not establish the required result: The critical service has an explicit recovery path for a single peer outage. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
Question 82
At a two-region enterprise VXLAN fabric, before changing the fabric, the team observes: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path 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?
- 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.
- Measure route and forwarding convergence when one spine path is withdrawn; compare BFD or LACP failure notifications with packet-loss interval.
- Inspect individual member utilization during a single-flow test; confirm the platform's actual LACP load-balancing hash inputs.
Explanation
Correct Answer
A:The first observation is: Map appliance ports to each vPC member The independent second observation is: Test loss of the attached peer in a maintenance window. Together they test the proposed diagnosis of this incident: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. The underlying technical principle is: An orphan device depends on one peer rather than the shared vPC downstream pair, creating a distinct single-switch failure domain. If those checks confirm it, the appropriate next action is: Identify orphan attachments and create an authorized resilient attachment or application-level failover plan. The expected measurable result is: The critical service has an explicit recovery path for a single peer outage.
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 legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. The discriminating observations here are: Map appliance ports to each vPC member Test loss of the attached peer in a maintenance window.
C: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 legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. The discriminating observations here are: Map appliance ports to each vPC member Test loss of the attached peer in a maintenance window.
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: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. The discriminating observations here are: Map appliance ports to each vPC member Test loss of the attached peer in a maintenance window.
Question 83
At a 60-rack compute cluster, the data-center team needs to explain this behavior: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?
- vPC peers present a coordinated port-channel to a downstream device; matching member, VLAN and peer-keepalive conditions remain important.
- Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links.
- An orphan device depends on one peer rather than the shared vPC downstream pair, creating a distinct single-switch failure domain.
- 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
C:The controlling technical principle is: An orphan device depends on one peer rather than the shared vPC downstream pair, creating a distinct single-switch failure domain. This matters because the reported design failure is: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. The first diagnostic check is: Map appliance ports to each vPC member The independent check is: Test loss of the attached peer in a maintenance window. These facts support the targeted intervention: Identify orphan attachments and create an authorized resilient attachment or application-level failover plan. Confirm that the resulting design meets this condition: The critical service has an explicit recovery path for a single peer outage.
Incorrect Answers
A: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 legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. The governing principle in this situation is: An orphan device depends on one peer rather than the shared vPC downstream pair, creating a distinct single-switch failure domain.
B: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 legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. The governing principle in this situation is: An orphan device depends on one peer rather than the shared vPC downstream pair, creating a distinct single-switch failure domain.
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: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. The governing principle in this situation is: An orphan device depends on one peer rather than the shared vPC downstream pair, creating a distinct single-switch failure domain.
Question 84
At a virtualized application data center, the team completed an authorized repair for: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?
- The workload maintains intended IP reachability through the rack move.
- The critical service has an explicit recovery path for a single peer outage.
- No single flow is constrained below its required throughput by an avoidable member-link bottleneck.
- Both uplinks carry the intended VLANs with deterministic redundancy.
Explanation
Correct Answer
B:The relevant measurable success criterion is: The critical service has an explicit recovery path for a single peer outage. It addresses the original reported defect: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Map appliance ports to each vPC member Test loss of the attached peer in a maintenance window. The correction being evaluated is: Identify orphan attachments and create an authorized resilient attachment or application-level failover plan. The underlying reason that correction matters is: An orphan device depends on one peer rather than the shared vPC downstream pair, creating a distinct single-switch failure domain.
Incorrect Answers
A: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 legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. The expected measurable outcome for the actual incident is: The critical service has an explicit recovery path for a single peer outage. A positive result for the other service would not prove this requirement is met.
C: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 legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. The expected measurable outcome for the actual incident is: The critical service has an explicit recovery path for a single peer outage. A positive result for the other service would not prove this requirement is met.
D: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 legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. The expected measurable outcome for the actual incident is: The critical service has an explicit recovery path for a single peer outage. A positive result for the other service would not prove this requirement is met.
Question 85
At an AI-training data-center pod, the architecture standards group considers the recurring risk: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path 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?
- Validate member-level hot spots when workload flow count changes.
- Review appliance HA, policy synchronization and bypass tests with each topology change.
- Maintain an orphan-port inventory with risk and recovery ownership.
- Track route and forwarding convergence after routing software upgrades.
Explanation
Correct Answer
C:The most relevant ongoing safeguard is: Maintain an orphan-port inventory with risk and recovery ownership. The risk it addresses is: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. This check is tied to the technical principle: An orphan device depends on one peer rather than the shared vPC downstream pair, creating a distinct single-switch failure domain. The immediate correction remains: Identify orphan attachments and create an authorized resilient attachment or application-level failover plan. Periodically validate the safeguard through two different observations. Map appliance ports to each vPC member Test loss of the attached peer in a maintenance window. The continuing acceptance target is: The critical service has an explicit recovery path for a single peer outage.
Incorrect Answers
A: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 legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. 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: The critical service has an explicit recovery path for a single peer outage.
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 legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path 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: The critical service has an explicit recovery path for a single peer outage.
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 legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. 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: The critical service has an explicit recovery path for a single peer outage.
Question 86
At a regulated private-cloud campus, a proposed deployment has this failure mode: 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 maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?
- Identify orphan attachments and create an authorized resilient attachment or application-level failover plan.
- Align the downstream LACP and both vPC peer configurations under the supported dual-homing design.
- Size an individual link for maximum elephant-flow requirements or distribute the workload across multiple eligible flows.
- Design an approved distributed gateway and overlay extension aligned with mobility limits and MAC scale.
Explanation
Correct Answer
C:The relevant failure 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. The technical distinction is: LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links. The targeted correction is: Size an individual link for maximum elephant-flow requirements or distribute the workload across multiple eligible flows. Before changing the design, check two independent observations. Inspect individual member utilization during a single-flow test Confirm the platform's actual LACP load-balancing hash inputs. Accept the change only if: No single flow is constrained below its required throughput by an avoidable member-link bottleneck.
Incorrect Answers
A: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 2x25G port-channel is selected to carry a single 40G backup flow, assuming the flow will be striped evenly across both member links. Even a successful repair of the alternative would not establish the required result: No single flow is constrained below its required throughput by an avoidable member-link bottleneck. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
B: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 2x25G port-channel is selected to carry a single 40G backup flow, assuming the flow will be striped evenly across both member links. Even a successful repair of the alternative would not establish the required result: No single flow is constrained below its required throughput by an avoidable member-link bottleneck. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
D: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 2x25G port-channel is selected to carry a single 40G backup flow, assuming the flow will be striped evenly across both member links. Even a successful repair of the alternative would not establish the required result: No single flow is constrained below its required throughput by an avoidable member-link bottleneck. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
Question 87
At a dual-spine infrastructure project, the cause remains unconfirmed for this reported issue: A 2x25G port-channel is selected to carry a single 40G backup flow, assuming the flow will be striped evenly across both member 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 vPC consistency and suspended-member reasons; verify LACP partner and allowed VLANs on both paths.
- 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
D:The first observation is: Inspect individual member utilization during a single-flow test The independent second observation is: Confirm the platform's actual LACP load-balancing hash inputs. Together they test the proposed diagnosis of this incident: 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 underlying technical principle is: LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links. If those checks confirm it, the appropriate next action is: Size an individual link for maximum elephant-flow requirements or distribute the workload across multiple eligible flows. The expected measurable result is: No single flow is constrained below its required throughput by an avoidable member-link bottleneck.
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: 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 discriminating observations here are: Inspect individual member utilization during a single-flow test Confirm the platform's actual LACP load-balancing hash inputs.
B: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 2x25G port-channel is selected to carry a single 40G backup flow, assuming the flow will be striped evenly across both member links. The discriminating observations here are: Inspect individual member utilization during a single-flow test Confirm the platform's actual LACP load-balancing hash inputs.
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: 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 discriminating observations here are: Inspect individual member utilization during a single-flow test Confirm the platform's actual LACP load-balancing hash inputs.
Question 88
At a low-latency GPU workload fabric, a failure review must identify the central technical cause 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. 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.
- Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links.
- LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links.
- An orphan device depends on one peer rather than the shared vPC downstream pair, creating a distinct single-switch failure domain.
Explanation
Correct Answer
C:The controlling technical principle is: LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links. This matters because the reported design failure 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. The first diagnostic check is: Inspect individual member utilization during a single-flow test The independent check is: Confirm the platform's actual LACP load-balancing hash inputs. These facts support the targeted intervention: Size an individual link for maximum elephant-flow requirements or distribute the workload across multiple eligible flows. Confirm that the resulting design meets this condition: No single flow is constrained below its required throughput by an avoidable member-link bottleneck.
Incorrect Answers
A: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 2x25G port-channel is selected to carry a single 40G backup flow, assuming the flow will be striped evenly across both member links. The governing principle in this situation is: LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links.
B: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 2x25G port-channel is selected to carry a single 40G backup flow, assuming the flow will be striped evenly across both member links. The governing principle in this situation is: LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links.
D:The offered principle describes orphan port failure when vpc peer dies: An orphan device depends on one peer rather than the shared vPC downstream pair, creating a distinct single-switch failure domain. That is useful for a distinct incident, such as: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. It does not account for the reported failure: 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 governing principle in this situation is: LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links.
Question 89
At a two-region enterprise VXLAN fabric, the service owner needs evidence of resolution for: 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 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.
- Parallel spine capacity is usable without uncontrolled Layer 2 loop propagation.
- The workload maintains intended IP reachability through the rack move.
- Permitted traffic follows required inspection while preventing uncontrolled bridging loops.
Explanation
Correct Answer
A:The relevant measurable success criterion is: No single flow is constrained below its required throughput by an avoidable member-link bottleneck. It addresses the original reported defect: A 2x25G port-channel is selected to carry a single 40G backup flow, assuming the flow will be striped evenly across both member links. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Inspect individual member utilization during a single-flow test Confirm the platform's actual LACP load-balancing hash inputs. The correction being evaluated is: Size an individual link for maximum elephant-flow requirements or distribute the workload across multiple eligible flows. The underlying reason that correction matters is: LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links.
Incorrect Answers
B:This metric would help validate a correction to spanning-tree reliance in leaf-spine, rather than the original reported issue. The other issue 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. Here the defect to be resolved 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. The expected measurable outcome for the actual incident is: No single flow is constrained below its required throughput by an avoidable member-link bottleneck. A positive result for the other service would not prove this requirement is met.
C: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 2x25G port-channel is selected to carry a single 40G backup flow, assuming the flow will be striped evenly across both member links. The expected measurable outcome for the actual incident is: No single flow is constrained below its required throughput by an avoidable member-link bottleneck. 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: 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 expected measurable outcome for the actual incident is: No single flow is constrained below its required throughput by an avoidable member-link bottleneck. A positive result for the other service would not prove this requirement is met.
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.