Refer to the exhibit. You configure SD-WAN on a standalone FortiGate device. You want to create an SD-WAN rule that steers traffic related to Facebook and LinkedIn through the less costly internet link. What must you do to set Facebook and LinkedIn applications as destinations from the GUI?
Correct Answer: B
According to the SD-WAN 7.6 Core Administrator curriculum and the FortiOS 7.6 Administration Guide , setting common web-based services like Facebook and LinkedIn as destinations in an SD-WAN rule is primarily accomplished through the Internet Service Database (ISDB) . * Internet Service vs. Application Control : In FortiOS, there is a distinction between Internet Services (which use a database of known IP addresses and ports to identify traffic at the first packet) and Applications (which require the IPS engine to inspect deeper into the packet flow to identify Layer 7 signatures). * SD-WAN Efficiency : Fortinet recommends using the Internet service field for services like Facebook and LinkedIn in SD-WAN rules because it allows the FortiGate to steer the traffic immediately upon the first packet. If the " Application " signatures were used instead, the first session might be misrouted because the application is not identified until after the initial handshake. * GUI Configuration : As shown in the exhibit (image_b3a4c2.png), the " Destination " section of an SD-WAN rule includes an Internet service field by default. To steer Facebook and LinkedIn traffic, the administrator simply clicks the " + " icon in that field and selects the entries for Facebook and LinkedIn from the database. * Feature Visibility (Alternative) : While you can enable a specific " Application " field in System > Feature Visibility (by enabling " Application Detection Based SD-WAN " ), this is typically used for less common applications that do not have dedicated ISDB entries. For the specific " applications " mentioned (Facebook and LinkedIn), they are natively available in the Internet service field, making Option B the most direct and common implementation. Why other options are incorrect : * Option A : Licensing for application signatures is part of the standard FortiGuard services and is not a prerequisite specific only to " applications as destinations " in SD-WAN rules. * Option C : Standalone FortiGate devices fully support application-based and ISDB-based steering in SD-WAN rules. * Option D : While enabling feature visibility would add an additional field for L7 applications, it is not a " must " for Facebook and LinkedIn, which are already accessible via the Internet Service field provided in the default GUI layout.
Question 22
SD-WAN interacts with many other FortiGate features. Some of them are required to allow SD-WAN to steer the traffic. Which three configuration elements must you configure before FortiGate can steer traffic according to SD- WAN rules? (Choose three.)
Correct Answer: A,C,D
According to theSD-WAN 7.6 Core Administratorstudy guide and theFortiOS 7.6 Administration Guide, for the FortiGate SD-WAN engine to successfully steer traffic using SD-WAN rules, three fundamental configuration components must be in place. This is because the SD-WAN rule lookup occurs only after certain initial conditions are met in the packet flow: * Interfaces (Option C):You must first define the physical or logical interfaces (such as ISP links, LTE, or VPN tunnels) asSD-WAN members. These members are then typically grouped intoSD-WAN Zones. Without designated member interfaces, there is no "pool" of links for the SD-WAN rules to select from. * Routing (Option D):For a packet to even be considered by the SD-WAN engine, there must be a matching route in theForwarding Information Base (FIB). Usually, this is a static route where the destination is the network you want to reach, and the gateway interface is set to theSD-WAN virtual interface(or a specific SD-WAN zone). If there is no route pointing to SD-WAN, the FortiGate will use other routing table entries (like a standard static route) and bypass the SD-WAN rule-based steering logic entirely. * Firewall Policies (Option A):In FortiOS, no traffic is allowed to pass through the device unless a Firewall Policypermits it. To steer traffic, you must have a policy where theIncoming Interfaceis the internal network and theOutgoing Interfaceis the SD-WAN zone (or the virtual-wan-link). The SD- WAN rule selection happens during the "Dirty" session state, which requires a policy match to proceed with the session creation. Why other options are incorrect: * Security Profiles (Option B):While mandatory forApplication-levelsteering (to identify L7 signatures), basic SD-WAN steering based on IP addresses, ports, or ISDB objects does not require security profiles to be active. * Traffic Shaping (Option E):This is an optimization feature used to manage bandwidth once steering is already determined; it is not a prerequisite for the steering engine itself to function.
Question 23
Refer to the exhibits. Two SD-WAN event logs, the member status, the SD-WAN rule configuration, and the health-check configuration for a FortiGate device are shown. Immediately after the log messages are displayed, how will the FortiGate steer the traffic based on the information shown in the exhibits? (Choose one answer)
Correct Answer: C
According to the SD-WAN 7.6 Core Administrator curriculum and the provided exhibits, the traffic steering decision is determined by the interaction between the Lowest Cost (SLA) strategy and the link health status reported in the event logs. Rule Strategy (Lowest Cost SLA): The SD-WAN rule configuration for ID 1 (named Critical-DIA) is set to mode sla. In this mode, the FortiGate will only steer traffic through member interfaces that satisfy the assigned Performance SLA targets. Member Preference: The rule defines priority-members 1 2. This means that under normal conditions (where both links are healthy), Member 1 (port1) is the preferred interface because it is listed first. Event Log Analysis: The first log message explicitly states: " Member status changed. Member out-of-sla. " for Member 1. This indicates that port1 has exceeded one of the thresholds (latency, jitter, or packet loss) defined in the Corp_HC health check. The second log confirms: " Number of pass member changed. New Value: 1, Old Value: 2 " . This verifies that while there were previously two links passing the SLA, now only one link (Member 2/port2) remains in a passing state. Steering Decision: Because the rule strategy is mode sla and the primary preferred member (port1) is now out- of-sla, the FortiGate immediately disqualifies Member 1 from the selection pool for this specific rule. It then moves to the next available member in the priority list that does satisfy the SLA, which is Member 2 (port2). Why other options are incorrect: Option A: FortiGate will not load balance or choose between both links because port1 is currently ineligible due to the SLA failure. Option B: Steering to port1 would violate the " Lowest Cost (SLA) " rule logic, as that link is no longer meeting the required health standards. Option D: FortiGate does not " skip " the rule unless no members meet the SLA and there is no fallback configured; in this scenario, port2 is still passing and available.
Question 24
Which statement about security posture tags in FortiSASE is correct?
Correct Answer: B
According to the FortiSASE 7.6 Administration Guide and FCP - FortiSASE 24/25 Administrator curriculum, security posture tags (often referred to as ZTNA tags) are the fundamental building blocks for identity-based and posture-based access control. * Multiple Tag Assignment : A single endpoint can be assigned multiple tags at the same time. For example, an endpoint might simultaneously have the tags " OS-Windows-11 " , " AV-Running " , and " Corporate-Domain-Joined " . * Evaluation Logic : During the policy evaluation process (for both SIA and SPA), FortiSASE or the FortiGate hub considers all tags assigned to the endpoint. Security policies can be configured to use these tags as source criteria. If an administrator defines a policy that requires both " AV-Running " and " Corporate-Domain-Joined, " the system evaluates both tags to decide whether to permit the traffic. * Dynamic Nature : Contrary to Option C, these tags are highly dynamic. They are automatically applied or removed in real-time based on the telemetry data sent by the FortiClient to the SASE cloud. If a user disables their antivirus, the " AV-Running " tag is removed immediately, and the endpoint ' s access is revoked by the next policy evaluation. * Scalability : While the system supports many tags, documentation recommends a baseline of custom tags for optimal performance, though it confirms that multiple tags are standard for reflecting a comprehensive security posture. Why other options are incorrect: * Option A : This is incorrect because the system does not pick just one tag; it evaluates the collection of tags against the policy ' s requirements (e.g., matching any or matching all). * Option C : This is incorrect because tags are dynamic and change as soon as the endpoint ' s status (like vulnerability count or software presence) changes. * Option D : This is incorrect because the architectural advantage of ZTNA is the ability to layer multiple security " checks " (tags) for a single user.
Question 25
Which authentication method overrides any other previously configured user authentication on FortiSASE?
Correct Answer: D
In FortiSASE, SSO authentication takes precedence over all other configured authentication methods. When SSO is enabled, it overrides local, RADIUS, and MFA user authentication settings.