lock_openFree sampleContent inspectionmedium
An antivirus profile is applied to a policy that inspects HTTPS web traffic, yet malware delivered over HTTPS is reaching internal hosts while the same files delivered over plain HTTP are blocked as expected. The antivirus signatures are current. Which configuration gap most likely explains why the HTTPS-delivered malware is not being caught?
- ASSL inspection is not configured on the policy, so the encrypted payload is never decrypted for the antivirus engine to scan.check_circle Correct
- BThe antivirus profile is missing a grayware category, so encrypted malware is reclassified as grayware and allowed through.
- CThe FortiGuard antivirus database failed to update, which would block HTTP malware too rather than only the HTTPS path.
- DThe profile uses proxy-based inspection, which cannot scan web protocols and only supports email-borne malware.
Understand that antivirus cannot scan HTTPS payloads unless SSL inspection decrypts the traffic first. The antivirus engine matches signatures against cleartext content, so malware inside an encrypted HTTPS session stays hidden until SSL inspection decrypts it; without that decryption the engine never sees the file regardless of signature freshness.
Why A is correct: Correct: without SSL inspection the FortiGate cannot decrypt HTTPS, so the antivirus engine never sees the cleartext file and cannot match its signatures, which explains why only the encrypted path leaks malware.
Why B is wrong: Grayware categorisation does not bypass encryption inspection, and missing grayware coverage would not selectively let HTTPS malware through, so this misattributes the cause.
Why C is wrong: A stale database would affect both HTTP and HTTPS equally, but HTTP is still blocked and signatures are stated to be current, so this cannot be the selective cause.
Why D is wrong: Proxy-based inspection fully supports web protocols including HTTP and HTTPS, so claiming it only handles email-borne malware is factually incorrect.
lock_openFree sampleContent inspectionmedium
An administrator must choose the inspection mode for a firewall policy that carries web filtering. The security team needs each web page to be fully buffered and reassembled so that the page body can be examined as a complete object before the action is decided, accepting some extra latency in return. Which inspection mode meets this requirement, and why does it suit the goal?
- AFlow-based inspection, because it reconstructs each complete HTTP response in a proxy buffer before forwarding any packets to the client.
- BProxy-based inspection, because it terminates and reassembles the full HTTP transaction in a buffer, letting the web filter act on the complete page before delivery.check_circle Correct
- CFlow-based inspection with the IPS engine handling reassembly, because the single-pass engine collects the whole page in memory before any verdict.
- DProxy-based inspection, because it inspects each packet individually as it arrives and therefore adds the least possible latency to the page load.
Proxy-based inspection buffers and reassembles the full HTTP transaction so web filtering can act on the complete page, trading latency for thoroughness. Proxy-based inspection terminates the session in a buffer and reconstructs the entire request and response before forwarding, which lets web filtering evaluate the whole reassembled object; flow-based inspection scans the stream packet by packet in a single pass and never holds the full page as one object, so it is faster but less able to act on complete content.
Why A is wrong: Tempting because flow-based mode still performs web filtering, but it is wrong: flow-based inspection examines traffic packet by packet as it streams through and does not buffer the whole response, so it cannot present the full page body as one object.
Why B is correct: Correct: proxy-based inspection acts as a transparent proxy that buffers and reassembles the entire HTTP request and response, so the web filter can evaluate the complete reconstructed object before deciding to allow or block, at the cost of added latency and memory.
Why C is wrong: Tempting because flow-based mode does use the IPS engine for single-pass scanning, but it is wrong: that engine inspects the stream as it passes and does not hold the entire page to act on it as one buffered object the way a proxy does.
Why D is wrong: Tempting because it names the right mode, but the reasoning is wrong: proxy-based mode buffers and reassembles rather than inspecting packet by packet, and it adds more latency than flow-based, not the least.
lock_openFree sampleContent inspectionmedium
An administrator builds a new application control profile and sets the default action for all categories to Monitor. They then add a category override for Video/Audio set to Block, and a single application override for a specific streaming application set to Allow. When that streaming application is detected, which action does FortiGate apply?
- ABlock, because the Video/Audio category override takes precedence over any individual application override inside the profile.
- BMonitor, because the profile default action is applied first and logs the traffic before any override can change the verdict.
- CAllow, because an application override matches before the category override and the broad default action.check_circle Correct
- DBlock then Allow, because FortiGate applies the category action first and then re-evaluates the application override on the next session.
Understand that application control evaluates a named application override ahead of a category override and the profile default action. Within an application control profile FortiGate resolves the action by specificity: an individual application override is matched before a category override, and both are matched before the profile-wide default, so the per-application Allow is the action enforced.
Why A is wrong: This inverts the precedence order. Category-level settings are the broad fallback; a per-application override is evaluated first, so the application is not blocked by the category rule.
Why B is wrong: The default action is the lowest-priority fallback used only when no override matches, so it is tempting but does not apply when a specific application override exists.
Why C is correct: Application control evaluates the most specific match first: a named application override beats a category override, which beats the profile default, so the Allow override wins for that signature.
Why D is wrong: FortiGate does not apply two conflicting actions in sequence per session; it selects one action from the most specific match, so this describes behaviour that does not occur.
lock_openFree sampleContent inspectionhard
An administrator wants the FortiGate to detect traffic that deviates from normal protocol behaviour, such as an unusually high rate of TCP SYN packets toward a server, rather than matching a specific known exploit pattern. Which IPS capability is designed for this rate-based, behavioural detection?
- ASignature override action, which changes how a single named exploit signature is handled when matched.
- BWeb filtering category override, which reclassifies a destination URL to permit or block the connection.
- CApplication control signature matching, which identifies the application by its traffic fingerprint regardless of port.
- DDoS anomaly detection using rate thresholds, which flags or drops traffic that exceeds configured behavioural limits for a protocol.check_circle Correct
Distinguish rate-based anomaly detection (DoS thresholds) from signature pattern matching within FortiGate IPS. Signature-based IPS matches known exploit patterns, while anomaly detection works on behaviour. DoS anomaly sensors compare protocol traffic rates against configured thresholds and act when limits are exceeded, catching floods that have no single fixed signature.
Why A is wrong: Tempting because overrides tune IPS behaviour, but an override only adjusts the action of an existing pattern-based signature and does not perform rate or behaviour analysis.
Why B is wrong: Tempting because it is another inspection feature, but web filtering evaluates URL categories and has no role in detecting abnormal packet rates or protocol anomalies.
Why C is wrong: Tempting because application control also fingerprints traffic, but it identifies which application is in use rather than measuring rate-based anomalies against a behavioural threshold.
Why D is correct: Correct. Anomaly-based DoS sensors use configurable rate thresholds to detect behaviour such as SYN floods, acting when traffic exceeds the normal baseline rather than matching a fixed signature.
lock_openFree sampleContent inspectionmedium
A FortiGate is performing deep inspection on user traffic. A particular client application uses certificate pinning and fails to connect through the firewall, although it works when the device is taken off the network. What is the most appropriate way to keep that application working without weakening inspection for everyone else?
- ASwitch the whole inspection profile to certificate inspection so the pinned application stops detecting a re-signed certificate.
- BAdd the application's destination host or category to the SSL exemption list so its sessions bypass decryption while other traffic is still deeply inspected.check_circle Correct
- CDisable strict certificate checking on the FortiGate so pinned applications accept the re-signed certificate.
- DInstall the FortiGate CA certificate inside the pinned application so it trusts the re-signed certificate like a browser would.
Certificate-pinned applications break under deep inspection, so exempt their destinations from decryption rather than weakening inspection globally. Certificate pinning hard-codes an expected server certificate or public key inside the client, so any FortiGate re-signed certificate is rejected regardless of trusted root stores. The targeted fix is to exempt only the pinned application's destinations from SSL inspection while keeping deep inspection on all other sessions.
Why A is wrong: Tempting because certificate inspection avoids re-signing and fixes the pinned app, but it is wrong: it disables deep inspection for all users, weakening inspection broadly rather than narrowly.
Why B is correct: Correct: pinned applications reject re-signed certificates, so exempting only that destination from decryption restores the application while deep inspection continues for all other traffic.
Why C is wrong: Tempting because it mentions certificate checking, but it is wrong: pinning is enforced by the client against its embedded certificate, so a FortiGate-side setting cannot make the client accept the re-signed certificate.
Why D is wrong: Tempting because installing the CA fixes browser warnings, but it is wrong: pinning validates against a specific expected certificate or key, not the system trust store, so adding the CA does not satisfy the pin.