Quiz: Module 18: Architecture Patterns on AWS

A startup is building its first product: a simple task management application with CRUD operations, a small team of 3 developers, and uncertain traffic patterns. The team is debating between a microservices architecture and a monolithic architecture. Which approach should the team choose, and why?

A media company needs to serve 1 million page views per day for a content website. The content is mostly static (articles, images) with a dynamic comments section. The company wants the lowest possible latency for users worldwide and the lowest hosting cost for static content. Which architecture pattern should the company use?

A company is migrating a monolithic Java application to microservices on AWS. The application has 8 major features, and the team wants to minimize migration risk. Which migration strategy should the team use?

An e-commerce platform processes orders through the following steps: validate the order, charge the payment, update inventory, and send a confirmation email. Each step is handled by a different service. The payment service occasionally fails due to third-party API timeouts. The team wants to ensure that a payment failure does not block inventory updates or email notifications. Which architecture pattern best addresses this requirement?

When should you choose Amazon EventBridge over Amazon SQS for event routing?

A solutions architect is designing a data processing pipeline. Raw CSV files (50 MB each, 100 files per day) are uploaded to S3. Each file must be validated, transformed into Parquet format, and stored in a separate S3 bucket for analytics queries using Athena. Which pipeline architecture is most appropriate for this scale?

A company runs a three-tier web application (ALB, EC2 Auto Scaling group, RDS PostgreSQL). The application experiences 10x traffic spikes during flash sales that last 2 hours. During normal hours, traffic is steady and predictable. The company wants to optimize costs without degrading performance during spikes. Which architectural change should the company evaluate?

A solutions architect is presenting two architecture options to a stakeholder for a new application: Option A: ECS Fargate with ALB, RDS Multi-AZ, ElastiCache. Estimated cost: $2,500/month. Provides consistent sub-50ms latency, 99.95% availability, and supports WebSocket connections. Option B: API Gateway + Lambda + DynamoDB. Estimated cost: $800/month at current traffic. Provides variable latency (50ms to 500ms due to cold starts), 99.95% availability, and does not natively support WebSocket connections on REST APIs. The application requires WebSocket support for real-time notifications and consistent sub-100ms latency. Which option should the architect recommend, and how should the architect justify the higher cost?