The answer is Azure Logic Apps with a Container Instances connector because it provides the event-driven queue trigger and automatic scaling required for this batch processing scenario. When a message lands in Azure Queue Storage, the Logic Apps workflow fires immediately via the queue trigger, then uses the Container Instances connector to spin up a new container group per message, ensuring each 5-minute image job runs only on demand with no idle costs. On the AZ-204 exam, this tests your understanding of serverless orchestration patterns—specifically how Logic Apps bridges queue-based eventing with containerized compute. A common trap is choosing Azure Functions with a queue binding, but Functions lack native ACI orchestration and would require custom code to manage container lifecycle. Memory tip: think “Queue fires Logic, Logic fires Container” to remember the three-step chain—storage trigger, orchestration layer, compute execution.
AZ-204 Develop Azure compute solutions Practice Question
This AZ-204 practice question tests your understanding of develop azure compute solutions. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are designing a solution that uses Azure Container Instances (ACI) to run a batch job that processes images. The job is triggered by a message in Azure Queue Storage. Each image takes about 5 minutes to process. You need to ensure that the container runs only when there are messages in the queue and scales automatically. What should you use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Azure Logic Apps with a Container Instances connector.
Option A is correct because Azure Logic Apps provides a serverless workflow that can be triggered by a queue message (via the Azure Queue Storage connector) and then use the Container Instances connector to start a container group. This ensures the container runs only when messages are present and scales automatically by creating a new container instance per message, matching the requirement for event-driven, on-demand execution without idle costs.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Use Azure Logic Apps with a Container Instances connector.
Why this is correct
Logic Apps can trigger on queue messages and start ACI containers per message.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use Azure Functions with a custom container and queue trigger.
Why it's wrong here
Azure Functions supports custom containers, but scaling is per function, not per container instance.
✗
Use Azure Batch to process the images in a pool of VMs.
Why it's wrong here
Azure Batch is designed for larger-scale parallel workloads; ACI is simpler for this scenario.
✗
Deploy the image processing job as a pod in Azure Kubernetes Service.
Why it's wrong here
AKS adds complexity and cost; ACI is simpler for event-driven batch jobs.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume Azure Functions is the only serverless option for queue-triggered workloads, overlooking that Logic Apps can directly orchestrate ACI creation without writing custom code, which is simpler and more aligned with the requirement to 'run the container only when there are messages'.
Trap categories for this question
Scenario analysis trap
Azure Batch is designed for larger-scale parallel workloads; ACI is simpler for this scenario.
Detailed technical explanation
How to think about this question
Under the hood, the Logic Apps Container Instances connector uses the Azure Resource Manager REST API to create container groups with a specified image and resource requirements. Each queue message triggers a separate Logic Apps run, which in turn creates a new container instance, allowing parallel processing of multiple images. The container group is automatically deleted after completion (if configured), ensuring cost efficiency. In a real-world scenario, this pattern is ideal for sporadic workloads where you want to avoid paying for idle compute resources.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-204 question in full detail.
Develop Azure compute solutions — This question tests Develop Azure compute solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use Azure Logic Apps with a Container Instances connector. — Option A is correct because Azure Logic Apps provides a serverless workflow that can be triggered by a queue message (via the Azure Queue Storage connector) and then use the Container Instances connector to start a container group. This ensures the container runs only when messages are present and scales automatically by creating a new container instance per message, matching the requirement for event-driven, on-demand execution without idle costs.
What should I do if I get this AZ-204 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.