Study guide
14.2 Common AZ-305 Decision Traps
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.2 Common AZ-305 Decision Traps
Key Takeaways Explain This Topic AI
AZ-305 wrong answers are almost always technically real services — the differentiator is one specific word in the scenario stem, not whether the service exists.
VPN Gateway vs. ExpressRoute vs. VNet Peering hinges on whether the stem requires a bandwidth SLA/dedicated circuit versus simple encrypted or backbone connectivity.
SQL Managed Instance vs. Azure SQL Database vs. Cosmos DB hinges on instance-level compatibility needs versus PaaS simplicity versus global distribution.
Storage redundancy (LRS/ZRS/GRS/RA-GRS/GZRS) hinges on whether the failure scope is hardware, datacenter/zone, or full region, and whether secondary read access is required.
Build a signal-word reflex for the recurring trap pairs (Policy vs. RBAC, Backup vs. Site Recovery, Zones vs. Sets, NSG vs. Firewall) rather than re-deriving each from scratch under time pressure.
Last updated: July 2026
Why "trap pairs" dominate AZ-305 wrong answers
AZ-305 rarely tests whether you have memorized the name of an Azure service. It tests whether you can tell apart two or three services that all plausibly solve the same general problem but differ on one specific requirement. Nearly every hard question on this exam reduces to a trap pair : two options that both sound correct until you notice the one word in the stem that only one of them satisfies. Building a fast, reliable "signal word" reflex for the most common trap pairs is one of the highest-leverage things you can do in your final review.
Connectivity traps: VPN Gateway vs. ExpressRoute vs. VNet Peering
Signal in the stem Correct choice Why
"Over the public internet, encrypted, quick to provision, lower cost" Site-to-Site VPN Gateway Uses an IPsec/IKE tunnel across the internet; cheapest and fastest of the three to stand up, but shares internet bandwidth and latency variability
"Private, dedicated circuit, guaranteed bandwidth and SLA, no internet path, large sustained data volume" ExpressRoute A private connection through a connectivity provider, bypassing the public internet entirely; scales from tens of Mbps up to 100 Gbps with ExpressRoute Direct, at higher cost and longer provisioning lead time
"Two Azure virtual networks need to talk to each other, low-latency Microsoft backbone routing, no encryption requirement stated" VNet Peering Routes over Microsoft's private backbone with no gateway to manage and no extra encryption; global peering spans regions, regional peering stays in one region, but neither is transitive by default
The single most common wrong answer here is picking ExpressRoute whenever the word "private" appears, even when the stem never mentions guaranteed bandwidth, an SLA, or high sustained volume. If the requirement is simply "encrypted connectivity from on-premises to Azure," a VPN Gateway already satisfies it at a fraction of ExpressRoute's cost and lead time — do not over-engineer past what the stem actually requires.
Data platform traps: SQL Managed Instance vs. Azure SQL Database vs. Cosmos DB
Signal in the stem Correct choice Why
"Lift-and-shift SQL Server, SQL Agent jobs, cross-database queries, linked servers, CLR" Azure SQL Managed Instance Near-100% surface-area compatibility with on-premises SQL Server, including instance-level features Azure SQL Database does not support
"Modern single database or elastic pool, serverless auto-pause, no instance-level features needed" Azure SQL Database Fully managed PaaS database with DTU or vCore purchasing models and a serverless compute tier that pauses during idle periods to save cost
"Global distribution, single-digit-millisecond read/write latency at the 99th percentile, schema-flexible, multi-region active-active writes" Azure Cosmos DB Purpose-built for globally distributed, horizontally scalable workloads with tunable consistency models, unlike either SQL option
Watch for stems that mention "existing stored procedures" or "T-SQL compatibility" — those phrases point away from Cosmos DB even when the workload also mentions global users, because compatibility with existing relational code overrides the appeal of global distribution.
Storage redundancy traps: LRS vs. ZRS vs. GRS vs. RA-GRS vs. GZRS
Option Copies & placement Durability Protects against
LRS (Locally Redundant Storage) 3 synchronous copies, single datacenter 11 nines (99.999999999%) per year Hardware failure only — no datacenter or region protection
ZRS (Zone-Redundant Storage) 3 synchronous copies across availability zones, same region ~12 nines A full datacenter/zone outage within the region
GRS (Geo-Redundant Storage) LRS in primary region + async copy to a paired secondary region (6 copies total) ~16 nines A full region outage — secondary data is not readable by default
RA-GRS Same as GRS, plus read access to the secondary endpoint ~16 nines Region outage, with read access to secondary during the outage
GZRS ZRS in primary + async replication to secondary region ~16 nines Zone outage in primary AND region outage, in one tier
The recurring trap: a stem that says "must remain available during a full region outage" but a candidate answers ZRS because it "sounds like more redundancy than LRS." ZRS never leaves the region, so it cannot survive a region-wide outage — only GRS, RA-GRS, or GZRS qualify. Conversely, if the stem asks for the lowest-cost option and a single datacenter outage is an acceptable risk, LRS is correct even though it looks "weak" next to the other four.
Other high-frequency trap pairs
- Trap pair Rule of thumb
- Azure Policy vs. RBAC Policy enforces what configuration is allowed; RBAC controls who can perform actions
Azure Backup vs. Azure Site Recovery Backup recovers from data loss (point-in-time restore); Site Recovery recovers from site loss (regional failover)
Availability Zones vs. Availability Sets Zones span separate datacenters (99.99% SLA); Sets span fault/update domains within one datacenter (99.95% SLA)
NSG vs. Azure Firewall NSG is a stateless, free, subnet/NIC-level 5-tuple filter; Azure Firewall is a stateful, centrally managed service with FQDN filtering and threat intelligence
Password Hash Sync vs. Pass-through Authentication vs. Federation PHS validates a synced hash in the cloud (simplest, no on-premises dependency); PTA validates live against on-premises AD (requires an always-on agent); Federation delegates to AD FS (most complex, needed for advanced on-premises auth rules)
Load Balancer vs. Application Gateway vs. Front Door Load Balancer is Layer 4 (TCP/UDP); Application Gateway is regional Layer 7 with a built-in WAF; Front Door is global Layer 7 with edge caching and anycast routing