AI-200 Event Driven Integration Practice Test 2 — 15 Questions

Question 1

You are writing a Python application that sends telemetry data to an Azure Event Hub. To ensure high performance and non-blocking batch sends, which method from the `azure-eventhub` SDK should you use?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

producer.create_batch() followed by producer.send_batch(). The azure-eventhub SDK's EventHubProducerClient exposes create_batch() to build an EventDataBatch up to the maximum message size, then send_batch() transmits it asynchronously in a single AMQP transfer. This amortizes connection and protocol overhead across many events and returns an awaitable so the caller is not blocked. It is the documented high-throughput pattern for telemetry ingestion.

Answer

event_grid_publisher.upload_blob()

Answer

client.publish_to_service_bus_queue()

Answer

producer.send_single_event_blocking() for every record

Question 2

You are designing an enterprise messaging architecture using Azure Service Bus. Which THREE features are available exclusively in the Premium tier and not in the Standard tier? (Choose three)

Accepted Answer

Virtual Network (VNet) service endpoints and Private Link integration. Option A is correct because network isolation capabilities—VNet service endpoints and Azure Private Link—are Premium-tier-only features that let you restrict Service Bus namespace access to your virtual network, whereas Standard exposes only public endpoints. Option B is correct because Premium provides dedicated, isolated compute and memory resources per namespace (scaling in messaging units), while Standard uses shared multi-tenant infrastructure. Option D is correct because Premium supports large messages up to 100 MB (via the large message support/AMQP claim-check mechanism), while Standard caps message size at 256 KB (or 1 MB for the maximum setting). Option C is not exclusive to Premium: duplicate detection with its configurable message history window is available in both Standard and Premium tiers. Option E is not exclusive either: publishing to Topics and Subscriptions is supported in both Standard and Premium (only Basic lacks Topics).

Answer

Duplicate detection message history windows

Answer

Publishing messages to Topics and Subscriptions

Question 3

Your application publishes messages to an Azure Service Bus queue. Which TWO methods can a C# .NET worker use to settle a message after successful processing? (Choose two)

Accepted Answer

DeadLetterMessageAsync(). Option E, CompleteMessageAsync(), is correct because in the Azure.Messaging.ServiceBus SDK a receiver settles a successfully processed message by calling CompleteMessageAsync() on the ServiceBusReceiver, which deletes the message from the queue and finalizes the PeekLock. Option C, DeadLetterMessageAsync(), is also a valid settlement method: it moves the message to the queue's dead-letter subqueue (with a reason and description) instead of completing it, which is a legitimate way to settle a message when processing cannot succeed. The other options are not settlement methods: PeekLockMessageAsync() (A) is not a real SDK method for settling (peeking/locking is handled via ReceiveMessageAsync/PeekMessageAsync and the PeekLock receive mode), ScheduleMessageAsync() (B) enqueues a new message for future delivery, and CreateMessageBatchAsync() (D) only creates a batch for sending multiple messages.

Answer

PeekLockMessageAsync()

Answer

ScheduleMessageAsync()

Answer

CreateMessageBatchAsync()

Question 4

You are designing a multi-tenant AI document processing system. Tenants upload documents, and events are dispatched via Azure Event Grid. You need to ensure that tenant isolation is maintained and that events are securely delivered to tenant-specific webhook endpoints using Azure AD (Entra ID) authentication. Which authentication mechanism should you configure on the Event Grid subscription?

Accepted Answer

Configure a Managed Identity and Microsoft Entra ID authentication on the Event Grid webhook subscription destination.. Configuring a Managed Identity and Microsoft Entra ID authentication on the Event Grid webhook subscription destination allows Event Grid to authenticate to the webhook using Microsoft Entra ID tokens, ensuring secure delivery. This maintains tenant isolation by using per-tenant identities.

Answer

Configure a Shared Access Signature (SAS) token on the Event Grid topic endpoint.

Answer

Attach an IP firewall rule on the Event Grid namespace to restrict delivery sources.

Answer

Enable Basic Authentication with a static API key in the Event Grid subscription schema settings.

Question 5

You are designing a secure enterprise event-driven architecture. Events published to an Azure Event Grid Domain must be partitioned based on a tenant ID. How should publishers send events to the Event Grid Domain to ensure proper routing to domain topics?

Accepted Answer

Publish events directly to the Event Grid Domain endpoint and specify the subject or topic name within the event structure.. Event Grid Domains are designed as a single publishing endpoint that fans out to thousands of domain topics. Publishers send events to the domain endpoint and set the 'subject' field (or use the topic name in the URL path) so Event Grid routes each event to the correct domain topic based on the tenant ID. This is the native partitioning mechanism for Event Grid Domains and avoids per-tenant endpoint sprawl.

Answer

Send all events to an Azure Service Bus Topic, then configure a logic app to forward them to Event Grid.

Answer

