Check Real Fortinet NSE6_EDR_AD-7.0 Exam Question for Free (2026) [Q19-Q44]

Share

Check Real Fortinet NSE6_EDR_AD-7.0 Exam Question for Free (2026)

Get Ready to Boost your Prepare for your NSE6_EDR_AD-7.0 Exam with 35 Questions

NEW QUESTION # 19
Refer to the exhibits.

You are attempting to move a collector into the High Security Collector Group for isolation but encounter an error in the API request as shown in the exhibit. To successfully isolate the collector, which API parameter must you correct? (Choose one answer)

  • A. Set the organization parameter to Default.
  • B. Change the HTTP method in the request from PUT to POST.
  • C. Update the authorization credentials in the API header.
  • D. Set the target collector group parameter to Engineering group.

Answer: A

Explanation:
The correct answer is A. Set the organization parameter to Default .
From the first exhibit, the API query result for the Collector shows:
* Collector name: Desktop-PC
* Collector group name: Engineering
* Organization: Default
* State: Running
But in the second exhibit, the API request is using:
* organization = Fortinet-Training
* collectors = Desktop-PC
* targetCollectorGroup = High Security Collector Group
That organization value is wrong. The Collector belongs to the Default organization, so the API request must reference the Collector's actual organization. Otherwise FortiEDR cannot locate or move that Collector under the organization specified in the request.
The FortiEDR guide confirms that Collector Groups are used to assign different FortiEDR policies to different Collectors, and that Collectors can be moved between groups/organizations in the Inventory workflow. In Hoster view, FortiEDR shows Collectors from all organizations and allows moving Collectors between organizations, but the organization context must match the Collector being managed.
Option B is wrong because the exhibit shows the API request is authorized; the failure is a 400 Bad Request , not an authentication failure. Option C is wrong because the endpoint shown is already a move/update operation using PUT, and the issue is not the HTTP method. Option D is wrong because Engineering is the current Collector Group. The goal is to move the Collector to High Security Collector Group , so changing the target back to Engineering would not isolate or harden the Collector.
=========


NEW QUESTION # 20
Refer to the Exhibit:

Based on the investigation view shown in the exhibit, which two statements about this event are true? (Choose two answers)

  • A. An exception was created for this incident.
  • B. The device has been isolated.
  • C. The raw data is displayed in the stacks view.
  • D. The exfiltration prevention policy blocked this event.

Answer: A,C

Explanation:
The correct answers are A and C .
The exhibit shows a green checkmark in the Exception column for the filezilla.exe event. In FortiEDR, an exception means a whitelist has been created for a specific flow/security-event pattern. The guide states that exceptions limit enforcement of a rule and that after an exception is defined, identical new events are no longer triggered. It also explains that past security events display an icon indicating that an exception has been defined for them.
The exhibit also shows the event flow ending in filezilla.exe with a red highlighted activity and a blocked symbol. In the Incidents/Investigation workflow, FortiEDR represents blocked policy violations as security events, and the guide explains that FortiEDR can enforce policy by blocking malicious connection establishment requests to prevent exfiltration. It also states that Block means the malicious exfiltration or file- changing attempt was blocked.


NEW QUESTION # 21
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. Export and review the collector logs from the Central Manager for connection errors.
  • 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. Verify that TCP ports 8081 and 555 are open between the collector and the central manager.

Answer: C,D

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 # 22
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 sends OS metadata to the FortiEDR manager.
  • C. FCS correlates and analyzes the collected logs.
  • D. FCS identifies if a malicious event has taken place and reports the detection incident.

Answer: C,D

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 # 23
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. A partial exception is applied to this event.
  • C. The exception is applied only on device C8092231196.
  • D. FCS playbooks are enabled by Fortinet support.

Answer: A,D

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 # 24
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 is allowed in all communication control policies.
  • B. The application is ignored because its reputation score is acceptable to the security policy.
  • C. The application has not made any connection attempts.
  • D. The application is blocked by the security policies.

Answer: A,C

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 # 25
Refer to Exhibit.

Based on the Postman output shown in the exhibit, why is the user receiving an unauthorized error? (Choose one answer)

  • A. FortiEDR requires a password reset the first time a user logs in.
  • B. The user account does not have the REST API role assigned.
  • C. The central manager is rejecting the request because of an unsupported HTTP method.
  • D. API access is disabled on the central manager.

Answer: B

Explanation:
The correct answer is C. The user account does not have the REST API role assigned .
The exhibit shows a Postman request to the FortiEDR Central Manager REST endpoint:
/management-rest/inventory/list-collectors
The response is 401 Unauthorized , which means the request reached the FortiEDR API endpoint but the supplied user credentials are not authorized for REST API access.
The FortiEDR 7.0.0 Administration Guide states that when adding or editing a user, the Rest API advanced option controls whether the user is allowed to access the FortiEDR Central Manager through API calls. The guide defines this option as: "Rest API - Specifies whether to allow the user to access the FortiEDR Central Manager through API calls." Therefore, the most accurate cause is that the account being used in Postman does not have the Rest API permission enabled.
Option A is incorrect because the request uses GET against a list endpoint, and an unsupported method would not normally be represented by this user-authentication failure. Option B is not supported by the exhibit or guide wording; the guide describes enabling REST API access per user. Option D is incorrect because first- login password reset is not the direct cause of this REST API authorization failure. The guide separately discusses password reset and password policy behavior, but that is not what the API error indicates.


NEW QUESTION # 26
What specific action does FortiEDR take when the Zero Trust Device Tagging playbook is activated?
(Choose one answer)

  • A. It updates FortiClient EMS through an API and assigns a classification fabric tag.
  • B. It assigns a default tag to all endpoints.
  • C. It removes unmanaged endpoints from FortiClient EMS.
  • D. It disables the endpoint until a tag is assigned.

