The prefix list can be used directly through the peer command in deploying BGP without passing Filter-Policy or Route-Policy.

Question

Options

• ATRUE
• BFALSE

• A
  82% (50)
• B
  18% (11)

Explanation

Option A is correct because, in BGP (particularly on platforms like Huawei VRP), the peer command supports a direct ip-prefix parameter that lets you attach a prefix list to a specific peer for inbound or outbound filtering - for example, peer <ip> ip-prefix <name> import/export - without needing to wrap it inside a Route-Policy or Filter-Policy first. This makes prefix lists a first-class filtering tool at the peer level, useful for straightforward permit/deny filtering based on network prefixes. Option B is wrong because it falsely implies that prefix lists are only accessible as indirect references inside Route-Policy or Filter-Policy constructs; that is true for more complex conditional logic, but not for simple prefix-based filtering on a peer. Memory tip: Think of it as a shortcut - if you only need to filter by prefix (no attribute manipulation), BGP's peer command lets you "skip the middleman" (Route-Policy/Filter-Policy) and attach the prefix list directly.

No community discussion yet for this question.