Courseiva

Fortinet NSE 7 Advanced Security NSE7 (NSE7) — Questions 451–525

718 questions total · 10 pages · All types, answers revealed

Page 6

Page 7 of 10

Page 8
451
MCQmedium

A FortiGate administrator is using the built-in FortiGuard web filter to block malicious websites. Users report that they can still access a site that is categorized as 'Malware' by FortiGuard. The administrator verifies that the web filter profile is applied to the policy and that the category is set to block. What is the most likely reason for this issue?

A.The web filter profile is set to monitor mode instead of block.
B.The site is using HTTPS and SSL inspection is not enabled.
C.The FortiGuard service is not reachable.
D.The web filter cache has not been updated.
AnswerB

Without SSL inspection, FortiGate cannot see the full URL or the server certificate details for HTTPS traffic, so it cannot apply web filtering based on the category of the site. The web filter may see only the IP address or SNI, which might not be categorized. Enabling SSL inspection allows FortiGate to decrypt and inspect the traffic, enforcing the web filter. This is the most common reason for web filter bypass on HTTPS sites.

Why this answer

The most likely reason is that the site uses HTTPS and SSL inspection is not enabled. FortiGate cannot inspect the encrypted traffic to determine the URL category, so the web filter cannot block it. Enabling SSL inspection allows FortiGate to decrypt and apply the web filter.

Other options like cache, monitor mode, or FortiGuard reachability are less likely given the scenario details. Thus, SSL inspection is the key.

Exam trap

The trap here is assuming that web filtering works on HTTPS without SSL inspection, overlooking the need to decrypt traffic to see the full URL and apply categories.

452
MCQmedium

An administrator configures a WAF profile on FortiGate to protect a web application. However, the administrator notices that SQL injection attacks are not being blocked. What should the administrator check first?

A.The SQL injection signatures are enabled in the WAF profile
B.The WAF profile is attached to the correct firewall policy
C.The FortiGate has a valid Advanced Web Protection subscription
D.The web application is using HTTPS and SSL inspection is configured
AnswerA

SQL injection detection depends on the signature set being active within the WAF profile; if those signatures are disabled, FortiGate inspects traffic but takes no blocking action. Verifying signature status first confirms the detection engine is armed, directly addressing the stem's symptom of attacks passing through unblocked.

Why this answer

SQL injection attacks are blocked by specific signatures within the WAF profile. If these signatures are not enabled, the WAF will not inspect HTTP requests for SQL injection patterns, allowing attacks to pass through. The administrator must verify that the SQL injection signatures are toggled on under the WAF profile's signature configuration.

Exam trap

The trap here is that candidates often assume attaching the WAF profile to a firewall policy is sufficient, overlooking the granular signature enablement required within the profile itself.

How to eliminate wrong answers

Option B is wrong because even if the WAF profile is attached to the correct firewall policy, it will not block SQL injection if the signatures themselves are disabled; the profile attachment is a prerequisite but not the root cause. Option C is wrong because a valid Advanced Web Protection subscription is required for the WAF feature to be available, but if the profile is already configured and applied, the subscription is active; the issue is signature enablement, not licensing. Option D is wrong because HTTPS and SSL inspection affect decryption of traffic, but SQL injection signatures operate on the decrypted HTTP payload; if SSL inspection is not configured, the WAF cannot inspect encrypted traffic, but the question states attacks are not being blocked, implying traffic is reaching the WAF, so the issue is signature enablement, not SSL inspection.

453
MCQeasy

Which of the following best describes the function of FortiDeceptor in an enterprise network?

A.It provides endpoint detection and response (EDR) capabilities on workstations.
B.It deploys decoys and lures to detect attackers inside the network.
C.It acts as a web application firewall for protecting web servers.
D.It provides sandboxing for advanced malware analysis.
AnswerB

FortiDeceptor uses deception technology to detect lateral movement.

454
MCQeasy

A FortiGate administrator is configuring SSL VPN for remote users. The administrator wants to ensure that users can only access specific internal resources based on their user group. Which SSL VPN configuration mode should be used to provide granular access control?

A.Web mode with a portal configured to show only specific bookmarks.
B.Web mode with a realm that maps to an LDAP group.
C.Tunnel mode with firewall policies that match user groups and specific internal subnets.
D.Tunnel mode with split tunneling disabled.
AnswerC

In tunnel mode, the SSL VPN client receives an IP address and routes traffic to internal resources. By creating firewall policies that match user groups and specific destination subnets, the administrator can enforce granular access control. Only users in the allowed groups can reach the defined resources, while others are denied.

Why this answer

SSL VPN tunnel mode combined with firewall policies that reference user groups and specific internal subnets provides granular access control. The firewall policies determine which users can access which resources, based on their group membership. This is the standard method for enforcing least privilege in SSL VPN deployments.

Exam trap

The trap here is thinking that web mode bookmarks or split tunneling settings alone can enforce granular access control, when in fact firewall policies based on user groups and destinations are required.

455
MCQhard

A FortiGate is deployed with two ISPs and SD-WAN. The organization uses OSPF to exchange routes with a remote branch. The administrator notices that the FortiGate is not installing OSPF-learned routes into the routing table. The OSPF configuration is verified to be correct, and neighbors are established. Which configuration could be causing the issue?

A.The SD-WAN health-check is configured with 'update-static-route' and is overriding OSPF routes.
B.The administrative distance of OSPF is set to 200, which is higher than the default 110.
C.A distribute-list configured under OSPF is filtering the routes from being installed.
D.The OSPF interface is configured as 'passive', which prevents route exchange.
AnswerC

A distribute-list applied under OSPF filters routes during installation into the routing table, so neighbours stay established and the config looks valid while prefixes are silently dropped. This directly explains why OSPF-learned routes never appear despite correct adjacency.

Why this answer

A distribute-list applied under OSPF can filter routes from being installed into the routing table even when OSPF neighbors are fully established and the OSPF database contains the routes. This is a common cause of routes being learned but not installed, as the filter operates after the SPF calculation and before route insertion.

Exam trap

The trap here is that candidates assume OSPF neighbors being up and routes appearing in the OSPF database guarantee route installation, but a distribute-list can silently block installation without affecting neighbor adjacency or the LSDB.

How to eliminate wrong answers

Option A is wrong because the SD-WAN health-check with 'update-static-route' only affects static routes, not OSPF-learned routes; it cannot override OSPF routes in the routing table. Option B is wrong because the default administrative distance for OSPF is 110, and setting it to 200 would make OSPF routes less preferred but would not prevent them from being installed if no better route exists; the question states routes are not installed at all, not that they are overridden. Option D is wrong because a passive OSPF interface prevents sending or receiving OSPF hellos and thus prevents neighbor formation, but the question states neighbors are established, so passive configuration cannot be the issue.

456
MCQmedium

An administrator is configuring a FortiGate to block outbound traffic to known malicious IP addresses. They want the block list to be updated automatically from a commercial threat intelligence service that provides a REST API. Which FortiGate feature should be used?

A.FortiGuard IP Reputation service
B.External Threat Feed connector
C.DNS Filter with botnet C&C category
D.Static firewall address objects
AnswerB

The External Threat Feed connector allows the FortiGate to poll an external HTTP/HTTPS server or REST API for a list of malicious IPs or domains. The administrator can configure the connector with the feed URL, refresh interval, and authentication. The fetched entries are stored as a threat feed object that can be referenced in firewall policies or blocklists, enabling automatic updates.

Why this answer

The External Threat Feed connector is designed to ingest IP or domain blocklists from external HTTP/HTTPS sources, including REST APIs. It automates updates and integrates with firewall policies. The other options are either manual, domain-focused, or tied to Fortinet's own reputation service, which cannot be customized to an arbitrary third-party feed.

Exam trap

The trap here is assuming that FortiGuard IP Reputation can be pointed at any external feed, when it is a fixed Fortinet service.

457
MCQhard

An administrator is troubleshooting an SD-WAN rule that is not matching traffic as expected. The rule is configured with a source address of 'all', destination '10.0.0.0/24', and service 'HTTP'. The rule is placed after a rule that matches all traffic to '10.0.0.0/24' with service 'ALL'. The administrator notices that HTTP traffic to 10.0.0.0/24 is being handled by the first rule. What is the most likely cause?

A.The SD-WAN rule with service 'ALL' has a higher priority value, which overrides the order of rules.
B.SD-WAN rules are evaluated in order, and the first matching rule is applied. The rule with service 'ALL' matches HTTP traffic, so it takes precedence.
C.The HTTP rule is not matching because the service 'HTTP' is not defined in the SD-WAN rule; the administrator must use 'ALL' for web traffic.
D.SD-WAN rules are evaluated based on the most specific match, so the HTTP rule should take precedence regardless of order.
AnswerB

SD-WAN rules are evaluated sequentially from top to bottom. The first rule matches all services, including HTTP, so it captures the traffic before the more specific rule is evaluated. To fix this, the administrator should reorder the rules so that the HTTP-specific rule is above the generic rule.

Why this answer

SD-WAN rules are processed in the order they are listed, and the first rule that matches the traffic is used. In this case, the rule with service 'ALL' matches HTTP traffic before the HTTP-specific rule is evaluated. The solution is to move the HTTP rule above the generic rule.

Exam trap

The trap here is assuming that SD-WAN rules use a most-specific-match logic like firewall policies, when in fact they are order-dependent.

458
Multi-Selecteasy

An administrator wants to enforce that only devices with the latest antivirus signatures and a corporate disk encryption solution can access a sensitive application via ZTNA. Which two FortiClient EMS components must be configured? (Choose two.)

Select 2 answers
A.Device posture checks
B.VPN tunnels
C.SAML SSO
D.ZTNA tags
AnswersA, D

Device posture checks in FortiClient EMS evaluate endpoint compliance conditions such as antivirus signature currency and disk encryption status. They produce the compliance result that ZTNA enforcement then uses to permit or deny access to the sensitive application.

Why this answer

Option A (Device posture checks) is correct because posture checks in FortiClient EMS evaluate endpoint compliance conditions such as antivirus signature currency and disk encryption status, which are exactly the requirements the administrator wants to enforce. Option D (ZTNA tags) is correct because FortiClient EMS dynamically assigns ZTNA tags to endpoints based on posture results, and these tags are then used in ZTNA firewall policies to allow or deny access to the sensitive application. Together, posture checks generate the compliance data and ZTNA tags translate that data into enforceable access control.

Option B (VPN tunnels) is not needed because ZTNA provides application-level access without requiring a traditional VPN tunnel. Option C (SAML SSO) is an identity authentication mechanism and does not by itself verify antivirus signatures or disk encryption compliance.

459
Drag & Dropmedium

Drag and drop the steps to configure a FortiGate as a DHCP server into the correct order.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

The correct sequence to configure a FortiGate as a DHCP server is: first select the interface that will serve DHCP, then enable DHCP on that interface, set the IP address scope (range), configure additional options such as default gateway and DNS servers, and finally apply the configuration. This order ensures dependencies are met and the configuration is valid.

460
MCQeasy

Which Fortinet product is designed specifically to detect and deceive attackers by creating decoy systems and luring them away from real assets?

A.FortiDeceptor
B.FortiSandbox
C.FortiEDR
D.FortiWeb
AnswerA

FortiDeceptor deploys decoy systems, services and tokens that mimic genuine assets, so any interaction with them signals malicious reconnaissance. It then deceives attackers by luring them away from production resources while generating high-fidelity alerts, directly satisfying the requirement for a product built specifically for deception rather than prevention or detection alone.

Why this answer

FortiDeceptor is Fortinet's dedicated deception-based threat detection solution. It creates realistic decoy systems (honeypots) and lures attackers away from real assets, providing early detection and threat intelligence without relying on signatures. This aligns with the question's specific requirement for a product designed to detect and deceive attackers using decoys.

Exam trap

The trap here is that candidates often confuse FortiSandbox's sandboxing (which also uses isolated environments) with deception technology, but sandboxing analyzes files while deception lures attackers with decoys.

How to eliminate wrong answers

Option B (FortiSandbox) is wrong because it is a malware analysis and detection platform that executes suspicious files in a sandboxed environment to identify threats, not a deception technology that creates decoy systems. Option C (FortiEDR) is wrong because it focuses on endpoint detection, response, and real-time threat hunting on endpoints, not on deploying decoys to lure attackers. Option D (FortiWeb) is wrong because it is a web application firewall (WAF) that protects web servers from application-layer attacks, not a deception-based system for luring attackers away from assets.

461
MCQmedium

An administrator configures a prefix list to filter routes received from a BGP neighbor. The prefix list permits 192.168.0.0/16 le 24. Which routes are permitted?

A.Only routes with prefix length exactly 16 within 192.168.0.0/16
B.Only routes with prefix length exactly 24 within 192.168.0.0/16
C.Any route with prefix length greater than 24 within 192.168.0.0/16
D.Any route with prefix length between 16 and 24 inclusive, starting with 192.168
AnswerD

The `le 24` operator extends the match beyond the /16 network to any more-specific prefix up to and including /24, so 192.168.0.0/16 through 192.168.1.0/24 all qualify. Routes with prefix lengths of 25 or greater, and any prefix outside the 192.168 range, are denied.

Why this answer

The prefix list `192.168.0.0/16 le 24` permits any route that matches the prefix `192.168.0.0/16` and has a prefix length between 16 and 24 inclusive. The `le` (less-than-or-equal-to) operator sets the maximum prefix length, so routes with lengths 16, 17, 18, 19, 20, 21, 22, 23, and 24 are all allowed, as long as they fall within the 192.168.0.0/16 network.

Exam trap

The trap here is that candidates often misinterpret `le 24` as meaning 'length exactly 24' or 'lengths less than 24', when in fact it means 'lengths from the network prefix length up to and including 24'.

How to eliminate wrong answers

Option A is wrong because it incorrectly restricts the prefix length to exactly 16, ignoring the `le 24` modifier that permits longer prefixes up to 24. Option B is wrong because it incorrectly restricts the prefix length to exactly 24, ignoring the base prefix length of 16 and the range allowed by `le`. Option C is wrong because it states prefix lengths greater than 24 are permitted, but `le 24` explicitly limits the maximum prefix length to 24, so lengths 25 or longer are denied.

462
MCQeasy

A FortiGate administrator is configuring a ZTNA rule to allow access to an internal web application only for users who authenticate with multi-factor authentication (MFA). The administrator has configured the ZTNA rule to require the 'MFA' tag from FortiClient EMS. However, users who have MFA enabled are still being denied access. What is the most likely reason?

