Which policy and action combination would ensure that a request to http://xenapp.citrix.com on a load-balanced virtual server is sent to Service_1?

Which policy and action combination would ensure that a request to http://xenapp.citrix.com on a load-balanced virtual server is sent to Service_1?

• A. add filter action Redirect_Service_1_Act redirect Service_1 add filter policy Redirect_Service_1_Pol -rule REQ.HTTP.HEADER HOSTANME CONTAINS xenapp.citrix.com reqAction Redirect_Service_1_Act
• B. add filter action Redirect_Service_1_Act forward Service_1 add filter policy Redirect_Service_1_Pol -rule REQ.HTTP.HEADER HOSTANME CONTAINS xenapp.citrix.com reqAction Redirect_Service_1_Act
• C. add filter action Redirect_Service_1_Act forward Service_1 add filter policy Redirect_Service_1_Pol -rule REQ.HTTP.HEADER HOSTANME CONTAINS xenapp.citrix.com
• D. add filter action Redir

Answer: (B)

Routing decisions on a load-balancing virtual server are made by pairing a match policy with an action. To ensure a request for xenapp.citrix.com goes to Service_1, you need a policy that checks the HTTP Host header for xenapp.citrix.com and an action that forwards the request to Service_1. In the correct setup, the filter action is defined to forward to Service_1, and the filter policy ties the Host header rule (host contains xenapp.citrix.com) to that action. When a request arrives for xenapp.citrix.com, it matches the policy and is forwarded to Service_1, achieving the intended routing without instructing the client to navigate elsewhere. Using a redirect action would cause the client to issue a new request to a different URL, which isn’t suitable for internal service routing. The other options either lack the necessary action linkage or are incomplete, so they wouldn’t reliably route to Service_1.

Routing decisions on a load-balancing virtual server are made by pairing a match policy with an action. To ensure a request for xenapp.citrix.com goes to Service_1, you need a policy that checks the HTTP Host header for xenapp.citrix.com and an action that forwards the request to Service_1. In the correct setup, the filter action is defined to forward to Service_1, and the filter policy ties the Host header rule (host contains xenapp.citrix.com) to that action. When a request arrives for xenapp.citrix.com, it matches the policy and is forwarded to Service_1, achieving the intended routing without instructing the client to navigate elsewhere.

Using a redirect action would cause the client to issue a new request to a different URL, which isn’t suitable for internal service routing. The other options either lack the necessary action linkage or are incomplete, so they wouldn’t reliably route to Service_1.