Knowledge Management
About 10% of the CIS-ITSM exam — see all 6 domains.
Purpose and KCS
Knowledge Management captures, structures, and shares knowledge so issues are resolved faster and self-service deflects tickets. ServiceNow aligns to Knowledge-Centered Service (KCS): capturing knowledge as a by-product of solving problems, reusing it, improving it on use, and rewarding contribution. KCS-enabled features include creating articles in the flow of incident/problem work and flagging articles for improvement.
Data model and lifecycle
Articles live on the kb_knowledge table and belong to a Knowledge Base (kb_knowledge_base) organized by categories. The article lifecycle is Draft → (Review/Approval) → Published → Retired, optionally governed by knowledge workflows (publish and retire approval flows) and an article Valid to date, which is an expiration date (after it the article is no longer valid). Valid to does not itself schedule a review; the optional article expiry notification (off by default) sends a monthly email about articles that expire the next month.
User Criteria: the central testable concept
Access is controlled by User Criteria at the knowledge base level via four settings:
- Can Read: who may view articles.
- Can Contribute: who may create, edit, and retire articles.
- Cannot Read and Cannot Contribute: explicit exclusions, which take precedence over the "Can" settings when there is overlap.
Articles can also carry their own Can Read / Cannot Read user criteria. Knowledge categories organize articles but do not control who can read them.
User criteria match on roles, groups, companies, departments, locations, or scripted conditions. To let a group author articles in a base, they must be on Can Contribute (and generally hold a knowledge role). This precedence behavior (Cannot overrides Can) is a frequent exam item.
Feedback and search
Knowledge supports article feedback (helpful/flag, ratings, comments), knowledge search surfaced in workspaces and the portal, and contextual search that proposes relevant articles while logging an incident. Users can search/read in Employee Center and the Service Portal subject to user criteria.
Exam focus
- KCS = capture/reuse/improve/reward in the flow of work.
kb_knowledgearticles in akb_knowledge_base; Draft → Published → Retired.- User Criteria: Can Read / Can Contribute / Cannot Read / Cannot Contribute; Cannot overrides Can.
- Contextual search proposes articles during incident logging.
Sample questions from this domain
Three of the 30 in this domain, with the reasoning. The full set is in the question bank.
What is the primary purpose of Knowledge Management in ServiceNow?
- A. To find and remove the root cause of recurring incidents so the same failures stop happening
- B. To route support requests to the right group so agents can restore service as fast as possible
- C. To capture, store, and share knowledge so users and agents can resolve issues efficiently ✓
- D. To keep a reviewed record of each configuration item so agents can see what an issue affects
Why: Knowledge Management captures, stores, and shares knowledge so end users can help themselves and agents resolve issues faster. Removing root causes is the goal of Problem Management, fast restoration and routing describe Incident Management, and a record of configuration items is the job of the CMDB.
On which table are knowledge articles stored?
- A. kb_knowledge ✓
- B. kb_knowledge_base
- C. kb_feedback
- D. kb_category
Why: Knowledge articles are records on the kb_knowledge table. kb_knowledge_base holds the knowledge base records themselves, kb_category holds the categories inside a base, and kb_feedback holds ratings, comments and flags left on articles.
Which baseline mechanism controls which users can read or contribute to a particular knowledge base?
- A. User criteria (Can Read / Cannot Read / Can Contribute / Cannot Contribute) ✓
- B. Knowledge categories, with read and contribute roles set per category
- C. The knowledge base Managers field, listing the users allowed to read and write
- D. The knowledge role alone, which grants read and contribute rights in every base
Why: Access to a knowledge base is set with user criteria in its Can Read, Cannot Read, Can Contribute and Cannot Contribute related lists, and the Cannot lists win on overlap. Categories organize articles but do not control access. The Managers field names the people who manage the base, not its readers or authors. The knowledge role lets a user author articles, but user criteria still decide which bases that user can contribute to.