KCS Quiz 7 exam topics set 1

KCS Exam Topics Quiz - Set 1 (Questions 1-25)¶

Focus: KCS Principles, Core Concepts, and Value Creation¶

#

When should knowledge be captured in KCS? (Select all that apply)

During issue resolution
In the moment
After the case is closed
During weekly documentation reviews
#

Which of the following are NOT KCS practices? (Select all that apply)

Creating articles after resolution
Knowledge engineering
Writing from memory later
Capture in the moment
#

Context is important because: (Select all that apply)

It can only be captured in the moment
Context is as important as content
After-the-fact documentation loses context
Context can be recreated later
#

Technical accuracy is REQUIRED in which fields? (Select all that apply)

Problem statement
Resolution
Environment
Cause
#

Search terms and self-service activity should be: (Select all that apply)

Captured as candidate knowledge
Used to improve articles
Used to create new articles
Discarded after searching
#

WIP (Work in Progress) articles: (Select all that apply)

Should be saved even without a solution
Show issue is already reported
Enable collaboration
Must have a resolution before saving
#

The "Good Enough" rule means: (Select all that apply)

Share what is known now
Articles evolve through reuse
Wait for perfect information
Article doesn't need all scenarios
#

Attributes of knowledge include: (Select all that apply)

Knowledge evolves over time
Knowledge is never perfect or complete
Shared knowledge > individual knowledge
Knowledge remains static once documented
#

A Principle in KCS: (Select all that apply)

Is a fundamental belief
Explains WHY we do things
Applies across multiple practices
Explains HOW to do things
#

Knowledge in KCS is: (Select all that apply)

Information we can act on
A by-product of interaction
Only expert opinions
All documented information
#

The Create Value principle states: (Select all that apply)

Knowledge is the product
Value comes from reuse, improvement, and creation
Tasks are the product
Knowledge workers deliver knowledge, not just tasks
#

KCS and the knowledge base: (Select all that apply)

Knowledge base is embedded in daily work
Proper KCS does NOT increase handle time
Knowledge base is separate from daily work
Reuse, improve, create knowledge as a habit
#

KCS complements but does NOT replace: (Select all that apply)

Technical documentation
Policies
Legal/regulatory content
Problem solving activities
#

Tacit knowledge: (Select all that apply)

Is hard to express without context
Emerges during interaction
Can be documented without demand
Is always explicit
#

Demand-driven means: (Select all that apply)

Capture knowledge based on real issues
Knowledge validated through reuse
What is requested determines what to capture
Anticipate and document future issues
#

What determines value in KCS? (Select all that apply)

Reuse by others
Demand from real requests
Expert approval
Article length
#

The 80/20 rule states: (Select all that apply)

~20% of articles solve ~80% of issues
~80% of articles are rarely reused
This pattern is normal and expected
80% of articles need review
#

Just-in-time (not just-in-case) means: (Select all that apply)

Create content when needed
Avoid anticipating issues
Plan documentation quarterly
Future value cannot be predicted accurately
#

The Solve Loop: (Select all that apply)

Is request-response work
Resolves requests efficiently
Captures resolution experience
Is organizational learning
#

The Evolve Loop: (Select all that apply)

Is organizational learning
Analyzes reuse patterns
Identifies high-impact improvements
Is individual case handling
#

Problem solving in KCS is: (Select all that apply)

Non-deterministic
Contextual
Resources emerge during work
Deterministic like manufacturing
#

Organizations adopt KCS to: (Select all that apply)

Scale capabilities
Handle limited staffing and budgets
Meet increasing demand for knowledge
Eliminate support staff
#

Benefits of KCS include: (Select all that apply)

Operational efficiency
Self-service success
Organizational learning and improvement
Lower operating cost per customer
#

The organization as a network: (Select all that apply)

Connects people to content (known issues)
Connects people to people (new issues)
More agile than siloed structures
Maintains strict hierarchy
#

Technology in KCS: (Select all that apply)

Enables collaboration across people, time, and location
Supports scaling KCS practices
Tools enable KCS but don't create value by themselves
KCS-Verified tools support core KCS behaviors