Study guide

1.3 Skills Outline, Domain Weights & How to Use This Guide

Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Orientation

1.1 AZ-305 Current Exam Facts & Format 1.2 Candidate Profile, Prerequisites & the AZ-104 Requirement 1.3 Skills Outline, Domain Weights & How to Use This Guide

2 Chapter 2: Logging, Monitoring & Diagnostics Design

2.1 Logging Solution Design 2.2 Log Routing Design 2.3 Azure Monitor Metrics & Alerting Design 2.4 Application Insights & Diagnostic Monitoring Design

3 Chapter 3: Authentication & Authorization Design

3.1 Authentication Solution Design 3.2 Identity Management Design 3.3 Authorization for Azure Resources 3.4 Authorization for On-Premises Resources 3.5 Secrets, Certificates & Key Management Design

4 Chapter 4: Governance, Compliance & Identity Governance Design

4.1 Management Group & Subscription Hierarchy Design 4.2 Resource Group Organization & Tagging Strategy Design 4.3 Compliance Management Design 4.4 Identity Governance Design

5 Chapter 5: Relational Data Storage Design

5.1 Relational Data Storage Selection 5.2 Database Service & Compute Tier Design 5.3 Database Scalability Design 5.4 Relational Data Protection Design

6 Chapter 6: Semi-Structured & Unstructured Data Storage Design

6.1 Semi-Structured Data Storage Design 6.2 Unstructured Data Storage Design 6.3 Storage Tier & Cost-Performance Trade-off Design 6.4 Unstructured Data Protection & Durability Design

7 Chapter 7: Data Integration & Analytics Design

7.1 Data Integration Pipeline Design 7.2 Event-Based & Real-Time Data Integration Design 7.3 Data Analytics Platform Design

8 Chapter 8: Backup & Disaster Recovery Design

8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO 8.2 Azure Site Recovery Architecture for Hybrid Workloads 8.3 Compute Backup & Recovery Design 8.4 Database Backup & Recovery Design 8.5 Unstructured Data Backup & Recovery Design

9 Chapter 9: High Availability Design

9.1 Compute High Availability: Availability Sets & Availability Zones 9.2 Compute High Availability: Load Balancing & VM Scale Set Design 9.3 Relational Data High Availability Design 9.4 Semi-Structured & Unstructured Data High Availability Design

10 Chapter 10: Compute Solution Design

10.1 Compute Requirements Analysis & Virtual Machine-Based Solution Design 10.2 Container-Based Solution Design (AKS, Container Apps, Azure Container Instances) 10.3 Serverless-Based Solution Design (Azure Functions, Logic Apps) 10.4 Batch Processing Solution Design (Azure Batch, HPC Workloads)

11 Chapter 11: Application Architecture Design

11.1 Messaging Architecture Design (Service Bus, Queue Storage) 11.2 Event-Driven Architecture Design (Event Grid, Event Hub) 11.3 API Integration & Application Caching Design (API Management, Azure Cache for Redis, CDN) 11.4 Application Configuration Management & Automated Deployment Design (App Configuration, DevOps Pipelines, Deployment Slots)

12 Chapter 12: Migration Design

12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation 12.2 IaaS & PaaS Workload Migration Design 12.3 Database Migration Design (Data Migration Service, Database Migration Assistant) 12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)

13 Chapter 13: Network Solution Design

13.1 Internet Connectivity Design 13.2 Hybrid Connectivity Design 13.3 Network Security Optimization Design 13.4 Network Performance Optimization & Load-Balancing/Routing Design

14 Chapter 14: Final Review, Exam Strategy & Career Path

14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions 14.2 Common AZ-305 Decision Traps 14.3 Final Study Plan & Practice Assessment Strategy 14.4 After AZ-305: Retake Policy, Renewal & Career Path

1.3 Skills Outline, Domain Weights & How to Use This Guide

Key Takeaways Explain This Topic AI

AZ-305 has four domains -- Identity/Governance/Monitoring (25-30%), Data Storage (20-25%), Business Continuity (15-20%), and Infrastructure (30-35%) -- spanning 12 official subgroups.

Domain weights are published as ranges, not fixed numbers; plan around the midpoint but expect some variance by exam form.

Most exam questions test generally available (GA) features; only widely adopted preview features are likely to appear.

This guide's 14 chapters and 56 sections map, with a small number of explicit merges and splits, onto every one of the roughly 49 official testable objectives Microsoft publishes.

Allocate study hours in proportion to domain weight rather than evenly across all four domains, and reserve the final 10-15% of prep time for cross-domain scenario practice.

Last updated: July 2026

Skills Outline, Domain Weights & How to Use This Guide

Quick Answer: AZ-305 measures four co-equal design domains as of the April 17, 2026 exam update — Identity, Governance & Monitoring (25-30%) , Data Storage (20-25%) , Business Continuity (15-20%) , and Infrastructure (30-35%) — spanning 12 official functional subgroups and roughly 49 distinct "Recommend/Evaluate/Specify" testable objectives. This guide maps every one of those 49 objectives to a numbered chapter and section so you can study in blueprint order and track your own coverage precisely.

Why the Domain Weights Should Drive Your Study Plan

Treating all four AZ-305 domains as equally important is one of the most common planning mistakes candidates make. Domain 4 (Infrastructure) alone can account for more than a third of the exam, while Domain 3 (Business Continuity) can be as little as 15%. If you split a 100-hour study plan into four equal 25-hour blocks, you will systematically under-prepare for Infrastructure and over-prepare for Business Continuity relative to how the real exam is actually built. Reading the weight table below as a study-time budget, not just as trivia, is the single highest-leverage adjustment you can make before you open Chapter 2.

