Question 560
At Cobalt Retail, an infrastructure review by the branch WAN platform team is evaluating payment-site availability across a 64-store retail WAN during a regional modernization (FT-A-01-01). The review finds that a multinational firm sends all branch traffic through one distant hub and suffers avoidable latency. Any correction must respect this operating requirement: PCI-segmented traffic remains on approved paths. Which corrective approach best resolves the observed issue while meeting the operating constraint?
Explanation
Correct Answer
The observed problem is that a multinational firm sends all branch traffic through one distant hub and suffers avoidable latency. Design regional SD-WAN hubs with documented interregion routing and application placement as part of Cobalt Retail's payment-site availability update (FT-A-01-01), while enforcing the constraint that PCI-segmented traffic remains on approved paths. A successful implementation must be checked rather than assumed: In a controlled a 64-store retail WAN acceptance test, Representative branch traffic reaches the approved regional hub and retains reachability during a hub failure; the outcome is recorded under Cobalt Retail's rollout (FT-A-01-01). The technical reason is that Regional hub placement balances application proximity and operational resilience.
Incorrect Answers
The source case reports that a multinational firm sends all branch traffic through one distant hub and suffers avoidable latency. “Partition tenant-specific templates and administrative scopes while sharing only approved common baselines; use a reviewed service change record” addresses the technical dependency: Service-provider scale requires isolation of change authority and tenant-specific routing. The reported problem instead follows: Regional hub placement balances application proximity and operational resilience. The more direct correction is “Design regional SD-WAN hubs with documented interregion routing and application placement; stage the change with an explicit backout plan”.
The source case reports that a multinational firm sends all branch traffic through one distant hub and suffers avoidable latency. This option would change the control governed by: An overlay depends on an underlying reachable transport and does not replace it. That does not resolve the present failure, where regional hub placement balances application proximity and operational resilience. The applicable response is “Design regional SD-WAN hubs with documented interregion routing and application placement; stage the change with an explicit backout plan”.
The source case reports that a multinational firm sends all branch traffic through one distant hub and suffers avoidable latency. “Tune latency and jitter thresholds against the real application tolerance and path baseline; stage the change with an explicit backout plan” addresses the technical dependency: Overly tight performance targets can create harmful path instability. The reported problem instead follows: Regional hub placement balances application proximity and operational resilience. The more direct correction is “Design regional SD-WAN hubs with documented interregion routing and application placement; stage the change with an explicit backout plan”.