Study guide

14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions

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

14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions

Key Takeaways Explain This Topic AI

AZ-305 scenario stems routinely combine Identity/Governance/Monitoring, Data Storage, Business Continuity, and Infrastructure requirements into a single question.

Decompose every scenario into individually tagged requirement bullets before evaluating answer options.

Numeric constraints (RTO/RPO, latency, region counts) and absolute words ("minimal," "must not") eliminate wrong answers fastest.

The correct answer satisfies every stated constraint simultaneously, even when it is the less flashy service compared to a competing option.

Always re-check a surviving answer against requirements tagged to a different domain than the question's apparent primary subject.

Last updated: July 2026

Why cross-domain scenarios are the real AZ-305 test

Every earlier chapter in this guide isolated one design skill at a time: how to design authentication, how to pick a storage redundancy tier, how to size a recovery objective. The real AZ-305 exam does not test skills in isolation. A single scenario stem routinely bundles an identity requirement, a data requirement, a continuity requirement, and an infrastructure requirement into one company profile, then asks for one architecture decision that has to satisfy all of them at once. Microsoft's own guidance for this exam states that questions "present complex scenarios requiring trade-off analysis" rather than single-fact recall — that is the whole difference between AZ-305 and an implementation exam like AZ-104.

This matters because the domain weights (25-30% Identity/Governance/Monitoring, 20-25% Data Storage, 15-20% Business Continuity, 30-35% Infrastructure) describe how often a domain is the primary subject of a question, not how often it appears as a supporting constraint. A question whose primary subject is Infrastructure (network topology) can still fail you if you ignore an embedded Identity constraint ("subsidiary must keep its own on-premises AD DS as the identity source") or a Continuity constraint ("the design must support a 15-minute RTO"). Practicing scenarios that cross domains — rather than only drilling isolated flashcard-style facts — is what closes the gap between "I know the services" and "I can pass AZ-305."

A four-step method for decomposing a multi-domain stem

List every requirement as its own line. Do not read the paragraph once and jump to the options. Physically (or mentally) break the scenario into bullet points — one bullet per stated requirement or constraint.

Tag each requirement to a domain. Identity/Governance/Monitoring, Data Storage, Business Continuity, or Infrastructure. Some bullets touch two domains (for example, "quarterly access review for the subsidiary's admins" is Identity and Governance).

Find the requirement with a hard number or hard word. Numbers (RTO, RPO, latency, percentage, region count) and hard words ("must," "cannot," "no additional hardware," "minimal application changes") eliminate the most wrong answers fastest. Start there, not with the domain you personally find easiest.

Re-check the surviving option against every OTHER domain's requirement. The most common trap is an option that satisfies the domain the question looks like it is about while quietly violating a requirement from a different domain buried earlier in the stem.

Worked scenario 1: acquisition with conflicting constraints

Scenario: Contoso Ltd. runs a three-tier order-processing application in a single Azure region. Contoso has just acquired a subsidiary that operates its own on-premises Active Directory Domain Services (AD DS) forest and a large SQL Server database. The architecture must: (1) give subsidiary users single sign-on to the existing application without creating duplicate cloud identities; (2) migrate the subsidiary's SQL Server database to Azure with minimal changes to existing stored procedures, SQL Agent jobs, and linked-server references; (3) guarantee the application can fail over to a secondary Azure region with a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes; (4) keep all new diagnostic data flowing into the existing Log Analytics workspace rather than a new one.

Requirement Domain Correct decision Why the tempting alternative fails

SSO without duplicating identities Identity Extend the existing Microsoft Entra tenant to the subsidiary's on-premises forest with Microsoft Entra Connect (password hash sync or pass-through authentication) Creating a brand-new guest/B2B invitation for every subsidiary user duplicates identity administration and breaks the "no duplicate identities" constraint

Migrate SQL Server with minimal app changes Data Azure SQL Managed Instance — near-100% surface-area compatibility, supports SQL Agent, linked servers, and cross-database queries Azure SQL Database (single database/elastic pool) does not support SQL Agent jobs or cross-database queries, so "minimal application changes" is violated

15-minute RTO / 5-minute RPO Business Continuity An auto-failover group for the Managed Instance plus Azure Site Recovery replication for the VM tier A nightly backup-and-restore strategy cannot hit a 15-minute RTO for a large database — restore time alone usually exceeds that window, so backup-only is a trap

Centralized diagnostics Infrastructure/Monitoring Point new resources' diagnostic settings at the existing Log Analytics workspace Provisioning a second workspace fragments queries and alerting, and adds an unnecessary resource to govern

Notice that three of the four correct answers are the "less exciting" option (auto-failover group over disaster recovery scripting, existing workspace over a new one). AZ-305 consistently rewards the option that satisfies every stated constraint over the option that showcases the newest or most powerful service.

Worked scenario 2: global retail data residency

A second pattern worth practicing: a global retailer needs (a) per-region data sovereignty because of local regulation, (b) low-latency writes from IoT point-of-sale devices in multiple regions, and (c) delegated administration so each region's IT team can manage only its own resources. The cross-domain answer combines Cosmos DB with multi-region writes (data, low-latency writes per region), Azure Policy scoped per management group to enforce data-residency rules (governance), and RBAC role assignments scoped to each region's resource group (identity) — three different domains, one coherent design. A wrong-but-plausible answer might recommend a single global SQL Database with read replicas; that satisfies "low latency reads" but not "low-latency writes " in every region, which is the differentiating word in the stem.

Practice questions