The Four Official Domains, In Full

# Domain Official weight Functional subgroups

1 Design identity, governance, and monitoring solutions 25-30% Logging and monitoring; Authentication and authorization; Governance

2 Design data storage solutions 20-25% Relational data; Semi-structured and unstructured data; Data integration

  • 3 Design business continuity solutions 15-20% Backup and disaster recovery; High availability
  • 4 Design infrastructure solutions 30-35% Compute; Application architecture; Migrations; Network

Across those 12 subgroups, Microsoft publishes roughly 49 distinct testable objectives — each phrased as a "Recommend a...", "Evaluate a...", or "Specify a..." bullet. This guide's 14 chapters and 56 sections map onto that full list, with a small number of especially broad objectives split across two sections and a small number of tightly overlapping objectives merged into one, so that every official bullet still traces to exactly one place you can study and check off.

A Note on What "Weight" Actually Means

Microsoft publishes each domain as a range (for example, 25-30%) rather than a single fixed number, because the exact number of questions drawn from each domain varies slightly by the specific exam form a candidate receives. Treat the midpoint of each range as your planning number — about 27.5% for Domain 1, 22.5% for Domain 2, 17.5% for Domain 3, and 32.5% for Domain 4 — while understanding that any single attempt could lean a few points in either direction within that band. Domain 4 (Infrastructure) is the single largest domain, meaning roughly one in three AZ-305 questions touches compute, application architecture, migrations, or networking.

Two more notes come directly from Microsoft's own study guide and matter just as much as the weight table itself. First, the bullets listed under each skill only illustrate how that skill is assessed — related topics not explicitly named in a bullet can still appear on the exam, so treat each objective as a theme rather than an exhaustive checklist. Second, most questions cover generally available (GA) Azure features; preview (non-GA) features only appear if they are already commonly used in the field. Do not spend scarce study time memorizing a brand-new preview-only service unless it has clearly seen wide adoption.

How This Guide Is Organized

  • Chapters Domain Weight Sections
  • 1 Introduction and orientation (this chapter) — 3
  • 2-4 Domain 1: Identity, Governance and Monitoring 25-30% 13
  • 5-7 Domain 2: Data Storage 20-25% 11
  • 8-9 Domain 3: Business Continuity 15-20% 9
  • 10-13 Domain 4: Infrastructure 30-35% 16
  • 14 Final Review, Exam Strategy and Career Path — 4

That is 56 sections across 14 chapters in total. Chapters run in official blueprint order, and each chapter corresponds to one of the 12 official functional subgroups (or, for Chapters 1 and 14, to non-domain orientation and review content that every ExamFinch guide includes).

How to Use This Guide Effectively

Work chapters in numeric order the first time through. They follow blueprint order, and the later Infrastructure chapters assume you already know the identity and governance vocabulary introduced in Chapters 2-4 (for example, managed identities and RBAC scope reappear constantly once you reach compute and networking design).

Budget study time roughly proportional to weight , not evenly across the four domains. Heavier domains — Infrastructure and Identity/Governance/Monitoring — deserve more hours than lighter ones like Business Continuity, but do not skip Business Continuity's 15-20% just because it is the smallest slice; that is still potentially 1 in 5 questions on the exam.

Answer every quiz question in each section before moving on , and re-attempt any section where you miss more than one question. The quizzes are written to mirror the scenario style of the real exam, not to test rote recall.

Treat Chapter 14's "Common Decision Traps" section as a checklist to revisit after finishing all four domain chapters. Many AZ-305 wrong answers come from confusing two superficially similar services — SQL Managed Instance versus Cosmos DB, or LRS versus ZRS versus GRS replication — and that chapter collects the most frequent traps in one place for a final pass.

Pair this guide with hands-on labs. AZ-305 is a design exam, but design intuition is built by having actually deployed the services you are choosing between; reading alone rarely produces reliable trade-off instincts on its own.

A Study-Time Allocation Scenario

A candidate budgeting 100 hours over 10 weeks might split time roughly as: about 28 hours on Chapters 2-4 (Identity, Governance and Monitoring), about 23 hours on Chapters 5-7 (Data Storage), about 18 hours on Chapters 8-9 (Business Continuity), and about 31 hours on Chapters 10-13 (Infrastructure) — reserving the final 10-15% of total time for Chapter 14's cross-domain scenario practice and a full timed practice-question run. This mirrors the exam's own weight distribution rather than splitting time evenly across four domains, which would over-invest in Business Continuity and under-invest in Infrastructure relative to how the real exam is actually built.

Key Takeaways

AZ-305 has four domains — Identity/Governance/Monitoring (25-30%), Data Storage (20-25%), Business Continuity (15-20%), and Infrastructure (30-35%) — spanning 12 official subgroups.

Domain weights are published as ranges, not fixed numbers; plan around the midpoint but expect some variance by exam form.

Most exam questions test generally available (GA) features; only widely adopted preview features are likely to appear.

This guide's 14 chapters and 56 sections map, with a small number of explicit merges and splits, onto every one of the roughly 49 official testable objectives Microsoft publishes.

Allocate study hours in proportion to domain weight rather than evenly across all four domains, and reserve the final 10-15% of prep time for cross-domain scenario practice.