Exam MD-102 topic 1 question 84 discussion

Should be A. https://learn.microsoft.com/en-us/mem/intune/apps/apps-win32-prepare

It's A. With win32 apps you are able to package applications with custom scripts, config files, multiple .msi and .exe files and whatever you did like in SCCM or MDT.

You can upload LOB apps directly with the msi or msix or msixbundle etc extensions. But you cannot upload .exe files in that option. Since the question doesn't really say what type of files there are, I'd package all files in a intunewim format and execute the script command to install it using a script.

so many discussable questions.. not stated correctly as MS always does. what do they mean with installation files... are that for example dll files or MSI? In case of any files except msi you should give answer A. if they mean multiple msi files it must be C in order to proceed (without the need of scripting). In my opinion this should not make it to the final exam questions, to many room for assumptions I do have several years experience in working with Intune

its A.

For deploying an application that contains multiple installation files to Windows 11 devices enrolled in Microsoft Intune, the first step is: A. Prepare the contents of App1 by using the Microsoft Win32 Content Prep Tool. The Microsoft Win32 Content Prep Tool is used to prepare complex applications, including those with multiple files and dependencies, for deployment via Microsoft Intune. This tool packages the application into a format (.intunewin) that is suitable for uploading to Intune and deploying across your managed devices. This process is necessary for applications that cannot be directly uploaded in their original format due to their complexity or the presence of multiple installation files. After preparing the app with the tool, you can then upload the packaged file to Intune for deployment.

A. As previously mentioned, you can't upload to intune until all the app files are wrapped with the .intunewin app wrapper

C is correct Win32 app is not mentioned in the question. So it's an normal app.

A. Prepare the contents of App1 by using the Microsoft Win32 Content Prep Tool. Here's why: Microsoft Win32 Content Prep Tool specifically prepares Windows applications for deployment with Microsoft Intune. It converts the installation files into the format required by Intune (.intunewin) and gathers information about the application for proper management. Android application package (APK) wouldn't be relevant since you're dealing with Windows 11 devices and App1. Uploading the contents directly without preparation can lead to deployment failures in Intune. Microsoft Deployment Toolkit (MDT) focuses on creating Windows images, not preparing existing applications for Intune deployment.

A. Prepare the contents of App1 by using the Microsoft Win32 Content Prep Tool.

Multiple files. Must be A. Need to wrap all the files as an intunewin

What should you do first? A. Prepare the contents of App1 by using the Microsoft Win32 Content Prep Tool

The Microsoft Win32 Content Prep Tool zips all files and subfolders when it creates the .intunewin file. this will solve the requirement with multiple installation files next step is to upload to intune

It doesn't mention at all that we are deploying a legacy application; how did people get to that conclusion?

nowhere in the question does it say anything about win32 apps preferably would use app wrapping tool first but c is most correct

Answer is A, uploading apps to intune requires them to be in the correct format. Cannot upload until the prep tool has been run.

The answer is: A. Prepare the contents of App1 by using the Microsoft Win32 Content Prep Tool. The other answer choices are incorrect: B. An Android application package (APK) is used to deploy Android apps, not Win32 apps. C. You cannot upload the contents of App1 to Intune until you have prepared the app content by using the Microsoft Win32 Content Prep Tool. D. The Microsoft Deployment Toolkit (MDT) is used to deploy Windows operating systems and other software to computers, not to manage mobile devices.