NSE4 · Question #256
In order to load-share traffic using multiple static routes, the routes must be configured with ...
The correct answer is A. the same distance and same priority. To enable Equal-Cost Multi-Path (ECMP) load sharing for static routes on a FortiGate, all routes must be configured with the same administrative distance and priority.
Question
In order to load-share traffic using multiple static routes, the routes must be configured with ...
Options
- Athe same distance and same priority.
- Bthe same distance and the same weight.
- Cthe same distance but each of them must be assigned a unique priority.
- Da distance equal to its desired weight for ECMP but all must have the same priority.
How the community answered
(25 responses)- A88% (22)
- B8% (2)
- C4% (1)
Why each option
To enable Equal-Cost Multi-Path (ECMP) load sharing for static routes on a FortiGate, all routes must be configured with the same administrative distance and priority.
For FortiGate to perform Equal-Cost Multi-Path (ECMP) load sharing using multiple static routes, all the static routes targeting the same destination must be configured with the exact same administrative distance and the exact same priority. This equality signals to the routing table that these routes are equally preferred paths, allowing traffic to be distributed among them.
FortiGate static routes use 'priority' for tie-breaking when distances are equal, not 'weight' for unequal cost load balancing.
Assigning a unique priority when distances are the same would cause the FortiGate to select only the route with the lowest priority, not to load-share.
While ECMP involves equal costs, the concept of 'weight' for ECMP is not directly applied in FortiGate static routes; path preference is determined by distance and priority.
Concept tested: FortiGate ECMP static route configuration
Source: https://docs.fortinet.com/document/fortigate/7.4.0/administration-guide/869581/equal-cost-multi-path-ecmp
Topics
Community Discussion
No community discussion yet for this question.