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

Question 1

You are building an event-driven AI workflow where an Azure Event Grid event triggers an Azure Function. To ensure that the function handles the Event Grid handshake validation handshake correctly when the subscription is created, what must your function code include?

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

Accepted Answer

Code to handle the SubscriptionValidationEvent and return the validation code.. When Event Grid creates a webhook subscription, it sends a SubscriptionValidationEvent to the endpoint. The function must detect this event type, extract the validationCode from the event data, and return it in the HTTP response so Event Grid can confirm endpoint ownership. Without this handshake handling, the subscription creation fails and events are never delivered.

Answer

An Event Hubs consumer group checkpoint store configuration.

Answer

A Service Bus session lock renewal loop.

Answer

An AMQP listener connection string.

Question 2

Your AI application consumes messages from an Azure Service Bus queue. During peak hours, processing takes longer than expected, and messages are frequently locked out and redelivered prematurely. You want to increase the time a message remains locked by the receiver. Where should you configure this setting?

Accepted Answer

On the Azure Service Bus queue properties by modifying the LockDuration setting.. The LockDuration setting on a Service Bus queue controls how long a message is locked by a receiver before it becomes available for redelivery. Increasing this value prevents premature lock expiration during long processing, directly addressing the described issue.

Answer

On the Event Grid subscription retry interval settings.

Answer

On the Event Hubs consumer group retention period.

Answer

In the Azure Function host.json file under the eventHubs retry policy.

Question 3

An AI pipeline uses Azure Service Bus Queues. You want to inspect the number of messages currently residing in a queue waiting to be processed without actually receiving or locking them. Which Azure Portal section or metric should you check?

Accepted Answer

The Service Bus Queue 'Overview' blade displaying Active Message Count metrics.. The Service Bus Queue 'Overview' blade in the Azure Portal displays the Active Message Count metric, which reports the number of messages currently in the queue that are ready to be received. This is a non-destructive metric — it does not lock or receive messages — and is the standard way to inspect queue depth.

Answer

The Azure Storage Account queued message monitoring graphs.

Answer

The Event Grid subscription delivery status log.

Answer

The Event Hubs capture storage container file list.

Question 4

You are designing an enterprise event-driven architecture for AI workloads. Which TWO Azure services provide native support for publishing discrete, reactive event notifications when resources are created or modified? Each correct answer represents a complete solution.

Accepted Answer

Azure Blob Storage (native event notifications). Azure Blob Storage natively supports event notifications that fire discrete, reactive events such as Microsoft.Storage.BlobCreated and Microsoft.Storage.BlobDeleted when blobs are created or modified, which fits the requirement for resource-change notifications. Azure Event Grid is a fully managed publish-subscribe eventing service that natively delivers discrete, reactive event notifications from Azure resources (including Blob Storage) to subscribers via event subscriptions, making it the canonical service for this scenario. Azure Notification Hubs is a push-notification service for mobile/consumer devices (APNs, FCM, WNS), not a resource-event publisher. Azure Event Hubs is a big-data streaming/telemetry ingestion service (high-throughput event streaming), not a discrete resource-change notification publisher. Azure Service Bus Queues are a brokered messaging construct for commands/messages with queuing semantics, not native resource event notifications.

Answer

Azure Notification Hubs

Answer

Azure Event Hubs

Answer

Azure Service Bus Queues

Question 5

Your enterprise architecture uses Azure Service Bus Topics and Subscriptions with geo-disaster recovery paired namespaces. A disaster occurs, and you trigger a failover to the secondary region. What happens to the messages currently in the subscriptions of the primary namespace?

Accepted Answer

Messages remaining in the primary namespace are not automatically replicated to the secondary namespace; failover relies on metadata synchronization.. Service Bus geo-disaster recovery (Geo-DR) pairs a primary and secondary namespace and continuously replicates only the namespace metadata — queues, topics, subscriptions, filters, and authorization rules. Message data itself is not replicated, so messages sitting in the primary namespace's subscriptions at the moment of failover are not available in the secondary namespace and are effectively stranded until the primary is restored.

