Users attempting to access https://mycitrix.training.lab/exchange2016/owa are redirected to CAS_vserver_www instead of CAS_vserver_owa. What action should the administrator take to resolve the issue?

• A. Unbind cs vserver CAS_vserver_cs -Ibvserver CAS_vserver_www
• B. Bind cs vserver CAS_vserver_cs -policyName CAS_policy_cs_owa -priority 80
• 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)

In this scenario, routing decisions for incoming HTTPS requests are controlled by content-switching policies that examine the URL and send the request to the appropriate back-end vserver. The issue is that requests to the OWA path are being directed to the general web vserver instead of the Exchange OWA vserver. The precise fix is to create a content-switching policy that identifies the OWA URL path and forwards those requests to the OWA vserver.

The best action is to add a policy named CAS_policy_cs_owa with a rule that checks the URL for the OWA path, using HTTP.REQ.URL.SET_TEXT_MODE(IGNORECASE).CONTAINS(/owa) so the match is case-insensitive and robust for any /owa variant. The action CAS_action_cs_owa directs matched requests to the OWA vserver. Binding this policy to the content-switching vserver CAS_vserver_cs with the appropriate priority ensures that any request containing /owa is routed to CAS_vserver_owa rather than CAS_vserver_www, resolving the misrouting.

Unbinding or binding other policies without a proper URL match would not establish the necessary path-specific routing, and simply attaching an existing policy without the correct rule would fail to change the destination.