A recreation booking site serves a static front end, calls business logic through an API, and must avoid storing session state on servers. Which architecture best matches a serverless multi-tier pattern?
Select an answer to reveal the explanation.
Short Explanation
Static pages up front, Lambda behind API Gateway in the middle, managed data in the back—and sessions live off the servers. One EC2 burrito with local sessions is the opposite of serverless multi-tier.
Full Explanation
A common serverless multi-tier design uses static hosting for the presentation tier, API Gateway plus Lambda for application logic, and a managed database or similar store for data, keeping compute ephemeral and stateless. Monolithic EC2 with local sessions or unmanaged FTP/sticky-disk patterns do not match that architecture.