Latest NSE5_FWB_AD-8.0 Exam Dumps Fortinet Exam from Training Expert Lead2PassExam
Pass Fortinet Fortinet NSE 5 - FortiWeb 8.0 Administrator PDF Dumps | Recently Updated 38 Questions
NEW QUESTION # 14
You have configured parameter validation, file security, and machine learning (ML) anomaly detection for a web form, but some server-side request forgery tests are still succeeding. You need to advise the team on what to prioritize next to improve SSRF protection without compromising other parts of the application.
Which recommendation would best strengthen FortiWeb's ability to block remaining SSRF attempts?
- A. Review and refine input validation logic, as SSRF may be exploiting backend behavior or bypassing weak filters.
- B. Apply HTTPS inspection at the transport layer, which FortiWeb does not use to block SSRF.
- C. Disable ML anomaly detection and rely solely on parameter inspection.
- D. Offload all server-side request forgery (SSRF) protection to FortiGate and remove FortiWeb from the API flow.
Answer: A
Explanation:
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.
NEW QUESTION # 15
Refer to the exhibit.
There is only one administrator account configured on FortiWeb and IPv6 is not configured on any interface.
Which action should an administrator take to restrict any brute force attacks that attempt to gain access to the FortiWeb management GUI?
- A. Delete the built-in administrator user and create a new one.
- B. Make configuration changes on the upstream device.
- C. Replace 0.0.0.0/0 with a specific IP address.
- D. Change the setting in the Access Profile field to Read_Only .
Answer: C
Explanation:
The exhibit shows the administrator account using IPv4 trusted hosts with a broad entry that effectively allows management access attempts from any IPv4 source. To reduce brute force exposure against the FortiWeb GUI, the administrator should restrict the trusted host entry to a specific trusted management IP address or subnet. FortiWeb administrator accounts can be limited by trusted host settings, so only defined source addresses can even attempt to authenticate. Changing the upstream device may help, but FortiWeb should still enforce its own management access restriction. Deleting the built-in administrator account does not solve the source-access problem. Changing the access profile to read-only only limits privileges after login; it does not prevent brute force attempts against the GUI.
NEW QUESTION # 16
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.
Answer:
Explanation:
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.
NEW QUESTION # 17
A FortiWeb administrator is deciding between using SAML SSO or HTML authentication. They want to minimize the number of credential prompts users receive across multiple Fortinet services.
Which statement accurately describes which option is best, and why?
- A. HTML form authentication, because it's faster and doesn't need external systems.
- B. SAML, because it blocks users from accessing anything not approved in FortiWeb policy.
- C. SAML SSO, because it supports identity authentication on Fortinet devices.
- D. HTML form, because it provides token-based access to remote services.
Answer: C
NEW QUESTION # 18
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?
- A. Replace ZTNA with bot protection to reduce false positives.
- B. Enable API protection and client management to enforce identity checks on mobile API traffic.
- C. Log only API traffic and rely on FortiAnalyzer for future alerts.
- D. Switch to a reverse-proxy mode to bypass cookie-based controls.
Answer: B
Explanation:
The issue is unauthorized access through a mobile API, so the control must enforce API-specific identity and access rules. FortiWeb API protection can validate API structure, methods, paths, and authorization requirements, while client management can help associate requests with legitimate clients or authenticated users. ZTNA profiles and cookie security can help with access and session protection, but they do not replace API-specific authorization controls. Switching reverse-proxy mode to bypass cookie controls makes no sense and could weaken protection. Replacing ZTNA with bot protection addresses a different problem: automation, not API authorization. Logging only records activity after the fact and does not prevent bypass. The correct action is to enable API protection and client management for mobile API traffic.
NEW QUESTION # 19
A FortiWeb administrator wants to stop coordinated scraping traffic coming from several IP addresses, each making only a few requests so thresholds never trigger.
Which tactic should the administrator deploy to identify botnets using shared behavioral signals instead of volume?
- A. A static blocklist for all IP addresses seen in logs, even if most appear only once.
- B. Bot mitigation with device fingerprinting to correlate clients by behavior, headers, and JavaScript challenges instead of IP address volume.
- C. A DoS protection profile with extremely low request limits for the entire site.
- D. A web application firewall (WAF) rule that blocks every user agent that is not on a manually created allowlist.
Answer: B
Explanation:
The scenario describes distributed scraping where each individual IP stays below request-rate thresholds. A simple DoS threshold is weak here because the attacker avoids volume-based detection per source. Static blocklists are also ineffective because many botnet IPs may appear only once or rotate frequently. Blocking every non-allowlisted user agent would cause severe false positives and is easy for bots to evade by spoofing headers. FortiWeb bot mitigation is the correct control because it can evaluate behavior beyond source IP volume. Device fingerprinting, browser behavior, headers, JavaScript challenges, and client characteristics help correlate suspicious automation even when requests are spread across many addresses. Therefore, bot mitigation with behavioral/device fingerprinting is the strongest answer.
NEW QUESTION # 20
Refer to the exhibit.
You have deployed FortiWeb behind a FortiGate that is configured as a reverse proxy and inserts the X- Forwarded-For HTTP header when forwarding HTTP and HTTPS traffic.
FortiWeb is using a custom inline protection profile, and logging is enabled, as shown in the exhibit.
You notice that FortiWeb is blocking legitimate users, and all requests in the attack logs appear to come from the FortiGate IP address, not the original client IP address.
Which action should you take to fix this issue?
- A. Disable IP-based detection features on FortiWeb to avoid IP-related blocking.
- B. Modify the protection profile to use the X-Forwarded-For header for client IP address detection.
- C. Recreate the server policy using the predefined profile instead of a custom one.
- D. Replace the current deployment mode with a one-arm proxy to expose source IP addresses.
Answer: B
Explanation:
The FortiGate is acting as an upstream reverse proxy, so FortiWeb sees the FortiGate address as the direct source IP unless it is configured to read the original client IP from the inserted HTTP header. Since FortiGate already inserts X-Forwarded-For, the proper fix is to modify the FortiWeb protection profile or related client- IP configuration so FortiWeb uses that header for client IP detection. This restores accurate logging, rate limiting, reputation checks, and IP-based enforcement. Changing to one-arm proxy is unnecessary and disruptive. Disabling IP-based detection weakens protection instead of fixing attribution. Recreating the policy with a predefined profile does not address the missing client IP mapping. The correct adjustment is to trust and use X-Forwarded-For.
NEW QUESTION # 21
A FortiWeb administrator is deciding between using SAML SSO or HTML authentication. They want to minimize the number of credential prompts users receive across multiple Fortinet services.
Which statement accurately describes which option is best, and why?
- A. HTML form authentication, because it's faster and doesn't need external systems.
- B. SAML, because it blocks users from accessing anything not approved in FortiWeb policy.
- C. SAML SSO, because it supports identity authentication on Fortinet devices.
- D. HTML form, because it provides token-based access to remote services.
Answer: C
Explanation:
SAML SSO is the correct choice when the goal is to reduce repeated credential prompts across multiple services. SAML uses a federated identity model, where users authenticate through an identity provider and then use assertions to access service providers without repeatedly entering credentials. This is exactly the value of single sign-on. HTML form authentication is more local and application-specific; it can authenticate users to a protected site, but it does not provide the same cross-service identity federation. Option B overstates SAML as a policy-blocking mechanism. Option C may be simpler but does not meet the SSO requirement.
Option D incorrectly describes HTML form authentication as token-based remote-service access.
NEW QUESTION # 22
Refer to the exhibit.
What does the exhibit show?
- A. A sample response returned by the FortiGate API at https://fortigate.com/ui.
- B. An API schema file.
- C. The FortiGate UI interface in HTML.
- D. The result of a show ui details command on a FortiWeb server.
Answer: B
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
NEW QUESTION # 23
You need to monitor and respond to repeated suspicious activity from individual users who are accessing your web application.
Your goal is to evaluate each action the user takes and apply a response when their behavior becomes risky.
What can you configure on FortiWeb to track user behavior and respond automatically when risky activity continues?
- A. Configure rate limiting on the IP reputation blocklist.
- B. Add a custom signature to block suspicious URLs immediately.
- C. Set up scoring in the protection profile to track request behavior over time.
- D. Enable automatic cookie security under the server policy.
Answer: C
Explanation:
The requirement is to track user behavior over time and respond when cumulative activity becomes risky.
FortiWeb client management and threat scoring are built for that purpose. When enabled in the protection profile, FortiWeb can associate activity with a client, assign threat weights to suspicious behavior, and apply actions such as alerting, denying, or period blocking after a defined score threshold is exceeded. Rate limiting is useful for traffic volume, but it does not evaluate a user's full behavior pattern. A custom signature blocks a specific pattern immediately, not cumulative behavior. Cookie security protects session cookies but does not calculate behavioral risk. The correct configuration is scoring in the protection profile to track and respond to repeated risky actions.
NEW QUESTION # 24
How should a FortiWeb administrator configure behavior-based bot detection to identify traffic from nonhuman users?
- A. Block all traffic that doesn't come from known devices.
- B. Create IP blocklists based on login failures.
- C. Set request rate limits and enable mouse movement tracking.
- D. Disable JavaScript execution for anonymous users.
Answer: C
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.
NEW QUESTION # 25
Refer to the exhibit.
You are configuring SSL offloading on FortiWeb to protect a public-facing application. Clients connect using HTTPS, while FortiWeb forwards requests to the back-end server using HTTP.
You are reviewing certificate deployment and need to decide where to install the private key for the certificate used in client connections.
In this SSL offloading setup, which device is responsible for using the private key associated with the web server certificate?
- A. The client, because it initiates the TLS handshake and verifies the certificate.
- B. The server, because it always handles certificates regardless of SSL mode.
- C. None. SSL offloading does not require a private key because FortiWeb only forwards traffic.
- D. FortiWeb, because it terminates the HTTPS session and decrypts traffic.
Answer: D
Explanation:
In SSL offloading, FortiWeb is the TLS endpoint for client connections. The client negotiates HTTPS with FortiWeb, not directly with the back-end web server. Therefore, FortiWeb must have the website certificate and associated private key so it can complete the TLS handshake, decrypt inbound HTTPS traffic, inspect the HTTP content, and then forward the request to the server using HTTP or a separate back-end connection.
Option B is wrong because TLS termination requires the private key. Option C describes SSL inspection or direct server termination, not offloading. Option D is wrong because clients verify the certificate but do not possess or use the server's private key. FortiWeb owns the private-key function in this design.
NEW QUESTION # 26
Refer to the exhibit.
You are a FortiWeb administrator reviewing how FortiAI protects sensitive data when interacting with a large language model (LLM).
Drag each label to the corresponding step in the FortiAI data privacy workflow.
Answer:
Explanation:
Explanation:
The FortiAI privacy workflow is designed to prevent sensitive local values from being exposed directly to the external LLM. First, the administrator submits a natural-language query. FortiWeb then masks sensitive data before the request leaves the local environment. The FortiAI Proxy sends the masked query to the LLM, allowing the LLM to process the intent without seeing the original confidential values. The LLM returns a function response rather than directly operating on sensitive production data. FortiWeb then unmasks the values and runs the query locally, keeping sensitive data under FortiWeb control. Finally, the administrator sees the result with the original values restored. This preserves usability while reducing data exposure risk.
NEW QUESTION # 27
You are setting up a FortiWeb policy to protect a customer login portal. Users connect to https://login.training.
lab, and you want FortiWeb to forward those requests to a load-balanced pool of back-end servers.
Which three components must you configure to complete the server policy?
- A. Web application firewall (WAF) profile, DoS policy, and server name indication (SNI)-based certificate.
- B. DNS resolver, URL rewrite rule, and HTTP health check.
- C. Virtual server, server pool, and port settings (service).
- D. Real server, IPsec tunnel, and static route.
Answer: C
Explanation:
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.
NEW QUESTION # 28
A large enterprise has an existing web infrastructure with complex routing rules and static IP address assignments. The network administrators cannot modify the current IP address scheme, but they need FortiWeb to inspect and block threats like SQL injection and cross-site scripting (XSS) without changing the client-server communication flow.
In this situation, which FortiWeb operation mode is the most suitable?
- A. Reverse proxy mode
- B. Decryption mirror mode
- C. Web Cache Communication Protocol (WCCP) redirection mode
- D. True transparent proxy mode
Answer: D
NEW QUESTION # 29
......
Updated Test Engine to Practice NSE5_FWB_AD-8.0 Dumps & Practice Exam: https://www.lead2passexam.com/Fortinet/valid-NSE5_FWB_AD-8.0-exam-dumps.html