A Cisco ESA administrator must provide outbound email authenticity and configures a DKIM signing profile to handle this task. What is the next step to allow this organization to use DKIM for their…

Question

Options

• AConfigure the Trusted Sender Group message authenticity policy.
• BExport the DNS TXT record to provide to the DNS registrar.
• CImport the DNS record of the service provider into the Cisco ESA.
• DEnable the DKIM service checker.

• A
  4% (1)
• B
  93% (25)
• C
  4% (1)

Explanation

DKIM (DomainKeys Identified Mail) works by having the sending mail server sign outbound messages with a private key. Receiving servers then verify the signature using the corresponding public key, which must be published in DNS as a TXT record under the signing domain's _domainkey subdomain. After creating the DKIM signing profile on Cisco ESA (which generates the key pair and signing configuration), the administrator must export the DNS TXT record containing the public key and provide it to the DNS registrar or DNS administrator so it can be published publicly. Without this step, receiving mail servers have no way to retrieve the public key to verify signatures, and DKIM authentication will fail. Importing a DNS record (C), enabling a service checker (D), or configuring a Trusted Sender Group (A) are not the next required steps in making DKIM operational for outbound mail.

No community discussion yet for this question.