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

Question 1

Your application publishes custom events to an Azure Event Grid topic. You want to ensure that event publishers transmit data over secure HTTPS endpoints only. How should you enforce this?

Accepted Answer

Event Grid enforces HTTPS by default for all custom topic publishing endpoints.. Azure Event Grid custom topics expose a publishing endpoint that only accepts HTTPS (TLS 1.2+) requests — there is no HTTP listener. Publishers must POST events to the topic's HTTPS URL using the `aeg-sas-key` header or Microsoft Entra ID token. Because HTTPS is the only supported transport, no additional configuration (certificates, firewalls, or gateways) is required to enforce it.

Answer

You must install a self-signed SSL certificate on the publisher client machine.

Answer

Configure an Azure Firewall rule allowing port 80 outbound.

Answer

You must configure an Azure Application Gateway in front of the Event Grid topic.

Question 2

You are managing an Azure Service Bus Premium namespace. Your application requires strict transactional messaging where a worker receives a message from Queue A, processes it, and sends a resulting message to Queue B. If any step fails, both actions must be rolled back. How should you implement this?

Accepted Answer

Wrap the receive and send operations inside a .NET TransactionScope block.. In Azure Service Bus, transactional messaging across multiple entities (like receiving from one queue and sending to another) can be achieved using the .NET TransactionScope class. This ensures that both operations are committed or rolled back together.

Answer

Set the message session ID to the same value on both queues.

Answer

Enable Event Grid automatic forwarding between queues.

Answer

Use Event Hubs checkpoints for transactional rollback.

Question 3

You are designing an enterprise AI event-driven pipeline. Events from multiple SaaS applications are published to an Azure Event Grid domain. You need to ensure that a rogue tenant cannot exhaust the delivery throughput of other tenants. Which feature should you leverage?

Accepted Answer

Deploy separate Event Grid topics or distinct Event Domains per tenant with dedicated custom access keys or managed identities.. Deploying separate Event Grid topics or distinct Event Domains per tenant with dedicated access keys or managed identities isolates each tenant's publishing and delivery throughput, preventing a rogue tenant from exhausting shared resources. Event Grid domains allow multi-tenant publishing with per-tenant topics, but true throughput isolation requires separate domains or topics with separate authentication and quotas. This design ensures noisy-neighbor effects are contained.

Answer

Set the maximum delivery retry count to zero for all tenants.

Answer

Enable Azure DDoS Protection Standard on the storage account dead-letter container.

Answer

Configure Service Bus partitioned queues in front of the Event Grid domain.

Question 4

Your application publishes events to an Azure Event Grid system topic. You want to filter events so that your webhook subscriber receives only events where the 'eventType' is 'Microsoft.Storage.BlobCreated'. Where should you configure this filter?

Accepted Answer

In the Event Grid subscription filter configuration blade under 'Included Event Types'.. Event filtering for Azure Event Grid is configured on the Event Grid subscription itself, not in the subscriber or the event source. The 'Included Event Types' setting in the Event Grid subscription filter configuration blade lets you specify which event types (such as 'Microsoft.Storage.BlobCreated') are delivered to the subscriber endpoint. This filter is evaluated by Event Grid before the event is pushed to the webhook, so only matching events reach the subscriber.

Answer

Within the Azure Function host.json configuration file.

Answer

In the Service Bus Topic subscription SQL filter.

Answer

Inside the Azure Storage account connection string settings.

Question 5

You are designing an AI streaming architecture using Azure Event Hubs in a Dedicated cluster. You need to monitor capacity utilization to ensure the cluster does not exceed its allocated Processing Units (PUs). Which metric should you track in Azure Monitor?

Accepted Answer

Dedicated Cluster Memory and CPU Usage / Processing Units (PUs) Utilization metrics.. In an Azure Event Hubs Dedicated cluster, capacity is measured and billed in Processing Units (PUs), and the cluster exposes specific Azure Monitor metrics for CPU, memory, and PU utilization. Tracking 'Processing Units (PUs) Utilization' (alongside CPU and Memory usage) is the direct way to see whether the cluster is approaching its allocated PU ceiling. These metrics are emitted per cluster under the Microsoft.EventHub/clusters namespace, so they are the authoritative signal for capacity planning.

