An administrator notices that users trying to access https://mycitrix.training.lab/exchange2016/owa are redirected to CAS_vserver_www instead of CAS_vserver_owa. Which configuration change resolves the issue?

• A. Unbind cs vserver CAS_vserver_cs -lbvserver CAS_vserver_www
• B. Bind cs vserver CAS_vserver_cs -policyName CAS_policy_cs_owa -priority 120
• C. Bind cs vserver CAS_vserver_cs -policyName CAS_policy_cs_owa -priority 80
• D. Add cs policy CAS_policy_cs_owa -rule "HTTP.REQ.URL.SET_TEXT_MODE(IGNORECASE).CONTAINS(\"/owa\")" -action CAS_action_cs_owa

Answer: (D)

Traffic routing in a Citrix ADC content-switching setup works by evaluating policies that inspect the URL and forward the request to the appropriate vserver. To fix the redirection of OWA requests to the WWW vserver, you need a rule that explicitly identifies the OWA path and sends those requests to the OWA vserver.

Adding a content-switching policy that matches the OWA URL and directs it to the OWA vserver does exactly that. The rule uses HTTP.REQ.URL.SET_TEXT_MODE(IGNORECASE).CONTAINS("/owa") so it catches the OWA path regardless of case, such as /owa or /OWA, and the action CAS_action_cs_owa forwards the request to CAS_vserver_owa. Because the CS vserver evaluates policies in order of priority, this dedicated policy ensures requests for /owa are routed to the correct backend rather than being handled by the WWW vserver.

Unbinding or adjusting static bindings without a targeted URL match could disrupt other traffic or fail to guarantee that only OWA requests go to the OWA vserver. The direct URL-based policy creates a precise, reliable route for OWA traffic.