Free NSE5_FWB_AD-8.0 Exam Braindumps
Fortinet NSE 5 - FortiWeb 8.0 Administrator Questions 6–10 (page: 3)

Updated On: 22-Aug-2026

Refer to the exhibit.


A FortiWeb administrator tests a new form input value after training the machine learning (ML) anomaly detection system.
The hidden Markov model (HMM) flags the input as abnormal, while the support vector machine (SVM) model classifies it as normal. FortiWeb allows the request.
What does this result indicate about the FortiWeb ML anomaly detection behavior?

  1. FortiWeb is correctly allowing an unusual but non-malicious input based on combined HMM and SVM
    evaluation.
  2. The anomaly detection thresholds are too low and must be increased.
  3. FortiWeb failed to detect an attack and should have blocked the request.
  4. One of the ML models should be disabled to avoid inconsistent results.

Answer(s): A

Explanation:

FortiWeb ML anomaly detection uses multiple models to evaluate whether input is truly malicious or simply unusual. In this case, the input appears abnormal to the HMM pattern model, but the SVM classification considers it acceptable, so FortiWeb treats it as normal and allows the request.



A third-party penetration test reveals that users can bypass login controls through a mobile API. Your current FortiWeb configuration includes zero trust network access (ZTNA) profiles and cookie security, but API protection and client management are not enabled. The security team asks you to recommend the most effective way to close this gap.
Which FortiWeb adjustment would best prevent future unauthorized API access?

  1. Switch to a reverse-proxy mode to bypass cookie-based controls.
  2. Enable API protection and client management to enforce identity checks on mobile API traffic.
  3. Log only API traffic and rely on FortiAnalyzer for future alerts.
  4. Replace ZTNA with bot protection to reduce false positives.

Answer(s): B

Explanation:

API protection and client management are designed to control and validate access to API endpoints, including mobile API traffic. Enabling them allows FortiWeb to apply identity-aware checks, manage API clients, and prevent unauthorized access paths that are not adequately protected by cookie security alone.



Which statement best describes the difference between SAML authentication and HTML authentication in FortiWeb site publishing?

  1. SAML authentication delegates login to an external system, while HTML authenticates directly on FortiWeb.
  2. SAML authentication is used for internal apps while HTML authentication is used for cloud apps.
  3. SAML authentication encrypts passwords while HTML authentication sends passwords in cleartext format.
  4. SAML authentication uses a passwordless login, while HTML authentication uses tokens.

Answer(s): A

Explanation:

SAML authentication relies on an external identity provider to authenticate the user and return an assertion to FortiWeb. HTML authentication uses a FortiWeb-hosted login page or form-based authentication process where FortiWeb directly handles the user login workflow for the published site.



Refer to the exhibit.

You are deploying FortiWeb to handle HTTPS traffic from clients and forward cleartext traffic to a back-end server.
You want FortiWeb to decrypt the HTTPS session, inspect the traffic, and then send the traffic to the server using HTTP.
What can you configure on FortiWeb to make this behavior happen?

  1. Enable reencryption on the back-end interface so the server receives HTTPS traffic.
  2. Configure passive SSL inspection so FortiWeb analyzes encrypted packets without terminating SSL.
  3. Configure FortiWeb to reuse the same certificate for inbound and outbound HTTPS traffic without decrypting traffic.
  4. Enable SSL offloading so FortiWeb terminates the client's HTTPS session and forwards decrypted HTTP
    traffic to the back-end server.

Answer(s): D

Explanation:

SSL offloading allows FortiWeb to terminate the client HTTPS connection, decrypt and inspect the traffic, and then forward the request to the back-end server over HTTP. This provides inspection while removing the SSL processing requirement from the server.



A user from group B sends 150 requests in one minute to this endpoint:

Group B users are allowed access to only /api/v1/reports and are limited to 50 requests per minute.
What should the FortiWeb administrator configure to stop this abuse?

  1. Move the user to group A to increase their limit.
  2. Apply group-based rate limiting to restrict group B users to 50 requests per minute.
  3. Nothing. They should allow the request because the API key is valid.
  4. Change the host to block access to /api/v1/data.

Answer(s): B

Explanation:

Group-based rate limiting enforces the allowed request threshold for group B users, limiting them to 50 requests per minute and preventing excessive API use even when the request includes a valid API key.



Viewing page 3 of 11
Viewing questions 11 - 15 out of 50 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!