Skip to main content

Learning path

Solutions Architect learning path: everything to study, topic by topic

Comprehensive Solutions Architect assessment covering requirements analysis, integration architecture, security design, scalability, cloud patterns, and enterprise architecture.

Short answer

To learn Solutions Architect, work through 6 modules and 34 topics in the order they build on each other. It starts with Requirements Analysis, then moves on to Integration Architecture and Security Architecture. Use the map as a checklist, or measure your level and study only what is missing.

6
modules
34
topics
60
min to assess

What you will study

Topics are grouped by module. Open one to see its objectives and key concepts.

1 · Requirements Analysis5 topics
  • Functional Requirements

    Eliciting, documenting, and validating functional requirements using use cases, user stories, and acceptance criteria

    Objectives

    • Translate business needs into structured functional requirements
    • Prioritize requirements using MoSCoW or weighted scoring

    Key concepts

    • use cases
    • user stories
    • acceptance criteria
    • requirements traceability
    • MoSCoW prioritization
    • business rules
  • Non-Functional Requirements

    Defining quality attributes: performance, availability, reliability, maintainability, and security constraints

    Objectives

    • Define measurable NFRs with clear acceptance criteria
    • Identify trade-offs between competing quality attributes

    Key concepts

    • SLA/SLO/SLI
    • availability targets
    • latency budgets
    • throughput requirements
    • ISO 25010
    • quality attribute scenarios
  • Constraints & Assumptions

    Identifying technical, business, regulatory, and organizational constraints that shape architecture decisions

    Objectives

    • Document constraints and assumptions explicitly
    • Assess impact of constraints on architecture decisions

    Key concepts

    • technical constraints
    • budget constraints
    • regulatory constraints
    • legacy system constraints
    • assumption documentation
    • risk registry
  • Stakeholder Mapping

    Identifying stakeholders, understanding their concerns, and mapping influence and interest to drive architecture communication strategies

    Objectives

    • Create stakeholder maps and communication plans
    • Tailor architecture documentation to different audiences

    Key concepts

    • stakeholder matrix
    • RACI charts
    • power/interest grid
    • viewpoint modeling
    • architecture communication
    • stakeholder concerns
  • Architecture Documentation

    Structured architecture documentation using the C4 model, architecture decision records (ADRs), and diagram tooling for effective communication

    Objectives

    • Create multi-level architecture documentation using the C4 model
    • Write effective ADRs that capture context, decision, and consequences

    Key concepts

    • C4 model
    • Context diagram
    • Container diagram
    • Component diagram
    • Code diagram
    • ADRs
    • architecture decision records
    • diagram tools
2 · Integration Architecture5 topics
  • API Design Patterns

    REST, GraphQL, gRPC design principles, versioning strategies, and API gateway patterns

    Objectives

    • Choose appropriate API style for a given use case
    • Design APIs with proper versioning and error handling

    Key concepts

    • REST principles
    • GraphQL schema design
    • gRPC/protobuf
    • API versioning
    • API gateway
    • rate limiting
    • pagination
    • HATEOAS
  • Event-Driven Integration

    Message queues, event buses, pub/sub patterns, event sourcing, and CQRS for system integration

    Objectives

    • Design event-driven systems with proper ordering and delivery guarantees
    • Implement saga patterns for distributed transactions

    Key concepts

    • pub/sub
    • message queues
    • event sourcing
    • CQRS
    • saga pattern
    • dead letter queues
    • idempotency
    • eventual consistency
  • Data Flow Design

    Designing data movement between systems including ETL, CDC, data replication, and synchronization patterns

    Objectives

    • Design data flow architectures for multi-system environments
    • Choose between batch and streaming integration approaches

    Key concepts

    • data flow diagrams
    • ETL vs ELT
    • change data capture
    • data replication
    • data synchronization
    • batch vs streaming
  • Authentication Patterns

    OAuth 2.0, OIDC, SAML, JWT, API key management, and federated identity patterns

    Objectives

    • Select appropriate authentication flow for different client types
    • Design secure token-based authentication across microservices

    Key concepts

    • OAuth 2.0 flows
    • OIDC
    • SAML
    • JWT
    • API keys
    • mTLS
    • federated identity
    • token refresh
  • Enterprise Integration Patterns

    Applying EIP patterns: content-based routing, aggregators, splitters, correlation IDs, and saga orchestration

    Objectives

    • Apply enterprise integration patterns to design reliable message-based system integrations
    • Implement saga orchestration with compensating transactions for distributed business processes

    Key concepts

    • content-based router
    • aggregator
    • splitter
    • correlation ID
    • saga pattern
    • compensating transactions
    • message channels
