Scenario: A Citrix Administrator configured a responder policy as follows: > add responder action Redirect_Act respondwith…

The configuration creates a responder policy that inspects incoming DIAMETER requests. The policy rule, diameter.req.avp(264).value.eq(\”host1.example.net\”), specifically targets the DIAMETER request (diameter.req) and checks if the Attribute-Value Pair (AVP) with code 264 (Origin-Host) has a value of host1.example.net.

If this condition is true, the associated action, RedirectAct, is executed. This action uses the DIAMETER.NEWREDIRECT function to generate and send a redirect response to the client. The redirect target is specified as aaa://host.example.com. Since the policy is bound to the virtual server with –type REQUEST, it evaluates client requests as they arrive.

B. The policy is bound with –type REQUEST and the expression uses diameter.req, meaning it evaluates incoming requests, not outgoing responses.

C. This is incorrect as the policy evaluates requests, not responses, and it incorrectly swaps the origin and destination hosts from the configuration.

D. The responder action explicitly defines the redirect target as host.example.com, not host1.example.com.

1. Citrix ADC 14.1 Product Documentation

"AppExpert > Policies and Expressions > Advanced policy expressions reference > DIAMETER expressions". This document confirms that DIAMETER.REQ.AVP() is used to extract an AVP from a DIAMETER request

and AVP code 264 corresponds to the Origin-Host AVP.

2. Citrix ADC 14.1 Product Documentation

"AppExpert > Responder > Responder actions". This section details the respondwith action and its use with expressions. It specifies that DIAMETER.NEWREDIRECT(redirect-url) creates a DIAMETER redirect response with the specified URL.

3. Citrix ADC 14.1 Product Documentation

"AppExpert > Responder > Responder policies". This documentation explains that binding a policy with –type REQUEST causes the Citrix ADC to evaluate the policy during request processing.