Use Azure Event Hubs capture keys to route events to tenant-specific storage containers.

Answer

Create separate Event Grid custom topics for each tenant and configure an Azure API Management gateway to multiplex the requests.

Question 6

You are architecting a real-time anomaly detection system. Sensor data is ingested into an Azure Event Hub. Due to intermittent network issues between the IoT gateway and Azure, duplicate events are occasionally sent. You need downstream Stream Analytics to process each unique event exactly once within a sliding window. Which Event Hub property should you leverage?

Accepted Answer

Partition Key. Event Hubs supports publisher journaling and offset tracking, but for exact-once processing or deduplication, Stream Analytics utilizes the Event Hub Enqueued Time and Partition ID along with watermark definitions, or you can leverage Event Hubs partition keys to ensure identical events go to the same partition.

Answer

Service Bus Duplicate Detection History Window

Answer

Capture Window Size

Answer

Event Grid Advanced Filtering

Question 7

Your company's security policy requires that all Azure Event Grid namespaces and topics reside within a virtual network and are not accessible over the public internet. Which feature should you implement?

Accepted Answer

Configure Private Endpoints on an Event Grid Premium namespace.. Azure Event Grid Premium tier is the only tier that supports Private Endpoints, which place the namespace/topic on a private IP within your VNet and remove public internet exposure. Private Endpoints use Azure Private Link to map the Event Grid resource to a NIC in your subnet, satisfying the 'no public internet' requirement. Standard and Basic tiers do not support Private Link, so they cannot meet this policy.

Answer

Configure Service Bus Virtual Network rules on a Standard namespace.

Answer

Enable Storage firewall rules on the Event Grid subscription storage account.

Answer

Attach an Azure Application Gateway in front of the Event Grid Standard endpoint.

Question 8

An enterprise AI system uses Azure Service Bus Topics to distribute work items. One of your subscriptions has a high volume of low-priority messages that block high-priority tasks. You want to enable high-priority messages to be processed first without creating separate topics. Which Service Bus feature should you use?

Accepted Answer

Create multiple subscriptions with SQL filters evaluating a custom 'Priority' property.. Service Bus subscriptions can have SQL filters that evaluate message properties. By creating multiple subscriptions with filters on a custom 'Priority' property, high-priority messages can be routed to a subscription that is processed first, without creating separate topics.

Answer

Configure Event Grid advanced filters on the Service Bus topic.

Answer

Enable Service Bus Priority Queueing in the namespace configuration settings.

Answer

Enable Auto-forwarding from the low-priority queue to the dead-letter queue.

Question 9

Your distributed AI system uses Azure Event Hubs with multiple partitions. A downstream machine learning model worker needs to guarantee that all inference requests originating from the same client session are processed by the exact same worker instance and partition in order to maintain conversation context. How should you ensure this?

Accepted Answer

Include a consistent PartitionKey when publishing events to the Event Hub.. Setting a consistent PartitionKey (e.g., the client session ID) on each published event ensures Event Hubs hashes that key to the same partition every time. Since a partition is consumed by exactly one worker at a time, all events for that session are processed in order by the same worker, preserving conversation context.

Answer

Set the Event Hub consumer group owner to exclusive mode.

Answer

Enable Event Hubs Capture with automatic partition balancing.

Answer

Configure a Service Bus session on the Event Hub consumer group.

Question 10

You are integrating an external SaaS platform with your Azure AI architecture using Azure Event Grid. The external partner wants to ensure that the events they receive from your custom topic are authentic and originated from your Event Grid namespace. Which security feature should you advise the partner to verify?

Accepted Answer

Validate the event delivery request using the AEG-Signature HTTP header and webhook HMAC verification.. Azure Event Grid supports webhook authentication via HMAC signature validation. When delivering events to a webhook endpoint, Event Grid includes an AEG-Signature header containing a hash-based message authentication code (HMAC) computed using a secret key that you configure on the event subscription. The partner can verify this signature to confirm the events are authentic and originated from your Event Grid namespace. This is the standard mechanism for validating Event Grid event delivery to external endpoints.

Answer

Check the Azure Active Directory tenant ID in the Event Hubs connection string.

Answer

Verify the SAS token attached to the event payload body.

Answer

Inspect the Storage account access key provided in the event subject.

Question 11

Your team is building a real-time speech transcription pipeline using Azure Event Hubs. Due to intermittent network drops, client applications need to be able to send messages with a scheduled delivery time so they are processed later. Which Azure messaging service supports scheduled message delivery natively?

Accepted Answer

Azure Service Bus. Azure Service Bus natively supports scheduled message delivery via the ScheduledEnqueueTimeUtc property (or ScheduleMessageAsync in the SDK), which holds messages in the queue until a specified future time before releasing them to consumers. This is a first-class feature designed exactly for the scenario described, where clients need to defer processing. Event Hubs, Event Grid, and Storage Queues do not offer this native scheduling capability.

