In FortiOS 7.6, when FortiGate is integrated with FortiAnalyzer and FortiManager, firewall policies rely on a Universally Unique Identifier (UUID) to ensure proper policy tracking, synchronization, and log correlation across devices.
Why the UUID is required
Every firewall policy in FortiOS has a UUID.
FortiManager uses the UUID to:
Track policies across managed FortiGate devices
Maintain policy consistency during installs and revisions
FortiAnalyzer uses the UUID to:
Correlate logs accurately to the correct firewall policy
Preserve log association even if policy order or policy ID changes
Without a UUID:
Policy-to-log mapping can break
FortiManager cannot reliably manage or synchronize policies
FortiAnalyzer log analysis becomes inconsistent
This is explicitly documented in Fortinet administration and logging architecture references.
Why the other options are incorrect
B . Policy ID
Policy ID can change when policies are moved and is not reliable for long-term correlation across FortiManager and FortiAnalyzer.
C . Sequence ID
Sequence ID reflects GUI ordering only and has no role in log correlation.
D . Log ID
Log ID is generated per log event, not per firewall policy.

In FortiOS 7.6, the predefined deep-inspection and custom-deep-inspection SSL inspection profiles intentionally exclude certain web categories (such as Finance and Banking and Health and Wellness) and well-known domains (for example, Apple, Google, Adobe). This behavior is documented and intentional.
The two correct reasons are:
B . The legal regulation aims to prioritize user privacy and protect sensitive information for these websites.
Correct
Categories like Finance and Banking and Health and Wellness commonly handle highly sensitive personal data.
Many privacy and compliance regulations (for example, GDPR, PCI-DSS, HIPAA-like requirements) discourage or restrict SSL interception for such traffic.
To reduce legal and compliance risks, FortiOS exempts these categories from deep SSL inspection by default.
This is explicitly stated in FortiOS SSL/SSH Inspection documentation.
C . These websites are in an allowlist of reputable domain names maintained by FortiGuard.
Correct
FortiGuard maintains a reputable/trusted domain list for well-known services and platforms.
These domains are excluded from deep inspection by default to:
Prevent application breakage
Avoid certificate pinning and compatibility issues
Maintain user experience
This is why domains such as Apple, Google, Adobe, and app stores appear under SSL inspection exemptions.
Why the other options are incorrect
A . Resource utilization optimization
Incorrect.
While reduced inspection can save resources, this is not the primary documented reason for exempting these categories.
D . FortiGate temporary certificate denies access to HSTS websites
Incorrect.
Although HSTS and certificate pinning can cause issues with SSL inspection, this option describes a side effect, not the reason for exemption.
The exemption exists to avoid such problems, not because the certificate denies access.

From the current HA status, HQ-NGFW-1 is the primary and HQ-NGFW-2 is the secondary.
The administrator then changes these HA parameters:
HQ-NGFW-1: set override disable, set priority 90
HQ-NGFW-2: set override enable, set priority 110
In FGCP (A-P mode), the override (preemption) feature controls whether a higher-priority unit is allowed to take over the primary role.
When override is enabled, the cluster will prefer (and can re-elect) the unit with the highest device priority to become primary (preempting a lower-priority primary when conditions trigger re-election behavior as defined by FGCP).
Here, HQ-NGFW-2 has:
override enabled
higher priority (110) than HQ-NGFW-1 (90)
Therefore, the expected result is that HQ-NGFW-2 becomes the primary.
Why the other options are incorrect:
B is incorrect because it claims HQ-NGFW-2 has lower priority (it is higher: 110 > 90).
C is incorrect because a mismatch in the override setting is not what causes the "configuration out of sync" condition shown in get system ha status (that is about synchronized configuration databases, not a requirement that override values must match to remain in-sync).
D is incorrect because HA settings like override/priority are not synchronized in the way regular configuration objects are; they are device-level HA parameters.

From the routing table in the exhibit, there is already a static route for 172.20.1.0/24 pointing out port3 with:
Distance = 9
Priority = 2
Type = Static
In FortiOS, route selection prefers (in order) the route with the lowest administrative distance to a destination. Therefore, to make traffic to 172.20.1.0/24 go through port2 only, the administrator must ensure the port2 static route is more preferred than the existing port3 route.
Why C is correct
C . The existing static route through port3 must have the distance set to 11.
If the existing port3 route distance is increased to 11, then a new port2 route with distance 9 will be preferred (9 < 11). This makes the port3 route a backup route instead of the active one.
Why D is correct
D . The new static route must have the distance set to 9
Setting the new port2 route distance to 9 (and increasing the port3 route to 11 as in option C) ensures FortiGate selects the port2 route as the best route for 172.20.1.0/24.
Why A and B are not correct
A (priority 3): By itself it does not guarantee selection over the existing route, and FortiOS route choice is driven primarily by distance.
B (metric 1): Metric is not the primary selector for static route preference compared to administrative distance in this scenario.
So the two criteria that achieve the objective are:
Make the existing port3 route less preferred by increasing its distance (C) Ensure the new port2 route uses the preferred distance (D)

The exhibit shows a FortiGate UTM application control log with fields such as:
type="utm"
subtype="app-ctrl"
action="block"
policyid=1
appid=30220
appcat="Video/Audio"
service="HTTP"
apprisk="elevated"
This is a forward traffic security log, generated by Application Control applied to a firewall policy.
Why the correct answers are C and D
C . By filtering by policy universally unique identifier (UUID) and application name in the log entry Correct.
FortiOS logs can be viewed and filtered in:
Log & Report → Forward Traffic
Administrators can filter logs using fields such as:
Policy ID / Policy UUID
Application name (app)
Application ID (appid)
The log entry clearly includes application-related fields, making filtering by policy and application a valid and documented way to view these logs.
D . In the Forward Traffic section
Correct.
The log is a UTM Application Control log for traffic passing through a firewall policy.
Such logs are displayed under:
Log & Report → Forward Traffic
This is the standard and correct location to view application control, web filter, IPS, and other security profile logs related to user traffic.
Why the other options are incorrect
A . By right clicking the implicit deny policy
Incorrect.
Implicit deny policies do not generate UTM forward traffic logs like the one shown.
Application control logs are generated only by explicit firewall policies with security profiles enabled.
B . Using the FortiGate CLI command diagnose log test
Incorrect.
diagnose log test is used to test log connectivity and log settings, not to view historical log entries.
It does not display traffic or UTM logs.