KCS Quiz 8 exam topics set 2

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

Focus: Article Structure, Reuse, and Linking¶

#

The core KCS article structure includes: (Select all that apply)

Issue
Environment
Resolution
Cause (optional)
#

The Environment field: (Select all that apply)

Must be true before resolution
Must be true after resolution
Is a key driver of findability
Is optional for internal articles
#

The Cause field: (Select all that apply)

Is optional
Provides context for why issue occurred
Is required for all articles
Must be technical in nature
#

Content capture best practices: (Select all that apply)

Use complete thoughts, not complete sentences
Capture in the moment
Use requestor's context
Use formal writing style only
#

Regarding templates: (Select all that apply)

Start with one simple template
Keep number of templates low
Create many templates for each scenario
Add templates only if clear need exists
#

Searching in KCS: (Select all that apply)

Should happen early and often
Refine as understanding improves
Stop after a few refinements with clear description
Should continue until resolution
#

Searching is different from Google because: (Select all that apply)

KCS search engines have less traffic
KCS search needs more context
Short, vague searches are ineffective
KCS uses better algorithms
#

Purpose of reuse includes: (Select all that apply)

Prevent solving issues already solved
Leverage collective experience
Improve speed and accuracy
Reduce rework and duplicate effort
#

WIP articles enable: (Select all that apply)

Identifying similar issues
Finding issues already being worked
Collaboration
Organizational learning
#

Linking articles to incidents: (Select all that apply)

Is critical for Evolve Loop analysis
Enables link rate metrics
Supports new vs. known analysis
Is optional for internal cases
#

Many-to-many relationships mean: (Select all that apply)

One incident can link to multiple articles
One article can link to multiple incidents
Links must be structured for reporting
Only one-to-one relationships allowed
#

When reusing an article: (Select all that apply)

Link it to the event
Improve it with new details
Reuse always includes improvement
Just copy the content
#

KCS articles should: (Select all that apply)

Be short (~1 page)
Link to other resources
Act as context-sensitive index
Duplicate all reference content
#

"Reuse is Review" means: (Select all that apply)

Articles are validated when used
The best validators are those who use them
Reuse tests article quality
All articles need formal review cycles
#

The 80/20 rule in content reuse: (Select all that apply)

~20% of articles solve ~80% of issues
~80% of articles are rarely reused
This pattern is normal
All articles should be reviewed equally
#

"Flag It or Fix It" rule states: (Select all that apply)

If confident and licensed, fix it immediately
If not confident or lack license, flag it
Collective ownership of content
All changes need approval
#

When merging duplicate articles: (Select all that apply)

Merge into the oldest article
Preserves metadata and history
Delete the newer duplicate
Keep the newest article
#

Articles that are NOT reused: (Select all that apply)

Should not be reviewed
Don't provide value
Follow the 80/20 pattern
Need quarterly review
#

Content Standard defines: (Select all that apply)

How articles should be written
Field definitions
Style guide
Template criteria
#

Content Standard ownership: (Select all that apply)

Owned by knowledge workers
Designed by cross-functional team
Created by people who use and create content
Owned by QA team
#

Content Standard structure: (Select all that apply)

Enough to maintain consistency
Not so much that it slows capture
Balance is critical
Maximum structure for quality
#

Content Standard customization: (Select all that apply)

70-80% common across organizations
20-30% tailored to domain
Avoid over-customization
100% standardized globally
#

Content Standard must define: (Select all that apply)

Article structure
Good vs bad examples
Metadata definitions
Style guide
#

Linking to non-KCS content is allowed when: (Select all that apply)

Content is in a maintained repository
Specific answer is findable by search
Accessible to intended audience
Written in audience's context
#

Article versioning and delivery: (Select all that apply)

Must preserve what was delivered to requestor
Articles continue to evolve after closure
Can capture resolution in incident or snapshot article
Link to specific article version if supported