Answer

Azure Event Grid

Answer

Azure Storage Queues

Answer

Azure Event Hubs

Question 12

Your enterprise AI solution utilizes Azure Service Bus Premium. Which THREE features are exclusively available in the Premium messaging tier (or require Premium) compared to the Standard tier? Each correct answer represents a differentiating feature.

Accepted Answer

Dedicated resource allocation (isolated CPU and memory per namespace). Option A is correct because Azure Service Bus Premium provides dedicated resource allocation, giving each namespace isolated CPU and memory so workloads are not affected by noisy neighbors, unlike the multi-tenant Standard tier. Option B is correct because auto-inflate, which automatically scales messaging units to handle throughput spikes, is a Premium-only capability. Option E is correct because network isolation features such as VNet service endpoints and private endpoints (Azure Private Link) require the Premium tier. Option C is not exclusive to Premium, since brokered queues and topics can be created in the Standard tier as well. Option D is not exclusive either, because message sessions for FIFO ordering are supported in the Standard tier, not only Premium.

Answer

Creation of brokered message queues and topics

Answer

Basic message session support for FIFO ordering

Question 13

Your application consumes messages from an Azure Service Bus queue using PeekLock mode. Which THREE actions can your worker code perform on a received message object? Each correct answer represents a valid Service Bus SDK operation.

Accepted Answer

DeadLetterAsync() to move the message to the dead-letter sub-queue. In PeekLock mode, the Service Bus SDK exposes settlement methods on the received message object: CompleteAsync() (option E) marks the message as successfully processed and deletes it from the queue, which is exactly the intended operation for a worker that finished handling the message. AbandonAsync() (option D) releases the lock and makes the message immediately available again for redelivery, which is valid when the worker cannot process the message but wants it retried. DeadLetterAsync() (option C) moves the message to the dead-letter sub-queue, which is valid for messages that are malformed or cannot be processed after retries. Option A is wrong because CommitTransactionAsync() is a method on the ServiceBusTransactionContext/ServiceBusClient transaction object, not on the received message instance. Option B is wrong because CaptureToBlobAsync() is not a Service Bus message operation; message capture/archiving is not performed via a method on the received message in this way.

Answer

CommitTransactionAsync() directly on the message instance

Answer

CaptureToBlobAsync() to archive the message to storage

Question 14

You are deploying an event-driven AI workflow using Azure Service Bus. Which TWO mechanisms help ensure message delivery reliability and prevent data loss during transient outages? Each correct answer represents a valid reliability mechanism.

Accepted Answer

Duplicate detection using a configurable time window. Option A, duplicate detection using a configurable time window, is correct because Azure Service Bus can track a MessageId within a configurable DuplicateDetectionHistoryTimeWindow (default 10 minutes, max 7 days) and silently drop duplicate sends, preventing duplicate processing and data integrity issues during retries caused by transient outages. Option E, dead-lettering queues for handling poison or unprocessable messages, is correct because Service Bus automatically moves messages that exceed MaxDeliveryCount or fail filtering/processing into a dead-letter queue, preserving them for later inspection instead of losing them. Option B is incorrect because Event Hubs partition auto-deletion is not a Service Bus reliability feature and would actually cause data loss. Option C is incorrect because Event Grid webhook retries do not provide infinite retention, and Event Grid is a separate service from Service Bus. Option D is incorrect because Storage Queue client-side polling loops are a different service's pattern and do not by themselves guarantee reliable delivery or prevent data loss in Service Bus.

Answer

Event Hubs partition auto-deletion

Answer

Event Grid webhook retry push loops with infinite retention

Answer

Storage Queue client-side polling loops

Question 15

Your enterprise AI solution requires secure connectivity between Azure Event Grid and private webhook endpoints. Which THREE features support secure, private event delivery? Each correct answer represents a valid security feature.

Accepted Answer

Private Endpoints for inbound event publishing connectivity. Option A is correct because Azure Private Endpoints create a private IP address in your virtual network for the Event Grid topic/domain, enabling inbound event publishing over the Microsoft backbone without exposing traffic to the public internet. Option D is correct because Event Grid supports managed identities (system-assigned or user-assigned) to authenticate webhook deliveries via Microsoft Entra ID tokens, eliminating the need to embed secrets in the subscription. Option E is correct because IP firewall rules on Event Grid topics/domains restrict which source IP addresses are allowed to publish events, providing network-level access control. Option B is not correct because Service Bus SAS keys apply to Service Bus entities, not to Event Grid event subscription webhook authentication. Option C is not correct because anonymous public webhook access bypass headers would weaken security by allowing unauthenticated delivery, which contradicts the requirement for secure, private connectivity.

Answer

Service Bus shared access signature (SAS) keys on event subscriptions

Answer

Anonymous public webhook access bypass headers