nerdexam
Cisco

352-001 · Question #94

Which two resources are propagated by the headend router for constrained based path computation with MPLS Traffic Engineering? (Choose two.)

The correct answer is C. link bandwidth D. link affinity. MPLS TE constrained-based path computation (CSPF) at the headend uses link bandwidth and link affinity attributes flooded via OSPF-TE or IS-IS-TE extensions to select a valid path.

Layer 3 Control Plane

Question

Which two resources are propagated by the headend router for constrained based path computation with MPLS Traffic Engineering? (Choose two.)

Options

  • Aaverage link utilization
  • Baverage input queue depth
  • Clink bandwidth
  • Dlink affinity
  • Elink delay
  • Flink jitter

How the community answered

(32 responses)
  • A
    13% (4)
  • B
    3% (1)
  • C
    75% (24)
  • F
    9% (3)

Why each option

MPLS TE constrained-based path computation (CSPF) at the headend uses link bandwidth and link affinity attributes flooded via OSPF-TE or IS-IS-TE extensions to select a valid path.

Aaverage link utilization

Average link utilization is not a standard attribute in the MPLS TE link attribute set - TE extensions advertise reservable and unreserved bandwidth values, not real-time utilization averages.

Baverage input queue depth

Average input queue depth is an operational queue metric and is not part of the MPLS TE link attribute set propagated via OSPF-TE or IS-IS-TE.

Clink bandwidthCorrect

Link bandwidth - specifically maximum bandwidth, maximum reservable bandwidth, and unreserved bandwidth per priority level - is flooded via IGP TE opaque LSAs so the headend CSPF engine can verify which links can accommodate the tunnel's requested bandwidth.

Dlink affinityCorrect

Link affinity (administrative groups or link colors) is a TE attribute flooded with IGP TE extensions, allowing the CSPF algorithm to include or exclude links based on affinity constraints configured on the TE tunnel.

Elink delay

Link delay is not a standard CSPF constraint in traditional MPLS TE deployments - RFC 7471 defines delay measurement extensions, but delay is not part of the core headend CSPF resource set.

Flink jitter

Link jitter is not a standard MPLS TE link attribute and is not propagated for constrained-based path computation in traditional TE implementations.

Concept tested: MPLS TE CSPF link attribute propagation

Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/mp_te_path_control/configuration/xe-16/mp-te-path-control-xe-16-book/mp-te-over.html

Topics

#MPLS TE#constrained path computation#link affinity#link bandwidth

Community Discussion

No community discussion yet for this question.

Full 352-001 Practice