Skip to main content

AWS SAP-C02 Exam Domains Guide (2026)

The AWS Certified Solutions Architect – Professional (SAP‑C02) exam validates advanced architecture skills. AWS organizes the exam into four domains that represent the key phases of enterprise solution design and lifecycle management. Each domain defines a specific set of architecture competencies you must demonstrate—not just recall facts about services.

This guide explains what each domain measures, how the domains interconnect in real projects, and how to approach your study so you develop the mindset of an enterprise architect rather than someone who simply passes a test.

CloudCertPro focuses on architectural understanding. You will not find exam dumps, leaked questions, or memorization shortcuts here. What you will find is a clear roadmap to the skills that make a Professional Solutions Architect.

SAP-C02 Exam Domain Overview​

The table below shows the four official SAP‑C02 domains, their approximate exam weighting, core focus areas, and a recommended study priority based on how fundamental each domain is to building architecture expertise.

DomainWeightFocusRecommended Study Priority
Domain 1: Design Solutions for Organizational Complexity26%Multi‑account governance, landing zones, identity, hybrid networking, migration strategyHigh (foundational; other domains depend on the enterprise context)
Domain 2: Design for New Solutions30%Greenfield architecture: compute, storage, networking, databases, analytics, integration, securityVery High (largest domain; includes core service selection and design patterns)
Domain 3: Continuous Improvement for Existing Solutions26%Operational excellence, observability, cost optimization, resilience improvements, modernizationHigh (tests ability to evolve architectures; builds on Domain 2)
Domain 4: Accelerate Workload Migration and Modernization18%Migration planning, hybrid architectures, VMware, database migration, application refactoringMedium (specialized migration knowledge, but essential for many enterprise engagements)

These percentages reflect the approximate distribution of scored questions on the exam. Study each domain proportionally, but also understand that real‑world architecture requires applying them together, not in isolation.

Domain 1: Design Solutions for Organizational Complexity​

Domain 1 addresses the enterprise foundation. Before you design a single workload, you need a secure, governed, multi‑account environment that aligns with the organization’s operational and compliance requirements.

This domain tests your ability to:

  • Design multi‑account strategies using AWS Organizations, organizational units (OUs), and service control policies (SCPs).
  • Implement landing zones with AWS Control Tower or custom automation.
  • Define identity architectures that span accounts—IAM roles, cross‑account access, and federation with AWS IAM Identity Center (formerly AWS SSO) or third‑party identity providers.
  • Plan network connectivity across accounts and with on‑premises environments using Transit Gateway, Direct Connect, and VPN.
  • Establish governance with AWS Config, CloudTrail, AWS Budgets, and automated remediation.
  • Design migration strategies and portfolios, including assessment, readiness, and the 7 Rs (rehost, replatform, repurchase, refactor, retire, retain, relocate).

Key services and tools: AWS Organizations, Control Tower, IAM, IAM Identity Center, RAM, Transit Gateway, Direct Connect, SCPs, AWS Config, CloudTrail, AWS Migration Hub.

Exam tip: Many candidates skip Domain 1 because it feels abstract, but enterprise‑level governance frequently appears in the case‑study scenarios. You must understand how SCPs, permission boundaries, and account structures interact.

Domain 2: Design for New Solutions​

Domain 2 is the largest domain and the heart of the exam. Here you design new, cloud‑native solutions from scratch, selecting and combining AWS services to meet business and technical requirements. This domain expects you to apply the Well‑Architected Framework across all six pillars.

You will need to:

  • Translate business requirements into technical architectures.
  • Select compute services (EC2, Lambda, ECS/EKS, AWS Outposts, etc.) based on workload characteristics and cost profiles.
  • Design storage solutions using S3, EBS, EFS, FSx, and data lifecycle policies.
  • Architect networking topologies—VPCs, subnets, security groups, NACLs, load balancing, Global Accelerator, CloudFront.
  • Choose database services (RDS, Aurora, DynamoDB, ElastiCache, Redshift) for performance, consistency, and scale.
  • Integrate application components with messaging services (SQS, SNS, EventBridge, Step Functions, AppSync).
  • Design for analytics and big data (Kinesis, Glue, EMR, Athena, QuickSight).
  • Apply security best practices: encryption, IAM, WAF, Shield, Secrets Manager.
  • Enforce resilience with multi‑AZ and multi‑region deployments, backup, and disaster recovery.

Key services and tools: EC2, Lambda, ECS/EKS, S3, EBS, EFS, FSx, VPC, ELB, Route 53, CloudFront, Global Accelerator, RDS, Aurora, DynamoDB, ElastiCache, Redshift, SQS, SNS, EventBridge, Step Functions, Kinesis, Glue, IAM, KMS, WAF, Shield.

Exam tip: Domain 2 questions often combine multiple services in a single scenario. Practice evaluating trade‑offs quickly: “Do I need real‑time analytics or batch processing? Does this workload need relational ACID transactions or key‑value lookups?” The faster you can map requirements to architecture patterns, the better.

Domain 3: Continuous Improvement for Existing Solutions​

Domain 3 shifts from new design to iterative improvement. As a Professional architect, you must assess existing workloads and recommend optimizations that enhance operational excellence, performance, security, reliability, and cost.

You should be able to:

  • Analyze an existing architecture and identify bottlenecks, single points of failure, or security gaps.
  • Improve observability through CloudWatch, X‑Ray, and distributed tracing.
  • Design automated operational responses using EventBridge, Systems Manager, and runbooks.
  • Optimize cost by right‑sizing, using Savings Plans, Spot Instances, and S3 lifecycle policies.
  • Modernize legacy applications to serverless, containerized, or microservices architectures.
  • Increase resilience by introducing multi‑AZ or cross‑region patterns.
  • Evaluate and implement CI/CD pipelines for infrastructure and application deployment.

