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

Question 1

An application publishes custom events to an Azure Event Grid custom topic. You need to route events dynamically based on the event's 'department' property in the event payload. Which filtering mechanism should you configure on the Event Grid subscription?

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

Accepted Answer

Advanced Filters. Advanced Filters in Azure Event Grid allow filtering based on any property within the event payload, including custom properties like 'department'. They support operators such as string comparisons, numeric comparisons, and boolean logic, enabling dynamic routing based on event data. This is the correct mechanism because the requirement is to filter on a custom property in the event schema, which Advanced Filters are designed to handle.

Answer

Event Hubs Capture filters

Answer

Subject Begins With/Ends With filters

Answer

Service Bus Correlation Filters

Question 2

You are designing an asynchronous AI image classification workflow. Client applications upload images to Azure Blob Storage and need to be notified immediately when processing completes. The notification must include custom metadata generated by the AI worker. Which architecture should you implement?

Accepted Answer

The AI worker publishes a custom event to an Azure Event Grid Topic upon completion.. The AI worker publishing a custom event to an Azure Event Grid Topic upon completion is correct because Event Grid supports custom events with metadata and can push notifications to subscribers immediately. This allows clients to receive the custom metadata generated by the worker. Other options do not provide immediate notification with custom metadata.

Answer

Use Azure Service Bus topics with session IDs set to the image hash.

Answer

Configure an Azure Storage queue that triggers whenever a blob is modified.

Answer

Poll the Azure Blob Storage container metadata every 5 seconds from the client app.

Question 3

Your organization requires that all messages sent to an Azure Service Bus Premium namespace are encrypted using customer-managed keys (CMK) stored in Azure Key Vault. Where must you configure this encryption setting?

Accepted Answer

At the Service Bus Namespace level. Customer-managed key (CMK) encryption for Azure Service Bus is configured at the namespace level, where you specify the Key Vault key and managed identity used to access it. This setting applies to all queues and topics within the namespace, ensuring data at rest is encrypted with your key. Namespace-level configuration is the only supported scope for CMK in Service Bus.

Answer

Inside the Event Grid subscription endpoint URI

Answer

At the individual Queue or Topic level

Answer

Within the Azure Function consumer application configuration

Question 4

You are architecting an AI-driven video analytics pipeline using Azure Event Hubs. You need to ensure that frames belonging to the exact same video session are processed in strict chronological order by the same backend stream analytics worker. How should you partition your Event Hub?

Accepted Answer

Include the video session ID as the Partition Key when publishing events to the Event Hub.. Event Hubs guarantees ordering only within a partition, so all events sharing the same partition key are routed to the same partition and delivered in order to a single consumer. Using the video session ID as the partition key ensures every frame from a session lands on one partition, where one stream analytics worker processes them chronologically. This is the standard pattern for session affinity and ordered processing in Event Hubs.

Answer

Increase the consumer group count to match the number of active video sessions.

Answer

Set the message TTL to zero and enable capture mode on the Event Hub namespace.

Answer

Deploy an Azure Service Bus Session-enabled queue in front of the Event Hubs ingestion layer.

Question 5

You are developing a serverless application using Azure Functions that reacts to Azure Blob Storage creation events. Which event schema format should your function code expect by default when triggered by an Event Grid subscription?

Accepted Answer

Azure Event Grid schema. Azure Functions triggered by an Event Grid subscription receive events in the Azure Event Grid schema by default. This schema includes fields like `id`, `subject`, `data`, `eventType`, `eventTime`, and `dataVersion`, with the actual blob details nested under `data`. The function code must deserialize this JSON structure to access properties such as the blob URL. No additional configuration is needed to use this default schema.

Answer

Apache Kafka record batch schema

Answer

AMQP 1.0 message envelope

Answer

SOAP XML envelope

Question 6

You are configuring geo-disaster recovery for an Azure Service Bus Premium namespace containing critical financial transactions. A regional outage occurs. After initiating a failover to the secondary region, what happens to the alias pointing to the namespace?

Accepted Answer

The alias automatically points to the secondary namespace, and pairing is broken.. After a geo-disaster recovery failover in Azure Service Bus Premium, the alias automatically points to the secondary namespace and the pairing between primary and secondary is broken. The alias is a stable connection string endpoint that clients use, so applications do not need to change connection strings; however, the former primary becomes unusable until it is re-paired. This is the documented behavior of Service Bus Geo-DR failover.

Answer

The secondary namespace remains in Read-Only mode until manually unlocked.

Answer

The alias becomes invalid, and you must deploy a new Service Bus namespace from scratch.

Answer

Unreplicated messages in the primary queue are automatically migrated in real-time.

Question 7

Your Azure Event Hubs namespace is experiencing high throughput spikes from AI inference nodes. You notice that some client producers are receiving 'QuotaExceededException' errors. What is the root cause and how should you remediate it?

Accepted Answer

Ingress or egress limits have been exceeded; enable Auto-Inflate on the Event Hubs namespace.. QuotaExceededException in Azure Event Hubs is thrown when the namespace's throughput unit (TU) or processing unit (PU) capacity is saturated — specifically when ingress or egress rates exceed the provisioned limits. Enabling Auto-Inflate automatically scales the TU count (up to a configured maximum) to absorb the spike, which is the correct remediation for bursty AI inference workloads. Auto-Inflate is the native elasticity mechanism for Event Hubs and directly addresses the quota breach.

Answer

The partition count has been exceeded; decrease the number of consumer groups.

Answer

The SAS token has expired; regenerate the connection string.

Answer

The message retention period has expired; increase retention days.

Question 8

You are implementing distributed tracing across an event-driven AI workflow that passes messages from Azure Service Bus to Azure Functions, and finally to an Azure Cosmos DB database. Which mechanism should you use to propagate correlation context between these services?

