220-1102 Question 22
Single answerCompatibility concerns between operating systemsA small accounting firm uses a custom invoicing application that was written for Windows 7 and relies on a 32-bit ActiveX control in Internet Explorer. The firm is replacing several PCs with new systems running Windows 11 Pro. During testing, the application launches but the browser-based invoicing component fails to load. Management wants the lowest-cost solution that allows the staff to continue using the legacy application while the software vendor develops a supported replacement. Which action should the technician recommend FIRST?
- A
Enable Hyper-V and run a supported Windows 7 virtual machine dedicated to the legacy application
- B
Reformat the new PCs and install Windows 7 directly so the application runs natively
- C
Use Microsoft Edge in Internet Explorer mode to load the ActiveX component without any other changes
- D
Upgrade the application's ActiveX control from 32-bit to 64-bit in the browser settings
- E
Join the PCs to a workgroup instead of the domain so older browser components can run
Show answer and explanation
Correct answer: A
Explanation
This question tests the ability to choose a realistic compatibility strategy when migrating from an older operating system to a newer one. In A+ Core 2 scenarios, technicians should recognize that older applications may depend on deprecated browsers, plugins, drivers, or 32-bit components that are not fully supported on modern operating systems. The best first recommendation is usually to preserve the supported host OS and use a compatibility layer such as virtualization when the business must temporarily continue using legacy software. This aligns with industry best practices: avoid deploying unsupported operating systems like Windows 7 on production hardware, especially when security and compliance matter. Microsoft has retired Internet Explorer as a standalone browser in modern Windows versions, and while Edge IE mode can support some legacy sites, it is not a universal fix for every old ActiveX-dependent application. Virtualization is commonly used as a short-term mitigation while planning application modernization or vendor replacement.
- A. Correct.
Correct. Running the legacy application in a virtual machine is a practical compatibility solution when older software depends on deprecated components such as Internet Explorer and older ActiveX controls. This approach preserves the new Windows 11 host, limits risk, and avoids replacing the entire operating system. In real environments, legacy app support is often handled through virtualization or application isolation until the software can be upgraded. The technician should also verify licensing and security controls, but this is the best first recommendation given the cost and compatibility requirements.
- B. Incorrect.
Incorrect. Installing Windows 7 directly on new PCs is not an appropriate recommendation. Windows 7 is end of support, lacks current security updates, and may not have proper driver support for modern hardware. Although it might restore compatibility, it creates major security, compliance, and supportability problems. A+ best practices favor supported operating systems whenever possible.
- C. Incorrect.
Incorrect. Edge's Internet Explorer mode can help with some older web apps, but it does not guarantee compatibility with all legacy Internet Explorer dependencies, especially applications designed specifically for older OS versions and 32-bit browser controls. The scenario states that the component fails during testing on Windows 11, so assuming IE mode alone will resolve the issue is too optimistic and does not address broader OS compatibility concerns.
- D. Incorrect.
Incorrect. A technician cannot simply 'upgrade' a legacy 32-bit ActiveX control to 64-bit through browser settings. That would require vendor redevelopment or replacement of the control. This distractor reflects a common misconception that architecture mismatches can be fixed with a configuration change rather than software compatibility work.
- E. Incorrect.
Incorrect. Domain membership versus workgroup membership has nothing to do with whether an outdated ActiveX control or Internet Explorer-dependent application can run. This option confuses network management configuration with application compatibility.