When BGP uses Filter-Policy, you can use the filter-policy export command to filter the routes published externally. Only routes that pass the filtering can be added to the BGP local routing table…

Question

Options

• ATRUE
• BFALSE
• C
• D

• A
  6% (2)
• B
  75% (24)
• C
  16% (5)
• D
  3% (1)

Explanation

B is correct because the statement contains a critical inaccuracy: filter-policy export only controls which routes BGP advertises outbound to peers - it does not determine what gets added to the BGP local routing table. Routes that fail the export filter are simply not advertised; they remain in the local BGP routing table unchanged.

The statement incorrectly merges two distinct functions: populating the local BGP routing table (controlled by import policies like filter-policy import) and advertising routes to peers (controlled by filter-policy export). These are separate operations at separate stages of BGP processing.

Option A is wrong because it accepts the flawed premise that export filtering affects local route storage - it doesn't; export filtering is strictly an outbound advertisement gate.

Memory tip: Think of the BGP local table as a warehouse and filter-policy export as the loading dock gate - the gate controls what leaves the warehouse to customers (peers), but it has no say over what's stored on the shelves inside (local table). To control what enters the warehouse, you need an import policy.

No community discussion yet for this question.