Answer

Service Bus Active Message Count.

Answer

Event Grid Delivery Success Rate percentage.

Answer

Storage Account Blob Capacity utilization.

Question 6

You are designing an asynchronous AI transaction pipeline using Azure Service Bus. You need to implement the Competing Consumers pattern where multiple worker instances process messages from a single queue without duplicating work. How does Azure Service Bus natively support this pattern?

Accepted Answer

Service Bus automatically locks and distributes messages across competing workers using PeekLock mode.. Azure Service Bus natively implements the Competing Consumers pattern through PeekLock receive mode: each worker receives a message, obtains an exclusive lock token, and other workers cannot see that message until the lock expires or is released. This broker-side locking distributes messages across competing workers without duplicate processing, as long as handlers settle messages within the lock duration.

Answer

Configure Event Hubs consumer groups with exclusive read locks.

Answer

You must write custom distributed locking logic using Azure Blob Leases in front of the queue.

Answer

You must deploy an Event Grid topic with a round-robin webhook load balancer.

Question 7

You are configuring network security for an enterprise Azure Service Bus Premium namespace. Which THREE networking features can you configure to secure the namespace? (Choose three)

Accepted Answer

Private endpoints using Azure Private Link. Option A (Private endpoints using Azure Private Link) is correct because Service Bus Premium supports Private Link, which assigns a private IP from your VNet to the namespace and removes exposure to the public internet, allowing secure access over the Microsoft backbone network. Option C (IP firewall rules) is correct because Service Bus Premium lets you restrict access to specific public IP addresses or CIDR ranges via the namespace's networking firewall, blocking all other public traffic by default. Option D (Virtual Network (VNet) service endpoints) is correct because Service Bus Premium supports VNet service endpoints, which extend your VNet identity to the service over the Azure backbone and let you restrict access to specific subnets. Option B is incorrect because Event Grid MQTT broker certificate authentication applies to Event Grid's MQTT support, not to Azure Service Bus. Option E is incorrect because Blob storage container access policies are a storage feature unrelated to securing a Service Bus namespace.

Answer

Event Grid MQTT broker certificate authentication

Answer

Blob storage container access policies

Question 8

You are architecting an event-driven AI ingestion pipeline using Azure Event Hubs. Which TWO features or capabilities are native to Azure Event Hubs? (Choose two)

Accepted Answer

Apache Kafka protocol endpoint compatibility. Option B is correct because Azure Event Hubs natively exposes a Kafka-compatible endpoint (port 9093, SASL/PLAIN or SASL/OAUTHBEARER), letting existing Apache Kafka producers and consumers connect without code changes. Option C is correct because Event Hubs Capture is a built-in feature that automatically archives streaming data to Azure Blob Storage or Azure Data Lake Storage in Avro format based on a time or size window, with no custom consumer required. Option A is not native: dead-lettering after a max delivery count is a Service Bus queue/subscription behavior, not an Event Hubs feature (Event Hubs uses consumer offsets and checkpointing). Option D is not native: webhook subscription validation handshakes belong to Event Grid event subscriptions, not Event Hubs. Option E is not native: AMQP 1.0 sessions with FIFO per session ID are a Service Bus messaging capability; Event Hubs provides partition-based ordering, not AMQP session management.

Answer

Automatic dead-letter queue routing after max delivery count

Answer

Webhook event schema subscription validation handshakes

Answer

AMQP 1.0 message session management for FIFO per session ID

Question 9

Your enterprise application uses Azure Event Grid. Which TWO event schemas are natively supported when publishing events to an Event Grid custom topic? (Choose two)

Accepted Answer