3 · Security Architecture4 topics
  • Zero Trust Architecture

    Designing networks and systems with zero trust principles: verify explicitly, least privilege, assume breach

    Objectives

    • Design zero trust network architectures
    • Apply zero trust principles to cloud-native environments

    Key concepts

    • verify explicitly
    • least privilege
    • assume breach
    • micro-segmentation
    • identity-centric security
    • BeyondCorp
    • NIST SP 800-207
  • IAM Design

    Identity and access management architecture: RBAC, ABAC, policy engines, and privilege escalation prevention

    Objectives

    • Design IAM models for multi-tenant environments
    • Implement least-privilege access across cloud services

    Key concepts

    • RBAC
    • ABAC
    • policy engines
    • service accounts
    • least privilege
    • privilege escalation
    • IAM policies
    • cross-account access
  • Encryption Strategies

    Encryption at rest and in transit, key management, HSMs, envelope encryption, and certificate management

    Objectives

    • Design end-to-end encryption architectures
    • Implement automated key rotation and certificate management

    Key concepts

    • TLS/mTLS
    • encryption at rest
    • KMS
    • HSM
    • envelope encryption
    • certificate rotation
    • key hierarchy
    • data classification
  • Compliance Frameworks

    HIPAA, SOC 2, PCI-DSS, GDPR, and FedRAMP compliance architecture and audit readiness

    Objectives

    • Map compliance requirements to architecture controls
    • Design audit-ready systems with automated compliance monitoring

    Key concepts

    • HIPAA
    • SOC 2
    • PCI-DSS
    • GDPR
    • FedRAMP
    • audit trails
    • data residency
    • compliance automation
4 · Scalability & Performance4 topics
  • Capacity Planning

    Forecasting resource needs, sizing infrastructure, and planning for growth with quantitative models

    Objectives

    • Build quantitative capacity models for distributed systems
    • Identify bottlenecks using load testing and performance profiling

    Key concepts

    • throughput modeling
    • resource sizing
    • growth projections
    • headroom planning
    • load testing
    • bottleneck analysis
    • Little's Law
  • Caching Strategies

    Multi-layer caching: CDN, application cache, database cache, cache invalidation patterns, and consistency trade-offs

    Objectives

    • Design multi-layer caching architectures
    • Handle cache invalidation and consistency challenges

    Key concepts

    • CDN caching
    • Redis/Memcached
    • cache-aside
    • write-through
    • write-behind
    • cache invalidation
    • TTL strategies
    • cache stampede
  • Load Balancing

    L4/L7 load balancing, algorithms, health checks, session affinity, global load balancing, and failover strategies

    Objectives

    • Choose appropriate load balancing strategies for different architectures
    • Design failover-aware load balancing with health monitoring

    Key concepts

    • L4 vs L7 load balancing
    • round robin
    • least connections
    • consistent hashing
    • health checks
    • session affinity
    • global server load balancing
  • Database Scaling

    Vertical vs horizontal scaling, read replicas, sharding strategies, connection pooling, and NewSQL approaches

    Objectives

    • Design database scaling strategies for high-throughput systems
    • Evaluate trade-offs between consistency and availability in distributed databases

    Key concepts

    • vertical scaling
    • read replicas
    • sharding
    • connection pooling
    • partitioning
    • NewSQL
    • CAP theorem
    • replication lag
