Exam AZ-800 topic 3 question 6 discussion

Answer should be 1-Hyper-v 2-hyper-v or process (we can install wsl and configure process isolation for linux containers , earlier wsl didn't support window 2019 or 2022 . https://learn.microsoft.com/en-us/windows/wsl/install-on-server) 3-Hyper-v or process

Container1: Hyper-V Container2: Hyper-V Container3: Hyper-V or Process AFAIK, container running as process will utilize system's kernel. Obviously, linux cannot use window's kernel. Container, regardless of the mode, can have the capability to distribute multiple IP addresses, not just ports.

1.Hyper-V isolation only 2.Hyper-V isolation only 3.Hyper-V isolation only Hyper-V Isolation: This isolation mode runs each container in a lightweight, highly optimized Hyper-V virtual machine. Each Hyper-V isolated container gets its own dedicated kernel, network stack, and resources. This allows you to configure network interfaces within the container's virtual machine, including assigning multiple static IP addresses Process Isolation Limitations: While process isolation provides resource and process separation for Windows containers, it shares the host's network stack. Assigning a dedicated static IP address directly to a process-isolated Windows container is not a standard or straightforward configuration. You would typically rely on port mapping to access the database service on the host's IP address and a specific port. This doesn't fulfill the requirement of the container itself having a dedicated static IP address.

Container1: Hyper-V isolation only Container2: Hyper-V isolation only Container3: Hyper-V isolation or process isolation

Hyper-V isolation Hyper-V isolation Hyper-V or process

All the above answers are correct - Hyper V - Process - Hyper V or Process isolation

1 - https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container#hyper-v-isolation 3 - https://ubuntu.com/tutorials/windows-ubuntu-hyperv-containers#7-run-an-ubuntu-container-on-hyperv 3 - https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container

Container1: - Hyper-V isolation only This is a Windows container that must NOT share a kernel with other containers. To achieve this, you can use Hyper-V isolation. Container2: - Process isolation only This is a Linux container that requires two static IP addresses. In Windows Server, Linux containers cannot use Hyper-V isolation; To achieve this, you can only use process isolation. Container3: - Hyper-V isolation or process isolation This is a Windows container that runs a database and requires a static IP address. For Windows containers, you can use either Hyper-V isolation or process isolation, and it depends on your specific requirements. Since there are no specific constraints mentioned, you have the flexibility to choose either isolation mode.

Containers 1 and 2 should use Hyper-V isolation 3 can use both

If running in Process isolation mode, you must run on the same type of kernel (OS) as the host; Hyper-V isolation mode provides more flexibility when running non-Windows containers on Windows hosts. so Container2: Hyper-V

As I can understand, Linux container must use Hyper-V isolation mode, not process isolation.

In referenced document there is no information about what isolation type is posible for linux containers. Could anyone explain me (and give references) why linux container can use process isolation only? Some articles which I found in Internet suggests rather HyperV isolation only...