AI-200 Event Driven Integration — 50 Questions

Question 1

You are integrating an Azure Event Hubs namespace with Azure Machine Learning for real-time model training. You need to archive raw telemetry data into Azure Data Lake Storage Gen2 in Apache Parquet format without writing custom code. Which feature should you enable?

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

Accepted Answer

Event Hubs Capture. Event Hubs Capture is the built-in feature that automatically writes streaming data from an Event Hub to Azure Blob Storage or Azure Data Lake Storage Gen2 in Avro or Parquet format without custom code. It is configured at the Event Hub level with a capture window (size or time) and a destination, making it the correct no-code archival solution. This directly satisfies the requirement to archive raw telemetry to ADLS Gen2 in Parquet.

Answer

Event Grid system topic with a Storage Blob export endpoint

Answer

Azure Stream Analytics job with a Blob output sink

Answer

Service Bus Geo-Disaster Recovery replication

Question 2

You are designing an AI application that needs to route real-time telemetry events from thousands of IoT devices to multiple downstream serverless functions simultaneously. Which Azure service should you use as the event broker?

Accepted Answer

Azure Event Grid. Azure Event Grid is a fully managed event routing service that uses a publish-subscribe model, allowing events to be delivered to multiple subscribers simultaneously. It is designed for high-scale, real-time event distribution from sources like IoT devices to serverless functions, with built-in support for filtering and fan-out. The [CORRECT] option is Event Grid because it natively supports the fan-out pattern required to route telemetry to multiple downstream functions concurrently.

Answer

Azure Service Bus Queues

Answer

Azure Event Hubs

Answer

Azure Blob Storage

Question 3

You are designing a message-based architecture in Azure Service Bus where certain high-priority messages must bypass standard messages in the queue and be processed immediately. What feature should you implement?

Accepted Answer

Implement custom application logic that peeks and receives messages by sequence number, while utilizing multiple queues for high versus low priority.. The correct approach is to implement custom application logic that peeks and receives messages by sequence number, while utilizing multiple queues for high versus low priority. Azure Service Bus does not have a built-in message priority feature. To achieve priority processing, you must design your solution with separate queues for different priority levels and have consumers process high-priority queues first. Alternatively, you can use the PeekLock mode to inspect messages and selectively receive based on sequence number, but this is complex and not recommended for high throughput.

Answer

Enable Express Queues to bypass disk I/O for high-priority messages.

Answer

Configure Event Grid priority routing filters.

Answer

Set the Priority property on the BrokeredMessage header to 10.

Question 4

Your organization uses Azure Event Grid to route cloud events across different departments. Security auditors require that all event traffic destined for a webhook endpoint is authenticated using Azure Active Directory (Microsoft Entra ID) bearer tokens. How should you configure the event subscription?

Accepted Answer

Configure a Managed Identity on the event subscription and select the target audience.. Event Grid supports Microsoft Entra ID (Azure AD) authentication for webhook delivery via managed identities. When you configure a managed identity on the event subscription and specify the target audience (the App ID URI of the destination webhook), Event Grid obtains a bearer token from Entra ID and includes it in the Authorization header of the delivery request. This satisfies the auditor requirement that all event traffic to the webhook is authenticated with Entra ID bearer tokens.

Answer

Enable IP firewall rules on the Event Grid topic to restrict traffic.

Answer

Use Basic Authentication with a static API key stored in App Settings.

Answer

Embed a Shared Access Signature (SAS) token directly in the webhook URL query parameters.

Question 5

Your team needs to monitor when virtual machines are created or deleted across an entire Azure subscription so that an automated audit logger is triggered. Which Azure service should you use to capture these management plane operations?

Accepted Answer

Azure Event Grid. Azure Event Grid is the event-routing service designed to react to Azure resource management events, including virtual machine creation and deletion. Azure Resource Manager publishes these management-plane events to Event Grid, and you create an event subscription that pushes them to a handler such as an Azure Function or Logic App that performs the audit logging. This is the canonical serverless, push-based pattern for reacting to resource lifecycle changes across a subscription.

Answer

Azure Logic Apps

Answer

Azure Service Bus

Answer

Azure Event Hubs

Question 6

