CompTIA A+ • Mission 01
Role: Junior IT Support Specialist. You are three minutes into your first shift when the first ticket arrives. Your job is not to randomly try fixes. Ask, observe, test, verify, and document.
Before Mission 01
You are not expected to know every answer yet. You are expected to know what you are preparing for and to build study habits now.
Mission briefing • Module 1
CompTIA Module 1 begins with a simple idea: IT support is a problem-solving job. The daily routine can change constantly because different users, systems, devices, and organizations use technology differently.
An IT specialist receives problems that may involve hardware, software, accounts, networks, printers, mobile devices, cloud services, security, or user configuration. Your first responsibility is to understand the problem before trying to fix it.
There may be no single predictable routine. One request may involve email, the next a disconnected server, and the next a device that will not power on. Broad knowledge and the ability to learn are part of the job.
Written and oral communication both matter. Ask useful questions, listen to the user, explain what you are doing, and write notes another technician can understand. Technical skill without clear communication can still produce poor support.
A clean workspace makes tools and parts easier to locate and reduces mistakes. Mental organization matters too: arrange your evidence and thoughts before communicating findings to users or other stakeholders.
A+ develops knowledge across hardware, software and operating systems, networking, cloud, security, and troubleshooting. You do not need to memorize everything today; you need to build connections as the course progresses.
Certification preparation gives you a defined body of knowledge and a way to demonstrate technical readiness. Use the exam objectives as a checklist—not as something to discover a week before the exam.
Lesson 1.2 • Troubleshooting methodology
Before choosing a fix, determine the cause, symptoms, consequences, priority, and severity. Critical systems and severe issues may need attention before lower-impact problems.
Gather information from the user. Capture exact error messages or sounds, determine who else is affected, how long the issue has occurred, and what changed recently. Before risky work, protect critical information with an appropriate backup or verify that the responsible person has done so.
Research when appropriate, physically inspect the system, and reproduce the problem when safe and useful. Decide whether evidence points toward hardware, software, a physical issue, or a logical/configuration issue.
Test theories individually so you know what the evidence actually proves. Do not change five things at once and then guess which one fixed the problem.
Check simple causes: power, plugs, cables, switches, input source, Wi-Fi state, mute settings, or other basic configuration. A simple cause can produce a dramatic symptom.
If the first theory fails, use the new evidence to form another. Escalate when the issue is beyond your skill or knowledge, or outside your authorization because of policy, warranty, or scope.
After identifying the cause, choose an authorized solution. Consider risk, policy, warranty, cost, downtime, user impact, and whether a workaround is needed before making the change.
Do not stop because the original symptom disappeared. Confirm the solution resolved the issue, make sure the full system works, and implement reasonable preventive measures when appropriate.
Record findings, actions, outcomes, parts used (including useful cost/purchase information), steps taken, software or physical tools used, and lessons learned. Good notes help the next technician and your future self.
Support queue
After each choice, explain your reasoning on the Technician Case File.
A teacher reports a completely black monitor. The desktop tower appears to be running.
One employee cannot reach a website. Nearby employees are working normally.
The PC was fine yesterday. The user installed a new application before leaving.
A user clicks Print, but no page appears. Other applications work normally.
You identify a failed component in a device that is under vendor warranty. Company policy says only the vendor may open it.
Your score: . Now finish the Technician Case File by explaining why each action belonged at that point in the troubleshooting process.
Open the Case FileModule 1 certification practice
These are original FamilyPD practice questions aligned to the concepts in Module 1—not CompTIA exam questions.
Build your study system
Your notebook should help Future You recognize exam clues quickly. Do not copy every paragraph. Capture the ideas, decisions, and visual cues you need to remember.
Title: IT Specialist + Troubleshooting Mindset
Key idea: An IT specialist is a problem solver, communicator, organized learner, and technician who works across hardware, software/OS, networking, cloud, and security.
Troubleshooting flow: Identify → Theory → Test → Plan/Implement → Verify → Document.
Exam clues: Circle or highlight words such as FIRST, NEXT, BEST, MOST likely. Note that a scenario may be testing judgment rather than a definition.
Missed-question note: Write the clue you missed—not the whole question. Example: “User says issue started after a change → ask what changed before replacing hardware.”
Add a real example: After using the Raspberry Pi 5, record one symptom, one theory you tested, what fixed it, and how you verified the result.
Primary source used for this lesson: CompTIA A+ 220-1201 Module 1 presentation, “What Does an IT Specialist Do?” including Lesson 1.1 “The Hero of Problem Solving” and Lesson 1.2 “The Troubleshooting Methodology,” © CompTIA, Inc.
Certification alignment: CompTIA A+ Core 1 (220-1201) V15 Exam Objectives and Core 2 (220-1202) V15 Exam Objectives.
This page uses independently written FamilyPD explanations, scenarios, interface design, and practice questions. It does not reproduce CompTIA exam questions or the supplied presentation slides.
CompTIA and A+ are trademarks of CompTIA, Inc. Family Personal Development, Inc. is not affiliated with or endorsed by CompTIA unless expressly stated.
