The answer is cold start latency, as this is the primary factor when choosing between Azure Functions Consumption plan and Azure Container Instances for a background job processing Service Bus messages. On the Consumption plan, Azure Functions can experience cold starts because the runtime initializes from zero after a period of inactivity, introducing delay for the first message, whereas Azure Container Instances maintain a warm state once deployed, eliminating this latency. For the AZ-204 exam, this distinction tests your understanding of serverless execution models and scaling behavior—specifically that the Consumption plan auto-scales to handle up to 200 concurrent instances per function app, while Container Instances require manual scaling or KEDA orchestration. A common trap is assuming both services have identical startup performance; remember that Consumption plan trades cold starts for automatic scaling, while Container Instances trade scaling complexity for consistent responsiveness. Memory tip: "Cold starts are the price of auto-scaling convenience."
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.
Which THREE factors should you consider when choosing between Azure Functions (Consumption plan) and Azure Container Instances for running a background job that processes messages from Azure Service Bus?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Scaling behavior (automatic vs. manual).
Option A is correct because Azure Functions on the Consumption plan automatically scales out based on the number of incoming Service Bus messages, handling up to 200 concurrent instances per function app, while Azure Container Instances require manual scaling or external orchestration (e.g., KEDA) to adjust the number of container groups. This makes scaling behavior a key differentiator when choosing between the two services for a background job.
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.
✓
Scaling behavior (automatic vs. manual).
Why this is correct
Functions auto-scale; ACI may need manual scaling or scale rules.
Related concept
Read the scenario before looking for a memorised answer.
✓
Cost model (per execution vs. per second).
Why this is correct
Functions pay per execution; ACI pays per second of container runtime.
Related concept
Read the scenario before looking for a memorised answer.
✗
Ability to use custom base images.
Why it's wrong here
Both can use custom images (Functions Linux supports custom containers).
✗
Native support for Service Bus trigger.
Why it's wrong here
Both support Service Bus triggers.
✓
Cold start latency.
Why this is correct
Functions Consumption plan has cold starts; ACI does not.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume Azure Container Instances are always cheaper or more flexible for custom images, but they overlook the critical operational difference in scaling behavior and native trigger support, which are primary decision factors for event-driven background jobs.
Detailed technical explanation
How to think about this question
Under the hood, Azure Functions Consumption plan uses the Scale Controller to monitor the Service Bus queue length via the GetMessages API and adjusts the number of function instances accordingly, with a default maximum of 200 instances. In contrast, Azure Container Instances rely on the container group's CPU/memory limits and require manual scaling or integration with KEDA, which uses the Service Bus REST API to trigger scaling decisions. A real-world scenario where this matters is a high-throughput order processing system: Functions can handle sudden spikes automatically, while Container Instances might require pre-provisioned instances or custom autoscalers to avoid message backlog.
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: Scaling behavior (automatic vs. manual). — Option A is correct because Azure Functions on the Consumption plan automatically scales out based on the number of incoming Service Bus messages, handling up to 200 concurrent instances per function app, while Azure Container Instances require manual scaling or external orchestration (e.g., KEDA) to adjust the number of container groups. This makes scaling behavior a key differentiator when choosing between the two services for a background job.
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.