You have a Microsoft Deployment Toolkit (MDT) deployment share.
From the Deployment Workbench, you open the New Task Sequence Wizard and select the Standard Client Upgrade Task Sequence task sequence template.
You discover that there are no operating system images listed on the Select OS page as shown in the following exhibit.
You need to be able to select an operating system image to perform a Windows 11 in-place upgrade.
What should you do?
To perform a Windows 11 in-place upgrade using Microsoft Deployment Toolkit (MDT), you need to have the operating system source files available in the deployment share. Importing a custom image file is typically used when you have a pre-created image, but for an in-place upgrade task sequence, you need the full set of source files from the Windows 11 installation media. This ensures that all necessary components and files are available for the upgrade process. Therefore, you should import a full set of source files to resolve the issue of missing operating system images and proceed with the upgrade.
The correct answer is B. Import a full set of source files. Here's why: Enabling monitoring (A) won't resolve the issue of missing operating system images. It only collects information about deployments. Importing a custom image file (C) is only necessary if you have a specific, pre-created image you want to use. In this case, the task requires a full set of source files to build the image. Running the Update Deployment Share Wizard (D) updates the share with changes made elsewhere, but it won't add new images unless they are already available in the source files. Importing a full set of source files (B) provides the necessary components for MDT to create the installation media, including the Windows 11 image. This is the standard way to add new operating systems to MDT deployment shares. Therefore, importing a full set of source files, which contains the Windows 11 installation files, will address the issue of missing images and allow you to proceed with the Windows 11 in-place upgrade task sequence.
Pretty sure it should be B. https://learn.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit#add-windows-10-enterprise-x64-full-source
B is the correct answer
B is correct
The keyword here is "perform a Windows 11 in-place upgrade" Cannot upgrade using custom images
I think this question may be missing something, this is what I found from one of the links below, this particular bit is important: Add Windows 10 Enterprise x64 (full source) Note If you have already have a Windows 10 reference image in the MDT Build Lab deployment share, you can use the deployment workbench to copy and paste this image from the MDT Build Lab share to the MDT Production share and skip the steps in this section. It says if there was already an image created then add this so you don't need to import the entire source. So we could presume there was already an image, so really B and C could be correct
Agree with VirtualJP
Upgrade with custom image can't be done. Only vanilla full source files
- Obtain the Windows 11 installation media or ISO. - Use the "Import Operating System" wizard in MDT to import the source files. After importing the source files, you should be able to see the operating system images listed when creating a task sequence for a Windows 11 in-place upgrade.
Import custom image file, Although option B is Correct as Windows is not Open source it is not viable
Here's why: Importing a full set of source files into the Deployment Workbench is necessary to have an operating system image available for the in-place upgrade task sequence. The in-place upgrade task sequence requires access to the Windows 11 source files to perform the upgrade. Options A, C, and D are not directly related to the availability of operating system images in the task sequence. Enabling monitoring (Option A) is for tracking deployment progress, importing a custom image file (Option C) is for using a custom image (not needed for an in-place upgrade), and running the Update Deployment Share Wizard (Option D) is for updating the deployment share but doesn't specifically address the lack of operating system images.
indeed B to me.
Thank you for your confidence, BUT can you back up your choice with documentation?