Accepted Answer

W3C Trace Context standard HTTP headers (such as traceparent) propagated through Service Bus message user properties.. Distributed tracing across Azure services relies on the W3C Trace Context standard, which defines headers like traceparent and tracestate to propagate correlation IDs. In Service Bus, these can be carried in message user properties (application properties) so that downstream services like Azure Functions and Cosmos DB can continue the trace. This enables end-to-end visibility in Application Insights.

Answer

Enabling Azure Monitor diagnostic logs on the storage account.

Answer

Using AMQP 1.0 session locks to lock the trace state across network boundaries.

Answer

Custom GUID generation stored exclusively in the Event Grid event subject field.

Question 9

Your team needs to process high-volume clickstream data from a web application using Apache Kafka protocols while leveraging Azure-managed infrastructure. Which Azure service should you deploy?

Accepted Answer

Azure Event Hubs. Azure Event Hubs is a fully managed, real-time data ingestion service that supports the Apache Kafka protocol via its Kafka endpoint. It is designed for high-throughput event streaming and can handle clickstream data at scale. By deploying Event Hubs, you can use Kafka producers and consumers without managing Kafka clusters.

Answer

Azure Event Grid

Answer

Azure Notification Hubs

Answer

Azure Service Bus

Question 10

An event subscriber endpoint hosted on an Azure App Service web app is failing to receive events from an Azure Event Grid system topic. Upon investigation, you discover Event Grid received a handshake validation failure. What is the most likely cause?

Accepted Answer

The web app did not correctly handle and echo back the validation code during the Webhook handshake.. Event Grid requires a webhook validation handshake when a new event subscription is created. The subscriber endpoint must respond to the validation event by echoing back the validation code within a short timeout. If the web app fails to handle this handshake—for example, by not returning the validation code or returning an error—Event Grid marks the subscription as failed and does not deliver events. The most likely cause is that the web app did not correctly process and echo the validation code.

Answer

The event payload exceeded the 1 megabyte size limit.

Answer

The Service Bus connection string was incorrectly formatted.

Answer

The App Service pricing tier does not support HTTPS connections.

Question 11

You are writing a Python worker application that consumes messages from an Azure Service Bus queue. To prevent message loss during unexpected application crashes, you need to ensure that messages are locked while being processed and only deleted from the queue after successful processing. Which receive mode should you use?

Accepted Answer

PeekLock mode. PeekLock mode is correct because it locks the message for a configurable duration while the consumer processes it, and the message is only deleted after the consumer explicitly completes it. If the application crashes, the lock expires and the message becomes available again, preventing message loss. ReceiveAndDelete would remove the message immediately upon receipt, risking loss on failure.

Answer

Deferred mode

Answer

SessionLock mode

Answer

ReceiveAndDelete mode

Question 12

You are designing a multi-tenant AI ingestion pipeline using Azure Event Hubs. You need to ensure that low-priority tenants cannot starve high-priority tenants of partition resources. Which feature should you implement?

Accepted Answer

Deploy separate Event Hubs namespaces for high-priority and low-priority tenants.. Event Hubs throughput and partition resources are scoped to a namespace, so tenants sharing a single namespace compete for the same throughput units and partitions. Deploying separate namespaces for high-priority and low-priority tenants physically isolates their throughput units, partitions, and throttling limits, preventing noisy-neighbor starvation. This is the standard multi-tenant isolation pattern for Event Hubs.

Answer

Set the Capture interval to 60 seconds for low-priority partitions.

Answer

Configure RBAC permissions to restrict low-priority tenants to Reader roles.

Answer

Enable Azure DDoS Protection Standard on the Event Hubs consumer group.

Question 13

You are troubleshooting a high-throughput stream processing pipeline using Azure Event Hubs. Consumers are experiencing lag because messages are accumulating faster than they can be processed. You want to temporarily replay historical events from 2 hours ago without altering the current consumer group offsets permanently. What should you do?

Accepted Answer

Create a new temporary consumer group and initialize the event receiver with a custom starting offset based on enqueued timestamp.. Creating a new temporary consumer group and initializing the event receiver with a custom starting offset based on enqueued timestamp is correct because it allows replaying historical events without affecting the existing consumer group's offsets. The new consumer group starts from a specified time, and the original group continues from its current position. Other options do not achieve this.

Answer

Enable Geo-Disaster Recovery to force the secondary region to sync historical logs.

Answer

Delete the existing consumer group and recreate it with a 2-hour retention limit.

Answer

Purge all messages from the Event Hub using the Azure CLI az eventhubs purge command.

Question 14

You are building an event-driven application where messages sent to an Azure Service Bus queue must not be processed until a specific date and time in the future (e.g., 2 hours from now). What property should you set on the outgoing message?

Accepted Answer

ScheduledEnqueueTimeUtc. ScheduledEnqueueTimeUtc is the Service Bus message property that defers a message's visibility in the queue until a specified UTC timestamp. Setting it to two hours in the future means the broker holds the message and only makes it available to receivers after that time, exactly matching the delayed-processing requirement. This is the native, broker-side scheduling mechanism for Service Bus.

Answer

TimeToLive

Answer

LockDuration

Answer

SequenceNumber

Question 15

Your application publishes events to an Azure Event Grid topic. You want to ensure that event publishers must present a valid shared access signature or key in the HTTP request header. Which header name does Event Grid expect for key-based authentication?

Accepted Answer

aeg-sas-key. Azure Event Grid accepts key-based authentication via the 'aeg-sas-key' HTTP header, which carries the topic or domain access key. Publishers include this header to authenticate without needing an Microsoft Entra ID token, and Event Grid validates it against the topic's configured keys.

Answer

Authorization

Answer

x-functions-key

Answer

sb-connection-string