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

Question 1

You are building an order processing system with Azure Service Bus. Multiple clients might accidentally submit the exact same order twice within a 60-second window due to network retries. You need to prevent duplicate orders from entering the queue. What should you configure?

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

Accepted Answer

Enable Duplicate Detection on the queue and set the history time window to 60 seconds.. Azure Service Bus Duplicate Detection uses a DuplicateDetectionHistoryTimeWindow to track MessageId values of recently sent messages. When enabled, the broker rejects messages with the same MessageId within the specified window. Setting the window to 60 seconds ensures that duplicate orders submitted within that timeframe are discarded, preventing duplicates from entering the queue.

Answer

Configure Auto-Forwarding to a dead-letter queue with a 60-second TTL.

Answer

Set the LockDuration property to 60 seconds.

Answer

Enable partitioning and set the partition key to the client IP address.

Question 2

You are designing a high-scale event ingestion pipeline using Azure Event Hubs in a secure enterprise environment. Public internet access must be disabled entirely. Producers and consumers reside in a peered Virtual Network (VNet). How should you configure network connectivity to the Event Hubs namespace?

Accepted Answer

Configure Private Endpoints for the Event Hubs namespace and disable public network access.. Azure Private Endpoints create a private IP address for the Event Hubs namespace inside your VNet via Azure Private Link, and disabling public network access ensures all traffic flows over the Microsoft backbone rather than the internet. This is the canonical pattern for fully private, enterprise-grade Event Hubs connectivity from peered VNets.

Answer

Enable Service Bus Relay hybrid connections across the VNet gateway.

Answer

Deploy an Azure Bastion host in the subnet connected to the Event Hubs SAS key manager.

Answer

Configure IP firewall rules to allow the default gateway IP of the VNet.

Question 3

Your application uses Azure Event Grid to deliver events to an Azure Function webhook. Due to a downstream database outage, the Azure Function returns HTTP 500 errors. How does Event Grid handle event delivery when the endpoint fails?

Accepted Answer

Event Grid retries delivery using an exponential backoff retry policy for up to 24 hours.. Azure Event Grid guarantees at-least-once delivery by retrying failed event deliveries using an exponential backoff policy. When a webhook returns HTTP 500, Event Grid treats it as a retryable failure and continues retrying for up to 24 hours, after which the event is either dropped or sent to a dead-letter destination if configured. This built-in retry mechanism ensures transient downstream failures do not immediately lose events.

Answer

Event Grid stops the event subscription until manually restarted by an administrator.

Answer

Event Grid immediately discards the event upon receiving the first HTTP 500 error.

Answer

Event Grid automatically migrates the event to an Azure Service Bus queue.

Question 4

You are building an AI financial transactions ledger using Azure Service Bus. Each transaction must be processed strictly in order per account ID, and if a transaction fails, subsequent transactions for that specific account must wait until the issue is resolved. Which feature should you use?

Accepted Answer

Service Bus Sessions (SessionId set to the account ID). Service Bus Sessions provide FIFO ordering guarantees per SessionId, and setting SessionId to the account ID ensures all transactions for a given account are processed sequentially by a single receiver. Sessions also enable the receiver to lock the session, so if a transaction fails, subsequent messages in that session are not delivered until the lock is released or the message is completed/abandoned. This satisfies both the strict per-account ordering and the blocking-on-failure requirement.

Answer

Event Hubs partitions with round-robin load balancing

Answer

Azure Storage Queues with invisible timeout properties

Answer

Event Grid advanced filters keyed by account ID

Question 5

An application publishes custom events to an Azure Event Grid topic. You want to inspect the dead-lettered events that failed delivery after the maximum retry period. Where must you configure the dead-letter destination?

Accepted Answer

Azure Blob Storage container. Event Grid dead-lettering requires an Azure Blob Storage container as the destination, configured on the event subscription. When an event fails all delivery retries (default 30 attempts over 24 hours), it is written to that container as a blob so you can inspect and reprocess it. Blob Storage is the only supported dead-letter target for Event Grid.

