The answer is to enable the 'Always On' setting in the App Service application settings. This setting prevents the App Service from being unloaded after periods of inactivity, directly addressing the cold start latency that occurs during auto-scale events. Without 'Always On', idle instances are recycled by the platform, meaning when a new instance is spun up due to a CPU spike, it must go through a full initialization process—loading the application binaries, establishing database connections, and warming caches—which can take several minutes. On the AZ-204 exam, this scenario tests your understanding of how App Service plan scaling interacts with instance lifecycle management; a common trap is to assume that scaling out is instantaneous or that upgrading to a Premium tier alone solves the delay. The core issue is not the scaling trigger but the initialization time of new instances. Memory tip: Think of 'Always On' as keeping the engine warm—without it, every new instance is a cold start, and cold engines take time to rev up.
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.
Your company runs a critical web application on Azure App Service (Windows) that experiences intermittent high CPU usage. The application uses the Standard tier with auto-scaling based on CPU percentage. During auto-scale events, there is a delay of several minutes before new instances become available, causing temporary performance degradation. You need to reduce the latency of scaling out. What should you do?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable the 'Always On' setting in the App Service application settings.
The 'Always On' setting prevents the App Service from being unloaded after periods of inactivity, which reduces the cold-start latency when new instances are added during auto-scale events. Without 'Always On', idle instances may be recycled, causing delays of several minutes as the application re-initializes on new VMs.
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.
✗
Configure auto-scaling to use HTTP queue length as the metric.
Why it's wrong here
HTTP queue length is a scaling metric but does not improve instance startup speed.
✓
Enable the 'Always On' setting in the App Service application settings.
Why this is correct
Always On prevents the app from being unloaded, reducing cold start time.
Related concept
Read the scenario before looking for a memorised answer.
✗
Upgrade the App Service plan to the Premium tier.
Why it's wrong here
Premium tier provides additional features but does not eliminate cold start latency.
✗
Change the auto-scale metric to memory percentage instead of CPU.
Why it's wrong here
Memory metric does not address CPU-related performance issues.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume upgrading the tier or changing the metric will solve scaling latency, but the real bottleneck is the cold-start time of the application itself, which 'Always On' directly mitigates.
Detailed technical explanation
How to think about this question
When 'Always On' is disabled, the App Service's worker process (w3wp.exe) can be terminated after 20 minutes of inactivity, and new instances must reload the entire application from scratch, including DLLs, static files, and database connections. Enabling 'Always On' keeps the worker process alive, so when auto-scale adds a new instance, it can serve requests almost immediately because the application is already loaded in memory. This setting is particularly critical for applications with long startup times, such as those using Entity Framework or heavy dependency injection.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
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: Enable the 'Always On' setting in the App Service application settings. — The 'Always On' setting prevents the App Service from being unloaded after periods of inactivity, which reduces the cold-start latency when new instances are added during auto-scale events. Without 'Always On', idle instances may be recycled, causing delays of several minutes as the application re-initializes on new VMs.
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.