Your startup wants to implement an order fulfillment process for selling a personalized gadget that needs an
average of 3-4 days to produce with some orders taking up to 6 months you expect 10 orders per day on your
first day. 1000 orders per day after 6 months and 10,000 orders after 12 months.
Orders coming in are checked for consistency men dispatched to your manufacturing plant for production
quality control packaging shipment and payment processing If the product does not meet the quality standards
at any stage of the process employees may force the process to repeat a step Customers are notified via email
about order status and any critical issues with their orders such as payment failure.
Your case architecture includes AWS Elastic Beanstalk for your website with an RDS MySQL instance for
customer data and orders.
How can you implement the order fulfillment process while making sure that the emails are delivered reliably?
A.
Add a business process management application to your Elastic Beanstalk app servers and re-use the ROS
database for tracking order status use one of the Elastic Beanstalk instances to send emails to customers.
B.
Use SWF with an Auto Scaling group of activity workers and a decider instance in another Auto Scaling
group with min/max=1 Use the decider instance to send emails to customers.
C.
Use SWF with an Auto Scaling group of activity workers and a decider instance in another Auto Scaling
group with min/max=1 use SES to send emails to customers.
D.
Use an SQS queue to manage all process tasks Use an Auto Scaling group of EC2 Instances that poll the
tasks and execute them. Use SES to send emails to customers.
C
https://acloud.guru/forums/aws-certified-solutions-architect-professional/discussion/-KR0eDcXaZ3Xn42BVJoT/?answer=-KR1gY0YplksaP8O3Ph4
I don’t like option A because it forces you to build your own application to track this complicated workflow. SWF is specifically built for this type of tracking.
It can’t be option D because SQS can only hold info for up to 14 days.
Options B & C are identical except in B the Decider sends the email and in C SES is used to send the email. This is very tricky syntax. SES, is of course Amazon’s email service. It would not likely make sense to have an SMTP server on a Decider. It is possible that the decider could send the email through SES, but I think that a Decider would actually put the decision to email into the queue and an activity worker would pick it up and send the email through SES. Regardless option C appears to be the correct answer.
0
0