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

Question 1

You are troubleshooting a connection issue where an on-premises worker application cannot connect to an Azure Event Hubs namespace over AMQP port 5671 due to strict corporate firewall rules. Only port 443 outbound traffic is allowed. How can you configure the client connection to bypass this restriction?

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

Accepted Answer

Configure the Event Hub client connection to use AMQP over WebSockets (port 443).. Azure Event Hubs supports AMQP over WebSockets, which tunnels AMQP traffic over port 443 (HTTPS). By configuring the Event Hubs client to use WebSockets (e.g., setting the transport type to AmqpWebSockets), the connection uses port 443, which is allowed by the corporate firewall. This is the standard workaround for restrictive firewall environments.

Answer

Deploy an Azure VPN Gateway on the local workstation.

Answer

Switch the connection string to use an Event Grid webhook protocol.

Answer

Open an Azure Support ticket to whitelist port 5671 on the Azure backbone router.

Question 2

Your application publishes events to an Azure Event Grid custom topic. You need to inspect the operational health and delivery success metrics of your event subscriptions. Where should you view these metrics natively in the Azure Portal?

Accepted Answer

The Metrics blade of the Event Grid Topic or Domain in the Azure Portal. Azure Event Grid exposes native platform metrics on the Event Grid Topic or Domain resource itself, including publish/delivery success, matched/attempted/dropped events, and delivery latency. These are surfaced under the Metrics blade of the topic or domain in the Azure Portal, where you can chart and alert on them. This is the built-in operational health view for event subscriptions without needing external tooling.

Answer

The Azure Storage Account Access Logs

Answer

The Service Bus Explorer tool

Answer

The App Service Kudu diagnostic console

Question 3

You are designing an enterprise-grade event-driven system where producers send financial transactions to Azure Event Hubs. You must guarantee that every single message is accounted for and that no data is lost even if an entire availability zone suffers a catastrophic failure. Which deployment configuration should you select for your Event Hubs namespace?

Accepted Answer

Deploy an Event Hubs namespace in a region supporting Availability Zones with zone redundancy enabled (Premium or Dedicated tier).. Zone-redundant Event Hubs, available in Premium and Dedicated tiers, replicates data across three availability zones within a region. This ensures that if an entire availability zone fails, the namespace remains available and no committed messages are lost, satisfying the requirement for catastrophic AZ failure resilience.

Answer

Configure Event Grid system topics with auto-delete set to false.

Answer

Deploy a Basic tier Event Hubs namespace with 30 consumer groups.

Answer

Use Azure Storage Queues configured with RA-GRS replication.

Question 4

You are designing an event-driven AI document processing pipeline. Incoming PDF documents are uploaded to Azure Blob Storage, triggering an Event Grid event. The event triggers an Azure Function that downloads the PDF, processes it with Azure AI Document Intelligence, and saves results to Azure Cosmos DB. Under high load, duplicate events are occasionally received by the function, causing duplicate Cosmos DB records. How should you design the Azure Function to handle idempotency?

Accepted Answer

Implement idempotency in the Azure Function by checking if the document record already exists in Cosmos DB or using an upsert operation with a deterministic ID.. Idempotency in an at-least-once event pipeline is achieved by making the consumer's write operation idempotent — either by checking for an existing record before insert or by using an upsert with a deterministic ID derived from the event. This ensures duplicate Event Grid deliveries produce the same final state in Cosmos DB without creating duplicate records.

Answer

Set the Event Grid retry count to zero.

Answer

Deploy an Azure Service Bus queue in front of Blob Storage to serialize all requests into a single partition.

Answer

Configure Event Grid delivery mode to 'Exactly-Once' in the subscription settings.

Question 5

Your organization uses Azure Event Hubs to ingest telemetry from smart meters. You want to grant an external analytics vendor read-only access to the Event Hub data without sharing your master connection string or account keys. What should you create?

Accepted Answer

A SAS authorization rule with 'Listen' permissions only, or assign the Azure Event Hubs Data Receiver RBAC role.. To grant read-only access to Event Hubs without sharing master keys, you can create a SAS authorization rule with only 'Listen' permissions or assign the Azure Event Hubs Data Receiver RBAC role to the vendor's identity. Both methods follow the principle of least privilege and allow the vendor to receive events without management or send rights.

Answer

An Event Grid subscription key with administrator rights.

