A company is developing an application that provides order shipping statistics for retrieval by a REST API. The company wants to extract the shipping statistics, organize the data into an easy-to-read HTML format, and send the report to several email addresses at the same time every morning.
Which combination of steps should a solutions architect take to meet these requirements? (Choose two.)
To meet the requirements of extracting shipping statistics, organizing the data into an HTML format, and sending the report to several email addresses at the same time every morning, the best approach is to use Amazon SES and Amazon EventBridge with AWS Lambda. Amazon SES is capable of formatting data into HTML and sending it via email, which meets the requirement for sending the report. Amazon EventBridge can create a scheduled event that triggers an AWS Lambda function to query the application's API for the data, fulfilling the need to perform this task every morning at the same time. Combining SES with EventBridge and Lambda allows for the automation and scheduling needed, as well as the capability to send formatted emails.
You can use SES to format the report in HTML. https://docs.aws.amazon.com/ses/latest/dg/send-email-formatted.html
this document is talking about the SES API. not ses. SES does not format data. just sending emails. https://aws.amazon.com/ses/
When you send an email with Amazon SES, the email information you need to provide depends on how you call Amazon SES. You can provide a minimal amount of information and have Amazon SES take care of all of the formatting for you. Or, if you want to do something more advanced like send an attachment, you can provide the raw message yourself. https://docs.aws.amazon.com/ses/latest/dg/send-email-concepts-email-format.html
B&D are the only 2 correct options. If you are choosing option E then you missed the daily morning schedule requirement mentioned in the question which cant be achieved with S3 events for SNS. Event Bridge can used to configure scheduled events (every morning in this case). Option B fulfills the email in HTML format requirement (by SES) and D fulfills every morning schedule event requirement (by EventBridge)
I don't believe you are correct when you say that E cannot meet the scheduling requirement. If the glue action is scheduled and outputs to S3, then as the S3 event destination is SNS, in effect you have a way of getting SNS to have a scheduled release.
But E does not include a glue action. We need either C or D for the scheduling, plus B or E for the email sending.
the daily schedule can be achieve with event bridge - schedule and event bridge to trigger daily - the event briodge will trigger a lambda function that will collect data and save it in s3 - once data in s3 the event noitification will trigger SNS to send emails
Answer: B and D Other options A. Amazon Kinesis Data Firehose: This service is typically used for real-time streaming data processing rather than for scheduled tasks like generating a morning report. C. Amazon EventBridge to invoke an AWS Glue job: AWS Glue is a data integration service that's more focused on ETL (extract, transform, load) operations, often involving large datasets and complex transformations, which might be more than needed for this scenario. E. Amazon S3 with SNS topic: Storing data in S3 and using SNS for notification is viable, but this doesn't directly address the need to format the data into HTML and send it as an email report. SNS is better suited for sending notifications rather than formatted reports.
"At the same time every morning" requires scheduling, which is only mentioned in C and D. AWS Glue has no native functionality to query REST APIs, thus we need a Lambda function -> D. For email we need SES or SNS, but as we want "an easy-to-read HTML format", SNS is out. SNS can send notifications, not formatted emails. Thus B.
Both SES and SNS can format html, but there is a disconnection between B and D. Where do you store the data between the steps?
Why would I need to "store the data"? Wouldn't the Lamba function just call the SES API?
Defo B and D Look at the aws notes on Sns Notes You can't customize the body of the email message. The email delivery feature is intended to provide internal system alerts, not marketing messages. It can't send anything but notifications. SES can send normal emails therefore, BD is the answer.
Very detailed question so let's break it down: "send the report to several email addresses at the same time every morning" this locks B as nothing else can do it. A: Firehose to collect data from API will work but it cannot generate a report C: Glue is ETL, it cannot extract data from an API E: Store data in S3. No idea what this will help with The API provides order shipping data so you can query it. Lambda can be used to query the API easily so D is good choice that works with B. BD is correct combination
the reason why "B" is more correct than "E" is because is more simple and you don't have to store data is not what they want, also SES is a service that is meant for sending the data through email, and is exactly what the company wants. is not the first time the admin is wrong with the answer
Create an Amazon EventBridge (Amazon CloudWatch Events) scheduled event that invokes an AWS Lambda function to query the application's API for the data. Then use Amazon Simple Email Service (Amazon SES) to format the data and to send the report by email.
SNS & Glue
BC - Question says extract the data - which is the job of AWS Glue and then invoke SES endpoint to send email. SES support html format. But BD also seems possible.
Option B suggests using Amazon SES, which allows you to format the data and email the report to multiple recipients in an efficient and scalable way. Option E proposes storing application data in Amazon S3, which is scalable and durable storage. By configuring an Amazon SNS topic as an S3 event destination, you can automatically trigger the report to be sent via email whenever new data is added to S3.
Chat GPT says : With Amazon SES, you can send rich, formatted email content, including text, HTML, attachments, and embedded images, suitable for email communication. Amazon SNS is primarily used for sending plain-text or JSON-formatted messages, suitable for notifications and alerts across different channels. This can suggest that we need to use SES if we want to use HTML content.
Key: Send email every morning same time - 1. Simple email 2. AWS Event Bridge with lambda
I think there is a problem with the answer. It should be that ses sends the email processed by lambda.
Key: retrieval by a REST API, that's why use lambda
E should be correct: https://saturncloud.io/blog/how-to-send-html-mails-using-amazon-sns/
I believe BD are the answers. E can't be used, because, in E can't help with email formatting. E won't be the best choice even for scheduling.