AZ-305
Designing Microsoft Azure Infrastructure Solutions
Designing Microsoft Azure Infrastructure Solutions: AZ-305 Exam Guide
AZ-305 validates whether you can turn business and technical requirements into secure, governed, resilient Azure and hybrid designs. It serves solution architects and experienced Azure professionals who must balance identity, storage, continuity, networking, compute, monitoring, and migration choices across one solution. This guide helps you decide whether your foundation is ready, which skill domains deserve the most study time, whether the official prerequisite is complete, and what to do before scheduling.
What does AZ-305 validate?
AZ-305, Designing Microsoft Azure Infrastructure Solutions, tests architecture decisions rather than isolated product recall. Microsoft describes the target role as an Azure solutions architect who designs cloud and hybrid solutions involving compute, network, storage, monitoring, and security, while translating stakeholder requirements into designs aligned with the Azure Well-Architected Framework and Cloud Adoption Framework for Azure.
The architect role is collaborative. Microsoft identifies developers, administrators, security engineers, and data engineers as partner roles. That means preparation should include the boundaries between disciplines: how an application requirement affects network placement, how identity affects data access, how continuity requirements affect storage architecture, and how governance affects the operational design.
The practical question is not simply whether you have used an Azure service. It is whether you can justify a design under constraints such as availability, security, performance, operational control, migration complexity, and organizational governance. Build that reasoning habit into every study session.
Who should take this exam?
AZ-305 is aimed at candidates with advanced IT-operations knowledge and experience designing Azure solutions. Microsoft specifically expects knowledge of networking, virtualization, identity, security, business continuity, disaster recovery, data platforms, and governance, plus experience with Azure administration, Azure development, and DevOps processes.
The official certification has a formal prerequisite: to earn Microsoft Certified: Azure Solutions Architect Expert, you must earn Microsoft Certified: Azure Administrator Associate. AZ-305 is the required exam for that certification. Treat the prerequisite as a scheduling decision, not as a minor footnote. Passing AZ-305 does not remove the need to earn the prerequisite certification.
You may still study AZ-305 while completing the prerequisite, but first establish which credential you are pursuing. If your immediate goal is architecture competence rather than the expert certification, use the exam objectives as a skills framework while tracking the certification requirement separately.
A strong candidate can explain trade-offs across an entire platform. A candidate who knows individual Azure services but cannot connect identity, network, data, resilience, and operations should first strengthen those foundations before relying on exam-focused revision.
Readiness check before booking
Before scheduling, test yourself with a design exercise: start with a business requirement, identify constraints, sketch a target architecture, and explain why each major Azure choice fits. If you cannot defend the design without searching for basic service capabilities, use a foundation phase before committing to an exam date.
Check whether you can describe the purpose and trade-offs of core compute models, virtual networking, storage and database choices, authentication, governance, monitoring, backup, disaster recovery, and migration approaches. You do not need to memorize every configuration screen, but you do need to recognize which design concern each service addresses.
Microsoft’s course prerequisites expect previous experience deploying or administering Azure resources and strong conceptual knowledge of Azure compute, virtual networking including load balancers, Azure storage technologies, and application concepts such as messaging and high availability. Use that expectation as a practical readiness benchmark.
Which skills carry the most weight?
The current AZ-305 skills outline groups the exam into four domains. Design infrastructure solutions accounts for 30–35% of the exam, design identity, governance, and monitoring solutions accounts for 25–30%, design data storage solutions accounts for 20–25%, and design business continuity solutions accounts for 15–20%. Use these official ranges to allocate study effort, while still covering every domain.
The ranges describe the skills measured, not a promise about the exact composition of a particular exam attempt. They are useful for prioritization: infrastructure and identity deserve substantial time, storage needs deliberate comparison practice, and continuity should not be neglected simply because it has the smallest stated range.
The official study guide says its bullets illustrate how skills are assessed and that related topics may also be covered. Most questions focus on generally available features, although preview features may appear when they are commonly used. Study the objective wording as a map of decisions, not as a complete list of every possible question.
Microsoft updated the English-language version on April 17, 2026. Review the current study guide immediately before final revision so that notes, courses, and practice work reflect the applicable skills version.
How should the percentages change your plan?
Give the largest share of your active design practice to infrastructure and identity, but do not turn the plan into a percentage-only checklist. A weak continuity or storage foundation can still undermine an otherwise strong architecture because the exam asks you to manage how decisions in different areas affect the overall solution.
A practical allocation is to study each domain once for coverage, then revisit infrastructure and identity more frequently because their official ranges are larger. Reserve the final review for cross-domain scenarios rather than rereading the same service descriptions.
Do not treat the older Exam Readiness Zone episode’s illustrative distribution as a replacement for the current skills outline. The exam was updated on April 17, 2026, so anchor your schedule to the current AZ-305 study guide and use readiness material only where it remains relevant to the current objectives.
What belongs in identity, governance, and monitoring?
This domain requires you to design how people, workloads, resources, and operations are controlled and observed. The official learning path breaks the work into governance, authentication and authorization, and logging and monitoring. Study those together because an identity decision without governance or operational visibility is incomplete.
For identity, practice separating authentication from authorization. Ask who or what needs access, how access is granted, how it is limited, and how it is reviewed or removed. Include human users, applications, services, administrators, and hybrid identities in your reasoning. The goal is to select a design that supports least privilege and workable administration without confusing identity proof with permission assignment.
For governance, examine how an organization standardizes subscriptions, resource organization, policies, tagging, access boundaries, and compliance controls. Start with the organizational requirement, then decide where the control belongs and how exceptions should be handled. Avoid choosing a governance mechanism merely because it is familiar; explain its scope and operational effect.
For monitoring, connect the signal to the action. Decide which logs, metrics, alerts, and diagnostic information are needed, where they should be collected, who should respond, and how retention or cost affects the design. A monitoring answer is stronger when it identifies the failure or security event the design must reveal.
The three-module identity, governance, and monitoring learning path is a useful focused starting point. It covers governance, authentication and authorization, and logging and monitoring, and is classified as advanced for the Solution Architect role.
Identity mistakes to eliminate
A common mistake is treating broad administrative access as a convenient default. In scenario questions, identify the narrowest role and scope that satisfies the requirement, then consider how the access is reviewed and operated. Another mistake is overlooking workload identity and designing only for interactive users.
Candidates also conflate governance with security. Governance can enforce organizational rules and structure, while security design addresses threats, access, protection, and detection. They overlap, but they answer different questions. Write a one-sentence purpose for each control in your notes.
Monitoring is often studied last and remembered as a list of tools. Replace that approach with incident paths: what signal indicates a problem, what context is required to investigate it, and what action should follow?
How should you prepare for data storage design?
Storage preparation should focus on matching data characteristics to an architecture. For every scenario, identify data type, access pattern, consistency needs, transaction behavior, scale, latency, protection requirements, and operational ownership before comparing Azure storage or database options.
Separate unstructured storage decisions from database decisions. For unstructured data, consider object access, lifecycle, redundancy, security boundaries, and performance needs. For relational or non-relational data, reason from schema, relationships, query patterns, transactional requirements, and scaling behavior rather than selecting a database by brand recognition.
Data integration also matters. Map how data enters the platform, moves between components, is transformed, and becomes available to applications or analytics. A design that names a data store but ignores ingestion, synchronization, or failure handling is not a complete architecture.
Practice explaining the cost of a choice without inventing precise financial assumptions. For example, describe the operational or performance trade-off qualitatively unless the scenario supplies the necessary figures. The exam tests design judgment; unsupported numerical estimates can distract from the actual requirement.
Use the storage domain to build comparison tables with columns for workload type, consistency, scaling, availability, security, migration difficulty, and management model. Then cover the table and recreate the reasoning from a new scenario.
Storage pitfalls in scenario questions
Do not confuse redundancy with backup. Redundancy supports availability or durability against particular failures; backup and recovery address restoration and retention requirements. Read the recovery requirement carefully and identify the failure scope before choosing a protection approach.
Do not assume that the newest or most scalable data service is automatically correct. A service must fit the application’s access pattern, data model, integration needs, and operational constraints. Likewise, a migration requirement may favor compatibility and minimal disruption over a redesign.
When reviewing an answer, ask whether the proposed store satisfies both the primary workload and the stated recovery, security, and monitoring requirements. If one requirement is met only by an unstated add-on, mark that as a gap in your design notes.
How do you study business continuity and disaster recovery?
Business continuity preparation begins with business impact, not with a product list. Identify what must remain available, what data loss is acceptable, how quickly service must return, which dependencies are critical, and which failure scope the design must withstand. Then map those requirements to architecture and operating procedures.
Distinguish availability, backup, disaster recovery, and continuity planning in your notes. They are related but not interchangeable. A highly available application can still need backup; a backup can still require a recovery design; and a recovery design can still fail if dependencies, identity, networking, or operational ownership are missing.
For each scenario, create a recovery chain: protected data, recovery location or mechanism, application dependencies, network and identity readiness, restoration sequence, validation, and return to normal operations. Include the decision that determines whether the target is met, rather than memorizing isolated service names.
Test your design against failure boundaries. Ask what happens when a resource fails, a zone or region is unavailable, a dependency is inaccessible, or data is corrupted. The correct architecture depends on the boundary and the business requirement, not on a universal high-availability pattern.
A useful study artifact is a one-page continuity matrix. Put business requirement, failure scenario, recovery objective, affected components, protection method, and validation step in separate columns. Fill it from case studies and revisit errors after each practice session.
What infrastructure topics need hands-on design practice?
The infrastructure domain covers the core architecture decisions around compute, application architecture, networking, and migration. Microsoft’s four-module infrastructure learning path specifically covers designing an Azure compute solution, application architecture, network solutions, and migrations, and identifies the path as advanced.
For compute, compare virtual machines, containers, and serverless approaches by workload control, scaling, deployment model, operations, and dependency requirements. Do not study these as a hierarchy. The scenario’s workload characteristics determine whether control, portability, event-driven execution, or reduced infrastructure management matters most.
For application architecture, trace requests and dependencies through the system. Identify communication style, messaging needs, state management, scaling boundaries, failure handling, and deployment concerns. A strong design explains how components interact and what happens when a dependency is slow or unavailable.
For networking, start with connectivity and trust boundaries. Work through address planning, segmentation, routing, name resolution, ingress, egress, hybrid connectivity, load distribution, and private access requirements. Draw the flow of a request instead of memorizing diagrams; the drawing exposes missing paths and conflicting assumptions.
For migrations, distinguish assessment, dependency discovery, target design, data movement, cutover, validation, and rollback. A migration architecture is more than selecting a destination service. It must preserve the required behavior while addressing downtime, compatibility, security, and operational transition.
Use the infrastructure learning path’s prerequisites honestly. It expects conceptual knowledge of compute, applications, networking, and migration solutions, along with working experience architecting compute and network solutions. If those areas are unfamiliar, spend time building and explaining small reference designs before attempting timed revision.
Infrastructure design mistakes
One frequent error is selecting compute before clarifying the application’s execution model. Begin with workload behavior, state, scaling, deployment, and operational constraints. Another is designing network components without tracing traffic from client to application to data and back.
Migration questions punish vague sequencing. Record what must be assessed, what can move independently, what requires synchronization, and how the business confirms success. A technically compatible target can still be unsuitable if the cutover or dependency plan is absent.
Avoid treating hybrid connectivity as a single checkbox. Identify the systems on each side, the traffic direction, name resolution, security controls, resilience expectations, and operational ownership. This produces a design that can be evaluated rather than a collection of product labels.
Which official learning resources should you use?
Start with the current AZ-305 study guide because it defines the audience, skills measured, scoring information, update notes, and links to related preparation resources. Then use Microsoft’s learning paths to fill domain gaps and the official course outline to organize broader architecture study.
The infrastructure learning path contains four modules, takes approximately 3 hours 39 minutes, and covers compute, applications, networking, and migrations. It is a compact first pass, not a substitute for experience or deliberate design practice. Complete it once for coverage, then return to modules that expose weak decisions.
The identity, governance, and monitoring learning path contains three modules covering governance, authentication and authorization, and logging and monitoring. Use it as a focused second path, especially if your background is stronger in compute or networking than in platform controls.
The instructor-led course is AZ-305T00-A. Microsoft classifies it as Advanced, associates it with the Solution Architect role, and lists a course duration of 4 days. Its topics include governance, compute, application architecture, storage, data integration, authentication, networks, business continuity, and migrations. Use the course when structured instruction, case-study discussion, or an employer-sponsored learning format fits your schedule.
Microsoft also provides an Exam Readiness Zone episode for identity, governance, and monitoring. Because the English exam version changed on April 17, 2026, verify that any older video emphasis is still consistent with the current study guide before using it as your blueprint.
How should you build a practical study sequence?
Study in dependency order: establish the exam’s current scope, assess your foundations, cover the four domains, connect the domains through architecture cases, and then rehearse decision-making under time pressure. This sequence prevents early memorization from hiding gaps in networking, identity, data, or recovery design.
Phase one is scope and baseline. Read the current study guide, record each domain and its official range, check the prerequisite certification, and take an official practice assessment if available. For every missed topic, classify the problem as knowledge, interpretation, or decision trade-off. That classification determines the next study action.
Phase two is foundation repair. Use the infrastructure path for compute, application architecture, networking, and migrations, and the identity path for governance, authentication and authorization, and monitoring. Pair each lesson with a small design note: requirement, candidate options, selected design, rejected option, and reason.
Phase three is domain consolidation. Study storage and continuity alongside infrastructure rather than treating them as isolated products. Build architecture sketches that include application traffic, identity boundaries, data flows, monitoring signals, backup or recovery paths, and migration dependencies.
Phase four is scenario practice. Work through new cases without looking at notes. For each case, underline constraints, identify the primary decision, eliminate options that violate a requirement, and document the secondary effects on security, operations, availability, and cost. Review the reasoning, not only the final selection.
Phase five is final readiness. Revisit the current study guide, recent exam updates, language information, sandbox, and weak-topic notes. Stop adding unrelated services. Your final sessions should improve accuracy in requirement interpretation and trade-off analysis.
A four-stage roadmap
A flexible roadmap can be organized into four stages: scope, learn, integrate, and verify. The calendar length should follow your existing experience and schedule rather than an invented universal timetable. Allocate more time to the stage where your baseline assessment shows uncertainty.
Scope: confirm the current skills version, prerequisite, available language, and official resources. Learn: complete the relevant Microsoft paths and close foundational gaps. Integrate: solve cross-domain architecture cases and explain rejected alternatives. Verify: use practice assessment results, the exam sandbox, and a final review of the study guide to decide whether booking is sensible.
At the end of each stage, produce evidence of readiness. Examples include a domain checklist, a corrected design diagram, a continuity matrix, or a written explanation of why one option satisfies the requirements better than another. Passive completion of videos is weaker evidence than a design you can defend.
How should you use practice questions?
Practice questions are most valuable when they reveal a reasoning error. After each item, explain which requirement controlled the answer, which alternatives failed, and which service capability was decisive. Do not measure readiness by recognizing a repeated question pattern or by memorizing answer positions.
Use Microsoft’s free practice assessment as a diagnostic if it is available through the official exam resources. Record topic, error type, and corrective resource. A missed identity question may require authorization fundamentals; a missed migration question may require dependency and cutover sequencing; a missed continuity question may require separating backup from recovery.
Avoid exam dumps, leaked questions, and memorization claims. They do not replace the knowledge or judgment measured by the exam and can lead you to study stale or misleading material. Work from official objectives, training, practice assessments, and your own architecture reasoning.
Practice reading the full scenario before choosing an answer. Mark requirements involving security, latency, resilience, administration, compatibility, or minimum operational effort. Many wrong options are plausible services that solve only part of the problem.
What delivery and scheduling details are confirmed?
The official AZ-305 page lists the exam in English, Japanese, Chinese (Simplified), Korean, German, French, Spanish, Portuguese (Brazil), Chinese (Traditional), and Italian. Check the live Schedule Exam area for the languages and appointments available to you, because availability and localized updates can change.
Microsoft states that localized versions are updated approximately eight weeks after the English version when a localized version is available, while also noting that this schedule is not guaranteed in every case. If language timing matters, verify the current version rather than assuming the localized exam matches the English update immediately.
If the exam is not available in your preferred language, Microsoft says you can request an additional 30 minutes to complete it. Confirm the accommodation or language procedure through the official scheduling and support information before booking; do not rely on an informal assumption about what will be granted.
Microsoft lists a passing score of 700. The score is a formal requirement, not a prediction of how many questions must be correct, so do not convert it into an invented percentage or target question count.
Microsoft lists AZ-305 as having no retirement date. Continue to check the official exam page and study guide for changes, because Microsoft updates exams to reflect role requirements. The English-language version was updated on April 17, 2026, and the current study guide should be your authority for recent changes.
Microsoft recommends registering with a personal Microsoft account. If you use an organizational work or school account and later leave that organization, Microsoft warns that your exam records may be lost and unrecoverable. Make the account decision before scheduling, not after the appointment is recorded.
The exam page states that price is based on the country or region where the exam is proctored. Confirm the exact current price with the exam provider before registering rather than relying on an old listing.
What to check before registration
Confirm four items in your Microsoft Learn profile: the correct personal account, the prerequisite certification status, the exam language, and the appointment details offered in your region. Then review the current study guide and exam page once more for update notices.
Use the exam sandbox to become familiar with the official exam environment. This is a preparation recommendation supported by Microsoft’s exam resources; it is not a claim about the exact format or content of your future exam attempt.
If you need extra time or another accommodation, request it through the official process early enough for the provider to review it. Keep your registration information consistent across your profile and appointment.
How do you know when to schedule?
Schedule when you can repeatedly explain architecture choices from unfamiliar requirements, not merely when you have finished a course. Your decision should combine domain coverage, prerequisite status, practice-assessment evidence, and confidence in the current skills outline.
Use a simple readiness review. For each of the four domains, write one design from memory, identify its main trade-offs, and connect it to at least two other domains. Then choose a weak area and repair it using the official study guide or Microsoft learning path. If the same foundational issue continues to appear, postpone booking and address the foundation.
A suitable candidate can answer questions such as: Which identity boundary is appropriate? What data model and access pattern does the workload require? What failure must the continuity design survive? How will traffic reach the workload and its dependencies? Which migration sequence limits disruption? These are study prompts, not predicted exam questions.
Do not book solely because AZ-305 has no listed retirement date. That status removes one scheduling pressure, but it does not make the current blueprint permanent. Keep the exam page and study guide in your review routine, especially when your preparation extends across an update.
What should you do in the final review?
Final review should be selective: verify the current blueprint, revisit errors, redraw one or two complete architectures, and confirm scheduling details. Avoid starting a large new course or trying to memorize every Azure feature during the last stage.
Create four short review sheets, one for each official domain. On each sheet, list requirements to identify, design choices to compare, dependencies to check, and common failure modes. Keep the domain label beside the notes so the material remains connected to the skills outline.
For identity, review authentication, authorization, governance, and monitoring relationships. For storage, review data characteristics, access patterns, integration, and protection. For continuity, review failure scope, recovery objectives, dependencies, and validation. For infrastructure, review compute, application architecture, networking, and migration sequencing.
Finish with an account and logistics check: prerequisite certification, personal Microsoft account, language, accommodation request if needed, appointment, and current provider information. These are practical safeguards, while the official exam page remains the source for current scheduling conditions.
What are the next actions after reading this guide?
Open the current AZ-305 study guide and write down the four domains exactly as Microsoft presents them. Confirm the Azure Administrator Associate prerequisite if you are pursuing Azure Solutions Architect Expert. Then complete a baseline assessment and let the results determine whether your next step is foundation study, domain training, or integrated scenario practice.
Next, work through the four-module infrastructure learning path and the three-module identity, governance, and monitoring path. Turn each module into a design artifact rather than a completion mark. Add storage and continuity decisions to the same architecture sketches so that your preparation reflects how solutions work in practice.
Finally, review the exam page for the current language, score, update, retirement, account, and price information before scheduling. Use the official URLs below as your reference set, and return to them whenever your preparation timeline or the exam version changes.
Conclusion
AZ-305 preparation is strongest when it combines official scope with defensible architecture decisions. Confirm the prerequisite and current blueprint, prioritize infrastructure and identity without neglecting storage or continuity, and use Microsoft learning resources to repair specific gaps. Before booking, verify language, account, accommodation, score, price, and appointment details on the official pages. Your final readiness test is simple: can you translate a requirement into a complete Azure or hybrid design and explain the trade-offs across its connected components?
Related exams
- AZ-104 exam — Microsoft Azure Administrator
- AZ-140 exam — Configuring and Operating Windows Virtual Desktop on Microsoft Azure
- AZ-120 exam — Planning and Administering Microsoft Azure for SAP Workloads
- AZ-700 exam — Designing and Implementing Microsoft Azure Networking Solutions
- AZ-400 exam — Microsoft Azure DevOps Solutions
- AZ-800 exam — Administering Windows Server Hybrid Core Infrastructure