Answer

Azure SQL Database table

Answer

Local App Service temporary file system

Answer

Azure Service Bus Dead-Letter Queue

Question 6

Your enterprise application uses Azure Service Bus Topics. A specific downstream billing system needs to receive only messages where the 'Region' property in the message application properties equals 'NorthAmerica'. What should you create on the Service Bus subscription?

Accepted Answer

A SQL Filter or Correlation Filter on the subscription. Azure Service Bus subscriptions support SQL Filters and Correlation Filters that evaluate message application properties (e.g., Region = 'NorthAmerica') and route only matching messages to the subscription. A Correlation Filter is especially efficient for equality checks on properties like Region, while SQL Filters allow more complex expressions. This is the native filtering mechanism for Service Bus Topics.

Answer

An Event Grid Advanced Filter on the namespace topic

Answer

A Storage Queue access policy

Answer

An Event Hubs Partition Key routing rule

Question 7

You are configuring Azure Event Grid to send events to an Azure Logic App. Which built-in trigger should you use in your Logic App workflow to receive these events seamlessly?

Accepted Answer

When a resource event occurs (Azure Event Grid trigger). The 'When a resource event occurs' trigger is the native Azure Event Grid trigger in Logic Apps, designed specifically to subscribe to Event Grid topics and system topics. It handles the Event Grid subscription handshake, event schema validation, and delivery automatically, so events published to Event Grid flow directly into the workflow without custom parsing. This is the seamless, first-party integration path for Event Grid-to-Logic App event delivery.

Answer

When messages arrive in a Service Bus queue

Answer

When a blob is added or modified (V2)

Answer

When an HTTP request is received

Question 8

Your application publishes messages to an Azure Service Bus queue. The messages contain sensitive personal data. Enterprise compliance mandates that message payloads are encrypted end-to-end at the application layer before being sent to Service Bus. How should you implement this?

Accepted Answer

Encrypt the message payload in your application code using a key from Azure Key Vault before sending, and decrypt upon receipt.. End-to-end application-layer encryption means the payload must be encrypted before it leaves the producer and decrypted only by the consumer, so the broker never sees plaintext. Using a key from Azure Key Vault to encrypt in code and decrypt on receipt satisfies this because Service Bus only transports ciphertext, and key custody stays in Key Vault.

Answer

Configure Event Grid advanced filters to redact sensitive keys.

Answer

Enable Service Bus Premium Geo-Disaster Recovery with encryption enabled.

Answer

Use Shared Access Signature tokens with 5-minute expirations.

Question 9

You are designing an IoT data ingestion architecture using Azure Event Hubs. Devices occasionally send malformed JSON payloads that cause stream processing jobs to crash. You need to route these invalid messages to a separate error container without stopping the main ingestion stream. What should you implement?

Accepted Answer

Use Azure Stream Analytics with an error output data stream configured for malformed events.. Azure Stream Analytics supports an error output data stream that captures malformed or deserialization-failed events, allowing the main query to continue processing valid events while routing bad records to a separate sink (e.g., Blob Storage container). This is the documented pattern for handling malformed JSON without stopping the stream. Configuring the error output to point at an 'error' container satisfies the requirement.

Answer

Enable Event Hubs Capture with the JSON validation flag set to strict.

Answer

Set up an Event Grid system topic filter for 'MalformedEvent'.

Answer

Configure the Service Bus dead-letter queue on the Event Hub producer client.

Question 10

Your organization uses Azure Event Grid namespaces for MQTT client messaging in an industrial IoT scenario. Which authentication method should you configure for IoT devices connecting directly to the Event Grid namespace MQTT broker?

Accepted Answer

X.509 client certificates. Azure Event Grid namespaces support MQTT v3.1.1 and v5.0, and for direct device connections the recommended and supported authentication method is X.509 client certificates. Devices present a client certificate during the TLS handshake, and Event Grid validates it against a trusted CA or thumbprint. This is the standard for IoT device authentication in Event Grid MQTT broker.

