正解:E
Reference:
In Windows Server container scenarios, process isolation shares the host kernel, while Hyper-V isolation runs each container inside a lightweight Hyper-V VM that provides a stronger boundary. The Windows Server Hybrid Core Infrastructure guidance states that when you must run a Windows container with a VM boundary, you start it using Hyper-V isolation. Operationally, this is done at run time with the Docker CLI by specifying the isolation mode: docker run --isolation=hyperv .... Other parameters don't meet the requirement: --expose only publishes ports, --privileged is a Linux concept not used for Windows security boundaries, --runtime selects the OCI runtime (relevant to Linux), and --entrypoint overrides the default process but does nothing for isolation. Using --isolation=hyperv ensures the container launches on a minimal Hyper-V partition created by the Windows container host, satisfying scenarios that require strict separation, kernel mismatch tolerance, or enhanced defense-in-depth-exactly what the requirement "run the container on a Hyper-V virtual machine" describes. This aligns with the exam's emphasis on selecting the proper Windows container isolation mode to meet security and compatibility goals during deployment and operations.