In FortiOS 7.6, the Antivirus scan master switch in an antivirus profile becomes available only after at least one supported protocol is enabled for inspection.
What the exhibit shows
A new antivirus profile named FTP_AV_Profile
Feature set: Flow-based
Antivirus scan switch is grayed out
All Inspected Protocols (HTTP, SMTP, POP3, IMAP, FTP, CIFS) are currently disabled Why the Antivirus scan switch is grayed out In FortiOS antivirus profiles:
The Antivirus scan toggle is a dependent control
It cannot be enabled unless at least one inspected protocol is selected This prevents enabling AV scanning when there is no traffic type to scan This behavior is documented in the FortiOS 7.6 Antivirus Profile configuration section.
Once you enable a protocol (for example, FTP), the Antivirus scan switch becomes active and configurable.
Why option B is correct
B . None of the inspected protocols are active in this profile.
All protocol toggles are OFF
Therefore, FortiGate disables (grays out) the Antivirus scan option
This is expected and correct behavior
Why the other options are incorrect
A . Antivirus scan is disabled under Feature visibilityIncorrect. Feature Visibility controls whether Antivirus appears in the GUI, not whether the scan switch is enabled inside a profile.
C . Feature set must be Proxy-basedIncorrect. Antivirus scanning is supported in both flow-based and proxy-based modes.
D . Less than 2 GB RAM does not support Antivirus scanIncorrect. Memory size affects performance and offloading, not basic AV scan availability.

With full SSL inspection, FortiGate performs a man-in-the-middle process: it decrypts the HTTPS session, inspects it, then re-encrypts it. To do this, FortiGate presents a substitute certificate to the client, signed by the CA certificate configured in the SSL/SSH inspection profile (for example, Fortinet_CA_SSL or a custom enterprise CA).
Browsers will show certificate warning errors when the issuing CA is not trusted by the client device/browser trust store. This only happens for HTTPS because certificates are used in TLS; HTTP has no certificate exchange, so no warning appears.
Why the other options are incorrect:
A: Allowing invalid server certificates affects whether FortiGate blocks/permits connections to sites with bad certs; it does not fix the client warning about FortiGate's substituted cert.
B: Proxy vs flow inspection mode does not inherently cause certificate warnings; the warning is about trust of the signing CA.
D: Missing extensions is not the typical reason across "any HTTPS website"; the standard reason is the client does not trust the FortiGate inspection CA

"FortiSASE provides secure access to remote users for the following use cases:
* SIA enables secure web browsing for remote users to protect from known and unknown threats
* SPA enables explicit application access under a zero-trust access or with SD-WAN integration to ensure secure application access
* SSA addresses shadow IT visibility challenges and safeguards data loss prevention"
"FortiCASB provides cloud-based and API-based features to enable deep inspection of SaaS applications to enable detailed monitoring, analysis, and reporting features... Data loss prevention (DLP) helps to identify, monitor, and protect organizational data at rest and in motion." Technical Deep Dive:
The correct answer is C. Secure SaaS access (SSA).
The question gives two very specific requirements:
Shadow IT visibility
Prevent sensitive files from leaving the organization without approval
The study guide maps both directly to SSA. In FortiSASE, SSA aligns with SaaS governance and CASB-style controls. That is the right architecture when you need visibility into sanctioned and unsanctioned SaaS usage, plus DLP controls for uploads, sharing, and file movement.
Why the other options are wrong:
SIA focuses on securing internet browsing and remote web traffic.
SPA is for explicit zero-trust access to private applications.
SSD-WAN is not the FortiSASE method for SaaS visibility/DLP control.
In practice, SSA is the choice because it combines SaaS visibility, activity monitoring, and DLP-style enforcement. That lets an administrator detect shadow SaaS usage and apply controls such as blocking uploads, monitoring sharing events, or restricting file transfers based on policy. This is a CASB-oriented use case, not just generic web security.

In FortiOS 7.6, SD-WAN Performance SLAs are used to measure link quality and influence SD-WAN rule decisions. The following three statements are true.
C). All the SLA targets can be configured.
True
SD-WAN Performance SLAs allow administrators to configure:
Latency
Jitter
Packet loss
Mean Opinion Score (MOS) (for voice)
Threshold values for these metrics are fully configurable per SLA.
This is explicitly documented in the SD-WAN Performance SLA configuration section.
D). They are applied in an SD-WAN rule lowest cost strategy.
True
Performance SLAs are commonly used with the Lowest Cost (SLA-based) strategy.
In this strategy:
FortiGate selects the lowest-cost link that meets the SLA requirements.
If a link violates the SLA, it is excluded from selection.
E). They can be measured actively or passively.
True
FortiOS supports:
Active probing (synthetic probes such as ping/HTTP)
Passive measurement (based on real traffic statistics)
Administrators can choose how SLAs are measured depending on the deployment and requirements.
Why the other options are incorrect
A). They rely on session loss and jitter.
Incorrect
SLAs measure packet loss, latency, and jitter.
Session loss is not an SLA metric in FortiOS.
B). They monitor the state of the FortiGate device.
Incorrect
Performance SLAs monitor link quality, not FortiGate system health or device state.