Defend multi-account, network, security, resilience, and cost choices for a complex organization.
30-Day AWS Solutions Architect – Professional (SAP-C02) Sprint
Pass SAP-C02 by building Professional-level architecture judgment through official guidance, scenarios, applied design, and timed simulations.
Milestones
Observable progress—not content consumed.
Design production solutions across deployment, continuity, security, reliability, performance, and cost.
Diagnose and improve an existing workload against Well-Architected tradeoffs.
Complete timed simulations, close key gaps, and sit SAP-C02.
Learning path
3 of 8 actions complete
Set the SAP-C02 target and establish a baseline
Review exam logistics, reserve the target date, create a four-domain scorecard, and answer architecture questions without notes.
AWS Certified Solutions Architect – Professional
Assigned: Review the exam overview, duration, format, preparation steps, and scheduling path.
Why it matters: Anchor the plan to the current exam format and official preparation path.
Bring back: Which two domains feel least automatic today?
Link checked Jul 21, 2026Reflection logSaved evidence
Learn the Well-Architected decision model
Study architecture tradeoffs and map the four exam domains to the decisions you just reviewed.
AWS Well-Architected Framework
Assigned: Read the introduction, tradeoffs, six pillars, and Well-Architected Tool overview.
Why it matters: Learn the architecture-evaluation model behind Professional-level decisions.
Bring back: Which two pillars are in tension in your sample migration choice?
Link checked Jul 21, 2026SAP-C02 Exam Guide
Assigned: Use the Content Outline as a 20-minute coverage-map check.
Why it matters: Preserve the official scope without turning it into the curriculum.
Bring back: Map each domain to one architecture decision you now understand.
Link checked Jul 21, 2026Reflection logCapture what changed
Scenario drill: organizational complexity
Work timed scenarios covering multi-account governance, hybrid connectivity, centralized logging, and cost allocation; document decisive requirements.
Real-world practice: Use a sanitized migration case without client names, account IDs, or operational data.
Reflection logCapture what changed
Learn multi-VPC hybrid networks and multi-account design
Extract decision rules for Transit Gateway, peering, account isolation, centralized logging, and shared services.
Building a Scalable and Secure Multi-VPC AWS Network Infrastructure
Assigned: Read hub-and-spoke, routing, hybrid connectivity, availability, and tradeoffs.
Why it matters: Understand enterprise networking decisions behind hybrid scenarios.
Bring back: What requirement makes Transit Gateway stronger than repeated VPC peering?
Link checked Jul 21, 2026Reflection logCapture what changed
Apply Domain 1 to a migration architecture
Write a one-page target state covering network path, DNS, identity, account model, logging, recovery objective, and rejected alternatives.
Real-world practice: Apply general patterns to a sanitized migration situation.
Reflection logCapture what changed
Consider: What requirement eliminated the most tempting alternative?
Learn cost governance and cloud financial management
Turn cost visibility, tagging, purchasing, efficiency, and multi-account guardrails into architecture decision cues.
Cost Optimization Pillar
Assigned: Read cloud financial management, expenditure awareness, resource efficiency, and optimization over time.
Why it matters: Treat cost choices as architecture decisions, not post-launch cleanup.
Bring back: Which control belongs at organization level and which belongs in workload design?
Link checked Jul 21, 2026Reflection logCapture what changed
Complete the Domain 1 checkpoint simulation
Complete a timed scenario set, grade the decision rationale, and turn misses into an if-requirement-then-pattern error log.
Reflection logCapture what changed
Consider: Which three decision cues would have prevented the missed answers?
Learn identity, cryptography, and resilient-system patterns
Choose among workforce, workload, federated, and customer identity; then connect key, secret, certificate, and recovery choices to requirements.
Choosing an AWS Identity Service
Assigned: Review the identity foundations and selection tables.
Why it matters: Differentiate workforce, workload, federated, and application identities.
Bring back: Choose identity patterns for employee, workload, and external customer principals.
Link checked Jul 21, 2026