A municipal CRM follows a classic three-tier design: web, application, and database. How should the architect place the tiers for a scalable, loosely coupled layout on AWS?
Select an answer to reveal the explanation.
Short Explanation
Three floors, three locks: ALB to the app tier, database tucked in private subnets, each floor scalable alone. One public kitchen-sink instance or a naked public database is how outages and breaches share a calendar invite.
Full Explanation
Classic multi-tier architectures separate presentation, application, and data tiers, typically using an ALB toward the app tier and placing databases in private subnets without public exposure. Collocating all tiers on one public instance or eliminating server tiers undermines scalability and isolation.