ZScaler Bandwidth control

Question 1

What is the default behavior of ZScaler Bandwidth control?

Answer 1

By default, Zscaler utilizes all available bandwidth unless there’s a policy in place to manage the contention between applications, prioritizing full bandwidth utilization.

Question 2

How does ZScaler manage TCP connections for bandwidth control?

Answer 2

Zscaler manages TCP connections through TCP proxy, employing techniques like adjusting the TCP window size and buffering rather than dropping packets, ensuring smoother application performance.

Question 3

What distinguishes ZScaler’s bandwidth shaping from bandwidth policy?

Answer 3

Unlike bandwidth policing, which drops packets exceeding thresholds, Zscaler’s shaping uses buffers to manage excess traffic, preventing packet loss and maintaining user experience.

Question 4

How is Bandwidth Control initially set up in ZScaler?

Answer 4

Bandwidth Control is configured at each location by specifying upload and download speeds in megabits per second, reflecting the traffic expected to be handled by Zscaler.

Question 5

What are bandwidth classes in ZScaler’s Bandwidth control? There are 8 total.

Answer 5

Zscaler uses predefined and custom bandwidth classes to manage traffic types, such as file sharing or streaming, aligning bandwidth usage with business needs.

Question 6

How does ZScaler ensure optimal bandwidth usage for different applications?

Answer 6

Through bandwidth rules, Zscaler allows setting minimum and maximum bandwidth limits for applications, ensuring critical apps have guaranteed bandwidth while limiting less essential traffic.