Hello again. In the previous lesson, you separated the work of information architects, cloud architects, data engineers, and governance specialists. That role map matters for certification planning: AZ-900 and DP-900 do not test whether you hold a particular job title. They test whether you can describe concepts, recognize appropriate services, and make basic distinctions that those roles use.
This lesson creates a practical crosswalk between the work you will produce in this course and the two Microsoft fundamentals exams:
- AZ-900: Microsoft Azure Fundamentals — broad cloud, Azure architecture, security, governance, and management knowledge.
- DP-900: Microsoft Azure Data Fundamentals — data concepts, Azure data stores, relational and non-relational data, and analytics knowledge.
The goal is not to turn every portfolio artifact into an exam answer. Instead, you will use the course plan to identify what each artifact proves, what it helps you revise, and where you will need focused certification study beyond the portfolio.
Certification blueprints are coverage maps, not career definitions
A certification study guide is a blueprint: Microsoft’s published statement of the knowledge areas an exam can assess. It is not a job description, and passing an exam does not by itself demonstrate that someone has designed or operated an enterprise-scale system.
That distinction is useful for a career transition:
- Certification preparation gives you a structured vocabulary and validates foundational knowledge.
- Portfolio work shows that you can apply that knowledge to a realistic business problem.
- Entry-level job readiness comes from connecting the two clearly and honestly.
For example, an Azure architecture diagram can support AZ-900 preparation because it may show regions, resource groups, storage, identity boundaries, tags, and governance controls. But a diagram alone does not prove that you understand the difference between a virtual machine, a container, and a function. You still need to be able to explain those choices in plain language.
Microsoft’s official AZ-900 guide divides the exam into three broad domains:
| AZ-900 domain | Approximate weighting in the supplied guide | Central question |
|---|---|---|
| Cloud concepts | 25–30% | What is cloud computing, and what are its service and deployment models? |
| Azure architecture and services | 35–40% | Which Azure components and services provide compute, networking, storage, identity, and security? |
| Azure management and governance | 30–35% | How are Azure resources governed, costed, deployed, monitored, and managed? |
The wording “describe” appears repeatedly in the official objectives. At this level, you should be able to recognize a scenario, select or distinguish the relevant concept, and explain the reason for a basic choice. You are not expected to be a senior Azure administrator.
Study guide for Exam AZ-900: Microsoft Azure Fundamentals
Read Microsoft Learn’s official AZ-900 study guide as the source of truth for the exam blueprint. Focus on the headings and individual skills, not on trying to memorize service names on this first pass.
In the “Skills measured as of July 20, 2026” section, first scan “Skills at a glance” to see the three weighted domains. Then read the cloud concepts objectives in “Describe cloud concepts.” In “Describe Azure architecture and services,” read the core architecture objectives, followed by the service and security objectives. Finally, in “Describe Azure management and governance,” read the management and governance objectives. As you read, notice which items this course addresses directly and which will require separate, targeted revision.
A useful three-label system
When mapping course evidence to a certification objective, avoid writing simply “covered.” Use one of these labels instead:
| Label | Meaning | Example |
|---|---|---|
| Direct | A planned lesson or artifact explicitly teaches and applies the objective. | A resource hierarchy diagram directly supports AZ-900 management groups, subscriptions, resource groups, and resources. |
| Supporting | The artifact reinforces the objective but does not fully teach or demonstrate it. | A target-state architecture may include a virtual network, but does not necessarily teach AZ-900 networking concepts in full. |
| Gap | The planned course does not provide enough coverage; add focused certification study. | A certification objective about Power BI visualizations needs additional revision if the portfolio does not include a Power BI artifact. |
This system prevents two unhelpful extremes: understating the value of practical work, or claiming that a single diagram provides complete exam preparation.
DP-900: the data-centered map
DP-900 is narrower than AZ-900 in one sense—it is centered on data workloads—but it goes deeper into data representation, relational concepts, data storage, and analytics.
The supplied official guide groups DP-900 content into four domains:
| DP-900 domain | Approximate weighting in the supplied guide | Central question |
|---|---|---|
| Core data concepts | 25–30% | How is data represented, stored, and used in transactional or analytical workloads? |
| Relational data on Azure | 20–25% | How do relational databases, SQL, normalization, and Azure relational services work? |
| Non-relational data on Azure | 15–20% | When are Azure Storage and Azure Cosmos DB appropriate? |
| Analytics workloads on Azure | 25–30% | How is data ingested, processed, analyzed, and visualized at scale? |
This course begins with the business meaning of information, then builds toward Azure storage, relational databases, integration pipelines, data quality, governance, and analytics architecture. That sequence is broader than DP-900 because enterprise information work also involves ownership, retention, privacy, architecture principles, and AI governance. Still, much of it gives you strong DP-900 preparation.
Study guide for Exam DP-900: Microsoft Azure Data Fundamentals
Read Microsoft Learn’s official DP-900 study guide to establish the data-certification checklist for the rest of the course. Pay particular attention to the difference between data concepts, storage choices, and analytics workloads.
In the “Skills measured as of July 21, 2026” section, begin with “Skills at a glance.” In “Describe core data concepts,” read the representation, storage, workload, and role objectives. Next, in “Identify considerations for relational data on Azure,” read the relational objectives. In “Describe considerations for working with non-relational data on Azure,” read the storage and Cosmos DB objectives. Finish with the analytics objectives in “Describe an analytics workload on Azure.” Mark any terms that are new; later modules will turn many of them into concrete decisions and artifacts.
What the two certifications overlap—and do not overlap—on
Both exams are foundational, but they organize knowledge differently.
| Topic | AZ-900 emphasis | DP-900 emphasis |
|---|---|---|
| Cloud service models | Direct: public, private, hybrid, IaaS, PaaS, SaaS, serverless | Background context only |
| Azure governance | Direct: tags, Policy, resource locks, Purview, cost management | Relevant to responsible data work, but not a major DP-900 domain |
| Identity and security | Direct: Microsoft Entra, authentication, RBAC, Zero Trust, Defender for Cloud | Important context, but not a central DP-900 objective area |
| Structured and semi-structured data | Indirect through Azure services | Direct: core data concept |
| SQL and normalization | Not a principal AZ-900 focus | Direct: relational data |
| Blob Storage and Cosmos DB | Azure Storage appears as an Azure service | Direct: non-relational data decisions |
| Data ingestion and analytics | Broad Azure-service awareness | Direct: batch, streaming, analytical stores, Fabric, and Power BI |
A sensible sequence for this course is therefore:
- Build a broad cloud and governance foundation through the early and Azure-focused modules.
- Develop data fluency through modeling, SQL, storage, integration, and analytics modules.
- Use the capstone to connect both perspectives in one explainable architecture.
You do not need to decide now which exam to take first. The mapping simply ensures that every hour of portfolio work also has a clear learning value for certification preparation.
The planned course-to-certification crosswalk
The following table maps major planned artifacts in this course to the official exam areas. It is deliberately conservative: a Direct label means the course has a stated outcome that closely fits the objective; it does not mean no additional review will ever be needed.
| Planned course evidence | AZ-900 connection | DP-900 connection | Mapping status |
|---|---|---|---|
| Data, information, metadata, and knowledge examples; structured, semi-structured, and unstructured classification | Supports understanding of why different Azure services exist | Structured, semi-structured, and unstructured data are direct DP-900 concepts | DP-900 Direct |
| Business record lifecycle and stakeholder map | Supports governance context and responsible information management | Supports data-workload roles, though DP-900 specifically emphasizes database administrators, engineers, and analysts | Supporting |
| Information requirements brief with KPIs, source data, quality expectations, access needs, and timeliness | Helps interpret cloud and data-service scenarios | Helps distinguish transactional reporting needs from analytical needs | Supporting |
| System context diagram and information-flow diagram | Supports Azure architectural thinking and communication | Supports understanding of sources, destinations, and ingestion | Supporting |
| Entity-relationship diagram, primary and foreign keys, normalized design, and SQL queries | Limited AZ-900 relevance | Relational concepts, normalization, common SQL statements, and database objects | DP-900 Direct |
| Subject-area map, conceptual architecture, principles, and target-state information architecture | Supports Azure solution design, governance, and resource organization choices | Supports analytical architecture and information-flow reasoning | Supporting |
| Purview glossary terms, cataloged assets, classifications, ownership, quality rules, RACI, and escalation process | Microsoft Purview is a direct AZ-900 governance objective; the course goes beyond exam-level detail | Helpful professional context, but not a major DP-900 domain | AZ-900 Direct |
| Privacy classification, Microsoft Entra access design, Azure roles, Key Vault choices, retention rules, and risk register | Identity, authentication, authorization, RBAC, security, and governance are direct AZ-900 content | Background context for protected data workloads | AZ-900 Direct |
| Cloud deployment and service-model decisions; shared responsibility; region, availability-zone, and hierarchy diagram | Direct coverage of cloud models, shared responsibility, service types, regions, subscriptions, resource groups, and management groups | Provides cloud context for data services | AZ-900 Direct |
| Cost drivers, tags, Azure Policy, and resource-lock selections | Direct coverage of Azure cost management and governance tools | Not a principal DP-900 area | AZ-900 Direct |
| Azure storage decision matrix; data lake zones; relational and Cosmos DB service selections; storage-account practice | Azure Storage, tiers, redundancy, and storage-account concepts | Azure Storage, relational services, and Cosmos DB are direct DP-900 content | Both Direct |
| Data pipeline diagram; batch, streaming, API, and file-transfer decisions; Azure Data Factory pipeline; workflow automation | Supports awareness of Azure services and serverless-style automation patterns | Ingestion, processing, and batch versus streaming are direct DP-900 analytics concepts | DP-900 Direct; AZ-900 Supporting |
| Data-quality scorecard, master-data design, remediation workflow, and Purview lineage interpretation | Supports governance and Purview understanding | Extends beyond the named DP-900 objectives, while reinforcing data-management reasoning | Supporting |
| Grounded AI architecture, AI risk assessment, and AI controls | Useful portfolio evidence for modern information architecture, but not central to either blueprint | Useful data-governance context, but not central to the blueprint | Outside both exams |
| Final target-state Azure architecture and governance pack | Integrates architecture, security, governance, cost, and management concepts | Integrates storage, analytical architecture, ingestion, and data-service choices | Integration evidence |
Two important conclusions follow from this crosswalk.
First, the course gives especially strong planned evidence for:
- AZ-900 governance, identity, security, cloud structure, storage, and cost controls
- DP-900 data concepts, SQL and relational design, Azure data stores, and data ingestion
Second, there are a few certification topics that should be treated as planned study gaps, rather than silently assumed to be covered.
| Certification area needing focused revision | Why it is a gap or only supporting coverage |
|---|---|
| AZ-900 compute choices: virtual machines, containers, web apps, scale sets, and functions | The course uses cloud architecture decisions, but does not devote a full outcome to comparing every AZ-900 compute option. |
| AZ-900 networking: virtual networks, subnets, DNS, peering, VPN Gateway, ExpressRoute, and endpoints | Security boundaries appear in architecture work, but detailed networking vocabulary needs dedicated revision. |
| AZ-900 deployment and monitoring tools: Cloud Shell, CLI, PowerShell, ARM, infrastructure as code, Azure Advisor, Service Health, and Azure Monitor | These are useful cloud-foundation topics but are not the main focus of the portfolio plan. |
| DP-900 Power BI capabilities, data models, and visualizations | The course emphasizes information architecture and Azure data services rather than a dedicated Power BI build. |
| DP-900 database administrator and data analyst responsibilities | You have a direct lesson on data-engineer and architecture/governance roles, but should separately review the specific responsibilities named in the DP-900 guide. |
A gap is not a problem. It is a useful instruction: when certification time arrives, you will know exactly where focused revision adds value.
Turn artifacts into a certification evidence tracker
A portfolio artifact becomes more valuable when you can state both its professional purpose and its certification connection. Maintain a simple tracker as the course progresses.
| Field | What to record |
|---|---|
| Artifact | The file, diagram, configuration, query set, or written decision you created |
| Business purpose | The problem it addresses |
| Certification objective | The relevant AZ-900 or DP-900 topic in your own words |
| Evidence statement | What the artifact demonstrates that you can explain |
| Mapping label | Direct, Supporting, or Gap |
| Next revision action | A short topic or service comparison to study later |
Here are three examples drawn from planned work later in the course.
| Artifact | Evidence statement | Certification connection | Label |
|---|---|---|---|
| Azure resource hierarchy diagram | “I organized resources into management groups, subscriptions, resource groups, and individual resources, explaining the purpose of each level.” | AZ-900 core Azure architecture | Direct |
| SQL and relational-model mini-project | “I identified entities, assigned keys, normalized a simple design, and queried related tables using joins and aggregates.” | DP-900 relational concepts and common SQL statements | Direct |
| Customer-service target architecture | “I selected governed Azure storage and analytical services based on data structure, refresh frequency, access requirements, and cost constraints.” | DP-900 data stores and analytics; AZ-900 storage and governance | Direct for selected services; Supporting for broader Azure service coverage |
Notice the wording. It makes a claim that is specific enough to discuss in an interview, without overstating the level of experience. For example, it is more credible to say, “I created a guided Data Factory pipeline and documented its controls,” than “I am an enterprise data-integration expert.”
Keep the official guides version-aware
Certification blueprints change. The supplied guides explicitly include an update date and explain that objectives may be revised. When you decide to schedule an exam, revisit the official study guide and compare its current skills list against your tracker.
A practical final review sequence is:
- Review every official objective and mark it Direct, Supporting, or Gap.
- Use portfolio artifacts to explain Direct objectives aloud without reading notes.
- Study Gap objectives by service category, rather than trying to memorize isolated definitions.
- Practice scenario questions that ask for the most appropriate model, service, control, or workload type.
- Update portfolio descriptions so they accurately reflect what you built and what you can explain.
This approach keeps certification study connected to meaningful work rather than becoming a disconnected list of product names.
Key takeaways
AZ-900 and DP-900 are complementary foundations:
- AZ-900 covers broad cloud concepts, Azure architecture and services, identity and security, governance, cost, deployment, and monitoring.
- DP-900 focuses on data types, data workloads, relational and non-relational Azure services, ingestion, analytics, and Power BI awareness.
- Your course portfolio will provide direct evidence for many objectives, particularly Azure governance, storage, relational design, SQL, data ingestion, and analytics architecture.
- Some areas—especially Azure networking, detailed compute options, deployment and monitoring tools, and Power BI—need targeted supplementary study when preparing for the exams.
- A certification evidence tracker helps you connect each artifact to a credible skill statement rather than claiming broad expertise without proof.
Next, you will identify which planned artifacts are strongest for an entry-level résumé and for interview examples, turning this certification crosswalk into a practical career-evidence plan.