Free Practice Questions for the Fortinet NSE 5 Network Security Analyst NSE5_FWB_AD-8.0 Exam (2026 Updated)

This is a stored cross-site scripting attack. The attacker submits JavaScript into a product review form, and the application stores and displays it later to other users. When victims view the review, their browsers execute the attacker’s script as if it came from the trusted site. That is dangerous because the script can access browser-side data available to the page, such as cookies, tokens, page content, or session-related information depending on browser and cookie security settings. It does not directly leak the back-end database; that would be more aligned with SQL injection. It also does not inherently bypass login pages or require the victim to click a link. The core risk is malicious code execution in the victim’s browser.

================

When FortiWeb is deployed behind a load balancer or upstream proxy, it may see only the load balancer IP address as the source for every request. This causes poor client identification and can lead FortiWeb to block many legitimate users as if they are one abusive client. The correct fix is to preserve the original client IP address in an HTTP header, commonly using X-Forwarded-For or a similar trusted client-IP header. FortiWeb can then be configured to read that header for accurate client identification, logging, rate limiting, and IP-based security decisions. Bot detection, signature updates, and HTTPS caching do not solve the core source-IP visibility problem.

================

The correct answers are C and D. FortiWeb uses its own built-in/self-signed or configured server certificate when an administrator connects to the FortiWeb GUI over HTTPS. FortiWeb can also authenticate as a client when it connects to protected back-end servers over HTTPS, and it may present its own certificate for client PKI authentication. Option A is wrong because transparent inspection mode does not make FortiWeb the SSL endpoint in the same way; it inspects traffic without acting as the primary TLS termination point. Option B is also wrong because simply routing HTTPS without decryption does not require FortiWeb to present its own certificate. FortiWeb certificates matter when FortiWeb is an HTTPS endpoint or an authenticated HTTPS client.

================

A FortiWeb server policy binds the listener, destination pool, and service handling required for traffic flow. The virtual server defines the public-facing listener where client traffic arrives. The server pool defines the real back-end servers or load-balanced pool where FortiWeb forwards accepted traffic. The service or port settings define whether FortiWeb handles HTTP, HTTPS, or another configured service. A WAF profile is important for security inspection, but the question asks for the three components needed to complete the forwarding policy. DNS resolver, URL rewrite, health checks, IPsec tunnels, and static routes may be useful in some deployments, but they are not the required core components of the server policy.

================

SSRF is an application-layer abuse case where attacker-controlled input causes the backend application to make unintended server-side requests. FortiWeb controls such as parameter validation, file security, and ML anomaly detection reduce risk, but SSRF often succeeds when the application accepts weakly validated URLs, hostnames, redirects, metadata endpoints, internal IP ranges, or backend-only resources. Disabling ML would weaken protection. Moving SSRF protection to FortiGate is wrong because SSRF depends on HTTP/API logic, not only network-layer filtering. HTTPS inspection alone does not solve unsafe backend request behavior. The correct priority is to refine input validation and filtering logic so FortiWeb can better detect and block malicious URL, parameter, and backend-request patterns.

================

The exhibit is written in structured OpenAPI/YAML-style format. It includes fields such as info, version, title, servers, paths, HTTP method get, operationId, responses, content type application/json, and a schema definition. That is not HTML and it is not a live API response. It is also not CLI output from FortiWeb. FortiWeb OpenAPI validation uses OpenAPI description files in YAML or JSON to define API structure, endpoints, parameters, and expected data types. FortiWeb then uses that uploaded schema as a baseline to validate API requests and block requests that do not conform. So the exhibit is best identified as an API schema file

The exhibits show a mismatch between the configured server pool and the server pool referenced by the server policy. The server pool containing the two back-end servers is named app-server-pool1 , but the server policy is selecting server-pool1 . In reverse proxy mode, FortiWeb receives traffic on the virtual server and then forwards it to the server pool selected in the server policy. If the policy points to the wrong or empty pool, traffic will not be forwarded to the intended back-end servers, even if health checks for the correct pool are healthy. Client Real IP affects source IP preservation, not pool selection. The FortiGate should forward traffic to FortiWeb, not directly bypass it. The correct fix is to select the correct server pool.

================