CloudEvents 1.0 schema. Azure Event Grid custom topics natively support two event schemas for publishing: the CloudEvents 1.0 schema (option D) and the proprietary Azure Event Grid schema (option E). CloudEvents 1.0 is the CNCF-standardized, interoperable envelope format that Event Grid accepts directly, while the Azure Event Grid schema is the service's original native format with fields like 'eventType', 'subject', 'data', and 'dataVersion'. Both are selectable via the topic's input schema setting and are the only two schemas Event Grid accepts for custom topic publishing. Options A, B, and C are incorrect: Apache Kafka record batch binary, AMQP 1.0 binary stream envelopes, and SOAP 1.2 XML are not supported input schemas for Event Grid custom topics, even though Event Grid can deliver to Kafka or use AMQP internally for its own transport.

Answer

Apache Kafka record batch binary schema

Answer

AMQP 1.0 binary stream envelope

Answer

SOAP 1.2 XML messaging schema

Question 10

You are troubleshooting event delivery failures in Azure Event Grid. Which TWO mechanisms can help you analyze or recover undeliverable events? (Choose two)

Accepted Answer

Configuring a Dead-Letter destination pointing to an Azure Blob Storage container. Option A is correct because Azure Event Grid supports a dead-letter destination (typically an Azure Blob Storage container) where events that cannot be delivered after all retry attempts are stored, allowing you to inspect and later reprocess the undeliverable events. Option C is correct because enabling Azure Monitor diagnostic settings on the Event Grid topic or subscription lets you route delivery and publish metrics plus resource logs (e.g., DeliveryFailures, DroppedEvents) to Log Analytics, Storage, or Event Hubs, which is the standard way to analyze delivery failures. Option B is not applicable because Service Bus session locks are a Service Bus feature for ordered, session-aware message consumption, not an Event Grid delivery-recovery mechanism. Option D is wrong because 'az servicebus queue purge' deletes messages from a Service Bus queue and has nothing to do with Event Grid undeliverable events. Option E is wrong because Event Hubs Capture writes event data to storage in Avro format and does not replay webhook HTTP headers for Event Grid.

Answer

Enabling Service Bus message session locks on the event subscription

Answer

Running the az servicebus queue purge command

Answer

Using Event Hubs Capture to replay webhook HTTP headers

Question 11

You are designing a big data telemetry ingestion pipeline using Azure Event Hubs. Which THREE configuration options or properties must you consider when planning Event Hubs capacity and scaling? (Choose three)

Accepted Answer

Partition Count. Partition Count (A) is correct because partitions are the fundamental unit of scale and parallelism in Event Hubs; the number of partitions determines the maximum concurrent readers per consumer group and directly caps ingress/egress throughput, so it must be planned up front since it cannot be reduced after creation. Throughput Units (TUs) or Processing Units (PUs) (D) are correct because they define the provisioned capacity of the namespace (TUs for Standard/Dedicated, PUs for Premium), governing ingress (e.g., 1 MB/s per TU) and egress limits and enabling auto-inflate scaling. Message Retention Period (E) is correct because it determines how long events remain available in the partition stream (1–7 days Standard, up to 90 days Premium/Dedicated), which affects storage consumption, replay/recovery windows, and downstream checkpointing design. Service Bus Lock Duration (B) is incorrect because it is a Service Bus queue/subscription peek-lock setting, not an Event Hubs property. Event Grid Webhook Handshake Timeout (C) is incorrect because it belongs to Event Grid event subscription delivery validation, not Event Hubs capacity planning.

Answer

Service Bus Lock Duration

Answer

Event Grid Webhook Handshake Timeout

Question 12

You are designing an event-driven architecture that needs to integrate multiple Azure services. Which THREE statements accurately describe the ideal use cases for Azure Event Grid, Azure Service Bus, and Azure Event Hubs respectively? (Choose three)

Accepted Answer