A.The users are not using the correct SSL VPN client to connect.
B.The ZTNA rule is not applied to the correct user group.
C.The ZTNA rule is configured to use the wrong authentication scheme.
D.The 'MFA' tag is not being synchronized from FortiClient EMS to the FortiGate.
AnswerD

ZTNA relies on tags from FortiClient EMS to enforce compliance. If the 'MFA' tag is not synchronized, the FortiGate will not see that the user has MFA enabled, and the ZTNA rule will deny access. The administrator should verify that the EMS connector is properly configured and that the tag is being synchronized. This is a common issue when the EMS integration is not fully functional or when the tag is not correctly assigned in EMS.

Why this answer

ZTNA rules enforce access based on tags from FortiClient EMS. If the 'MFA' tag is not synchronized to the FortiGate, the rule cannot verify that the user has MFA, resulting in denial. The administrator must ensure the EMS connector is working and the tag is correctly assigned.

Other options would produce different symptoms.

Exam trap

The trap here is assuming that MFA configuration on the endpoint automatically grants the tag, without verifying that the tag is synchronized to the FortiGate.

463
MCQeasy

An administrator wants to ensure that FortiGate validates the identity of the remote VPN peer using a certificate during IKEv2 phase 1. Which authentication method should the administrator select in the IPsec phase 1 configuration?

A.Aggressive mode
B.Pre-shared key
C.EAP
D.Signature (RSA)
AnswerD

Signature (RSA) makes FortiGate verify the peer's certificate during IKEv2 phase 1, satisfying the requirement for certificate-based peer identity validation. The remote gateway proves possession of its private key by signing the IKEv2 exchange, and FortiGate validates that signature against a trusted CA certificate.

Why this answer

Selecting Signature (RSA) in the IPsec phase 1 configuration enables the FortiGate to use digital certificates for authentication, where the remote peer's identity is validated using its certificate. This meets the requirement of validating the identity of the remote VPN peer using a certificate during IKEv2 phase 1.

Exam trap

NSE7 often tests the confusion between authentication methods and exchange modes; candidates may select Aggressive mode thinking it provides certificate authentication, but it is just a mode.

How to eliminate wrong answers

Option A is wrong because Aggressive mode is an IKE phase 1 exchange mode, not an authentication method; it can be used with pre-shared keys or certificates but does not itself provide certificate validation. Option B is wrong because Pre-shared key uses a shared secret for authentication, not certificates. Option C is wrong because EAP (Extensible Authentication Protocol) is typically used for user authentication, often with RADIUS, and does not inherently use certificates for peer identity validation in IKEv2 phase 1.

464
MCQmedium

An administrator needs to ensure that all firewall policies in a FortiGate VDOM have a common set of inspection profiles added at the end of the policy list. Which FortiManager feature best achieves this?

A.ADOM overrides
B.Central SNAT
C.Revision history
D.Policy package header/footer policies
AnswerD

Header and footer policies in a policy package are automatically prepended or appended to every policy in the package, so a common inspection profile set is applied consistently across all VDOM policies without editing each rule individually. This satisfies the requirement to add profiles at the end of the policy list.

Why this answer

Policy package header/footer policies in FortiManager allow you to define a set of policies that are automatically appended (or prepended) to every policy package within an ADOM or VDOM. This ensures that all firewall policies in the VDOM share a common set of inspection profiles at the end of the policy list, without manually editing each policy. It is the only feature designed specifically for this use case.

Exam trap

The trap here is that candidates often confuse ADOM overrides (which manage per-ADOM exceptions) with the ability to insert common policies, but only header/footer policies guarantee automatic placement at the end of every policy list in a VDOM.

How to eliminate wrong answers

Option A is wrong because ADOM overrides are used to apply configuration changes across multiple ADOMs or VDOMs, not to insert common inspection profiles at the end of a policy list. Option B is wrong because Central SNAT is a feature for centralized source NAT policy management, unrelated to inspection profiles or policy ordering. Option C is wrong because Revision history is a versioning and rollback feature, not a mechanism for adding common policies or profiles.

465
MCQeasy

A network administrator needs to configure SD-WAN on a FortiGate to distribute traffic across two WAN links based on session count. Which load balancing algorithm should be selected in the SD-WAN rule?

A.Volume
B.Lowest-cost
C.Spillover
D.Sessions
AnswerD

The Sessions algorithm distributes traffic according to the number of active sessions on each member, directly matching the session-count requirement. Source-IP, volume and spillover balance on different metrics, so they would not satisfy the stated constraint.

Why this answer

The 'Sessions' load balancing algorithm distributes new sessions across SD-WAN members based on the current session count, ensuring an even distribution of sessions. This directly matches the requirement to distribute traffic based on session count, as it selects the member with the fewest active sessions for each new session.

Exam trap

The trap here is confusing 'Sessions' with 'Volume' or 'Spillover', as candidates often assume bandwidth-based algorithms (like Volume) are the default for session distribution, but FortiGate's SD-WAN explicitly separates session count from byte volume in its load balancing options.

How to eliminate wrong answers

Option A is wrong because 'Volume' distributes traffic based on the total bytes transferred, not session count. Option B is wrong because 'Lowest-cost' selects the link with the lowest cost (based on cost metric), not session count. Option C is wrong because 'Spillover' forwards traffic to a primary link until a configured bandwidth threshold is exceeded, then spills over to a backup link, which is unrelated to session count.

466
MCQhard

An administrator is configuring ZTNA inline CASB for a SaaS application. The goal is to block upload of files containing credit card numbers. Which configuration components are required?

A.Use FortiClient to enforce DLP on endpoints
B.Configure an IPsec VPN between FortiGate and the SaaS provider
C.Configure a ZTNA application with a CASB profile and SSL inspection
D.Configure a web filter profile with DLP sensor
AnswerC

SSL inspection decrypts the TLS session so the CASB profile can inspect file payloads for credit card patterns before upload completes. Without decryption, the traffic is opaque and data-loss rules cannot match content. The ZTNA application binds the CASB profile to the SaaS destination, satisfying the inline blocking requirement.

Why this answer

ZTNA inline CASB for a SaaS application requires configuring a ZTNA application entry that includes a CASB profile and SSL inspection. The CASB profile defines the DLP rules (e.g., blocking credit card numbers), and SSL inspection decrypts the traffic so the CASB can inspect file uploads. This combination is the required configuration to enforce inline DLP on SaaS uploads.

Exam trap

NSE7 often tests the misconception that endpoint DLP or web filtering alone can enforce SaaS DLP — candidates must recognize that inline CASB requires ZTNA application configuration, a CASB profile, and SSL inspection to inspect encrypted SaaS traffic.

How to eliminate wrong answers

Option A is wrong because FortiClient endpoint DLP enforces data loss prevention on the endpoint, not inline CASB inspection of SaaS traffic, and does not meet the requirement for inline CASB blocking of uploads. Option B is wrong because an IPsec VPN between FortiGate and the SaaS provider is not a supported or practical configuration for SaaS CASB; SaaS providers do not terminate customer IPsec tunnels for this purpose. Option D is wrong because a web filter profile with a DLP sensor is used for web traffic filtering and DLP on HTTP/HTTPS, but it does not provide the CASB-specific application control and inline inspection needed for SaaS applications like the ZTNA CASB profile does.

467
MCQmedium

A FortiGate is managed by FortiManager. The administrator creates a new policy package for VDOM 'Sales' and installs it. Later, they find that the previous configuration has been overwritten. What should the administrator do to avoid this in the future?

A.Set the FortiGate to backup mode
B.Enable auto-lock on the policy package
C.Use the install preview before applying the changes
D.Enable revision history
AnswerC

Install preview compares the pending policy package against the FortiGate's running configuration, displaying added, modified and removed objects before committing. This satisfies the scenario's requirement to detect that installing the package would overwrite existing VDOM 'Sales' settings, letting the administrator reconcile differences first rather than discovering the loss afterwards.

Why this answer

Using the install preview allows the administrator to review the exact changes that will be applied to the FortiGate before committing them. This prevents accidental overwrites by showing a diff of the configuration, enabling the administrator to verify that the new policy package will not replace existing settings unintentionally.

Exam trap

The trap here is that candidates confuse revision history (which is post-hoc) with install preview (which is proactive), or mistakenly think auto-lock prevents overwrites when it only serializes administrative edits.

How to eliminate wrong answers

Option A is wrong because backup mode on FortiGate is used for disaster recovery or firmware upgrades, not for preventing configuration overwrites during policy package installation from FortiManager. Option B is wrong because auto-lock on a policy package prevents concurrent edits by multiple administrators, but does not prevent the installation process from overwriting the existing configuration. Option D is wrong because revision history tracks changes over time for rollback purposes, but does not provide a pre-installation review to avoid overwriting the current configuration.

468
Multi-Selectmedium

A network admin needs to configure a FortiGate to load balance traffic across two ISP links using SD-WAN. The requirement is to use both links simultaneously for different sessions based on source-destination IP hash. Which two settings are required? (Select TWO.)

Select 2 answers
A.Create an SD-WAN zone with both WAN members
B.Configure an SD-WAN rule with load balancing algorithm 'source-dest-ip-hash'
C.Add a performance SLA for each member
D.Set the rule strategy to 'best quality'
E.Enable 'spillover' under the SD-WAN rule
AnswersA, B

An SD-WAN zone groups the two WAN interfaces as members, which is the prerequisite for any SD-WAN rule to reference them. Without the zone, the load-balancing rule cannot bind both ISP links, so this satisfies the requirement to use both links simultaneously.

Why this answer

Option A is correct because SD-WAN load balancing requires the WAN interfaces to be grouped into an SD-WAN zone, which serves as the logical interface containing both ISP members that traffic can be distributed across. Option B is correct because the requirement explicitly states sessions must be distributed based on a source-destination IP hash, and the SD-WAN rule's load-balance algorithm must be set to 'source-dest-ip-hash' to achieve per-session hashing across both links simultaneously. Option C is not required because a performance SLA is only needed for quality-based or SLA-driven steering, not for pure hash-based load balancing.

Option D is incorrect because the 'best quality' strategy selects a single best link based on SLA metrics rather than distributing sessions across both links. Option E is incorrect because spillover is a strategy used to send traffic to a secondary link only when the primary exceeds a threshold, which does not satisfy the requirement of using both links simultaneously for different sessions.

Exam trap

The trap here is that candidates often confuse 'load balancing algorithm' (like source-dest-ip-hash) with 'strategy' (like best quality) or assume that performance SLAs are mandatory for any SD-WAN rule, when in fact SLAs are only needed for dynamic path selection based on link quality.

469
MCQmedium

A FortiGate administrator is troubleshooting an IPsec VPN where Phase 1 completes but Phase 2 fails to establish. The administrator reviews the Phase 2 configuration and notices that the local and remote subnets do not match between the two peers. Which action should the administrator take to resolve the Phase 2 failure?

A.Increase the Phase 1 lifetime so the tunnel stays up longer during renegotiation.
B.Adjust the Phase 2 selectors on both peers so the local and remote subnet definitions mirror each other.
C.Enable PFS on both peers and set the same Diffie-Hellman group.
D.Change the Phase 1 authentication method from pre-shared key to certificates on both peers.
AnswerB

Phase 2 selectors define which traffic is encrypted. If the local subnet on one peer does not correspond to the remote subnet on the other, the proposal does not match and Phase 2 fails. Aligning the selectors so each peer's local subnet equals the other's remote subnet resolves the mismatch and allows the child SA to establish.

Why this answer

Phase 2 selectors must mirror each other: one peer's local subnet must equal the other peer's remote subnet. When they do not match, the child SA negotiation fails even though Phase 1 succeeds. Aligning the selectors on both peers restores the correct traffic selectors and allows Phase 2 to complete.

Exam trap

The trap here is assuming Phase 2 failures are caused by Phase 1 settings, when a selector mismatch is the actual cause.

470
MCQmedium

An organization uses FortiWeb to protect its web applications. The security team wants to block requests that contain a specific custom pattern in the URL. Which feature should be used?

A.Inline Protection Profile
B.Custom Attack Signature
C.URL Access Rule
D.Web Application Firewall Policy
AnswerB

A custom attack signature matches arbitrary byte sequences, including regex patterns, against request URLs, so it satisfies the requirement to block a specific custom pattern. Unlike predefined signatures, it lets you define the exact match condition, then apply it in a protection profile with the action set to block.

Why this answer

Custom Attack Signatures in FortiWeb allow administrators to define user-specific patterns to match against HTTP request elements, including the URL. This feature is designed to block requests containing custom patterns, such as a specific string in the URL, by inspecting the request and triggering an action (e.g., alert or block) when the pattern is matched. Unlike other features, Custom Attack Signatures provide the granularity needed to detect and block arbitrary, organization-defined patterns in the URL.

Exam trap

The trap here is that candidates often confuse URL Access Rules (which control access based on URL paths) with Custom Attack Signatures (which detect arbitrary patterns in the URL), leading them to select URL Access Rule when the requirement is to block a specific custom pattern, not to restrict access to a directory.

How to eliminate wrong answers

Option A is wrong because Inline Protection Profiles are used to apply a set of predefined protection rules (e.g., SQL injection, XSS) to traffic, but they do not support the creation of custom patterns for URL matching. Option C is wrong because URL Access Rules control access based on URL path patterns (e.g., allow or deny access to specific directories), but they are not designed to block requests based on arbitrary custom patterns within the URL; they operate on access control logic, not attack signature matching. Option D is wrong because a Web Application Firewall Policy defines the overall security policy (e.g., which protections are enabled), but it does not itself contain the mechanism to define and match custom patterns in the URL; that is the role of signatures or rules within the policy.

471
MCQmedium

A FortiGate is configured with multiple VDOMs. The administrator wants to enable inter-VDOM routing between VDOM-A and VDOM-B. The administrator creates an inter-VDOM link and assigns IP addresses to both ends. Which additional configuration is required to allow traffic to pass between the VDOMs?

A.Enable inter-VDOM routing globally under System > Settings.
B.Create a firewall policy in VDOM-A allowing traffic from the source interface to the inter-VDOM link interface, and a policy in VDOM-B allowing traffic from the inter-VDOM link interface to the destination interface.
C.Assign both inter-VDOM link interfaces to the same zone.
D.Configure a static route in each VDOM pointing to the inter-VDOM link, and enable 'allow inter-VDOM traffic' on the link.
AnswerB

