Implement Best Practice Documentation

Question 1

Answer 1

Defining help-desk categories in the osTicket ticketing system.

Question 2

Answer 2

Lansweeper inventory management software.

Question 3

A Standard Operating Procedure (SOP)

Answer 3

is a detailed, step-by-step instruction set designed to ensure tasks are performed consistently and in alignment with organizational policy, helping employees work securely, efficiently, and with accountability—especially in areas like software installation, user onboarding, and offboarding.

Question 4

Ticketing systems

Answer 4

streamline IT support by creating and tracking unique support cases—each ticket includes user and device details, issue descriptions, urgency assessments, and potential troubleshooting steps, with escalation protocols if initial efforts don’t resolve the problem.

Question 5

Ticket categories

Answer 5

—like Requests, Incidents, and Problems—help organize support issues for efficient handling and reporting, though simplified user-facing options (e.g., “Help” or “New Device”) and flexible keyword tagging can improve usability and technician workflow.

Question 6

CRM (Customer Relationship Management)

Answer 6

is a centralized system that manages all interactions between a company and its customers.

Question 7

Asset ID

Answer 7

is a unique identifier, often a string of characters, assigned to a specific asset for tracking and management purposes.

Question 8

Ticket categories

Answer 8

help organize and route support requests efficiently by classifying them as Requests, Incidents, or Problems, but for end-user clarity, systems often use simplified labels (like Help or Onboarding) and may supplement with technician-assigned subcategories or keyword tags to improve tracking and reporting.

Question 9

Severity levels classify

Answer 9

support tickets by impact, typically as critical, major, or minor, to prioritize responses and escalate issues appropriately.

Question 10

Effective ticket management relies

Answer 10

on clearly tracking ownership and status throughout the troubleshooting process, using consistent documentation and escalation paths to ensure timely resolution and accountability.

Question 11

Escalation levels define how unresolved tickets move through support tiers

Answer 11

—from self-service (Tier 0) to frontline agents (Tier 1), then senior/internal or external experts (Tier 2), and finally engineering or leadership (Tier 3)—with ownership tracked at every stage to ensure progress and clear communication.

Question 12

Clear written communication in ticketing systems ensures

Answer 12

that all stages—problem description, progress notes, and problem resolution—are accurately documented using plain, concise language, enabling effective troubleshooting, collaboration, and transparency throughout the ticket’s lifecycle.

Question 13

Incident reports—also known as after-action reports or lessons learned—are

Answer 13

detailed reviews of major or critical incidents that gather input from all stakeholders to uncover root causes and propose solutions or preventive measures to reduce the likelihood of recurrence.

Question 14

Effective asset identification and inventory management ensures

Answer 14

organizations maintain a comprehensive catalog of both tangible assets (like deployed and backup hardware) and intangible assets (such as software licenses and intellectual property), supporting consistent provisioning, upkeep, and decommissioning throughout the IT service lifecycle.

Question 15

An asset-management database system centralizes

Answer 15

information like hardware specs, asset IDs, locations, assigned users, and service history. Tools like Lansweeper enhance this by scanning networks to automatically gather and update inventory data, streamlining both asset visibility and lifecycle tracking.

Question 16

Asset tags—like

Answer 16

barcodes and RFID stickers—provide unique IDs for each asset, enabling easy identification, tracking, and real-time location updates within inventory systems, which enhances asset management and helps deter theft.

Question 17

Network topology diagrams visually represent how

Answer 17

networked assets connect—both physically (e.g., cabling, switches, patch panels) and logically (e.g., VLANs, security zones, IP subnets). These diagrams can be manually created with tools like Microsoft Visio or automatically generated via network mapping software, helping teams plan, troubleshoot, and secure IT infrastructure.

Question 18

Asset documentation tracks t

Answer 18

he asset procurement life cycle, which includes: approving changes, budgeting and selecting vendors, securely deploying the asset, maintaining it during use, and safely disposing of it by removing sensitive data before decommissioning.

Question 19

Each asset record should include

Answer 19

procurement documentation like invoices, warranty or support contracts, and contact details, while software entries must also track licensing information, including allocated devices or users and any usage limits.

Question 20

Assigning assets to users or security groups ensures

Answer 20

clear accountability and management responsibility, avoiding the risks of anonymous or shared access.

Question 21

Linking inventory records to product documentation and knowledge base articles enhances

Answer 21

support by enabling self-service, providing context for recurring issues, and streamlining diagnostics through asset history and verified resources.

Question 22

knowledge base (KB)

Answer 22

is a centralized repository of information used to store, manage, and share knowledge within an organization or for its customers.

Question 23

Change management encompasses

Answer 23

structured policies and procedures designed to minimize disruption from configuration changes, ensuring that updates to systems or services are planned, tested, approved, and documented—closely aligning with configuration management to maintain system integrity and operational stability.

Question 24

The ITIL Configuration Management Model outlines

Answer 24

best practices for managing IT services by defining service assets, configuration items (CIs), and their secure configuration and performance baselines, with the main challenge being how much detail to document and maintain—especially during system changes.

Question 25

A change request documents

Answer 25

A change request documents the **need, purpose, and scope** of a proposed adjustment—whether reactive or proactive—and outlines its risks, benefits, affected systems, and success criteria, all formalized in a request-for-change (RFC) for approval.

Question 26

Change Advisory Board (CAB)

Answer 26

Normal or minor changes may be approved by a supervisor, but **major changes require review by a Change Advisory Board (CAB)**, which evaluates business justification, technical feasibility, and risks—with representation from stakeholders, implementers, and budget approvers.

Question 27

Risk analysis assigns a risk level to

Answer 27

a proposed change—based on quantitative metrics or qualitative insights—to guide approval decisions and prepare stakeholders for potential impacts.

Question 28

Testing and implementing a change involves

Answer 28

assigning a responsible person, conducting pre-implementation testing (often in a sandbox), scheduling during low-risk windows, notifying stakeholders, and preparing a rollback plan in case issues arise.

Question 29

End-user acceptance is fostered by involving

Answer 29

user-focused stakeholders during change planning, conducting user acceptance testing (UAT) for impactful updates, and providing training and priority support to ease transitions and reduce resistance.

Question 30

An Acceptable Use Policy (AUP)

Answer 30

defines appropriate usage of organizational resources to prevent misuse, enforce security, and meet compliance requirements—often supplemented by visible reminders like login splash screens to reinforce regulated behaviors.