JN0-106 Routing Fundamentals Practice Question
Which TWO configuration statements are valid for defining a static route on a Junos device?
⚠ Common exam trap
The trap here is that candidates familiar with Cisco IOS may mistakenly use `metric` or `passive` keywords, which are not valid in Junos for static routes, or confuse `reject-all` with the correct `reject` action.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
set routing-options static route 10.0.0.0/8 discard
Option A is correct because Junos supports the discard next-hop on a static route, which silently drops matching traffic and is configured exactly as set routing-options static route 10.0.0.0/8 discard. Option C is correct because qualified-next-hop is a valid Junos static-route next-hop type that allows a per-next-hop preference, so set routing-options static route 10.0.0.0/8 qualified-next-hop 192.168.1.1 preference 10 is syntactically valid. Option B is wrong because reject-all is not a valid Junos static-route next-hop keyword; the valid reject form is simply reject. Option D is wrong because Junos static routes do not use a metric statement; route preference is set with preference, not metric. Option E is wrong because passive is not a valid static-route option in Junos.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
set routing-options static route 10.0.0.0/8 discard
Why this is correct
The `discard` action is a valid static route next-hop type in Junos, causing the router to silently drop packets that match the route without generating an ICMP unreachable message. This statement installs a route to 10.0.0.0/8 with a next-hop type of 'discard', effectively blackholing traffic—a common technique for preventing routing loops or intentionally dropping traffic. The syntax `set routing-options static route 10.0.0.0/8 discard` is fully valid and correctly configured.
- ✗
set routing-options static route 10.0.0.0/8 reject-all
Why it's wrong here
The keyword `reject-all` is not a recognized static route next-hop action in Junos; the correct term is `reject`, which drops packets and sends an ICMP unreachable back to the source. Configuring `reject-all` would result in a syntax error because Junos expects either `discard`, `reject`, or an actual next-hop address. This option is invalid because it uses a nonexistent keyword rather than the actual Junos CLI token.
- ✓
set routing-options static route 10.0.0.0/8 qualified-next-hop 192.168.1.1 preference 10
Why this is correct
`qualified-next-hop` is a legitimate static route option in Junos that allows you to define a specific next hop with its own attributes, such as a different preference value, overriding the global preference for that route. The syntax shown—`set routing-options static route 10.0.0.0/8 qualified-next-hop 192.168.1.1 preference 10`—is correct and provides a way to create unequal-cost paths or backup routes with distinct administrative distances. This is a valid configuration statement.
- ✗
set routing-options static route 10.0.0.0/8 next-hop 192.168.1.1 metric 10
Why it's wrong here
Junos static routes do not use a `metric` option to influence route selection; instead, the correct parameter is `preference`, which sets the administrative distance. The statement attempts to use `metric`, which is not recognized for static routes (unlike protocols like RIP or OSPF), so Junos would reject the configuration. Since `metric` is not a valid static route attribute, this option is invalid.
- ✗
set routing-options static route 10.0.0.0/8 passive
Why it's wrong here
The keyword `passive` is not a valid configuration option for static routes in Junos; it is used in dynamic routing protocols such as OSPF or IS-IS to suppress hello messages on an interface. Static routes have no concept of being 'passive'—they are manually defined and do not participate in neighbor discovery. Attempting to apply `passive` in this context would produce an error, making the statement invalid.
Go deeper
Related to this question
About these practice questions
One of 326 original JN0-106 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This JN0-106 practice question is part of Courseiva's free Juniper Networks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the JN0-106 exam.