220-1102 Question 477
Single answerComplexityA small medical office asks a technician to recommend a replacement for a shared spreadsheet they use to track patient follow-up calls. The spreadsheet has become difficult to maintain because multiple employees edit it at the same time, accidental formula changes have caused reporting errors, and new staff require frequent retraining. The office manager says the solution must be easy for front-desk staff to learn, reduce mistakes, and avoid adding unnecessary features that staff will not use. Which recommendation BEST addresses the manager's concern about complexity while still meeting the business need?
- A
Replace the spreadsheet with a simple shared database or ticketing-style system that uses fixed fields, role-based access, and basic reporting
- B
Keep the spreadsheet, but add more worksheets, advanced formulas, and macros so all possible future workflows are covered
- C
Deploy a full enterprise resource planning (ERP) platform so the office can expand into inventory, accounting, and human resources later
- D
Move the spreadsheet to local copies on each employee's PC so accidental changes by one user do not affect others
Show answer and explanation
Correct answer: A
Explanation
The best answer is to replace the spreadsheet with a simpler, structured system designed for shared data entry. In CompTIA A+ Core 2 business and operational scenarios, technicians should recommend solutions that meet requirements while minimizing unnecessary complexity, user error, and support burden. A structured database or lightweight ticketing-style application is appropriate because it standardizes input, reduces accidental changes, and is easier to support than a heavily customized spreadsheet or oversized enterprise platform. This aligns with common IT best practices such as using the simplest effective solution, applying least privilege through role-based access, and selecting tools that improve maintainability and usability rather than adding features the organization does not need.
- A. Correct.
Correct. This recommendation reduces operational complexity by using structured data entry, limiting what users can modify, and providing only the features needed for the task. Fixed fields and role-based access help prevent accidental formula or layout changes, and a simpler workflow lowers training overhead. In A+ Core 2 scenarios, choosing the least complex solution that satisfies the requirement is a practical best practice.
- B. Incorrect.
Incorrect. Adding more worksheets, formulas, and macros increases complexity rather than reducing it. While it may seem flexible, it makes troubleshooting harder, raises the risk of user error, and usually increases training requirements. This reflects a common misconception that adding automation automatically makes a process easier for end users.
- C. Incorrect.
Incorrect. An ERP platform is far more complex than the office's stated need. Although it could provide broad business functionality, it would introduce unnecessary cost, administrative overhead, and training for a small task focused on follow-up tracking. This is an example of overengineering a solution instead of matching the tool to the business requirement.
- D. Incorrect.
Incorrect. Local copies would reduce collaboration and create version-control problems. Employees would likely work from different files, causing duplicate or conflicting information. This does not solve the root issue of complexity and data integrity; it shifts the problem into manual reconciliation.