Inter-VDOM link traffic is inspected by the firewall in each VDOM. Therefore, you need a policy in the source VDOM that permits traffic from the internal interface to the inter-VDOM link interface, and a policy in the destination VDOM that permits traffic from the inter-VDOM link interface to the destination interface. This two-policy requirement is mandatory. Without both policies, the FortiGate drops the traffic even if routing is correct. This is the standard configuration for inter-VDOM routing.

Why this answer

To enable inter-VDOM routing, you must create an inter-VDOM link and assign IP addresses. Then, you must add firewall policies in each VDOM to permit traffic across the link. Specifically, a policy in the source VDOM allowing traffic from the internal interface to the inter-VDOM link interface, and a policy in the destination VDOM allowing traffic from the inter-VDOM link interface to the destination interface.

These policies are required because each VDOM inspects traffic independently.

Exam trap

The trap here is thinking that creating the inter-VDOM link and adding routes is enough, when in fact firewall policies in both VDOMs are also required.

472
MCQeasy

What is the primary purpose of Content Disarm and Reconstruction (CDR) in advanced antivirus protection?

A.To detect and block known malware using signature-based detection
B.To reconstruct files by removing potentially malicious active content such as macros and scripts
C.To submit files to FortiSandbox for behavioral analysis
D.To encrypt files in transit to prevent interception
AnswerB

CDR strips active content such as macros, scripts and embedded objects from files, then rebuilds a clean, functional version, neutralising threats that signature-based detection may miss. This satisfies the requirement to remove potentially malicious active content rather than merely quarantine or block the file.

Why this answer

Content Disarm and Reconstruction (CDR) is designed to proactively neutralize threats by stripping or disabling potentially dangerous active content—such as macros, scripts, and embedded objects—from files while preserving the file's usability. Unlike signature-based detection, CDR does not rely on known threat signatures; instead, it reconstructs the file in a safe state, removing any elements that could execute malicious code. This makes CDR a zero-day prevention technique that blocks threats before they can be analyzed or detected by traditional methods.

Exam trap

The trap here is that candidates confuse CDR with sandboxing or signature-based detection, assuming CDR's purpose is to detect malware rather than to preemptively remove all potentially dangerous content regardless of detection status.

How to eliminate wrong answers

Option A is wrong because CDR does not use signature-based detection; it removes active content regardless of whether the content is known malware, making it effective against unknown and zero-day threats. Option C is wrong because while CDR can be used in conjunction with FortiSandbox, its primary purpose is not to submit files for behavioral analysis but to sanitize files at the gateway before delivery. Option D is wrong because encrypting files in transit is a data protection measure (e.g., TLS or IPsec) unrelated to CDR's function of removing malicious content from files.

473
MCQhard

A BGP peering between two FortiGates is not establishing. The administrator runs 'get router info bgp neighbor' and sees that the neighbor state is 'Idle' and the BGP configuration appears correct. What should the administrator check next?

A.Run 'diagnose ip router bgp all enable' to enable debug
B.Check the BGP AS number configuration
C.Verify that the BGP neighbor IP is reachable via the routing table
D.Increase the BGP timers
AnswerC

An Idle BGP state means the router cannot reach the neighbour, so the TCP session never opens. Verifying the neighbour IP is reachable in the routing table confirms whether a missing or incorrect route is blocking the peering, before checking timers or authentication.

Why this answer

When a BGP neighbor is stuck in the 'Idle' state, it typically indicates that BGP cannot initiate the TCP connection to the neighbor. The most common cause is that the neighbor IP address is not reachable via the routing table. Even if the BGP configuration (AS number, neighbor IP) is correct, BGP will remain Idle until it can successfully open a TCP session on port 179.

Therefore, verifying IP reachability (e.g., with 'ping' or checking the routing table) is the logical next step.

Exam trap

The trap here is that candidates often jump to debugging or assume a configuration error (like AS number mismatch) when the neighbor state is Idle, but the most fundamental cause—IP reachability—is frequently overlooked.

How to eliminate wrong answers

Option A is wrong because enabling BGP debug ('diagnose ip router bgp all enable') is a troubleshooting step that should be taken after verifying basic connectivity; it generates excessive output and is not the first check for an Idle state. Option B is wrong because the question states that the BGP configuration appears correct, so checking the AS number again is redundant and unlikely to resolve the issue. Option D is wrong because increasing BGP timers (keepalive/hold) only affects established sessions or session stability, not the initial TCP connection establishment; it will not move a session out of Idle.

474
MCQmedium

During a failover test in an HA cluster, the primary FortiGate fails over to the secondary. After failover, some existing TCP sessions are dropped. What is the MOST likely reason?

A.The failover caused a routing change
B.The session TTL expired during failover
C.The HA mode is active-passive
D.Session pickup is not enabled on the HA cluster
AnswerD

Without session pickup, the secondary FortiGate has no synchronised session table, so established TCP flows cannot be matched after failover and are dropped. Enabling session pickup replicates session state, preserving existing connections across the failover event.

Why this answer

In an HA cluster, session pickup (also known as session synchronization) is responsible for replicating session tables from the primary FortiGate to the secondary. When failover occurs, if session pickup is not enabled, the secondary FortiGate has no knowledge of existing TCP sessions, causing them to be dropped. This is the most likely reason because the secondary device cannot forward traffic for sessions it does not recognize, even if the network topology remains unchanged.

Exam trap

The trap here is that candidates often assume active-passive HA always drops sessions or that routing changes are the default cause, but Fortinet specifically tests that session pickup must be explicitly enabled to preserve TCP sessions during failover.

How to eliminate wrong answers

Option A is wrong because a routing change during failover is not inherent to HA failover itself; FortiGate HA typically uses virtual MAC addresses and floating IPs to maintain consistent routing, so sessions are not dropped due to routing changes unless the network is misconfigured. Option B is wrong because session TTL (time-to-live) expiration is not a typical cause during a controlled failover; session TTLs are usually long enough to survive the brief failover transition, and the issue is specifically about session state not being transferred. Option C is wrong because active-passive HA mode does not inherently cause session drops; in fact, active-passive HA with session pickup enabled can maintain sessions, and the mode alone is not the reason for dropped sessions—the missing feature is session synchronization.

475
MCQhard

A FortiGate is configured with a VIP (virtual IP) to publish an internal web server to the internet. External users report that they cannot access the web server, but internal users can access it using its private IP. The administrator runs 'diagnose debug flow' and sees that traffic from external users is being dropped with the message 'iprope_in_check() check failed, drop'. What is the most likely cause?

A.The firewall policy allowing access to the VIP does not have NAT enabled.
B.The firewall policy allowing access to the VIP is missing or placed after a deny policy.
C.There is an asymmetric routing issue or the return route is not via the FortiGate.
D.The VIP is not configured with the correct external interface.
AnswerB

The debug message 'iprope_in_check() check failed, drop' indicates that the traffic was dropped during the ingress policy check, often because no matching policy was found or a deny policy was matched. If the policy allowing access to the VIP is missing or is placed after a deny policy, external traffic would be dropped. This is a common cause when VIP access fails while internal access works. Therefore, this is the most likely cause.

Why this answer

The debug message 'iprope_in_check() check failed, drop' indicates that the traffic was dropped during the ingress policy check. This typically happens when no firewall policy matches the traffic or when a deny policy is matched before an allow policy. In this scenario, external users cannot access the VIP, but internal users can, suggesting the VIP itself is working.

The most likely cause is that the firewall policy allowing external access to the VIP is missing, disabled, or incorrectly ordered. The administrator should verify the policy configuration and order.

Exam trap

The trap here is interpreting the iprope_in_check failure as an RPF issue, but it often means no matching policy or a deny policy was hit first.

476
MCQmedium

An organization wants to implement a solution that can detect and automatically respond to threats across multiple Fortinet security products. Which product should they use?

A.FortiManager
B.FortiSIEM
C.FortiSOAR
D.FortiAnalyzer
AnswerC

FortiSOAR provides security orchestration, automation and response, ingesting events from FortiGate, FortiMail and other Fortinet products via playbooks and connectors. This satisfies the stem's requirement to detect and automatically respond across multiple Fortinet security products, which standalone management tools cannot orchestrate.

Why this answer

FortiSOAR is the correct choice because it is a security orchestration, automation, and response (SOAR) platform designed to ingest alerts from multiple Fortinet products (e.g., FortiGate, FortiSIEM, FortiMail) and execute automated playbooks for threat detection and response. Unlike management or analytics tools, FortiSOAR provides the cross-product incident response and automation capabilities required to detect and automatically respond to threats across the Fortinet security fabric.

Exam trap

The trap here is that candidates often confuse FortiManager or FortiAnalyzer as the automation hub, but FortiSOAR is the only product specifically designed for cross-product automated threat response, while FortiManager focuses on configuration management and FortiAnalyzer on log analytics.

How to eliminate wrong answers

Option A is wrong because FortiManager is a centralized management platform for deploying and managing Fortinet device configurations and policies, not for detecting or automatically responding to threats across products. Option B is wrong because FortiSIEM is a security information and event management (SIEM) system that collects and correlates logs for threat detection and compliance, but it lacks native automated response orchestration across multiple Fortinet products. Option D is wrong because FortiAnalyzer is a log aggregation and reporting appliance that provides analytics and forensics, but it does not have built-in automation and response capabilities to act on detected threats.

477
MCQhard

An administrator has configured FortiSandbox integration with FortiGate. Files are being submitted, but the firewall is not blocking subsequent downloads of files that FortiSandbox later identifies as malicious. The administrator verifies that the FortiSandbox license is valid and the connection is up. Which configuration is most likely missing?

A.The SSL inspection profile is not set to deep inspection.
B.The 'Retrieve and block' option is not enabled in the antivirus profile.
C.FortiSandbox is not configured as a fabric connector in Security Fabric.
D.The FortiSandbox appliance is not in the 'block' mode.
AnswerB

In the antivirus profile, the 'Retrieve and block' setting allows FortiGate to query FortiSandbox for verdicts on files that were previously submitted. If it is disabled, the firewall will not block files that FortiSandbox later marks as malicious. Enabling it ensures that verdicts are pulled and applied to subsequent traffic.

Why this answer

The 'Retrieve and block' option in the antivirus profile is responsible for pulling verdicts from FortiSandbox and blocking files that are later found malicious. Without it, FortiGate only submits files and does not act on subsequent verdicts. The other options address different aspects of integration or inspection and are not the cause of the described behavior.

Exam trap

The trap here is assuming that because files are submitted, the integration is complete, when in fact the retrieval of verdicts requires a separate setting.

478
MCQeasy

What is the primary purpose of FortiGuard Outbreak Prevention service?

A.To provide proactive protection against zero-day and fast-spreading threats
B.To provide real-time threat intelligence feeds to third-party SIEM systems
C.To automatically patch vulnerabilities in FortiGate firmware
D.To block all traffic from IP addresses listed in a community-based blocklist
AnswerA

FortiGuard Outbreak Prevention delivers proactive, pre-emptive signatures and threat intelligence against zero-day exploits and fast-spreading outbreaks before conventional signatures exist. This directly satisfies the stem's requirement for proactive protection, distinguishing it from reactive antivirus or IPS updates that depend on known, already-catalogued threat signatures.

Why this answer

FortiGuard Outbreak Prevention is designed to provide proactive protection against zero-day and fast-spreading threats by leveraging real-time threat intelligence from FortiGuard Labs. It automatically updates security policies and signatures to block emerging threats before they become widespread, reducing the window of vulnerability.

Exam trap

The trap here is that candidates often confuse Outbreak Prevention with general threat intelligence feeds or community blocklists, but the service specifically targets automated, proactive blocking of fast-spreading threats before signatures are fully developed.

How to eliminate wrong answers

Option B is wrong because FortiGuard Outbreak Prevention is not primarily for feeding threat intelligence to third-party SIEM systems; that function is served by FortiSIEM or FortiAnalyzer via syslog or API integrations. Option C is wrong because FortiGuard Outbreak Prevention does not patch FortiGate firmware; firmware patching is handled through FortiGuard Firmware Update service or manual upgrade processes. Option D is wrong because it does not rely on a community-based blocklist; instead, it uses curated, dynamic threat intelligence from FortiGuard Labs, not user-contributed lists.

479
MCQmedium

A network administrator is troubleshooting an IPsec VPN tunnel between two FortiGates. The tunnel is up but traffic is not passing. The administrator runs 'diagnose vpn ike gateway list' and sees that the IKE SA has been established. However, 'diagnose vpn tunnel list' shows no IPsec SA entries. What is the most likely cause?

A.The firewall policies are not configured to allow traffic through the tunnel
B.The phase 2 proposal (encryption, authentication, etc.) does not match between peers
C.The pre-shared key on both sides does not match
D.The interface MTU is set too low
AnswerB

A phase 2 mismatch prevents the IPsec SA from being negotiated, so Quick Mode fails while the IKE SA stays up. That matches the stem exactly: `diagnose vpn ike gateway list` shows an established IKE SA, but `diagnose vpn tunnel list` shows no IPsec SA entries. Phase 1 selectors and proposals are not the constraint here.

Why this answer

If the IKE SA is established but no IPsec SA entries appear in 'diagnose vpn tunnel list', the most likely cause is a Phase 2 proposal mismatch. Phase 1 (IKE SA) negotiates the secure channel, while Phase 2 (IPsec SA) negotiates the actual tunnel parameters. If the encryption, authentication, or other Phase 2 settings do not match, the IPsec SA will fail to establish, even though Phase 1 is up.

Exam trap

NSE7 often tests the distinction between Phase 1 and Phase 2 failures, so candidates may incorrectly blame firewall policies or pre-shared keys when the IKE SA is already up, missing that Phase 2 mismatch is the cause of missing IPsec SAs.

How to eliminate wrong answers

Option A is wrong because firewall policies affect traffic flow, not the establishment of IPsec SAs; if policies were missing, the tunnel could still be up but traffic would be blocked. Option C is wrong because a pre-shared key mismatch would prevent Phase 1 from establishing, so the IKE SA would not be up. Option D is wrong because MTU issues affect packet fragmentation and traffic flow, not the creation of IPsec SAs.

480
MCQhard

An administrator configures a hub-and-spoke ADVPN with FortiGate at the hub and multiple remote sites. After setup, spokes establish shortcuts directly. However, traffic between two spokes consistently goes through the hub even though shortcuts should exist. Running 'diagnose npu np6 ipsec peercache' shows no shortcut entries. What is the MOST likely reason?

