How to Run an Older Windows Container on an Upgraded Host?
You have a server named Server1 that runs Windows Server 2019 and hosts a container named Container1. Container1 uses a Windows Server 2019 base image that was built by using a Docker file. You upgrade Server1 to Windows Server 2022. You need to ensure that Container1 will run on Server1. The solution must minimize administrative effort. What should you do?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests understanding of Windows container isolation modes, specifically avoiding the trap of assuming process isolation works across major OS version upgrades.
When upgrading a Windows Server host, Windows containers built on older base images require Hyper-V isolation to function properly. Community consensus confirms that switching to Hyper-V mode is the correct solution with minimal administrative overhead.
Option C (Process isolation) is often incorrectly chosen because it offers better performance, but it fails when the host OS version differs from the container's base image version.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Hyper-V isolation encapsulates each container in a lightweight VM, providing its own isolated kernel. This architecture allows containers built on Windows Server 2019 to run seamlessly on a Windows Server 2022 host without requiring image modifications or rebuilds. Selecting this option directly satisfies the requirement to minimize administrative effort while ensuring compatibility after the host upgrade.Why the Other Options Are Wrong
Process isolation shares the host kernel, meaning the container OS must exactly match the host OS version; upgrading the host breaks this compatibility. Modifying the Dockerfile or rebuilding the base image would force developers to update all dependencies and reconfigure the build pipeline, violating the minimal effort constraint. These alternatives introduce unnecessary deployment delays and maintenance overhead.Community Comment Notes
Candidates overwhelmingly agreed on Option A, highlighting that Hyper-V isolation is the standard workaround for cross-version container compatibility. Comments consistently emphasized that this approach requires zero code changes or image regeneration, making it the most efficient operational decision. The unanimous voting reflects strong alignment with Microsoft's official container migration guidance.Official Reference
- https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyper-v-container
- https://learn.microsoft.com/en-us/virtualization/windowscontainers/about/
- https://techcommunity.microsoft.com/t5/windows-server-administration/running-windows-containers-on-different-os-versions/ba-p/386760
Exam Strategy
Always verify whether the exam scenario involves host OS version mismatches when dealing with Windows containers. If compatibility across different server versions is required, default to Hyper-V isolation to avoid kernel conflicts and save deployment time.