nerdexam
Cisco

352-001 · Question #517

What are two possible drawbacks of ending Loop-Free Alternate to support fast convergence for most destination IGP prefixes? (Choose two)

The correct answer is A. The IGP topology might need to be adjust E. Additional path computations are needed. LFA (Loop-Free Alternate) drawbacks include topology dependency that may require IGP redesign to achieve full prefix coverage, and the extra SPF computations required to identify qualifying alternate next-hops.

Layer 3 Control Plane

Question

What are two possible drawbacks of ending Loop-Free Alternate to support fast convergence for most destination IGP prefixes? (Choose two)

Options

  • AThe IGP topology might need to be adjust
  • BLoop-free alternate's convergence in less than 100 milliseconds is not possible
  • CLoop-free alternate's are supported only for prefixes that are considered external tot the IGP
  • DLoop-free alternates are not supported in global VPN VRF OSPF instances
  • EAdditional path computations are needed

How the community answered

(41 responses)
  • A
    61% (25)
  • B
    5% (2)
  • C
    24% (10)
  • D
    10% (4)

Why each option

LFA (Loop-Free Alternate) drawbacks include topology dependency that may require IGP redesign to achieve full prefix coverage, and the extra SPF computations required to identify qualifying alternate next-hops.

AThe IGP topology might need to be adjustCorrect

LFA coverage is highly topology-dependent - not all IGP prefixes will have a qualifying loop-free alternate neighbor, so the network topology may require redesign (adding links or adjusting metrics) to achieve alternate-path coverage for most destinations.

BLoop-free alternate's convergence in less than 100 milliseconds is not possible

Sub-100ms convergence is a primary goal and achieved benefit of LFA, not a drawback - LFA is specifically designed to enable IP fast reroute in under 50ms upon failure detection.

CLoop-free alternate's are supported only for prefixes that are considered external tot the IGP

LFA supports both internal (intra-area, inter-area) and external IGP prefixes, not exclusively external ones - this statement is factually incorrect regarding LFA's scope.

DLoop-free alternates are not supported in global VPN VRF OSPF instances

LFA can be deployed within VRF OSPF instances; there is no architectural restriction preventing LFA from operating in VPN VRF routing contexts.

EAdditional path computations are neededCorrect

Computing LFAs requires additional SPF runs beyond the primary path calculation - specifically, the router must execute SPF from each neighbor's perspective to determine which neighbors qualify as loop-free alternates, increasing CPU and memory consumption.

Concept tested: Loop-Free Alternate fast reroute drawbacks and limitations

Source: https://www.rfc-editor.org/rfc/rfc5286

Topics

#Loop-Free Alternate#LFA#fast reroute#IGP convergence

Community Discussion

No community discussion yet for this question.

Full 352-001 Practice