Answer: A


NEW QUESTION # 27
Refer to the Exhibit:

Based on the incident details shown in the exhibit, which two statements about this incident are true? (Choose two answers)

  • A. The incident has already been fully handled.
  • B. The incident occurred on only one device.
  • C. The incident is classified by the FortiEDR Core.
  • D. The destination IP address is blocked by FortiGate.

Answer: C,D

Explanation:
The correct answers are A and C .
The exhibit shows an audit/response action stating that IP address 74.125.235.20 was added to malicious IP addresses on firewall FortiGate . This matches the FortiEDR playbook action Block address on Firewall .
The guide states that this action ensures connections to remote malicious addresses associated with the security event are blocked, and that a firewall connector must already be configured for this action. It also explains that a checkmark in a classification column means communication with the affected destination is automatically blocked when a security event with that classification is triggered.
Option C is the second best answer because FortiEDR events are initially classified by FortiEDR detection logic/Core, and the guide states that classifications are initially determined by the Core but can later be changed automatically by FortiEDR Cloud Service or manually. The exhibit shows "Classification Changed To: Suspicious (By Fortinet)" , but it does not say the event was manually classified by an administrator. So the event classification process is FortiEDR-driven, with later Fortinet/FCS-style automatic classification possible.
Option B is wrong. The exhibit shows one raw-data row with device cwinserv-32 +2 , which indicates more than one affected device/raw item is represented in the aggregation. So it did not occur on only one device.
Option D is wrong because the incident rows clearly show Unhandled . The guide states that security events are initially marked as unread and unhandled, and the unread/unhandled status helps users track whether anyone has read and handled the event.
=========


NEW QUESTION # 28
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 delegate it to other organizations.
  • B. Create a separate communication control policy for each organization.
  • C. Create a new communication control policy and apply it to multiple organizations.
  • D. Create a new communication control policy and assign it globally to all organizations.

Answer: B


NEW QUESTION # 29
Which two Python commands are supported when using FortiEDR Connect to directly access a protected device shell? (Choose two answers)

  • A. %psexec
  • B. %upload_file
  • C. %ipconfig_all
  • D. %timestamp

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 # 30
Refer to the exhibits.

What happens when the net user command runs on an endpoint? (Choose one answer)

  • A. It triggers an incident when the query matches the target process (net.exe).
  • B. It blocks CLI commands by default.
  • C. It triggers an immediate endpoint alert.
  • D. It triggers FortiEDR rules because the activity is not suspicious.

Answer: A

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 # 31
You are asked to configure a query to run every 15 minutes, automatically searching for specific registry modifications across all endpoints. Which FortiEDR feature must you configure? (Choose one answer)

  • A. A communication control rule with a 15-minute delay
  • B. A scheduled query defined within a threat hunting profile
  • C. A new playbook trigger based on the registry change event
  • D. A manual query linked to a policy override

Answer: B

Explanation:
The correct answer is C.
The FortiEDR guide explains that Threat Hunting searches across endpoint activity events, including registry activity. It states that Threat Hunting can search based on attributes of files, registry keys and values, network, processes, event log, and activity event types. This fits the requirement to search for specific registry modifications across endpoints.
The guide also explains that after filtering activity events, the query can be saved and defined as a Scheduled Query. It says: "Scheduled Query: Mark this option to automate the process of detecting threats so that this query is run automatically according to the schedule that you define." It also states that a security event is automatically created in the Incidents tab when matches are detected, and notifications can be sent through email, Syslog, and other configured methods.
The guide further states that the Repeat Every/On options define the frequency and schedule when the query runs. Therefore, a 15-minute recurring query is handled through the Scheduled Query capability in Threat Hunting, not Communication Control, policy override, or a manual Playbook trigger.
Strictly speaking, the guide calls this a scheduled query under Threat Hunting saved queries, not a
"communication control rule" or "manual query." Option C is the intended answer.
=========


NEW QUESTION # 32
Refer to the exhibit.

Based on the threat hunting event details shown in the exhibit, which two statements about the event are true?
(Choose two answers)

  • A. The PING.EXE process was blocked.
  • B. The user fortinet has executed a ping command.
  • C. There are no MITRE details available for this event.
  • D. The activity event is associated with the file action.

Answer: B,D

Explanation:
The correct answers are B and D .
The exhibit shows a Process Creation activity event where cmd.exe is the source process and PING.EXE is the target process. The displayed Executing user is R2D2-KVM63\fortinet, and the command line shows fortinet.com, which means the user fortinet executed a ping command targeting fortinet.com.
The FortiEDR guide explains that Threat Hunting activity events consist of a source , an action , and a target
. It also states that Process Actions have another process as the target and include process-related actions such as Process Creation .
The exhibit also shows file-related details for the executable, including the executable path, product, SHA1 hash, and command line. In FortiEDR Threat Hunting, process execution events are tied to executable-file metadata, so the event is associated with the executable file involved in the process action. This supports B in the exam's intended wording.
Option A is not reliable because the screenshot does not prove MITRE details are unavailable; it only shows that no MITRE detail is visible in the current portion of the details pane. The guide states that MITRE indications appear when an activity event has related MITRE information.
Option C is wrong because the screenshot shows the process status as Running and does not show a block indicator. A green check does not mean blocked; it indicates a trusted/signed/allowed status context. There is no evidence that PING.EXE was blocked.


NEW QUESTION # 33
......

Use Free NSE6_EDR_AD-7.0 Exam Questions that Stimulates Actual EXAM : https://braindumps.getvalidtest.com/NSE6_EDR_AD-7.0-brain-dumps.html