An administrator wants to create a policy to add a traffic policer called "policer-ccnp" to police data traffic on the WAN Edge. Which configuration accomplishes this task in vSmart?

Question

Exhibit

Options

• Avpn 1 interface ge 0/4 policer policer-ccnp in
• Bpolicy data-policy policy-ccnp vpn-list list-ccnp sequence number action accept set policer policer-ccnp
• Cpolicy access-list list-ccnp sequence number action accept policer policer-ccnp
• Dvpn 1 interface ge 0/4 policer policer-ccnp out

• A
  7% (2)
• B
  75% (21)
• C
  14% (4)
• D
  4% (1)

Explanation

In Cisco SD-WAN, centralized data policies are defined on the vSmart controller and pushed to WAN Edge devices. A traffic policer is applied within a data-policy using the 'set policer' action inside a sequence's accept action. Option B correctly follows this hierarchy: policy > data-policy > vpn-list > sequence > action accept > set policer policer-ccnp. Options A and D show interface-level policer configuration (e.g., 'policer policer-ccnp in/out' under an interface), which is a localized configuration done directly on the WAN Edge - not a vSmart-centralized policy. Option C incorrectly uses 'access-list', which is used for control-plane filtering (e.g., route filtering), not for applying data-plane traffic policing. Only a data-policy with 'set policer' achieves centralized traffic policing from vSmart.

No community discussion yet for this question.