What is the primary role of a Subnet IP (SNIP) in Citrix ADC deployments?

What is the primary role of a Subnet IP (SNIP) in Citrix ADC deployments?

• A. Source traffic for proxy
• B. Bind to VIP for SSL offload
• C. Serve as DNS resolver
• D. Not used

Answer: (B)

Subnet IP provides the source address that the Citrix ADC uses when it originates connections to resources on that subnet. When a client connects to a VIP and the ADC forwards the request to backend servers, the outbound traffic from the ADC appears with the SNIP as the source IP. Responses come back to the SNIP and are then delivered to the client via the VIP. This is why SNIPs must be on the same subnet as the servers they reach, and you often configure multiple SNIPs for different subnets or for redundancy. SSL offload is performed at the VIP, not via the SNIP, so the SNIP isn’t bound to the VIP for that purpose. While the ADC can act as a DNS resolver, that’s not the SNIP’s primary role; the SNIP’s main job is to source outbound traffic to backend resources.

Subnet IP provides the source address that the Citrix ADC uses when it originates connections to resources on that subnet. When a client connects to a VIP and the ADC forwards the request to backend servers, the outbound traffic from the ADC appears with the SNIP as the source IP. Responses come back to the SNIP and are then delivered to the client via the VIP. This is why SNIPs must be on the same subnet as the servers they reach, and you often configure multiple SNIPs for different subnets or for redundancy. SSL offload is performed at the VIP, not via the SNIP, so the SNIP isn’t bound to the VIP for that purpose. While the ADC can act as a DNS resolver, that’s not the SNIP’s primary role; the SNIP’s main job is to source outbound traffic to backend resources.