In Huawei system, the prefix list (ip ip-prefix) can be called by which of the following tools? (Multiple choice)

Question

Options

• ARouting policy (route-policy)
• BPolicy routing (policy-based-route)
• CFilter-Policy
• DTraffic-Policy
• EAS-Path filter

• A
  78% (28)
• D
  8% (3)
• E
  14% (5)

Explanation

In Huawei's VRP system, an ip ip-prefix list is a route-matching tool, so it can be referenced by any mechanism that needs to match IP prefixes to make routing decisions. Route-policy (A) uses if-match ip-prefix to conditionally apply route attributes; Policy-based-route (B) uses if-match ip-prefix to steer traffic to specific next-hops based on destination/source prefixes; and Filter-policy (C) directly references a prefix list to permit or deny routes during import/export filtering - all three operate in the routing plane where prefix matching is native.

Traffic-Policy (D) is wrong because it is a QoS/MQC tool that classifies traffic flows using ACLs, DSCP markings, or protocol types - not routing prefixes - so it has no mechanism to call an ip ip-prefix list. AS-Path filter (E) is wrong because it is a completely separate filtering object (ip as-path-filter) that matches BGP routes by their AS-path attribute using regular expressions, not by IP prefix - it is a peer of the prefix list, not a caller of it.

Memory tip: Ask yourself, "Does this tool make a routing decision based on an IP network address?" If yes (route-policy, filter-policy, PBR) → it can call a prefix list. If it matches QoS markings (Traffic-Policy) or BGP path attributes (AS-path filter) → it cannot.

No community discussion yet for this question.