Key services and tools: CloudWatch, X‑Ray, Systems Manager, EventBridge, AWS Config, Compute Optimizer, Auto Scaling, S3 storage classes, AWS Backup, CodePipeline, CodeBuild, CodeDeploy.

Exam tip: The “improve” scenarios often present a suboptimal architecture and ask you to identify the most impactful change. Always weigh the cost and effort of the improvement against the business value.

Domain 4: Accelerate Workload Migration and Modernization​

Domain 4 focuses on moving workloads to AWS and transforming them once they are there. Enterprise architects lead migration projects, so you need to understand the tools, patterns, and risks involved.

This domain covers:

  • Migration assessment and readiness using AWS Migration Evaluator, Application Discovery Service, and Migration Hub.
  • Hybrid architectures with VMware Cloud on AWS, Outposts, and hybrid DNS.
  • Database migration using AWS Database Migration Service (DMS), Schema Conversion Tool (SCT), and native replication tools.
  • Application migration with AWS Application Migration Service (MGN) and CloudEndure.
  • Data transfer options: Snow Family, DataSync, Transfer Family, and Direct Connect.
  • Modernization patterns: refactoring monoliths to microservices, moving from Windows to Linux, adopting serverless.
  • Post‑migration optimization and licensing considerations.

Key services and tools: Migration Hub, DMS, SCT, MGN, CloudEndure, Snow Family, DataSync, Direct Connect, VMware Cloud on AWS, Outposts, App2Container, Lambda, ECS/EKS.

Exam tip: Domain 4 scenarios often describe a large on‑premises estate. You must decide between rehosting, replatforming, and refactoring based on timeline, budget, and business goals. Know which AWS service handles each migration pattern.

Domain Relationships​

Real‑world architecture projects rarely follow a single domain in isolation. The four SAP‑C02 domains work together as a continuous lifecycle:

  • Start with Domain 1: Build the multi‑account structure, identity, and governance so that new workloads land in a secure, compliant environment.
  • Move to Domain 2: Design the specific solutions that deliver business value, leveraging the foundation from Domain 1.
  • After deployment, Domain 3 kicks in: monitor, optimize, and harden the running systems.
  • When legacy systems need to move to the cloud, or when you decide to re‑platform an existing application, apply Domain 4. These migrations feed back into Domains 2 and 3 as the migrated workloads become part of the ongoing design and improvement cycle.

On the exam, case studies often interweave domains: a question about a migration may also test your knowledge of organizational governance (Domain 1) and post‑migration optimization (Domain 3). Treat the domains as interconnected, not as separate checklists.

Study Strategy​

A strategic study order helps you build foundational knowledge before tackling the most cross‑cutting topics.

  1. Start with Domain 2 – Design for New Solutions. This is the largest and most fundamental domain. Mastering the core services, architecture patterns, and design trade‑offs here will make every other domain easier. Spend the most time here.
  2. Move to Domain 3 – Continuous Improvement. Now that you know how to build new systems, learn to evaluate and improve existing ones. This deepens your understanding of operational excellence and cost optimization.
  3. Study Domain 4 – Accelerate Workload Migration and Modernization. With strong design and operational knowledge, explore the migration tools and patterns. You will recognize many of the target architectures from Domain 2.
  4. Finish with Domain 1 – Design Solutions for Organizational Complexity. This domain makes more sense after you have seen the real‑world architectures from the other domains. Enterprise governance ties everything together; understanding the workloads first helps you see why the controls matter.

This order builds a logical progression: design → improve → migrate → govern. Adjust based on your experience; if you already lead enterprise migrations, start with Domain 4 or 1.

Use these CloudCertPro resources to turn domain knowledge into exam‑ready architecture skills:

Walk through each domain page, study the related services, then practice with scenarios that integrate multiple domains. The exam measures your ability to apply knowledge, not your ability to recite facts.

Understanding where SAP‑C02 fits in the broader AWS certification landscape helps you plan your career path.

CertificationLevelRelationship to SAP‑C02
AWS Solutions Architect – Associate (SAA‑C03)AssociateBuilds the core design skills that SAP‑C02 extends into enterprise‑grade complexity. Not a formal prerequisite, but strongly recommended.
[AWS Certified AI Practitioner] (/aws/aif-c01/)FoundationalBroad AI/ML concepts; useful if your SAP‑C02 work includes AI‑powered solutions.
[AWS Certified Machine Learning Engineer – Associate] (/aws/mla-c01/)AssociateSpecialized ML deployment and pipeline design; complements the data and analytics aspects of SAP‑C02.

SAP‑C02 itself is the Professional architecture credential. Combining it with specialty certifications in security, networking, or data creates a well‑rounded enterprise architect profile.

Key Takeaways​

  • SAP‑C02 is organized into four domains that mirror the lifecycle of an enterprise solution: organizational foundations, new solution design, continuous improvement, and migration/modernization.
  • The domains are interconnected; the exam tests your ability to navigate between them in realistic scenarios.
  • Focus your study on architecture decisions, trade‑offs, and the integration of multiple AWS services—not on memorizing isolated facts.
  • Use CloudCertPro’s domain‑guided path: study the official objectives, dive into services, master architecture patterns, and then apply your knowledge in scenario‑based practice.
  • Professional‑level architecture is about balancing conflicting priorities: security vs. cost, resilience vs. simplicity, speed vs. compliance. That is the skill this domain guide helps you develop.

Start with Domain 2 →