Learning path
Data Solutions Architect learning path: everything to study, topic by topic
Comprehensive Data Solutions Architect assessment covering data modeling, pipeline architecture, storage and compute, data governance, real-time streaming, and data strategy.
Short answer
To learn Data Solutions Architect, work through 6 modules and 44 topics in the order they build on each other. It starts with Data Modeling, then moves on to Pipeline Architecture and Storage & Compute. Use the map as a checklist, or measure your level and study only what is missing.
What you will study
Topics are grouped by module. Open one to see its objectives and key concepts.
1 · Data Modeling4 topics
Dimensional Modeling
Star schema, snowflake schema, fact and dimension tables, grain definition, and Kimball methodology
Objectives
- Design dimensional models with correct grain definition
- Choose between star and snowflake schemas based on query patterns
Key concepts
- star schema
- snowflake schema
- fact tables
- dimension tables
- grain definition
- Kimball methodology
- conformed dimensions
Normalization Patterns
Normal forms (1NF-3NF, BCNF), denormalization strategies, and normalization vs performance trade-offs
Objectives
- Apply normal forms to relational data models
- Decide when denormalization is justified for performance
Key concepts
- 1NF
- 2NF
- 3NF
- BCNF
- denormalization
- functional dependencies
- transitive dependencies
Schema Design
Schema evolution, backward/forward compatibility, schema-on-read vs schema-on-write, and NoSQL schema patterns
Objectives
- Design schemas that evolve safely across producers and consumers
- Choose between schema-on-read and schema-on-write for different use cases
Key concepts
- schema evolution
- backward compatibility
- forward compatibility
- schema-on-read
- schema-on-write
- NoSQL patterns
- schema registry
Slowly Changing Dimensions
SCD Types 1-6, hybrid approaches, temporal data modeling, and bitemporal design
Objectives
- Select the appropriate SCD type for given business requirements
- Implement bitemporal data models for audit and compliance
Key concepts
- SCD Type 1
- SCD Type 2
- SCD Type 3
- SCD Type 6
- effective dating
- bitemporal modeling
- surrogate keys
2 · Pipeline Architecture7 topics
ETL/ELT Patterns
ETL vs ELT architectures, transformation strategies, data validation, and pipeline design patterns
Objectives
- Choose between ETL and ELT based on architecture constraints
- Design data pipeline layers with appropriate transformation staging
Key concepts
- ETL vs ELT
- transformation layers
- staging areas
- data validation
- incremental loading
- full refresh
- medallion architecture
Orchestration Tools
Airflow, Dagster, Prefect, Step Functions — DAG design, scheduling, retry policies, and dependency management
Objectives
- Design DAGs with proper dependency management and failure handling
- Choose orchestration tools based on team and infrastructure constraints
Key concepts
- DAG design
- scheduling strategies
- retry policies
- dependency management
- backfill
- SLA monitoring
- task isolation
Data Contracts
Producer-consumer contracts, schema enforcement, SLA definitions, and breaking change management for data interfaces
Objectives
- Design data contracts that protect downstream consumers
- Implement contract testing in data pipelines
Key concepts
- data contracts
- producer ownership
- consumer SLAs
- schema enforcement
- breaking change policy
- contract testing
- data product interfaces
Idempotent Processing
Designing pipelines that produce consistent results on re-execution: deduplication, upsert patterns, and watermark-based processing
Objectives
- Design idempotent data pipelines that handle re-execution safely
- Implement deduplication strategies for at-least-once delivery
Key concepts
- idempotency
- deduplication
- upsert patterns
- watermarks
- deterministic processing
- checkpoint recovery
- at-least-once delivery
MLOps Pipeline Design
ML pipeline orchestration, feature stores, model registry, model serving infrastructure, monitoring, A/B testing, and data/model versioning for production ML systems
Objectives
- Design end-to-end MLOps pipelines from feature engineering to model serving
- Implement model monitoring and drift detection for production ML systems
Key concepts
- ML pipeline orchestration
- feature stores
- model registry
- model serving
- monitoring
- A/B testing
- data/model versioning
AI/ML Data Infrastructure
Feature stores for ML, training data pipeline design, model serving data needs, embedding pipelines, and data versioning for reproducibility
Objectives
- Design feature store architectures supporting both online and offline ML workloads
- Build training data pipelines with versioning and reproducibility guarantees
Key concepts
- feature stores
- training data pipelines
- model serving data
- embedding pipelines
- data versioning
- online/offline feature serving
- feature freshness
Data Platform Migration
Legacy to modern platform migration, zero-downtime migration strategies, dual-write patterns, data validation during migration, and rollback planning
Objectives
- Design zero-downtime migration strategies for production data platforms
- Implement dual-write patterns with validation and reconciliation
Key concepts
- zero-downtime migration
- dual-write patterns
- data validation
- rollback planning
- strangler fig pattern
- migration waves
- reconciliation
3 · Storage & Compute6 topics
Lakehouse Architecture
Lakehouse design combining data lake flexibility with warehouse reliability: Delta Lake, Iceberg, Hudi, and medallion architecture
Objectives
- Design lakehouse architectures with appropriate table format selection
- Implement medallion architecture with quality gates between layers
Key concepts
- lakehouse
- Delta Lake
- Apache Iceberg
- Apache Hudi
- medallion architecture
- ACID on object storage
- time travel
Warehouse Design
Cloud warehouse architecture: Snowflake, BigQuery, Redshift design patterns, workload management, and query optimization
Objectives
- Design warehouse architectures optimized for different query patterns
- Implement workload management for mixed analytical workloads
Key concepts
- virtual warehouses
- workload management
- clustering keys
- materialization strategies
- query optimization
- compute-storage separation
- concurrency scaling
Partitioning Strategies
Table partitioning, data layout optimization, partition pruning, and bucketing for query performance
Objectives
- Design partitioning strategies that optimize query performance
- Diagnose and resolve data skew and small file problems
Key concepts
- range partitioning
- hash partitioning
- list partitioning
- partition pruning
- bucketing
- Z-ordering
- data skew
- small file problem
File Format Selection
Parquet, ORC, Avro, JSON, CSV — choosing formats based on read/write patterns, compression, and schema evolution needs
Objectives
- Select optimal file formats based on access patterns and schema requirements
- Configure compression and encoding for cost and performance optimization
Key concepts
- Parquet
- ORC
- Avro
- columnar vs row-based
- compression codecs
- predicate pushdown
- schema evolution
- nested data
Open Table Formats
Apache Iceberg, Delta Lake, and Apache Hudi — table format comparison, schema evolution, time travel, partition evolution, and interoperability across engines
Objectives
- Compare open table formats and select the right one for specific workload patterns
- Design partition evolution strategies that avoid costly data rewrites
Key concepts
- Apache Iceberg
- Delta Lake
- Apache Hudi
- table format comparison
- schema evolution
- time travel
- partition evolution
Emerging Data Technologies
Vector databases for AI workloads, graph analytics platforms, serverless data processing, real-time OLAP engines, and evaluating emerging data technologies
Objectives
- Evaluate emerging data technologies against established solutions for specific use cases
- Design proof-of-concept evaluations for vector databases and graph analytics
Key concepts
- vector databases
- graph analytics
- serverless data processing
- real-time OLAP
- technology evaluation
- adoption risk assessment
- proof of concept design
4 · Data Governance & Quality8 topics
Data Lineage
Column-level lineage tracking, impact analysis, lineage visualization, and automated lineage extraction from SQL and code
Objectives
- Implement automated lineage tracking across data pipelines
- Use lineage for impact analysis and debugging
Key concepts
- column-level lineage
- table-level lineage
- impact analysis
- lineage graphs
- automated extraction
- OpenLineage
- lineage metadata
Data Cataloging
Metadata management, data discovery, business glossary, and catalog governance for large-scale data platforms
Objectives
- Design a data catalog strategy for enterprise data discovery
- Implement metadata governance with stewardship models
Key concepts
- metadata management
- data discovery
- business glossary
- technical metadata
- usage statistics
- data stewardship
- tag governance
Data Quality Frameworks
Data quality dimensions, automated testing, Great Expectations, dbt tests, and quality SLAs for data products
Objectives
- Design data quality frameworks with automated testing and alerting
- Define and enforce data quality SLAs for data products
Key concepts
- completeness
- accuracy
- consistency
- timeliness
- Great Expectations
- dbt tests
- data quality SLAs
- anomaly detection
PII Handling
PII detection, tokenization, masking, anonymization, GDPR right-to-be-forgotten, and privacy-preserving analytics
Objectives
- Design PII handling architectures that satisfy GDPR and CCPA requirements
- Implement tokenization and masking without breaking analytical workflows
Key concepts
- PII detection
- tokenization
- data masking
- k-anonymity
- differential privacy
- GDPR right to erasure
- consent management
- data classification
Data Contracts & Schema Evolution
Implementing data contracts between producers and consumers with schema versioning and backward/forward compatibility
Objectives
- Design data contracts with schema versioning and compatibility guarantees
- Implement Schema Registry integration for Avro or Protobuf with backward compatibility
Key concepts
- data contracts
- Schema Registry
- backward/forward compat
- Avro/Protobuf evolution
- breaking changes
- producer-consumer agreements
- SLA enforcement
Data Observability Architecture
Building end-to-end data observability: freshness, volume, schema, distribution monitoring, and incident response
Objectives
- Design a data observability system covering the five pillars with lineage-aware alerting
- Implement incident classification and escalation workflows for data quality failures
Key concepts
- data observability pillars
- freshness
- volume anomalies
- distribution monitoring
- lineage-aware alerts
- Monte Carlo
- incident classification
Data Platform Security Architecture
Encryption at rest and in transit, tokenization strategies, data classification frameworks, access control models, and security architecture for data platforms
Objectives
- Design end-to-end security architectures for enterprise data platforms
- Implement data classification frameworks with appropriate access control models
Key concepts
- encryption at rest
- encryption in transit
- tokenization
- data classification
- RBAC/ABAC
- column-level security
- data masking policies
Data SLA & Reliability Engineering
Data SLOs and SLAs, incident management for data systems, on-call for data platforms, error budgets, and reliability patterns for data pipelines
Objectives
- Define data SLOs and SLAs with measurable freshness, completeness, and accuracy targets
- Build incident management processes adapted for data platform failures
Key concepts
- data SLOs
- data SLAs
- incident management
- error budgets
- on-call for data
- reliability patterns
- chaos engineering for data
5 · Real-Time & Streaming6 topics
Kafka/Kinesis Patterns
Topic design, partitioning strategies, consumer groups, retention policies, and operational patterns for event streaming
Objectives
- Design Kafka topic architectures with appropriate partitioning and retention
- Manage consumer groups for reliable, scalable event processing
Key concepts
- topic design
- partition key selection
- consumer groups
- retention policies
- replication factor
- ISR
- compacted topics
- dead letter topics
Stream Processing
Flink, Spark Structured Streaming, ksqlDB — windowing, watermarks, state management, and late data handling
Objectives
- Design stream processing applications with correct windowing and late data handling
- Choose between stream processing frameworks based on requirements
Key concepts
- windowing
- watermarks
- state management
- late data handling
- event time vs processing time
- checkpointing
- backpressure
Change Data Capture
Debezium, DMS, log-based CDC, trigger-based CDC, and CDC integration with streaming platforms
Objectives
- Implement CDC pipelines for real-time data synchronization
- Handle schema evolution and initial snapshots in CDC systems
Key concepts
- Debezium
- log-based CDC
- trigger-based CDC
- outbox pattern
- CDC to Kafka
- schema evolution in CDC
- initial snapshot
Materialized Views
Stream-table duality, incremental materialization, serving layer design, and real-time aggregation patterns
Objectives
- Design materialized view strategies for real-time analytics
- Balance freshness, cost, and query performance in materialization
Key concepts
- stream-table duality
- incremental materialization
- serving layer
- real-time aggregations
- CQRS
- pre-computed views
- refresh strategies
Exactly-Once Semantics
Achieving exactly-once processing in distributed streaming: transactional producers, idempotent consumers, and end-to-end guarantees
Objectives
- Implement end-to-end exactly-once semantics in streaming architectures
- Evaluate trade-offs between exactly-once and at-least-once delivery
Key concepts
- exactly-once semantics
- transactional producers
- idempotent consumers
- two-phase commit
- fencing tokens
- kafka transactions
- end-to-end guarantees
Real-Time Data Architecture
Streaming-first architecture design, Kappa vs Lambda architecture, event-driven analytics, real-time decisioning systems, and low-latency data serving
Objectives
- Design streaming-first architectures with appropriate pattern selection (Kappa vs Lambda)
- Build real-time decisioning systems with sub-second latency requirements
Key concepts
- streaming-first architecture
- Kappa architecture
- Lambda architecture
- event-driven analytics
- real-time decisioning
- low-latency serving
- event sourcing
6 · Data Strategy13 topics
Data Mesh
Domain ownership, data as a product, self-serve data platform, and federated computational governance
Objectives
- Design data mesh architectures with appropriate domain boundaries
- Evaluate when data mesh is appropriate vs centralized data platforms
Key concepts
- domain ownership
- data as a product
- self-serve platform
- federated governance
- data product thinking
- domain boundaries
- interoperability
Data Products
Data product design, APIs and interfaces, discoverability, SLAs, and lifecycle management for data-as-a-product
Objectives
- Design data products with clear interfaces and quality guarantees
- Implement data product lifecycle management
Key concepts
- data product canvas
- product SLAs
- discoverability
- self-describing data
- versioning
- lifecycle management
- consumption patterns
Cost Modeling
Data platform cost optimization: storage tiering, compute right-sizing, query cost attribution, and FinOps for data
Objectives
- Design cost-optimized data architectures with appropriate storage tiering
- Implement cost attribution models for shared data platforms
Key concepts
- storage tiering
- compute right-sizing
- query cost attribution
- chargeback models
- data lifecycle policies
- cost per query
- FinOps for data
Vendor Evaluation
Evaluating data platform vendors: Snowflake vs Databricks vs BigQuery, build vs buy, and total cost of ownership analysis
Objectives
- Conduct structured vendor evaluations with TCO analysis
- Design proof-of-concept tests for data platform selection
Key concepts
- vendor evaluation matrix
- total cost of ownership
- build vs buy
- proof of concept design
- migration risk
- vendor lock-in
- reference architecture
Organizational Maturity
Data maturity models, organizational readiness assessment, center of excellence design, and data literacy programs
Objectives
- Assess organizational data maturity and design improvement roadmaps
- Build data centers of excellence that scale with the organization
Key concepts
- data maturity model
- organizational readiness
- center of excellence
- data literacy
- change management
- skills assessment
- operating model design
AI Architecture for Data Platforms
LLM integration in the data stack, embedding pipelines, vector databases, RAG for analytics, and AI-assisted data quality for modern data platforms
Objectives
- Design AI-augmented data platform architectures with LLM and vector database integration
- Implement RAG patterns for analytics and data discovery use cases
Key concepts
- LLM integration in data stack
- embedding pipelines
- vector databases
- RAG for analytics
- AI-assisted data quality
Enterprise Data Platform Design
Designing enterprise-scale data platforms: ingestion, storage tiers, compute, governance, and consumption layers
Objectives
- Design a multi-layered enterprise data platform with appropriate storage tiers and compute
- Define platform topology including ingestion, transformation, and consumption layers
Key concepts
- data platform layers
- medallion architecture
- hot/warm/cold storage
- data zones
- semantic layer
- platform topology
- operational metadata
Cloud Data Warehouse Selection at Scale
Evaluating and selecting cloud data warehouses at scale: Snowflake vs BigQuery vs Redshift, cost models, and migration strategies
Objectives
- Evaluate Snowflake, BigQuery, and Redshift trade-offs across cost, performance, and ecosystem
- Design a migration strategy from an on-premises or legacy warehouse to a cloud data warehouse
Key concepts
- Snowflake
- BigQuery
- Redshift
- cost per query
- concurrency scaling
- separation of compute/storage
- migration strategy
AI/ML Platform Architecture
Designing end-to-end ML platform architecture: data pipelines, feature stores, training, serving, monitoring, and governance
Objectives
- Design an end-to-end ML platform integrating data, feature store, training, and serving layers
- Implement model monitoring and governance for production ML systems
Key concepts
- ML platform layers
- feature store
- experiment tracking
- model registry
- serving infrastructure
- model monitoring
- governance framework
Data Platform Total Cost of Ownership
TCO modeling for data platforms, build vs buy decision frameworks, vendor comparison methodologies, hidden cost identification, and long-term cost projection
Objectives
- Build comprehensive TCO models that capture hidden and indirect costs of data platforms
- Apply structured build vs buy frameworks for data platform decisions
Key concepts
- TCO modeling
- build vs buy frameworks
- vendor comparison matrix
- hidden costs
- long-term cost projection
- opportunity cost
- total value of ownership
Multi-Cloud Data Strategy
Data portability across cloud providers, avoiding vendor lock-in, cross-cloud replication, multi-cloud data architectures, and abstraction layer design
Objectives
- Design multi-cloud data strategies that minimize lock-in while managing complexity
- Implement data portability patterns with cross-cloud replication and open formats
Key concepts
- data portability
- vendor lock-in avoidance
- cross-cloud replication
- abstraction layers
- multi-cloud governance
- egress cost management
- cloud-agnostic formats
Federated Data Architecture
Data mesh implementation patterns, domain ownership models, federated governance, data product interoperability, and organizational design for federation
Objectives
- Implement data mesh architectures with practical domain ownership and governance
- Design federated governance frameworks that balance autonomy with interoperability
Key concepts
- data mesh implementation
- domain ownership
- federated governance
- data product interop
- self-serve platform
- computational governance
- federated catalog
Data Platform Developer Experience
Self-service tooling for data teams, SDK design, data platform as product, developer portals, and internal platform adoption strategies
Objectives
- Design self-service data platform experiences with SDKs and golden paths
- Apply platform-as-product principles to drive internal adoption of data tools
Key concepts
- self-service tooling
- SDK design
- platform as product
- developer portals
- golden paths
- platform adoption
- developer onboarding
Levels: Junior, Mid, Senior, and Expert
Explain it in your own words
Graded by AI · no account · 1 questionNo options to guess from: you write, the AI grades against the topic's rubric and tells you what level your answer reads at.
Already studying Data 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 Data Solutions Architect?
Start with Data Modeling: Dimensional Modeling, Normalization Patterns, and Schema Design. The map orders topics by what they depend on, so each one prepares the next.
How long does a full Data 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.