CCNA Knowledge Management Questions

AI Search applies semantic and lexical correction, automatically fixing misspellings and mapping synonyms so queries still return relevant Knowledge articles. Legacy Text Search requires exact token matches, so typos or alternate wording fail. This satisfies the scenario's demand for capabilities beyond legacy Text Search.

Each translated article carries its own workflow state, so a translation can be reviewed, approved and published independently of its source. This lets regional teams release localised content on separate schedules while the original remains unchanged, matching the multilingual CSM scenario.

User Criteria in ServiceNow Knowledge Management allows administrators to define conditions based on user attributes, including company and product associations, to control which articles are visible. By setting up user criteria that reference the user's company or product entitlements, the specialist can ensure agents only see articles relevant to their assigned accounts and products. This is the correct mechanism for restricting article visibility dynamically.

Script-based User Criteria lets you evaluate account or entitlement fields dynamically, so only users whose account matches the specified customer accounts pass the check. This satisfies the constraint of restricting a knowledge base to specific customer accounts rather than broad audience segments.

A Notification configured on the kb_feedback table with a Rating less than or equal to 2 condition triggers automatically when feedback is submitted. This directly satisfies the requirement to notify the article author on low ratings.

The History context menu on the kb_knowledge record exposes field-level audit entries showing who changed which field and when. This satisfies the lifecycle audit requirement, since ServiceNow writes these records automatically to the audit table whenever the article is edited.

Routing a negative feedback task to the article's author satisfies the ownership constraint: the author holds the subject-matter expertise and edit rights needed to revise the flagged content. ServiceNow's knowledge feedback engine resolves assignment from the article record's author field, so the person who created the specific article receives the task.

Contextual Search Contexts bind search sources to case fields, and Search Criterias apply conditional filters so agents default to the product-specific knowledge base matching the case's product. This satisfies the requirement to scope searches per product line automatically.

Feedback submitted against an article creates a feedback record and, where configured, a feedback task; both appear in the related lists on the article form. This satisfies the requirement to see the Outdated flag raised by a customer.

Contextual Search Sources are the configuration records that map external repositories, such as SharePoint, into CSM search. Defining one registers the connector and its search profile, so agents see external knowledge results during case creation, satisfying the requirement to search beyond ServiceNow articles.

Hierarchical categories within each Knowledge Base provide a structured taxonomy for classifying articles, satisfying the requirement to categorise knowledge articles. Categories nest under a Knowledge Base, enabling browsing and filtering by topic. This is a native ServiceNow Knowledge Management categorisation method, distinct from article metadata such as keywords or article types.

The 'Can contribute' field on a knowledge base accepts user criteria, which defines who can create and edit articles. By creating user criteria that includes only the knowledge_admin role and applying it, only those users can contribute, while others can still read published articles if read criteria allow. This precisely meets the requirement.

Search Contexts define the conditions, such as Product and Category, that map a case to a specific knowledge base for Contextual Search. Configuring the matching rule there satisfies the requirement to auto-suggest articles from a designated knowledge base.

A scheduled job can query the kb_knowledge table for articles with a last review date older than 90 days and update their state to Retired. This is a flexible and reliable way to automate retirement based on the last review date. It ensures articles are retired exactly 90 days after their last review, meeting the requirement.

The Email UI action on the article preview or contextual search panel opens a compose window pre-populated with the article link, letting the agent send it to the external contact. This satisfies the requirement to email a published article directly from the case.

Separate Knowledge Bases per subsidiary, each governed by distinct User Criteria, enforce record-level visibility so articles from Subsidiary A cannot surface for Subsidiary B users. User Criteria restrict access by user attributes, company, or role, satisfying the stem's hard isolation requirement within one shared ServiceNow instance.

Knowledge Workflow Configuration enforces the approval gate, satisfying the requirement that Tier 2 articles be reviewed by a Knowledge Manager before external publication. It defines states and transitions, so articles cannot reach published status without the designated approver completing their review step.

Contextual Search surfaces relevant published articles directly on the case form, and its 'Attach' button links the selected article to the case record, creating the reference and tracking relationship the agent needs without leaving the case.

Comments and ratings submitted through the Customer Service Portal are written to the kb_feedback table, which stores the article reference, rating value, and user comments. This satisfies the requirement to capture portal-submitted feedback against knowledge articles.

The Contextual Search sidebar, surfaced via the Assistant tab, queries the knowledge base from within the active case form, so the agent never navigates away. This directly satisfies the stem's constraint of searching articles without leaving the case, unlike standalone Knowledge portals or global search interfaces.

Retiring a published article requires the knowledge_manager role, though workflow configuration can extend this to the author. This satisfies the stem's dependency on the configured approval workflow, which governs who may transition an article out of the published state.

Contextual Search Result Configurations let administrators define which fields are matched and assign field weights, so serial numbers in case descriptions surface relevant articles prominently. This satisfies the requirement to boost matches on the specific serial number field.

ServiceNow resolves the article's Language field against the user's active session language, so a French portal session retrieves the French translation. This satisfies the internationalised knowledge base constraint: the platform stores each translation as a separate article version, and language matching selects the appropriate one automatically.