A.The spokes are not running BGP over the ADVPN tunnels.
B.The firewall policies on the spokes do not allow shortcut traffic.
C.Shortcut tunnels are disabled on the hub phase1 configuration.
D.The network processor (NP6) is not enabled for IPsec acceleration.
AnswerA

Shortcuts require BGP to advertise spoke routes across the ADVPN overlay; without it, the hub cannot signal peers to build direct tunnels, so no shortcut entries appear in the NP6 peercache. The stem's missing shortcut condition is therefore explained by absent BGP peering between spokes.

Why this answer

In a hub-and-spoke ADVPN, BGP is required to propagate the spoke's private IP addresses (used as tunnel endpoints) across the overlay network. Without BGP, spokes do not learn each other's tunnel IPs, so they cannot initiate shortcut tunnels. The 'diagnose npu np6 ipsec peercache' command shows no shortcut entries because the shortcut negotiation never starts.

Exam trap

The trap here is that candidates often assume shortcut tunnels are automatically established once ADVPN is configured, overlooking the critical requirement of a dynamic routing protocol (BGP) to exchange tunnel endpoint addresses between spokes.

How to eliminate wrong answers

Option B is wrong because firewall policies on spokes control traffic forwarding, not the establishment of shortcut tunnels; if shortcuts are not formed, traffic will be forwarded via the hub regardless of policies. Option C is wrong because shortcut tunnels are enabled by default on the hub phase1 configuration, and disabling them would prevent all shortcut creation, but the question states shortcuts should exist, implying the hub configuration is correct. Option D is wrong because NP6 IPsec acceleration is a hardware offload feature that affects performance, not the control-plane logic of shortcut tunnel establishment.

481
MCQeasy

An organization wants to prevent users from downloading malicious files from the internet. Which FortiGate security profile should be applied to the outbound firewall policy to block files based on their hash if they have been identified as malicious by FortiSandbox?

A.Application Control profile
B.IPS profile
C.Antivirus profile
D.Web Filter profile
AnswerC

The antivirus profile performs hash-based checks against FortiSandbox verdicts, blocking files already identified as malicious. Applied to the outbound policy, it inspects downloaded files and drops those matching known malicious hashes, directly satisfying the requirement to block downloads by hash.

Why this answer

The Antivirus profile is the correct choice because it integrates with FortiSandbox to block files based on their hash when identified as malicious. FortiGate's antivirus engine can submit files to FortiSandbox for analysis, and if the file's hash matches a known malicious signature, the antivirus profile will block the download. This is specifically designed for file-based threat detection at the application layer, unlike other profiles that focus on different security functions.

Exam trap

The trap here is that candidates may confuse the Antivirus profile with the Web Filter profile, thinking that web filtering handles all malicious content, but web filtering only controls URL access, not file hash-based blocking.

How to eliminate wrong answers

Option A is wrong because Application Control profiles manage and filter network traffic based on application signatures (e.g., Facebook, YouTube), not file hash-based blocking. Option B is wrong because IPS profiles detect and prevent network-level exploits and vulnerabilities using signature-based and behavioral analysis, not file hash matching. Option D is wrong because Web Filter profiles control access to URLs and web categories (e.g., blocking gambling sites), not file hash-based malicious content detection.

482
MCQhard

A FortiGate is configured with two VRF instances: VRF10 (for the finance department) and VRF20 (for the engineering department). Each VRF has its own routing table and interfaces. The administrator needs to allow a server in VRF10 (10.10.10.10) to communicate with a server in VRF20 (10.20.20.20). The administrator has already configured the necessary firewall policies to allow the traffic. However, pings from 10.10.10.10 to 10.20.20.20 fail. What is the most likely cause?

A.The FortiGate requires a static route in the global routing table to route traffic between VRFs.
B.The VRFs are isolated by default; inter-VRF routing requires configuring route leaking or a VRF-to-VRF link.
C.The FortiGate does not support inter-VRF routing; a separate physical interface is required to connect the VRFs.
D.The firewall policies must be configured with the 'set vrf' option to specify the source and destination VRFs.
AnswerB

VRF instances on FortiGate are isolated routing domains. By default, there is no communication between them. To allow traffic between VRFs, the administrator must configure route leaking, which involves exporting routes from one VRF and importing them into another, typically using route-maps or BGP. Alternatively, a VRF-to-VRF link can be created using a pair of interfaces, but that is more complex. Since the administrator only configured firewall policies, the missing piece is the routing configuration to leak routes between VRF10 and VRF20.

Why this answer

VRF instances provide isolated routing tables. By default, traffic cannot flow between them. To enable communication, the administrator must configure route leaking, which allows routes from one VRF to be imported into another.

This is typically done using BGP with route targets or static route leaking commands. Firewall policies alone are insufficient because the FortiGate lacks a route to the destination network in the other VRF. Therefore, the missing configuration is route leaking or a VRF-to-VRF link.

Exam trap

The trap here is assuming that firewall policies alone can enable inter-VRF communication, overlooking the need for route leaking between isolated routing tables.

483
MCQeasy

An organization uses FortiClient EMS to enforce compliance on endpoints. They want to ensure that only devices with updated antivirus definitions can access the corporate VPN. Which FortiClient configuration should be applied?

A.Create a compliance rule in FortiClient EMS to check antivirus definitions
B.Use a firewall policy to block traffic from non-compliant devices
C.Configure a ZTNA tag that requires updated antivirus
D.Enable CASB in the ZTNA proxy
AnswerA

A compliance rule in FortiClient EMS queries the endpoint's antivirus signature version and flags non-compliant devices, satisfying the requirement that only endpoints with updated definitions reach the VPN. FortiClient EMS then shares this compliance status with FortiGate, which enforces it through the VPN portal's host-check policy.

Why this answer

To enforce compliance based on antivirus definitions, a compliance rule must be created in FortiClient EMS that checks the antivirus definition status. This rule is then used in a ZTNA or VPN policy to allow or deny access. Firewall policies, ZTNA tags, or CASB alone do not check antivirus definitions.

Exam trap

The trap is confusing the mechanism (compliance rule in EMS) with enforcement points (firewall policy, ZTNA tag); the question asks for the configuration that checks antivirus definitions, which is the compliance rule.

How to eliminate wrong answers

Option B is wrong because a firewall policy blocks traffic based on IP/port, not endpoint compliance like antivirus definitions. Option C is wrong because a ZTNA tag is a label applied based on compliance rules; it does not itself check antivirus definitions. Option D is wrong because CASB is for cloud access security, not endpoint antivirus compliance.

484
MCQmedium

A FortiGate administrator wants to stop outbound DNS queries to a known malicious domain that is not present in any static blocklist. The administrator has already licensed FortiGuard DNS Filtering and enabled DNS filtering on the firewall policy. Which FortiGuard service must the FortiGate resolve the domain against so that the query is blocked based on the latest threat intelligence?

A.FortiGuard IP Reputation service
B.FortiGuard Antispam service
C.FortiGuard DNS Filtering service
D.FortiGuard Web Filtering
AnswerC

The FortiGuard DNS Filtering service maintains a real-time database of malicious and risky domains specifically for DNS resolution requests. When DNS filtering is enabled on the policy, the FortiGate sends the queried domain to this service and blocks the response if the domain is rated as malicious. This directly prevents the endpoint from learning the IP address of the malicious domain.

Why this answer

FortiGuard DNS Filtering is the service that evaluates domain names during DNS resolution and blocks queries for malicious or risky domains. Enabling DNS filtering on the firewall policy causes the FortiGate to consult this service for each lookup, so the endpoint never receives the IP address. Web Filtering, Antispam, and IP Reputation operate at different layers and cannot stop the domain from resolving.

Exam trap

The trap here is assuming that any FortiGuard security service enabled on a policy will automatically inspect DNS queries, when only the DNS Filtering service is queried for domain reputation during resolution.

485
Multi-Selecthard

A network administrator is troubleshooting a scenario where FortiView in FortiAnalyzer shows no traffic data for a specific FortiGate, but logs are being received. Which two possible causes should the administrator investigate? (Choose two.)

Select 2 answers
A.The FortiGate's clock is not synchronized with FortiAnalyzer
B.The FortiAnalyzer ADOM is configured as a global ADOM
C.The FortiGate is not sending traffic logs; only event logs are being forwarded
D.The FortiView database is corrupted or needs to be rebuilt
E.The FortiAnalyzer disk is full and not indexing new logs
AnswersC, D

FortiView traffic views are built solely from traffic logs. If the FortiGate forwards only event logs, the FortiAnalyzer receives data but no traffic records exist to populate FortiView, directly explaining the empty traffic display despite logs arriving.

Why this answer

Option C is correct because FortiView visualizations are built from traffic (forward) logs, so if the FortiGate only forwards event logs and no traffic logs, FortiAnalyzer will show received logs but no traffic data in FortiView. Option D is correct because if the FortiView log database (the SQL/traffic log database used for FortiView aggregation) is corrupted or requires a rebuild, FortiAnalyzer can still receive logs while FortiView fails to display traffic data until the database is repaired or rebuilt. Option A is not the cause because clock skew typically affects log timestamps and correlation, not the complete absence of FortiView traffic data when logs are arriving.

Option B is not the cause because a global ADOM affects ADOM scope and policy/object visibility, not whether FortiView renders traffic logs for a FortiGate. Option E is not the cause because a full disk would generally prevent or impair log reception/indexing broadly, whereas the scenario states logs are being received.

Exam trap

The trap here is that candidates assume any log reception implies traffic data is available for FortiView, but FortiView specifically requires traffic logs, not just any log type, and a corrupted database can silently break FortiView while other log viewing features remain functional.

486
Multi-Selectmedium

A FortiGate administrator is troubleshooting an issue where IPsec VPN traffic is not being forwarded correctly in a multi-VDOM environment. Which TWO factors should the administrator verify?

Select 2 answers
A.The firewall policy for the VPN traffic is present in the correct VDOM
B.The VPN tunnel is configured in the correct VDOM
C.Inter-VDOM routing is enabled globally
D.The management VDOM has an IPsec policy
E.The FortiGate is in transparent mode
AnswersA, B

Policy must be in the VDOM where traffic flows.

Why this answer

A is correct because firewall policies are VDOM-scoped; even if the VPN tunnel is up, traffic will not be forwarded unless a policy explicitly permits it within the VDOM that owns the VPN interface. The administrator must verify that the policy allowing the IPsec traffic exists in the correct VDOM, as policies from one VDOM cannot control traffic in another.

Exam trap

The trap here is that candidates often assume inter-VDOM routing is a global feature that must be enabled, when in fact it is handled by per-VDOM configurations such as inter-VDOM links or policies.

487
MCQmedium

An administrator is configuring an SD-WAN rule to prefer a specific overlay tunnel for VoIP traffic. The rule uses the 'SLA' strategy with a performance SLA that measures jitter and latency. After applying the rule, the administrator notices that VoIP traffic is still being routed over a different member that does not meet the SLA. What is the most likely cause?

A.The performance SLA is not assigned to the SD-WAN rule, so the rule cannot use SLA status for member selection.
B.The SD-WAN rule is placed below a static route in the routing table, so it is not evaluated.
C.The performance SLA is configured with the wrong protocol; it must use HTTP to measure jitter and latency.
D.The SD-WAN rule is configured with the 'load-balance' strategy instead of 'SLA', so it does not consider SLA status.
AnswerA

For an SD-WAN rule using the SLA strategy to select members based on performance, the performance SLA must be referenced in the rule's configuration. Without it, the rule cannot evaluate SLA status and may default to other criteria. This is the most likely cause of the observed behavior.

Why this answer

An SD-WAN rule with the SLA strategy must explicitly reference a performance SLA to use its measurements for member selection. If the SLA is not linked, the rule cannot determine which members meet the SLA and may fall back to other criteria, causing traffic to use a non-compliant member. Ensuring the correct SLA is attached to the rule resolves the issue.

Exam trap

The trap here is assuming that the SD-WAN rule automatically uses any performance SLA configured on the same members without explicit association.

488
Multi-Selecthard

A FortiGate administrator is troubleshooting why a custom IPS signature is not triggering on traffic matching the pattern. Which TWO checks should be performed?

Select 2 answers
A.Check the signature's severity level in the IPS sensor
B.Ensure the FortiGate is in proxy-based inspection mode
C.Confirm the IPS sensor is applied to the correct firewall policy
D.Verify the signature uses correct protocol decoder
E.Verify that the custom signature is enabled in the IPS sensor
AnswersC, E

Without policy attachment, no inspection occurs.

Why this answer

An IPS sensor must be explicitly attached to a firewall policy via the 'inspection-mode' or 'ips-sensor' configuration to inspect traffic. Even if a custom signature is correctly defined and enabled, it will never trigger if the sensor containing it is not applied to the policy that matches the target traffic. This is a fundamental prerequisite for any IPS signature to process packets.

Exam trap

The trap here is that candidates often focus on signature configuration details (severity, decoder, mode) and overlook the policy attachment step, which is the most common root cause for a custom signature not triggering.

489
MCQeasy

A multinational company uses FortiGate devices as VPN gateways to connect its headquarters (HQ) and branch offices via IPsec VPN tunnels. The company is migrating its remote access solution from IPsec VPN to SSL VPN using FortiClient. Currently, 500 remote users connect via IPsec VPN with pre-shared keys and XAuth authentication. The migration must be seamless with minimal downtime, and users must continue to authenticate using their existing Active Directory credentials. The SSL VPN portal must provide access to internal web applications and some legacy TCP-based applications that do not support HTTP. The security team requires that all traffic between remote users and the internal network be encrypted and that the SSL VPN use a certificate from a public CA to avoid certificate warnings on client devices. The IT team wants to use FortiToken for two-factor authentication (2FA) for all VPN users. Which of the following is the most appropriate course of action to meet all requirements?

A.Configure SSL VPN with a self-signed certificate and use the local password database for authentication. Enable FortiToken and configure the portal to provide both web and TCP forwarding applications.
B.Deploy SSL VPN with a public CA certificate, configure LDAP authentication against Active Directory, enable FortiToken for 2FA, and create a split-tunneling policy that uses both SSL VPN web mode and tunnel mode via FortiClient.
C.Set up SSL VPN with a public CA certificate, use LDAP for authentication, but do not enable FortiToken because it would require a separate token per user.
D.Create a new IPsec VPN configuration using certificate-based authentication and FortiToken, and gradually move users to the new IPsec VPN.
AnswerB

