easymulti selectObjective-mapped

A batch container in Azure Container Instances should stop after a successful run and may retry only when the process fails. Which two restart policies are correct for that style of workload? Select two.

Question 1easymulti select
Full question →

A batch container in Azure Container Instances should stop after a successful run and may retry only when the process fails. Which two restart policies are correct for that style of workload? Select two.

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Scheduled

Scheduled is not a supported restart policy for Azure Container Instances.

B

Best answer

Never

Never lets the container exit and stay stopped, which is useful for one-time batch jobs.

C

Best answer

OnFailure

OnFailure restarts the container only when it exits with a failure code, not after success.

D

Distractor review

Always

Always restarts the container after it exits, which is not appropriate for a completed batch job.

E

Distractor review

Manual

Manual is not a valid Azure Container Instances restart policy.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this AZ-104 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Never — For batch-style container work, the administrator should choose a restart policy that does not keep relaunching the container after a successful completion. Never is the simplest fit because the container exits and stays stopped. OnFailure is also appropriate when you want retries only if the process fails, while still allowing successful runs to finish and remain stopped. These are the two ACI restart policies that fit the described workload pattern. Why others are wrong: Always is designed for long-running services, because it restarts the container after exit regardless of outcome. Manual and Scheduled are not Azure Container Instances restart policies, so they are not valid choices. The scenario is about a one-time batch workload, so the policy must allow the run to end without endless restarts.

What should I do if I get this AZ-104 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.