Question 300
A customer asks why adding a second spine path does not necessarily double the rate of one elephant-flow TCP session. Which controlled change best addresses the described requirement?
Explanation
Correct Answer
This action addresses the stated defect: validate resilient ECMP and, if required, test multiple flows or adjust workload distribution within approved designs. The underlying constraint is that equal-cost multipath commonly hashes individual flows to a path while distributing many flows across available next hops. Verify rather than assume success: demonstrate aggregate load sharing across many five-tuple flows while a single flow remains stable on one path.
Incorrect Answers
The option “Correct underlay failure detection and routing convergence within the approved topology and timer policy” is useful in a different setting: A two-spine fabric can tolerate one path failure but the application sees blackholing for several minutes after a spine uplink drops. The case being tested is: A customer asks why adding a second spine path does not necessarily double the rate of one elephant-flow TCP session. The governing requirement is to Validate resilient ECMP and, if required, test multiple flows or adjust workload distribution within approved designs. The most relevant correction is “Validate resilient ECMP and, if required, test multiple flows or adjust workload distribution within approved designs”.
“Use validated spine-leaf cabling and routing relationships rather than ad hoc lateral transit links” is relevant to a different condition: A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. The stated question instead concerns: A customer asks why adding a second spine path does not necessarily double the rate of one elephant-flow TCP session. The governing requirement is to Validate resilient ECMP and, if required, test multiple flows or adjust workload distribution within approved designs. The most relevant correction is “Validate resilient ECMP and, if required, test multiple flows or adjust workload distribution within approved designs”.
“Repair the routed underlay addressing or protocol configuration and then validate overlay sessions” is associated with a distinct issue: An additional rack joins a Clos fabric with healthy physical interfaces but fails to form underlay neighbor sessions. By contrast, the actual problem is: A customer asks why adding a second spine path does not necessarily double the rate of one elephant-flow TCP session. The governing requirement is to Validate resilient ECMP and, if required, test multiple flows or adjust workload distribution within approved designs. The most relevant correction is “Validate resilient ECMP and, if required, test multiple flows or adjust workload distribution within approved designs”.