220-1102 Question 293
Single answerImpact considerations for new applicationsA small accounting firm plans to deploy a new tax-preparation application to all employee laptops before the busy season. During pilot testing, the application runs slowly on several older systems, and one user reports that the install required a newer .NET component than was currently installed. The IT technician wants to reduce deployment issues and avoid disrupting users during business hours. Which action should the technician take FIRST to address the impact considerations of the new application?
- A
Perform a compatibility and requirements assessment, including hardware, operating system, and prerequisite dependencies, before scheduling the rollout
- B
Increase the virtual memory setting on all laptops and deploy the application immediately to keep the project on schedule
- C
Disable endpoint protection temporarily during installation to prevent conflicts with the new application
- D
Replace the application with a web-based alternative because local applications are more likely to fail on older systems
Show answer and explanation
Correct answer: A
Explanation
This question focuses on impact considerations for new applications, a common A+ Core 2 topic. Before deploying software broadly, technicians should assess system requirements, software dependencies, compatibility with the existing operating system, and the likely effect on user productivity. Pilot testing already revealed two key risks: poor performance on older hardware and a missing prerequisite (.NET). Best practice is to review vendor documentation for minimum and recommended requirements, confirm prerequisite components, test on representative systems, and plan deployment during low-impact times. In Microsoft environments, application vendors commonly document supported OS versions and required frameworks such as .NET, and enterprise deployment best practices emphasize validating these factors before rollout. This approach reduces failed installations, support tickets, and business disruption.
- A. Correct.
Correct. When evaluating the impact of a new application, the first step is to verify system requirements and dependencies such as CPU, RAM, storage, supported operating system version, and required components like .NET. This helps identify devices that need upgrades or remediation before deployment and reduces user disruption. In real environments, reviewing prerequisites and pilot results before broad rollout is standard change-management and deployment practice.
- B. Incorrect.
Incorrect. Increasing virtual memory might temporarily mask performance issues, but it does not address whether the systems meet the application's actual hardware, OS, or dependency requirements. Deploying immediately without validating compatibility increases the risk of failed installs, poor performance, and downtime.
- C. Incorrect.
Incorrect. Temporarily disabling endpoint protection is not an appropriate first step for impact analysis and can introduce unnecessary security risk. While security software can sometimes affect installation, the scenario points to prerequisite and performance issues, which should be evaluated through requirements checking and testing first.
- D. Incorrect.
Incorrect. Replacing the application with a web-based alternative is an unsupported assumption and not the first action an A+ technician should take. The issue described is about deployment impact and compatibility assessment, not application selection. A technician should first validate requirements and dependencies using the current approved application.