FortiWeb is blocking groups of users behind your load balancer. In the logs, all users show the same source IP address.Which action should you take to restore proper client identification?
Answer(s): D
When traffic passes through a load balancer, FortiWeb may see only the load balancer IP as the source. Inserting the original client IP address in an HTTP header, such as X-Forwarded-For, allows FortiWeb to identify individual clients correctly and avoid applying IP-based blocking to an entire group of users.
Your company hosts two different web applications: a shopping site and a blog. You want FortiWeb to apply different protection profiles and forwarding rules to each application.How should you configure FortiWeb to support this?
Separate server policies allow FortiWeb to match each web application independently and apply its own protection profile, virtual server settings, server pool, and forwarding behavior. This is the correct approach when different applications require different security and routing requirements.
A FortiWeb administrator needs to allow a known web indexer to scan the website for search engine visibility.What is the easiest way to allow this on FortiWeb?
Answer(s): C
Adding the known web indexer IP address to the trusted IP address list is the simplest way to allow its scanning activity. FortiWeb treats traffic from trusted IPs as allowed, preventing the indexer from being blocked by bot, rate, or other protection controls during legitimate crawling.
Which action must a FortiWeb administrator take to enable FortiAppSec Cloud Advanced Bot Protection (ABP) service in a cloud deployment?
Answer(s): B
FortiAppSec Cloud Advanced Bot Protection is enabled by activating the ABP feature in FortiWeb and associating it with the FortiAppSec Cloud Application ID. This links the FortiWeb deployment to the cloud-based bot protection service so it can analyze and enforce advanced bot detection for the protected application.
Refer to the exhibit.Users complain that parts of the finances.fortinet.demo page fail to load. You see repeated 500 errors for view.js, view.css and favicon.ico.What is the most likely cause?
The page loads the main document successfully, but multiple required subresources fail immediately afterward. This pattern is consistent with FortiWeb rate limiting being set too aggressively, causing normal browser requests for page components such as JavaScript, CSS, and favicon files to be rejected before the full page can render properly.
Post your Comments and Discuss Fortinet NSE5_FWB_AD-8.0 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the NSE5_FWB_AD-8.0 content, but please register or login to continue.