Get 2026 Most Reliable Fortinet NSE6_EDR_AD-7.0 Training Materials
The Realest Study Materials NSE6_EDR_AD-7.0 Dumps
NEW QUESTION # 21
Refer to the exhibit.
Based on the event shown in the exhibit, which two statements about the event are true? (Choose two answers)
- A. The event is marked as Handled.
- B. FCS classified the event as malicious.
- C. TestApplication.exe is sophisticated malware.
- D. The user was able to launch TestApplication.exe.
Answer: B,D
Explanation:
The correct answers are B and C .
The exhibit shows the event classification as Malicious . In FortiEDR, event classification can be performed by the Core and later updated by FortiEDR Cloud Service (FCS) . The guide states that the audit history shows the classification chronology and includes details when FCS reclassifies a security event after the Core' s initial classification. It also states that notifications can be based on either Core or FCS classification depending on whether FCS classification is received within the timeout period.
The exhibit also shows TestApplication.exe with Status: Running . That means the process was launched and is currently running on the endpoint. Therefore, C is correct.
Option A is wrong because the exhibit clearly shows Status: Unhandled , not Handled. The guide states that FortiEDR security events are initially marked as unread and unhandled, and users can later mark them handled through the incident handling workflow.
Option D is wrong because the exhibit shows rule indicators such as Invalid Checksum , Suspicious Packer
, and Writable Code , but it does not prove that TestApplication.exe is "sophisticated malware." FortiEDR classifies the event as malicious, but the guide's Malicious classification means the event is verified to have malicious capability, is intended to harm the infected device, and has no commercially viable use; the exhibit alone does not justify the stronger claim "sophisticated malware."
=========
NEW QUESTION # 22
Which two Python commands are supported when using FortiEDR Connect to directly access a protected device shell? (Choose two answers)
- A. %timestamp
- B. %ipconfig_all
- C. %upload_file
- D. %psexec
Answer: B,C
Explanation:
The correct answers are A. %upload_file and B. %ipconfig_all .
The FortiEDR 7.0.0 Administration Guide states that FortiEDR Connect opens a console that provides direct access to a FortiEDR-protected device through a remote shell connection. This allows administrators to respond to incidents, run commands and scripts, collect and download forensic data, and remediate threats.
The guide also states that the FortiEDR Connect terminal has a prompt where commands can be typed, and the Help button displays the supported commands and their parameters.
The guide further confirms that FortiEDR Connect supports FortiEDR-specific commands, Windows command-line access through %cmd , and Python commands.
For the exact command list, Fortinet's official FortiEDR Connect technical tip lists the supported commands.
In that list, %ipconfig_all is explicitly described as returning extended IP information, and %upload_file is explicitly described as uploading a file to the specified path. ( Fortinet Community ) Options C. %psexec and D. %timestamp are not listed as supported FortiEDR Connect commands in the official Fortinet command list. Therefore, they must not be selected.
=========
=========
NEW QUESTION # 23
Refer to the exhibit.
Based on the exhibit, which two observations are true? (Choose two answers)
- A. FCS has classified this as malicious.
- B. EDR has never encountered this malware before.
- C. This incident has been resolved.
- D. FortiEDR has classified this as suspicious.
Answer: A,B
Explanation:
The correct answers are C and D .
The exhibit shows the incident classification as Malicious . In the Activity Audit, the entry from FortinetCloudServices states: "Classification change: Malicious" and also says the file is classified as malicious. This directly proves that FCS classified the event as malicious . The FortiEDR guide explains that the audit history shows the chronology for classifying the security event and displays details when FortiEDR Cloud Service (FCS) reclassifies a security event after its initial classification by the Core.
The exhibit also states that the file was "Detected as Unknown malware." This supports option D in the exam wording: FortiEDR/FCS has classified the file as malicious, but it is being identified as unknown malware , meaning it was not recognized as a known malware family/signature at the time of classification.
The guide explains that FCS enhances classification using data enrichment, automated and manual analysis, file analysis, sandboxing, machine learning flow analysis, commonality analysis, crowdsourced data deduction, and other methods, so "unknown malware" can still be classified malicious by FCS.
Option A is wrong because the exhibit shows Malicious , not Suspicious. Option B is wrong because the incident status is Unhandled , not resolved or handled.
=========
NEW QUESTION # 24
Refer to the Exhibit:
A FortiEDR analyst is prioritizing response efforts. One application has a vulnerability score of Critical but an Unknown ACI rating, while another has a Medium vulnerability score with active ACI evidence of adversary targeting. Which application must be addressed first? (Choose one answer)
- A. The decision depends only on asset criticality, not scores.
- B. Both applications should be treated equally because patching is necessary.
- C. The application with the Critical vulnerability score should be addressed first.
- D. The application with the Medium vulnerability score and ACI evidence should be addressed first.
Answer: D
Explanation:
The correct answer is D .
The FortiEDR 7.0.0 Administration Guide explains that FortiEDR displays two severity ratings for applications: NIST Severity and ACI Severity . NIST Severity is based on FortiEDR's vulnerability scoring system using the NIST Cybersecurity Framework. ACI Severity, however, is Adversary Centric Intelligence provided by FortiRecon and FortiGuard Threat Analysts, covering dark web, open-source, and technical threat intelligence, including threat actor insights . This helps administrators proactively assess risk, respond faster to incidents, understand attackers, and protect assets.
The guide also states that FortiEDR helps analysts prioritize alerts and incidents using risk factors such as severity of vulnerabilities , relevance of threat intelligence feeds , and severity of affected endpoints , so effort is focused on the most significant organizational risks.
Therefore, the application with Medium NIST severity but active ACI evidence of adversary targeting should be prioritized over an application with Critical NIST severity but Unknown ACI rating , because active adversary-centric intelligence indicates current attacker interest or exploitation relevance. In plain terms: a theoretical critical vulnerability matters, but an actively targeted vulnerability is the fire you put out first.
Option B is tempting but incomplete because it relies only on NIST/CVSS severity. FortiEDR's ACI rating exists specifically to add adversary context to prioritization. Option A is wrong because FortiEDR does not treat all vulnerable applications equally. Option C is wrong because asset criticality can matter, but the guide does not say prioritization depends only on asset criticality.
=========
NEW QUESTION # 25
A company requires a global communication policy for a FortiEDR multi-tenant environment. Which recommendation must you make? (Choose one answer)
- A. Create a new communication control policy and apply it to multiple organizations.
- B. Create a new communication control policy and assign it globally to all organizations.
- C. Create a separate communication control policy for each organization.
- D. Create a new communication control policy and delegate it to other organizations.
Answer: C
NEW QUESTION # 26
Within the FortiEDR architecture, which component needs JumpBox capabilities to enable authenticated and controlled communication with FortiAnalyzer? (Choose one answer)
- A. Reputation Server
- B. Aggregator
- C. Core
- D. Central manager
Answer: C
Explanation:
The correct answer is A. Core.
For FortiAnalyzer / FortiAnalyzer Cloud integration, the FortiEDR 7.0.0 Administration Guide states that one prerequisite is "A Jumpbox with connectivity to FortiAnalyzer." The same section says to refer to Setting up the FortiEDR Core for details about installing a FortiEDR Core and configuring it as a Jumpbox. In the connector configuration, the guide also states that the Jumpbox field is used to select the FortiEDR Jumpbox that will communicate with FortiAnalyzer or FortiAnalyzer Cloud.
So, the FortiEDR component associated with JumpBox capability is the Core. The Central Manager must have connectivity to Fortinet Cloud Services, but it is not the component configured as the JumpBox. The Aggregator handles registration, configuration, and monitoring between Collectors/Cores and Central Manager, and the Reputation Server is unrelated to FortiAnalyzer JumpBox communication in this context.
=========
NEW QUESTION # 27
Refer to the exhibit.
What observation can you make about the ConnectivityTestAppNew.exe incident? (Choose one answer)
- A. The incident was archived from the console unhandled.
- B. A rule assigned action is set to block but the policy is in simulation mode.
- C. The incident was handled automatically by the communication control policy.
- D. The incident has not been handled by a console administrator.
Answer: D
Explanation:
The correct answer is B .
In the exhibit, the incident status clearly shows Unhandled at the incident level and also on the event rows.
The FortiEDR guide explains that every detected security event is initially marked as unread and unhandled
, and these statuses help multiple FortiEDR Central Manager users track whether anyone has read and handled the message.
The guide also states that when a FortiEDR Central Manager user marks a security event as Handled , all users see it as handled. The process is performed by selecting the event and clicking Handle Incident or the flag icon, then saving the incident handling details.
So the valid observation from the exhibit is that the incident has not been handled by a console administrator .
Option A is not supported by the exhibit. There is no visible evidence that the policy is in Simulation mode.
Option C is wrong because the incident is still visible, not archived or deleted. Option D is wrong because the status is explicitly Unhandled ; it was not handled automatically by a Communication Control policy.
=========
NEW QUESTION # 28
You find third-party software on a user's computer that does not appear in the application list on the communication control console. Which two statements are true about this situation? (Choose two answers)
- A. The application has not made any connection attempts.
- B. The application is allowed in all communication control policies.
- C. The application is ignored because its reputation score is acceptable to the security policy.
- D. The application is blocked by the security policies.
Answer: A,B
Explanation:
The best answers are A and D , but be careful: A is directly verified by the guide; D is the only remaining statement that can be true in policy context, but it is weaker than A.
The FortiEDR 7.0.0 Administration Guide states that the Communication Control tab identifies communicating applications detected in the organization. More specifically, the Applications page lists "all communicating applications detected in your organization that have ever attempted to communicate." Therefore, if software exists on a user's computer but does not appear in the Communication Control application list, the most direct explanation is that it has not attempted external communication .
The guide also explains that FortiEDR Communication Control reduces the scope of administration because Security/IT only needs to handle applications that communicate externally. It also states that non-authorized applications can still execute, and only their outgoing communication is prevented. This confirms that the Communication Control application list is not a full software inventory; it is a list of applications that have communicated or attempted communication.
Option B is not correct. If an application were blocked due to FortiEDR security-policy enforcement after a connection attempt, FortiEDR would generate security-event visibility in the Incidents workflow, not simply hide the application from Communication Control. FortiEDR Collectors send communication-related data for Communication Control, and security events are sent for enforcement/monitoring purposes.
Option C is also wrong. Reputation score affects policy decisions and application risk evaluation, but it does not cause an application to be ignored or excluded from the application list. The guide says each application in the Applications page shows a reputation indicator, which proves reputation is displayed for listed applications rather than used to hide them.
For option D , if the application has never attempted communication, Communication Control has no observed communication event to list. In exam logic, this can be interpreted as the application is not currently being denied by Communication Control policies. However, the stronger technical truth is this:
Communication Control does not list installed software; it lists applications that have attempted to communicate.
=========
NEW QUESTION # 29
Which two statements correctly describe the IoT probing process on FortiEDR? (Choose two answers)
- A. Only healthy collectors participate in IoT probing.
- B. Collectors running on servers are always used for IoT probing.
- C. It captures all traffic from neighboring devices for deep packet inspection.
- D. It identifies nearby devices by retrieving details such as hostname and IP address.
Answer: A,D
Explanation:
The correct answers are B and C .
The FortiEDR 7.0.0 Administration Guide explains that IoT device discovery continuously identifies newly connected non-workstation devices, such as printers, cameras, and media devices. During discovery, each relevant Collector periodically probes nearby neighboring devices. The guide states that nearby devices usually respond by providing information about themselves, including the device/host name and IP address .
This directly supports option B .
Option C is also correct because the guide states that Collectors in degraded , disabled , or isolated states do not take part in the IoT probing process. It also says FortiEDR uses the most powerful Collectors in each subnet and excludes weaker Collectors, including disabled and degraded Collectors.
Option A is wrong because the guide explicitly says Collectors running on servers do not take part in IoT probing. Option D is wrong because IoT probing is not described as deep packet inspection of all neighboring traffic; it is a discovery/probing process used to identify nearby devices and collect basic device information.
=========
NEW QUESTION # 30
Refer to the exhibit.
An event exception is shown. Which two statements about the exception are true? (Choose two answers)
- A. The system owner can modify the trigger rules parameters.
- B. FCS playbooks are enabled by Fortinet support.
- C. A partial exception is applied to this event.
- D. The exception is applied only on device C8092231196.
Answer: A,B
Explanation:
The correct answers are C and D .
The exhibit shows an exception created/updated by FortinetCloudServices after the file Update.exe was classified as Good . This aligns with the FortiEDR Cloud Service behavior described in the guide. The guide states that once FCS is connected, it can enable Tuning , which means automated security event exception
/allowlisting. After a triggered security event is reclassified as Safe, an automated cross-environment exception can be pushed downstream and the event expires, preventing it from triggering again.
Option C is correct because the Event Exceptions window includes Triggered Rules , and the guide states that when editing an exception, the administrator can modify the Collector Groups , Destinations , Users , and the pairs of rules and processes that define the exception in the Triggered Rules area.
Option D is the Fortinet/FCS-related statement supported by the guide's FCS behavior. The guide says FCS can enable follow-up actions, including Tuning through automated exceptions and Playbook Actions , and that playbook policy remediation actions are based on the final FCS determination.
Option A is wrong because the exhibit explicitly states "All the Raw Data Items are covered." A partial exception would mean not all raw data items are covered. The guide explains that if an exception does not cover all raw data items, FortiEDR displays a different indicator and distinguishes covered from non-covered raw data items.
Option B is wrong because the exception scope in the exhibit is set to All groups , All destinations , and All users . The comment references device C8092231196, but that is not the same as saying the exception applies only to that device.
=========
NEW QUESTION # 31
You discovered that a newly installed collector does not display on the Inventory tab in the central manager.
Which two troubleshooting steps must you perform? (Choose two answers)
- A. Verify that TCP ports 8081 and 555 are open between the collector and the central manager.
- B. Verify that the central manager can resolve the collector hostname through DNS.
- C. Check whether the FortiEDR services are running on the collector device.
- D. Export and review the collector logs from the Central Manager for connection errors.
Answer: A,C
Explanation:
The correct answers are B and C .
The FortiEDR 7.0.0 Administration Guide has a specific troubleshooting section named "A FortiEDR Collector does not display in the INVENTORY tab." It states that after a Collector is first launched, it registers with the FortiEDR Central Manager and appears in the Inventory tab. If it does not appear, the first checks are to confirm that the device where the Collector is installed is powered on and has Internet connectivity, and to validate that ports 8081 and 555 are available and not blocked by another third-party product.
Option B is therefore correct in the exam sense because ports 8081 and 555 must be open for FortiEDR communication. More precisely, the Collector communicates with the Aggregator on port 8081 and the Core on port 555 , not directly to the Central Manager in every architecture. The option wording says "between the collector and the central manager," which is technically loose, but the required troubleshooting item is still the port availability.
Option C is also correct because the same guide says to check that the endpoint is powered on and connected.
In practical FortiEDR troubleshooting, this includes confirming the FortiEDR Collector service/driver are running on the endpoint; otherwise the Collector cannot register or report health.
Option A is not listed in the FortiEDR guide as a required step for this issue. Option D is not the best answer because the guide says logs are generally retrieved when Fortinet Support requests them, and Collector logs can only be exported for Collectors in Running status; a newly installed Collector that does not appear in Inventory cannot normally be selected from Central Manager for log export.
NEW QUESTION # 32
A collector attempts to access a known malicious website. FortiEDR is configured for eXtended detection with FortiAnalyzer. What two roles does Fortinet Cloud Services (FCS) perform in this process? (Choose two answers)
- A. FCS sends a log record to FortiAnalyzer.
- B. FCS identifies if a malicious event has taken place and reports the detection incident.
- C. FCS correlates and analyzes the collected logs.
- D. FCS sends OS metadata to the FortiEDR manager.
Answer: B,C
Explanation:
The correct answers are C and D .
The guide states that for eXtended Detection Source integration, FortiEDR connects to external systems to collect activity logs. The aggregated data is then sent to Fortinet Cloud Services (FCS) , where it is correlated and analyzed to detect malicious indications. Those malicious indications result in security events for eXtended Detection policy rule violations .
For FortiAnalyzer/FortiAnalyzer Cloud specifically, the guide states that this integration is used to correlate data between FortiEDR and the Fortinet Security Fabric and issue eXtended Detection alerts .
Option A is wrong because FCS does not send the original log record to FortiAnalyzer. FortiAnalyzer is the external source whose data is correlated with FortiEDR data. Option B is wrong because OS metadata is collected by the Collector and handled through FortiEDR components; the FCS role here is cloud-side enrichment, correlation, and detection, not sending OS metadata back to the manager.
=========
NEW QUESTION # 33
Refer to the exhibits.
What happens when the net user command runs on an endpoint? (Choose one answer)
- A. It triggers FortiEDR rules because the activity is not suspicious.
- B. It triggers an incident when the query matches the target process (net.exe).
- C. It blocks CLI commands by default.
- D. It triggers an immediate endpoint alert.
Answer: B
Explanation:
The correct answer is C .
The exhibit shows a Threat Hunting saved query named CLI Command with the query:
Target.Process.Filename ( " net.exe " )
It is configured as a Scheduled Query , classified as Suspicious , and set to repeat every 15 minutes . The FortiEDR guide states that saving a Threat Hunting query allows it to be defined as a scheduled query to automate threat detection. When the scheduled query runs and detects matching activity, a security event is automatically created in the Incidents tab .
The guide also states that scheduled queries run automatically according to the configured schedule, and each time a match is detected, FortiEDR generates a security event in the Incidents tab and sends notifications according to the security event configuration.
So, when the endpoint runs:
net user edruser password! /ADD
FortiEDR records the relevant process activity, and when the scheduled query runs, it matches the target process net.exe and creates an incident/security event. It is not immediate by default because the query is scheduled every 15 minutes. It also does not block CLI commands by default unless playbook actions or policy controls are configured. The activity is treated according to the saved query classification, which in the exhibit is Suspicious .
=========
NEW QUESTION # 34
Refer to the exhibits.
The application policy logs and application details are shown. Collector C8092231196 is a member of the Finance group. In this scenario, what must you do to block the FileZilla application? (Choose one answer)
- A. Assign the Simulation Communication Control Policy to the DBA group.
- B. Assign the Finance policy to a broader collector group, such as the Default Collector Group.
- C. Assign the Finance policy to the DBA group.
- D. Deny the application in the Finance policy.
Answer: D
Explanation:
The correct answer is B. Deny the application in the Finance policy .
The FortiEDR 7.0.0 Administration Guide states that Communication Control policies define the actions to be taken for a given application or application version . It also states that each Communication Control policy applies to specific Collector Groups , and all devices that belong to those Collector Groups follow that policy. A Collector Group can be assigned to only one Communication Control policy.
In the exhibit, the Collector C8092231196 is stated to be a member of the Finance group. Therefore, to block FileZilla for that Collector, the application action must be set to Deny under the Finance policy , because that is the policy context that applies to the Collector's group.
The guide also explains that you can modify a policy action for an application/version so that the selected application is explicitly set to Allow or Deny for the relevant policy. When modified this way, the Application
/Version Details area shows the action as manually changed and excluded from the original policy action.
Option A is wrong because assigning a Simulation Communication Control Policy to the DBA group does not affect a Collector in the Finance group. Option C is wrong because assigning the Finance policy to the DBA group would affect DBA Collectors, not the Finance Collector in the scenario. Option D is wrong because assigning the Finance policy to a broader group such as Default Collector Group is unnecessary and could over-broaden the policy impact. The precise action is to deny FileZilla in the policy that applies to the Collector's own group: Finance policy .
=========
NEW QUESTION # 35
......
LATEST NSE6_EDR_AD-7.0 Exam Practice Material: https://measureup.preppdf.com/Fortinet/NSE6_EDR_AD-7.0-prepaway-exam-dumps.html