Azure Event Hubs is designed for high-throughput big data streaming and telemetry ingestion pipelines.. Option A is correct because Azure Event Hubs is a big-data streaming platform built for ingesting millions of events per second from telemetry, logs, and IoT sources into pipelines like Azure Stream Analytics or Spark. Option C is correct because Azure Event Grid is a reactive, push-based pub/sub service that routes discrete event notifications from Azure resource events and custom topics to subscribers such as Functions, Logic Apps, and webhooks. Option E is correct because Azure Service Bus provides enterprise brokering with queues, topics/subscriptions, sessions, transactions, dead-lettering, and guaranteed FIFO ordering via sessions. Option B is wrong because Kafka-protocol streaming is a feature of Event Hubs (Kafka endpoint), not Event Grid. Option D is wrong because Service Bus is a brokered messaging service with at-least-once delivery and store-and-forward semantics, not a stateless sub-millisecond webhook notifier like Event Grid.

Answer

Azure Event Grid is designed for high-speed Kafka protocol big data telemetry streaming.

Answer

Azure Service Bus is optimized for stateless event notifications with sub-millisecond webhook delivery.

Question 13

Your enterprise system uses Azure Service Bus. Which TWO mechanisms can you implement to handle 'poison' or repeatedly failing messages? (Choose two)

Accepted Answer

Configuring Max Delivery Count and automatic dead-lettering. Option D is correct because Service Bus queues and subscriptions have a MaxDeliveryCount property (default 10); once a message's delivery count exceeds this value, the broker automatically moves it to the dead-letter queue ($DeadLetterQueue), which is the built-in mechanism for isolating poison messages. Option E is correct because the application can proactively dead-letter a message by calling DeadLetterMessageAsync() (or DeadLetterAsync() on the ServiceBusReceiver/MessageReceiver) when it detects a non-retryable or repeatedly failing message, giving explicit control over poison-message handling. Option A is incorrect because Auto-Inflate only scales messaging units/throughput capacity and has nothing to do with message failure handling. Option B is incorrect because Event Grid advanced filters apply to event subscriptions for Event Grid events, not to Service Bus queue message processing or dead-lettering. Option C is incorrect because setting a null Partition Key only affects session/partition routing behavior and does not address poison messages.

Answer

Configuring Auto-Inflate on the Service Bus namespace

Answer

Enabling Event Grid advanced filters on the queue

Answer

Setting the Partition Key to a null value

Question 14

You are configuring authentication and authorization across Azure messaging and eventing services. Which THREE statements regarding security features are correct? (Choose three)

Accepted Answer

Shared Access Signature (SAS) tokens can be generated with specific permissions and expiration times.. Option B is correct because SAS tokens for Service Bus, Event Hubs, and Storage are constructed with a signed resource URI, key name, expiry, and explicit permissions (for example Send, Listen, Manage), allowing least-privilege, time-bound access. Option C is correct because Service Bus and Event Hubs both expose data-plane RBAC roles such as Azure Service Bus Data Owner/Sender/Receiver and Event Hubs Data Owner/Sender/Receiver, letting Microsoft Entra ID identities authenticate without embedding SAS keys. Option D is correct because Event Grid webhook and Azure Function/Service Bus/Event Hubs subscription targets can use a system-assigned or user-assigned managed identity, with the target validating the Entra-issued token, avoiding secrets in the subscription. Option A is wrong because Event Grid custom topics authenticate publishers with SAS keys or Microsoft Entra ID, not SQL database credentials. Option E is wrong because Service Bus queues are accessed via SAS or Entra ID over AMQP; anonymous public access is not required and should not be enabled.

Answer

Event Grid custom topics require SQL database credentials for publisher authentication.

Answer

Azure Service Bus queues require public anonymous access to be enabled for client SDK connections.

Question 15

You are designing an event-driven AI application that requires routing custom events from an Azure resource to multiple downstream serverless webhooks. Which Azure messaging service should you use to publish and route these events reliably?

Accepted Answer

Azure Event Grid. Azure Event Grid is a fully managed event routing service designed for event-driven architectures. It natively supports custom events published to a topic, and can route them to multiple subscribers—including serverless webhooks—via event subscriptions. It provides reliable delivery with retries, dead-lettering, and filtering, making it the ideal choice for routing custom events to multiple downstream webhooks.

Answer

Azure Service Bus

Answer

Azure Event Hubs

Answer

Azure Storage Queues