Scenario: A Citrix Administrator configured a responder policy as follows: > add responder action Redirect_Act respondwith "DIAMETER.NEW_REDIRECT(\"aaa://host.example.com\")" > add responder action…

Question

Options

• AResponse originated from "host1.example.net" will be redirected to "host.example.com".
• BResponse originated from "host.example.net" will be redirected to "host1.example.com".
• CRequest originated from "host.example.net" will be redirected to "host1.example.com".
• DRequest originated from "host1.example.net" will be redirected to "host.example.com".

• A
  24% (5)
• B
  5% (1)
• C
  14% (3)
• D
  57% (12)

Explanation

Option D is correct because the policy condition checks diameter.req.avp(264).value.eq("host1.example.net") - AVP 264 is the DIAMETER Origin-Host attribute, identifying where the request originated - and the action redirects that traffic to aaa://host.example.com. The binding uses -type REQUEST, confirming this applies to inbound requests, not responses.

Why the distractors fail:

• A & B say "Response originated from..." but the policy is bound with -type REQUEST, so it only intercepts requests, never responses.
• C flips the hostnames - the origin in the rule is host1.example.net (with the "1"), and the redirect destination is host.example.com (no "1"); C inverts both.
• B also uses the wrong redirect destination (host1.example.com instead of host.example.com).

Memory tip: In DIAMETER, AVP 264 = Origin-Host (think "264 = who sent it"). Read the policy rule left-to-right: "if Origin-Host equals host1.example.net → redirect to host.example.com." The -type REQUEST binding is the dead giveaway that eliminates any "Response" answer immediately.

No community discussion yet for this question.