CLF-C02 Cloud Technology and Services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Amazon SNS

  Why it's wrong here

  Amazon Simple Notification Service (SNS) is a pub/sub messaging service that delivers notifications to subscribers by fanning out to Lambda functions, HTTP/S endpoints, mobile push targets, and other destinations. Although SNS does have an email subscription protocol, it is not engineered for automated, high-volume transactional email: it lacks SES's dedicated IP management, reputation dashboard, detailed bounce/complaint handling, and content-filtering controls. Consequently, using SNS for password-reset emails would leave email deliverability and abuse handling largely unmanaged and is not the architecturally correct alternative to SES.

• ✗

  Amazon SQS

  Why it's wrong here

  Amazon Simple Queue Service (SQS) is a fully managed message queuing service used to decouple application components by temporarily buffering messages between producers and consumers. It does not natively send email at all; SQS queues are polled by application consumers, and any email dispatch would require a separate service to read the messages and actually deliver them, making SQS only a transport layer. A common real-world pattern is to place SQS between an application and SES to smooth out traffic spikes, but SQS itself can never substitute for email-sending capability, so it is incorrect to select it as the email-sending service.

• ✓

  Amazon SES

  Why this is correct

  Amazon Simple Email Service (SES) is the appropriate choice for a solution that must reliably send transactional emails such as order confirmations and password resets at high volume. It supports both sending and receiving email, provides built-in bounce and complaint tracking, suppression lists, and deliverability monitoring, and exposes APIs that allow templated, personalized messages to be sent at scale. SES also integrates with AWS Lambda and CloudWatch for event-based notifications, making it the native AWS email delivery service rather than a general-purpose messaging or queuing system.

• ✗

  Amazon Pinpoint

  Why it's wrong here

  Amazon Pinpoint is designed for targeted, audience-segmented marketing campaigns, not for the reliable, transactional one-to-one delivery of order confirmations and password resets at scale. It lacks the built-in, per-message sending limits and bounce/complaint handling that Amazon Simple Email Service (SES) provides for transactional email. Pinpoint is tempting because it can send bulk emails, but its correct use case is user engagement analytics and push notifications, not automated, high-volume transactional messages.

Go deeper

Related to this question