Azure Service Bus Flashcards
1
Q
What is JMS 2.0?
A
JMS 2.0 (Java Message Service 2.0) is an updated API for messaging in Java that simplifies message-driven applications by introducing features like simplified API methods, asynchronous message consumption, and improved resource management. It enhances the efficiency of developing messaging-based Java applications.
2
Q
What is AMQP 1.0?
A
AMQP 1.0 (Advanced Message Queuing Protocol) is an open standard messaging protocol designed for reliable, interoperable, and flexible message exchange across platforms. It ensures message delivery guarantees, supporting various patterns like publish-subscribe and point-to-point communication.
3
Q
What is the default redundancy model?
A
The default resilience model for Azure Service Bus is region-based redundancy, meaning it offers high availability within a single region without zone redundancy. This provides reliability but may not protect against individual zone failures unless zone redundancy is explicitly enabled.
4
Q
What is Azure Service Bus?
A
It is a platform-as-a-service Queue and pub-sub message broker
5
Q
What are the SKU and Pricing tiers?
A
- Basic Tier:
Features:
Supports queues only; topics and subscriptions are not available.
Scheduled messages are supported.
Maximum message size is 256 KB.
Use Case: Suitable for simple, point-to-point messaging scenarios without the need for advanced features.
Pricing: Pay-as-you-go model based on the number of operations. - Standard Tier:
Features:
Supports both queues and topics with subscriptions.
Enables features like transactions, duplicate detection, sessions, and auto-forwarding.
Maximum message size remains at 256 KB.
Use Case: Ideal for applications requiring more advanced messaging patterns, such as publish/subscribe, with moderate throughput needs.
Pricing: Includes a base charge with additional costs per operation and brokered connections beyond the included quota. - Premium Tier:
Features:
Offers all features of the Standard tier with additional capabilities.
Provides resource isolation through dedicated resources, ensuring predictable performance.
Supports larger message sizes up to 100 MB.
Includes features like Geo-Disaster Recovery (Geo-DR), Virtual Network (VNet) integration, and Java Message Service (JMS) 2.0 support.
6
Q
What type of messaging pattern does the Basic tier of Azure Service Bus support?
A
Point-to-point messaging (queues only)
7
Q
Does the Basic tier of Azure Service Bus support topics and subscriptions?
A
No, only queues are supported.
8
Q
What is the maximum message size in the Basic tier of Azure Service Bus?
A
256 KB
9
Q
What is the best use case for the Basic tier of Azure Service Bus?
A
Simple point-to-point messaging scenarios without advanced features.
10
Q
What additional messaging pattern does the Standard tier of Azure Service Bus support compared to the Basic tier?
A
Publish/subscribe (topics with subscriptions)
11
Q
Which advanced features are available in the Standard tier of Azure Service Bus?
A
Transactions, duplicate detection, sessions, and auto-forwarding.
12
Q
What is the maximum message size in the Standard tier of Azure Service Bus?
A
256 KB
13
Q
What is the ideal use case for the Standard tier of Azure Service Bus?
A
Applications with moderate throughput requiring publish/subscribe messaging.
14
Q
What resource allocation feature does the Premium tier of Azure Service Bus offer for performance?
A
Dedicated resources for predictable performance.
15
Q
What is the maximum message size in the Premium tier of Azure Service Bus?
A
100 MB
16
Q
Which additional advanced features are included in the Premium tier of Azure Service Bus?
A
Geo-Disaster Recovery (Geo-DR), VNet integration, and JMS 2.0 support.
17
Q
What type of applications is the Premium tier of Azure Service Bus suited for?
A
Mission-critical applications requiring high throughput, low latency, and enhanced reliability.
18
Q
Does the basic tier support Topics?
A
No, only queues
19
Q
Does the basic tier support scheduled messages?
A
Yes scheduled messages are supported?
20
Q
For the basic tier what is max message size?
A
256KB
21
Q
What is the lowest cost tier where i can get Topic support
A
Standard Tier
22
Q
What is a transaction?
A
In Azure Service Bus, a transaction is a feature that allows multiple operations to be grouped together into a single, atomic action. T
23
Q
Explain Azure Service Bus Standard SKU?
A
$9.72 monthly per azure subscription
13million/operations free, 13-100M $0.80per M
Partial JMS 2.0 feature set
Shared environment
24
Q
Explain Azure Service Bus Premium SKU?
A
Isolated environment
$0.928 per hour
Full JMS 2.0 feature set
25
What is a name space in Azure Service Bus?
In Azure Service Bus, a namespace is a container for all messaging components, which includes queues, topics, and subscriptions. It functions similarly to a "server" in other messaging technologies but is fully managed by Azure. Here’s a breakdown of what a namespace does:
Container: A namespace groups related Service Bus resources. Each namespace can contain multiple queues and topics, allowing you to logically organize your messaging entities.
Isolation: It provides isolation of resources, ensuring that queues, topics, and subscriptions within a namespace are accessible only within that namespace. This can enhance security and simplify access management.
Scalability: A namespace can be scaled to handle a large volume of messages. You can adjust throughput and other configurations at the namespace level to support high-demand scenarios.
Access Control: Access policies can be applied at the namespace level, giving fine-grained control over who can send, receive, or manage messages.
Each namespace is globally unique within Azure, meaning that it must have a unique name across all Azure subscriptions. When setting up Service Bus resources, you create a namespace as the first step before adding queues, topics, or any other messaging entities.
26
What option have we for integrating azure service bus in a vnet?
1. Private Endpoint (Recommended for secure, private access)
Description: A Private Endpoint is a network interface that connects you privately and securely to Azure Service Bus via the Azure backbone network, with a private IP address from your VNet.
How It Works: With Private Endpoints, the Service Bus endpoint is accessible only within your VNet and connected VNets through a private IP address.
Advantages:
Blocks public access and allows only VNet-internal traffic.
Integrates with Azure DNS private zones to resolve the Service Bus namespace to its private IP.
Enhances security as traffic does not traverse the public internet.
2. Service Endpoint (For additional access control)
Description: A Service Endpoint provides secure access to Azure Service Bus from a specific VNet subnet over the Azure backbone network.
How It Works: Service Endpoints extend the VNet’s identity to the Azure Service Bus service, allowing resources in that VNet to access Service Bus without needing public IP addresses.
Advantages:
Simplifies network security by allowing Azure Service Bus to recognize the subnet.
Can be configured with access control to limit access to specific subnets.
Limitations:
Unlike Private Endpoints, Service Endpoints do not block internet access to the Service Bus namespace.
Service Bus is still accessible over the public internet, so it’s less restrictive than Private Endpoints.
27
I have a Azure Service Bus with a Private Endpoint to a vnet, i want to restrict the network traffic to the ASB, what options do i have?
IP Firewall Rules (For allowing specific IP ranges)
Description: Azure Service Bus includes IP firewall rules that restrict access to specified IP addresses or IP ranges.
How It Works: Firewall rules allow you to control who can access your Service Bus namespace based on the IP addresses of incoming requests.
28
When using Azure Service Bus, do you get a public ip?
Azure Service Bus used to not provided a public IP, now it dose and you can turn it off if required or filter it using Azure Service Bus IP filters, you also get a FQDN and Premium tier supports VNet service endpoints and private endpoints for enhanced security.
29
Can i use the standard SKU with vNET private or service endpoints?
No, VNet service and private endpoints are only available with the Premium SKU of Azure Service Bus, not the Standard SKU.
30
Can you create a hierarchical name space for your Azure Service Bus?
Yes in the name space you can create hierarchical name space.
31
For Azure service bus what is the max message sizes for each sku?
Basic :
Messages can be up to 256 KB in size.
Standard :
HTTP and SBMP Protocols: Limited to 1 MB per message.
Premium Tier:
HTTP and SBMP Protocols: Limited to 1 MB per message.
AMQP Protocol: Supports messages up to 100 MB.
You can use paretations and get upto 80GB
32
When a message is accepted by Azure Service Bus, how is it copied?
Triple replicated to disk.
33
How do you push a message in the dead letter queue?
You call the dead letter api (same api just the dead letter part)
34
Why would you call the dead letter queue?
You (consumer) can handler it or there is a continued error)
35
What is scheduling in Azure Service Bus?
Scheduling in Azure Service Bus allows messages to be sent at a future time, enabling delayed message delivery. This feature is useful for scenarios where messages need to be deferred for processing later. Scheduled messages are held in the queue or topic until their delivery time.
36
Is scheduling in Azure Service Bus available on basic and standard tier
Yes, Azure Service Bus supports scheduled messages in both the Basic and Standard tiers. This feature allows you to send messages that are delivered at a specified future time, enabling delayed processing scenarios.
AZURE
37
Can you cancel Azure Service Bus scheduled messages?
Yes
38
What is a deferral in Azure Service Bus ?
A deferral in Azure Service Bus allows a message to be set aside temporarily when a receiver cannot process it immediately. The message remains in the queue but is hidden from other receivers. The deferred message can be retrieved later using its unique sequence number for processing.
39
What is a session in Azure Service Bus?
In Azure Service Bus, a session groups related messages with the same SessionId, enabling ordered, stateful message processing by a single receiver. This feature is useful for scenarios where message order and context are critical. Only one client processes each session at a time, ensuring exclusive handling.
40
What can you do for a queue that is super quite and what to save resources?
You can intergrade Azure Service Bus with Event Grid and subscribe for "ActiveMessageWitNoListeners", this kicks off Azure Event Grid and Event Grid can be used to spin up consumer to deal with the message.
41
What is a transaction in Azure Service Bus ?
its where the entire transaction suiceeds of not, this will meant that a consumer receives a message and is about to do some work by sending further messages, all messages need to succeed or all message will fail as a group.
42
What is the primary purpose of Azure Service Bus?
To provide a reliable messaging service between applications and services.
43
What is a Service Bus Topic?
A messaging entity that allows multiple subscribers to receive copies of messages.
44
How does Service Bus ensure message delivery?
It uses a queuing mechanism to guarantee at-least-once delivery of messages.
45
What are the key use cases of Azure Service Bus?
Asynchronous messaging, decoupling of services, and load leveling.
46
What are the key features of Service Bus Topics?
Message filtering, multiple subscriptions, and session support.
47
What architectural pattern does Service Bus support?
The publish/subscribe messaging pattern.
48
How does Service Bus handle message security?
Messages are encrypted in transit and at rest using Azure-managed keys.
49
What is Azure Entra ID RBAC in Service Bus?
It provides fine-grained access control for managing Service Bus resources.
50
What is the maximum message size in Service Bus Standard Tier?
256 KB per message.
51
What is the maximum message size in Service Bus Premium Tier?
1 MB per message.
52
What purchasing tiers does Azure Service Bus offer?
Basic, Standard, and Premium.
53
What is the key difference between Service Bus Standard and Premium tiers?
Premium provides dedicated resources and better performance.
54
What is the maximum retention period for messages in Service Bus?
14 days.
55
How does Service Bus achieve high availability?
Through geo-redundant data centers and failover capabilities.
56
What backup options are available in Service Bus?
Service Bus provides automatic replication and backup of messages.
57
How does Service Bus integrate with other Azure services?
It integrates with Azure Logic Apps, Functions, and Event Grid for workflow automation.
58
What is a Service Bus Subscription?
A named entity that receives a copy of messages from a Topic.
59
What is message dead-lettering in Service Bus?
Dead-lettering is used to handle messages that cannot be delivered or processed.
60
What is the default time-to-live (TTL) for messages in Service Bus?
14 days, configurable.
61
How does Service Bus support disaster recovery?
Through geo-replication and automated failover.
62
What are some common use cases for Service Bus?
Decoupling microservices, reliable messaging, and load balancing.
63
How does Service Bus ensure message ordering?
By using message sessions to maintain message order in a queue.
64
What is a dead-letter queue in Service Bus?
A subqueue that stores messages that cannot be processed.
65
How is security enforced in Service Bus?
Through Azure Entra ID integration, shared access policies, and encryption.
66
How does Service Bus handle large messages?
Large messages are handled by linking the message body to a blob in Azure Storage.
67
What is Auto-forwarding in Service Bus?
A feature that forwards messages from one queue or topic to another.
68
What is the role of the Service Bus Namespace?
It is a container for queues, topics, and subscriptions.
69
What are the benefits of using the Premium tier in Service Bus?
Guaranteed performance, isolation, and advanced features like virtual networks.
70
How does Service Bus manage duplicate messages?
It uses the Duplicate Detection feature to filter out duplicates.
71
What are message sessions in Service Bus?
They allow related messages to be processed in order as a single unit.
72
What governance features are available in Service Bus?
Policies for quotas, access control, and monitoring through Azure Monitor.
73
How does Service Bus scale?
It scales by creating more messaging entities and partitioning.
74
What integration does Service Bus have with Azure Entra ID?
Azure Entra ID can be used for authentication and RBAC for access control.
75
What is Message Deferral in Service Bus?
Deferral postpones the delivery of a message until conditions are met.
76
How does Service Bus handle throttling?
Service Bus applies rate limits to prevent overloading.
77
What are the message delivery modes in Service Bus?
Peek-lock and receive-and-delete.
78
What is the purpose of Peek-lock in Service Bus?
It locks the message for processing and avoids loss in case of failure.
79
What monitoring options are available for Service Bus?
Azure Monitor provides insights into performance and operations.
80
How does Service Bus integrate with Azure Logic Apps?
Logic Apps can trigger workflows based on Service Bus messages.
81
What are some performance optimization techniques for Service Bus?
Use sessions, partitioning, and the Premium tier for performance.
82
How does Service Bus support multi-region availability?
It uses geo-replication for data resiliency and disaster recovery.
83
What is Partitioning in Service Bus?
A feature that splits data across multiple partitions to improve performance.
84
How does Service Bus handle message filtering?
It allows custom filters to control which messages are sent to subscribers.
85
What is the role of Shared Access Policies in Service Bus?
They define permissions for managing and accessing Service Bus entities.
86
How does Service Bus support large-scale applications?
By providing high throughput, partitioning, and the Premium tier.
87
What is the difference between Service Bus and Event Hubs?
Service Bus is designed for reliable messaging, while Event Hubs focuses on event streaming.
88
How does Service Bus handle poison messages?
Poison messages are sent to the dead-letter queue after multiple failed attempts.
89
What is the maximum size for a Service Bus queue?
80 GB in the Premium tier.
90
How does Service Bus handle transactional messaging?
It supports atomic transactions to ensure all operations succeed or fail together.
91
What disaster recovery options are available for Service Bus?
Service Bus supports automated failover and geo-replication.
92
How can Service Bus messages be backed up?
Messages can be backed up by integrating with Azure Storage or other services.
93
What is the primary purpose of a Service Bus namespace?
A Service Bus namespace provides a container for Service Bus resources.
94
What is a Service Bus partitioned entity?
It is handled by multiple message brokers, improving throughput and resilience.
95
Where does Azure Service Bus store data?
Standard tier uses Azure SQL Database, Premium tier stores data in selected regions.
96
What protocols can be used with Azure Service Bus?
AMQP and HTTPS with TLS are used to send and receive messages.
97
What is AMQP-over-WebSockets in Service Bus?
It runs over TCP 443 like HTTPS, providing message functionality with added latency.
98
What should be considered when creating Service Bus entities?
Properties like partitioning, sessions, duplicate detection, and express entities are immutable.
99
How does Azure Service Bus handle large messages?
Use the claim check pattern for messages larger than the maximum size limit.
100
What are the firewall ports needed for Service Bus?
Ports 5671/5672 for AMQP and 443 for HTTPS/AMQP-over-WebSockets.
101
Does Service Bus support Java Message Service (JMS)?
Yes, Service Bus supports JMS 2.0 in the Premium tier.
102
What are Shared Access Signatures in Service Bus?
They are secure URI-based authentication tokens supported across multiple languages.
103
How does Service Bus handle message delivery between regions?
Data transfer within regions is free, while transfers outside the region incur egress charges.
104
Can you move a Service Bus namespace between subscriptions?
Yes, using the Azure portal or PowerShell.
105
What happens if you delete a Service Bus namespace?
You must wait 4 hours before recreating it with the same name in another subscription.
106
How does Service Bus handle exceptions?
It generates exceptions based on specific API errors, with recommended actions.
107
What is the data retention policy in Service Bus?
Messages can be retained for up to 14 days, after which they are deleted.
108
What ports are required for TLS 1.1 or higher in Service Bus?
Port 443 is required for TLS 1.1 and higher, and TLS 1.0 is deprecated.
109
How do you charge for Service Bus?
Charges are based on messaging operations, data transfer, and premium resource utilization.
110
How does Service Bus ensure durability?
It replicates data across availability zones and paired regions for durability.
111
What IP addresses are required for Service Bus communication?
Use nslookup on the namespace to find the dynamic IP addresses for firewall allowlisting.
112
What best practices improve Service Bus performance?
Use partitioning, optimize message size, and manage sessions for better throughput.
113
How can Service Bus entities be secured?
Through Shared Access Signatures, Azure Entra ID RBAC, and firewall rules.
114
How does Service Bus handle message ordering in a partitioned queue?
Message ordering is not guaranteed in partitioned entities.
115
What are express entities in Service Bus?
Express entities store messages only in memory, reducing persistence costs.
116
How do Service Bus and Event Grid differ?
Service Bus focuses on reliable messaging, while Event Grid handles event-driven communication.
117
Can you disable TLS 1.0 and 1.1 in Service Bus?
Yes, you can enforce a minimum TLS version for Service Bus namespaces.
