The correct answer is C . This scenario is the precise use case for virtual patching . The OT Security 7.6 study guide states that virtual patching protects OT devices that have not yet been updated against vulnerability exploits . FortiGate identifies the vulnerable asset, queries FortiGuard for device-specific vulnerabilities and mitigation rules, receives applicable OT virtual-patching signatures, and maps those rules to the device. When traffic associated with the vulnerable asset reaches FortiGate, the firewall policy containing the virtual-patching profile applies the protection. In the topology, FortiGate_Level2 is the enforcement point immediately protecting PLC-1 and the control-network assets. IPS at Level 5 provides broader perimeter protection, but it is not the device-specific compensating control requested here. Application Control primarily regulates industrial protocols and commands. Therefore, Virtual patching on FortiGate_Level2 is required.

================

The correct answer is A . Policy ID 8 contains the Supervisors user group, so authentication is required for traffic matching that policy. However, policy ID 9 permits traffic to PLC-1 without a user or user-group authentication requirement. Fortinet explains that when an authentication policy is followed by a fall-through policy that does not require authentication , traffic can match the fall-through policy and proceed without generating a login prompt. This is particularly relevant because the default CLI setting is auth-on-demand implicitly. Under the default implicitly behavior, FortiGate does not trigger active authentication when a matching unauthenticated fall-through policy exists. Setting auth-on-demand always, or requiring authentication on all potentially matching policies, changes that behavior. Therefore, HTTPS succeeds without prompting because authentication was not configured on firewall policy ID 9 .

The correct answer is D . Removing the air gap creates connectivity between the OT environment and external networks, significantly increasing exposure to unauthorized access and cyberattacks. Fortinet explains that the expansion of remote connectivity and IT/OT interconnections increases the OT attack surface and that the modern threat landscape requires IPS to block a wider range of threats . In the shown Purdue-style topology, FortiGate_Level5 is positioned at the upper boundary toward external connectivity and is therefore the appropriate enforcement point for protecting against attacks entering from outside the OT environment. Virtual patching at Level 2 is intended primarily to compensate for known vulnerabilities on specific OT devices that cannot yet be patched. Application Control provides industrial protocol visibility and command-level control, while merely enabling OT signatures at Level 3 does not replace perimeter intrusion prevention. Consequently, IPS belongs on FortiGate_Level5 .

================

According to the OT Security 7.6 Architect study guide regarding FortiAnalyzer Event Management :

Notification Options : When configuring a new event handler, FortiAnalyzer provides several built-in notification methods to alert administrators when specific log criteria are met. The most common and direct method is Send alert email (Option A).

Incident Management : To streamline the SOC workflow, an event handler can be configured to Automatically create an incident (Option D) based on the triggered event. This moves the event into the Incident Manager for further analysis.

Security Fabric Integration : In the 7.6 architecture, event handlers can directly trigger an Automation stitch (Option E). This allows the FortiAnalyzer to notify the root FortiGate to take action (like running a CLI script or changing a policy) across the Security Fabric.

Exclusions : Create a report (Option B) is typically a task performed by a Playbook or a scheduled report job, not a direct setting inside the basic event handler configuration. Quarantine an attacker (Option C) is an action that results from an automation stitch or playbook, but it is not a direct configuration toggle within the event handler itself.

The correct answer is A. FortiGate queries FortiGuard servers . The study guide explains the device detection process very clearly: “First, FortiGate attempts to detect the devices based on the information in the local device database (CIDB). If FortiGate cannot detect the devices locally, it queries the FortiGuard servers by sending data about the unknown devices to the FortiGuard servers. In response, the FortiGuard servers provide additional information about those devices.” This directly answers the question and shows that querying FortiGuard is the next step after local detection fails.

Option D is incorrect because the guide says FortiGate checks the local device database (CIDB) first, before this next step. Option B refers more to FortiNAC-style profiling logic, not FortiGate’s OT device detection flow. Option C is also incorrect because service connectors are not described here as the immediate follow-up step for unknown local device detection. The study guide specifically identifies FortiGuard servers as the next destination for device identification assistance.

The correct answer is D. You can configure forward domain IDs for each network .

The study guide explains that in FortiGate transparent mode, all interfaces belong to the same broadcast domain, even interfaces with different VLAN IDs , and then states that you can “subdivide into multiple broadcast domains” by configuring set forward-domain <</b> domain_ID > . It also states that “interfaces with the same domain ID belong to the same broadcast domain” and, with multiple forward domains, “traffic arriving on one interface is broadcast only to interfaces in the same forward domain ID.” That is the mechanism used to separate internal networks and confine traffic between network segments.

The other options do not fit this requirement. Universal ZTNA is for application access control, not segmentation between two OT networks. One traffic VDOM does not create segmentation by itself; multiple VDOMs would be needed for that type of isolation. An explicit software switch controls intraswitch traffic inside the same software-switch domain, not segmentation between separate networks like network 1 and network 2. Therefore, the correct way to implement the internal segmentation asked in the question is to assign different forward domain IDs to each network.