Question 88 of 500
MPLS and Segment RoutinghardMultiple ChoiceObjective-mapped

Quick Answer

The answer is to configure `label mode per-prefix` under the BGP neighbor or address-family. This is required because, by default, BGP-LU allocates labels on a per-next-hop basis, which means the label is shared across all prefixes using that next hop, preventing individual prefix installation into the LFIB. Setting `label mode per-prefix` forces BGP to allocate a unique label for each prefix, allowing the MPLS forwarding table to program the label-switched path for those BGP-LU routes. On the Cisco SPCOR 350-501 exam, this scenario tests your understanding of the interaction between BGP label allocation and MPLS forwarding—a common trap is assuming that a label in the BGP table guarantees LFIB installation, but without per-prefix mode or `mpls bgp forwarding`, the LFIB remains empty. Memory tip: "Per prefix, per path—without it, LFIB is a ghost."

350-501 MPLS and Segment Routing Practice Question

This 350-501 practice question tests your understanding of mpls and segment routing. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.

A network engineer notices that BGP-LU prefixes learned from an eBGP neighbor are not being installed in the MPLS forwarding table (LFIB). The BGP table shows the prefixes with the correct label. The IGP route to the neighbor is reachable. What additional configuration is needed?

Question 1hardmultiple choice
Open the full BGP breakdown →

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 `label mode per-prefix` under the BGP neighbor or address-family

For BGP-LU to install labels into LFIB, the `label mode` must be set to `per-prefix` or the router must have `mpls bgp forwarding` enabled. Without enabling label allocation per prefix, BGP-LU prefixes are not programmed in LFIB. The other options are not directly related.

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.

  • Enable `no bgp default ipv4-unicast`

    Why it's wrong here

    That command prevents IPv4 unicast from being advertised, not label installation.

  • Configure `mpls ldp autoconfig` on the interface

    Why it's wrong here

    LDP is not needed for BGP-LU labels.

  • Add `allowas-in` to accept routes with AS-path containing own AS

    Why it's wrong here

    allowas-in deals with AS-path loop prevention, not label installation.

  • Set `label mode per-prefix` under the BGP neighbor or address-family

    Why this is correct

    BGP-LU requires per-prefix label allocation for LFIB installation.

    Related concept

    OSPF neighbours must agree on key parameters.

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

    That command prevents IPv4 unicast from being advertised, not label installation.

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 350-501 OSPF questions on adjacency and route selection.

Related practice questions

Related 350-501 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free 350-501 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 350-501 question test?

MPLS and Segment Routing — This question tests MPLS and Segment Routing — OSPF neighbours must agree on key parameters..

What is the correct answer to this question?

The correct answer is: Set `label mode per-prefix` under the BGP neighbor or address-family — For BGP-LU to install labels into LFIB, the `label mode` must be set to `per-prefix` or the router must have `mpls bgp forwarding` enabled. Without enabling label allocation per prefix, BGP-LU prefixes are not programmed in LFIB. The other options are not directly related.

What should I do if I get this 350-501 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 350-501 OSPF questions on adjacency and route selection.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

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.

Loading comments…

Sign in to join the discussion.

This 350-501 practice question is part of Courseiva's free Cisco 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 350-501 exam.