nerdexam
Cisco

352-001 · Question #494

Refer to the exhibit. You are a network designer for AS65100, which buys transit from AS65200 and AS65300. AS65200 and AS65300 have a peering relationship and they both implement RFC1998. You must…

The correct answer is A. Set the MED to be lower for less preferred prefixes. E. AS-path prepending for less preferred prefixes. MED and AS-path prepending are provider-independent, standards-based BGP mechanisms that influence inbound traffic to specific border routers and automatically adapt when a BGP session fails via route withdrawal.

Layer 3 Control Plane

Question

Refer to the exhibit. You are a network designer for AS65100, which buys transit from AS65200 and AS65300. AS65200 and AS65300 have a peering relationship and they both implement RFC1998. You must design a BGP policy that ensures that inbound traffic always arrives at AS65100's closest BGP router to the destination. For high availability and operational simplicity, there should be no manual intervention if a BGP relationship fails. Which two policies achieve this goal? (Choose 2)

Options

  • ASet the MED to be lower for less preferred prefixes.
  • BSet communities that influence the local preference of the transit provider.
  • CBGP remote trigger black hole for less preferred prefixes.
  • DSelective route advertisement.
  • EAS-path prepending for less preferred prefixes.

How the community answered

(63 responses)
  • A
    65% (41)
  • B
    5% (3)
  • C
    22% (14)
  • D
    8% (5)

Why each option

MED and AS-path prepending are provider-independent, standards-based BGP mechanisms that influence inbound traffic to specific border routers and automatically adapt when a BGP session fails via route withdrawal.

ASet the MED to be lower for less preferred prefixes.Correct

MED (Multi-Exit Discriminator) allows AS65100 to advertise the same prefix through multiple border routers with different MED values - a lower MED signals to the transit provider that the corresponding entry point is preferred, steering inbound traffic to the closest border router without any manual reconfiguration if a session fails.

BSet communities that influence the local preference of the transit provider.

Although RFC1998 communities influence a transit provider's local preference, this method depends on provider-specific community support and does not directly guarantee hot-potato routing to the closest AS65100 border router in a deterministic way across both transit providers.

CBGP remote trigger black hole for less preferred prefixes.

BGP remote trigger black hole is a technique for null-routing unwanted traffic by signaling a discard route, not a mechanism for steering inbound traffic to a specific preferred border router.

DSelective route advertisement.

Selective route advertisement can change which prefixes are reachable via a given path but does not reliably enforce closest-router entry for all prefixes and may require manual updates when topology changes occur.

EAS-path prepending for less preferred prefixes.Correct

AS-path prepending on routes advertised through less preferred border routers artificially lengthens the AS path, causing transit providers to select the shorter-path route through the preferred (closest) entry point; since route withdrawal is automatic upon BGP session failure, this mechanism requires no manual intervention to maintain correct traffic flow.

Concept tested: BGP inbound traffic engineering using MED and AS-path prepending

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

Topics

#BGP#MED#AS-path prepending#inbound traffic engineering

Community Discussion

No community discussion yet for this question.

Full 352-001 Practice