Cost-Effective Serverless Contact Form on S3
Short answer
B Use API Gateway and Lambda to process the form and SNS to trigger email notifications, minimizing cost for low traffic.
Question
Key Takeaways
The exam tests the ability to decouple static hosting from dynamic logic; the common trap is over-engineering with EC2 or ECS when a simple Lambda function suffices for infrequent traffic.
This question evaluates the design of a cost-effective serverless architecture for a low-traffic static website requiring dynamic form processing and email notifications using AWS Lambda, API Gateway, and SNS.
Common mistake: Candidates often choose Amazon ECS (Option A) because they associate 'dynamic components' with containers, failing to recognize that Lambda is significantly more cost-effective for less than 100 monthly visits.
Expert Analysis
Why the Answer Is Correct
Option B is the correct choice because it leverages a fully managed, event-driven serverless stack that aligns perfectly with the low-traffic requirement. Amazon S3 hosts the static assets, while API Gateway triggers an AWS Lambda function to handle the form submission logic. Since the volume is under 100 visits/month, Lambda's free tier makes this nearly free. The use of Amazon SNS provides a robust, decoupled notification mechanism to send emails (via SES subscription or direct SNS-to-email), ensuring reliability without managing infrastructure.
Why the Other Options Are Wrong
Option A uses Amazon ECS, which requires provisioning and managing containers (Fargate or EC2), incurring continuous costs regardless of traffic, making it the least cost-effective option. Option C suggests using AWS Amplify for both static and dynamic content but incorrectly specifies SQS for delivery; SQS is a queue, not a notification service, and would require additional polling logic to actually notify the company. Option D involves migrating to Windows EC2 instances, which carries the highest cost due to instance hours and administrative overhead, completely violating the 'most cost-effective' constraint.
Community Comment Notes
The community consensus strongly supports Option B, with multiple users citing the low traffic volume ('fewer than 100 site visits') as the primary indicator for choosing Lambda over containerized solutions. One user noted that SNS is specifically designed for pushing messages to subscribers, reinforcing the architectural fit. Another commenter highlighted that the limitation of submissions allows for the pay-per-use model of Lambda to be optimal.
Exam Strategy
Always check the traffic volume and frequency first. If the workload is sporadic or low-volume, default to serverless options like Lambda rather than always-on compute like EC2 or ECS to minimize cost.
Frequently Asked Questions
Why not use ECS for the dynamic part?
How does SNS send the email?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 5 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 5
-
Scheldon 👍 3 Answered BAnswerB API gateway + Lambda seems to be the best option expecially when SNS is in use which is specially created to push messaged to the subscribers (company appropraiate team in this situation)
-
KennethNg923 👍 3 Answered Bas it said "The company expects fewer than 100 site visits each month" and Lambda charge per each time calling it, so i will go for B
-
EdricHoang 👍 3 Answered BLimitation is 100 submission a month, not frequent -> Lambda
-
mk168898 👍 2i see need to notify => SNS
-
Hkayne 👍 2 Answered BB is the right answer
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SAA-C03 Questions
Access 120 questions with complete answers and detailed explanations.
View Full SAA-C03 Practice Test →