How should the administrator rectify the Responder policy to redirect the root page to the home page without causing a loop?

How should the administrator rectify the Responder policy to redirect the root page to the home page without causing a loop?

• A. Change Responder Policy expression to http.REQ.URL.Contains("/")
• B. Change Responder Policy expression to http.REQ.URL.EQ("/")
• C. Change Responder action expression to "/"
• D. Change Responder Action expression to http.REQ.URL

Answer: (B)

In Responder policies, you control when a redirect happens by evaluating a policy expression against the incoming request. To move the root page to the home page without looping, you want the trigger to fire only when the request is exactly for the root path. The correct approach is to use an expression that checks the URL against a precise match: http.REQ.URL.EQ("/"). This means the redirect executes only when the requested URL is exactly "/", so once the user is redirected to the home page (for example "/home"), the root condition isn’t met anymore and the policy won’t trigger again, preventing a loop. Why the other options aren’t suitable: using a contains check would match many URLs (essentially any path with a slash), causing the redirect to apply more broadly and likely loop back when the home page is requested. Redirecting to "/" would send the user back to the root, creating an immediate loop. Redirecting to http.REQ.URL would direct the user to the URL they requested, which doesn’t accomplish a redirect to the home page and can loop or behave unpredictably.

In Responder policies, you control when a redirect happens by evaluating a policy expression against the incoming request. To move the root page to the home page without looping, you want the trigger to fire only when the request is exactly for the root path. The correct approach is to use an expression that checks the URL against a precise match: http.REQ.URL.EQ("/"). This means the redirect executes only when the requested URL is exactly "/", so once the user is redirected to the home page (for example "/home"), the root condition isn’t met anymore and the policy won’t trigger again, preventing a loop.

Why the other options aren’t suitable: using a contains check would match many URLs (essentially any path with a slash), causing the redirect to apply more broadly and likely loop back when the home page is requested. Redirecting to "/" would send the user back to the root, creating an immediate loop. Redirecting to http.REQ.URL would direct the user to the URL they requested, which doesn’t accomplish a redirect to the home page and can loop or behave unpredictably.