According to the OT Security 7.6 Architect study guide regarding the Purdue Model :

Asset Location : The study guide states that " All critical physical assets are located on the plant floor and equipped with IIoT sensors. "

Level Classification : The " plant floor " is further defined as the " control area zone, " which consists of Levels 0, 1, and 2 .

Hierarchy : The " Operations & Control " zone is identified as Level 3 and Level 3.5 .

Direct Answer : In the " Introduction " lesson ' s Knowledge Check , the specific question " In the Purdue model, at which level are IIoTs placed? " is provided with the verified answer: Below Level 3.5 .

Based on the OT Security 7.6 Architect study guide regarding the Asset Identity Center and Asset Management :

Vulnerability Visibility : The Asset Identity List tab displays key metadata for IT and OT devices, including detected addresses, users, and a specific column for Vulnerabilities .

Virtual Patching Feature : In the OT Security 7.6 architecture, the " Vulnerabilities " column is populated through the OT Security Service license, which includes " OT vulnerability correlation definitions & virtual patching signatures " .

Correlation Mechanism : FortiGate extracts metadata from OT traffic and uses these signatures to identify known vulnerabilities on the assets. For these vulnerabilities to be identified and correlated in the Asset Identity Center as shown in the exhibit (displaying a count of 8 vulnerabilities), the Virtual Patching feature must be active.

Architectural Implementation : Virtual patching is a critical component of the " Protection " layer in OT networks, allowing administrators to secure legacy or unpatchable PLCs and RTUs by blocking exploit attempts at the network level using IPS-based virtual patching signatures.

Exhibit Analysis : The presence of identified vulnerabilities (the number " 8 " in the red shield) in the Asset Identity List confirms that the FortiGate is actively performing vulnerability correlation, which is the operational result of having a Virtual Patching security profile applied to the relevant firewall policy.

The correct answer is A . The study guide states that “The OT view is not available by default. You must enable it in the Feature Visibility section of the GUI or using the CLI command shown on this slide” and shows config system settings → set gui-ot enable . It also says that “After you enable the feature, the Asset Identity Center contains an Asset Identity List tab and an OT View tab.” This directly explains why the OT View tab is missing: the feature that enables the Purdue-style OT display has not been enabled yet.

The OT View is the view that displays devices in a Purdue diagram , and the Asset Identity List also shows the current Purdue level for each device. Because the answer options do not explicitly say enable OT View in Feature Visibility , option A is the intended match, since it refers to enabling the Purdue-related OT display feature. Option B is incorrect because device detection affects visibility of devices, not whether the OT View tab exists. Option C is not supported by the study guide, and option D is also not given as the requirement for showing the OT View tab.

Comprehensive and Detailed Explanation From Exact Extract of OT Security 7.6 Study guides:

The correct answers are A and C .

A is correct because the exhibit explicitly shows Logging & Analytics → FortiAnalyzer: Disabled on this FortiGate. The FortiGate must therefore have its FortiAnalyzer logging destination enabled and configured. The study guide explains that the FortiAnalyzer Fabric connector consolidates traffic logs and, importantly, that “each FortiGate in the Security Fabric logs traffic to FortiAnalyzer independent of the root or other leaf devices.” This means each FortiGate requires its own functioning logging connection to FortiAnalyzer; being a Security Fabric member alone does not cause its logs to pass through the root FortiGate.

C is correct because FortiAnalyzer must accept and authorize the FortiGate as a managed/logging device before the FortiGate can establish the normal logging relationship. This complements the FortiGate-side Logging & Analytics configuration. The study guide ' s Security Fabric logging architecture shows individual FortiGate devices maintaining FortiAnalyzer log connections , with FortiAnalyzer receiving and correlating their traffic and UTM logs. It specifically states that if the root FortiGate is unavailable, logging from leaf FortiGate devices to FortiAnalyzer continues to function , confirming that the FortiGate-to-FortiAnalyzer logging relationship is direct.

B is incorrect because configuring Fabric settings on FortiAnalyzer is not the missing step indicated by the exhibit. The problem shown is that FortiAnalyzer logging is Disabled on the FortiGate .

D is incorrect because authorization on the root FortiGate concerns joining and trusting a FortiGate as a Security Fabric member. It does not authorize that FortiGate as a logging device on FortiAnalyzer. The study guide explicitly distinguishes the architecture by stating that every FortiGate logs to FortiAnalyzer independently of the root .

The correct answer is B . A historically flat OT network permits excessive east-west communication, allowing a compromised host to move laterally toward other controllers, HMIs, and critical systems. Fortinet recommends microsegmentation to control these communication paths. The study guide explains that microsegmentation controls intra-VLAN traffic through firewall policies , prevents hosts in the same segment from directly seeing or communicating with each other, and forces permitted communication through an enforcement point such as FortiGate. This provides granular host isolation and increased traffic visibility for monitoring and threat hunting. A normal hardware switch does not inherently impose the required security policies and therefore does not adequately restrict lateral movement. SD-WAN addresses WAN path selection and resilience, while two-factor authentication strengthens user authentication but does not control device-to-device traffic inside a flat process or control network. Therefore, firewall-based microsegmentation is the required architectural control.

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

The correct answer is C. You can implement parallel redundancy protocol . The study guide explains that media redundancy involves creating a backup path that can be used when part of the network fails and specifically states that “Parallel Redundancy Protocol (PRP) can be used for a star topology.” Since the problem described is many disconnections in the links , the issue is link availability, which is a media redundancy problem rather than a firewall virtualization or policy separation problem. PRP is designed to provide a backup communication path with low recovery time when links fail.

The other options do not fit this scenario as well. HA clusters are described in the guide as a solution for network node redundancy , where a backup firewall or switch takes over when the primary device fails. SD-WAN is recommended for remote site access across multiple WAN links, not for the local floor links shown in this topology. VDOMs provide logical segmentation, not link redundancy or higher link availability. Because the question is specifically about repeated link disconnections , the best action is to implement PRP .