5 · Cloud Architecture Patterns6 topics
  • Multi-Cloud Strategy

    Multi-cloud and hybrid cloud design, portability patterns, vendor lock-in mitigation, and cross-cloud networking

    Objectives

    • Design multi-cloud architectures with appropriate abstraction layers
    • Evaluate vendor lock-in trade-offs against operational complexity

    Key concepts

    • multi-cloud networking
    • abstraction layers
    • vendor lock-in mitigation
    • hybrid cloud connectivity
    • cloud-agnostic design
    • data sovereignty
  • Serverless Patterns

    Function-as-a-service architectures, event-driven serverless, cold start mitigation, and serverless anti-patterns

    Objectives

    • Design serverless architectures with proper error handling and observability
    • Identify when serverless is and is not appropriate

    Key concepts

    • FaaS
    • cold starts
    • step functions
    • serverless databases
    • event-driven workflows
    • serverless anti-patterns
    • provisioned concurrency
  • Containerization

    Container orchestration, Kubernetes architecture, service mesh, and container security patterns

    Objectives

    • Design Kubernetes-based architectures for production workloads
    • Implement service mesh for inter-service communication and observability

    Key concepts

    • Docker
    • Kubernetes
    • service mesh
    • sidecar pattern
    • pod design
    • Helm charts
    • container security
    • registry management
  • Infrastructure as Code

    Terraform, CloudFormation, Pulumi patterns, state management, module design, and GitOps workflows

    Objectives

    • Design modular IaC with proper state management and secret handling
    • Implement GitOps workflows for infrastructure deployment

    Key concepts

    • Terraform
    • CloudFormation
    • Pulumi
    • state management
    • module design
    • GitOps
    • drift detection
    • environment promotion
  • Cost Optimization

    FinOps practices, reserved vs on-demand vs spot, right-sizing, cost allocation, and architectural cost trade-offs

    Objectives

    • Design architectures optimized for cost without sacrificing reliability
    • Implement FinOps practices for continuous cost governance

    Key concepts

    • FinOps
    • reserved instances
    • spot instances
    • right-sizing
    • cost allocation tags
    • savings plans
    • cost anomaly detection
    • unit economics
  • AI Architecture Patterns

    Architectural patterns for integrating AI/ML capabilities: LLM integration, RAG pipelines, embedding strategies, AI guardrails, model serving, and prompt engineering at the architecture level

    Objectives

    • Design scalable RAG architectures with appropriate retrieval and generation pipelines
    • Implement AI guardrails and safety patterns at the architecture level

    Key concepts

    • LLM integration design
    • RAG patterns
    • embedding pipelines
    • AI guardrails
    • model serving
    • prompt engineering in architecture
