NSE7_SOC_AR-7.6 Fortinet NSE 7 - Security Operations 7.6 Architect Free Practice Exam Questions (2026 Updated)

The built-in Jinja editor in FortiSOAR 7.6 is a powerful utility designed to help playbook developers write and test complex data manipulation logic without having to execute the entire playbook. Its primary capabilities include:

Renders output (A): The editor provides a " Preview " or " Evaluation " pane. By combining a Jinja expression with a sample JSON input (manually entered or loaded), the editor dynamically calculates and displays the resulting output. This allows for immediate verification of data transformation logic.

Checks validity (B): The editor includes built-in linting and syntax validation. It alerts the developer to errors such as unclosed brackets, incorrect filter usage, or invalid syntax, ensuring that only valid Jinja code is saved into the playbook step.

Loads environment JSON (D): One of the most significant features for troubleshooting is the ability to load the environment JSON from a recent execution. This populates the editor ' s variable context (vars) with the actual data from a specific playbook run, allowing the developer to test expressions against real-world data that recently passed through the system.

Why other options are incorrect:

Creates new records in bulk (C): While Jinja expressions are used to format the data that goes into a record, the actual creation of records is handled by the " Create Record " step or specific Connectors, not by the Jinja editor utility itself.

Defines conditions to trigger a playbook step (E): Jinja is the language used to write conditions within a " Decision " step or " Step Utilities, " but the Jinja Editor is a tool for evaluating and testing those expressions. The definition of the condition logic and the triggering behavior is a function of the Playbook Engine and Step configuration, not the editor ' s standalone capabilities.

In FortiAnalyzer 7.6 and related SOC versions, incidents serve as centralized containers for tracking and analyzing security events. There are two primary automated and manual methods to initiate an incident:

Using a custom event handler (A): In FortiAnalyzer, event handlers are used to generate events from raw logs.1 A critical feature in recent versions is the Automatically Create Incident setting within a custom event handler.2 When enabled, the system automatically elevates a triggered event into a new incident record, allowing analysts to bypass the manual review of every individual event before an incident is raised.3

By running a playbook (D): Playbooks provide a powerful way to automate the incident lifecycle.4 A playbook can be configured with an Event Trigger, meaning it executes as soon as an event matches specific criteria. One of the core actions available within these playbooks is the Create Incident action, which can automatically populate incident details, severity, and category based on the triggering event ' s data.5 This ensures high-fidelity events are consistently captured for investigation.

Why other options are incorrect:

Using a connector action (B): While connectors allow FortiAnalyzer to communicate with external systems (like ITSM or Security Fabric devices), the act of " creating an incident " inside FortiAnalyzer is a function of the internal event engine or playbook automation, not a standalone connector action used for external integration.

Manually, on the Event Monitor page (C): While you can view, filter, and acknowledge events on the Event Monitor page, the process of manually raising an incident typically occurs from the Incidents module or by right-clicking an event to " Raise Incident " in the Log View or FortiView, rather than being a core function defined as occurring " on the Event Monitor page " in the same architectural sense as handlers and playbooks.

Exact Extract: “FortiSOAR incident handling phases are closely aligned with NIST incident handling phases… The Post-Incident Activity phase is renamed Aftermath. Functionally, they are identical.”

Exact Extract: “Use the Update Record step to update a record in a module within FortiSOAR. Use the Find Record step to find a record in a module within FortiSOAR.”

Exact Extract: “Use the Manual Task step to pause the playbook’s execution until you mark the task as skipped or completed.”

The correct answers are C, D, and E. The workflow must start when an existing incident is changed to the Aftermath phase, so the correct trigger is an On Update trigger with a condition that matches the incident phase. After the trigger fires, the incident already exists as the current playbook record, so a Find Record step is unnecessary. To set the incident status to Resolved and assign the purple team specialist as the incident lead, use an Update Record step. To create and assign the follow-up work item, use a Manual Task step assigned to the same specialist.

Option B is wrong because a Condition/Decision step evaluates logic; it does not assign records or create work. Option A is wrong because the playbook is already triggered by the updated incident record, so searching for matching incidents adds unnecessary complexity.

Technical Deep Dive: The clean playbook structure is: On Update trigger → Update Record → Manual Task. The trigger condition should check the incident phase field for Aftermath. The Update Record step should modify the current incident, setting fields such as Status = Resolved and Incident Lead = purple team specialist. The Manual Task step then creates analyst-visible work, such as “Write incident report,” assigned to that same user. This is FortiSOAR workflow automation; FortiGate NP/CP hardware offloading is irrelevant because there is no traffic-forwarding path involved.

To establish a successful integration between FortiSOAR 7.6 and a FortiGate firewall via the FortiGate connector, specific administrative and network requirements must be met on the FortiGate side:

