In a Responder policy that redirects requests with a specific Diameter AVP value to a new host, what will happen to a request originated from host1.example.net?

In a Responder policy that redirects requests with a specific Diameter AVP value to a new host, what will happen to a request originated from host1.example.net?

• A. Response originated from host1.example.net will be redirected to host.example.com
• B. Request originated from host1.example.net will be redirected to host.example.net
• C. Response originated from host1.example.net will be redirected to host.example.com
• D. Request originated from host1.example.net will be redirected to host.example.com

Answer: (D)

The core idea is that a Responder policy can intercept incoming requests and, based on a matching Diameter AVP value, redirect the client to another host. When the AVP value matches, the policy issues a redirect for the original request rather than altering a response after it’s generated. So a request that originates from host1.example.net will be redirected to the configured new host, host.example.com. This is about directing the request flow to the new destination, not about changing what the responding server sends back.

The core idea is that a Responder policy can intercept incoming requests and, based on a matching Diameter AVP value, redirect the client to another host. When the AVP value matches, the policy issues a redirect for the original request rather than altering a response after it’s generated. So a request that originates from host1.example.net will be redirected to the configured new host, host.example.com. This is about directing the request flow to the new destination, not about changing what the responding server sends back.