Which TWO of these statements about Azure compute types are true?

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

Choose 2.

Correct Containers on one host share that host's operating system kernel, which is why they start faster and pack more densely than virtual machines

True. Sharing the kernel removes a whole guest operating system per instance, and with it the boot time, the memory footprint and the patching.

Correct Azure Container Instances runs a container without you operating an orchestrator, while Azure Kubernetes Service exists for when you need scheduling, self-healing and rolling upgrades

True. That division is the usual exam discriminator: one container quickly and simply against a fleet that needs orchestrating.

Not correct A container isolates as strongly as a virtual machine, because each container boots its own kernel

False, and the reasoning is exactly backwards. Containers do not boot a kernel; they share the host's. That shared kernel is the reason their isolation boundary is weaker than a virtual machine's.

Not correct An Azure Function can only be started by an incoming HTTP request

False. HTTP is one trigger among many — a timer, a message on a queue, a new blob, or an event from another service will all start a function, which is what makes it event-driven rather than merely a web endpoint.

Not correct Adopting containers removes the need to decide how many instances of a service to run

False. Something still has to decide the replica count and react to load — you, an autoscaler, or an orchestrator you configured. Containers change the packaging, not the capacity question.

Why

Line the three compute types up by what you give away and what you get back. Virtual machines: full control, full responsibility, slowest to start. Containers: shared kernel, portable images, fast and dense, with orchestration as a separate decision — Container Instances for one container, Kubernetes Service for a fleet. Functions: no server in view at all, started by an event, billed by execution.

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