順便提一下，可以從雲存儲中下載KaoGuTi NSE7_SOC_AR-7.6考試題庫的完整版：https://drive.google.com/open?id=1DCzjTr7vlyD2RgeuuA_4Zv1knc9wDXmz
KaoGuTi是領先于世界的學習資料提供商之一，您可以下載我們最新的PDF版本免費試用作為體驗。我們還提供可靠和有效的軟件版本NSE7_SOC_AR-7.6題庫資料，幫助您模擬真實的考試環境，以方便考生掌握最新的Fortinet NSE7_SOC_AR-7.6考試資訊。在我們的指導和幫助下，可以首次通過您的考試，NSE7_SOC_AR-7.6考古題是IT專家經過實踐測試得到的，NSE7_SOC_AR-7.6考古題也能幫您在IT行業的未來達到更高的水平。
| 主題 | 簡介 |
|---|---|
| 主題 1 |
|
| 主題 2 |
|
| 主題 3 |
|
| 主題 4 |
|
為了配合當前真正的考驗，從KaoGuTi Fortinet的NSE7_SOC_AR-7.6考試認證考試考古題的技術團隊的任何變化及時更新的問題和答案，我們也總是接受用戶回饋的問題，充分的利用了一些建議，從而達到完美的KaoGuTi Fortinet的NSE7_SOC_AR-7.6考試認證測試資料，使我們KaoGuTi始終擁有最高的品質。
問題 #78
Refer to the exhibit.
You created a threat hunting playbook to perform a search query using the FortiSIEM connector. However, when you run the playbook, you do not see any output. Which step must you take first in your troubleshooting process?
答案：C
解題說明：
Exact Extract: "Fortinet recommends that you test a search query first in FortiSIEM to ensure that there are matching event logs. Then you can implement the same logic and time range with the connector action." Exact Extract: "You can define a time range, such as the last 30 days, and the maximum number of records to return in your query." The correct answer is A . The exhibit shows the FortiSIEM connector action completed with status: Success , but the returned events array is empty and totalCount is 0 . That means the connector did not fail; the query simply did not return matching FortiSIEM event logs. The first troubleshooting step is to run the same search directly in FortiSIEM Analytics with the same filters and time range to confirm whether matching logs actually exist.
B is wrong because saving empty output into a variable does not solve the missing results. C is not first because the connector action already shows Success , so connectivity is not the immediate problem. D is useful when mapping fields or understanding schema, but the immediate evidence points to no matching data, not unknown output structure.
Technical Deep Dive: In FortiSOAR threat-hunting playbooks, connector success only proves the API call completed. It does not prove the search logic was correct. Check the FortiSIEM query directly for event type, attribute names, time range, organization scope, and maximum result count. In this case, events: [] and totalCount: 0 are the hard clues. This is FortiSOAR-to-FortiSIEM query troubleshooting; FortiGate NP/CP offloading is irrelevant because no firewall packet-processing path is involved.
問題 #79
Review the incident report:
An attacker identified employee names, roles, and email patterns from public press releases, which were then used to craft tailored emails.
The emails were directed to recipients to review an attached agenda using a link hosted off the corporate domain.
Which two MITRE ATT & CK tactics best fit this report? (Choose two answers)
答案：A,B
解題說明：
Based on the official documentation for FortiSIEM 7.3 (which utilizes the MITRE ATT & CK mapping for incident correlation) and FortiSOAR 7.6 (which uses these tactics for incident classification and playbook triggering):
* Reconnaissance (Tactic TA0043): This tactic consists of techniques that involve adversaries actively or passively gathering information that can be used to support targeting. In this scenario, the attacker identifies " employee names, roles, and email patterns from public press releases. " This is categorized under Gather Victim Org Information (T1591) and Search Open Technical Databases (T1596) .
Since this activity happens prior to the compromise and involves gathering intelligence, it is strictly Reconnaissance.
* Initial Access (Tactic TA0001): This tactic covers techniques that use various entry vectors to gain an initial foothold within a network. The act of sending " tailored emails... to recipients to review an attached agenda using a link " is the definition of Phishing: Spearphishing Link (T1566.002) . This is the specific delivery mechanism used to gain the initial entry.
Why other options are incorrect:
* Discovery (B): This tactic involves techniques an adversary uses to gain knowledge about the internal network after they have already gained access. Since the attacker is looking at public press releases, they are operating outside the perimeter.
* Defense Evasion (D): This tactic consists of techniques that adversaries use to avoid detection throughout their compromise. While using an external link might bypass some basic reputation filters, the primary goal described in the report is the act of establishing contact and access, which is the core of the Initial Access tactic.
問題 #80
You are trying to create a playbook that creates a manual task showing a list of public IPv6 addresses. You were successful in extracting all IP addresses from a previous action into a variable called ip_list , which contains both private and public IPv4 and IPv6 addresses. You must now filter the results to display only public IPv6 addresses. Which two Jinja expressions can accomplish this task? (Choose two answers)
答案：C,D
解題說明：
In FortiSOAR 7.6 , the playbook engine utilizes the powerful ipaddr family of Jinja filters (derived from the Ansible netaddr library) to manipulate network data. To isolate public IPv6 addresses from a mixed list, the order of operations in the filter chain ensures the correct data is extracted:
* Double Filtering Sequence (B): In the expression {{ vars.ip_list | ipaddr( ' public ' ) | ipv6 }}, the first filter ipaddr( ' public ' ) processes the entire list and retains only public addresses, including both IPv4 and IPv6 versions. The second filter in the pipe, | ipv6, then takes that subset of public addresses and filters them again to keep only those that conform to the IPv6 standard. The final result is a list containing only public IPv6 addresses.
* Version-First Filtering (D): In the expression {{ vars.ip_list | ipv6 | ipaddr( ' public ' ) }}, the logic is reversed but equally effective. The first filter | ipv6 immediately strips all IPv4 and non-IP strings from the list, leaving only IPv6 addresses (both private and public). The subsequent filter | ipaddr( ' public ' ) then evaluates these IPv6 addresses and discards any that fall within the private/unique-local ranges (like ULA or link-local), resulting in the same set of public IPv6 addresses.
Why other options are incorrect:
* A (ipv6addr ' public ' ): While ipv6addr is a valid filter in many Ansible environments, FortiSOAR ' s standard documentation for manual task creation and data manipulation primarily emphasizes the use of the generic ipaddr filter with specific flags or chained version filters (like | ipv6) to ensure cross- compatibility with the underlying Python libraries used by the SOAR engine.
* C (!private syntax): The ipaddr filter utilizes specific keywords for classification. While " not private " is the logical requirement, the filter expects positive assertions such as ' public ' , ' private ' , or ' multicast ' . The !private syntax is not a supported or documented operator for this filter within the Fortinet SOC ecosystem.
問題 #81
When configuring an Ingest Bulk Feed playbook step, which two restrictions must you consider? Choose two answers.
答案：A,B
解題說明：
Exact Extract: "Ingest Bulk Feed: Insert and update large volumes of records. Significantly faster than Create Record, but does not trigger On Create and On Update triggers. Only primary fields, tags, lookups, and picklists are supported." The correct answers are C and D . The Ingest Bulk Feed step is designed for high-volume ingestion, such as threat intelligence feeds, vulnerabilities, or asset imports. Its tradeoff is that it bypasses normal record-trigger behavior. Therefore, records inserted or updated through this step will not trigger playbooks configured with On Create or On Update triggers. That is a major design restriction because downstream automation that depends on those triggers will not run automatically.
A is wrong because the step can be driven by data prepared earlier in the playbook, including connector output transformed into the expected structure. B is the opposite of the guide: Ingest Bulk Feed is significantly faster than Create Record.
Technical Deep Dive: Use Create Record when you need full model behavior, uniqueness handling, trigger execution, and precise per-record workflow control. Use Ingest Bulk Feed when volume and speed matter more than trigger execution. A common mistake is bulk-ingesting indicators or assets and expecting On Create playbooks to fire for enrichment. They will not. You must either enrich before ingestion or run a separate scheduled/manual playbook afterward. NP/CP offloading is irrelevant; this is FortiSOAR database/workflow behavior.
問題 #82
You want to trigger an incident when multiple failed logins from the same host are followed by a successful login on that same host within 15 minutes. The rule must correlate all events by source IP address and user to ensure they belong to the same login sequence. Which three configurations achieve this goal? Choose three answers.
答案：A,C,D
解題說明：
Exact Extract: "If there is more than one subpattern, you must specify the logic between the subpatterns and define the subpattern relationship and constraints." Exact Extract: "FortiSIEM also supports rules with multiple subpatterns... Subpattern X was FOLLOWED BY subpattern Y within the time window." Exact Extract: "This slide shows a multiple subpattern rule. The rule contains two subpatterns... with a FOLLOWED_BY operator... To ensure FortiSIEM is correlating the proper logs... [matching fields] must match. This is the relationship, also called a constraint, between the two subpatterns." The correct answers are C, D, and E. You need two subpatterns because the detection contains two different event patterns: repeated failed logins and a later successful login. You then need FOLLOWED_BY because the successful login must occur after the failed-login sequence, not merely within the same time range.
Finally, you must define subpattern relationships and constraints, matching source IP address and user, so FortiSIEM does not correlate failed logins from one user or host with a successful login from a different user or host. A is wrong because failed-login and successful-login subpatterns normally require different filters and often different aggregate thresholds. B is not the best answer as written because the key requirement is the rule
/subpattern relationship within the 15-minute correlation window, not simply assigning independent time windows to each subpattern.
Technical Deep Dive: The clean FortiSIEM logic is: failed-login subpattern with an aggregate such as COUNT(Matched Events) > = N, success-login subpattern with COUNT(Matched Events) > = 1, a FOLLOWED_BY operator, and constraints like FailedLogin Source IP = SuccessLogin Source IP and FailedLogin User = SuccessLogin User. The time window should represent 15 minutes, usually 900 seconds.
This is correlation-engine behavior; FortiGate NP/CP hardware offload has no role because FortiSIEM is analyzing normalized log events, not accelerating packet forwarding.
問題 #83
......
KaoGuTi為你提供了一個明確而優秀的選擇，為你減少煩惱。想早點成功嗎？早點拿到Fortinet NSE7_SOC_AR-7.6認證考試的證書嗎？快點將KaoGuTi加入購物車吧。KaoGuTi會給你很好的指導，能確保你通過考試。使用KaoGuTi你可以很快獲得你想要的證書。
NSE7_SOC_AR-7.6考試指南: https://www.kaoguti.com/NSE7_SOC_AR-7.6_exam-pdf.html
從Google Drive中免費下載最新的KaoGuTi NSE7_SOC_AR-7.6 PDF版考試題庫：https://drive.google.com/open?id=1DCzjTr7vlyD2RgeuuA_4Zv1knc9wDXmz