LDAP against Active Directory preserves existing credentials, FortiToken adds the required 2FA, a public CA certificate prevents client warnings, and combining web mode with tunnel mode via FortiClient covers both web apps and legacy TCP traffic while split tunnelling keeps internal traffic encrypted.

Why this answer

It meets all requirements: a public CA certificate avoids client certificate warnings, LDAP authentication against Active Directory allows seamless credential reuse, FortiToken provides the required 2FA, and combining SSL VPN web mode (for web apps) with tunnel mode via FortiClient (for legacy TCP applications) ensures full coverage. This approach minimizes downtime by migrating users gradually without changing their authentication backend.

Exam trap

The trap here is that candidates may think SSL VPN cannot handle non-HTTP applications, but FortiClient's tunnel mode with split tunneling or full tunneling can encapsulate any TCP/UDP traffic, making it suitable for legacy applications.

How to eliminate wrong answers

Option A is wrong because a self-signed certificate would cause certificate warnings on client devices, violating the requirement to avoid such warnings, and using the local password database does not integrate with existing Active Directory credentials. Option C is wrong because it explicitly disables FortiToken, failing the two-factor authentication requirement; the statement that FortiToken requires a separate token per user is incorrect—FortiToken can be assigned per user via the FortiGate or FortiAuthenticator. Option D is wrong because it proposes continuing with IPsec VPN instead of migrating to SSL VPN, and certificate-based authentication does not address the need for SSL VPN portal access to web and legacy TCP applications.

490
MCQmedium

A FortiGate is configured with multiple VDOMs. The administrator needs to provide a network engineer with read-only access to all VDOMs, but the engineer should not be able to make any configuration changes. Which administrative profile configuration should the administrator use?

A.Assign the engineer the built-in 'prof_admin' profile, which provides read-only access to all VDOMs by default.
B.Use the built-in 'prof_readonly' profile, which provides read-only access to all VDOMs by default.
C.Create a new administrative profile with 'None' access for all categories, and assign it to the engineer with 'All VDOMs' scope.
D.Create a new administrative profile with 'Read' access for all categories, and assign it to the engineer's administrator account with 'All VDOMs' scope.
AnswerD

An administrative profile defines the permissions for an administrator account. By creating a profile with 'Read' access for all categories (such as firewall, network, system, etc.), you ensure the engineer can view configurations but cannot modify them. Assigning the administrator account with 'All VDOMs' scope grants access to all VDOMs. This is the correct way to provide read-only access across all VDOMs. The profile can be customized to include read access to all relevant areas, and the scope ensures the engineer can switch between VDOMs and view their settings.

Why this answer

To provide read-only access to all VDOMs, you must create a custom administrative profile with 'Read' permissions for all categories. Then assign this profile to the engineer's administrator account and set the VDOM scope to 'All VDOMs'. This allows the engineer to view configurations in any VDOM but prevents any changes.

Built-in profiles do not offer this specific combination of read-only access across all VDOMs, so a custom profile is necessary.

Exam trap

The trap here is assuming that a built-in profile provides read-only access, but in FortiOS, read-only access requires a custom administrative profile with 'Read' permissions set for each category.

491
MCQhard

A FortiGate admin sees the following log: 'Action=blocked, Service=HTTP, Application=Outbreak, File=invoice.doc, ThreatScore=95'. What is the MOST likely explanation for this block?

A.The file was blocked by FortiGuard outbreak prevention
B.The file was blocked by the machine learning engine
C.The file was blocked by FortiSandbox verdict
D.The file was blocked by a custom IPS signature
AnswerA

FortiGuard outbreak prevention inspects files against known malware signatures and outbreak intelligence, matching the Application=Outbreak and ThreatScore=95 fields. The HTTP service and invoice.doc filename indicate a file transfer, which outbreak prevention scans and blocks on detection, satisfying the stem's blocked action.

Why this answer

The log entry shows 'Application=Outbreak' and 'ThreatScore=95', which are specific indicators of FortiGuard outbreak prevention. FortiGuard outbreak prevention uses real-time threat intelligence to block files associated with widespread malware campaigns before traditional signatures are updated. The 'Outbreak' application tag and high threat score directly correspond to this feature, not to machine learning, sandbox verdicts, or custom IPS signatures.

Exam trap

The trap here is that candidates confuse 'Outbreak' with a generic malware detection term, not realizing it is a specific FortiGuard feature with its own log field, distinct from machine learning, sandbox, or IPS-based blocks.

How to eliminate wrong answers

Option B is wrong because the machine learning engine in FortiGate uses behavioral analysis and static file analysis to detect unknown malware, but it does not generate an 'Application=Outbreak' tag; that tag is specific to FortiGuard outbreak prevention. Option C is wrong because a FortiSandbox verdict would appear in logs as 'Action=blocked' with 'Application=Sandbox' or 'Verdict=malicious', not 'Application=Outbreak'. Option D is wrong because a custom IPS signature would log 'Action=blocked' with 'Signature=...' or 'IPS=...', not 'Application=Outbreak' or 'ThreatScore=95'.

492
MCQeasy

An administrator needs to back up the configuration of a FortiGate managed by FortiManager before making major changes. Which feature in FortiManager should the administrator use?

A.Policy package import/export
B.Automation stitch
C.Install preview
D.Revision history
AnswerD

Revision history stores configuration revisions of managed FortiGate devices in FortiManager, allowing the administrator to review and revert changes. It satisfies the backup-before-change requirement, unlike scripts or provisioning templates, which push configuration rather than preserve prior states.

Why this answer

Revision History in FortiManager allows administrators to create, view, and restore previous configuration versions of managed FortiGate devices. This is the correct feature for backing up a configuration before making major changes, as it provides a point-in-time snapshot that can be rolled back if needed.

Exam trap

The trap here is that candidates may confuse 'Install preview' (which shows changes to be applied) with a backup mechanism, but it does not save the current state for rollback, whereas Revision History explicitly provides that capability.

How to eliminate wrong answers

Option A is wrong because Policy package import/export is used to transfer policy packages between FortiManager and FortiGate or between FortiManager instances, not to back up the entire device configuration before changes. Option B is wrong because Automation stitch is a FortiGate feature that automates responses to events (e.g., triggering scripts or sending alerts), not a configuration backup mechanism. Option C is wrong because Install preview shows the pending changes that will be applied during an install operation, but it does not create a backup or allow rollback of the current configuration.

493
MCQeasy

Which Fortinet product is designed to deploy decoy systems to lure attackers and detect lateral movement within the network?

A.FortiSandbox
B.FortiDeceptor
C.FortiSOAR
D.FortiEDR
AnswerB

FortiDeceptor deploys decoy systems across network segments, luring attackers into interacting with emulated assets. This satisfies the requirement to detect lateral movement, since any east-west traffic touching a decoy reveals an intruder's internal reconnaissance. Unlike prevention-focused controls, it provides early breach detection through deception rather than signature-based blocking.

Why this answer

FortiDeceptor is specifically designed to deploy decoy systems (honeypots) that mimic real assets, such as servers or endpoints, to lure attackers. It detects lateral movement by monitoring decoy interactions and generating alerts when an attacker probes or compromises these fake targets, providing early warning of network intrusion.

Exam trap

The trap here is that candidates may confuse FortiDeceptor with FortiSandbox, assuming sandboxing involves decoys, but FortiSandbox focuses on file analysis while FortiDeceptor is purpose-built for deception-based threat detection.

How to eliminate wrong answers

Option A is wrong because FortiSandbox is a threat analysis and detection appliance that executes suspicious files in a sandboxed environment to identify malware, not a decoy system for luring attackers. Option C is wrong because FortiSOAR is a security orchestration, automation, and response (SOAR) platform that coordinates incident response workflows, not a deception-based detection tool. Option D is wrong because FortiEDR is an endpoint detection and response solution that monitors and protects endpoints from threats using behavioral analysis and machine learning, not by deploying decoy systems.

494
MCQhard

An administrator runs 'diagnose sys session list' and sees sessions with 'proto=6 proto_state=02' and a long duration. The administrator is troubleshooting why sessions are not being terminated after a policy change that should block the traffic. What does 'proto_state=02' indicate?

A.The session is in TIME_WAIT state
B.The session is in SYN_SENT state, waiting for a SYN-ACK
C.The session is in established state (TCP connection active)
D.The session is in FIN_WAIT state, closing the connection
AnswerC

proto_state=02 denotes an established TCP session, meaning the three-way handshake completed and the connection remains active. FortiGate keeps such sessions alive until FIN or RST, so a policy change alone will not terminate them; they must be cleared manually.

Why this answer

In Fortinet's 'diagnose sys session list' output, 'proto=6' indicates TCP, and 'proto_state=02' maps to the TCP established state (ESTABLISHED). This means the session has completed the three-way handshake and is actively passing data. A long duration in this state explains why the session persists even after a policy change that should block new traffic—the existing session remains in the kernel session table until it times out or is explicitly cleared, because FortiGate's stateful inspection does not retroactively terminate established sessions upon policy modification.

Exam trap

The trap here is that candidates confuse the numeric 'proto_state' values with generic TCP states from RFC 793, but Fortinet uses its own mapping where '02' specifically means ESTABLISHED, not TIME_WAIT or FIN_WAIT, leading to incorrect assumptions about session termination behavior.

How to eliminate wrong answers

Option A is wrong because TIME_WAIT is represented by proto_state=05, not 02, and indicates a session waiting for a potential delayed packet after a connection close. Option B is wrong because SYN_SENT corresponds to proto_state=01, which is the initial state before the handshake completes, not a long-duration established session. Option D is wrong because FIN_WAIT is represented by proto_state=03 or 04 (depending on direction), not 02, and indicates an active closure sequence, not an ongoing data transfer.

495
MCQmedium

An administrator wants to create an automation stitch that sends a webhook notification when an IPS attack is detected. Which trigger and action should be used?

A.Trigger: 'IPS Event'; Action: 'Webhook'
B.Trigger: 'FortiGuard'; Action: 'Quarantine'
C.Trigger: 'System Event'; Action: 'Email'
D.Trigger: 'Incoming Webhook'; Action: 'IPS Event'
AnswerA

The IPS Event trigger fires whenever the IPS engine logs an attack detection, and the Webhook action posts the event payload to the configured external URL. This pairing satisfies the requirement to send a webhook notification on IPS detection.

Why this answer

An automation stitch requires a trigger that matches the event type and an action that performs the desired response. 'IPS Event' is the correct trigger for detecting an IPS attack, and 'Webhook' is the action that sends an HTTP POST request to a configured endpoint, which is the standard method for webhook notifications in FortiOS.

Exam trap

The trap here is that candidates confuse 'IPS Event' with 'System Event' or 'FortiGuard', or mistakenly think 'Incoming Webhook' is a trigger for outbound notifications, when in fact it is for receiving external triggers.

How to eliminate wrong answers

Option B is wrong because 'FortiGuard' is a trigger for FortiGuard threat intelligence updates, not for IPS events, and 'Quarantine' is an action for isolating compromised hosts, not for sending webhook notifications. Option C is wrong because 'System Event' is a trigger for system-level events like interface status changes, not for IPS attacks, and 'Email' is an action for sending email alerts, not webhook notifications. Option D is wrong because 'Incoming Webhook' is a trigger for receiving external webhooks, not for detecting IPS attacks, and 'IPS Event' is a trigger, not an action.

496
MCQmedium

A FortiGate 600E is running in multi-VDOM mode and is managed by FortiManager. The administrator needs to assign CPU and memory resource limits to a specific VDOM so that it cannot consume more than 30% of the system's resources. Which FortiGate feature should the administrator configure?

A.Create a traffic shaping policy for all traffic entering and leaving the VDOM.
B.Assign the VDOM to a dedicated NP6 processor using NPU offload settings.
C.Enable VDOM resource limits under the global system settings and assign per-VDOM CPU and memory quotas.
D.Configure a separate administrative profile that restricts the VDOM's access to system resources.
AnswerC

FortiOS supports per-VDOM resource limits through the 'config system vdom-resource-limits' or similar global settings. Once enabled, you can assign CPU and memory quotas to individual VDOMs. This directly addresses the requirement to cap a VDOM's resource usage, ensuring it does not starve other VDOMs on the same physical device.

Why this answer

The correct answer is to enable VDOM resource limits and assign per-VDOM quotas. This is the only method that directly enforces CPU and memory limits on a per-VDOM basis, ensuring fair resource distribution. Other options address bandwidth, administrative access, or hardware offloading, none of which satisfy the requirement to cap CPU and memory usage.

Exam trap

The trap here is confusing traffic shaping, which controls bandwidth, with resource limits, which control CPU and memory usage.

497
MCQhard

You run 'diagnose sys session filter dport 179' on a FortiGate and see many sessions with proto=6 and proto_state=01. What does this indicate about the BGP sessions?

A.BGP sessions are fully established and exchanging routes.
B.BGP sessions are being actively torn down.
C.BGP sessions are in the process of being established, but not yet fully up.
D.BGP sessions are using TCP port 179 but are idle.
AnswerC

proto_state=01 denotes a TCP session in the SYN-sent or SYN-received phase, meaning the three-way handshake has not completed. For BGP over TCP port 179, this confirms sessions are still being established and are not yet exchanging routing updates.

Why this answer

Proto=6 indicates TCP, and proto_state=01 corresponds to TCP SYN_SENT (state 1 in the Linux TCP state model used by FortiGate). This means the BGP session has sent a SYN but has not yet received a SYN-ACK, so the three-way handshake is incomplete and the session is not established. BGP uses TCP port 179, so seeing many sessions in this state indicates ongoing connection attempts that have not yet completed.

Exam trap

The trap here is that candidates often assume any session on port 179 with proto=6 (TCP) means BGP is working, but they overlook the TCP state field; FortiGate's proto_state values directly map to TCP connection phases, and 01 specifically indicates the session is still in the handshake phase, not established.

How to eliminate wrong answers

Option A is wrong because a fully established BGP session would show proto_state=08 (TCP ESTABLISHED), not 01. Option B is wrong because sessions being torn down would show states like FIN_WAIT (proto_state=09 or 0A) or CLOSE_WAIT (proto_state=0B), not SYN_SENT. Option D is wrong because an idle TCP session on port 179 would still be in ESTABLISHED state (08) if the connection was previously successful, or would not exist if never established; proto_state=01 indicates active connection initiation, not idleness.

498
MCQeasy

Which FortiGate feature is used to detect link failures within milliseconds, allowing rapid convergence for routing protocols like OSPF and BGP?