Answer

SQL Database connection strings

Answer

Anonymous access with IP restriction headers

Answer

OAuth 2.0 client credentials grant via Service Bus endpoints

Question 11

You are managing an Azure Service Bus Standard namespace. Your development team requests the ability to use Topics and Subscriptions. What action must you take to support this requirement?

Accepted Answer

Ensure the Service Bus namespace is at the Standard or Premium tier.. Azure Service Bus Topics and Subscriptions are only available in the Standard and Premium tiers. The Basic tier does not support topics; it only supports queues. Therefore, to use Topics and Subscriptions, the namespace must be at the Standard or Premium tier.

Answer

Enable AMQP 1.0 multiplexing on the Basic tier namespace.

Answer

Create an Event Hubs capture rule to simulate topic subscriptions.

Answer

Upgrade the namespace to Azure Event Grid Premium.

Question 12

Your application emits custom events to an Azure Event Grid topic. You want to test your webhook endpoint locally during development without deploying your code to Azure. Which tool should you use to receive events directly from Event Grid?

Accepted Answer

Deploy the Event Grid Viewer sample web app to an accessible public URL or use ngrok to tunnel your local port.. Event Grid delivers events via HTTP POST to a webhook endpoint, so the endpoint must be reachable from the public internet. During local development, you either deploy the Event Grid Viewer sample to a publicly accessible URL or use ngrok to create a public tunnel that forwards to your localhost port. This lets Event Grid push events directly to your local debugging session without deploying your application to Azure.

Answer

Use Azure Bastion to connect your localhost to the Event Grid topic.

Answer

Configure a local SQL Server Express trigger.

Answer

Attach an Azure Service Bus queue directly as a local debugging breakpoint.

Question 13

You are optimizing an Azure Event Hubs stream processing application in Python. Messages are being processed too slowly, and you notice high CPU utilization on the consumer instance due to synchronous network I/O. Which programming model should you adopt to maximize ingestion throughput?

Accepted Answer

Use the asynchronous Event Hub client library (`azure-eventhub.aio`) with `asyncio` for non-blocking I/O operations.. The azure-eventhub.aio library exposes an async client built on asyncio, allowing the consumer to await network I/O (receiving events, checkpointing) without blocking the event loop. This eliminates the CPU waste caused by synchronous blocking calls and lets a single instance handle many concurrent partition receivers, maximizing throughput.

Answer

Increase the partition count of the Event Hub to 1,000 partitions.

Answer

Switch from Event Hubs to Azure Storage Queues for parallel processing.

Answer

Migrate all consumer code to use synchronous REST API polling over HTTPS GET requests.

Question 14

You are designing an enterprise messaging solution using Azure Service Bus. You need to ensure that messages published within a transaction (involving multiple messages sent to different queues) either all succeed or all fail together. What feature should you use?

Accepted Answer

Service Bus client transaction scope (TransactionScope in .NET). The correct feature is the Service Bus client transaction scope (TransactionScope in .NET). Azure Service Bus supports transactions that allow multiple messages sent to different queues or topics to be committed atomically. Using TransactionScope in .NET, developers can group send operations so that either all messages are committed or none are. This ensures consistency across multiple entities within a single transaction.

Answer

Storage Account atomic blob leases

Answer

Event Grid atomic batch publishing mode

Answer

Event Hubs transaction coordinator checkpointing

Question 15

Your organization requires that all data transmitted to an Azure Service Bus namespace is encrypted in transit using Transport Layer Security (TLS). What is the minimum required TLS version enforced by modern Azure Service Bus secure baselines?

Accepted Answer

TLS 1.2. Modern Azure Service Bus secure baselines require a minimum of TLS 1.2 for all data in transit. TLS 1.2 is the enforced floor because older protocols (SSL 3.0, TLS 1.0, TLS 1.1) have known cryptographic weaknesses and are deprecated across Azure services.

Answer

SSL 3.0

Answer

Plaintext HTTP with custom Base64 encoding

Answer

TLS 1.0