Question
You have a Windows Server container host named Server1.
You start the containers on Server1 as shown in the following table.
You need to validate the status of ProcessA and ProcessC.
Where can you verify that ProcessA and ProcessC are in a running state? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
| Name | Image | Uses Hyper-V isolation | Process running on container |
| --- | --- | --- | --- |
| Container1 | microsoft/iis | No | ProcessA |
| Container2 | microsoft/iis | No | ProcessB |
| Container3 | microsoft/iis | Yes | ProcessC |
| Container4 | microsoft/iis | Yes | ProcessD |
Explanation
ProcessA: Container1 and Server1 only. Container1 uses process isolation, so it shares the kernel with the host. A process running in it is a real process on Server1 and appears in Get-Process on the host with the same process ID it has inside the container. Windows containers still isolate the process and thread ID space per container, so ProcessA is not visible from Container2, Container3 or Container4.
ProcessC: Container3 only. Container3 uses Hyper-V isolation, so it runs inside its own lightweight utility VM with its own kernel. ProcessC exists only in that VM. On Server1, searching for the process with Get-Process fails, and only the vmwp worker process that hosts the utility VM is visible. Other containers cannot see it either, because each Hyper-V isolated container has its own kernel boundary.