Answer

All queued messages are automatically migrated to the secondary region within 5 seconds.

Answer

Azure Event Grid automatically replays all lost messages from the storage capture.

Answer

The primary namespace messages are permanently deleted and cannot be recovered.

Question 6

Your AI processing pipeline requires high-throughput streaming ingestion and retention of telemetry data. Which THREE features or capabilities are native to Azure Event Hubs? Each correct answer represents a complete capability.

Accepted Answer

Event Hubs Capture for automatically batching and saving stream data to Azure Storage. Option A is correct because Event Hubs Capture is a native feature that automatically batches streaming data and writes it to Azure Blob Storage or Azure Data Lake Storage (in Avro format) based on a time or size window, satisfying the retention requirement without custom code. Option C is correct because Consumer Groups are a native Event Hubs construct that lets multiple independent applications each maintain their own offset and read the same event stream independently, which is essential for multiple downstream consumers. Option D is correct because Event Hubs partitions the stream and allows multiple receivers to process partitions in parallel, which is the foundation of its high-throughput streaming ingestion and parallel processing model. Option B is not correct because Event Hubs does not natively push events via webhooks for serverless triggers; that pattern belongs to Event Grid, whereas Event Hubs uses AMQP/Kafka pull-based consumption. Option E is not correct because automatic dead-lettering based on a MaxDeliveryCount threshold is a Service Bus queue/subscription feature, not a native Event Hubs capability.

Answer

Native webhook push delivery for discrete serverless event triggers

Answer

Automatic dead-lettering of messages exceeding a MaxDeliveryCount threshold

Question 7

When designing an event-driven architecture using Azure Event Grid, which THREE security or delivery mechanisms can be configured on an event subscription? Each correct answer represents a valid configuration option.

Accepted Answer

Advanced filtering based on event data property values. Option B is correct because Event Grid event subscriptions support advanced filtering, which evaluates event data fields (such as string, number, boolean, and arrays) against operators like StringContains, NumberGreaterThan, and BoolEquals to route only matching events. Option C is correct because an event subscription can define a dead-letter destination, which must be an Azure Blob Storage container, where undeliverable events are stored along with a reason for delivery failure. Option E is correct because Event Grid supports using a managed identity (system-assigned or user-assigned) on the event subscription to authenticate delivery to supported destinations such as webhooks and Service Bus, avoiding embedded secrets. Option A is not applicable because AMQP 1.0 broker transaction coordination is a Service Bus/AMQP messaging concept, not an Event Grid subscription setting. Option D is not applicable because Service Bus session lock duration is a Service Bus queue/subscription feature and cannot be configured on an Event Grid event subscription.

Answer

AMQP 1.0 broker transaction coordination

Answer

Service Bus session lock duration extension

Question 8

You are configuring an Azure Service Bus Topic and Subscriptions for an AI text classification system. Which THREE filter types are supported on Service Bus subscriptions for routing messages? Each correct answer represents a valid filter type.

Accepted Answer

Boolean Filters (True/False filters). Service Bus subscriptions support exactly three filter types: Boolean filters, SQL filters, and Correlation filters. Option A (Boolean Filters) is correct because a TrueFilter (1=1) captures all messages to a subscription and a FalseFilter (1=0) blocks all messages, which is useful for a catch-all or disabled subscription in the classification pipeline. Option D (SQL Filters) is correct because they use SQL-like expressions evaluated against message system and user properties (for example, sys.Label='sports' AND priority>5), enabling content-based routing of text classification messages. Option E (Correlation Filters) is correct because they match on properties such as CorrelationId, MessageId, Label, ReplyTo, and custom properties, providing efficient exact-match routing for AI workloads. Option B (Regex Pattern Matching Filters) is not a supported Service Bus filter type, and Option C (Machine Learning Inference Filters) does not exist as a native subscription filter; both are invalid for this scenario.

