A containerised platform has grown to thirty services that must be scheduled across nodes, restarted automatically when they fail, upgraded without downtime, and able to find each other by name. Which hosting option matches that list?

Microsoft Certified: Azure Fundamentals (AZ-900), objective architecture-and-services. Azure architecture and services hard

Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.

Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.

The options

Correct Azure Kubernetes Service

Correct. Scheduling, self-healing, rolling upgrades and service discovery are the definition of orchestration, and Kubernetes Service is the managed orchestrator — Azure runs the control plane, you run the workloads.

Not correct Azure Container Instances

Wrong at this scale. Container Instances is the fastest way to run a single container precisely because there is no orchestrator involved — and an orchestrator is exactly what every requirement on this list is asking for.

Not correct One large virtual machine running all thirty containers, started by a shell script

Wrong. You would be hand-building an orchestrator, badly, and the single machine is a single point of failure for all thirty services at once.

Not correct A single App Service web app holding all thirty images

Wrong. App Service can run containers, but a web app hosts one application, so it cannot model thirty independently scheduled and independently upgraded services.

Why

Both container services are examinable and the split between them is the point. Container Instances runs a container quickly with nothing to manage — burst capacity, a batch job, a simple isolated task. Kubernetes Service exists when you need something to keep deciding where workloads run and to react when they fail. The tell in a question is the vocabulary of orchestration: scheduling, self-healing, rolling upgrades, service discovery.

Where this comes from

Cited
Microsoft AZ-900 study guide skill area architecture-and-services.compute-and-networking

Practise this

Reading one question is not practice. The trainer will draw a set from objective architecture-and-services and space the ones you get wrong.

Practise Microsoft Certified: Azure Fundamentals (AZ-900)

More questions on this objective

All questions on Azure architecture and services