Fortinet NSE5_FWB_AD-8.0 Exam Actual Questions
Fortinet NSE 5 - FortiWeb 8.0 Administrator (Page 2 )

Updated On: 25-Jul-2026

DRAG DROP (Drag and Drop is not supported)
You are working on securing HTTPS communication across different services using FortiWeb. Your task is to configure and validate digital certificates for various traffic and communication needs.
Match each FortiWeb certificate feature to the certificate-related task that supports the feature.

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Refer to the exhibit.

What does the exhibit show?

  1. The FortiGate UI interface in HTML.
  2. A sample response returned by the FortiGate API at https://fortigate.com/ui.
  3. The result of a show ui details command on a FortiWeb server.
  4. An API schema file.

Answer(s): D

Explanation:

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



A FortiWeb administrator sees the following request:
GET /api/v1/data HTTP/1.1 Host: example.com Authorization: ApiKey abc123def456
The API key belongs to a user in group B who is authorized to access only /api/v1/reports.
What should the administrator do to prevent this unauthorized access?

  1. Restrict access to /api/v1/data using user group–based access control.
  2. Block /api/v1/data for all user groups to avoid policy confusion.
  3. Move the user to group A so they can access both endpoints.
  4. Allow all valid API keys to access any API endpoint.

Answer(s): A

Explanation:

The problem is not that the API key is invalid; the key belongs to a real user. The issue is authorization scope: group B is allowed only to access /api/v1/reports, but the request targets /api/v1/data. The correct FortiWeb control is API gateway rule enforcement using API key verification and API user grouping. FortiWeb can restrict API access by user group, sub-URL, API key verification, and configured violation actions. Blocking the endpoint for every group is too broad, moving the user to another group grants unnecessary privilege, and allowing all API keys to access all endpoints destroys endpoint-level authorization. The correct fix is group-based access control on /api/v1/data.



While reviewing FortiWeb logs, you notice a suspicious login request that failed authentication. You suspect it may be part of an injection attack targeting the login form.
Which input pattern is an example of a typical SQL injection attempt that could bypass authentication checks?

  1. '||(SELECT password FROM users WHERE role='admin')||'
  2. <sql>select(ALL USERS);</sql>
  3. <script>document.location='/steal?cookie='+document.cookie</script>
  4. SELECT username FROM accounts WHERE username='admin';-- ' AND password='password';

Answer(s): D

Explanation:

Option D is the strongest SQL injection example because it uses SQL syntax with a comment marker --to neutralize the password condition. In a vulnerable login query, that could cause the database to evaluate only the username portion and ignore the password check, creating an authentication bypass. Option C is not SQL injection; it is cross-site scripting because it executes JavaScript in the browser. Option B is fake XML-like markup and not a realistic SQL payload. Option A contains a SQL-like subquery, but it is not the best authentication-bypass pattern shown. FortiWeb’s injection defenses are designed to detect SQL injection and XSS as malicious input patterns targeting application logic.



You are reviewing SSL-related issues on FortiWeb. An administrator reports that they receive a certificate warning when they access the FortiWeb GUI over HTTPS. Separately, your FortiWeb device also makes outbound HTTPS requests to a back-end API server.
In which two situations would FortiWeb use its own certificates to establish or secure the connection? (Choose two.)

  1. When a client browser initiates an SSL session and FortiWeb is in transparent inspection mode.
  2. When FortiWeb is routing an HTTPS connection to a FortiGate without decrypting it.
  3. When an administrator connects to the FortiWeb GUI using HTTPS in a browser.
  4. When FortiWeb connects to a back-end server over HTTPS as a client.

Answer(s): C,D

Explanation:

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.



DRAG DROP (Drag and Drop is not supported)
A FortiWeb administrator is reviewing issues found during a security audit. The audit lists shortcomings based on behavior, configuration, and data protection.
The administrator must break down the findings and match them with the correct FortiWeb feature.
Select each FortiWeb feature in the left column, hold and drag it to the blank space next to the OWASP issue in the column on the right. Once you match a FortiWeb feature to the OWASP issue, you can move it again if you want to change your answer by clicking on the FortiWeb feature. You need to match five FortiWeb features to the OWASP issue in the work area.

  1. See Explanation section for answer.

Answer(s): A

Explanation:


The mapping follows the security risk each FortiWeb feature mitigates. User Tracking maps to Broken Access Control because it helps enforce authenticated-session behavior and can prevent unauthorized access patterns. HSTS Header Security maps to Cryptographic Failures because it forces browsers toward HTTPS and reduces downgrade or weak transport behavior. Padding Oracle Protection also maps to Cryptographic Failures because padding oracle attacks exploit weaknesses in encrypted session or token handling. Web Vulnerability Scan maps to Security Misconfiguration because scans help expose misconfigured, exposed, or vulnerable application components. Session Forwarding fits Insecure Design because it helps enforce expected application flow rather than allowing users or attackers to jump through weakly designed paths.



How should a FortiWeb administrator configure behavior-based bot detection to identify traffic from nonhuman users?

  1. Set request rate limits and enable mouse movement tracking.
  2. Block all traffic that doesn’t come from known devices.
  3. Disable JavaScript execution for anonymous users.
  4. Create IP blocklists based on login failures.

Answer(s): A

Explanation:

FortiWeb bot mitigation is designed to distinguish automated clients from real human users by evaluating request behavior and browser interaction signals. Request-rate limits help detect automation patterns such as excessive requests over a short period, while mouse movement tracking is a behavioral or biometric-style control that helps confirm whether a browser session is being operated by a human. Blocking all unknown devices is too aggressive and would create major false positives. Disabling JavaScript for anonymous users would actually weaken behavior collection because FortiWeb uses JavaScript-based techniques in some bot workflows. Login-failure IP blocklists help against credential attacks, but they do not broadly identify nonhuman users. Therefore, request limits plus mouse movement tracking is the best answer.



You are a FortiWeb administrator investigating an SQL injection attack on your company’s customer portal. The network firewall and intrusion prevention system (IPS) did not stop the attack.
You decide to deploy a web application firewall (WAF) to help prevent this type of attack.
Which two actions can you take to block application-layer threats? (Choose two.)

  1. Focus on client-side risks, such as protecting user browsers.
  2. Inspect general network traffic equally between clients and servers.
  3. Detect and block threats like SQL injection, cross-site scripting (XSS), and other Layer 7 attacks.
  4. Filter and analyze HTTP/S requests to block attacks targeting the web server.

Answer(s): C,D

Explanation:

A WAF such as FortiWeb is specifically built to protect web applications and web servers from HTTP and HTTPS application-layer attacks. SQL injection and cross-site scripting are Layer 7 threats that exploit web application input handling, not general network-layer forwarding. FortiWeb inspects HTTP/S requests, applies attack signatures, protocol validation, parameter validation, and other web protection controls to detect malicious payloads before they reach the protected application. Option A is wrong because protecting user browsers is mainly endpoint or client security, not WAF server-side protection. Option B is too generic and describes network firewall or IPS-style inspection rather than web application firewall enforcement. The two correct WAF actions are detecting Layer 7 attacks and analyzing HTTP/S requests targeting the web server.



Viewing page 2 of 6
Viewing questions 9 - 16 out of 36 questions


Post your Comments and Discuss Fortinet NSE5_FWB_AD-8.0 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!