A.ECMP
B.OSPF Fast Hello
C.BFD
D.Route tagging
AnswerC

BFD (Bidirectional Forwarding Detection) provides sub-second, millisecond-level link failure detection by sending rapid echo and control packets independent of routing protocol hello timers. This satisfies the stem's requirement for millisecond detection, triggering OSPF and BGP to converge rapidly rather than waiting for slower protocol-specific dead intervals.

Why this answer

Bidirectional Forwarding Detection (BFD) is the correct answer because it provides sub-second (millisecond) link failure detection independent of routing protocols. Unlike OSPF or BGP's own keepalive mechanisms, BFD can detect failures in as little as 50-100 ms, enabling rapid convergence for protocols like OSPF and BGP by immediately notifying them of a neighbor loss.

Exam trap

The trap here is that candidates confuse OSPF Fast Hello (which still operates in the hundreds-of-milliseconds range) with BFD's true sub-100 ms detection, or they mistakenly think ECMP or route tagging are involved in failure detection.

How to eliminate wrong answers

Option A is wrong because ECMP (Equal-Cost Multi-Path) is a load-balancing technique that distributes traffic across multiple equal-cost paths, not a failure detection mechanism. Option B is wrong because OSPF Fast Hello reduces the hello interval to achieve faster neighbor loss detection (e.g., 1 second), but it still relies on OSPF's own timers and cannot reach the millisecond detection speeds that BFD offers. Option D is wrong because route tagging is used for policy-based routing or redistribution control (e.g., marking routes with tags to filter or manipulate them), not for detecting link failures.

499
MCQmedium

An administrator notices that a FortiGate's CPU is consistently high, and the performance dashboard shows the 'ipsengine' process consuming most CPU. The administrator suspects a specific traffic pattern is overwhelming the IPS engine. Which CLI command should be used to identify the top sessions by bandwidth that may be triggering the IPS engine?

A.diagnose sys session list
B.diagnose sys session top
C.diagnose netlink top
D.diagnose sys top
AnswerB

diagnose sys session top shows the top sessions sorted by bandwidth usage. This command is ideal for identifying which sessions are consuming the most traffic, which can help determine if a particular flow is causing high IPS engine CPU. It provides a concise list of top sessions with source, destination, and bandwidth.

Why this answer

High CPU on the IPS engine often results from a few heavy sessions. The diagnose sys session top command lists the top sessions by bandwidth, allowing the administrator to quickly identify the offending traffic. This is more direct than dumping all sessions or looking at interface statistics.

Exam trap

The trap here is confusing process monitoring commands (like diagnose sys top) with session monitoring commands that sort by bandwidth.

500
MCQmedium

Refer to the exhibit. A user reports that accessing a legitimate HTTPS website is blocked. The FortiGate logs show that the connection was denied by the antivirus profile. What is the most likely cause?

A.The antivirus profile detected a false positive in the encrypted traffic
B.The application list blocked the HTTPS application
C.The IPS profile blocked a vulnerability in the website
D.The protocol options profile blocked the SSL handshake
AnswerA

The antivirus profile performs deep inspection, including of HTTPS traffic after decryption, and can flag benign content as malicious. A false positive therefore causes the FortiGate to deny a legitimate site, matching the logged antivirus denial. This satisfies the stem's encrypted-traffic constraint, since inspection requires SSL decryption.

Why this answer

The antivirus (AV) profile on FortiGate performs deep inspection of HTTPS traffic by decrypting it, scanning the content, and re-encrypting it. If the AV signature database contains a false positive for a legitimate website's content (e.g., a benign JavaScript file matching a malware signature), the connection will be denied. The log explicitly states the denial was by the AV profile, not by any other security profile, making a false positive in encrypted traffic the most likely cause.

Exam trap

The trap here is that candidates may confuse the security profile that generated the log entry (antivirus) with other profiles (application control, IPS, protocol options) that could also block HTTPS traffic, but the log's explicit attribution to the AV profile eliminates those possibilities.

How to eliminate wrong answers

Option B is wrong because the log shows the connection was denied by the antivirus profile, not by an application control profile; the application list blocking HTTPS would generate a log entry from the application control module, not the AV module. Option C is wrong because an IPS profile blocking a vulnerability would generate a log entry from the IPS sensor, not the antivirus profile, and the log explicitly attributes the denial to the AV profile. Option D is wrong because the protocol options profile blocking the SSL handshake would produce a log from the SSL inspection module or a protocol violation, not from the antivirus profile, and the connection was denied after inspection, not during the handshake.

501
Multi-Selectmedium

An administrator is configuring FortiClient EMS to enforce compliance for ZTNA. Which TWO settings are required on FortiGate to use compliance-based ZTNA tags?

Select 2 answers
A.FortiClient EMS is added as a security fabric connector
B.The ZTNA proxy rule includes a condition for required ZTNA tags
C.SSL deep inspection is enabled on the firewall policy
D.A local user database is configured for authentication
E.FortiGate is configured as a SAML IdP
AnswersA, B

Compliance tags originate from FortiClient EMS, so the FortiGate must first learn them. Adding EMS as a security fabric connector establishes that channel, allowing the FortiGate to receive endpoint compliance posture and populate ZTNA tags.

Why this answer

Option A is correct because FortiGate must add FortiClient EMS as a Security Fabric connector (via Fabric Connectors > Endpoint/EMS) so it can receive the compliance-based ZTNA tags that EMS dynamically assigns to endpoints. Option B is correct because the ZTNA proxy policy must reference those tags as a matching condition (e.g., source 'ZTNA Tags' with the required compliance tag) for the tags to actually enforce access; without the tag condition, compliance data is never evaluated. Option C is not required: SSL deep inspection is a traffic-inspection feature and is unrelated to receiving or matching ZTNA compliance tags.

Option D is not required: ZTNA tag-based enforcement relies on EMS-assigned tags, not on a local user database for authentication. Option E is not required: FortiGate acting as a SAML IdP is an authentication scenario and is not needed to consume EMS compliance tags for ZTNA.

Exam trap

NSE7 often tests the misconception that SSL deep inspection or local authentication is required for ZTNA tags, when the actual requirements are the EMS Fabric connector and the tag condition in the proxy rule.

502
MCQhard

A FortiGate administrator is configuring a ZTNA rule that uses a proxy-based policy to inspect traffic to a web application. The administrator wants to ensure that only users who have a valid certificate installed on their endpoint are allowed access. The certificate is issued by the corporate PKI and is stored in the user's certificate store. Which ZTNA configuration element should the administrator use to enforce this requirement?

A.Client certificate authentication in the ZTNA proxy rule
B.ZTNA tagging with a dynamic firewall address
C.FortiClient EMS compliance rule with certificate check
D.SSL VPN with certificate authentication
AnswerA

Client certificate authentication in a ZTNA proxy rule requires the client to present a valid certificate during the TLS handshake. The FortiGate validates the certificate against a configured CA and can enforce additional checks such as revocation status. This directly ensures that only users with a valid corporate PKI certificate are granted access, matching the scenario's requirement.

Why this answer

Client certificate authentication in the ZTNA proxy rule is the correct choice because it enforces certificate validation during the TLS handshake. The FortiGate acts as a proxy and can request a client certificate, verify it against a trusted CA, and check revocation. This provides strong authentication that the user possesses a valid certificate from the corporate PKI.

Other options either rely on endpoint compliance reporting or are for different access methods, and they do not provide the same cryptographic assurance.

Exam trap

The trap here is assuming that FortiClient EMS compliance checks alone can enforce certificate-based access, when only client certificate authentication in the proxy rule validates the certificate during the connection.

503
MCQeasy

Which FortiGate security feature removes potentially malicious active content from files (e.g., macros, scripts) before delivering them to end users?

A.Antivirus
B.Data Leak Prevention
C.File Filter
D.Content Disarm and Reconstruction
AnswerD

Content Disarm and Reconstruction strips and rebuilds potentially malicious active content such as macros and scripts from files, delivering sanitised versions to users. Unlike antivirus signature matching, CDR removes the threat regardless of whether the payload is known, satisfying the requirement to eliminate active content before delivery.

Why this answer

Content Disarm and Reconstruction (CDR) is the correct answer because it specifically removes potentially malicious active content—such as macros, scripts, and embedded objects—from files (e.g., Office documents, PDFs) by stripping the active elements and reconstructing a safe, sanitized version before delivery. Unlike traditional scanning, CDR does not rely on signatures or heuristics; it assumes the file could be malicious and proactively neutralizes threats by rebuilding the file with only safe, static content.

Exam trap

The trap here is that candidates confuse 'File Filter' (which blocks file types) with 'Content Disarm and Reconstruction' (which sanitizes file content), or they assume 'Antivirus' handles all file-based threats, not realizing that CDR addresses zero-day macro and script attacks that antivirus signatures may miss.

How to eliminate wrong answers

Option A (Antivirus) is wrong because antivirus uses signature-based and heuristic detection to identify known malware, but it does not remove active content from files; it only blocks or quarantines files that match a threat pattern. Option B (Data Leak Prevention) is wrong because DLP focuses on detecting and preventing unauthorized transmission of sensitive data (e.g., credit card numbers, PII) via content inspection, not on removing active content from files. Option C (File Filter) is wrong because file filter controls which file types are allowed or blocked based on extension or MIME type, but it does not sanitize or remove active content from within permitted files.

504
MCQeasy

Which routing protocol is commonly used in SD-WAN deployments to exchange routes between FortiGate and the provider edge router in an MPLS network?

A.RIP
B.BGP
C.IS-IS
D.OSPF
AnswerB

BGP is the exterior gateway protocol used between the FortiGate and the provider edge router to exchange routes across the MPLS network, supporting policy and multi-path control. OSPF and RIP are interior protocols, unsuitable for PE-to-CE peering here.

Why this answer

BGP is the correct answer because it is the standard exterior gateway protocol used in MPLS Layer 3 VPNs to exchange customer routes between a FortiGate (CE router) and the provider edge (PE) router. BGP supports advanced features like route filtering, load balancing, and traffic engineering, which are essential for SD-WAN overlay integration with MPLS underlay networks.

Exam trap

The trap here is that candidates often default to OSPF as a 'common' routing protocol in enterprise networks, failing to recognize that MPLS VPNs specifically require BGP for inter-domain route exchange and SD-WAN overlay integration.

How to eliminate wrong answers

Option A is wrong because RIP is a distance-vector protocol with a maximum hop count of 15, making it unsuitable for the scalable, policy-rich route exchange required between a FortiGate and an MPLS PE router. Option C is wrong because IS-IS is a link-state IGP typically used within service provider networks for internal routing, not for exchanging customer routes with a CE device in an MPLS VPN context. Option D is wrong because OSPF is an IGP designed for intra-domain routing and lacks the path-vector attributes (e.g., AS_PATH, MED) needed for MPLS VPN route distribution and SD-WAN policy-based path selection.

505
MCQeasy

What is the role of FortiGuard Outbreak Prevention in FortiGate's security suite?

A.To deliver real-time threat intelligence and block fast-spreading outbreaks
B.To provide offline signature updates for antivirus
C.To perform sandbox analysis of files
D.To manage endpoint security policies
AnswerA

FortiGuard Outbreak Prevention pushes real-time outbreak intelligence to the FortiGate, letting it block fast-spreading threats before signature updates arrive. This satisfies the scenario's requirement for immediate protection against rapidly propagating outbreaks, distinct from standard IPS signatures that lag behind emerging campaigns.

Why this answer

FortiGuard Outbreak Prevention is a real-time threat intelligence service that proactively blocks fast-spreading outbreaks by delivering immediate signature updates and threat data to FortiGate devices. Unlike scheduled updates, it uses a push mechanism to rapidly deploy protections against emerging threats, reducing the window of vulnerability during zero-day or widespread attacks.

Exam trap

The trap here is that candidates often confuse Outbreak Prevention with regular antivirus signature updates or sandboxing, but the key distinction is that Outbreak Prevention is a real-time, push-based service for fast-spreading threats, not a scheduled or offline update mechanism.

How to eliminate wrong answers

Option B is wrong because offline signature updates are handled by FortiGuard's regular antivirus update service, not Outbreak Prevention, which requires an active internet connection for real-time intelligence. Option C is wrong because sandbox analysis is performed by FortiSandbox, a separate product that integrates with FortiGate but is not part of Outbreak Prevention's role. Option D is wrong because managing endpoint security policies is the function of FortiClient or FortiEDR, not FortiGate's Outbreak Prevention service.

506
MCQhard

A FortiGate admin configures a firewall policy with an antivirus profile in flow-based inspection mode. The admin notices that some large files are being scanned but others are allowed without scanning. What is the most likely cause?

A.The antivirus signatures are outdated
B.The antivirus profile has an exemption for certain file types
C.The FortiGate's antivirus buffer size is exceeded, causing some files to bypass scanning
D.Flow-based inspection cannot scan files larger than 10 MB
AnswerC

In flow-based antivirus inspection, files are buffered up to a configured limit before scanning. Files exceeding that buffer size cannot be held for inspection, so the FortiGate passes them unscanned, explaining why only some large files bypass scanning.

Why this answer

In flow-based inspection, FortiGate uses a buffer to reassemble files before scanning. When a file exceeds the configured antivirus buffer size (default 1 MB for flow-based), the FortiGate cannot buffer the entire file for scanning and allows it to pass without inspection. This explains why some large files bypass scanning while smaller ones are scanned.

Exam trap

The trap here is that candidates assume flow-based inspection can scan any file size, overlooking the buffer size limitation that causes large files to bypass scanning entirely.

How to eliminate wrong answers

Option A is wrong because outdated signatures would cause missed detections, not selective bypassing of large files; all files would still be scanned. Option B is wrong because file-type exemptions would consistently skip those file types regardless of size, not selectively allow only large files. Option D is wrong because flow-based inspection does not have a hard 10 MB limit; the buffer size is configurable and defaults to 1 MB, and files larger than the buffer are bypassed, not blocked.

507
MCQhard

A FortiGate is configured with an IPsec VPN tunnel to a remote peer. The tunnel is up, but traffic is not passing through it. The administrator runs 'diagnose vpn tunnel list' and sees that the tunnel is established. The administrator then runs 'diagnose debug flow' and sees that traffic is being dropped with the message 'iprope_in_check() check failed, drop'. What is the MOST likely cause of the drop?