6 · Enterprise Architecture10 topics
  • TOGAF Alignment

    Architecture Development Method (ADM), enterprise continuum, architecture building blocks, and capability mapping

    Objectives

    • Apply TOGAF ADM phases to real architecture initiatives
    • Create architecture building blocks aligned with enterprise continuum

    Key concepts

    • ADM phases
    • architecture building blocks
    • solution building blocks
    • enterprise continuum
    • capability mapping
    • architecture repository
  • Governance Frameworks

    Architecture governance boards, decision records, fitness functions, and compliance monitoring for enterprise systems

    Objectives

    • Establish architecture governance with appropriate lightweight processes
    • Use fitness functions to enforce architectural properties

    Key concepts

    • architecture decision records
    • fitness functions
    • governance boards
    • architectural principles
    • exception process
    • compliance monitoring
  • Technology Radar

    Technology evaluation, adoption lifecycle, build vs buy analysis, and managing technology portfolio risk

    Objectives

    • Build and maintain a technology radar for the organization
    • Make informed build-vs-buy decisions with total cost of ownership analysis

    Key concepts

    • technology radar
    • adopt/trial/assess/hold
    • build vs buy
    • technology portfolio
    • innovation budget
    • technical debt management
  • Migration Strategy

    The 7 Rs of migration, strangler fig pattern, big bang vs phased migration, data migration strategies, and cutover planning

    Objectives

    • Design end-to-end migration strategies for enterprise systems
    • Plan data migration with zero or minimal downtime

    Key concepts

    • 7 Rs of migration
    • strangler fig pattern
    • big bang vs phased
    • data migration
    • cutover planning
    • rollback strategy
    • parallel running
  • Domain-Driven Design

    Strategic and tactical DDD patterns: bounded contexts, aggregates, context mapping, ubiquitous language, domain events, and anti-corruption layers for complex domains

    Objectives

    • Decompose complex domains into bounded contexts with clear ownership boundaries
    • Design context maps to manage inter-context relationships and integration patterns

    Key concepts

    • bounded contexts
    • aggregates
    • context mapping
    • ubiquitous language
    • domain events
    • anti-corruption layer
  • Event Storming

    Collaborative domain discovery workshops using event storming to identify domain events, commands, aggregates, bounded contexts, and process hotspots

    Objectives

    • Facilitate event storming workshops to discover domain complexity
    • Translate event storming outputs into bounded context boundaries and service design

    Key concepts

    • event storming workshops
    • domain event discovery
    • commands
    • aggregates
    • bounded context identification
    • hotspots
  • Architecture Fitness Functions

    Defining and implementing automated architecture fitness functions to objectively measure and enforce architectural characteristics

    Objectives

    • Define quantifiable fitness functions for non-functional architectural characteristics
    • Implement automated fitness function checks in CI/CD pipelines to enforce architectural constraints

    Key concepts

    • fitness functions
    • evolutionary architecture
    • automated governance
    • architectural characteristics
    • ArchUnit
    • chaos experiments
  • Evolutionary Architecture

    Designing systems that safely evolve over time using guided change, incremental migration, and architecture runway

    Objectives

    • Design architecture strategies that accommodate change without big-bang rewrites
    • Apply strangler fig and anti-corruption layer patterns for safe system evolution

    Key concepts

    • guided change
    • incremental migration
    • architecture runway
    • strangler fig
    • feature toggles
    • anti-corruption layers
    • coupling metrics
  • Technical Debt Strategy & Governance

    Systematically measuring, prioritizing, and governing technical debt at organizational scale

    Objectives

    • Measure and categorize technical debt using systematic frameworks and tooling
    • Build the business case for debt reduction and prioritize remediation by ROI and risk

    Key concepts

    • debt quadrants
    • debt registers
    • hotspot analysis
    • refactoring investment ROI
    • SonarQube
    • architectural debt
    • debt velocity
  • Architecture Decision Records at Scale

    Establishing ADR practices across multiple teams: templates, tooling, governance, and architectural knowledge management

    Objectives

    • Establish ADR practices and tooling that scale across multiple engineering teams
    • Design a governance model distinguishing team-level decisions from organizational architecture decisions

    Key concepts

    • ADR structure
    • Nygard format
    • MADR
    • team-level vs org-level ADRs
    • decision logs
    • architecture kanban
    • RFC process

Levels: Junior, Mid, Senior, and Expert

Explain it in your own words

Graded by AI · no account · 1 question

No options to guess from: you write, the AI grades against the topic's rubric and tells you what level your answer reads at.

0 / 600

Already studying Solutions Architect?

The assessment measures topic by topic, and your plan skips what you already know.

Open to read. An account is only needed to be measured.

Frequently asked questions

Where should I start studying Solutions Architect?

Start with Requirements Analysis: Functional Requirements, Non-Functional Requirements, and Constraints & Assumptions. The map orders topics by what they depend on, so each one prepares the next.

How long does a full Solutions Architect assessment take?

A full assessment of this path takes about 60 minutes. Study time depends on where you start; a diagnostic shows which topics you can skip.

Do I need an account to use this page?

No. The map, objectives and key concepts are open. You only need an account to be measured, get your gap by topic and receive a plan.