70-695 · Question #46
You plan to sequence a 32-bit application named App1. App1 is compatible with Windows 7 and Windows 8.1. You have the following operating systems deployed to the network: -64-bit version of Windows…
The correct answer is A. 1. A 32-bit App-V package is generally compatible across different 32-bit and 64-bit Windows operating system versions as long as the application itself supports those OS versions. Therefore, only one App-V package is needed for a 32-bit application compatible with both Windows 7…
Question
You plan to sequence a 32-bit application named App1. App1 is compatible with Windows 7 and Windows 8.1. You have the following operating systems deployed to the network:
-64-bit version of Windows 8.1 Enterprise -64-bit version of Windows 8.1 Pro -32-bit version of Windows 8.1 Pro -64-bit version of Windows 7 Enterprise -32-bit version of Windows 7 Pro -64-bit version of Windows 7 Pro You need to identify the minimum number of Microsoft Application Virtualization (App-V) packages that must be created to ensure that App1 can run on all of the client computers on the network. How many App-V packages should you identify?
Options
- A1
- B2
- C3
- D4
- E6
How the community answered
(43 responses)- A77% (33)
- B2% (1)
- C5% (2)
- D12% (5)
- E5% (2)
Why each option
A 32-bit App-V package is generally compatible across different 32-bit and 64-bit Windows operating system versions as long as the application itself supports those OS versions. Therefore, only one App-V package is needed for a 32-bit application compatible with both Windows 7 and 8.1.
For a 32-bit application, App-V sequencing creates a package that can run on both 32-bit and 64-bit versions of supported Windows operating systems, as 64-bit Windows includes the WoW64 (Windows-on-Windows 64-bit) subsystem to run 32-bit applications. Since the application App1 is compatible with Windows 7 and Windows 8.1, a single 32-bit App-V package will suffice for all listed operating systems.
There is no technical requirement to create separate packages based on Windows 7 vs. 8.1 or Pro vs. Enterprise editions for a 32-bit App-V application.
Creating multiple packages is unnecessary when a single 32-bit package can cover all listed compatible operating system variations.
This choice suggests an incorrect understanding of App-V package compatibility across different Windows versions and architectures for 32-bit applications.
This choice implies a need for a package per specific OS version and architecture, which is not true for 32-bit App-V applications.
Concept tested: App-V package compatibility for 32-bit applications
Source: https://learn.microsoft.com/en-us/windows/application-management/app-v/appv-sequencer-deployment-guide
Topics
Community Discussion
No community discussion yet for this question.