After a resident pays an online building permit fee, the city must send a reliable transactional receipt email from its verified domain. Which AWS service should handle that outbound email?
Select an answer to reveal the explanation.
Short Explanation
SES is the city’s outbound mail truck for application email — receipts, confirmations, notices — without standing up a whole mailbox farm. SNS push is for apps, WorkMail is people’s inboxes, and Pinpoint leans campaign/engagement; for a simple transactional receipt, SES is the fit.
Full Explanation
After a resident pays an online building permit fee, the city must send a reliable transactional receipt email from its verified domain—Amazon SES is the service that should handle that outbound email. Simple Email Service is built for application-generated email at scale: receipts, confirmations, notices, and other transactional messages, using verified identities and proper authentication (SPF/DKIM/DMARC practices) so citizen inboxes trust city mail.
Amazon SNS mobile push delivers app notifications, not SMTP email receipts as its primary model for this stem. Amazon WorkMail provides employee mailbox suites; buying full mailboxes for every seasonal inspector is the wrong tool merely to send automated receipts. Amazon Pinpoint journeys emphasize customer engagement and campaigns; while related to messaging, the straightforward transactional receipt path at CLF identify level is SES. Pick the simplest correct service for transactional email.
Exam caveat: SES = send email from apps; WorkMail = managed mailboxes for people; SNS = pub/sub notifications including SMS/push; Pinpoint = engagement/campaigns. Receipt after payment → SES.
Operational check for permit receipts: verify the sending domain in SES, configure DKIM, move out of sandbox for production volumes, template receipt content with payment IDs (no unnecessary card data), handle bounces and complaints, log message IDs for support disputes, and throttle or queue bursts after high-volume filing deadlines.