{"id":23882,"date":"2026-09-28T10:54:42","date_gmt":"2026-09-28T10:54:42","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=23882"},"modified":"2026-09-28T10:54:42","modified_gmt":"2026-09-28T10:54:42","slug":"fortinet-fcp_fml_ad-7-4-practice-test-questions-and-exam-dumps-part19-q361-380","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/fortinet-fcp_fml_ad-7-4-practice-test-questions-and-exam-dumps-part19-q361-380\/","title":{"rendered":"Fortinet FCP_FML_AD-7.4 Practice Test Questions and Exam Dumps Part19 Q361-380"},"content":{"rendered":"

View Full <\/b>Fortinet FCP_FML_AD-7.4 Exam Dumps<\/b><\/a> and Practice Test Dumps.<\/b><\/p>\n


\n<\/b>Q361. What does DANE help FortiMail verify?<\/b><\/p>\n

    \n
  1. <\/b> Mailbox quota<\/span><\/li>\n
  2. <\/b> Archive retention<\/span><\/li>\n
  3. <\/b> TLS identity through DNS information<\/span><\/li>\n
  4. <\/b> Administrator password age<\/span><\/li>\n<\/ol>\n

    Correct Answer: 3. TLS identity through DNS information<\/b><\/p>\n

    Explanation<\/b><\/p>\n

    DANE allows FortiMail to use DNS based authentication information when establishing secure email transport. It can help verify the certificate or encryption information associated with the destination mail service by using protected DNS records. FortiMail TLS profiles can configure DANE support as none, opportunistic, or mandatory when the required TLS settings permit it. DANE adds another method of validating secure SMTP transport instead of depending only on traditional certificate authority trust. It does not control mailbox quotas or administrator passwords. Its purpose is strengthening authentication of encrypted mail transport through DNS published security information.<\/span><\/p>\n

    Q362. What does SMTPUTF8 support?<\/b><\/p>\n

      \n
    1. <\/b> International email addresses<\/span><\/li>\n
    2. <\/b> Antivirus updates<\/span><\/li>\n
    3. <\/b> Archive rotation<\/span><\/li>\n
    4. <\/b> Administrator profiles<\/span><\/li>\n<\/ol>\n

      Correct Answer: 1. International email addresses<\/b><\/p>\n

      Explanation<\/b><\/p>\n

      SMTPUTF8 extends SMTP so FortiMail can support internationalized email addresses containing characters outside the traditional ASCII character set. When enabled, FortiMail can also perform DNS queries involving supported international domain names. This feature is important for organizations that exchange email using addresses containing language specific characters. Both FortiMail and communicating mail systems must support the required standards for successful delivery. SMTPUTF8 does not update antivirus databases or manage archive rotation. Its purpose is expanding SMTP compatibility so email addresses and related domain information can contain supported international characters.<\/span><\/p>\n

      Q363. What can MTA STS checking improve?<\/b><\/p>\n

        \n
      1. <\/b> Quarantine storage<\/span><\/li>\n
      2. <\/b> Mailbox authentication<\/span><\/li>\n
      3. <\/b> Spam scoring<\/span><\/li>\n
      4. <\/b> Security of outbound SMTP transport<\/span><\/li>\n<\/ol>\n

        Correct Answer: 4. Security of outbound SMTP transport<\/b><\/p>\n

        Explanation<\/b><\/p>\n

        MTA STS allows receiving domains to publish policies describing how sending mail systems should use TLS when delivering email to them. FortiMail can check these policies for outgoing email according to system configuration. Administrators can configure checking for external domains or for all applicable domains. A TLS profile can then use MTA STS information when determining secure delivery requirements. This helps reduce the risk that encrypted SMTP communication is downgraded or redirected improperly. MTA STS does not manage quarantine capacity or spam scoring. Its purpose is improving the security requirements applied to outbound SMTP transport.<\/span><\/p>\n

        Q364. What does the MSA service provide?<\/b><\/p>\n

          \n
        1. <\/b> Archive searching<\/span><\/li>\n
        2. <\/b> Separate SMTP message submission<\/span><\/li>\n
        3. <\/b> DKIM key storage<\/span><\/li>\n
        4. <\/b> Malware quarantine<\/span><\/li>\n<\/ol>\n

          Correct Answer: 2. Separate SMTP message submission<\/b><\/p>\n

          Explanation<\/b><\/p>\n

          The SMTP message submission service allows email clients to submit outgoing messages through a separate service rather than using the same SMTP handling intended primarily for mail transfer agents. FortiMail can enable this service on a dedicated TCP port. The commonly configured submission port is 587. Separating client submission from normal mail relay can make authentication and access policies easier to manage. MSA does not perform archive searching or store DKIM keys. Its purpose is providing an appropriate SMTP service through which authenticated email clients can submit messages for delivery.<\/span><\/p>\n

          Q365. What can delivery tracking record?<\/b><\/p>\n

            \n
          1. <\/b> Mail queue delivery status<\/span><\/li>\n
          2. <\/b> Administrator passwords<\/span><\/li>\n
          3. <\/b> DNS ownership<\/span><\/li>\n
          4. <\/b> DKIM private keys<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1. Mail queue delivery status<\/b><\/p>\n

            Explanation<\/b><\/p>\n

            Delivery tracking records changes in the delivery state of messages handled by the FortiMail queue. Recorded states can include queued, delivering, delivered, blocked, or failed. Administrators can use this information in history logs to determine what happened to a message after FortiMail accepted it. This is particularly useful when investigating delayed or failed mail because it provides visibility beyond the initial message processing stage. Delivery tracking does not expose administrator passwords or cryptographic keys. Its purpose is maintaining a useful history of message delivery progress so administrators can troubleshoot mail flow more effectively.<\/span><\/p>\n

            Q366. What does TLS tracking make available?<\/b><\/p>\n

              \n
            1. <\/b> Additional quarantine folders<\/span><\/li>\n
            2. <\/b> Sender aliases<\/span><\/li>\n
            3. <\/b> TLS usage statistics<\/span><\/li>\n
            4. <\/b> Administrator certificates<\/span><\/li>\n<\/ol>\n

              Correct Answer: 3. TLS usage statistics<\/b><\/p>\n

              Explanation<\/b><\/p>\n

              TLS tracking allows FortiMail to collect statistics about whether messages were received or delivered through encrypted or unencrypted SMTP connections. When enabled, administrators can review TLS statistics in FortiView. The information can show which domains communicated through secure connections and which TLS versions were used. This is useful for identifying domains that still rely on clear text transport or older security protocols. TLS tracking does not create certificates or sender aliases. Its purpose is providing visibility into actual use of encrypted SMTP transport so administrators can evaluate and improve email transport security.<\/span><\/p>\n

              Q367. What does an EHLO limit help prevent?<\/b><\/p>\n

                \n
              1. <\/b> Excessive SMTP probing<\/span><\/li>\n
              2. <\/b> Archive deletion<\/span><\/li>\n
              3. <\/b> DKIM signing<\/span><\/li>\n
              4. <\/b> Mailbox expansion<\/span><\/li>\n<\/ol>\n

                Correct Answer: 1. Excessive SMTP probing<\/b><\/p>\n

                Explanation<\/b><\/p>\n

                A session profile can restrict how many EHLO or HELO commands a client is permitted to issue during one SMTP session. Excessive greetings can be associated with automated probing or attempts to test how the mail server responds to repeated SMTP initialization. FortiMail can terminate a connection after the configured limit is exceeded. This forces abusive clients to establish new sessions and makes repeated probing less efficient. The setting does not control mailbox capacity or DKIM signing. Its purpose is protecting SMTP sessions from clients that repeatedly issue greeting commands beyond normal expected behavior.<\/span><\/p>\n

                Q368. What can an email per session limit reduce?<\/b><\/p>\n

                  \n
                1. <\/b> DNS lookups<\/span><\/li>\n
                2. <\/b> Certificate validation<\/span><\/li>\n
                3. <\/b> Archive indexing<\/span><\/li>\n
                4. <\/b> Mass mailing activity<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 4. Mass mailing activity<\/b><\/p>\n

                  Explanation<\/b><\/p>\n

                  FortiMail session profiles can restrict how many email messages a client is permitted to send during one SMTP session. This helps reduce mass mailing activity and prevents a single connection from being used to submit an excessive volume of messages. When the configured limit is reached, FortiMail can terminate or restrict further activity according to session processing. Administrators should select values that accommodate legitimate mail systems while discouraging abusive automation. The setting does not control archive indexing or certificate validation. Its purpose is limiting message volume within individual SMTP sessions and reducing automated bulk mail abuse.<\/span><\/p>\n

                  Q369. What can minimum encryption strength require?<\/b><\/p>\n

                    \n
                  1. <\/b> Longer quarantine retention<\/span><\/li>\n
                  2. <\/b> A minimum TLS key strength<\/span><\/li>\n
                  3. <\/b> More archive accounts<\/span><\/li>\n
                  4. <\/b> Additional recipient aliases<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 2. A minimum TLS key strength<\/b><\/p>\n

                    Explanation<\/b><\/p>\n

                    A FortiMail TLS profile can require a minimum encryption strength when secure transport is configured. This ensures that an encrypted SMTP connection does not use cryptographic parameters that are weaker than the organization’s security requirement. If the remote system cannot establish a connection that meets the configured strength, FortiMail can apply the selected failure behavior. Administrators should balance security with compatibility because some older mail systems may not support stronger cryptography. The setting does not affect archive accounts or recipient aliases. Its purpose is enforcing an acceptable cryptographic strength for protected TLS communication.<\/span><\/p>\n

                    Q370. What can a TLS failure action determine?<\/b><\/p>\n

                      \n
                    1. <\/b> Response when secure transport fails<\/span><\/li>\n
                    2. <\/b> Mailbox creation<\/span><\/li>\n
                    3. <\/b> Antivirus update time<\/span><\/li>\n
                    4. <\/b> Archive password<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 1. Response when secure transport fails<\/b><\/p>\n

                      Explanation<\/b><\/p>\n

                      A TLS profile can define how FortiMail responds when the required secure connection cannot be established. Depending on configuration, FortiMail can fail the delivery permanently or return a temporary failure so another attempt can occur later. This is particularly important when secure TLS transport is mandatory because silently falling back to clear text could violate security requirements. Administrators should choose the failure behavior according to business and partner communication needs. The TLS failure action does not create mailboxes or determine antivirus update times. Its purpose is controlling delivery behavior when required encryption cannot be successfully established.<\/span><\/p>\n

                      Q371. What can full archive indexing index?<\/b><\/p>\n

                        \n
                      1. <\/b> Only recipient addresses<\/span><\/li>\n
                      2. <\/b> Only message subjects<\/span><\/li>\n
                      3. <\/b> Entire archived messages<\/span><\/li>\n
                      4. <\/b> Only administrator actions<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 3. Entire archived messages<\/b><\/p>\n

                        Explanation<\/b><\/p>\n

                        FortiMail archive accounts can use different indexing levels. Full indexing processes the entire archived message rather than indexing only headers or leaving the archive unindexed. This improves the ability to perform detailed content searches across archived email. The tradeoff is that full indexing requires additional storage and processing compared with header only indexing. Administrators should select an index type according to archive search requirements and available resources. Full indexing is not limited to recipient addresses or message subjects. Its purpose is making the complete archived message searchable for faster and more detailed archive investigations.<\/span><\/p>\n

                        Q372. What can remote archive IMAP access provide?<\/b><\/p>\n

                          \n
                        1. <\/b> SMTP rate control<\/span><\/li>\n
                        2. <\/b> Access to archived email<\/span><\/li>\n
                        3. <\/b> DKIM verification<\/span><\/li>\n
                        4. <\/b> Antivirus scanning<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 2. Access to archived email<\/b><\/p>\n

                          Explanation<\/b><\/p>\n

                          FortiMail can permit archive accounts to be accessed remotely through IMAP when that capability is enabled. The archive account name can be used as the login identity together with the configured archive password. This allows authorized users or applications to access stored archived messages without relying solely on the FortiMail graphical interface. Access should be protected carefully because archives can contain sensitive historical email. IMAP archive access does not perform DKIM verification or antivirus scanning. Its purpose is providing an additional supported method for authorized retrieval and management of archived email.<\/span><\/p>\n

                          Q373. What can an archive Forward to setting do?<\/b><\/p>\n

                            \n
                          1. <\/b> Send a copy to another email address<\/span><\/li>\n
                          2. <\/b> Disable SMTP<\/span><\/li>\n
                          3. <\/b> Increase spam scoring<\/span><\/li>\n
                          4. <\/b> Delete archived mail<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 1. Send a copy to another email address<\/b><\/p>\n

                            Explanation<\/b><\/p>\n

                            An archive account can be configured with a Forward to address. When FortiMail archives a qualifying email, it can also forward a copy to the specified email address. This can support external retention workflows, compliance monitoring, or integration with another archival platform. Administrators should ensure the destination is secure because archived messages may contain confidential information. The forwarding function does not delete the archive copy or increase spam scoring. Its purpose is allowing FortiMail to send an additional copy of archived messages to another configured email destination when organizational requirements call for it.<\/span><\/p>\n

                            Q374. When can personal quarantine fall back to system quarantine?<\/b><\/p>\n

                              \n
                            1. <\/b> For incoming email<\/span><\/li>\n
                            2. <\/b> During DNS lookup<\/span><\/li>\n
                            3. <\/b> For outgoing email<\/span><\/li>\n
                            4. <\/b> During administrator login<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 3. For outgoing email<\/b><\/p>\n

                              Explanation<\/b><\/p>\n

                              Personal quarantine is designed primarily for incoming email associated with individual recipients. When an antispam action attempts to use personal quarantine for outgoing email, FortiMail instead falls back to the system quarantine. This is necessary because the normal personal quarantine workflow is not appropriate for outbound messages in the same way it is for incoming recipient mail. Administrators should understand this fallback when designing outbound spam actions so messages are held in the expected location. The behavior is unrelated to DNS or administrator login. Its purpose is ensuring outgoing quarantined messages are stored in an appropriate centralized location.<\/span><\/p>\n

                              Q375. What can system quarantine notification provide?<\/b><\/p>\n

                                \n
                              1. <\/b> Automatic DNS configuration<\/span><\/li>\n
                              2. <\/b> More disk interfaces<\/span><\/li>\n
                              3. <\/b> New mail routes<\/span><\/li>\n
                              4. <\/b> A release link for quarantined mail<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 4. A release link for quarantined mail<\/b><\/p>\n

                                Explanation<\/b><\/p>\n

                                When FortiMail sends a message to system quarantine, administrators can enable a notification profile that informs selected people about the quarantined email. The notification can contain a link that allows an authorized recipient to release the held message. This provides a convenient review workflow without requiring every recipient to navigate manually through quarantine management. Notifications should be configured carefully so only appropriate people receive release capability. They do not configure DNS or create routes. Their purpose is informing authorized users that a message has been quarantined and providing a controlled method for releasing it when appropriate.<\/span><\/p>\n

                                Q376. What can repackage infected email with customized content do?<\/b><\/p>\n

                                  \n
                                1. <\/b> Delete the sender account<\/span><\/li>\n
                                2. <\/b> Forward infected email as an attachment<\/span><\/li>\n
                                3. <\/b> Disable TLS<\/span><\/li>\n
                                4. <\/b> Create an archive account<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 2. Forward infected email as an attachment<\/b><\/p>\n

                                  Explanation<\/b><\/p>\n

                                  An antivirus action profile can repackage an infected email so the original message is forwarded as an attachment inside a new message with customized explanatory content. Administrators can use an email template to explain that the attached message was identified as infected or otherwise modified by antivirus processing. This approach preserves the original email for controlled review while giving recipients a clear warning. It should only be used where organizational policy permits access to infected content. Repackaging does not disable TLS or create archives. Its purpose is delivering the original infected message inside a controlled warning message.<\/span><\/p>\n

                                  Q377. What happens to some reject actions during FortiSandbox holding?<\/b><\/p>\n

                                    \n
                                  1. <\/b> They can fall back to system quarantine<\/span><\/li>\n
                                  2. <\/b> They disable FortiGuard<\/span><\/li>\n
                                  3. <\/b> They become archive actions<\/span><\/li>\n
                                  4. <\/b> They create recipient aliases<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 1. They can fall back to system quarantine<\/b><\/p>\n

                                    Explanation<\/b><\/p>\n

                                    FortiMail antivirus and antispam action behavior can change when messages are being held for FortiSandbox analysis or certain FortiGuard outbreak protection functions. In these situations, a configured reject action can fall back to system quarantine because FortiMail has already accepted or retained the message for further analysis. Administrators should understand this behavior when troubleshooting why a message was quarantined instead of rejected immediately. The fallback does not create aliases or disable FortiGuard. Its purpose is ensuring that messages requiring delayed security analysis remain under controlled FortiMail storage while the final security determination is completed.<\/span><\/p>\n

                                    Q378. What can archive account status control?<\/b><\/p>\n

                                      \n
                                    1. <\/b> SMTPUTF8 support<\/span><\/li>\n
                                    2. <\/b> Sender reputation<\/span><\/li>\n
                                    3. <\/b> Whether the archive account is usable<\/span><\/li>\n
                                    4. <\/b> TLS key strength<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 3. Whether the archive account is usable<\/b><\/p>\n

                                      Explanation<\/b><\/p>\n

                                      An archive account must be enabled before FortiMail can use it as a destination for email archiving. If the account is disabled, it cannot be selected or used normally in the places where archive destinations are required. This provides administrators with a way to temporarily stop use of an archive account without necessarily deleting its configuration. Archive status does not affect TLS strength or sender reputation. Its purpose is controlling whether a configured archive account is active and available for policies and other archive related functions that need to store retained email.<\/span><\/p>\n

                                      Q379. What does header only archive indexing process?<\/b><\/p>\n

                                        \n
                                      1. <\/b> Entire attachment content<\/span><\/li>\n
                                      2. <\/b> Message headers<\/span><\/li>\n
                                      3. <\/b> Administrator logs<\/span><\/li>\n
                                      4. <\/b> Antivirus databases<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 2. Message headers<\/b><\/p>\n

                                        Explanation<\/b><\/p>\n

                                        Header indexing creates searchable archive information from message headers without indexing the complete contents of each archived email. This can provide faster searching for common fields while consuming fewer resources than full message indexing. Administrators can choose between no indexing, header indexing, and full indexing according to search needs and available storage. Header indexing is useful when searches mainly depend on sender, recipient, subject, and similar message metadata. It does not index antivirus databases or administrator logs. Its purpose is providing a balanced archive search option that indexes important email header information without processing the entire message.<\/span><\/p>\n

                                        Q380. What can SMTP MSA authentication protect?<\/b><\/p>\n

                                          \n
                                        1. <\/b> Archive indexing<\/span><\/li>\n
                                        2. <\/b> DNS caching<\/span><\/li>\n
                                        3. <\/b> Quarantine retention<\/span><\/li>\n
                                        4. <\/b> Client message submission<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 4. Client message submission<\/b><\/p>\n

                                          Explanation<\/b><\/p>\n

                                          FortiMail can enable authentication for SMTP services including message submission. Authentication helps ensure that only approved users or systems can submit messages through the service. This is especially important for MSA because it is intended for email clients rather than unrestricted mail transfer between servers. Administrators can combine authentication with TLS so credentials and submitted messages receive stronger protection while travelling across the network. MSA authentication does not control archive indexing or quarantine retention. Its purpose is verifying the identity of clients that use FortiMail’s dedicated SMTP submission service to send email.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full Fortinet FCP_FML_AD-7.4 Exam Dumps and Practice Test Dumps. Q361. What does DANE help FortiMail verify? Mailbox quota Archive retention TLS identity through DNS information Administrator password age Correct Answer: 3. TLS identity through DNS information Explanation DANE allows FortiMail to use DNS based authentication information when establishing secure email transport. It can help […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23882"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=23882"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23882\/revisions"}],"predecessor-version":[{"id":23883,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23882\/revisions\/23883"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=23882"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=23882"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=23882"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}