In the Administering Windows Server Hybrid Core Infrastructure content for File Services, Microsoft describes File Server Resource Manager (FSRM) as the feature used to control the types of files that users can store on file servers. The guide explains that a file screen "prevents users from saving unauthorized file types on a volume or in a folder by applying a file group (such as Audio and Video) or custom file name patterns (for example, *.mp4)." It further clarifies that file screening "does not affect access permissions to other files and folders and allows permitted file types to be stored without restriction." By contrast, NTFS permissions govern access (read/write/modify) and "cannot filter by file extension," and NTFS quotas and File Management Tasks address capacity and automated tasks, not content blocking. Therefore, to stop users from storing .MP4 while allowing all other files, you create a File Screen on the path to Share1 and block either the built-in Audio and Video file group or a custom pattern *.mp4. This aligns precisely with the exam guide's directive that FSRM File Screening is the supported and intended method to restrict file types on Windows file shares while leaving other file operations unaffected.

Explanation:

In the Windows Server container topic of Administering Windows Server Hybrid Core Infrastructure, Microsoft states the behavior of the two Windows container isolation modes very clearly:
* Process isolation: "Windows Server containers run with process isolation and share the kernel with the host. Because the container uses the host's kernel, the container base image must match the host OS version (including build) for the container to start."
* Hyper-V isolation: "With Hyper-V isolated containers, each container runs inside a lightweight virtual machine that has its own kernel, providing kernel-level isolation. Hyper-V isolation removes the requirement for the container image version to match the host, allowing older or different Windows versions to run on a newer host." Applying those rules to Host1 (Windows Server 2022):
* Image1 (Windows Server 2022) matches the host version. Therefore, it can run with process isolation (kernel shared and versions match). Hyper-V isolation is always available as well, so either process or Hyper-V isolation can be used.
* Image2 (Windows Server 2019) does not match the host's kernel version. With process isolation this mismatch prevents startup. However, Hyper-V isolation provides its own kernel boundary, so the container can run only with Hyper-V isolation.
Thus, the correct selections are: Image1 - Hyper-V isolation or process isolation; Image2 - Hyper-V isolation only.