[2026年08月06日]NSE5_FWB_AD-8.0練習試験問題集で試験99%合格率があります [Q11-Q36]

[2026年08月06日]NSE5_FWB_AD-8.0練習試験問題集で試験99%合格率があります

最新の検証済みNSE5_FWB_AD-8.0問題と解答、合格保証もしくは全額返金

質問 # 11
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. Switch to a reverse-proxy mode to bypass cookie-based controls.
B. Enable API protection and client management to enforce identity checks on mobile API traffic.
C. Replace ZTNA with bot protection to reduce false positives.
D. Log only API traffic and rely on FortiAnalyzer for future alerts.

正解：B

解説：
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.

質問 # 12
Refer to the exhibits.

You are configuring a FortiWeb device in reverse proxy mode, placed downstream from a FortiGate. The server pool includes two back-end web servers: 10.1.1.21 and 10.1.1.22, and you've defined a health check policy.
After completing the server policy configuration and applying it to a virtual server, you notice that FortiWeb is not forwarding traffic to the back-end servers. No errors or health check failures appear in the logs.
Based on the configuration shown in the exhibit, which change should you make to restore back-end traffic flow?

A. Select the correct server pool in the FortiWeb server policy.
B. Change the virtual server IP address to match one of the back-end servers.
C. Enable Client Real IP to ensure traffic goes to the back-end servers.
D. Configure FortiGate to forward traffic to the back-end IP addresses directly.

正解：A

解説：
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.

質問 # 13
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. FortiWeb, because it terminates the HTTPS session and decrypts traffic.
B. The client, because it initiates the TLS handshake and verifies the certificate.
C. None. SSL offloading does not require a private key because FortiWeb only forwards traffic.
D. The server, because it always handles certificates regardless of SSL mode.

正解：A

解説：
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.

質問 # 14
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.)

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

正解：C、D

解説：
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.

質問 # 15
Refer to the exhibit.

What does the exhibit show?

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

正解：A

解説：
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

質問 # 16
A FortiWeb administrator is hardening a customer checkout website.
The site contains sensitive links such as Login, Payment, and Admin, which are embedded in the HTML content of several pages.
A vulnerability scan shows that automated bots can crawl the web pages and easily enumerate these links by parsing the HTML source, even though users access them normally, through the site navigation.
Which FortiWeb feature should the administrator enable to prevent automated scanners from discovering these links?

A. Link cloaking
B. URL rewriting
C. Deep packet inspection
D. URL encryption

正解：A

解説：
Link cloaking is the FortiWeb feature designed to hide sensitive URLs or links from automated scanners and crawlers that parse HTML source code. In this scenario, the problem is not routing, encryption, or packet inspection; the problem is that bots can read embedded links directly from page content and enumerate sensitive paths such as Login, Payment, and Admin. Link cloaking helps obscure those links so that automated tools cannot easily discover them while normal users can still navigate the site as intended. URL rewriting changes URLs for routing or presentation, but it is not the most precise feature for hiding embedded links from scanners. Deep packet inspection is too broad and does not specifically solve HTML link enumeration.

質問 # 17
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. Replace the current deployment mode with a one-arm proxy to expose source IP addresses.
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. Disable IP-based detection features on FortiWeb to avoid IP-related blocking.

正解：B

解説：
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.

質問 # 18
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, because it provides token-based access to remote services.
B. SAML SSO, because it supports identity authentication on Fortinet devices.
C. HTML form authentication, because it's faster and doesn't need external systems.
D. SAML, because it blocks users from accessing anything not approved in FortiWeb policy.

正解：B

解説：
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.

質問 # 19
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.

正解：

解説：

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.

質問 # 20
Refer to the exhibits.

A new domain, https://finance.fortinet.demo, was added but not explicitly mapped. Users report the site loads correctly, but you're unsure which back-end server is being used.
Why is this request succeeding despite no explicit routing rule for finance.fortinet.demo?

A. The inherited certificate has a wildcard entry for all subdomains.
B. The connection is passed to FortiGate for secondary routing.
C. FortiWeb auto-generates fallback policies for new domains.
D. The request defaults to app_server_1 because it is marked as the default route.

正解：D

解説：
The exhibit shows FortiWeb using HTTP content routing, with multiple routing policies and one policy marked as the default. The domain finance.fortinet.demo does not match the explicit routing rules shown, so FortiWeb falls back to the default HTTP content routing entry. In the policy table, app_server_1 is marked as the default route, meaning unmatched requests are sent to that server pool. The certificate does not determine back-end routing; it only supports TLS identity. FortiWeb does not automatically create routing policies for new domains, and the request is not passed to FortiGate for secondary content routing. Because no explicit hostname match exists, the default content routing policy handles the request.

質問 # 21
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.

正解：

解説：

質問 # 22
You are reviewing the FortiWeb integration with the Advanced Bot Protection (ABP) service.
Match each step in the ABP flow with its description.

正解：

解説：

Explanation:

The ABP workflow begins when FortiWeb challenges the browser by injecting JavaScript used to collect behavior data. The client browser then executes that JavaScript and sends the observed behavior information to the ABP service. FortiWeb then uses the ABP service decision process to determine whether the browser behavior looks human or automated. If the ABP service identifies the activity as malicious or bot-like, FortiWeb blocks the request before it reaches the protected application. If the request is validated as coming from a real user, FortiWeb allows the traffic to continue to the back-end server. The order is important because FortiWeb cannot allow or block based on ABP until browser behavior has first been collected and evaluated.

質問 # 23
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.

正解：

解説：

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.

質問 # 24
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 web application firewall (WAF) rule that blocks every user agent that is not on a manually created allowlist.
B. A DoS protection profile with extremely low request limits for the entire site.
C. A static blocklist for all IP addresses seen in logs, even if most appear only once.
D. Bot mitigation with device fingerprinting to correlate clients by behavior, headers, and JavaScript challenges instead of IP address volume.

正解：D

解説：
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.

質問 # 25
You are hosting multiple secure web applications behind a single public IP address on FortiWeb.
When a client connects to a service, FortiWeb needs to:
* Identify the correct SSL certificate.
* Decrypt the request.
* Route the request to the correct back-end server.
Match each FortiWeb function to the request handling step that performs the function.

正解：

解説：

Explanation:

When multiple HTTPS applications share one public IP address, the client begins the TLS connection and includes the requested hostname in the SNI field. FortiWeb uses SNI-based certificate selection to choose the appropriate certificate for that hostname. After presenting the correct certificate and completing the TLS handshake, FortiWeb decrypts the HTTPS session so it can inspect HTTP content. Content inspection then evaluates the host header and URL path, which are needed for application-aware routing decisions. Finally, intelligent traffic routing forwards the request to the correct back-end server or server pool. The sequence matters: FortiWeb cannot inspect the host and URL path or route by content until the HTTPS session is terminated and decrypted.