- A
There is no route on the neighbor back to the FortiGate's loopback IP
BGP uses TCP; if the neighbor cannot reach the update-source IP, the TCP handshake fails, keeping the session in Idle.
- B
The loopback interface is down or has no IP address assigned
Why wrong: If the loopback is down, the update-source would fail, but the BGP session might show Idle; however, ping to neighbor works, so local loopback is likely up.
- C
The BGP neighbor's remote-as is misconfigured
Why wrong: Misconfigured remote-as usually leads to Active state, not Idle.
- D
The BGP timer values (keepalive/hold) are mismatched
Why wrong: Timer mismatch typically causes session flapping, not persistent Idle.
Quick Answer
The answer is that there is no route on the neighbor back to the FortiGate's loopback IP. This is the most likely reason for the BGP Idle state because when you configure an update-source loopback1, the FortiGate uses that loopback address as the source IP for the TCP connection. Even if the neighbor IP is reachable via ping, the neighbor must have a route back to that specific loopback IP; otherwise, the TCP handshake fails, keeping the session stuck in Idle. On the Fortinet NSE 7 Advanced Security NSE7 exam, this scenario tests your understanding of BGP peering prerequisites—specifically that reachability is not enough; the source and destination IPs must be mutually routable. A common trap is assuming a successful ping to the neighbor’s interface IP means the session should work, but the loopback update-source changes the source address, and the neighbor must have a route to it. Remember the memory tip: “Ping the loopback, not just the link.”
NSE7 Advanced Networking and SD-WAN Practice Question
This NSE7 practice question tests your understanding of advanced networking and sd-wan. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
An administrator runs 'get router info bgp summary' and sees that the BGP session to a neighbor is in the 'Idle' state. The neighbor IP is reachable via ping. The BGP configuration uses loopback interfaces with 'update-source loopback1'. What is the MOST likely reason for the Idle state?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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
There is no route on the neighbor back to the FortiGate's loopback IP
BGP Idle state often indicates a TCP connection issue. If the update source is a loopback, the neighbor must have a route to that loopback IP, or the update-source must match the neighbor's configured remote-as and reachability.
Key principle: OSPF neighbour adjacency depends on matching area, hello/dead timers, network type, and authentication — IP reachability alone is not enough.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
There is no route on the neighbor back to the FortiGate's loopback IP
- ✗
The loopback interface is down or has no IP address assigned
Why it's wrong here
If the loopback is down, the update-source would fail, but the BGP session might show Idle; however, ping to neighbor works, so local loopback is likely up.
- ✗
The BGP neighbor's remote-as is misconfigured
Why it's wrong here
Misconfigured remote-as usually leads to Active state, not Idle.
- ✗
The BGP timer values (keepalive/hold) are mismatched
Why it's wrong here
Timer mismatch typically causes session flapping, not persistent Idle.
Common exam traps
Common exam trap: OSPF can fail even when IP connectivity looks correct
OSPF neighbour formation depends on matching areas, timers, network type, authentication and passive-interface behaviour. Do not choose an answer only because the devices can ping.
Trap categories for this question
Command / output trap
If the loopback is down, the update-source would fail, but the BGP session might show Idle; however, ping to neighbor works, so local loopback is likely up.
Detailed technical explanation
How to think about this question
OSPF questions usually test the details that control adjacency and route selection. Read the neighbour state, area, router ID and interface configuration before deciding what is wrong.
KKey Concepts to Remember
- OSPF neighbours must agree on key parameters.
- Router ID selection can affect neighbour relationships and LSDB output.
- OSPF cost influences the preferred path.
- A route can appear in OSPF information but not become the installed route.
TExam Day Tips
- Check area mismatch first when OSPF adjacency fails.
- Review passive interfaces when a network is advertised but no neighbour forms.
- Use show ip ospf neighbor and show ip route clues carefully.
Key takeaway
OSPF neighbour adjacency depends on matching area, hello/dead timers, network type, and authentication — IP reachability alone is not enough.
Real-world example
How this comes up in practice
A network engineer at a university connects two campus buildings via a fibre link. Both routers run OSPF, but no adjacency forms — even though both routers can ping each other. The engineer finds one router is in area 0 and the other in area 1. OSPF adjacency requires matching area numbers, hello/dead timers, and network type. IP reachability alone is not enough.
What to study next
Got this wrong? Here's your next step.
Review OSPF neighbour requirements — matching area type, hello and dead timers, network type, stub flags, and authentication. Study show ip ospf neighbor states (INIT, 2-WAY, FULL). Then practise related NSE7 OSPF questions on adjacency and route selection.
- →
Advanced Networking and SD-WAN — study guide chapter
Learn the concepts, then practise the questions
- →
Advanced Networking and SD-WAN practice questions
Targeted practice on this topic area only
- →
All NSE7 questions
1,000 questions across all exam domains
- →
Fortinet NSE 7 Advanced Security NSE7 study guide
Full concept coverage aligned to exam objectives
- →
NSE7 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related NSE7 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Advanced Networking and SD-WAN practice questions
Practise NSE7 questions linked to Advanced Networking and SD-WAN.
Advanced VPN and Zero Trust practice questions
Practise NSE7 questions linked to Advanced VPN and Zero Trust.
Enterprise Firewall and VDOMs practice questions
Practise NSE7 questions linked to Enterprise Firewall and VDOMs.
Advanced Threat Protection practice questions
Practise NSE7 questions linked to Advanced Threat Protection.
Troubleshooting and Diagnostics practice questions
Practise NSE7 questions linked to Troubleshooting and Diagnostics.
NSE7 fundamentals practice questions
Practise NSE7 questions linked to NSE7 fundamentals.
NSE7 scenario practice questions
Practise NSE7 questions linked to NSE7 scenario.
NSE7 troubleshooting practice questions
Practise NSE7 questions linked to NSE7 troubleshooting.
Practice this exam
Start a free NSE7 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this NSE7 question test?
Advanced Networking and SD-WAN — This question tests Advanced Networking and SD-WAN — OSPF neighbours must agree on key parameters..
What is the correct answer to this question?
The correct answer is: There is no route on the neighbor back to the FortiGate's loopback IP — BGP Idle state often indicates a TCP connection issue. If the update source is a loopback, the neighbor must have a route to that loopback IP, or the update-source must match the neighbor's configured remote-as and reachability.
What should I do if I get this NSE7 question wrong?
Review OSPF neighbour requirements — matching area type, hello and dead timers, network type, stub flags, and authentication. Study show ip ospf neighbor states (INIT, 2-WAY, FULL). Then practise related NSE7 OSPF questions on adjacency and route selection.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
OSPF neighbours must agree on key parameters.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 21, 2026
This NSE7 practice question is part of Courseiva's free Fortinet 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 NSE7 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.