Skip to main content
Revy's Tech Journey, powered by Revtek
Back to Study
A+ Core 2 · CompTIA 220-1202 V15 · Objective C2-4.1

Given a scenario, implement best practices associated with documentation and support systems information management

Drill flashcardsFocused quizBrowse all objectives (sidebar view)

Objective 4.1: Given a scenario, implement best practices associated with documentation and support systems information management

Cert: CompTIA A+ Core 2 (220-1202) V15 Domain: 4.0 Operational Procedures Weight: Part of the 21% Operational Procedures domain Depth: Given a scenario, implement. The candidate must apply ticketing, asset management, and documentation practices.

What this objective tests

You should know what goes in a help-desk ticket, how asset management and CMDB work, what types of operational documents matter, and how SLAs work internally and externally.

Key facts

Ticketing systems:

  • The central record of every issue, request, and change in IT. Examples: ServiceNow, Zendesk, Jira Service Management, Freshservice, Atera, NinjaOne PSA, ConnectWise PSA.

User information (in a ticket):

  • Who is reporting the issue. Name, contact, department, location.

Device information:

  • What device is affected. Hostname, asset tag, serial number, OS, model.
  • Pulled from asset management or filled in by tech.

Description of issues:

  • What's happening. Specific symptoms, when it started, what changed, what's been tried.
  • Vague descriptions ("computer is slow") slow troubleshooting; concrete descriptions ("Outlook hangs on send/receive starting after Tuesday's Windows update") speed it up.

Categories:

  • Bucketing the ticket: Hardware, Software, Network, Account/Access, Request, Incident.
  • Drives routing and metrics.

Severity:

  • How impactful the issue is. Common scales: P1 (critical, system down) > P2 (urgent, major impact) > P3 (normal) > P4 (low).
  • Influences response time per SLA.

Escalation levels:

  • Tier 1 (front-line, common issues), Tier 2 (specialist, deeper diagnosis), Tier 3 (engineering or vendor).
  • Escalate when current tier can't resolve within reasonable time.

Clear, concise written communication:

  • Issue description: what's happening.
  • Progress notes: what's been tried, what was found.
  • Issue resolution: what fixed it, why, links to KB articles.
  • Future techs read this. Future you reads this. Write like someone else will need it.

Asset management:

  • Tracking hardware and software inventory: who has what, where, with what config, under what warranty.

Inventory lists:

  • Source of truth for hardware. Tag, serial, model, location, assigned user, status (active, in stock, retired, lost).

Configuration management database (CMDB):

  • Database of configuration items (CIs) and their relationships. CIs include hardware, software, services, locations, people.
  • ITIL concept; ServiceNow's flagship area.

Asset tags and IDs:

  • Sticker or laser-etched ID on equipment. Maps physical device to inventory record.

Procurement life cycle:

  • Stages: requirement > approval > order > receive > deploy > maintain > retire.
  • Each stage produces records.

Warranty and licensing:

  • Track hardware warranty expiration dates (vendor support coverage).
  • Track software licenses: count, allocation, renewal dates.

Assigned users:

  • Who currently has each asset. Updates as people change roles.

Incident reports:

  • Formal write-up of security incidents, outages, or major events. Includes timeline, scope, impact, root cause, response, lessons learned.

Standard operating procedures (SOPs):

  • Step-by-step documented procedures for repeatable tasks. Examples: software install, new user onboarding, password reset, server restart.

Software package custom installation procedure:

  • SOP for installing a specific app with the org's preferred settings, license keys, deployment quirks.
  • Repeatable; reduces install variance.

New user / onboarding setup checklist:

  • Standardized list for new employee IT setup: account creation, MFA enrollment, equipment assignment, app access, training.
  • Prevents "we forgot to set up X for the new hire."

User off-boarding checklist:

  • Reverse of onboarding. Disable accounts, retrieve equipment, transfer ownership of files, revoke licenses, document.

Service-level agreements (SLAs):

  • Contractual or internal commitment on response and resolution times.

Internal SLAs:

  • Between IT and the business it serves. "Tier 1 responds within 1 hour; P1 incidents resolved within 4 hours."

External / third-party SLAs:

  • Between you and your vendors (ISP, MSP, SaaS provider). Their commitment to you.

Knowledge base (KB) / articles:

  • Documented solutions to common issues. Often public-facing for users (FAQ) and internal-facing for techs (procedures).

Common gotchas

  • Vague ticket descriptions. "Email broken" vs "Outlook fails to send/receive starting after 2024-11-12 Windows update, error 0x80004005." The second one gets resolved faster.
  • Untagged asset. Device shows up in the field with no asset tag, no record. Either it's stolen, ad-hoc, or someone skipped the process. Investigate.
  • No CMDB relationships. Inventory exists but not the relationships (this server hosts this app for this department). Limits root-cause investigation.
  • Onboarding checklist missing MFA step. New hire calls back the next week locked out.
  • Off-boarding "we'll do it later." Departing employee retains access for weeks. Compliance and security risk.
  • No KB articles for recurring issues. Same problem solved fresh every time. Document repeat fixes.

Real-world context

For an MSP, the documentation surface looks like:

  • Ticketing system (PSA): every issue, change, request. Linked to clients, assets, users, SLAs.
  • RMM: monitoring data, automated remediation logs. Some PSAs integrate with RMM.
  • CMDB or inventory tool: Hudu, IT Glue, Confluence pages, or PSA-native asset module.
  • SOP library: New-client onboarding, common fix procedures, vendor management.
  • KB: for end-user self-service and tech internal reference.
  • Client-facing portal: ticket submission, SLA visibility, knowledge articles.

The discipline is "write it down" mixed with "make it searchable." Tickets, SOPs, and KB articles all need consistent tagging so future techs can find them.

Sources

  • [CompTIA A+ 220-1202 Exam Objectives Version 4.0, Section 4.1](../../../../../../30-RevyTechJourney/CompTIA%20A%2B%20220-1202%20Exam%20Objectives%20%284.0%29.pdf)
  • [ITIL: Service Management framework](https://www.axelos.com/certifications/itil-service-management)
  • [Atlassian: What is a CMDB](https://www.atlassian.com/itsm/it-service-management/cmdb)
  • [Microsoft Learn: ITSM basics](https://learn.microsoft.com/en-us/azure/azure-monitor/alerts/itsmc-overview)