Microsoft Certified: Azure Solutions Architect ExpertDesign business continuity solutionsMedium
A global company uses an Azure Service Bus namespace to handle critical messages between its microservices deployed across different Azure regions. The company requires a disaster recovery solution for Service Bus that ensures messages are not lost and processing can continue with minimal downtime in the event of a regional outage. Which Azure Service Bus feature should be implemented?
- AService Bus Premium tier with Availability Zones
- BService Bus Geo-disaster recovery
- CAzure Event Hubs Capture
- DService Bus Standard tier with message deferral
Show answer & explanationAnswer & explanation
Correct answer: B. Service Bus Geo-disaster recovery
Service Bus Geo-disaster recovery provides a primary-secondary namespace pairing across Azure regions. In a regional outage, a manual or automated failover can be initiated to the secondary namespace, ensuring message continuity and minimal downtime without data loss.
Why the other options are wrong
- A. Availability Zones provide high availability within a single region, not disaster recovery across regions.
- C. Azure Event Hubs Capture is for capturing Event Hubs data to storage, not for Service Bus disaster recovery.
- D. Message deferral is a messaging pattern, not a disaster recovery solution for an entire Service Bus namespace.
Azure Service Bus Geo-disaster recovery
A Service Bus feature that enables continuous replication of metadata between a primary and secondary namespace in different Azure regions, allowing for seamless failover in case of a regional disaster.
- Requires Service Bus Premium tier
- Automatically replicates namespace metadata (queues, topics, subscriptions)
- Requires manual or programmatic initiation of failover
- Provides a consistent alias for applications after failover
Memory trick: Geo-DR ensures messages always find their way, even if a region vanishes.