API Administrator and Key (D): FortiSOAR does not use standard UI login credentials. Instead, it requires a REST API Administrator account to be created on the FortiGate. This account must be assigned an administrative profile with the necessary permissions (e.g., Read/Write for Firewall policies or Address objects). Upon creation, the FortiGate generates a unique API Key, which must be entered into the " API Key " field of the FortiSOAR configuration wizard as shown in the exhibit.

HTTPS Management Access (C): The connector communicates with the FortiGate using REST API calls over HTTPS (port 443 by default). Therefore, the physical or logical interface on the FortiGate that corresponds to the " Hostname " IP (172.16.200.1) must have HTTPS enabled under " Administrative Access " in its network settings. If HTTPS is disabled, the connection will time out or be refused.

Why other options are incorrect:

Trusted hosts (A): While it is a best practice to restrict API access to specific IPs (like the FortiSOAR IP), the integration can technically function without " Trusted hosts " enabled if the network allows the traffic. However, the absence of an API key or HTTPS access will definitively cause a failure regardless of trusted host settings.

VDOM name (B): In the exhibit, the VDOM field contains multiple values ( " VDOM_1 " , " VDOM_2 " ). If VDOMs are disabled on the FortiGate, this field should generally be left blank or set to the default " root. " Setting it specifically to " VDOM_1 " when VDOMs are disabled is not a universal requirement for connectivity; the primary handshake depends on the API key and HTTPS connectivity.

The Pyramid of Pain (David Bianco) is a core concept taught in FortiSIEM 7.3 and FortiSOAR 7.6 curriculum to help SOC analysts prioritize threat intelligence and detection logic. The model ranks indicators based on the " pain " or effort they cause an adversary to change:

IP Addresses (Easy): These are classified as " Easy " to change. An attacker can simply rotate through a proxy service, use a different VPS, or utilize a new compromised host to continue their campaign. While more valuable than a file hash, they provide relatively low-long term value to the defender because they are so ephemeral.

TTPs (Tough/Hard): This is the apex of the pyramid. TTPs (Tactics, Techniques, and Procedures) represent the fundamental way an adversary operates. If a defender successfully detects and blocks a Tactic (e.g., a specific way an attacker performs privilege escalation), the adversary is forced to reinvent their entire operational process, which is time-consuming and difficult.

Why other options are incorrect:

Artifacts (C): According to the pyramid, Network/Host Artifacts are classified as " Annoying " , not " Easy " . While an attacker can change them, it requires modifying their code or script behavior, which causes more friction than simply switching an IP address.

Tools (D): Tools are classified as " Challenging " . While alternatives exist, an adversary usually invests significant time mastering a specific toolset; losing the ability to use that tool effectively disrupts their efficiency significantly.

Understanding the Playbook and its Components:

The exhibit shows a playbook in which an event trigger starts actions upon detecting a malicious file.

The initial tasks in the playbook include CREATE_INCIDENT and GET_EVENTS.

Analysis of Current Tasks:

EVENT_TRIGGER STARTER: This initiates the playbook when a specified event (malicious file detection) occurs.

CREATE_INCIDENT: This task likely creates a new incident in the incident management system for tracking and response.

GET_EVENTS: This task retrieves the event details related to the detected malicious file.

Objective of the Next Task:

The next logical step after creating an incident and retrieving event details is to update the incident with the event data, ensuring all relevant information is attached to the incident record.

This helps SOC analysts by consolidating all pertinent details within the incident record, facilitating efficient tracking and response.

Evaluating the Options:

Option A: Update Asset and Identity is not directly relevant to attaching event data to the incident.

Option B: Attach Data to Incident sounds plausible but typically, updating an incident involves more comprehensive changes including status updates, adding comments, and other data modifications.

Option C: Run Report is irrelevant in this context as the goal is to update the incident with event data.

Option D: Update Incident is the most suitable action for incorporating event data into the existing incident record.

Conclusion:

The next task in the playbook should be to update the incident with the event data to ensure the incident reflects all necessary information for further investigation and response.

Understanding the MITRE ATT & CK Framework:

The MITRE ATT & CK framework is a comprehensive matrix of tactics and techniques used by adversaries to achieve their objectives.

It is widely used for understanding adversary behavior, improving defense strategies, and conducting security assessments.

Analyzing the Options:

Option A: The framework provides detailed technical descriptions of adversary activities, including specific techniques and subtechniques.

Option B: The framework includes information about mitigations and detections for each technique and subtechnique, providing comprehensive guidance.

Option C: MITRE ATT & CK covers a wide range of attack vectors, including those targeting user endpoints, network devices, and servers.

Option D: Some techniques or subtechniques do indeed fall under multiple tactics, reflecting the complex nature of adversary activities that can serve different objectives.

Conclusion:

The statement that best describes the MITRE ATT & CK framework is that it contains some techniques or subtechniques that fall under more than one tactic.