This chapter covers the creation and use of knowledge base articles, a critical component of operational procedures for the CompTIA A+ Core 2 (220-1102) exam. Knowledge base articles are written documents that capture solutions to common technical problems, ensuring consistency and efficiency in troubleshooting. Approximately 5% of exam questions touch on this topic, often within the context of documentation and change management. Mastering this skill helps technicians avoid reinventing solutions and provides a reliable reference for team members.
Jump to a section
Creating a knowledge base article is like writing a detailed recipe for a complex dish that you've perfected over years. When you cook, you don't just list ingredients—you include exact measurements, cooking times, and troubleshooting tips like 'if the sauce is too thin, simmer for 5 more minutes.' Similarly, a knowledge base article must capture every step, tool, and decision point so that another technician can replicate your success without your experience. Just as a recipe gets tested by others to ensure it works, a knowledge base article should be peer-reviewed and validated. The article is the 'canonical source of truth'—like a well-worn cookbook in a busy restaurant kitchen—that prevents each cook from reinventing the wheel. When a new technician encounters an error message, they search the knowledge base instead of guessing, saving time and reducing errors. The article must be structured with clear headings, exact commands, and expected outcomes, much like a recipe's prep time, cook time, and yield. Without such documentation, institutional knowledge is lost when the expert leaves—like a chef taking their secret recipes to another restaurant.
What is a Knowledge Base Article and Why Does It Exist?
A knowledge base article is a documented solution or procedure that captures technical expertise for reuse. In IT support, knowledge base articles serve as the organization's collective memory. They exist to:
Reduce resolution time for recurring issues.
Ensure consistent solutions across different technicians.
Onboard new staff faster by providing a library of proven fixes.
Preserve institutional knowledge when employees leave.
For the 220-1102 exam, you need to understand that knowledge base articles are part of the "Operational Procedures" domain, specifically under "Given a scenario, implement documentation and change management best practices." The exam focuses on the structure, content, and lifecycle of these articles.
How It Works Internally – The Mechanism of Creation
A knowledge base article is not just a note; it follows a structured format to ensure usability. The typical components are:
Title: Clear, searchable, and descriptive (e.g., "Error 0x80070005 – Access Denied When Installing Update").
Symptoms: What the user or technician sees (e.g., error messages, behavior).
Cause: The root cause, determined through diagnosis.
Solution: Step-by-step instructions to resolve the issue.
Affected Systems: Hardware, software, or configurations involved.
Workaround: Temporary fix if a permanent solution is pending.
References: Links to related articles, vendor documentation, or RFCs.
Date and Author: For version control and accountability.
The creation process follows these steps: 1. Identify a recurring issue or a new problem that lacks documentation. 2. Diagnose and resolve the issue, documenting every step. 3. Write the article using a template, ensuring clarity and completeness. 4. Peer-review the article for accuracy and readability. 5. Approve and publish to the knowledge base. 6. Periodically review and update the article.
Key Components, Values, Defaults, and Timers
In a knowledge base system, each article has metadata: - Article ID: Unique identifier (e.g., KB12345). - Status: Draft, Published, Archived. - Version Number: Increments with each edit. - Last Reviewed Date: Typically set for annual review, but critical articles may be reviewed quarterly. - Owner: The person responsible for keeping the article current.
Defaults in many systems: - Review period: 365 days (one year). - Expiry: Articles older than 3 years may be automatically archived unless updated. - Access permissions: Usually read-only for technicians, edit for authors and admins.
Configuration and Verification Commands
While knowledge base article creation is not command-line driven, many IT service management (ITSM) tools have web interfaces or APIs. For example, in a system like ServiceNow or Jira Service Management, creating an article involves filling fields. There are no CLI commands for this on the CompTIA A+ exam. However, you should know how to search a knowledge base:
Use keywords from error messages.
Filter by product, component, or date.
Check the article's rating or number of times used.
How It Interacts with Related Technologies
Knowledge base articles are closely tied to: - Change Management: Articles may document steps for implementing a change. - Incident Management: When an incident is resolved, the solution can be turned into a knowledge base article. - Problem Management: Root cause analysis often leads to new articles. - Asset Management: Articles may reference specific hardware or software assets.
For the exam, remember that knowledge base articles are a form of documentation that supports other ITIL processes. They are not a standalone activity but part of a larger operational framework.
Writing Effective Knowledge Base Articles
To create a high-quality article:
Use consistent terminology.
Write in plain language, avoiding jargon unless necessary.
Include screenshots or diagrams where helpful.
Validate the solution by testing it on a clean system.
Anticipate common mistakes and include troubleshooting tips.
Example structure for a solution article:
Title: How to Reset a Forgotten Local Administrator Password in Windows 10 Symptom: Unable to log in to a Windows 10 workstation with administrator privileges. Cause: The administrator password was forgotten or not documented. Solution: 1. Boot the system from a Windows 10 installation media. 2. Select "Repair your computer" > Troubleshoot > Command Prompt. 3. Use the following commands to enable the built-in Administrator account:
net user administrator /active:yesRestart and log in with the Administrator account (no password).
Reset the original user's password via Local Users and Groups or net user.
Disable the Administrator account if desired:
net user administrator /active:noAffected Systems: Windows 10 Pro, Enterprise, Education (version 1809 and later). References: Microsoft KB article 4025684.
Common Pitfalls and How to Avoid Them
Too vague: "Check network settings" is not helpful. Specify exact settings to check.
Outdated information: Always verify that the solution works with current versions.
No context: Include why the solution works, not just how.
Assuming prior knowledge: Write for a technician with basic skills, not an expert.
Exam Relevance
The 220-1102 exam may present a scenario where you need to identify the best practice for creating documentation. For example:
Which of the following should be included in a knowledge base article? (Answer: Step-by-step instructions, cause, symptoms, workaround)
What is the first step in creating a knowledge base article? (Answer: Identify the issue and verify the solution)
Remember: Knowledge base articles are not just for errors; they can also document standard operating procedures (SOPs), onboarding steps, and configuration guidelines.
Identify Recurring Issue or Gap
The first step is to identify a problem that occurs frequently or a gap in existing documentation. This could be a common error message, a new software deployment, or a process that is currently undocumented. The technician should confirm that the issue is not already covered by existing articles. This step often involves checking incident logs, talking to colleagues, or reviewing help desk tickets. For the exam, know that knowledge base articles are created to prevent reinventing solutions and to standardize responses. A gap analysis may be performed to prioritize which issues need articles first.
Diagnose and Resolve the Issue
Before writing, the technician must fully understand the problem and have a verified solution. This involves troubleshooting the issue from start to finish, documenting each test and command used. The solution must be tested on a clean system to ensure it works without side effects. If a workaround is used, note it separately. The technician should capture exact error messages, log entries, and system configurations. This step ensures that the article is accurate and reliable. In an exam scenario, you might be asked what to do before writing an article: the correct answer is to verify the solution works.
Write the Article Using a Template
Using a consistent template ensures all articles have the same structure, making them easier to read and search. Templates typically include fields for title, symptoms, cause, solution, affected systems, workaround, references, and date. The title should be descriptive and include key error codes. The solution should be step-by-step, with commands in code blocks. Avoid ambiguous language. For example, instead of 'restart the service,' specify 'run `services.msc`, find the Print Spooler service, right-click and select Restart.' The article should be peer-reviewed before publishing. The exam may test the importance of using a template for consistency.
Peer Review and Approval
Before publishing, the article should be reviewed by another technician or a supervisor. The reviewer checks for technical accuracy, clarity, completeness, and adherence to the template. They may test the solution themselves. Any errors or omissions are corrected. After review, the article is approved and its status changed from 'Draft' to 'Published.' Some organizations require approval from a change advisory board (CAB) if the solution involves a change to the environment. The exam emphasizes that peer review helps catch mistakes and ensures quality. Failure to review can lead to incorrect solutions being used.
Publish and Communicate
Once approved, the article is published to the knowledge base. The knowledge base should be easily searchable by all technicians. The publication may trigger a notification to the team, especially if the article addresses a critical or common issue. The article's metadata is updated with the publication date and author. The article is now available for use. Technicians should be trained to search the knowledge base before escalating issues. The exam may ask about the importance of making articles accessible and searchable. A well-organized knowledge base with tags and categories improves efficiency.
Periodic Review and Update
Knowledge base articles are not static; they must be reviewed and updated regularly. The review cycle is often set at 1 year, but critical articles may be reviewed more frequently. During review, the article is checked for relevance, accuracy, and compatibility with current systems. If the solution is no longer valid, the article may be updated or retired. Outdated articles can cause confusion and wasted time. The exam may test the concept of 'knowledge base article lifecycle' and the need for scheduled reviews. Some systems automatically flag articles for review after a set period.
In a large enterprise IT support center, knowledge base articles are the backbone of first-level support. For example, a common issue is 'Outlook crashes when opening attachments.' A technician discovers that the cause is a corrupted temporary file. The solution is to clear the temp folder and disable a specific add-in. This is documented as a knowledge base article. When the help desk receives similar calls, they search for 'Outlook crash attachment' and find the article, resolving the issue in 10 minutes instead of 30. The article includes exact paths and commands, such as %temp% and Outlook.exe /safe. The article is reviewed quarterly because Outlook updates may change the behavior.
Another scenario: A company deploys a new VPN client. The initial setup fails for many users due to a missing certificate. The support team creates a knowledge base article with step-by-step instructions to install the certificate manually. The article includes screenshots and a link to the certificate file. This reduces support calls by 70%. The article is updated when the certificate expires or is replaced.
In a managed service provider (MSP) environment, knowledge base articles are shared across multiple client sites. A technician working on a client's server encounters an error: 'Event ID 1000, Application Error – svchost.exe.' The technician searches the internal knowledge base and finds an article from another team that solved a similar issue by applying a Windows update. The article includes the specific KB number and the registry key to verify the fix. This cross-team reuse saves hours of research. The MSP has a policy that any solution used more than three times must be documented as a knowledge base article.
Common misconfigurations: Articles that are too long or too short. An article that lists 20 steps without explanation overwhelms the reader. Conversely, an article that says 'restart the server' without specifying a maintenance window or impact analysis is dangerous. Best practice is to include prerequisites, expected outcomes, and rollback steps. Also, articles must be version-controlled; if a technician edits an article without approval, the old version is lost. Most systems track changes, but the exam emphasizes that only authorized personnel should edit articles.
The 220-1102 exam tests knowledge base article creation under Objective 4.1: 'Given a scenario, implement documentation and change management best practices.' Specific sub-objectives include: - 'Identify the components of a knowledge base article.' - 'Explain the purpose of knowledge base articles.' - 'Describe the process for creating and maintaining knowledge base articles.'
Common wrong answers on exam questions: 1. Choosing 'Write the article immediately after encountering an issue' – Candidates often think that documentation should be done right away, but the correct first step is to verify the solution works. Writing prematurely leads to inaccurate articles. 2. Selecting 'Include only the solution, not the cause' – Some believe brevity is key, but the exam expects articles to include both cause and solution for full understanding. 3. Thinking that knowledge base articles are only for errors – They can also document standard procedures, configurations, and policies. 4. Assuming that once published, an article never needs updating – The exam stresses the need for periodic review.
Specific numbers/values to memorize:
Typical review period: 1 year (365 days).
Statuses: Draft, Published, Archived.
Components: Title, Symptom, Cause, Solution, Workaround, Affected Systems, References, Date, Author.
Edge cases the exam loves:
What if a solution is a workaround and not a permanent fix? The article should clearly label it as a workaround and reference the permanent fix if known.
What if the article is for a security vulnerability? It should be marked as sensitive and access restricted.
What if multiple solutions exist? The article should list them in order of preference or complexity.
How to eliminate wrong answers:
If an answer says 'skip peer review to save time,' eliminate it – peer review is essential.
If an answer says 'use a narrative style,' eliminate it – technical articles should be structured and step-by-step.
If an answer says 'only document issues you personally encounter,' eliminate it – knowledge base articles should cover common issues from all sources.
Remember: The exam is scenario-based. Read the scenario carefully; it will often indicate whether the question is about creating, updating, or using a knowledge base article. Look for keywords like 'first step,' 'best practice,' 'most important,' and 'should be included.'
Knowledge base articles capture solutions to common problems, ensuring consistency and efficiency.
Essential components: Title, Symptoms, Cause, Solution, Workaround, Affected Systems, References, Date, Author.
The creation process: identify issue, diagnose/resolve, write, peer review, publish, maintain.
Peer review is critical for accuracy and quality.
Articles must be reviewed periodically (typically every 365 days) and updated or archived as needed.
Knowledge base articles support change management, incident management, and problem management processes.
Use a consistent template to ensure uniformity across articles.
Searching the knowledge base should be a first step in troubleshooting before escalating.
These come up on the exam all the time. Here's how to tell them apart.
Knowledge Base Article
Focuses on specific issues or errors.
Includes symptoms, cause, solution, and workaround.
Used reactively to resolve incidents.
Typically shorter, targeting a single problem.
Created after a problem is solved.
Runbook
Focuses on processes and procedures.
Includes step-by-step instructions for routine tasks.
Used proactively to perform operations.
Can be longer, covering complex workflows.
Created before a task is performed.
Mistake
Knowledge base articles are only for help desk technicians.
Correct
Knowledge base articles are used by all IT staff, including system administrators, network engineers, and security analysts. They document procedures, configurations, and solutions for any technical audience.
Mistake
A knowledge base article should be written as soon as the issue is encountered.
Correct
The article should be written only after the solution has been verified and tested. Writing prematurely can lead to incorrect or incomplete information. The correct sequence is: diagnose, resolve, verify, then document.
Mistake
The solution section should be brief and skip steps to avoid redundancy.
Correct
The solution must be detailed and step-by-step, including exact commands, paths, and expected outcomes. Skipping steps can cause confusion and errors. The article should be written for a technician with basic skills.
Mistake
Once published, a knowledge base article is final and does not need updates.
Correct
Articles must be reviewed and updated periodically (typically annually) to stay accurate. Software updates, new versions, or changes in environment can make an article obsolete. Outdated articles should be archived.
Mistake
Knowledge base articles are only for troubleshooting errors.
Correct
They can also document standard operating procedures (SOPs), onboarding checklists, configuration guides, and best practices. The exam recognizes that any repeatable process benefits from documentation.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
The first step is to identify a recurring issue or a gap in existing documentation. However, before writing, you must fully diagnose and verify the solution. The exam asks: 'What should you do first?' The correct answer is to identify the issue and confirm the solution works. Do not write the article until the solution is tested.
Yes, including the cause helps technicians understand why the solution works and aids in diagnosing similar issues. The exam expects articles to have both symptoms and cause. Omitting the cause can lead to misapplication of the solution.
Best practice is to review articles at least annually (every 365 days). Critical articles may be reviewed more frequently. The exam may ask about review cycles; remember the default is 1 year. Articles that are no longer accurate should be updated or archived.
A workaround is a temporary fix that allows the user to continue working while a permanent solution is developed. A solution is the definitive fix. In an article, clearly label workarounds and reference the permanent solution if known. The exam may test that workarounds should be documented separately.
Yes, but they may need to be restricted to authorized personnel. For security vulnerabilities, the article should be marked as sensitive and not include details that could be exploited. The exam may present a scenario where you need to decide the appropriate access level for a security-related article.
You should notify the article owner or submit a correction request. Do not edit the article directly unless you have permission. The exam emphasizes that only authorized personnel should modify articles to maintain version control and accuracy.
You can reference vendor documentation, but avoid direct plagiarism. Summarize steps in your own words and cite the source. The exam may test that articles should be original and tailored to your environment.
You've just covered Knowledge Base Article Creation — now see how well it sticks with free 220-1102 practice questions. Full explanations included, no account needed.
Done with this chapter?