Study guide

11.1 Messaging Architecture Design (Service Bus, Queue Storage)

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

11.1 Messaging Architecture Design (Service Bus, Queue Storage)

Key Takeaways Explain This Topic AI

Azure Service Bus Standard/Basic caps messages at 256 KB; Premium raises that to 100 MB but only over the AMQP protocol (1 MB over SBMP/HTTP) and is billed in Messaging Units of 1, 2, 4, 8, or 16.

Use Service Bus Topics and Subscriptions (not Storage Queues) whenever one message must fan out to multiple independent downstream systems.

Sessions provide guaranteed FIFO ordering per session key; duplicate detection needs an explicit history window (default 10 minutes, configurable up to 7 days) to suppress retried sends.

Azure Storage Queues are the cheap default for a simple, high-volume work backlog (64 KB message cap, no ordering, no pub-sub) when Service Bus's enterprise features are not required.

For payloads larger than the queue's message-size limit, use the claim-check pattern: store the payload in Blob Storage and put only a pointer/reference on the queue.

Last updated: July 2026

Why Messaging Architecture Design Matters on AZ-305

Messaging design sits inside Design infrastructure solutions , the highest-weighted AZ-305 domain at 30-35%, under the "Design an application architecture" functional subgroup. This is where the exam stops asking what a service does and starts asking which of several plausible services is correct for this exact requirement . The two core Azure messaging services — Azure Service Bus and Azure Storage Queues — both move a message from a producer to a consumer asynchronously, so a candidate who only knows the marketing description of each will miss scenario questions that hinge on a single differentiating requirement: strict ordering, duplicate suppression, pub-sub fanout, transactional batching, or raw message size. Expect at least one AZ-305 item that gives you five or six requirements and asks you to eliminate three services before landing on the right one.

Core Concepts and Terminology

Asynchronous messaging decouples a producer from a consumer: the producer writes a message and moves on; the consumer reads and processes it whenever it is ready. This buys resilience (a consumer outage does not lose work) and independent scaling, but requires the consumer to handle at-least-once delivery — the same message can arrive more than once, so consumer logic must be idempotent (processing the same message twice produces the same result as processing it once).

Azure Service Bus

Service Bus is Microsoft's enterprise message broker, built for reliable, ordered, and sometimes transactional business messaging.

Queues — point-to-point; each message is processed by exactly one competing consumer.

Topics and Subscriptions — publish-subscribe; one published message can be delivered to many independent subscriptions, each with its own SQL-like or correlation filter rule, so different downstream systems can each receive only the messages they care about from the same feed.

Sessions — group related messages by a session key so a single consumer processes them strictly in order (first-in, first-out, or FIFO) and can maintain state across the sequence. Without sessions, Service Bus delivery order is not guaranteed once more than one consumer is competing.

Dead-letter queue (DLQ) — an automatic sub-queue that quarantines a message once MaxDeliveryCount is exceeded (default 10 delivery attempts) or its time-to-live (TTL) expires, so poison messages do not block the main queue forever.

Duplicate detection — an optional history window (default 10 minutes, configurable up to 7 days) that uses each message's MessageId to silently drop resends from a retrying client.

Transactions — batch multiple send/complete operations into one atomic unit within a single entity (and across entities in Premium), useful when a message must be completed and a new one sent together or not at all.

Auto-forwarding — chains a queue or topic subscription to another queue/topic (up to four hops) for simple two-stage routing without custom relay code.

Tiers : Basic and Standard are shared multi-tenant infrastructure billed per operation, capped at 256 KB per message. Premium is dedicated capacity billed in Messaging Units (1, 2, 4, 8, or 16) , giving predictable low-latency performance, virtual network (VNet) service endpoints and private endpoints, availability-zone support, and messages up to 100 MB — but only over the Advanced Message Queuing Protocol (AMQP); the older SBMP and HTTP protocols stay capped at 1 MB even on Premium. Premium also adds geo-disaster recovery through a paired namespace with manual failover for regional outages.

Azure Storage Queues

A queue that lives inside a Storage Account, aimed at simplicity and cost rather than enterprise features.

Message size capped at 64 KB ; total queue capacity is limited only by the storage account (up to 500 TB).

At-least-once delivery, no guaranteed ordering , and no pub-sub — a message goes to whichever single consumer dequeues it first.

Per-message TTL is configurable (default 7 days; can be set to -1 for messages that never expire).

A visibility timeout hides a dequeued message from other consumers while it is being processed; if the consumer crashes before deleting it, the message reappears for another consumer to retry.

Far cheaper per operation than Service Bus — the right default when an application just needs a durable backlog of work items and none of Service Bus's enterprise guarantees.

  • Capability Service Bus Storage Queues
  • Max message size 256 KB (Standard) / 100 MB AMQP (Premium) 64 KB
  • Ordering Guaranteed via Sessions Not guaranteed
  • Publish-subscribe Yes (Topics/Subscriptions) No
  • Duplicate detection Yes, configurable window No (build your own)
  • Transactions Yes No
  • Dead-lettering Automatic sub-queue Manual (poison-message pattern)
  • Relative cost Higher Lower
  • Best fit Enterprise integration, ordered/transactional workflows Simple, high-volume work backlog
  • Decision Framework

Need to fan one event out to several independent downstream systems → Service Bus Topics .

Need strict per-key ordering plus duplicate suppression plus transactional completion → Service Bus with Sessions and a duplicate-detection window sized to your client's retry interval.

Need a cheap, simple, very high-volume backlog with no ordering requirement → Storage Queue .

Message is larger than the queue's limit (for example, a multi-megabyte document) → use the claim-check pattern : store the payload in Blob Storage and enqueue only a reference, regardless of which queue technology you pick, or move to Service Bus Premium if the whole message truly must travel through the broker.

Need predictable low latency, VNet isolation, and geo-disaster recovery for a regulated workload → Service Bus Premium .

Exam Scenario

An order-management platform must publish each new order so that inventory, shipping, and invoicing systems each receive and process it independently. Orders from the same customer must be processed strictly in the order placed, and a flaky mobile client sometimes submits the same order twice within a few seconds. The correct design is a Service Bus Topic with three subscriptions (one per downstream system), Sessions enabled and keyed on customer ID to preserve per-customer ordering, and a duplicate-detection window covering the client's retry interval. A Storage Queue is wrong because it cannot fan out to three independent subscribers or guarantee ordering; Event Grid (covered next) is wrong because it is built for lightweight, fire-and-forget notifications, not ordered, deduplicated, guaranteed-delivery business transactions.