Question 1
A Fortinet SD-WAN/FortiSASE operations team encounters the following situation: A global retailer's 82 branches in three continents hairpin every intraregion transfer through one distant hub, adding 180 ms to warehouse synchronization. Given this specific Fortinet deployment or fault, which action should the engineer prioritize to resolve the reported condition?
Explanation
Correct Answer
This is the intended corrective decision for the described condition: A global retailer's 82 branches in three continents hairpin every intraregion transfer through one distant hub, adding 180 ms to warehouse synchronization. The underlying issue is that The centralized hub topology introduces avoidable intercontinental transit for traffic that has a local destination After this action, the specific acceptance evidence should be: Path traces between two warehouses in the same region stay on the regional overlay and application latency falls below its target.
Incorrect Answers
This is a plausible action for another Design enterprise SD-WAN architectures situation: A managed service provider uses one shared BGP routing table for two bank customers, and one customer's private prefix appears in the other's branch route view. Its target cause is: Tenant routes were mixed in a common routing context without an isolation boundary. The present case instead needs to address: The centralized hub topology introduces avoidable intercontinental transit for traffic that has a local destination. It does not directly remediate the actual observed failure.
This is a plausible action for another Design enterprise SD-WAN architectures situation: A logistics group plans zero-touch activation of 90 stores, but its CSV import associates branch device serials with the wrong site blueprints. Its target cause is: The ZTP assignment data binds the hardware to another location's configuration. The present case instead needs to address: The centralized hub topology introduces avoidable intercontinental transit for traffic that has a local destination. It does not directly remediate the actual observed failure.
This is a plausible action for another Design enterprise SD-WAN architectures situation: An acquisition adds 30 western offices and the existing eastern SD-WAN hub cannot provide acceptable interactive voice latency across the new footprint. Its target cause is: The existing hub topology was sized and positioned for the previous geographic footprint. The present case instead needs to address: The centralized hub topology introduces avoidable intercontinental transit for traffic that has a local destination. It does not directly remediate the actual observed failure.