Overview
Knowledge Management is 12% of the exam with two objectives. The first is conceptual and configuration based: the article lifecycle from draft to published to archived, versioning and translation, the Knowledge-Centered Service (KCS) methodology, and Lightning Knowledge setup with record types, data categories, channels, approval processes and permissions.
The second applies that setup to requirements. You decide how Knowledge supports reps through the console Knowledge component, article recommendations and attaching articles to cases, and how it powers self-service through Experience Cloud help centers and public knowledge bases. Knowledge is also the main grounding source for Agentforce Service Agent, so article quality, structure and channel visibility now affect what an AI agent can answer and what it must refuse or escalate.
How it's tested
Questions describe a knowledge problem, such as content that cannot be found, articles visible to the wrong audience, slow publishing or stale answers from an AI agent. You choose the lifecycle step, KCS practice or configuration setting that fixes it with the least disruption.
-
Who sees it
An article audience is wrong, and you adjust channels, data category visibility or record type access.
-
Lifecycle and KCS
Content is slow, stale or duplicated, and you apply article versioning, approvals or KCS practices so reps capture knowledge in the flow of work.
-
Deliver it
Reps, customers or an AI agent need answers, and you choose the console component, help center or grounding approach.
Reps solve new product issues daily, but articles take three weeks to publish through a central team, so the help center lags behind. Adopting KCS lets licensed reps create draft articles while solving cases, with experienced coaches reviewing and publishing. Articles flagged as validated reach the help center quickly, and reuse data shows which ones need improvement.
Objectives 2
Official objectives from the Salesforce outline, in outline order.
4.1 Explain the Knowledge article lifecycle, Knowledge Centered Service (KCS), and Salesforce Knowledge Management configuration.Article states, KCS practice and Lightning Knowledge setup.
- What it means
- Articles move through draft, published and archived states, with new versions drafted from published ones. KCS is a methodology in which knowledge is captured, structured, reused and improved as part of solving cases. Lightning Knowledge stores articles as Knowledge records.
- What to understand
- Know the setup: enable Lightning Knowledge, assign Knowledge User licenses, create record types (for example FAQ and Troubleshooting), configure data category groups and visibility by role or profile, choose channels (Internal App, Customer, Partner, Public Knowledge Base), and add approval processes for publishing. Understand versioning, translation with multiple languages, article validation status and archiving. In KCS, the Solve Loop (capture, structure, reuse, improve) runs in daily work and the Evolve Loop measures and improves the system.
- How it shows up
- A setup or process requirement is given, and you pick the lifecycle action, KCS practice or configuration that meets it.
- Common confusion
- Mixing up record types, which define article structure, with data categories, which classify and control visibility.
4.2 Given a set of requirements, determine how to configure knowledge to deliver service support and self-service processes.Getting articles to reps, customers and AI agents.
- What it means
- Configured Knowledge must reach people where they work: reps in the console, customers on help centers and in messaging, and AI agents that answer questions.
- What to understand
- For reps, add the Knowledge component to case pages, enable article suggestions from case details, let reps attach articles to cases and share them in email or messaging, and allow article creation from the case. For self-service, publish to the Customer or Public Knowledge Base channel and expose articles through Experience Cloud with data category visibility for guest and authenticated users. For Agentforce Service Agent, ground answers in Knowledge, keep articles concise and well structured, and exclude internal content from external channels.
- How it shows up
- A delivery requirement is described, and you choose the channel, component or visibility setting that makes the right article appear.
- Common confusion
- Assuming publishing an article makes it visible everywhere, when channel and category settings also apply.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Lightning Knowledge
Knowledge stored as standard Knowledge records.
- Remember
- Uses record types and page layouts.
- Tested as
- Setup scenarios.
- Trap
- Thinking it still uses article types.
-
Article lifecycle
Draft, published, archived, with versions.
- Remember
- Edit a published article by creating a new draft version.
- Tested as
- Publishing questions.
- Trap
- Expecting direct edits to published content.
-
Knowledge User license
Feature license to author articles.
- Remember
- Needed to create and edit, not just read.
- Tested as
- Licensing questions.
- Trap
- Assigning it to read-only users.
-
Data categories
Hierarchical classification of articles.
- Remember
- Control visibility by role, profile or permission set.
- Tested as
- Audience and filtering scenarios.
- Trap
- Using record types for visibility.
-
Record types for Knowledge
Different article structures and layouts.
- Remember
- FAQ versus procedure templates.
- Tested as
- Structure scenarios.
- Trap
- Using them to classify by product.
-
Channels
Internal App, Customer, Partner, Public Knowledge Base.
- Remember
- Set per article to control where it appears.
- Tested as
- Self-service visibility.
- Trap
- Publishing internal steps to Public.
-
Approval process
Review step before publishing.
- Remember
- Useful in regulated content.
- Tested as
- Governance questions.
- Trap
- Applying it to every minor fix.
-
KCS Solve Loop
Capture, structure, reuse, improve.
- Remember
- Happens during case work.
- Tested as
- KCS scenarios.
- Trap
- Leaving creation to a separate team.
-
KCS Evolve Loop
Content health and process improvement.
- Remember
- Uses reuse and quality data.
- Tested as
- Program-level questions.
- Trap
- Ignoring metrics after launch.
-
Attach article to case
Links articles used to solve cases.
- Remember
- Feeds reuse metrics and recommendations.
- Tested as
- Measurement scenarios.
- Trap
- Skipping it so reuse cannot be measured.
-
Knowledge as AI grounding
Articles feed AI agent answers.
- Remember
- Quality and visibility shape responses.
- Tested as
- Agentforce scenarios.
- Trap
- Grounding on internal-only content externally.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Record types vs data categories
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Record types | Article structure and layout | Define fields and templates | Used to restrict audiences |
| Data categories | Hierarchical classification | Filtering and visibility | Used to change layouts |
Knowledge channels
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Internal App | Visible to internal users | Rep-facing content | Forgetting to tick it for reps |
| Customer | Visible to customer site users | Authenticated customers | Assuming guests see it |
| Partner | Visible to partner site users | Partner portals | Mixing with customer content |
| Public Knowledge Base | Visible to unauthenticated users | Open help centers and search | Publishing internal procedures |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Record types for audience
- What candidates pick
- Create a record type per audience.
- Why it looks right
- Record types change what users see on layouts.
- Why it's wrong
- Audience visibility is handled by data category visibility and channels; record types define structure.
Clue to watch for Requirement is about who can view articles.
-
Central authoring only
- What candidates pick
- Have a knowledge team write every article.
- Why it looks right
- It seems to protect quality.
- Why it's wrong
- It creates a bottleneck; KCS has reps capture content in the flow of work with coaching and review.
Clue to watch for Article backlog or slow publishing is mentioned.
-
Edit published directly
- What candidates pick
- Change the live article immediately.
- Why it looks right
- It is fastest.
- Why it's wrong
- Changes are made in a new draft version and republished, keeping version history.
Clue to watch for Audit or version history is required.
-
Publish means public
- What candidates pick
- Assume a published article appears on the help center.
- Why it looks right
- Publishing sounds final.
- Why it's wrong
- The article also needs the right channel and category visibility for site users.
Clue to watch for Customers cannot find a published article.
-
Approvals for everything
- What candidates pick
- Require approval on every article change.
- Why it looks right
- It adds control.
- Why it's wrong
- Heavy approval slows reuse; reserve approvals for regulated or high-risk content.
Clue to watch for Content is low risk and changes often.
-
AI fixes bad content
- What candidates pick
- Expect the AI agent to answer well from messy articles.
- Why it looks right
- Generative AI seems flexible.
- Why it's wrong
- Grounded answers reflect source quality; unclear or outdated articles produce weak or wrong answers.
Clue to watch for AI agent answers are inaccurate.
Answer framework
Use these steps when a scenario involves articles, visibility or knowledge processes.
- Identify the audience that needs the article: reps, authenticated customers, partners, the public or an AI agent.
- Check structure first: is the right record type and layout used, and is the content concise enough for reuse?
- Check visibility next: article channel, data category visibility for that audience, and user permissions or licenses must all allow access.
- Check the lifecycle: draft, approval if needed, publish, new version for edits and archive for retired content.
- Check process health: are reps capturing and improving articles through KCS while they solve cases, and are reuse, attach rates and article feedback measured and acted on?
Practice question
Want more like this? The Service-Con-201 practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Work hands-on. In a Developer org, enable Lightning Knowledge, create two record types, build a data category group for products, and write a few articles. Publish one to each channel, then test visibility as an internal user, a customer site user and a guest. Create a new version of a published article and archive an old one. This exercise covers most configuration questions.
Next, study KCS. The Consortium for Service Innovation publishes the KCS principles, and Trailhead covers Knowledge-Centered Service with Salesforce. Know the Solve and Evolve Loops and why reps, not a central team, should capture knowledge. Then read the Agentforce Service Agent help on using Knowledge to answer questions.
High-priority ideas are the visibility stack (channel, category, permission) and record types versus categories. Underestimated is the link between article quality and AI agent accuracy, which newer questions draw on. Rehearse it by rewriting one vague article into a short, structured answer an AI agent could quote.
FAQ
How much of the exam covers Knowledge Management?
Knowledge Management accounts for 12% per third-party copies of the current guide, roughly seven scored questions as a planning estimate, across two objectives.
Do I need to know classic Knowledge with article types?
Focus on Lightning Knowledge with record types. Classic article types are legacy and unlikely to be the expected answer.
Is KCS a Salesforce feature?
No. KCS is a methodology from the Consortium for Service Innovation. Salesforce Knowledge supports it with features such as article creation from cases and validation status.
Who needs a Knowledge User license?
Users who create or edit articles. Users who only read articles internally, and site users, do not need it.
How does Knowledge relate to Agentforce?
Agentforce Service Agent can ground its answers in Knowledge articles, so the visible, well-written articles largely decide answer quality.
Can one article appear in several channels?
Yes. An article can be published to any combination of Internal App, Customer, Partner and Public Knowledge Base channels.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- HubSpot Inbound Marketing Certification Study guide
- Salesforce Certified Platform Developer I Study guide
- Google Ads Search Certification Study guide
- ServiceNow Certified System Administrator Study guide
- Salesforce Certified Platform Administrator Study guide
- ServiceNow Certified Application Developer Study guide
Test your Domain 4 knowledge
You have covered the article lifecycle, KCS and Lightning Knowledge setup and delivery. Check whether you can trace an article visibility problem to its cause.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the Service-Con-201 AI tutor Get any concept explained your way