Quick Answer
The answer is Azure WebJobs with Always On enabled. This is correct because enabling Always On on an App Service plan prevents the platform from recycling or unloading the web app during idle periods, which would otherwise terminate a long-running background job. Without Always On, the App Service recycles after 20 minutes of inactivity, and the Consumption plan imposes a strict 5-minute timeout, making it impossible to reliably run a job that lasts up to 30 minutes. On the AZ-204 exam, this question tests your understanding of background job execution models and the critical distinction between Always On and default App Service behavior. A common trap is choosing Azure Functions on a Consumption plan, which has a hard 230-second timeout, or assuming a WebJob alone is sufficient. Remember the memory tip: “Always On keeps the job from being gone”—if your background job runs longer than 5 minutes, Always On is the key to preventing recycling.
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 need to deploy a microservice that runs a long-running background job (up to 30 minutes). The job should not be affected by App Service recycling. Which Azure technology should you use?
Azure Automation Runbook
Why wrong: Runbooks are for automation, not long-running background jobs.
Azure WebJobs with Always On enabled
WebJobs run in App Service background and with Always On, they persist.
Azure Functions (Consumption plan)
Why wrong: Consumption plan functions have a timeout limit of 5 or 10 minutes.
Azure Kubernetes Service (AKS)
Why wrong: AKS is more complex than needed for a single background job.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Azure WebJobs with Always On enabled
Option B is correct because Azure WebJobs with Always On enabled ensures the WebJob runs continuously on a dedicated App Service instance, preventing it from being unloaded during idle periods or App Service recycling. This allows the long-running background job (up to 30 minutes) to complete without interruption, as the WebJob runs in the same process as the web app and is not subject to the 5-minute timeout of the Consumption plan.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Azure Automation Runbook
Why it's wrong here
Runbooks are for automation, not long-running background jobs.
Azure WebJobs with Always On enabled
Why this is correct
WebJobs run in App Service background and with Always On, they persist.
Related concept
Read the scenario before looking for a memorised answer.
Azure Functions (Consumption plan)
Why it's wrong here
Consumption plan functions have a timeout limit of 5 or 10 minutes.
Azure Kubernetes Service (AKS)
Why it's wrong here
AKS is more complex than needed for a single background job.
Common exam traps
The trap here is that candidates often choose Azure Functions (Consumption plan) because of its simplicity, forgetting that the Consumption plan has a hard 5-minute execution timeout, making it unsuitable for long-running jobs, while WebJobs with Always On is the correct choice for persistent background processing within App Service.
Detailed technical explanation
Under the hood, WebJobs with Always On enabled run as a continuous process within the same App Service sandbox, leveraging the same application pool; the Always On setting prevents the app pool from being shut down due to idle timeouts (default 20 minutes). This ensures the WebJob's background thread remains active, even during App Service recycling events (e.g., platform updates), because the WebJob is restarted automatically by the Azure WebJobs SDK's continuous job host. In a real-world scenario, this is critical for tasks like processing large queues or generating reports that must survive platform maintenance.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Develop Azure compute solutions — study guide chapter
Learn the concepts, then practise the questions
Develop Azure compute solutions practice questions
Targeted practice on this topic area only
All AZ-204 questions
997 questions across all exam domains
Microsoft Azure Developer Associate AZ-204 study guide
Full concept coverage aligned to exam objectives
AZ-204 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise AZ-204 questions linked to Develop Azure compute solutions.
Practise AZ-204 questions linked to Develop for Azure storage.
Practise AZ-204 questions linked to Implement Azure security.
Practise AZ-204 questions linked to Connect to and consume Azure services and third-party services.
Practise AZ-204 questions linked to Monitor, troubleshoot, and optimize Azure solutions.
Practise AZ-204 questions linked to AZ-204 fundamentals.
Practise AZ-204 questions linked to AZ-204 scenario.
Practise AZ-204 questions linked to AZ-204 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Develop Azure compute solutions — This question tests Develop Azure compute solutions — Read the scenario before looking for a memorised answer..
The correct answer is: Azure WebJobs with Always On enabled — Option B is correct because Azure WebJobs with Always On enabled ensures the WebJob runs continuously on a dedicated App Service instance, preventing it from being unloaded during idle periods or App Service recycling. This allows the long-running background job (up to 30 minutes) to complete without interruption, as the WebJob runs in the same process as the web app and is not subject to the 5-minute timeout of the Consumption plan.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Last reviewed: Jun 24, 2026
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.