ProcessA runs in Container1 and Container2, which use Process Isolation (indicated by "Uses Hyper-V isolation: No"). In this mode, containers share the host’s kernel. Processes are isolated from each other but are visible in the host's process table. Thus, ProcessA is visible from the containers and Server1.

ProcessC runs in Container3, which uses Hyper-V Isolation (indicated by "Uses Hyper-V isolation: Yes"). This mode runs the container inside a highly optimized virtual machine. It provides a separate kernel, ensuring that processes inside the container are not visible to the host (Server1) or other containers. Consequently, ProcessC is only visible within Container3.

Microsoft Learn: "Windows Container Isolation Modes - Process Isolation," Section: Process isolation. [https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container#process-isolation]

Microsoft Learn: "Windows Container Isolation Modes - Hyper-V Isolation," Section: Hyper-V isolation. [https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container#hyper-v-isolation]

Official Microsoft Courseware: Course AZ-800T00: Administering Windows Server Hybrid Core Infrastructure, Module 6: "Deploying and managing containers on Windows Server."

IEEE Xplore: "Performance Evaluation of Windows Server Containers and Hyper-V Containers," Section III (Container Architecture). [https://doi.org/10.1109/CLOUD.2017.65]