Answer

Regex Pattern Matching Filters

Answer

Machine Learning Inference Filters

Question 9

Your team is comparing Azure Event Grid, Event Hubs, and Service Bus for an AI platform integration project. Which THREE statements correctly contrast these services? Each correct answer is factually accurate.

Accepted Answer

Event Grid is optimized for pub/sub discrete event notifications with push delivery.. Option B is correct because Event Grid is purpose-built for reactive, discrete-event pub/sub scenarios and pushes events to subscribers via webhooks or Azure service handlers, making it ideal for serverless triggers. Option C is correct because Event Hubs is a big-data streaming platform engineered for high-throughput telemetry and event ingestion (millions of events per second) with partitioned consumer groups and retention, not discrete notification routing. Option E is correct because Service Bus is the enterprise brokered-messaging service offering transactions, sessions for strict FIFO ordering, dead-lettering, duplicate detection, and scheduled delivery. Option A is wrong because native webhook push delivery for serverless triggers is an Event Grid capability, not Event Hubs, which requires consumers to pull from partitions (or use the Kafka/AMQP endpoints). Option D is wrong because AMQP 1.0 session-based strict FIFO ordering is a Service Bus feature, not Event Grid, which delivers discrete events with at-least-once semantics and no ordering guarantees.

Answer

Event Hubs provides native webhook push delivery for serverless triggers without consumer code.

Answer

Event Grid supports AMQP 1.0 session-based strict FIFO message ordering.

Question 10

You are troubleshooting an Azure Function triggered by an Azure Event Grid subscription. The function is failing to receive events. Which TWO diagnostic steps should you take in the Azure Portal or via Azure CLI? Each correct answer is a valid troubleshooting action.

Accepted Answer

Inspect the configured dead-letter blob storage container for undelivered event files.. Option A is correct because Event Grid supports a dead-letter destination (a Storage blob container) where events are written when they cannot be delivered to the subscriber, so inspecting that container reveals undelivered event files and their failure reasons. Option C is correct because Event Grid exposes metrics such as Delivery Failed Events, Dropped Events, and Matched Events in Azure Monitor, which directly show whether events are being matched to the subscription and whether delivery to the function is failing. Option B is not applicable because AMQP port 5671 is used by Service Bus and Event Hubs, not by Event Grid, which delivers events over HTTPS (port 443) to webhook/function endpoints. Option D is not applicable because Service Bus session lock renewal is a Service Bus feature unrelated to Event Grid subscriptions. Option E is not applicable because Event Hubs consumer group checkpoints relate to Event Hubs consumption, not to Event Grid event delivery to an Azure Function.

Answer

Verify the AMQP listener port 5671 firewall rules on the function app.

Answer

Review Service Bus session lock renewal logs.

Answer

Check Event Hubs consumer group checkpoint offset status.

Question 11

You are architecting an asynchronous machine learning inference pipeline. Which TWO Azure services allow you to decouple event publishers from event consumers using a publish-subscribe (pub/sub) pattern? Each correct answer represents a valid pub/sub architecture service.

Accepted Answer

Azure Event Grid. Azure Event Grid (A) is correct because it is a fully managed event-routing service that implements the pub/sub pattern: publishers emit events to topics and multiple subscribers receive them via event subscriptions with filters, enabling full decoupling of producers and consumers. Azure Service Bus Topics (E) is correct because a topic supports the publish-subscribe model where each subscriber creates its own subscription and receives a copy of every message, providing decoupled, asynchronous delivery with features like filters and sessions. Azure Notification Hubs (B) is a push-notification broadcast service for mobile devices, not a general event pub/sub backbone for decoupling publishers and consumers. Azure Storage Queues (C) implements point-to-point queue messaging where each message is consumed by a single receiver, not a fan-out pub/sub pattern. Azure Event Hubs Capture (D) is a feature that automatically persists streaming data to Blob Storage or Data Lake, not a pub/sub decoupling service.