You are optimizing the cost and performance of an Azure Event Hubs namespace processing millions of financial telemetry records daily. Traffic fluctuates heavily between business hours and night time. You want to ensure the namespace scales automatically without manual intervention while bounding maximum costs. What should you configure?

Accepted Answer

Enable Auto-Inflate and set the maximum Throughput Units limit.. Auto-Inflate is the native Event Hubs feature that automatically scales Throughput Units (TUs) upward when ingress/egress exceeds the current allocation, and setting a maximum TU limit caps the cost ceiling. This satisfies both requirements: automatic scaling during business-hour spikes and a bounded maximum spend. It requires the namespace to be on a Standard, Premium, or Dedicated tier (not Basic).

Answer

Set the retention period to 1 hour to reduce storage overhead.

Answer

Configure an Azure Autoscale rule on the Event Hubs Resource Group via Azure Monitor.

Answer

Upgrade the namespace to Azure Service Bus Premium with partitioned entities.

Question 7

You are integrating Azure Event Hubs with Apache Spark on Azure Databricks for real-time AI model scoring. You need to configure the Spark connector to read from all partitions of the Event Hub efficiently without missing records or creating duplicate processing bottlenecks. Which consumer property is critical to configure correctly?

Accepted Answer

A dedicated Consumer Group and correct starting offset configuration (e.g., startingPosition).. When reading from Azure Event Hubs with the Spark connector, the critical consumer-side configuration is a dedicated Consumer Group plus a correct starting offset (e.g., startingPosition set to earliest, latest, or a specific offset). This ensures each Spark job reads all partitions exactly once without duplicating another consumer's progress or skipping records.

Answer

Setting the Event Grid webhook handshake timeout to 120 seconds.

Answer

Enabling AMQP 1.0 web socket transport mode across all Spark worker nodes.

Answer

The Service Bus shared access policy connection string with Manage rights.

Question 8

You are configuring disaster recovery for an Azure Event Hubs namespace. You have established a geo-recovery pairing between a primary and secondary namespace. A failover has been executed. How should you re-establish replication back to the original primary namespace once it recovers?

Accepted Answer

Establish a new geo-recovery pairing or reverse the roles so the old primary becomes the secondary namespace.. After a failover in Azure Event Hubs geo-recovery, the original primary namespace becomes the secondary. To re-establish replication back to the original primary once it recovers, you must either create a new geo-recovery pairing or reverse the roles so that the old primary becomes the secondary namespace again. This re-enables replication from the new primary to the old primary.

Answer

Run the az eventhubs namespace sync command from the Azure CLI.

Answer

Delete both namespaces and recreate them using an Azure Resource Manager template.

Answer

Update the consumer group offsets manually on both namespaces.

Question 9

You are building an event-driven architecture where an Azure Function needs to process messages from an Azure Service Bus queue. To optimize cost and resource utilization during quiet periods, you want the Azure Function host to scale down to zero instances when the queue is empty, and scale out rapidly when messages arrive. Which hosting plan should you choose?

Accepted Answer

Azure Functions Premium Plan or Consumption Plan. The Azure Functions Premium Plan and Consumption Plan both support event-driven scaling, including scaling to zero instances when there are no events. The Consumption Plan is purely serverless and scales automatically based on event volume, while the Premium Plan offers pre-warmed instances and VNet integration but still scales to zero when idle. Both plans integrate natively with Azure Service Bus triggers, allowing the Function host to scale out rapidly when messages arrive and scale back to zero during quiet periods, optimizing cost and resource utilization.

Answer

Azure Virtual Machines with autoscale rules

Answer

Azure App Service Dedicated (App Service Plan - S1 tier)

Answer

Azure Kubernetes Service with manual pod scaling

Question 10

You are configuring an Azure Service Bus queue. Business requirements state that messages must automatically expire if they are not consumed within 30 minutes. Which property should you set on the queue definition?

Accepted Answer

DefaultMessageTimeToLive. DefaultMessageTimeToLive defines how long a message remains in the queue before it expires and is moved to the dead-letter queue (if enabled) or removed. Setting it to 30 minutes ensures messages that are not consumed within that window are automatically expired, satisfying the business requirement. This property applies to the queue and can be overridden per message.

Answer

DuplicateDetectionHistoryTimeWindow