Community question-to-article workflows let managers convert a verified community answer directly into a knowledge base article, preserving the original author and context. This satisfies the stem's requirement for Knowledge Management integration with Communities, closing the loop between peer-generated solutions and governed, reusable knowledge in the CSM environment.

A multi-step approval workflow or Flow Designer flow bound to the knowledge base enforces sequential authorisation: the partner lead approves first, then the internal knowledge manager. Workflow-driven approvals support ordered stages, which a single approval step cannot provide, meeting the stem's two-step requirement.

Community discussion threads and questions can be converted into draft knowledge articles, letting agents capture user-generated content without retyping it. This satisfies the stem's requirement to leverage community content for knowledge management, since the article inherits the thread's content and links back to the originating discussion.

Administrators access prior article iterations through the Versions related list, which records each saved revision as a separate entry. This satisfies the scenario's requirement to inspect historical article states without restoring them, since the related list exposes version metadata and content snapshots directly on the article record.

External repositories return their own field schemas, so mapping those result fields to ServiceNow search result display fields ensures titles, snippets, and links render correctly in the CSM portal, satisfying the requirement that external results appear as usable portal search results.

Create Knowledge from Community is the baseline UI action that copies a discussion thread's content into a draft knowledge article, preserving the link back to the source. It satisfies the requirement to convert a highly rated thread into validated knowledge.

The Create Knowledge UI action on the case form launches article creation with case fields pre-populated, letting the agent capture troubleshooting steps without leaving the record. This directly satisfies the requirement to author an article from the case itself.

When an author checks out a published article, ServiceNow creates a new version in Draft state for editing. The original published version remains published and continues to be visible to users until the new version is published. This ensures that the current published content is not disrupted during editing. This is the standard behavior of knowledge article versioning.

Flagging or submitting feedback marks the article as outdated without requiring author rights, routing it to knowledge managers for review. This satisfies the scenario where an agent identifies stale content but may lack permissions to edit the published article directly.

Flagging an article as 'Not Helpful' on the Customer Service Portal automatically creates a Knowledge Feedback Task, which routes to the assigned knowledge owner for review. This satisfies the default behaviour requirement without custom configuration, since the portal feedback action maps directly to that task type.

Deflection Tracking with Search Analytics feedback records portal searches and article views that end without case creation, attributing each deflection to the knowledge consumed. This supplies the exact count of cases avoided through portal article viewing that the manager needs.

The 'Create Knowledge' UI action on the community question record copies the thread's question and accepted answer into a new knowledge article draft. This satisfies the requirement to convert a resolved community thread into an official knowledge base article.

When an article is checked out, it is locked to that author. Other users cannot check it out until the first author checks it in or an administrator cancels the checkout. This prevents conflicting edits and preserves version integrity. The second author may see that the article is checked out and can request the first author to check it in, but cannot proceed themselves.

The Knowledge Base record's Workflow field binds an article workflow to that base, so every article created within 'Customer Support' inherits the approval cycle before publication. Configuring it there enforces the Knowledge Manager approval the stem requires.

The knowledge article workflow controls state transitions. To enforce approval before publishing, the workflow must include an approval activity in the Review state, assigned to the knowledge manager. When an article enters Review, the approval activity triggers, and the article cannot move to Published until approved. This directly meets the requirement by gating publication on manager approval.

Contextual Search in ServiceNow CSM uses the text entered in the short description field to search knowledge bases and display relevant articles in real time. It is designed to deflect cases by offering solutions as the user types. By enabling Contextual Search on the Customer Service Portal, the knowledge manager can provide immediate article suggestions, enhancing self-service and reducing case creation.

User Criteria referencing the Company field, or a script evaluating entitlement records, restricts article visibility to contacts whose company holds the Premium Support contract. This satisfies the requirement to enforce contract-based access rather than open portal access.

Translation Management links the translated article to the source as a separate record, so publishing the translation leaves the source article's workflow state untouched and still published, satisfying the requirement that the original remains live.

Associating the Search Context with the Workspace Search Config or Table Configuration wires the context into the agent workspace, so suggested articles surface against the record being viewed. Without this binding, the context never activates for agents.

Short Description and Description map directly onto the article's own equivalent fields, so ServiceNow copies them automatically when an agent creates a knowledge article from a case. This satisfies the stem's default-copy constraint without requiring manual entry or additional configuration.

Review is a baseline knowledge workflow state in CSM, sitting between Draft and Published so articles receive approval before publication. It satisfies the stem's requirement for one of the three out-of-the-box lifecycle states, alongside Draft and Published.

Even when published and readable, an article may be absent from search if the search source or profile index has not indexed it. Verifying AI Search or Contextual Search Source configuration and index status addresses this indexing constraint.

Checking out a published article creates a separate draft version; the published version stays live and readable. Readers continue seeing the last published content until the draft is published, satisfying the requirement that the published version remains visible during editing.

Enclosing a phrase in double quotes in ServiceNow search (including Contextual Search) forces an exact phrase match. This excludes articles that contain the individual words separately. The agent will get only articles that have the exact sequence 'password reset failed', significantly narrowing results. This is the standard syntax for exact phrase search in ServiceNow.