A customer would like to ensure that the traffic towards the Partner Gateway does not exceed a certain bandwidth. Which feature should be used?

Question

Options

• AModify the SD WAN Traffic Class and Weight Mapping
• BEnable the SD-WAN Overlay Rate-Limit.
• CChange the application priority to low.
• DEnable the rate limit under a new custom Business Policy Rule.

• A
  5% (2)
• B
  13% (5)
• C
  80% (32)
• D
  3% (1)

Explanation

Changing the application priority to low triggers the SD-WAN platform to apply bandwidth throttling for that traffic toward the Partner Gateway, effectively capping throughput at a controlled rate rather than just deprioritizing it in a queue.

Why the distractors are wrong:

• A (Traffic Class and Weight Mapping): This adjusts how bandwidth is distributed proportionally among traffic classes, but does not enforce a hard ceiling on traffic sent to a specific gateway.
• B (SD-WAN Overlay Rate-Limit): This controls the aggregate overlay tunnel bandwidth more broadly and is not the targeted mechanism for Partner Gateway-specific bandwidth enforcement.
• D (Business Policy Rate Limit): Business Policy Rules manage application routing and SLA-based decisions; a rate limit here applies to flow behavior generally, not specifically to cap bandwidth toward a Partner Gateway.

Memory tip: Think "low priority = low bandwidth allowance." When you want the Partner Gateway to receive no more than a set amount of traffic, you're throttling it down - and setting application priority to low is the mechanism that enforces that ceiling in this context. Associate "Partner Gateway bandwidth cap" with "pull the priority lever down."

No community discussion yet for this question.