AZ-204 Technology & Digital Applications 5 — Questions and Answers
Question 1: You need to deploy an Azure Function that processes IoT telemetry from millions of devices with minimal latency. Which trigger and hosting plan combination is most appropriate?
- HTTP trigger on Consumption plan
- Event Hubs trigger on Premium plan (Correct answer)
- Service Bus trigger on Consumption plan
- Timer trigger on Dedicated (App Service) plan
Correct answer: Event Hubs trigger on Premium plan
Event Hubs trigger is optimized for high-throughput streaming data, and the Premium plan provides pre-warmed instances and VNet integration required for low-latency, high-scale IoT scenarios.
Question 2: An application stores user-uploaded files in Azure Blob Storage. You need to allow users to download their files directly from Blob Storage without exposing the storage account key. What should you use?
- Set the container access level to 'Blob (anonymous read)'
- Generate a Shared Access Signature (SAS) token with read permission scoped to the user's blob (Correct answer)
- Use Azure CDN to proxy requests and hide the storage account
- Enable Azure AD authentication and issue access tokens to users
Correct answer: Generate a Shared Access Signature (SAS) token with read permission scoped to the user's blob
A user-delegation or service SAS token grants time-limited, permission-scoped access to a specific blob without exposing the storage account key.
Question 3: You are implementing a Saga pattern using Azure Durable Functions to coordinate a multi-step order fulfillment workflow with compensating transactions. Which Durable Functions pattern should you use?
- Fan-out/fan-in
- Function chaining (Correct answer)
- Eternal orchestration
- Human interaction / external events
Correct answer: Function chaining
Function chaining in Durable Functions sequentially calls activity functions in order, making it straightforward to implement Saga steps and call compensating activities if any step fails.
Question 4: A .NET application deployed to Azure App Service needs to write logs that can be queried in Log Analytics. Which approach integrates natively with Azure Monitor?
- Write logs to Console.WriteLine and enable App Service Logs streaming
- Use Application Insights SDK with ILogger integration to send structured telemetry (Correct answer)
- Write logs to a local file and use Azure Blob Storage log archiving
- Use Log4Net to write to a custom Azure Table Storage sink
Correct answer: Use Application Insights SDK with ILogger integration to send structured telemetry
The Application Insights SDK integrates with .NET's ILogger to capture structured logs and send them to Application Insights, which stores data in a Log Analytics workspace queryable via KQL.
Question 5: Your Cosmos DB application experiences 429 (Too Many Requests) errors during peak traffic. You have provisioned 1000 RU/s. What is the recommended first step to address this?
- Switch from provisioned throughput to serverless capacity mode
- Enable autoscale and set the maximum RU/s to 10,000
- Implement retry with exponential backoff in the client and review partition key design for hot partitions (Correct answer)
- Switch from the Core (SQL) API to the MongoDB API for better throughput
Correct answer: Implement retry with exponential backoff in the client and review partition key design for hot partitions
Retries with exponential backoff handle transient 429s, while reviewing partition key design eliminates hot partitions that cause 429s even when total RUs are sufficient.
Question 6: You need to expose a legacy SOAP backend service as a modern REST API using Azure API Management. Which APIM feature enables this?
- Create an HTTP passthrough API and manually convert XML in a Logic App
- Import the WSDL into APIM to create a SOAP API, then use the soap-to-rest policy to expose REST operations (Correct answer)
- Use Azure Functions to wrap the SOAP calls and expose HTTP endpoints
- Enable the APIM Developer Portal to auto-generate a REST facade
Correct answer: Import the WSDL into APIM to create a SOAP API, then use the soap-to-rest policy to expose REST operations
APIM supports importing WSDL definitions and the soap-to-rest transformation policy to expose SOAP operations as RESTful endpoints without modifying the backend.
Question 7: You need to implement content-based routing in an Azure Service Bus topic so that 'priority' orders go to a 'PrioritySubscription' and all others go to a 'StandardSubscription'. How do you configure this?
- Set the topic's PartitioningEnabled property to route by message content
- Define correlation filters on each subscription that match the message's custom 'Priority' property (Correct answer)
- Use a Service Bus namespace routing rule to split messages at the namespace level
- Configure Azure Event Grid to route messages between the two subscriptions
Correct answer: Define correlation filters on each subscription that match the message's custom 'Priority' property
Service Bus subscription filters, including correlation filters on user-defined message properties, route messages to the appropriate subscription based on content without consuming them from others.
You need to deploy an Azure Function that processes IoT telemetry from millions of devices with minimal latency.
Which trigger and hosting plan combination is most appropriate?