- A
Always
Why wrong: Always restarts the container after it exits, which is not what you want for a completed one-time job.
- B
OnFailure
Why wrong: OnFailure restarts the container when it exits with an error, so successful completion can still leave it stopped, but this policy is not the cleanest fit for a one-time task that should never restart.
- C
Never
Never is the correct restart policy for a one-time task that should run once and then stop. Azure Container Instances will not try to restart the container after it exits, even if it finishes successfully. That behavior matches import jobs, batch scripts, and other short-lived workloads that should complete and remain stopped.
- D
Manual
Why wrong: Manual is not a valid Azure Container Instances restart policy for a container group.
Quick Answer
The answer is Never. This is the correct restart policy for a one-time job in Azure Container Instances because it ensures the container group runs exactly once and does not restart after the job finishes successfully, regardless of the exit code. On the AZ-104 exam, this question tests your understanding of the three ACI restart policies—Always, OnFailure, and Never—and their appropriate use cases. A common trap is confusing OnFailure with Never; remember that OnFailure only prevents restarts on success but will restart on failure, while Never stops all restarts entirely. For a one-time import job that must not restart after completion, Never is the only policy that guarantees the job runs once and stays stopped. Memory tip: think “Never again” for a job that should never rerun.
AZ-104 Deploy and Manage Azure Compute Practice Question
This AZ-104 practice question tests your understanding of deploy and manage azure compute. 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.
A container group runs a one-time import job in Azure Container Instances. After the job finishes successfully, it should not restart. Which restart policy should you choose?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Never
The 'Never' restart policy ensures that the container group does not restart after the job completes, which is ideal for a one-time import job that should run exactly once. Azure Container Instances supports three restart policies: Always, OnFailure, and Never. For a job that must not restart after successful completion, 'Never' is the correct choice because it prevents any automatic restart regardless of the exit code.
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.
- ✗
Always
Why it's wrong here
Always restarts the container after it exits, which is not what you want for a completed one-time job.
- ✗
OnFailure
Why it's wrong here
OnFailure restarts the container when it exits with an error, so successful completion can still leave it stopped, but this policy is not the cleanest fit for a one-time task that should never restart.
- ✓
Never
Why this is correct
Never is the correct restart policy for a one-time task that should run once and then stop. Azure Container Instances will not try to restart the container after it exits, even if it finishes successfully. That behavior matches import jobs, batch scripts, and other short-lived workloads that should complete and remain stopped.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Manual
Why it's wrong here
Manual is not a valid Azure Container Instances restart policy for a container group.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse 'OnFailure' with 'Never' for a successful job, but 'OnFailure' still allows restarts on failure, which violates the 'should not restart' requirement; the question explicitly states the job finishes successfully, so the correct policy is 'Never' to guarantee no restart under any condition.
Detailed technical explanation
How to think about this question
Under the hood, Azure Container Instances uses the restart policy to control the container group's lifecycle based on the exit code of the primary container. When 'Never' is set, the container group runs once and transitions to a 'Stopped' state after the container exits, regardless of the exit code. This is particularly useful for batch jobs or data migration tasks where idempotency is not desired, and it avoids incurring costs from unnecessary container restarts.
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 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
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Deploy and Manage Azure Compute — study guide chapter
Learn the concepts, then practise the questions
- →
Deploy and Manage Azure Compute practice questions
Targeted practice on this topic area only
- →
All AZ-104 questions
1,170 questions across all exam domains
- →
AZ-104 study guide
Full concept coverage aligned to exam objectives
- →
AZ-104 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related AZ-104 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Manage Azure Identities and Governance practice questions
Practise AZ-104 questions linked to Manage Azure Identities and Governance.
Implement and Manage Storage practice questions
Practise AZ-104 questions linked to Implement and Manage Storage.
Deploy and Manage Azure Compute practice questions
Practise AZ-104 questions linked to Deploy and Manage Azure Compute.
Implement and Manage Virtual Networking practice questions
Practise AZ-104 questions linked to Implement and Manage Virtual Networking.
Monitor and Maintain Azure Resources practice questions
Practise AZ-104 questions linked to Monitor and Maintain Azure Resources.
AZ-104 Azure RBAC practice questions
Practise AZ-104 questions linked to AZ-104 Azure RBAC.
AZ-104 storage account practice questions
Practise AZ-104 questions linked to AZ-104 storage account.
AZ-104 virtual network practice questions
Practise AZ-104 questions linked to AZ-104 virtual network.
AZ-104 NSG practice questions
Practise AZ-104 questions linked to AZ-104 NSG.
AZ-104 Azure Monitor practice questions
Practise AZ-104 questions linked to AZ-104 Azure Monitor.
AZ-104 backup practice questions
Practise AZ-104 questions linked to AZ-104 backup.
AZ-104 managed identity practice questions
Practise AZ-104 questions linked to AZ-104 managed identity.
Practice this exam
Start a free AZ-104 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this AZ-104 question test?
Deploy and Manage Azure Compute — This question tests Deploy and Manage Azure Compute — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Never — The 'Never' restart policy ensures that the container group does not restart after the job completes, which is ideal for a one-time import job that should run exactly once. Azure Container Instances supports three restart policies: Always, OnFailure, and Never. For a job that must not restart after successful completion, 'Never' is the correct choice because it prevents any automatic restart regardless of the exit code.
What should I do if I get this AZ-104 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 →
Last reviewed: Jun 11, 2026
This AZ-104 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-104 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.