JN0-106 Routing table Practice Question
Which two events typically trigger a change to the routing table? (Choose two.)
⚠ Common exam trap
Many candidates confuse a configuration commit (option E) with an automatic routing table change. A commit only activates the configuration; it does not directly modify the routing table unless the configuration itself triggers a protocol event or interface change.
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
✓
Interface state change
An interface state change (up/down) directly affects the reachability of directly connected networks. When an interface goes up, Junos adds the corresponding directly connected route to the routing table; when it goes down, the route is removed. Similarly, a BGP neighbor reset causes the BGP session to be torn down and re-established, which triggers the withdrawal and re-advertisement of all BGP routes, thereby modifying the routing table.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Interface state change
Why this is correct
An interface state change (up or down) is a primary trigger for routing table updates. When an interface transitions, the kernel notifies rpd, which immediately adds or removes the directly connected route for that subnet; this change in turn causes the routing table to recalculate and, if necessary, sends updated route information to dynamic routing protocols like OSPF or IS-IS.
- ✗
System uptime
Why it's wrong here
System uptime is a counter that tracks how long the routing engine has been running; it is a candidate metric in BGP route selection (preferring older routes) but does not, by itself, cause the routing table to be rebuilt or updated. Routing table changes are driven by topology events, protocol messages, or explicit administrative actions, not by the passage of time or system restarts.
- ✗
Log file rotation
Why it's wrong here
Log file rotation is a housekeeping task performed by the system to archive or truncate log files (e.g., /var/log/messages). It has no connection to the routing protocol daemon (rpd) or the routing table because it neither alters interface states, receives routing updates, nor modifies active configuration that affects network reachability.
- ✓
BGP neighbor reset
Why this is correct
Resetting a BGP neighbor—whether a hard reset or a soft reset—forces the BGP session to be torn down or refreshed. The neighbor withdraws all previously advertised routes and then re-advertises them (for a hard reset, via a full session re-establishment), causing the routing table to be emptied and repopulated with those BGP routes, often leading to brief route churn and traffic loss.
- ✗
Configuration commit
Why it's wrong here
A configuration commit only activates the candidate configuration into the active configuration. Unless that configuration change directly alters an interface address, enables or disables a routing protocol, or adds/removes a static route, committing it does not itself modify the existing routing table; the table changes only when the underlying protocol or interface state actually changes.
Go deeper
Related to this question
About these practice questions
Courseiva writes every JN0-106 question from scratch — 156 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.