Answer

A SAS rule with 'Manage' permissions.

Answer

A Storage Account connection string with Contributor access.

Question 6

You are designing an enterprise event-driven architecture where microservices across different Azure subscriptions need to subscribe to domain events published by a central Order Service. Which Azure Event Grid architecture should you implement?

Accepted Answer

Deploy an Azure Event Grid Event Domain and create event subscriptions under the domain for each consuming team.. Azure Event Grid Event Domains are purpose-built for multi-tenant, multi-subscription event distribution scenarios. An Event Domain acts as a namespace that can host thousands of topics, allowing each consuming team or subscription to create its own event subscriptions under the domain without the publisher needing to manage individual topics per consumer. This decouples the central Order Service from consumer onboarding and scales cleanly across subscriptions.

Answer

Deploy an Azure Service Bus relay across all subscriptions.

Answer

Create individual Event Hubs namespaces in every consumer subscription and peer them via ExpressRoute.

Answer

Use Azure Storage Queues shared via SAS URLs across subscriptions.

Question 7

Your team is developing an Azure Function that acts as an Event Grid webhook subscriber. You want to test the function locally using the Azure Functions Core Tools CLI. Which command starts the local runtime and enables local event ingestion?

Accepted Answer

func start. The Azure Functions Core Tools command `func start` launches the local Functions host, which exposes the HTTP trigger endpoint (typically http://localhost:7071/api/<function>) that Event Grid can target as a webhook subscriber. It also loads local.settings.json so you can point at a real Event Grid subscription for end-to-end local testing. This is the standard way to run and debug a function locally before deploying.

Answer

dotnet watch run-eventgrid

Answer

az eventgrid topic local-debug

Answer

az functionapp deployment source config

Question 8

You are designing an AI streaming pipeline using Azure Event Hubs with Apache Kafka enabled. Existing Java producers using the Kafka producer API need to authenticate against Event Hubs securely using Microsoft Entra ID (OAuth 2.0). How should you configure the Kafka producer client properties?

Accepted Answer

Configure security.protocol=SASL_SSL, sasl.mechanism=OAUTHBEARER, and implement an OAuthBearerTokenCallbackHandler for Microsoft Entra ID token acquisition.. The correct configuration is to set security.protocol=SASL_SSL, sasl.mechanism=OAUTHBEARER, and implement an OAuthBearerTokenCallbackHandler for Microsoft Entra ID token acquisition. Azure Event Hubs with Kafka enabled supports OAuth 2.0 authentication via SASL/SSL. The Kafka producer must be configured to use SASL_SSL and the OAUTHBEARER mechanism, and the callback handler must obtain a token from Microsoft Entra ID (formerly Azure AD) and present it to Event Hubs.

Answer

Use plain text authentication with the Event Hub root SAS key as the username and password.

Answer

Deploy an Event Grid webhook proxy between the Kafka producer and Event Hubs.

Answer

Set the bootstrap.servers property to the Service Bus AMQP connection string.

Question 9

Your organization uses Azure Event Grid to route IoT device lifecycle events. You want to ensure that events published to your custom topic are encrypted at rest using Microsoft-managed keys by default. Which action is required to enable this?

Accepted Answer

No action is required; encryption at rest using Microsoft-managed keys is enabled by default.. Azure Event Grid automatically encrypts all events and data at rest using Microsoft-managed keys (MMK) with no configuration required. This encryption applies to custom topics, system topics, and domains by default, ensuring data is protected without any user action. Therefore, the correct answer is that no action is needed to enable encryption at rest with Microsoft-managed keys.

Answer

You must enable Event Hubs Capture on the topic.

Answer

You must configure a Storage Account dead-letter container.

Answer

You must link an Azure Key Vault instance during topic creation.

Question 10

Your application uses Azure Service Bus Queues. A spike in traffic causes multiple worker instances to contend for messages. You want to ensure that when a worker locks a message, no other worker can process it, and the lock is automatically renewed in the background if processing takes longer than expected. Which client library feature should you use?

Accepted Answer

Enable Auto-Lock Renewal on the message processor client.. Auto-Lock Renewal is a feature of the Service Bus message processor client (e.g., ServiceBusProcessor in .NET, ServiceBusProcessorClient in Java) that automatically extends the message lock in the background while the handler is still processing. This prevents lock expiration and message redelivery to other workers during long-running processing.

Answer

Increase the LockDuration property on the queue to 2 hours permanently.

Answer

Use Event Grid advanced filters to throttle incoming messages.

Answer

Switch the queue to ReceiveAndDelete mode.

Question 11

Your application sends messages to an Azure Service Bus queue. A downstream worker needs to postpone processing of a specific message until a later time without losing its place in the queue or dead-lettering it. What method should the worker invoke?

Accepted Answer

DeferMessageAsync(). DeferMessageAsync() postpones processing of a message by setting it aside while preserving its sequence number, allowing the worker to retrieve it later by sequence number without losing its place or dead-lettering it. This is the correct method for temporarily postponing a specific message in Azure Service Bus.

Answer

CompleteMessageAsync()

Answer

AbandonMessageAsync()

Answer

DeadLetterMessageAsync()

Question 12

You are designing a disaster recovery strategy for an Azure Event Hubs namespace. You configure Geo-Disaster Recovery pairing between a primary region (East US) and a secondary region (West US). During a disaster drill, you trigger a failover. What happens to the DNS alias pointing to the Event Hubs namespace?

Accepted Answer

The alias is automatically updated to point to the secondary namespace, enabling client reconnection without changing connection strings.. Geo-Disaster Recovery in Azure Event Hubs uses a DNS alias (namespace hostname) that abstracts the primary and secondary namespaces. When you trigger a failover, the alias's DNS CNAME record is automatically repointed to the secondary namespace, so clients using the alias connection string reconnect without any configuration change. This is the core value of the alias-based failover model.

Answer

The primary namespace automatically becomes the replica of the secondary namespace without breaking the pair.

Answer

The alias enters a Read-Only state for 24 hours while DNS propagation finishes globally.

Answer

The alias is permanently deleted and clients must be hardcoded with the secondary namespace connection string.

Question 13

Your application publishes events to an Azure Event Grid custom topic. You need to restrict publishing access so that only clients with a specific User-Assigned Managed Identity can send events. How should you secure the topic?

Accepted Answer

Assign the 'Event Grid Data Sender' role to the Managed Identity on the Event Grid topic resource scope.. Azure Event Grid integrates with Azure RBAC, and the built-in role 'Event Grid Data Sender' grants permission to publish events to a topic or namespace. Assigning this role to the user-assigned managed identity at the Event Grid topic resource scope allows only that identity to publish, satisfying the least-privilege requirement. This is the standard Entra ID-based authorization model for Event Grid publishing.

Answer

Embed the primary SAS access key into the client's application environment variables.

Answer

Enable AMQP 1.0 token authentication on the event subscription.

Answer

Configure an Azure Storage firewall rule on the topic endpoint.

Question 14

Your organization uses Azure Service Bus Topics. You need to ensure that messages published to a topic are delivered to subscriptions in a specific priority order (e.g., high priority messages processed before normal priority). What is the recommended Service Bus design pattern to achieve this?

Accepted Answer

Create separate queues or subscriptions for high-priority and normal-priority messages, and have workers poll the high-priority entity first.. Service Bus does not natively support message priority ordering, so the recommended pattern is to create separate queues or subscriptions for each priority level and have consumers drain the high-priority entity first. This gives deterministic priority handling because the broker processes each entity independently and the consumer controls polling order. It is the standard workaround for the absence of a built-in priority property.

Answer

Set the Priority property on the Service Bus message header to 99.

Answer

Configure Event Hubs partition key hashing to group priority messages.

Answer

Enable Event Grid priority filters on the topic.

Question 15

You are designing an AI streaming pipeline using Azure Event Hubs. You need to inspect diagnostic logs and operational metrics to track incoming request rates, server errors, and throttling events across the namespace. Where should you configure this telemetry collection in the Azure Portal?

Accepted Answer

Diagnostic Settings on the Event Hubs namespace pointing to a Log Analytics workspace.. Diagnostic Settings on the Event Hubs namespace is the correct place to route platform logs (including operational/diagnostic logs) and metrics to destinations like Log Analytics, Storage, or Event Hubs. This is where you enable collection of request rates, server errors, and throttling events for the namespace. It is the standard Azure Monitor integration point for resource-level telemetry.

Answer

Event Hubs Capture export storage container settings.

Answer

Azure Bastion diagnostic configuration.

Answer

Auto-Inflate throughput unit configuration blade.