A global company uses an Azure Service Bus namespace to handle critical messages between its distributed applications. The company needs to ensure that message processing can continue even if an entire Azure region becomes unavailable. The solution must support active/passive failover with minimal data loss and provide a consistent endpoint for applications. Which Azure Service Bus feature should be implemented?
- AStandard tier Service Bus with geo-redundant storage.
- BBasic tier Service Bus with Availability Zones.
- CMultiple Service Bus namespaces with Azure Traffic Manager.
- DPremium tier Service Bus with Geo-disaster recovery.
Show answer & explanationAnswer & explanation
Correct answer: D. Premium tier Service Bus with Geo-disaster recovery.
Azure Service Bus Premium tier offers Geo-disaster recovery, allowing for active/passive failover to a paired region. This feature provides a consistent alias for applications, synchronous metadata replication, and asynchronous data replication, ensuring minimal data loss (RPO = 0 for metadata, RPO of seconds/minutes for data) and continuous message processing during a regional outage.
Why the other options are wrong
- A. Standard tier does not support Geo-disaster recovery. Geo-redundant storage is for underlying storage, not for the Service Bus messaging plane itself.
- B. Basic tier does not support Geo-disaster recovery or Availability Zones. Availability Zones protect within a region, not against regional outages.
- C. While possible to use multiple namespaces with Traffic Manager, this would require manual failover and custom application logic for connection string management, which Geo-disaster recovery handles automatically with a consistent alias.
Azure Service Bus Geo-disaster recovery
Azure Service Bus Geo-disaster recovery, available in the Premium tier, provides active/passive failover across Azure regions for namespaces, ensuring business continuity with minimal data loss and a consistent endpoint.
- Requires Premium tier Service Bus.
- Active/passive failover to a paired region.
- Synchronous metadata replication, asynchronous data replication.
- Provides a consistent alias for connection strings.
- RPO is typically seconds/minutes for data, 0 for metadata.
Memory trick: Service Bus Premium Geo-DR keeps your messages flowing globally.