Free AI-200 Exam Braindumps
Developing AI Cloud Solutions on Azure Questions 56–60 (page: 13)

Updated On: 22-Aug-2026

An ACA app processes messages from an Azure Storage queue.
The app must scale automatically based on messages in a specific Azure Storage queue by using a Kubernetes Event-driven Autoscaler (KEDA) custom scale rule.
You need to configure the required scale rule values.
Which two values should you configure? Each correct answer presents part of the solution.
Note: Each correct selection is worth one point.

  1. Queue name
  2. Polling interval
  3. Trigger type
  4. Maximum replicas

Answer(s): A,C

Explanation:

[A] QeueName: The exact name of the specific Azure Storage queue your app is polling is required.
[C] Why Trigger Type is Required When configuring a custom scale rule in Azure Container Apps (ACA), the platform utilizes KEDA underneath. Because a custom rule can connect to many different event sources (such as Kafka, Redis, or Azure Storage), you must explicitly define the Trigger type (e.g., azure-queue) so KEDA knows which specific scaler to initiate.


Reference:

https://techcommunity.microsoft.com/blog/fasttrackforazureblog/container-apps-a-practical-scaling-with-azure-queue-scale-rule/3722075



You have an Event Grid subscription that triggers an Azure Function.
You need to prevent loss of events in case the endpoint returns an HTTP 400 response.
Which action should you perform?

  1. Implement optimistic batching.
  2. Implement asynchronous handshake validation.
  3. Configure a dead-letter destination.
  4. Configure a retry policy.

Answer(s): C

Explanation:

Configuring a dead-letter destination is exactly the right step to take.
By default, when an endpoint returns an HTTP 400 (Bad Request) or HTTP 413 (Payload Too Large) response, Azure Event Grid immediately stops delivery attempts and drops the message. It treats these specific errors as non-transient, client-side issues, meaning it skips its standard 24-hour retry policy.
Configuring a dead-letter destination ensures that these dropped events are safely preserved for future troubleshooting and reprocessing.


Reference:

https://turbo360.com/blog/azure-event-grid-dead-letter-monitoring



You are designing an Azure Function that will process orders from a new Azure Service Bus queue.
You need to prevent the system from processing messages more than once and preserve failed messages for investigation.
Which two actions should you implement? Each correct answer presents part of the solution.
Note: Each correct selection is worth one point.

  1. Include a dead-letter handling process.
  2. Process orders by using an HTTP trigger.
  3. Enable duplicate detection on the queue.
  4. Enable sessions on Service Bus.

Answer(s): A,C

Explanation:

To ensure reliable order processing with zero duplicates and safe error handling, you should implement an Azure Function with an Azure Service Bus Trigger utilizing duplicate detection, PeekLock settlement, and custom dead-letter routing.
References: https://azureintegrations.com/2020/03/01/azure-servce-bus-best-practises/


Reference:

References: https://azureintegrations.com/2020/03/01/azure-servce-bus-best-practises/



You are designing an Azure Function app that exposes a public API.
The solution must:
-Validate incoming request data and return results immediately to the caller.
-Support Microsoft Entra ID authentication.
-Guarantee idempotent processing when the same request is retried.
-Scale automatically under variable load.
-Avoid duplicate processing.
You need to implement a trigger.
Which trigger should you implement?

  1. Service Bus topic
  2. HTTP
  3. Azure Event Grid
  4. Azure Queue storage

Answer(s): B

Explanation:

An HTTP Trigger combined with Azure Durable Functions (Asynchronous Http Start pattern) and a backing database is the most appropriate architecture to fulfill all your requirements.
Immediate validation: HTTP triggers allow synchronous request-response communication, enabling you to validate payload data and return a 200 OK or 400 Bad Request to the caller instantly.
Entra ID authentication: Azure Functions native App Service Authentication (Easy Auth) integrates directly with HTTP endpoints to enforce Microsoft Entra ID token validation before your code even runs.
Automatic scaling: HTTP-triggered functions scale dynamically out-of-the-box using the Azure Functions Consumption or Premium hosting plans based on incoming web traffic.


Reference:

https://github.com/microsoft/woodgrove-auth-api/blob/main/README.md



A large retail company operates online and physical stores. The company tracks inventory levels in real time to manage stock efficiently across all locations. You develop an Azure Event Grid solution to handle events generated by the inventory management system deployed to Azure.
You need to implement a subscription filter that dynamically adjusts to seasonal changes in product demand.
Which event filter should you use?

  1. An advanced filter using a Boolean condition that evaluates multiple data fields, including a season field within the event data
  2. A prefix filter on the event type field that matches the current season's name
  3. A subscription filter that uses a label filter to include events tagged with seasonal promotional codes
  4. A static subject filter that targets events with a subject ending in "/seasonal/inventory"

Answer(s): A

Explanation:

To handle dynamic, seasonal changes in product demand within Azure Event Grid, you should use Advanced Filters with a string or numeric comparison that evaluates event data attributes, typically paired with an automated external process (like an Azure Function or Logic App) to dynamically update the subscription filter rules via the Event Grid management API as seasons change


Reference:

https://techcommunity.microsoft.com/blog/analyticsonazure/a-technical-implementation-guide-for-multi-store-retail-environments/4488418



Viewing page 13 of 27
Viewing questions 61 - 65 out of 174 questions


Post your Comments and Discuss Microsoft AI-200 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!