A ZIA Sublocation is a logical construct used to segment traffic within a broader, defined Location. It is defined by specific IP address ranges or subnets that are part of the parent Location's network. This allows an organization to apply distinct security policies, such as URL Filtering or Cloud App Control, to different groups of users or network segments that share the same internet egress point. A primary example is creating a sublocation for a guest Wi-Fi network to enforce stricter policies compared to the corporate network, even though both traffic types exit through the same gateway.

B: A Sublocation's purpose is for policy enforcement and is not defined by its relationship to a Zscaler Subcloud, which is an element of Zscaler's cloud architecture.

C: Sublocations are defined by distinct, non-overlapping IP subnets within a location to differentiate traffic, not to manage or identify overlapping IP addresses.

D: A sublocation is defined by an IP address or subnet, which is independent of the traffic forwarding method, such as Zscaler Client Connector versus a GRE tunnel.

1. Zscaler Help Portal

"About Sublocations": "You can create sub-locations for a location to apply different policies to different subnets within the location... A common use case is to create a sub-location for your guest Wi-Fi network. This allows you to apply a stricter policy to your guest Wi-Fi network." This source directly validates that sublocations are for segmenting traffic (like guest vs. employee) for policy application.

2. Zscaler Help Portal

"Configuring Locations": Under the "Sub-Locations" section

the documentation states

"Sub-locations are prefixes of the static IP addresses that are configured for the location. You can define sub-locations to apply policies on a more granular level." This confirms that sublocations are IP-based subsets of a location used for granular policy.