Question
You have a Windows Server container host named Server1 that has a single disk.
On Server1, you plan to start the containers shown in the following table.
| Name | Description |
| --- | --- |
| Container1 | Container1 is a Windows container that contains a web app in development. The container must NOT share a kernel with other containers. |
| Container2 | Container2 is a Linux container that runs a web app. The container requires two static IP addresses. |
| Container3 | Container3 is a Windows container that runs a database. The container requires a static IP address. |
Which isolation mode can you use for each container? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Explanation
Container1: Hyper-V isolation only. Process-isolated containers share the host's kernel with the host and with each other. Hyper-V isolation runs each container in its own lightweight utility VM with its own kernel, so it is the only mode that meets the requirement that Container1 must not share a kernel with other containers.
Container2: Hyper-V isolation only. Containers share the kernel of the host they run on, so a Linux container cannot run directly on the Windows kernel with process isolation. On a Windows host, a Linux container runs inside a lightweight Hyper-V VM that supplies a Linux kernel. Static IP addresses are a networking setting and do not change which isolation mode is possible.
Container3: Hyper-V isolation or process isolation. Container3 is a Windows container with no kernel-separation requirement, and a static IP address can be assigned in either mode (for example, on a transparent or l2bridge network). Both process isolation and Hyper-V isolation are therefore supported.
