Fortinet Certified Solution Specialist: Security Operations 7.6 Architect & Analyst Practice Mode

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose B0

  - Understanding the Playbook Configuration: The playbook "FortiMail Sender Blocklist" is designed to manually input email addresses or IP addresses and add them to the FortiMail block list. The playbook uses a FortiMail connector with the action ADD_SENDER_TO_BLOCKLIST. Analyzing the Playbook Execution: The configuration and actions provided show that the playbook is straightforward, starting with an ON_DEMAND STARTER and proceeding to the ADD_SENDER_TO_BLOCKLIST action. The action description indicates it is intended to block senders based on email addresses or domains. Evaluating the Options: Option A: Using GET_EMAIL_STATISTICS is not required for the task of adding senders to a block list. This action retrieves email statistics and is unrelated to the block list configuration. Option B: The primary reason for failure could be the requirement for a fully qualified domain name (FQDN). FortiMail typically expects precise information to ensure the correct entries are added to the block list. Option C: The trust level of the client-side browser with FortiAnalyzer's self-signed certificate does not impact the execution of the playbook on FortiMail. Option D: Incorrect connector credentials would result in an authentication error, but the problem described is more likely related to the format of the input data. Conclusion: The FortiMail Sender Blocklist playbook execution is failing because FortiMail is expecting a fully qualified domain name (FQDN). Reference: Fortinet Documentation on FortiMail Connector Actions. Best Practices for Configuring FortiMail Block Lists.