A.The VPN tunnel is using the wrong pre-shared key.
B.The firewall policy for the VPN traffic is missing or incorrect.
C.The IPsec phase2 selectors do not match the traffic being sent.
D.The routing table does not have a route to the remote subnet.
AnswerB

The message 'iprope_in_check() check failed, drop' indicates that the traffic was dropped by the firewall policy check. This typically means that no firewall policy matches the traffic, or the matching policy has an action of deny. In the context of an IPsec VPN, traffic arriving from the tunnel must be matched by a policy that allows it. If the policy is missing or misconfigured, the packet is dropped. This is the most likely cause.

Why this answer

The error 'iprope_in_check() check failed, drop' is generated by the firewall policy check. It means that the packet did not match any allow policy or matched a deny policy. In an IPsec VPN scenario, this often happens when the policy allowing traffic from the VPN tunnel is missing or incorrectly configured.

The administrator should verify that a policy exists with the correct incoming interface, source, destination, and service.

Exam trap

The trap here is focusing on IPsec configuration when the error clearly points to a firewall policy issue, leading to unnecessary troubleshooting of the tunnel itself.

508
MCQmedium

An administrator is configuring a FortiGate in multi-VDOM mode. The administrator wants to assign a physical interface to a non-management VDOM. The interface currently belongs to the root VDOM and has an IP address. What must the administrator do first?

A.Disable the interface, change its VDOM, and then re-enable it.
B.Enable administrative access on the interface and then change its VDOM assignment.
C.Create a VDOM link between the root VDOM and the target VDOM, then move the interface.
D.Remove the IP address and any references from the root VDOM, then assign the interface to the target VDOM.
AnswerD

Before moving a physical interface to another VDOM, it must not have any configuration that conflicts, such as an IP address or references in firewall policies. The administrator must remove the IP address and any references from the root VDOM. Then the interface can be assigned to the target VDOM without errors.

Why this answer

To move a physical interface from one VDOM to another, the interface must not have an IP address or be referenced in any configuration, such as firewall policies or routing. The administrator must remove the IP address and any references from the current VDOM first. After that, the interface can be assigned to the target VDOM.

Exam trap

The trap here is thinking that simply changing the VDOM assignment will automatically clear the IP address or that disabling the interface is sufficient.

509
MCQmedium

An administrator configures an automation stitch to respond to a high severity event. The trigger is 'event' and the action is 'CLI script'. What must be defined for the action to execute properly?

A.An API token for authentication
B.A FortiManager to execute the script
C.An email server to send the script output
D.A valid CLI script that contains commands to be executed on the FortiGate
AnswerD

The CLI script action executes FortiGate commands, so a valid script containing those commands must exist and be referenced for the stitch to run. Without it the action has nothing to execute, so defining the script satisfies the stem's requirement for proper action execution.

Why this answer

For an automation stitch action of type 'CLI script' to execute properly on a FortiGate, the action must reference a valid CLI script that contains the actual FortiGate CLI commands to be run. The script is defined locally on the FortiGate and does not require external authentication, a FortiManager, or an email server for execution.

Exam trap

The trap here is that candidates may assume a CLI script action requires an external orchestrator like FortiManager or authentication tokens, when in fact the script runs locally on the FortiGate and only needs a valid script definition.

How to eliminate wrong answers

Option A is wrong because an API token is not required for CLI script actions; API tokens are used for REST API authentication, not for executing predefined CLI scripts within an automation stitch. Option B is wrong because the CLI script action executes directly on the FortiGate itself, not on a FortiManager; FortiManager is only needed if the action type is 'FortiManager script'. Option C is wrong because an email server is only required if the action type is 'Email', not for executing a CLI script; the script output is handled locally or via other logging mechanisms.

510
Multi-Selecthard

A FortiGate administrator is investigating a slow network issue. The 'diagnose sys session stat' shows a high number of sessions. Which THREE commands can help identify the source of the high session count?

Select 3 answers
A.diagnose sys session list | grep <policy_id>
B.diagnose sys session filter src <IP>
C.diagnose sys session top-talkers
D.diagnose sys session stat
E.diagnose netlink interface list
AnswersA, B, C

Counts sessions per policy to see which policy is most used.

Why this answer

'diagnose sys session list | grep <policy_id>' filters the session list to show only sessions matching a specific firewall policy ID. This allows the administrator to identify which policy is handling the most sessions, helping to pinpoint the source of high session counts by correlating traffic patterns with policy usage.

Exam trap

The trap here is that candidates may think 'diagnose sys session stat' (Option D) provides source-level detail, but it only shows aggregate counters, not per-source or per-policy breakdowns, making it useless for identifying the specific source of high session counts.

511
MCQhard

A FortiGate is configured with a VIP (virtual IP) for an internal web server at 10.0.0.10, mapping to public IP 203.0.113.5. External users report that they cannot access the web server, but internal users can access it using the private IP. The administrator runs 'diagnose debug flow filter addr 203.0.113.5' and 'diagnose debug flow show function-name enable' and sees the following output: 'id=20085 trace_id=1 func=print_pkt_detail line=4793 msg="vd-root:0 received a packet(proto=6, 203.0.113.5:443->198.51.100.10:54321) from port1. flag [S], seq 123456, ack 0, win 8192"' followed by 'id=20085 trace_id=1 func=init_ip_session_common line=4970 msg="allocate a new session-00000123"' and then 'id=20085 trace_id=1 func=vf_ip_route_input_common line=2580 msg="find a route: flag=04000000 gw-10.0.0.10 via port2"'. No further output appears. What is the MOST likely cause of the issue?

A.The VIP is configured with port forwarding, but the external port does not match the internal port.
B.The VIP is not configured with the correct external IP address.
C.The internal web server is not responding to the SYN packet, or the return traffic is being dropped by the FortiGate.
D.The firewall policy that allows traffic from the external interface to the VIP does not exist or is incorrect.
AnswerC

The debug flow output ends after the route lookup, meaning the FortiGate forwarded the packet to the internal server but did not receive a response. This indicates that either the server is not responding (e.g., service down, firewall on server) or the return traffic is being dropped by the FortiGate. Common causes include asymmetric routing, missing return policy, or the server's default gateway not pointing to the FortiGate. The administrator should check the server's status and the FortiGate's session table for return traffic.

Why this answer

The debug flow output indicates that the FortiGate received the SYN packet, allocated a session, and performed a route lookup to forward the packet to the internal server. However, no further output appears, meaning the FortiGate did not receive a SYN-ACK from the server. This points to either the server not responding or the return traffic being blocked.

The administrator should verify the server's availability and check for asymmetric routing or missing return policies that could drop the response.

Exam trap

The trap here is assuming that a missing firewall policy is the cause, but the debug flow shows a session was allocated, indicating the policy likely matched.

512
MCQeasy

Which feature allows a FortiGate to participate in multiple routing tables simultaneously, enabling network segmentation and overlapping IP address spaces?

A.VDOM
B.Policy-based routing
C.VRF
D.Route redistribution
AnswerC

VRF (virtual routing and forwarding) creates separate routing table instances on one FortiGate, allowing simultaneous participation in multiple routing domains. This satisfies the segmentation and overlapping IP address requirement, since each VRF maintains independent routes.

Why this answer

C is correct because VRF (Virtual Routing and Forwarding) allows a FortiGate to maintain multiple separate routing tables (RIB) on the same physical device. Each VRF instance operates as an independent routing domain, enabling network segmentation and the use of overlapping IP address spaces without conflict, which is essential for MPLS L3VPN and multi-tenant environments.

Exam trap

The trap here is that candidates often confuse VDOMs with VRFs, assuming VDOMs alone provide routing table separation, but VDOMs are a management and security context while VRFs are the actual mechanism for multiple routing tables and overlapping IP spaces.

How to eliminate wrong answers

Option A is wrong because VDOMs (Virtual Domains) provide administrative separation and independent firewall policies, but they do not inherently create multiple routing tables for overlapping IP spaces; VDOMs can use VRFs internally, but the feature directly responsible for multiple routing tables is VRF. Option B is wrong because policy-based routing (PBR) allows traffic to be forwarded based on policies (e.g., source/destination) rather than the routing table, but it does not create multiple independent routing tables; it only overrides the default routing decision for specific traffic. Option D is wrong because route redistribution is a mechanism to exchange routes between different routing protocols or routing tables, but it does not enable the existence of multiple routing tables; it assumes they already exist.

513
MCQeasy

An administrator needs to view real-time traffic logs and top applications for a specific VDOM on FortiAnalyzer. Which tool should be used?

A.FortiView
B.Playbooks
C.Incident Management
D.Reports
AnswerA

FortiView aggregates real-time logs into visual dashboards, letting the administrator filter by VDOM and immediately see top applications and traffic sessions. Unlike Log View, which shows raw log entries, FortiView provides the live, per-VDOM analytics the scenario demands.

Why this answer

FortiView is the correct tool because it provides real-time traffic logs and top applications per VDOM on FortiAnalyzer. It uses live data streams from FortiGate logs to display current network activity, allowing administrators to filter by VDOM and view metrics like top applications, sources, and destinations without running a report or script.

Exam trap

The trap here is that candidates confuse FortiView's real-time monitoring with Reports' historical analysis, assuming both can show live data, but only FortiView provides sub-second updates without requiring a scheduled or on-demand report generation.

How to eliminate wrong answers

Option B is wrong because Playbooks are used for automated threat response and remediation workflows, not for real-time log viewing or application monitoring. Option C is wrong because Incident Management focuses on investigating and managing security incidents from events like IPS or malware, not on displaying live traffic logs or top applications. Option D is wrong because Reports generate historical, scheduled summaries of log data, not real-time views; they require processing time and cannot show live traffic.

514
MCQhard

A company uses an advanced antivirus profile with machine learning engine enabled. After a recent outbreak, several files that were previously undetected are now flagged. How does the outbreak prevention feature help in this situation?

A.It downloads the latest ML models from FortiGuard to detect new threats
B.It sends all files to FortiSandbox for analysis
C.It quarantines all files for 24 hours until a signature is released
D.It blocks all executable files from being downloaded
AnswerA

FortiGuard's outbreak prevention service pushes updated machine learning models to the firewall, so the ML engine can identify the newly observed malware without waiting for signature updates. This satisfies the scenario's need to detect files that were previously undetected during an active outbreak.

Why this answer

The outbreak prevention feature in FortiGate's advanced antivirus profile automatically downloads the latest machine learning (ML) models from FortiGuard when a new outbreak is detected. This allows the ML engine to identify and flag previously undetected files without requiring a traditional signature update, enabling proactive detection of zero-day threats.

Exam trap

The trap here is that candidates often confuse outbreak prevention with FortiSandbox integration, assuming that all unknown files must be sandboxed, when in fact outbreak prevention leverages ML model updates for faster, inline detection without the latency of sandbox analysis.

How to eliminate wrong answers

Option B is wrong because outbreak prevention does not send all files to FortiSandbox; FortiSandbox is a separate advanced threat protection feature that performs behavioral analysis, and outbreak prevention focuses on updating ML models, not redirecting traffic. Option C is wrong because outbreak prevention does not quarantine files for a fixed 24-hour period; it uses real-time ML model updates to detect threats immediately, and quarantining without analysis would disrupt legitimate operations. Option D is wrong because outbreak prevention does not block all executable files; it selectively applies ML-based detection to identify malicious executables while allowing benign ones, avoiding the overly restrictive and impractical approach of blocking all executables.

515
MCQmedium

An administrator is troubleshooting why a FortiGate is dropping traffic from a specific source IP (10.1.1.100). The administrator wants to see real-time per-packet details including the reason for drops. Which CLI command should the administrator use?

A.diagnose debug enable
B.diagnose debug flow filter addr 10.1.1.100
C.diagnose debug flow filter addr 10.1.1.100 && diagnose debug flow trace start 100 && diagnose debug enable
D.diagnose debug flow trace start 100
AnswerC

This sequence correctly sets a filter for the source IP, starts a flow trace for 100 packets, and enables debug output. The 'diagnose debug flow' commands provide detailed per-packet information including the reason for drops, which is exactly what the administrator needs to troubleshoot the issue.

Why this answer

To troubleshoot dropped traffic from a specific source IP, the administrator must set a filter, start the flow trace, and enable debug output. The combination of 'diagnose debug flow filter addr', 'diagnose debug flow trace start', and 'diagnose debug enable' provides real-time per-packet details including drop reasons, allowing effective diagnosis.

Exam trap

The trap here is assuming that setting the filter alone or enabling debug globally is sufficient, when in fact all three steps are required to capture and display the relevant flow information.

516
MCQmedium

A FortiGate 600E is deployed with multiple VDOMs in NAT/route mode. The administrator assigns VLAN 100 to VDOM-A on port1 and VLAN 200 to VDOM-B on port1, then configures the VLAN interfaces as management interfaces for each VDOM. Users in VDOM-A report intermittent connectivity to servers in VDOM-B, while pings between the VLAN interface IPs fail. What is the most likely cause?

A.No inter-VDOM links or firewall policies exist to permit traffic between VDOM-A and VDOM-B, so the VDOMs are isolated by design.
B.Two VLAN interfaces with management access enabled cannot coexist on the same physical interface; the second VDOM's VLAN is silently ignored.
C.Management access on a VLAN interface enables the administrative gateway, which overrides inter-VDOM routing and blocks data traffic.
D.VLAN interfaces in different VDOMs on the same physical port require the physical interface to be in a third VDOM with explicit VLAN trunking.
AnswerA

By default, VDOMs are isolated from each other. Even though VLAN 100 and VLAN 200 share a physical port, traffic cannot pass between VDOM-A and VDOM-B without an inter-VDOM link (or VDOM link) and firewall policies in each VDOM. Pings between VLAN interface IPs fail because there is no route or policy. Adding inter-VDOM links and policies would enable communication. This is the expected behavior for VDOM isolation.

Why this answer

VDOMs on a FortiGate are isolated routing and security domains. Even when VLAN subinterfaces on the same physical port are assigned to different VDOMs, traffic between those VDOMs does not flow automatically. Inter-VDOM links must be created and firewall policies must allow the traffic in both directions.

The failed pings and intermittent connectivity are classic symptoms of missing inter-VDOM routing, not a limitation of VLAN coexistence or management access.

Exam trap

The trap here is assuming that VLAN interfaces on the same physical port automatically provide a path between VDOMs, when in fact VDOMs remain isolated until inter-VDOM links and policies are configured.

517
MCQmedium

An organization wants to use FortiManager to manage multiple FortiGate devices. The administrator needs to ensure that each device group has separate policy and object configurations. Which FortiManager feature should be configured?

