What will be the effect of binding a responder policy to a vserver that uses a RESET action and targets specific source IPs?

What will be the effect of binding a responder policy to a vserver that uses a RESET action and targets specific source IPs?

• A. All the traffic from users with a source IP address of 192.168.149.10,192.168.149.39, or 192.168.149.49 will be blocked through the NetScaler.
• B. Only the users with a source IP address of 192.168.149.10,192.168.149.39, or 192.168.149.49 will be allowed to connect to vserver lb_vsrv_www.
• C. Only the users with a source IP address of 192.168.149.10,192.168.149.39, or 192.168.149.49 will be blocked.
• D. All the traffic will be allowed

Answer: (B)

Responder policies bound to a vserver with a RESET action terminate the TCP connection for any request that matches the policy. When the policy targets specific source IPs, only traffic from those addresses is affected. So, for those particular users, the NetScaler will send a reset and close the session, effectively blocking their access to the vserver. Other users whose source IPs aren’t in the targeted list will continue to connect normally. This is a TCP-layer block rather than an HTTP-level denial, and it does not block all traffic or allow only those users to connect.

Responder policies bound to a vserver with a RESET action terminate the TCP connection for any request that matches the policy. When the policy targets specific source IPs, only traffic from those addresses is affected. So, for those particular users, the NetScaler will send a reset and close the session, effectively blocking their access to the vserver. Other users whose source IPs aren’t in the targeted list will continue to connect normally. This is a TCP-layer block rather than an HTTP-level denial, and it does not block all traffic or allow only those users to connect.