Answer

LockDuration

Answer

AutoDeleteOnIdle

Question 11

Your application publishes custom events to Azure Event Grid using the CloudEvents 1.0 schema format. Which required attribute must be present in every CloudEvents JSON payload to ensure valid delivery?

Accepted Answer

specversion, type, source, and id. CloudEvents 1.0 defines a set of required context attributes that every event must carry: specversion, type, source, and id. Azure Event Grid enforces these when publishing with the CloudEvents schema, so omitting any of them causes the event to be rejected or fail validation. These four attributes identify the schema version, the event type, the originating context, and a unique identifier for the event.

Answer

PartitionKey and SequenceNumber

Answer

sb-connection-string and topic-name

Answer

authorization and aeg-sas-key

Question 12

You are writing a C# .NET console application that sends batch messages to an Azure Service Bus queue. To maximize performance and avoid exceeding payload size limits, how should you construct and send the batch?

Accepted Answer

Use ServiceBusSender.CreateMessageBatchAsync() to dynamically package messages up to the maximum batch size limit.. ServiceBusSender.CreateMessageBatchAsync() dynamically packages messages into a batch that respects the maximum batch size limit (256 KB for Standard, 1 MB for Premium), throwing or excluding messages that would exceed it. This is the correct way to maximize throughput while avoiding payload size errors when sending batches to a Service Bus queue.

Answer

Use individual SendMessageAsync calls inside a parallel Task.WhenAll loop.

Answer

Compress the entire list of messages into a single string and send it as an Event Grid webhook payload.

Answer

Add all 10,000 messages into a single List<ServiceBusMessage> and call SendMessagesAsync directly.

Question 13

Your application publishes messages to an Azure Service Bus topic. You want to ensure that messages published to the topic are automatically archived into an Azure Storage container for long-term auditing. Which native feature should you configure?

Accepted Answer

Deploy an Azure Function or Logic App triggered by the Service Bus topic subscriptions to write messages to Azure Blob Storage.. Azure Service Bus does not have a native 'Capture' feature like Event Hubs; however, you can configure Auto-Forwarding to a queue or use Azure Logic Apps / Azure Functions triggered by Service Bus to archive messages. (Wait, let's look closely at Service Bus features: Service Bus does not have native Capture like Event Hubs. Therefore, you must use an integration pattern like Azure Functions or Logic Apps).

Answer

Enable Geo-Disaster Recovery with Blob Storage as the secondary target.

Answer

Enable Service Bus Capture mode in the namespace configuration blade.

Answer

Configure Event Grid automated blob export on the topic.

Question 14

Your organization uses Azure Service Bus Queues. A downstream processing service is undergoing maintenance and will be offline for 4 hours. You want to temporarily pause message processing without losing messages or triggering dead-letter timeouts. What is the recommended approach?

Accepted Answer

Set the queue status to 'Disabled' via the Azure Portal or SDK.. Setting the Service Bus queue status to 'Disabled' pauses all receive operations while the queue retains messages and continues to accept sends. This preserves messages without triggering dead-lettering and is reversible by setting the status back to 'Active'.

Answer

Export all messages to Azure Blob Storage and purge the queue.

Answer

Delete the Service Bus queue and recreate it when maintenance finishes.

Question 15

Your application publishes custom events to an Azure Event Grid topic. You want to ensure that the webhook endpoint receiving these events can verify that the request genuinely originated from Event Grid. Which validation mechanism should your webhook implement?

Accepted Answer

Validate the validation handshake request during setup and check the aeg-signature header on incoming event deliveries.. Azure Event Grid uses a two-part security model for webhook endpoints: an initial validation handshake and per-event signature verification. During subscription creation, Event Grid sends a validation event that your endpoint must echo back to prove ownership; thereafter, each event delivery includes an aeg-signature header containing an HMAC-SHA256 hash of the event payload using a secret key. Validating this signature ensures the request truly originated from Event Grid and was not tampered with in transit.

Answer

Require mutual TLS client certificates issued by the consumer app.

Answer

Verify the client's SQL Server connection string.

Answer

Check that the incoming IP address matches Azure Blob Storage storage IPs.

Question 16

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?

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 17

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 18

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 19

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 20

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.