In an SDX with four VPX instances, a 10 GB license with 2 GB dedicated per instance; three instances do not reach the limit, but one requires 1 GB more. What change should be made to the instance to meet traffic requirements?

In an SDX with four VPX instances, a 10 GB license with 2 GB dedicated per instance; three instances do not reach the limit, but one requires 1 GB more. What change should be made to the instance to meet traffic requirements?

• 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)

Burst capacity lets a VPX on an SDX use extra bandwidth beyond its fixed 2 GB per-instance allotment during traffic spikes. To meet the one instance’s need for an additional 1 GB, you assign 1 GB of burst capacity to that specific VPX and give it the highest burst priority (lowest numeric value, such as 0). With the top priority, this VPX can draw the full extra 1 GB when demand rises, while the other VPXs stay within their 2 GB base unless they also need bursts. Choosing a lower priority (for example, 10) would mean the instance gets the burst bandwidth only after others with higher priority have used theirs, so it wouldn’t reliably meet the 1 GB requirement. Not increasing the license is appropriate here because burst capacity provides the needed headroom without upgrading licensing, and other options like LA channels don’t address per-VPX burst needs in this scenario.

Burst capacity lets a VPX on an SDX use extra bandwidth beyond its fixed 2 GB per-instance allotment during traffic spikes. To meet the one instance’s need for an additional 1 GB, you assign 1 GB of burst capacity to that specific VPX and give it the highest burst priority (lowest numeric value, such as 0). With the top priority, this VPX can draw the full extra 1 GB when demand rises, while the other VPXs stay within their 2 GB base unless they also need bursts.

Choosing a lower priority (for example, 10) would mean the instance gets the burst bandwidth only after others with higher priority have used theirs, so it wouldn’t reliably meet the 1 GB requirement. Not increasing the license is appropriate here because burst capacity provides the needed headroom without upgrading licensing, and other options like LA channels don’t address per-VPX burst needs in this scenario.