To accommodate increased traffic on a single SDX instance that has a 2 GB dedicated bandwidth per instance, which action is recommended?

• A. Purchase an SDX license to increase the bandwidth on the instances.
• B. Configure burst capacity on the instance adding 1 GB of bandwidth with burst priority 0.
• C. Configure LA channel to increase the bandwidth.
• D. Configure burst capacity of 1 GB with priority 10.

Answer: (B)

The scenario is about handling traffic spikes beyond the fixed two-gig bandwidth on an SDX instance. SDX supports burst capacity, which lets a single instance borrow extra bandwidth temporarily when demand rises, without changing the base license or reconfiguring overall topology. Adding 1 GB of burst capacity gives immediate headroom for bursts.

Burst priority determines which requests get the extra bandwidth when multiple entities compete for the burst pool. A lower value means higher priority, so assigning the highest-priority burst to this instance ensures it gets the extra bandwidth first during congestion. This is exactly what you want when a single instance experiences increased traffic, because the burst will be allocated preferentially.

Purchasing an SDX license would involve a broader licensing change and isn’t the targeted solution for a temporary spike. Using a link aggregation channel isn’t about increasing burstable capacity; it’s about combining physical links, which doesn’t address the need for temporary burst resources in this scenario. A higher burst priority would reduce the chances of obtaining the burst during contention, which defeats the goal of ensuring sufficient headroom during traffic surges.