Why containers on Azure matter - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use containers on Azure instead of traditional virtual machines?

Imagine you want to run multiple small apps on Azure. Which reason best explains why containers are better than traditional virtual machines for this?

A Containers cannot run on Azure, only virtual machines can.

B Containers require a full OS for each app, making them heavier than virtual machines.

C Virtual machines start instantly and share the same OS kernel, unlike containers.

D Containers share the host OS and start faster, using fewer resources than virtual machines.

💡 Hint

Think about how much system resources each app needs and how quickly it can start.

Containers share the host operating system kernel, so they use less memory and start faster than virtual machines, which each run a full OS.

❓ Architecture

intermediate

Which Azure service is best for running containers with automatic scaling?

You want to deploy a containerized app on Azure that can automatically add or remove instances based on demand. Which service should you choose?

A Azure Kubernetes Service (AKS)

B Azure Virtual Machines

C Azure Blob Storage

D Azure Functions

💡 Hint

Look for a service designed to manage many containers and scale them automatically.

Azure Kubernetes Service (AKS) manages containerized apps and can automatically scale the number of container instances based on load.

❓ security

advanced

What is a key security benefit of using containers on Azure?

Which option describes a main security advantage of running containers on Azure?

A Containers isolate applications from each other, reducing risk if one is compromised.

B Containers share all files and processes, so a breach affects all apps equally.

C Containers require no security updates because they are isolated from the host OS.

D Containers automatically encrypt all data without configuration.

💡 Hint

Think about how containers keep apps separated to limit damage.

Containers provide process and filesystem isolation, so if one container is compromised, others remain protected.

❓ service_behavior

advanced

What happens when you update a container image in Azure Container Instances (ACI)?

You have a container running in Azure Container Instances. You update the container image in your registry. What happens to the running container?

A Azure Container Instances deletes the container and creates a new one instantly.

B The container automatically updates itself without downtime.

C The running container does not change until you manually restart or redeploy it.

D The container crashes because the image changed.

💡 Hint

Consider how Azure Container Instances manages running containers and image updates.

Azure Container Instances does not automatically update running containers when the image changes; you must redeploy or restart the container.

✅ Best Practice

expert

Which practice best ensures reliable container deployments on Azure Kubernetes Service (AKS)?

To keep your containerized app running smoothly on AKS, which practice is most important?

A Disable automatic scaling to avoid unexpected changes.

B Use health probes (liveness and readiness) to monitor container status and restart unhealthy containers automatically.

C Deploy all containers on a single node to reduce network latency.

D Manually check container logs daily and restart pods if needed.

💡 Hint

Think about how AKS can detect and fix problems with containers automatically.

Health probes let AKS know if containers are healthy or ready to serve traffic, enabling automatic restarts and better reliability.