A.Policy packages with header/footer policies
B.Administrative Domains (ADOMs)
C.Global ADOM
D.Meta fields
AnswerB

Administrative Domains partition FortiManager into isolated management spaces, each holding its own devices, policies and objects. Enabling ADOMs in advanced mode lets you assign separate ADOMs per device group, satisfying the requirement that each group's policy and object configurations remain distinct and independently managed.

Why this answer

Administrative Domains (ADOMs) in FortiManager allow you to partition the management database so that each ADOM has its own independent set of policy packages and objects. By assigning each device group to a separate ADOM, administrators ensure that policy and object configurations are isolated and cannot be shared or accidentally overwritten between groups. This directly meets the requirement for separate configurations per device group.

Exam trap

The trap here is that candidates may confuse ADOMs with VDOMs or think that header/footer policies can achieve configuration separation, but ADOMs are the only FortiManager feature that provides full administrative and configuration isolation between device groups.

How to eliminate wrong answers

Option A is wrong because header/footer policies are used to insert common policy rules at the top or bottom of a policy package across multiple devices, not to create separate policy and object configurations for different device groups. Option C is wrong because the Global ADOM is a special ADOM that contains global objects and policies shared across all other ADOMs, which would merge configurations rather than keep them separate. Option D is wrong because meta fields are custom fields used to store additional metadata about managed objects (e.g., contact info, location) and do not provide any mechanism for isolating policy or object configurations between device groups.

518
MCQeasy

What is the purpose of a management VDOM on a FortiGate?

A.To log all administrative actions
B.To route traffic between different VDOMs
C.To increase the number of available firewall policies
D.To provide a dedicated environment for administrative access and management protocols
AnswerD

A management VDOM isolates administrative traffic, so management protocols such as HTTPS, SSH and SNMP terminate in a dedicated VDOM rather than the production data path. This satisfies the requirement for segregated administrative access, preventing management-plane traffic from mixing with user traffic and enabling separate routing and firewall policies for administrators.

Why this answer

A management VDOM is a dedicated virtual domain that isolates administrative traffic (e.g., HTTPS, SSH, SNMP, syslog) from data-plane traffic. This ensures that management access and protocols like RADIUS or TACACS+ authentication are processed in a separate context, preventing interference with production VDOMs and allowing granular administrative access control.

Exam trap

The trap here is that candidates often confuse a management VDOM with a logging or inter-VDOM routing function, but Fortinet specifically designed it to isolate administrative access and protocols, not to perform data-plane tasks like routing or logging.

How to eliminate wrong answers

Option A is wrong because logging all administrative actions is a function of the local log or syslog configuration, not a purpose of a management VDOM; a management VDOM can be used to send logs, but its primary purpose is not logging. Option B is wrong because routing traffic between different VDOMs is done by inter-VDOM links (IVL) or VDOM peering, not by a management VDOM, which is specifically for administrative access. Option C is wrong because the number of available firewall policies is limited by the FortiGate model and license, not by the presence of a management VDOM; a management VDOM does not increase policy capacity.

519
MCQmedium

A FortiGate administrator is configuring an IPsec VPN with multiple peers for redundancy. The administrator wants to ensure that if the primary peer becomes unreachable, the tunnel fails over to the secondary peer automatically. Which configuration is required to achieve this?

A.Configure a single phase 1 with 'set remote-gw' as a DNS name that resolves to both peers, and enable DPD.
B.Create separate phase 1 configurations for each peer, and use a route-based VPN with multiple tunnel interfaces and a routing protocol to select the active path.
C.Use a single phase 1 with 'set remote-gw 0.0.0.0' and configure multiple dial-up VPNs, then rely on DPD to failover.
D.Configure a single phase 1 with multiple remote gateways and enable 'set dpd on-idle'.
AnswerB

To achieve redundancy with automatic failover, you need separate phase 1 configurations for each peer. Using route-based VPNs (with tunnel interfaces) allows dynamic routing protocols like BGP or OSPF to detect failures and reconverge, or you can use link monitoring with static routes. This setup ensures that if one peer goes down, traffic is rerouted through the other. This is the standard method for IPsec VPN redundancy.

Why this answer

Automatic failover between IPsec peers requires multiple phase 1 configurations, one for each peer. Route-based VPNs with tunnel interfaces allow dynamic routing protocols to detect failures and reconverge, or static routes with link monitoring can be used. This ensures that if the primary peer becomes unreachable, traffic is redirected to the secondary peer.

DPD alone only detects failure; it does not perform failover.

Exam trap

The trap here is assuming that DPD or a single phase 1 with a DNS name can provide automatic failover, but redundancy requires separate phase 1 entries and routing mechanisms.

520
MCQmedium

A company's FortiGate is configured with multiple IPsec VPN tunnels to branch offices. One tunnel keeps dropping and re-establishing every few minutes. The logs show 'IPsec SA negotiation failed' with error 'proposal mismatch'. What is the most likely cause?

A.Dead Peer Detection (DPD) configured too aggressively
B.Mismatched encryption or authentication algorithms between the two VPN peers
C.NAT-Traversal (NAT-T) not enabled
D.Pre-shared key mismatch
AnswerB

IPsec phase 2 requires both peers to agree on identical encryption and authentication algorithms, plus matching DH groups. A proposal mismatch means the two ends offer no common transform set, so the quick mode negotiation fails and the tunnel tears down, matching the repeated SA negotiation errors in the logs.

Why this answer

The error 'proposal mismatch' directly indicates that the two IPsec peers cannot agree on the security parameters for the IKE or IPsec SA. This occurs when the encryption algorithm (e.g., AES256 vs. AES128), authentication algorithm (e.g., SHA256 vs.

SHA1), Diffie-Hellman group, or lifetime values do not match between the FortiGate and the remote peer. The tunnel drops and re-establishes because the negotiation fails, and the FortiGate retries with the same mismatched proposal, leading to repeated failures.

Exam trap

The trap here is that candidates often confuse 'proposal mismatch' with authentication failures (pre-shared key) or connectivity issues (NAT-T/DPD), but the specific log message 'proposal mismatch' is a direct indicator of cryptographic parameter disagreement, not a key or transport layer problem.

How to eliminate wrong answers

Option A is wrong because Dead Peer Detection (DPD) being too aggressive would cause the tunnel to be torn down due to missed keepalives, not a 'proposal mismatch' error; DPD failures generate 'DPD timeout' or 'peer not responding' logs. Option C is wrong because NAT-Traversal (NAT-T) not being enabled would cause issues with UDP encapsulation when a NAT device is present, but the error would be 'no response from peer' or 'NAT detection failed', not a proposal mismatch. Option D is wrong because a pre-shared key mismatch would cause an authentication failure during IKE Phase 1, resulting in 'authentication failed' or 'invalid pre-shared key' errors, not a proposal mismatch.

521
MCQmedium

An administrator sees the following error when trying to commit changes from FortiManager to a FortiGate: 'Policy check failed: Policy ID 5 uses a zone that does not exist on the device.' What is the most likely cause?

A.The policy package is locked by another administrator
B.The zone referenced in the policy is not yet created on the FortiGate
C.The FortiGate is not running the same firmware version as FortiManager
D.The administrator has insufficient permissions
AnswerB

FortiManager validates policy objects against the target FortiGate's configuration before committing. Because the referenced zone does not exist on the device, the policy check fails. Creating the zone on the FortiGate, or removing the zone reference, resolves the commit error.

Why this answer

The error 'Policy check failed: Policy ID 5 uses a zone that does not exist on the device' indicates that the FortiGate does not have the zone object referenced in the policy. When FortiManager pushes a policy that references a zone, the zone must already exist on the managed FortiGate; otherwise, the commit fails. Option B correctly identifies that the zone is missing on the FortiGate.

Exam trap

The trap here is that candidates may confuse a missing object error with a firmware version mismatch or permission issue, but the error message explicitly names the missing zone, making the root cause straightforward if read carefully.

How to eliminate wrong answers

Option A is wrong because a locked policy package would produce a different error, such as 'Policy package is locked by another administrator', not a zone existence error. Option C is wrong because firmware version mismatches typically cause compatibility warnings or installation failures, not a specific zone-not-found error. Option D is wrong because insufficient permissions would result in an authorization failure or 'Permission denied' error, not a policy check failure referencing a missing zone.

522
MCQeasy

An administrator wants to secure email traffic by ensuring that incoming emails are verified against the sender's domain SPF record. Which email authentication method provides this verification?

A.DKIM
B.SPF
C.DMARC
D.S/MIME
AnswerB

SPF publishes authorised sending hosts in DNS TXT records, letting the receiving server verify that the sending IP is permitted for the sender's domain. This directly satisfies the requirement to validate incoming email against the sender's domain SPF record.

Why this answer

SPF (Sender Policy Framework) is the email authentication method that verifies incoming emails against the sender's domain SPF record. It works by checking whether the sending mail server's IP address is authorized by the domain owner's DNS TXT record. This directly matches the administrator's requirement to verify incoming emails against the sender's domain SPF record.

Exam trap

The trap here is that candidates often confuse DKIM's signature verification with SPF's IP-based authorization, mistakenly thinking DKIM verifies the sender's domain against an SPF record.

How to eliminate wrong answers

Option A is wrong because DKIM (DomainKeys Identified Mail) uses a digital signature to verify that an email was not tampered with during transit, but it does not check the sending server's IP against the domain's SPF record. Option C is wrong because DMARC (Domain-based Message Authentication, Reporting & Conformance) builds on SPF and DKIM to provide policy enforcement and reporting, but it does not itself perform IP-based verification against an SPF record. Option D is wrong because S/MIME (Secure/Multipurpose Internet Mail Extensions) provides end-to-end encryption and signing using certificates, but it has nothing to do with verifying the sending server's IP against a domain's SPF record.

523
MCQmedium

An administrator is troubleshooting SD-WAN and runs the following CLI command: 'execute sdwan-health-check status' The output shows that one SD-WAN member has a status of 'dead'. What does this indicate?

A.The member interface is administratively down
B.The member is not meeting the performance SLA thresholds
C.The SD-WAN member is not included in any SD-WAN rule
D.The member has failed the health check probe to the target server
AnswerD

The health-check probe targets a configured server; a 'dead' status means probes from that member are failing, so it is excluded from SD-WAN path selection. This satisfies the stem's constraint of identifying why one member is unusable.

Why this answer

The 'execute sdwan-health-check status' command displays the results of active health-check probes sent to configured target servers. A status of 'dead' means that the SD-WAN member has failed to receive a successful response from the target server within the configured probe interval and retry count, indicating a loss of connectivity or reachability to that target. This is distinct from interface administrative status or SLA compliance, as the health check specifically tests end-to-end reachability to the probe target.

Exam trap

The trap here is confusing 'dead' (probe failure) with 'SLA violation' (performance threshold breach), as candidates often assume a dead member means it failed SLA metrics, but the health check status is binary—alive or dead—based solely on probe reachability, not on latency or jitter thresholds.

How to eliminate wrong answers

Option A is wrong because 'administratively down' is a separate interface state shown by 'show interface' or 'get system interface', not by the SD-WAN health check status command; a dead health check does not imply the interface is disabled. Option B is wrong because performance SLA thresholds (e.g., latency, jitter, packet loss) are measured separately and a member can be 'dead' even if it meets SLA metrics, as 'dead' indicates probe failure, not SLA violation. Option C is wrong because an SD-WAN member not included in any rule would simply not be used for traffic steering, but its health check status would still be reported as 'alive' or 'dead' based on probe results; exclusion from rules does not cause a 'dead' status.

524
MCQhard

An administrator is configuring FortiAnalyzer to receive logs from FortiGates in a multi-VDOM environment. The admin wants to ensure that logs from each VDOM are separated into their own datasets. What must be configured?

A.Enable per-VDOM logging on the FortiGate and use ADOMs on FortiAnalyzer
B.Use the same log settings for all VDOMs
C.Configure a separate log disk partition for each VDOM
D.Configure each VDOM to send logs to a different FortiAnalyzer
AnswerA

Per-VDOM logging makes the FortiGate tag each log with its originating VDOM, while ADOMs partition FortiAnalyzer's database so each VDOM's logs land in a separate dataset. This satisfies the stem's requirement for VDOM-level log separation in a multi-VDOM environment.

Why this answer

Per-VDOM logging on the FortiGate must be enabled to tag logs with the VDOM identifier, and ADOMs on FortiAnalyzer must be configured to segregate those logs into separate datasets. Without both, logs from different VDOMs would be mixed in a single dataset, defeating the purpose of isolation.

Exam trap

The trap here is that candidates often think disk partitions or separate FortiAnalyzers are required for log separation, but FortiAnalyzer ADOMs provide logical separation without additional hardware or complex partitioning.

How to eliminate wrong answers

Option B is wrong because using the same log settings for all VDOMs would not separate logs; it would cause all VDOM logs to be stored together in a single dataset on FortiAnalyzer. Option C is wrong because FortiAnalyzer does not support per-VDOM disk partitions; disk partitions are system-level and not tied to VDOMs. Option D is wrong because sending logs from each VDOM to a different FortiAnalyzer is unnecessary and inefficient; the correct approach is to use ADOMs on a single FortiAnalyzer to logically separate the data.

525
MCQeasy

Which FortiManager feature allows administrators to view the exact configuration changes that would be applied to a managed FortiGate before committing them?

A.Revision history
B.Install preview
C.Device manager
D.Policy checker
AnswerB

Install preview generates a comparison showing the exact configuration differences that would be pushed to a managed FortiGate, letting administrators inspect pending changes before committing them, which is precisely the pre-commit visibility the stem requires.

Why this answer

Install preview is the correct answer because it allows administrators to see the exact CLI commands that will be pushed to a managed FortiGate during the next install operation, without actually applying them. This feature provides a diff-like view of the configuration changes, enabling validation before committing changes to production devices.

Exam trap

The trap here is that candidates often confuse 'revision history' (which shows past configurations) with the ability to preview future changes, leading them to select Option A instead of recognizing Install Preview as the specific pre-commit review tool.

How to eliminate wrong answers

Option A is wrong because revision history stores previous configuration snapshots for rollback purposes, not a preview of pending changes. Option C is wrong because Device Manager is the overall interface for managing device configurations, not a specific feature for previewing changes before commit. Option D is wrong because Policy Checker is used to validate firewall policy consistency and conflicts, not to display pending configuration changes.

Page 6

Page 7 of 10

Page 8

All pages