AWS SAP-C02 Architecture Patterns
Architecture patterns are where individual decisions become complete systems.
While pillars explain how to make specific decisions and topics organize what decisions you’ll face, patterns show how everything fits together in production-ready architectures.
These aren’t theoretical patterns. They’re the recurring enterprise architectures that AWS Solutions Architects design repeatedly—and that SAP-C02 tests repeatedly.
What Makes Patterns Different #
| Content Type | Purpose | Scope |
|---|---|---|
| Pillars | Deep-dive into one decision area | Single topic, comprehensive depth |
| Categories | Group related decisions | Multiple pillars, organized by domain |
| Patterns | Complete architecture patterns | Multiple pillars + categories, integrated design |
An pattern answers: “When I need to build [X type of system], what does the complete architecture look like?”
Each pattern synthesizes decisions from multiple domains—networking, security, storage, compute—into a coherent whole. Understanding patterns helps you recognize complete patterns in exam questions, not just individual service choices.
The Six Enterprise Patterns #
SAP-C02 scenarios consistently map to six fundamental architecture patterns. Master these, and you’ll recognize the underlying structure in most exam questions.
1. Global & Multi-Region Scalability #
The Challenge: Serve users worldwide with consistent performance, maintain availability during regional failures, and manage data consistency across geographies.
When You’ll See It: Questions involving global user bases, sub-100ms latency requirements, regional failover, or data sovereignty with global access.
👉 Read enterprise pattern details for global scaling .
| Component | Pillar Coverage | Key Decisions |
|---|---|---|
| Content Delivery | CloudFront deep-dive | Origin selection, cache behaviors, edge functions |
| DNS Architecture | Route 53 Resolver | Routing policies, health checks, failover configuration |
| Global Databases | Aurora Global, DynamoDB Global Tables | Replication topology, consistency tradeoffs |
| Multi-Region HA | Active-Active DR patterns | Data synchronization, traffic distribution |
2. Hybrid Cloud & Edge Connectivity #
The Challenge: Connect on-premises infrastructure to AWS securely and reliably, extend cloud capabilities to edge locations, and manage hybrid identity and data flows.
When You’ll See It: Questions involving data center connectivity, bandwidth requirements, edge processing, hybrid DNS, or gradual cloud migration.
👉 Read enterprise pattern details for hybrid edge
| Component | Pillar Coverage | Key Decisions |
|---|---|---|
| Network Connectivity | Direct Connect, Site-to-Site VPN | Redundancy patterns, bandwidth sizing, encryption |
| Network Hub | Transit Gateway | Attachment strategies, route table design, inter-region peering |
| Hybrid DNS | Route 53 Resolver | Inbound/outbound endpoints, forwarding rules |
| Edge & Data Transfer | Storage Gateway, Snow Family | Gateway types, transfer optimization, edge compute |
3. Serverless & Microservices Design #
The Challenge: Build scalable, event-driven applications without managing infrastructure, decompose monoliths into independently deployable services, and orchestrate complex workflows.
When You’ll See It: Questions involving variable workloads, event processing, API backends, or container orchestration decisions.
👉 Read enterprise pattern details for serverless microservices
| Component | Pillar Coverage | Key Decisions |
|---|---|---|
| Compute & API | Lambda, API Gateway | Function design, concurrency, API patterns |
| Event Routing | EventBridge | Event buses, rules, cross-account events |
| Messaging | SQS, SNS | Queue types, fan-out patterns, ordering guarantees |
| Container Orchestration | ECS, EKS | Fargate vs EC2, service mesh, deployment strategies |
4. Legacy to Cloud Modernization #
The Challenge: Migrate existing workloads to AWS with minimal disruption, modernize applications incrementally, and manage the transition from legacy to cloud-native architectures.
When You’ll See It: Questions involving migration strategies, database migration, application refactoring, or phased modernization approaches.
👉 Read enterprise pattern details for legacy modernization
| Component | Pillar Coverage | Key Decisions |
|---|---|---|
| Migration Strategy | 6 Rs Framework | Rehost vs refactor, prioritization, wave planning |
| Database Migration | DMS, SCT | Homogeneous vs heterogeneous, CDC patterns |
| Application Evolution | Monolith to Microservices | Strangler pattern, service extraction, API facades |
| Architecture Assessment | Modernization patterns | Technical debt, cloud-native readiness |
5. Enterprise Data Lake & Analytics #
The Challenge: Build scalable data platforms that ingest, store, process, and analyze data from diverse sources while managing costs and ensuring security.
When You’ll See It: Questions involving data pipelines, analytics workloads, storage optimization, or cost management for data-intensive applications.
👉 Read enterprise pattern details for data analytics
| Component | Pillar Coverage | Key Decisions |
|---|---|---|
| Data Storage | S3 security, lifecycle policies | Bucket design, access patterns, tiering strategies |
| High-Performance Storage | Storage optimization | EBS types, EFS performance modes, FSx selection |
| Analytics Cost | CUR, cost analysis | Reserved capacity, query optimization, storage classes |
| Data Processing | Lake architecture | ETL patterns, query engines, catalog management |
6. Security & Governance at Scale #
The Challenge: Implement consistent security controls across hundreds of accounts, enforce compliance automatically, and maintain visibility into security posture organization-wide.
When You’ll See It: Questions involving multi-account security, compliance requirements, centralized logging, or organizational policy enforcement.
👉 Read enterprise pattern details for security governance
| Component | Pillar Coverage | Key Decisions |
|---|---|---|
| Account Structure | Organizations, SCPs | OU design, policy inheritance, guardrails |
| Landing Zone | Control Tower | Account factory, detective controls, customization |
| Identity | Federation patterns | IdP integration, role design, cross-account access |
| Security Services | GuardDuty, Config, Security Hub | Aggregation, automation, remediation workflows |
How Patterns Appear in SAP-C02 #
Exam questions rarely announce which pattern they’re testing. Instead, they describe business scenarios that map to these patterns. Learning to recognize the pattern accelerates your path to the correct answer.
| Scenario Signal | Likely Pattern |
|---|---|
| “Users in multiple continents report latency…” | Global & Multi-Region |
| “Existing data center must connect to AWS…” | Hybrid & Edge |
| “Variable traffic with unpredictable spikes…” | Serverless & Microservices |
| “Migrate 500 applications over 18 months…” | Legacy Modernization |
| “Petabytes of data from IoT sensors…” | Data Lake & Analytics |
| “200 AWS accounts across business units…” | Security & Governance |
Complex questions often combine patterns. A global financial services company migrating to AWS might involve elements of Legacy Modernization, Security & Governance, and Global Scaling simultaneously. The skill is identifying which pattern dominates the decision.
Pattern Study Strategy #
For Pattern Recognition #
- Read each pattern overview to understand the complete pattern
- Study the component pillars for decision-making depth
- Practice scenarios in related categories
- Return to the pattern to see how pieces connect
For Exam Preparation #
- Identify which patterns you understand least
- Focus pillar study on gaps within those patterns
- Practice cross-pattern scenarios that combine patterns
- Build mental models for recognizing patterns quickly
For Real-World Application #
These patterns transfer directly to production architecture work. The same patterns you learn for SAP-C02 are the patterns you’ll design and review in enterprise environments.
Continue Your Preparation #
Deepen Individual Decisions #
Each pattern builds on multiple pillars. When you need deeper understanding of a specific component—like Transit Gateway design or Lambda optimization—pillars provide comprehensive coverage.
Organize by Problem Domain #
Categories group decisions by architectural domain. Use them to strengthen specific areas or to see how pillars within a domain relate to each other.
Test Your Pattern Recognition #
500+ questions that test your ability to apply pattern knowledge under exam conditions. Scenarios identify their primary pattern, reinforcing pattern recognition.
Quick Reference: Pattern to Pillar Mapping #
| Pattern | Primary Pillars | Secondary Pillars |
|---|---|---|
| Global & Multi-Region | CloudFront, Route 53, Global Databases | Caching, DNS, Active-Active DR |
| Hybrid & Edge | Direct Connect, Transit Gateway | VPN, Storage Gateway, Snow Family |
| Serverless & Microservices | Lambda, EventBridge, SQS/SNS | API Gateway, ECS/EKS |
| Legacy Modernization | 6 Rs, DMS/SCT | Strangler Pattern, Well-Architected |
| Data Lake & Analytics | S3 Lifecycle, Lake Formation | Athena, Redshift, Cost Analysis |
| Security & Governance | Organizations, Control Tower | GuardDuty, Config, Security Hub |