Refer to the exhibits. The FortiMail Sender Blocklist playbook is configured to take manual input and add those entries to the FortiMail abc. com domain-level block list. The playbook is configured…

Question

Exhibit

Options

• AYou must use the GET_EMAIL_STATISTICS action first to gather information about email
• BFortiMail is expecting a fully qualified domain name (FQDN).
• CThe client-side browser does not trust the FortiAnalzyer self-signed certificate.
• DThe connector credentials are incorrect

• A
  12% (4)
• B
  3% (1)
• C
  9% (3)
• D
  76% (26)

Explanation

From the exhibits: - The FortiMail Sender Blocklist playbook is configured correctly in structure. - It uses the ADD_SENDER_TO_BLOCKLIST action from a FortiMail connector, which is - However, the playbook execution is failing. In FortiSOAR/FortiAnalyzer automation, if a playbook that uses a connector action (like modifying FortiMail configurations) fails at runtime, one of the most common causes is invalid or missing connector credentials. The FortiMail connector requires valid credentials (typically API user and password or token) to authenticate and perform actions like modifying the block list. If those credentials are incorrect, expired, or missing, the connector action will fail. The exhibit does not show successful test or validation of the connector, which suggests that credentials may not be set up properly.

No community discussion yet for this question.