JN0-102 · Question #101
Assuming both paths shown in the exhibit are available, which statement is correct? [edit routing-options] user@router# show static { route 0.0.0.0/0 { next-hop 10.1.1.1; qualified-next-hop…
The correct answer is B. Traffic matching the default route will use 10.1.1.254 as the next hop. The default static route will utilize 10.1.1.254 as its next-hop because its qualified-next-hop configuration explicitly assigns it a lower (more preferred) preference value of 4, overriding the primary next-hop's default preference of 5.
Question
Assuming both paths shown in the exhibit are available, which statement is correct? [edit routing-options] user@router# show static { route 0.0.0.0/0 { next-hop 10.1.1.1; qualified-next-hop 10.1.1.254 { preference 4; } } }
Options
- ATraffic matching the default route will use 10.1.1.1 as the next hop.
- BTraffic matching the default route will use 10.1.1.254 as the next hop.
- CTraffic matching the default route will be load-balanced per packet across both next hops.
- DTraffic matching the default route will be load-balanced per flow across both next hops.
How the community answered
(54 responses)- A7% (4)
- B74% (40)
- C17% (9)
- D2% (1)
Why each option
The default static route will utilize 10.1.1.254 as its next-hop because its `qualified-next-hop` configuration explicitly assigns it a lower (more preferred) preference value of 4, overriding the primary next-hop's default preference of 5.
The primary `next-hop 10.1.1.1` has a default preference of 5, which is higher (less preferred) than the `qualified-next-hop`'s preference of 4, meaning it will not be the primary active path.
The `qualified-next-hop 10.1.1.254` is explicitly configured with a preference of 4, which is lower (and thus more preferred) than the default static route preference of 5 implicitly assigned to the primary `next-hop 10.1.1.1` in Junos OS, making 10.1.1.254 the active next-hop if both are available.
Load balancing across multiple next-hops requires them to have the same preference and typically explicit load-balancing configuration, which is not present, as the different preferences result in a single active path.
Load balancing, whether per packet or per flow, is not enabled by default for static routes with different preference values, and no explicit load-balancing configuration is shown.
Concept tested: Junos static route qualified-next-hop and preference
Source: https://www.juniper.net/documentation/us/en/software/junos/static-routing/topics/topic-map/static-routes-configuring.html
Topics
Community Discussion
No community discussion yet for this question.