A+ Core 2 · Part 2 · Mission 11
Learn how a support technician documents work, communicates with customers, and chooses an operating system or file system. Read a concept, answer its check, then apply it in a realistic ticket.
I can document and prioritize a ticket; follow SOPs and SLAs; communicate professionally; compare operating systems and file systems; and identify compatibility and end-of-support risks.
Open the Core 2 Test Readiness tracker — review relevant Operational Procedures and Operating Systems objectives after this mission. Completing the mission does not automatically mark them mastered.
Think of a help desk ticket as a journey: gather evidence before selecting a fix, and confirm the result before closing.
A technician needs repeatable processes, clear evidence, and a way to hand work to another technician.
Step-by-step approved instructions for a repeatable task. Use a checklist when steps must be followed consistently; use guidelines when judgment is needed.
A technician repeatedly forgets the final verification step. What should be improved?
The SOP checklist — A standard procedure should include verification and documentation.
An agreement defining measurable service commitments, such as response targets, resolution targets, and availability. These are not interchangeable.
A provider promises a reply within 2 hours. Which metric is this?
Response time — A response target is not a promise that the problem is fixed.
A ticket captures the issue, impact, category, priority, owner, evidence, attempted fixes, customer updates, resolution, and confirmation. A request is not necessarily an incident.
A user asks for a new account. Which category fits best?
Service request — Provisioning a new account is a planned request.
Severity describes technical impact; priority determines work order using impact, urgency, and organizational rules. A single-person outage may be urgent if business-critical.
A payroll outage affects everyone. What should rise?
Priority — Widespread impact and time sensitivity justify faster handling.
Tier 0 is self-service; Tier 1 initial diagnosis; Tier 2 specialized support; Tier 3 advanced engineering/vendor-level work. Follow local policy rather than assuming every company uses identical tiers.
A technician lacks permission to change a server. What next?
Escalate appropriately — Do not bypass authorization.
Knowledge-base articles document symptoms, prerequisites, steps, results, and when to escalate. A lessons-learned review identifies changes to prevent recurrence.
A fix works repeatedly. What should be updated?
Knowledge base — Record reusable troubleshooting steps and limitations.
Defines acceptable and prohibited behavior on organizational devices and networks. Follow privacy, access, and retention policies when writing tickets.
A ticket contains a password. What should you do?
Remove the secret — Never expose credentials in routine ticket notes.
Technical accuracy is not enough: the customer must understand what will happen, when, and what is safe.
Let the customer describe symptoms, paraphrase the concern, ask for confirmation, and avoid assumptions or blame.
A customer is frustrated. What comes first?
Listen and clarify — Acknowledge the concern before troubleshooting.
Open-ended questions uncover the story: “What changed before this started?” Closed-ended questions confirm specifics: “Does it happen on Wi-Fi?”
You know little about a problem. Which question type first?
Open-ended — Begin broadly, then narrow with confirmation questions.
Explain next steps, realistic timeframes, impact, and updates. Never guarantee a fix before diagnosing the cause.
A repair may take hours. What should you provide?
Realistic update — Give a supported timeline and follow-up plan.
Arrive prepared, avoid distractions and jargon, respect culture and accessibility needs, and do not view unrelated personal files.
You see private photos during support. What should you do?
Avoid access — Only inspect material needed and authorized for the task.
Stay calm, avoid arguing, state boundaries, and seek supervisor/security help for threats according to policy.
A caller becomes threatening. What next?
Follow safety policy — Escalate unsafe behavior rather than continuing an abusive exchange.
An operating system manages hardware and applications. A file system organizes data on storage. Neither term means the same thing.
Windows supports many vendors and enterprise tools. macOS is Apple’s desktop OS. Windows 11 compatibility includes supported CPU, TPM 2.0, Secure Boot capability, memory and storage requirements.
A PC lacks TPM 2.0. What should be checked?
OS requirements — Verify vendor and Microsoft compatibility before upgrading.
Linux distributions package a kernel with user-space tools; UNIX is a related family with its own history. ChromeOS is Linux-based and emphasizes managed, web-centered workflows.
A Linux device has no desktop. Can it still run?
Yes, via shell — A graphical desktop is not required for Linux.
iOS runs on iPhone, iPadOS on iPad, and Android on many vendors’ devices. Check app permissions, update support, and device-specific management.
An app fails after an OS update. What check first?
App compatibility — Check supported OS versions and updates.
NTFS supports Windows permissions and journaling; FAT32 has a 4 GiB minus 1 byte maximum individual file size; exFAT supports large files and broad device interoperability.
A 6 GB video will not copy to FAT32. Why?
File size limit — Use an appropriate file system after backing up data.
ext4 and XFS are common Linux file systems; APFS is Apple’s modern file system; ReFS emphasizes resilience for supported Windows workloads. Features vary by version and platform.
A macOS startup disk uses which modern format?
APFS — APFS is the normal modern Apple file system.
End of support means vendor updates and assistance may stop. Unsupported software increases risk and may violate organizational policy.
An OS no longer gets security fixes. What next?
Plan migration — Document risk and move to supported software.
Read the reported symptoms. Choose a priority and the safest first step. Priority is based on impact and urgency, not just the number of affected people. These are training scenarios; real organizations use their own priority matrix.
Campus-wide outage: high priority because impact is broad; confirm and escalate under incident procedures. Mouse request: low priority when work can continue, and follow normal service-request fulfillment. Payroll: high priority because the deadline creates business urgency even though one workstation is affected. Confirm symptoms before escalating. Do not claim a specific SLA without organizational policy.
Simulation assumes a healthy 32 GiB drive, enough free space, and a single file. Choose the computer OS, drive format, and file size. Results distinguish file-size limits from OS compatibility. Never reformat a real drive without a verified backup.
A staff member reports: “I cannot save a 6 GB training video to a USB drive. Smaller files work.” Select a category and next diagnostic step. Then write a professional update.
“I confirmed that smaller files copy successfully. I’ll check the drive’s format and file-size limits before recommending a safe next step. I’ll update you after the check; please keep the original file until we verify the copy.”
For each case, choose the best next action. These are original training tasks, not actual exam questions.
Choose an answer for each question. Feedback explains the clue. Questions are original and are not official CompTIA exam items.
These are additional external resources for reinforcement; their coverage may extend beyond this mission.
Some vendor materials and video catalogs change over time. CompTIA and A+ are trademarks of CompTIA, Inc.; this is an independent educational resource.