Answer

Azure Notification Hubs

Answer

Azure Storage Queues

Answer

Azure Event Hubs Capture

Question 12

When designing an Azure Event Hubs streaming pipeline for AI telemetry, which THREE components or configurations are required to consume events reliably using the EventProcessorClient? Each correct answer represents a necessary element.

Accepted Answer

A Checkpoint Store (such as an Azure Blob Storage container client). Option A is correct because EventProcessorClient requires a CheckpointStore (typically backed by an Azure Blob Storage container client) to persist checkpoints and ownership information so partitions can be processed reliably and resumed after failures. Option C is correct because a Consumer Group name is mandatory when constructing the EventProcessorClient, as it defines the logical view of the event stream that the processor reads from and isolates offsets/checkpoints per group. Option E is correct because the client must be given the Event Hubs namespace connection string and the specific Event Hub name to connect and receive events. Option B is incorrect because Event Hubs is not Service Bus, so no Service Bus subscription connection is involved. Option D is incorrect because Event Grid custom topics are for event routing/notification, not for consuming Event Hubs streams with EventProcessorClient.

Answer

An active Azure Service Bus subscription connection

Answer

An Event Grid custom topic endpoint URL

Question 13

Your team is building an AI solution that processes thousands of images uploaded to Azure Blob Storage daily. Each image upload must trigger an immediate Azure Function to invoke Azure Cognitive Services for metadata extraction. Which event-driven messaging service should you choose for this near real-time pub/sub architecture?

Accepted Answer

Azure Event Grid. Azure Event Grid is purpose-built for near real-time, event-driven pub/sub with native first-class integration to Blob Storage events (BlobCreated) and Azure Functions. It pushes events within milliseconds of the blob upload, making it the correct choice for triggering a Function that calls Cognitive Services for metadata extraction.

Answer

Azure Service Bus Topics

Answer

Azure Storage Queues

Answer

Azure Event Hubs

Question 14

An AI system uses Azure Service Bus queues for processing text-generation jobs. A specific job causes the worker function to crash repeatedly, leading to the message being redelivered continuously. Which Service Bus feature should you configure to capture these poison messages after a specific delivery count is reached?

Accepted Answer

Dead-letter queue (DLQ). The dead-letter queue (DLQ) captures messages that cannot be processed successfully after a specified number of delivery attempts. By configuring the queue's MaxDeliveryCount, you can automatically move poison messages to the DLQ after they exceed that count, preventing infinite redelivery loops. This allows you to inspect and handle problematic messages separately.

Answer

Duplicate detection

Answer

Autoforwarding

Answer

Partitioning

Question 15

Your development team is implementing an event-driven microservices architecture using Azure Service Bus. You need to ensure strict FIFO (First-In, First-Out) message processing order for related financial transaction events in an AI fraud-detection workflow. Which THREE configuration steps are required? (Choose three)

Accepted Answer

Implement a MessageSession receiver in your client application to process messages sequentially per session.. Option D is correct because sessions must be explicitly enabled on the Service Bus queue (via the EnableSession property) before session-based FIFO ordering can be used; without this, session IDs are ignored. Option B is correct because setting a Session ID on all related financial transaction messages groups them into the same session, guaranteeing that messages with the same SessionId are delivered in order. Option A is correct because the receiving client must use a MessageSession receiver (via AcceptMessageSessionAsync) to process each session's messages sequentially and in FIFO order. Option C is not required because partitioning is a throughput/availability feature and does not provide FIFO ordering; in fact, partitioned entities without sessions do not guarantee ordering. Option E is not required because duplicate detection only prevents duplicate message submission within the history window and has no role in enforcing FIFO processing order.

Answer

Configure partitioning on the Service Bus namespace tier.

Answer

Enable duplicate detection with a 10-minute history window.