Hidden Static Route: Troubleshooting Next-Hop Issues
An engineer configures a static route to 192.168.0.0/16 with next-hop 172.16.1.1. The static route appears as 'hidden' in the routing table. What is the most likely cause?
⚠ Common exam trap
The trap is that candidates might think a hidden route is due to protocol preference or commit issues. In JUNOS, 'hidden' specifically indicates a next-hop resolution failure, meaning the next-hop address is not reachable via any active route.
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
✓
The next-hop address 172.16.1.1 is unreachable
In JUNOS, a static route with a next-hop that is not reachable (i.e., there is no active route to the next-hop) is automatically placed in a 'hidden' state. The most likely cause is that the next-hop 172.16.1.1 is unreachable.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The static route preference is set too high
Why it's wrong here
Preference is a metric used only when multiple routes to the same destination prefix compete for the active slot. A static route with a high preference value is simply less preferred and would only be considered if no lower-preference route exists, but it still remains a valid candidate route. Hidden status is unrelated to preference: a route is hidden when the routing protocol or next-hop resolution fails to install it, so raising the preference would not cause the route to be hidden.
- ✓
The next-hop address 172.16.1.1 is unreachable
Why this is correct
For a static route to be installed, its next-hop address must be resolvable through an entry in the routing table. If 172.16.1.1 is not reachable—for instance, the directly connected subnet is down or no route to that address exists—Junos marks the route as hidden because the next-hop cannot be resolved. The route remains in the configuration and can be seen with 'show route protocol static hidden', but it is not placed in the forwarding table. This is the exact reason the route appears as hidden.
- ✗
The static route has not been committed
Why it's wrong here
An uncommitted static route exists only in the candidate configuration and has not been activated in the routing engine. Since the routing table only reflects committed configuration, such a route would be entirely absent from the routing table—it would not show as hidden or appear in any show route output. The fact that the route appears at all (even as hidden) proves it was committed and is being evaluated by the routing protocols process.
- ✗
The static route is a discard route
Why it's wrong here
A discard static route uses the 'discard' next-hop type, which is a valid, always-resolvable next hop that instructs the router to silently drop matching packets. In the routing table, this route is displayed with the 'discard' flag, indicating an active route that discards traffic. It is not a hidden state; hidden routes are unresolved and never become active, so a discard route would never be described as hidden.
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.