Free NSE8_812 Exam Braindumps
Fortinet NSE 8 Written Questions 41–45 (page: 10)

Updated On: 10-Feb-2026

A customer wants to use the FortiAuthenticator REST API to retrieve an SSO group called SalesGroup. The following API call is being made with the 'curl' utility:



Which two statements correctly describe the expected behavior of the FortiAuthenticator REST API? (Choose two.)

  1. Only users with the "Full permission" role can access the REST API
  2. This API call will fail because it requires that API version 2
  3. If the REST API web service access key is lost, it cannot be retrieved and must be changed.
  4. The syntax is incorrect because the API calls needs the get method.

Answer(s): B,D

Explanation:

To retrieve an SSO group called SalesGroup using the FortiAuthenticator REST API, the following issues need to be fixed in the API call:
The API version should be v2, not v1, as SSO groups are only supported in version 2 of the REST API. The HTTP method should be GET, not POST, as GET is used to retrieve information from the server, while POST is used to create or update information on the server. Therefore, a correct API call would look like this: curl -X GET -H "Authorization: Bearer <token>" https://fac.example.com/api/v2/sso/groups/SalesGroup


Reference:

https://docs.fortinet.com/document/fortiauthenticator/6.4.1/rest-api-solution- guide/927310/introduction https://docs.fortinet.com/document/fortiauthenticator/6.4.1/rest-api-

solution-guide/927311/sso-groups



Refer to the exhibit.



A customer has deployed a FortiGate 200F high-availability (HA) cluster that contains & TPM chip. The exhibit shows output from the FortiGate CLI session where the administrator enabled TPM. Following these actions, the administrator immediately notices that both FortiGate high availability (HA) status and FortiManager status for the FortiGate are negatively impacted.
What are the two reasons for this behavior? (Choose two.)

  1. The private-data-encryption key entered on the primary did not match the value that the TPM expected.
  2. Configuration for TPM is not synchronized between FortiGate HA cluster members.
  3. The FortiGate has not finished the auto-update process to synchronize the new configuration to FortiManager yet.
  4. TPM functionality is not yet compatible with FortiGate HA.
  5. The administrator needs to manually enter the hex private data encryption key in FortiManager.

Answer(s): B,E

Explanation:

https://docs.fortinet.com/document/fortimanager/7.4.2/administration-guide/30332/verifying- devices-with-private-data-encryption-enabled



Refer to the exhibits.



The exhibits show a FortiMail network topology, Inbound configuration settings, and a Dictionary Profile.
You are required to integrate a third-party's host service (srv.thirdparty.com) into the e-mail processing path.
All inbound e-mails must be processed by FortiMail antispam and antivirus with FortiSandbox integration. If the email is clean, FortiMail must forward it to the third-party service, which will send the email back to FortiMail for final delivery, FortiMail must not scan the e-mail again.
Which three configuration tasks must be performed to meet these requirements? (Choose three.)

  1. Change the scan order in FML-GW to antispam-sandbox-content.
  2. Apply the Catch-Ail profile to the CFInbound profile and configure a content action profile to deliver to the srv. thirdparty. com FQDN
  3. Create an access receive rule with a Sender value of srv. thirdparcy.com, Recipient value of *@acme.com, and action value of Safe
  4. Apply the Catch-AII profile to the ASinbound profile and configure an access delivery rule to deliver to the 100.64.0.72 host.
  5. Create an IP policy with a Source value of 100. 64 .0.72/32, enable precedence, and place the policy at the top of the list.

Answer(s): A,B,E

Explanation:

A is correct because the scan order must be changed to antispam-sandbox-content in order for FortiMail to scan the email for spam and viruses before forwarding it to the third-party service. B is correct because the Catch-All profile must be applied to the CFInbound profile in order for FortiMail to forward clean emails to the third-party service. E is correct because an IP policy must be created with a Source value of 100.64.0.72/32 in order to allow emails from the third-party service to be delivered to FortiMail. The other options are not necessary to meet the requirements. Option C is not necessary because the access receive rule will already allow emails from the third-party service to be received by FortiMail. Option D is not necessary because the Catch-All profile already allows emails to be delivered to any destination.
Here are some additional details about integrating a third-party service into the FortiMail email processing path:
The third-party service must be able to receive emails from FortiMail and send them back to FortiMail.
The third-party service must be able to communicate with FortiMail using the SMTP protocol. The third-party service must be able to authenticate with FortiMail using the SMTP AUTH protocol. Once the third-party service is integrated into the FortiMail email processing path, all inbound emails will be processed by FortiMail as usual. If the email is clean, FortiMail will forward it to the third- party service. The third-party service will then send the email back to FortiMail for final delivery.
FortiMail will not scan the email again.



Refer to the exhibit showing a FortiSOAR playbook.



You are investigating a suspicious e-mail alert on FortiSOAR, and after reviewing the executed playbook, you can see that it requires intervention.
What should be your next step?

  1. Go to the Incident Response tasks dashboard and run the pending actions
  2. Click on the notification icon on FortiSOAR GUI and run the pending input action
  3. Run the Mark Drive by Download playbook action
  4. Reply to the e-mail with the requested Playbook action

Answer(s): A

Explanation:

The exhibited playbook requires intervention, which means that the playbook has reached a point where it needs a human operator to take action. The next step should be to go to the Incident

Response tasks dashboard and run the pending actions. This will allow you to see the pending actions that need to be taken and to take those actions. The other options are not correct. Option B will only show you the notification icon, but it will not allow you to run the pending input action. Option C will run the Mark Drive by Download playbook action, but this is not the correct action to take in this case. Option D is not a valid option. Here are some additional details about pending actions in FortiSOAR:
Pending actions are actions that need to be taken by a human operator. Pending actions are displayed in the Incident Response tasks dashboard. Pending actions can be run by clicking on the action in the dashboard.



Review the following FortiGate-6000 configuration excerpt:



Based on the configuration, which statement is correct regarding SNAT source port partitioning behavior?

  1. It dynamically distributes SNAT source ports to operating FPCs or FPMs.
  2. It is the default SNAT configuration and preserves active sessions when an FPC or FPM goes down.
  3. It statically distributes SNAT source ports to operating FPCs or FPMs
  4. It equally distributes SNAT source ports across chassis slots.

Answer(s): C

Explanation:

https://docs.fortinet.com/document/fortigate/7.4.1/fortigate-6000-administration- guide/81276/controlling-snat-port-partitioning-behavior "chassis-slots this option statically allocates SNAT source ports to all FPCs that are enabled when you enter the command. If you disable an FPC from the CLI, the SNAT source ports assigned to that FPC will not be re-allocated to the remaining FPCs. All FPCs that are still operating will maintain the same SNAT source port allocation and active sessions being processed by the still operating FPCs will not be affected."



Viewing page 10 of 22
Viewing questions 46 - 50 out of 118 questions


Post your Comments and Discuss Fortinet NSE8_812 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!