Courseiva

CCNA Knowledge Management Questions

39 questions · Knowledge Management · All types, answers revealed

1
MCQeasy

Universal Containers wants to ensure that agents can quickly find published FAQ articles related to common shipping inquiries while viewing a Case in Lightning Service Console. Where should the Service Cloud Consultant configure this capability?

A.Create a Global Action for Knowledge and place it on the global publisher layout.
B.Modify the Case page layout in Object Manager to include the Knowledge Related List.
C.Add the Knowledge component to the Case record page layout in Lightning App Builder.
D.Enable Article Recommendations in the Service Cloud Setup Assistant.
AnswerC

Adding the Knowledge component to the Case record page in Lightning App Builder places searchable published FAQ articles directly beside the case in the Service Console, satisfying the requirement that agents find shipping-related articles quickly while viewing a Case.

Why this answer

The Knowledge component in Lightning App Builder is the standard way to surface published Knowledge articles directly on a Case record page in the Lightning Service Console. It provides search, article linking, and suggested articles contextual to the Case, enabling agents to quickly find relevant FAQs without leaving the record.

Exam trap

Service-Con-201 often tests the difference between the Knowledge component (Lightning App Builder) and the Knowledge Related List (page layout) — candidates pick the Related List thinking it provides search, but it only lists linked articles.

How to eliminate wrong answers

Option A is wrong because a Global Action for Knowledge creates a standalone action button, not an embedded search/display component on the Case page — it doesn't provide the in-context article discovery experience. Option B is wrong because the Knowledge Related List on a page layout shows linked articles but does not offer the search and suggestion capabilities of the Knowledge component. Option D is wrong because Article Recommendations is a separate feature for suggesting articles based on case data, but the requirement is about agents searching and finding articles while viewing a Case — the Knowledge component is the direct configuration.

2
MCQhard

Universal Containers wants to implement article recommendations on Cases. When an agent views a Case with the subject 'Printer connection failed', the Lightning Knowledge component should automatically suggest relevant troubleshooting articles. How does Salesforce generate these recommendations?

A.It uses keyword matching from the Case Subject and Description against article titles and body content.
B.It relies entirely on manual tagging performed by agents when closing previous cases.
C.It requires custom Apex triggers that query articles using SOSL and push them to a custom related list.
D.It uses Assignment Rules configured in Setup to match case categories to data categories.
AnswerA

Keyword matching scans the Case Subject and Description, then compares those terms against article titles and body content to surface troubleshooting articles. This satisfies the stem's constraint that suggestions appear automatically when the agent opens the Case, without manual search or a preconfigured article mapping.

Why this answer

Salesforce Knowledge article recommendations on cases are generated by a keyword-matching algorithm that analyzes the case subject and description against article titles and body content. The Lightning Knowledge component surfaces articles with the highest relevance based on this text match. It does not require manual tagging or custom code.

Exam trap

The trap is overcomplicating the mechanism — candidates may assume AI or custom code is needed, but the standard feature uses simple keyword matching.

How to eliminate wrong answers

Option B is wrong because recommendations are not based solely on manual tagging by agents; the system uses automated keyword matching. Option C is wrong because custom Apex triggers with SOSL are not required — the standard component provides recommendations natively. Option D is wrong because assignment rules are used for case assignment, not for article recommendations; data categories can influence article visibility but not the recommendation engine itself.

3
MCQeasy

A Service Cloud consultant is setting up Lightning Knowledge for Universal Containers. Authors will draft troubleshooting articles that must go through a legal review before agents can use them, and the review must be triggered automatically when an author submits the article. Which configuration should the consultant implement?

A.Create a validation rule that prevents articles from being published unless the legal reviewer's name is entered in a field.
B.Build a Flow that sets the article status to Published whenever the author saves the record.
C.Configure a Knowledge article approval process with an assigned approver and enable it for the article type.
D.Assign the articles a Draft validation status and manually notify the legal team by email when each draft is finished.
AnswerC

Salesforce Knowledge supports approval processes on articles, where submitting an article for approval routes it automatically to the designated approver, such as the legal reviewer. This precisely fulfills the automatic-on-submit requirement and records the review decision on the article. It is the built-in mechanism for gated publishing and integrates with article status transitions.

Why this answer

An approval process on the Knowledge article type is the native way to require review before publication: submitting the article routes it to the assigned approver automatically and holds it out of the published state until approved. Manual notifications, validation rules, and auto-publishing each fail to enforce an automatic, gated review step.

Exam trap

The trap here is substituting a validation rule or manual notification for a true approval process, even though only an approval process automatically routes submitted articles to a designated reviewer.

4
MCQmedium

Universal Containers wants to retire an outdated article type while retaining access to historical articles that were already published under that type. What is the recommended best practice for the administrator?

A.Delete the Knowledge Record Type immediately to purge associated database tables and reclaim storage space.
B.Archive all active articles of that type, remove the Record Type from user profiles, and keep the object structure intact for historical reporting.
C.Convert the Knowledge object into a custom object using the Custom Object Conversion Wizard.
D.Change the API name of the Record Type to 'Deprecated' so agents know not to select it.
AnswerB

Archiving preserves published articles for historical reporting while removing them from active channels. Removing the Record Type from profiles prevents new articles of that type, and keeping the object structure intact retains historical data access.

Why this answer

To retire an article type or layout while keeping historical records accessible, administrators should unassign record types or archive existing articles, keeping in mind that Salesforce Knowledge uses record types rather than legacy 'article types' in Lightning.

5
MCQmedium

Universal Containers wants to categorize articles by product line and geography. Agents should be able to select multiple categories within the geography dimension for a single article. How should the consultant set up Data Categories?

A.Use custom hierarchical custom metadata types for geography and standard picklists for product lines.
B.Create two Data Category Groups: Product Line and Geography, and configure Geography to allow multiple category selection.
C.Create separate object record types for each geography and a multi-select picklist for product lines.
D.Create a single Data Category Group with dependent picklist fields mapping product to geography.
AnswerB

Two separate Data Category Groups keep product line and geography independent, and enabling multiple category selection on the Geography group lets agents tag one article with several geographies. This matches the requirement for multi-select within the geography dimension only.

Why this answer

Data Categories in Salesforce Knowledge are organized into Data Category Groups, each representing a dimension such as Product Line or Geography. To allow an agent to select multiple categories within a single dimension for one article, the consultant creates a Data Category Group for Geography and enables the 'Allow multiple categories to be selected' setting on that group. This is the native, declarative mechanism for multi-category tagging within a dimension.

Exam trap

Service-Con-201 often tests the misconception that picklists or record types can substitute for Data Categories in Knowledge, when only Data Category Groups support multi-select categorization per dimension.

How to eliminate wrong answers

Option A is wrong because custom metadata types and picklists are not the mechanism for Knowledge article categorization; Data Categories are the purpose-built feature and picklists cannot drive article visibility filters. Option C is wrong because record types and multi-select picklists do not integrate with Knowledge's category-based visibility model and cannot be used for article filtering. Option D is wrong because a single Data Category Group with dependent picklists conflates two separate dimensions into one group and does not support independent multi-select per dimension.

6
MCQeasy

An agent finds a published Knowledge article that contains a spelling error. The agent does not have permission to publish articles directly, but needs the error corrected. What action should the agent take?

A.Archive the article immediately and create a brand new article from scratch.
B.Click 'Edit' on the published article, which automatically creates a draft copy for editing and submission.
C.Email the system administrator with the corrected text so they can manually update the database.
D.Edit the published article directly, as all users have inline editing rights on published content.
AnswerB

Clicking Edit on a published article creates a draft copy rather than altering the live version, letting an agent without publish rights propose the spelling correction for review. The original published article remains unchanged until the draft is approved.

Why this answer

When an agent without publishing permissions needs to update an article, they create a 'Draft' version of the published article, make the edits, and submit it for review/approval.

7
Multi-Selecteasy

Universal Containers wants to ensure that support agents can effectively use Salesforce Knowledge within the Lightning Service Console. Which TWO features should the consultant configure or verify? (Choose two.)

Select 2 answers
A.Configure Salesforce Files sync for all article attachments.
B.Set up Omni-Channel supervisor tabs for Knowledge authoring queues.
C.Assign 'Read' and 'Create' object permissions for Knowledge on agent profiles.
D.Place the Lightning Knowledge component on the Case record page layout in Lightning App Builder.
E.Enable Salesforce CRM Content libraries for each article type.
AnswersC, D

Agents need object-level permissions on Knowledge to search, read and author articles from the console. Without Read and Create granted on their profiles, the Knowledge component and its actions remain inaccessible regardless of page configuration.

Why this answer

Option C is correct because agents need object-level permissions on the Knowledge object—specifically Read to view articles and Create (plus Edit as needed) to author or contribute articles—without which the Knowledge features in the console will be inaccessible or read-only. Option D is correct because the Lightning Knowledge component must be added to the Case record page via Lightning App Builder so agents can search, view, and attach articles directly within the Lightning Service Console while working a case. Option A is incorrect because Salesforce Files sync is a file-sharing feature unrelated to enabling Knowledge usage in the console.

Option B is incorrect because Omni-Channel supervisor tabs are for monitoring agent workload and routing, not for Knowledge authoring queues. Option E is incorrect because Salesforce CRM Content libraries are a separate content management capability and are not required to use Lightning Knowledge article types.

Exam trap

Service-Con-201 often tests the misconception that enabling Knowledge or adding the component alone is sufficient; candidates must remember that object permissions and page layout placement are both required.

8
MCQmedium

Universal Containers wants to restrict access to internal HR policy articles so that standard customer support agents cannot see them, while ensuring HR personnel can. How should the consultant achieve this?

A.Set the organization-wide default for Knowledge to Private and create a sharing rule for HR.
B.Use validation rules to prevent support profiles from querying HR record types.
C.Create a separate Knowledge object and assign it to the HR profile.
D.Assign data category visibility for the HR category exclusively to the HR profile and restrict it from support profiles.
AnswerD

Data category visibility operates on the category hierarchy independently of record ownership, so restricting the HR category to the HR profile blocks support agents from seeing those articles. This satisfies the requirement that only HR personnel access internal policy content.

Why this answer

Data categories combined with role-based or profile-based data category visibility allow organizations to control which user groups can view specific segments of the Knowledge base.

9
MCQeasy

An agent has finished updating an existing, published Knowledge article in Lightning Experience. What happens to the current published version while the agent is editing it?

A.The published version remains available to users while a separate draft version is edited.
B.The agent cannot edit a published article directly and must archive it first.
C.A copy of the article is created as a brand-new record with a different URL name.
D.The article is automatically unpublished and set to draft for all users until re-published.
AnswerA

Salesforce Knowledge versions articles separately: editing a published article creates a draft version, leaving the published version live and searchable for users until the draft is published. This satisfies the constraint that users retain uninterrupted access during the agent's edits.

Why this answer

In Salesforce Lightning Knowledge, when an agent edits a published article, the system creates a draft version while the published version remains live and available to users. This allows continuous editing without disrupting access to the current published content until the draft is published.

Exam trap

Service-Con-201 often tests whether candidates believe editing a published article takes it offline or creates a new record, when in fact Salesforce preserves the published version and creates a separate draft version.

How to eliminate wrong answers

Option B is wrong because agents can edit published articles directly; archiving is not a prerequisite. Option C is wrong because editing a published article does not create a brand-new record with a different URL name; it creates a version under the same article record. Option D is wrong because the article is not automatically unpublished; the published version stays live while the draft is edited.

10
MCQmedium

Universal Containers wants agents to provide feedback on Knowledge articles directly from the article view page in the console, indicating whether the article was helpful or not. How should the consultant enable this?

A.Enable Chatter Questions on the Knowledge article feed.
B.Create a custom object linked to Knowledge and place a related list on the page layout.
C.Enable Article Feedback in Knowledge Settings and add the feedback component to the article page layout.
D.Configure Case milestones to prompt agents for article ratings upon case closure.
AnswerC

Article Feedback must be switched on in Knowledge Settings, then the standard feedback component added to the article page layout so it renders in the console. This satisfies the requirement for agents to rate helpfulness directly from the article view.

Why this answer

Article Feedback is a native Knowledge setting that, once enabled, exposes a feedback component which can be placed on the article page layout so agents can rate whether an article was helpful. This directly satisfies the requirement of capturing agent feedback from the article view page in the console. No custom object or Chatter configuration is needed.

Exam trap

Service-Con-201 often tests whether candidates know that Article Feedback is a native Knowledge setting rather than something requiring custom objects or Chatter, so candidates who default to 'build a custom object' pick the wrong answer.

How to eliminate wrong answers

Option A is wrong because Chatter Questions enables Q&A-style discussions on feeds and does not provide a structured helpful/not-helpful rating mechanism on Knowledge articles. Option B is wrong because building a custom object and related list is unnecessary overhead when Salesforce provides a native Article Feedback feature. Option D is wrong because Case Milestones track time-based service-level targets and have no capability to prompt for article ratings at case closure.

11
MCQeasy

An administrator needs to create a new category group for Salesforce Knowledge. Where in Setup should the administrator navigate?

A.Object Manager > Knowledge > Categories
B.Data Category Setup
C.Service Console Settings
D.Knowledge Settings
AnswerB

Data Category Setup is the Setup node where category groups, categories and their hierarchy are created and assigned to profiles or permission sets, so it is the required location for building a new Knowledge category group.

Why this answer

Data Category Setup is the dedicated Setup node where admins create and manage data category groups, hierarchies, and category assignments for Salesforce Knowledge. Navigating to Setup > Data Category Setup provides the interface to define groups and categories. This is separate from Knowledge Settings, which controls general Knowledge behavior.

Exam trap

The trap is confusing Knowledge Settings (feature toggles) with Data Category Setup (category hierarchy management); candidates often pick Knowledge Settings because it sounds like the right place for Knowledge configuration.

How to eliminate wrong answers

Option A is wrong because Object Manager > Knowledge does not contain a 'Categories' sub-node for creating data category groups; Object Manager manages fields, layouts, and record types, not data category hierarchies. Option C is wrong because Service Console Settings configure console apps, utility bars, and navigation, not Knowledge data categories. Option D is wrong because Knowledge Settings controls features like article validation, publishing workflows, and Lightning Knowledge enablement, but not the creation of category groups.

12
MCQeasy

Universal Containers wants to ensure that when an agent closes a case, they are prompted to create a new Knowledge article if no existing article matches the case's resolution. The consultant needs to configure a solution that minimizes manual effort for agents. What should the consultant recommend?

A.Use the 'Knowledge' component on the Case page layout and enable the 'Suggest Articles' feature to prompt agents to create an article when closing.
B.Create a workflow rule on Case that triggers a Knowledge article creation when the case status changes to Closed.
C.Enable 'Knowledge Search' on the Case and set up a validation rule that prevents case closure unless a Knowledge article is linked.
D.Configure a Case Close quick action that includes a screen flow to search for existing articles and, if none match, launch the article creation page pre-populated with case details.
AnswerD

This approach uses a screen flow within a quick action to guide agents through searching for existing articles and, if none are found, to create a new article with case details pre-filled. It minimizes manual effort by automating the search and pre-population, and directly addresses the requirement to prompt for article creation upon case closure.

Why this answer

The correct solution is a Case Close quick action with a screen flow that searches for existing articles and, if none are found, allows the agent to create a new article pre-populated with case details. This streamlines the process, reduces manual data entry, and ensures knowledge capture at case closure.

Exam trap

The trap here is assuming that the 'Suggest Articles' feature or a validation rule can prompt for new article creation, when in fact they either only suggest existing articles or block closure without providing a creation path.

13
Multi-Selecthard

An administrator is designing a complex article publishing lifecycle. Which THREE actions can be automated as part of a Knowledge article approval process or workflow? Choose 3 answers.

Select 3 answers
A.Automatically convert the article's record type based on approval outcome.
B.Create follow-up tasks for authors to review expired articles.
C.Send email notifications to designated approvers when an article is submitted.
D.Trigger an automatic translation export to external localization vendors directly via standard approval actions.
E.Update specific fields on the article record (e.g., setting a Review Status field) upon approval or rejection.
AnswersB, C, E

Approval processes and workflow rules can invoke tasks, so a scheduled or approval-triggered action can generate follow-up tasks prompting authors to review expired articles. This satisfies the lifecycle requirement for automated author reminders within the publishing process.

Why this answer

Option B is correct because Knowledge workflows and approval processes can create follow-up tasks (via workflow rules, Flow, or Process Builder) that assign authors to review articles approaching or past their review/expiration date, supporting the article lifecycle. Option C is correct because approval processes natively support email alerts/notifications to designated approvers when an article is submitted for approval, keeping the approval chain informed. Option E is correct because approval and rejection actions can include field updates, such as setting a Review Status or Approval Status field on the article record, to reflect the outcome.

Option A is not correct because record type changes are not a standard automated approval action in Knowledge workflows and are typically handled by separate automation, not the approval process itself. Option D is not correct because triggering translation exports to external localization vendors is not a standard approval action; localization/translation is handled through separate translation workflows or integrations, not built-in approval actions.

Exam trap

Service-Con-201 often tests whether candidates assume that record type conversion or external system integration can be automated directly via standard approval actions, when these require custom development.

14
MCQmedium

Universal Containers wants to ensure that support agents can attach Knowledge articles to Cases via email responses to customers. How can this requirement be met?

A.Use the 'Insert Article' action within the Email action toolbar in the Case feed.
B.Configure Workflow email alerts to automatically attach matching knowledge articles.
C.Copy and paste the article HTML source code from the article management tab.
D.Write a custom Visualforce email template that queries Knowledge objects via SOQL.
AnswerA

The 'Insert Article' action in the Case feed's Email toolbar lets support agents embed Knowledge article content directly into outbound email responses, satisfying the requirement to attach articles via email. This native action preserves article formatting and tracks article usage against the Case, unlike manually copying text or attaching files.

Why this answer

The 'Insert Article' action in the Email action toolbar within the Case feed allows agents to search for and insert Knowledge articles directly into email responses. This is the native, supported way to attach articles to case emails. It preserves article formatting and tracking.

Exam trap

Service-Con-201 often tests the misconception that Workflow email alerts can attach Knowledge articles automatically, when in fact only the manual 'Insert Article' action in the email composer provides that capability.

How to eliminate wrong answers

Option B is wrong because Workflow email alerts cannot dynamically attach Knowledge articles based on matching criteria; they send predefined templates. Option C is wrong because copying and pasting HTML source code is error-prone, breaks formatting, and does not provide article tracking or version control. Option D is wrong because a custom Visualforce email template querying Knowledge via SOQL is over-engineered, requires development, and does not provide the interactive agent experience of inserting articles on the fly.

15
MCQmedium

Universal Containers uses Lightning Knowledge. A service manager reports that a published article about a discontinued router is still appearing in search results and being recommended on new cases, even though the product was retired six months ago. The manager wants the article to remain visible to internal users for historical reference but must stop it from appearing to customers and in case recommendations. Which action should the consultant recommend?

A.Remove the article from all data categories so it no longer matches customer-facing filters.
B.Archive the article so it is removed from search and recommendations but remains accessible to internal users.
C.Change the article's validation status from Published to Draft so it is removed from all channels.
D.Delete the article and rely on Salesforce's recycle bin for thirty days of historical access.
AnswerB

Archiving removes the article from active search results, article lists, and case recommendations while preserving it for internal reference through direct access and reporting. This matches the manager's requirement exactly: internal users can still view it, but customers and recommendation engines no longer surface it. Archiving is the standard lifecycle action for retiring obsolete content without deleting it.

Why this answer

Archiving is the Knowledge lifecycle action designed for retiring content: it removes an article from search results, article lists, and case recommendations while keeping it available for internal reference and reporting. Drafting removes visibility for everyone, deleting destroys the record, and stripping categories breaks organization without guaranteeing removal from recommendations.

Exam trap

The trap here is assuming that unpublishing or deleting is the only way to stop an article from surfacing, when archiving is the lifecycle state built specifically for retiring content while retaining internal access.

16
MCQeasy

A support supervisor needs to know how many times a specific Knowledge article has been viewed by customers on the public Experience Cloud site. Where can this information be found?

A.Google Analytics integration setup logs.
B.Case Comment History related list.
C.Knowledge Article View Statistics fields and standard reports.
D.Chatter feed analytics on the article record.
AnswerC

Knowledge Article View Statistics fields track views on public Experience Cloud sites, satisfying the supervisor's need for customer view counts. Standard reports built on these fields surface the totals directly, without custom development. This is the only option that measures external customer views rather than internal article usage.

Why this answer

Knowledge Article View Statistics are stored in the KnowledgeArticleViewStat object and surfaced through standard fields and reports in Salesforce Knowledge. These track how many times an article was viewed, including views from the public Experience Cloud site when the article is exposed there. This is the OOTB mechanism for measuring customer-facing article views.

Exam trap

Service-Con-201 often tests whether candidates know that article view metrics live in KnowledgeArticleViewStat and standard reports, not in Chatter, Case Comments, or external analytics tools — the trap is picking a plausible-sounding but unrelated tracking mechanism.

How to eliminate wrong answers

Option A is wrong because Google Analytics integration logs track web traffic at the site level, not per-article Knowledge view counts, and setup logs are not a reporting source for article metrics. Option B is wrong because Case Comment History tracks comments added to cases, which has nothing to do with article view counts. Option D is wrong because Chatter feed analytics track engagement on Chatter posts, not Knowledge article views on an Experience Cloud site.

17
Multi-Selectmedium

Universal Containers is setting up Data Categories and needs to control visibility across different business units. Which TWO statements are true regarding Data Category visibility? (Choose two.)

Select 2 answers
A.Data category visibility automatically mirrors the role hierarchy without manual setup.
B.External Experience Cloud users cannot have data category visibility restrictions applied.
C.Data categories dictate the object-level sharing model for standard Accounts and Contacts.
D.Data category visibility can be assigned via Profiles and Permission Sets.
E.Visibility can be set to 'All', 'None', or customized to specific branches of a category group.
AnswersD, E

Data category visibility is granted through profiles and permission sets, letting administrators scope category group access per business unit. This satisfies the stem's requirement to control visibility across different business units without relying on sharing rules or roles.

Why this answer

Option D is correct because data category visibility is granted through the user's profile or permission sets, where you select the category group and choose the categories (or branches) the user can see; this is the standard mechanism for controlling category access. Option E is correct because visibility settings support the predefined values 'All' (access to every category in the group), 'None' (no access), and a customized selection that grants access to specific branches or individual categories within the category group. Options A, B, and C are incorrect: data category visibility does not automatically mirror the role hierarchy (it must be explicitly assigned), external Experience Cloud users can indeed have data category visibility restrictions applied, and data categories control record visibility for knowledge articles and similar content—not the object-level sharing model for standard Accounts and Contacts, which is governed by org-wide defaults, sharing rules, and the role hierarchy.

Exam trap

Service-Con-201 often tests the misconception that data category visibility follows the role hierarchy automatically or that it controls object sharing, when it is a separate, explicitly assigned visibility layer.

18
MCQmedium

Universal Containers requires that when a Knowledge article is created, its URL name is automatically populated based on the title. How does Salesforce handle the URL Name field by default?

A.It is generated sequentially using system record IDs.
B.It is auto-populated from the article title, with the ability to be manually edited by authors.
C.It requires a custom Apex trigger to generate SEO-friendly URL strings.
D.It must be manually entered by the author every time to prevent duplicate URL errors.
AnswerB

Salesforce auto-generates the URL Name from the article title when the article is created, ensuring a readable, unique identifier without manual entry. Authors retain the ability to edit it afterwards, satisfying the requirement that population happens automatically while preserving flexibility.

Why this answer

By default, Salesforce auto-populates the URL Name field from the article title, converting it into a URL-friendly string, and authors can manually edit it afterward. This default behavior applies to Knowledge articles in Lightning Knowledge. It ensures each article has a readable, unique URL without requiring manual entry.

Exam trap

The trap is assuming URL Name requires manual entry or custom code; Service-Con-201 tests that it's auto-populated from the title by default and remains editable.

How to eliminate wrong answers

Option A is wrong because URL Name is not generated from system record IDs; it's derived from the title. Option C is wrong because no custom Apex trigger is needed—the auto-population is native. Option D is wrong because manual entry is not required; the field is auto-filled, though authors can edit it to resolve duplicates.

19
MCQhard

Universal Containers has enabled Lightning Knowledge and uses article suggestions on cases. A support director complains that when agents resolve a case, the resolution text they type is never captured as reusable knowledge, so the same issues are re-solved repeatedly. The director wants the fastest path to turn existing case resolutions into draft articles without requiring agents to author from scratch. Which feature should the consultant recommend?

A.Enable Einstein Article Recommendations so the system proposes articles when cases are created.
B.Build a report on closed cases and schedule it to email resolution text to the knowledge team weekly.
C.Enable the Knowledge Search component on the Case page layout so agents can look up existing articles faster.
D.Configure the Case Close action to create a draft article from the case's resolution field automatically.
AnswerD

Salesforce provides a case-to-article flow where a draft Knowledge article can be generated from a closed case's resolution, pre-populating the article body with the resolution text for review and publication. This is the fastest path because it repurposes work agents already did rather than requiring new authoring. The resulting draft enters the normal review workflow, so quality control is preserved while capture becomes effortless.

Why this answer

Creating a draft article from the case resolution converts work agents already performed into reviewable knowledge, which is the quickest capture path. Searching, reporting, and recommendations all assume the content already exists, so they cannot fix a gap where resolutions are never turned into articles in the first place.

Exam trap

The trap here is confusing tools that surface existing articles, such as search components and recommendations, with mechanisms that capture new knowledge from case resolutions.

20
MCQeasy

A support agent creates a new FAQ article in Salesforce Knowledge. What is the default status of this newly created article when saved for the first time?

A.Draft
B.Published
C.Pending Approval
D.Archived
AnswerA

Newly created Knowledge articles save as Draft by default, remaining unpublished and invisible to all users until submitted for approval or published. This matches the stem's first-save scenario without any additional configuration by the support agent.

Why this answer

When a new article is created in Salesforce Knowledge and saved for the first time, its default status is Draft. This allows authors to continue editing and refining content before submitting it for approval or publishing. Draft articles are not visible to end users in the customer-facing knowledge base or in the internal Knowledge sidebar unless the user has authoring permissions.

Exam trap

Service-Con-201 often tests the assumption that saving an article automatically publishes it or sends it for approval, but the default is always Draft until an explicit publish or submit action is taken.

How to eliminate wrong answers

Option B is wrong because Published status requires an explicit action (publish or submit for approval then publish), not the default on first save. Option C is wrong because Pending Approval only occurs after an author submits the article into an approval process, which is not automatic. Option D is wrong because Archived is a terminal state applied manually to retire outdated articles, not a default creation state.

21
MCQhard

Universal Containers uses Salesforce Knowledge with multiple languages enabled. An author makes a major update to the master English article. How does this affect the translated versions in Spanish and French?

A.The translated articles are automatically unpublished until the master article is approved.
B.The translations are automatically deleted and must be recreated from scratch.
C.The translated versions are flagged as 'Out of Date', and translation tasks are generated if configured.
D.The translated versions are automatically overwritten with machine-translated English text.
AnswerC

Major updates to the master article change its content, so Salesforce flags each translated version as 'Out of Date' rather than overwriting translations. Where translation workflows are configured, the system generates translation tasks, prompting translators to revise the Spanish and French versions.

Why this answer

When the master article is updated, Salesforce Knowledge marks all associated translations as 'Out of Date' so translators know the source has changed. If translation workflows or translation tasks are configured, the system generates tasks for the affected languages. The translations themselves remain published and usable until a translator updates them, but they carry the Out of Date flag.

Exam trap

The trap here is assuming that updating the master article automatically updates or unpublishes translations; in reality, Salesforce only flags them as Out of Date and relies on configured translation processes to act.

How to eliminate wrong answers

Option A is wrong because translations are not automatically unpublished when the master changes; they remain live with an Out of Date indicator. Option B is wrong because translations are never deleted automatically — they persist until manually removed or replaced. Option D is wrong because Salesforce does not perform machine translation; translations are authored by humans or external translation services, and the master update does not overwrite them.

22
Multi-Selecthard

Universal Containers is preparing to import 20,000 legacy articles into Salesforce Knowledge using the Knowledge Import Tool. Which THREE requirements must be met for a successful import? (Choose three.)

Select 3 answers
A.Valid article type names and matching field API names in the import files.
B.An active Enterprise integration license for each imported article.
C.A pre-approved Salesforce support ticket authorizing the batch size.
D.A properties file that defines the mapping and characteristics of the import.
E.A structured ZIP file containing CSV or XML files for article data.
AnswersA, D, E

The import files must reference article type names that already exist in the target org and field API names that match exactly, otherwise the Knowledge Import Tool rejects rows during validation. Mismatched names cause the entire import to fail rather than partially load.

Why this answer

Option A is correct because the Knowledge Import Tool requires that the article type names and field API names in the import files exactly match the existing article types and fields configured in the target Salesforce org, otherwise the import will fail validation. Option D is correct because the tool uses a properties file (typically named article.properties) to define the import mapping, article type, and other characteristics such as the file format and language. Option E is correct because the import must be packaged as a structured ZIP file containing CSV or XML files with the article data, along with the required properties file.

Option B is incorrect because importing articles does not require an Enterprise integration license per article; that license type is unrelated to Knowledge import. Option C is incorrect because no pre-approved Salesforce support ticket is required to authorize batch sizes for the Knowledge Import Tool.

Exam trap

Service-Con-201 often tests whether candidates confuse the Knowledge Import Tool's actual prerequisites (properties file, ZIP with CSV/XML, matching API names) with generic migration myths like 'support ticket approval' or 'per-article licenses', which do not exist.

23
Multi-Selecteasy

Universal Containers wants support agents to easily find relevant articles while chatting with customers in the Service Console. Which TWO features enhance agent efficiency with Knowledge during live chats? (Choose two.)

Select 2 answers
A.Article insert action directly within the chat panel or email composer.
B.Mandatory email attachments of all knowledge base files on every outgoing message.
C.Automatic conversion of chat transcripts into published knowledge articles via workflow.
D.Automatic voice-to-text translation of knowledge articles during phone calls.
E.Lightning Knowledge component placed on the Console workspace tab and utility bar.
AnswersA, E

Article insert action lets agents embed Knowledge articles straight into the chat panel or email composer without leaving the conversation, satisfying the requirement to find and share relevant articles during live chats. This removes context switching between the Service Console and Knowledge, directly enhancing agent efficiency while chatting with customers.

Why this answer

Option A is correct because the Article Insert action lets agents search Knowledge and drop article content or links directly into the chat panel or email composer, so they can share relevant answers with the customer without leaving the conversation. Option E is correct because placing the Lightning Knowledge component on the Console workspace tab and in the utility bar gives agents persistent, one-click access to search and view articles while handling live chats. Together these features reduce context switching and speed up response time during chats.

Option B is wrong because forcing every knowledge file as an email attachment is not a Knowledge efficiency feature and would be impractical and spammy. Option C is wrong because automatically converting chat transcripts into published articles is not a standard live-chat Knowledge feature and would not help agents find articles in the moment. Option D is wrong because voice-to-text translation of articles applies to phone calls, not live chat, and is not a Knowledge search aid.

Exam trap

Service-Con-201 often tests the misconception that chat transcripts auto-convert to articles or that attachments are mandatory, when the real efficiency features are the insert action and the Knowledge component placement.

24
MCQeasy

A support agent wants to search for Knowledge articles using specific terms and filter them by data category directly within the Lightning Service Console. Which tool provides this interface?

A.The Case Feed Publisher action menu.
B.The Knowledge Management app in App Launcher.
C.The Lightning Knowledge component on the Case or Home page.
D.Global Search results page with Knowledge object tab.
AnswerC

The Lightning Knowledge component embeds search and filtering directly in the Service Console, satisfying the requirement to query articles by term and narrow results by data category without leaving the case record. Its native category filter and search bar operate on the Knowledge object, unlike standalone search apps or external portals.

Why this answer

The Lightning Knowledge component can be placed on Case or Home pages and provides a search interface with term search and data category filters directly in the console. It is the standard tool for agents to find and attach articles without leaving the case. This component is designed for the Lightning Service Console experience.

Exam trap

Service-Con-201 often tests the confusion between the Knowledge Management app (for authors) and the Lightning Knowledge component (for agents), leading candidates to choose the admin app for agent search.

How to eliminate wrong answers

Option A is wrong because the Case Feed Publisher action menu is for composing emails, logging calls, and adding articles to a case, not for searching and filtering Knowledge by data category. Option B is wrong because the Knowledge Management app in App Launcher is an administrative app for authoring and managing articles, not a search interface for agents in the console. Option D is wrong because Global Search results do not provide data category filtering specific to Knowledge; that filtering is available in the Knowledge component or Knowledge tab.

25
MCQhard

Universal Containers has a large Lightning Knowledge base with articles assigned to a multi-level data category hierarchy covering region and product. Agents report that when they search from the Knowledge tab, results include articles for regions they do not support, forcing them to scan irrelevant content. The consultant confirms agents' profiles are already restricted to their own region categories. What should the consultant verify to explain why restricted articles still appear in search results?

A.Whether the agents' profiles lack the Knowledge User license, which controls search scope.
B.Whether articles are missing category assignments in the region category group, leaving them visible to all users.
C.Whether the search index has not yet been rebuilt after the last data category hierarchy change.
D.Whether the agents have the Manage Knowledge permission, which bypasses category visibility.
AnswerB

Articles that have no category assigned in a group are not filtered by that group's visibility rules, so they can surface for every user regardless of profile restrictions. If the region category group is not populated on these articles, agents will see out-of-region content even with proper profile settings. Verifying category assignment on the articles is the correct diagnostic step.

Why this answer

Category group visibility only filters articles that actually carry a category in that group. Articles with no region category assigned are treated as unrestricted and appear for all users, which explains why agents see out-of-region content despite correct profile restrictions. Verifying category assignments on the articles resolves the discrepancy.

Exam trap

The trap here is assuming profile category visibility alone guarantees filtering, when articles with no category assigned in a group remain visible to everyone regardless of those settings.

26
MCQmedium

Universal Containers wants to ensure that articles flagged with a 'Needs Review' validation status cannot be attached to cases by support agents. How should the consultant configure this?

A.Configure Knowledge Settings to exclude articles with specific validation statuses from search and case attachment.
B.Use data category visibility to hide articles undergoing review.
C.Write a validation rule on the CaseArticle object preventing attachment.
D.Remove read access to the Knowledge object for agents until validation is complete.
AnswerA

Knowledge Settings let administrators select validation statuses whose articles are excluded from search results and case attachment, directly preventing agents from attaching 'Needs Review' articles. This is enforced at the article lifecycle level, not through page layout or sharing rules.

Why this answer

Knowledge Settings includes an option to exclude articles with specific validation statuses from search and case attachment. By configuring this, articles flagged 'Needs Review' can be hidden from agents when they search or attach articles to cases. This is the declarative, native way to enforce the requirement without code.

Exam trap

The trap is thinking data category visibility or object permissions can filter by validation status; Service-Con-201 tests that Knowledge Settings has a specific validation status exclusion for search and case attachment.

How to eliminate wrong answers

Option B is wrong because data category visibility controls which categories of articles a user can see, not validation status; it doesn't target 'Needs Review' articles specifically. Option C is wrong because a validation rule on CaseArticle cannot prevent attachment based on the article's validation status—validation rules can't easily reference the related article's status in that context, and it's not the intended mechanism. Option D is wrong because removing read access to Knowledge entirely would block agents from all articles, not just those under review, and is overly broad.

27
Multi-Selecthard

Universal Containers operates globally and uses multi-language features in Salesforce Knowledge. Which THREE considerations must a consultant keep in mind when designing a multi-language knowledge base? (Choose three.)

Select 3 answers
A.Articles are created in a master language, and translations are linked to the master record.
B.Salesforce automatically machine-translates all articles into enabled languages every night.
C.Translation Management allows assigning translation tasks to specific users, queues, or agencies.
D.Every translated article requires a separate record type and independent workflow.
E.When a master article is updated, linked translations are flagged as 'Out of Date'.
AnswersA, C, E

Salesforce Knowledge uses a master-language model: each article originates in one master language, and every translation exists as a linked version referencing that master record. This architecture governs how languages, publishing, and updates are managed across the knowledge base.

Why this answer

Option A is correct because Salesforce Knowledge uses a master-language model: the original article is authored in the master language, and each translation exists as a linked version that inherits the master's structure and shares its ArticleNumber. Option C is correct because Translation Management lets you create translation tasks and assign them to specific users, queues, or external translation agencies, and it tracks the status of those tasks. Option E is correct because when the master article is edited, Salesforce marks the linked translations as 'Out of Date' so translators know they must be updated to match the master.

Option B is wrong because Salesforce does not perform automatic nightly machine translation; translations must be created manually or via a translation service/integration. Option D is wrong because translated articles do not require separate record types or independent workflows; they are versions of the same article and share its record type and lifecycle.

Exam trap

Service-Con-201 often tests the master-translation linkage and the 'Out of Date' flag behaviour, so candidates who assume automatic machine translation or per-translation record types pick wrong answers.

28
MCQeasy

A consultant is modifying the page layout for a Knowledge article type in Lightning Experience. Which tool is used to arrange fields and sections on the layout?

A.Knowledge Setup Wizard layout designer.
B.Experience Builder page editor.
C.Lightning App Builder canvas.
D.Object Manager Page Layouts for the Knowledge object.
AnswerD

Knowledge article types expose page layouts through Object Manager, where fields and sections are arranged for Lightning Experience. This is the native tool for the Knowledge object, satisfying the stem's requirement to modify layout structure rather than record types or Lightning pages.

Why this answer

In Lightning Experience, page layouts for any object, including Knowledge, are modified through the Object Manager's Page Layouts section. This tool allows administrators to arrange fields, sections, buttons, and related lists on the layout. The Knowledge object's page layouts are accessed via Object Manager > Knowledge > Page Layouts, where you can edit the layout for each article type.

Exam trap

The trap here is confusing Lightning App Builder with page layout editing; candidates might think Lightning App Builder is used for all layout changes, but standard page layouts are still edited in Object Manager.

How to eliminate wrong answers

Option A is wrong because there is no 'Knowledge Setup Wizard layout designer'; Knowledge setup involves enabling Lightning Knowledge and assigning record types, but layout editing is done in Object Manager. Option B is wrong because Experience Builder is for building Experience Cloud sites, not for editing internal page layouts. Option C is wrong because Lightning App Builder is used to create custom Lightning pages (apps, home pages, record pages), not to modify standard page layouts.

29
MCQhard

Universal Containers uses Salesforce Knowledge and has implemented multi-language support. They noticed that some articles are being searched for in Spanish, but no results are returned even though English articles exist. What is the likely cause?

A.The articles must be assigned a separate record type for each language.
B.Language fallback settings are not configured to show master language articles when translations are missing.
C.The Knowledge search index has not been rebuilt for Spanish characters.
D.Data category visibility is blocking Spanish users from seeing English category nodes.
AnswerB

Language fallback settings determine whether the master language article is returned when no translation exists. Without fallback enabled, Spanish searches match only Spanish articles, so English-only articles return nothing. Enabling fallback satisfies the requirement to surface master-language content for missing translations.

Why this answer

Salesforce Knowledge supports language fallback, which allows users searching in one language to see articles in another language (typically the master language) when translations are missing. If fallback is not configured, a Spanish-speaking user searching for a term will only see Spanish articles, and if none exist, no results are returned even though English articles cover the topic. Configuring language fallback settings ensures that master-language articles appear when translations are unavailable.

Exam trap

Service-Con-201 often tests whether candidates confuse language fallback with data category visibility or search indexing, leading them to select answers that address access or indexing rather than the language matching configuration.

How to eliminate wrong answers

Option A is wrong because Salesforce Knowledge does not require separate record types for each language; translations are managed as separate versions of the same article, linked by a common KnowledgeArticle record, not by record types. Option C is wrong because the Knowledge search index automatically handles non-English characters and does not require a manual rebuild for Spanish; search indexing issues would affect all languages, not just Spanish queries against English articles. Option D is wrong because data category visibility controls which categories a user can see, but if English articles exist in visible categories, Spanish users would still not see them without language fallback — the issue is language matching, not category access.

30
MCQmedium

Universal Containers wants articles to go through a mandatory review by a quality assurance team before they can be published. However, agents should still be able to save their work as drafts. What feature should the consultant implement?

A.Process Builder automation that changes status from Draft to Published only after QA field is checked.
B.Validation Rule on the Knowledge object checking the publication status.
C.Sharing rules restricting the Publish action to the QA profile.
D.Knowledge Approval Process with an entry criteria of Draft status and an approval action to publish.
AnswerD

A Knowledge Approval Process with entry criteria of Draft status lets agents save drafts freely, then forces submitted articles through the QA team's approval before the publish action executes. This enforces mandatory review while preserving draft saving.

Why this answer

A Knowledge Approval Process is the native mechanism to enforce mandatory review before publication. By setting entry criteria to Draft status and configuring an approval action that publishes the article upon final approval, agents can still save drafts and submit them for QA review. The approval process ensures no article is published without QA sign-off, while preserving the ability to work on drafts.

Exam trap

Service-Con-201 often tests the misconception that Process Builder or Validation Rules can replace a formal approval process, when only the Knowledge Approval Process provides the mandatory review chain with approver assignments.

How to eliminate wrong answers

Option A is wrong because Process Builder cannot reliably enforce a mandatory human review — it automates status changes based on field values, which can be bypassed or triggered prematurely, and it does not provide an approval workflow with assigned approvers. Option B is wrong because a Validation Rule can block saving or publishing under certain conditions, but it cannot orchestrate a multi-step review and approval chain; it only enforces data integrity. Option C is wrong because sharing rules control record access, not the Publish action itself; a QA profile with sharing access could still publish without a formal review step, and agents would be blocked from submitting for review.

31
MCQhard

An administrator is troubleshooting an issue where certain external users on a Community (Experience Cloud site) cannot view translated Knowledge articles. Standard internal users can view them without issue. What is the most likely cause of this behavior?

A.Knowledge translation is only supported for internal users with a full Salesforce license.
B.Translated articles automatically default to 'Archived' status when viewed by community license holders.
C.Language permissions and Data Category visibility for the specific language have not been granted to the Experience Cloud site profile or permission set.
D.The Knowledge component in Experience Cloud must have hardcoded language codes defined in URL parameters.
AnswerC

Knowledge access requires both the language itself and the article's data categories to be granted to the site's profile or permission set. External users lacking either see no translated articles, while internal users with full access view them normally, explaining the discrepancy.

Why this answer

The most likely cause is that language permissions and Data Category visibility for the specific language have not been granted to the Experience Cloud site profile or permission set. Knowledge articles in multiple languages require that the user's profile or permission set has access to the language and that the Data Categories are visible to the site. Internal users may have these permissions, while external users do not.

Exam trap

Service-Con-201 often tests Knowledge access for external users, and candidates may overlook language and Data Category permissions.

How to eliminate wrong answers

Option A is wrong because Knowledge translation is supported for external users with Community licenses; it is not limited to internal full-license users. Option B is wrong because translated articles do not automatically default to 'Archived' status for community users; status is independent of user type. Option D is wrong because the Knowledge component in Experience Cloud does not require hardcoded language codes in URL parameters; language selection is based on user locale and permissions.

32
MCQeasy

An author is writing a new Knowledge article and wants to include a step-by-step table and some embedded images. Which field type should the consultant add to the article page layout to support rich text formatting and images?

A.Encrypted Text
B.Web Address (URL)
C.Rich Text Area
D.Long Text Area
AnswerC

Rich Text Area stores HTML, enabling bold text, tables and inline images directly in the Knowledge article body. It satisfies the stem's requirement for step-by-step tabular content plus embedded images, which plain Text Area or single-line fields cannot render.

Why this answer

A Rich Text Area field supports formatted text, tables, hyperlinks, and inline images, which is exactly what the author needs for a step-by-step table with embedded images. It is the only standard field type in the list that natively renders rich HTML content within a Knowledge article.

Exam trap

Service-Con-201 often tests the difference between Long Text Area and Rich Text Area, so candidates who see 'text field' and pick Long Text Area miss that only Rich Text Area supports tables and embedded images.

How to eliminate wrong answers

Option A is wrong because Encrypted Text stores masked, encrypted values for sensitive data and cannot render formatting or images. Option B is wrong because Web Address (URL) stores a single hyperlink string and cannot hold tables or embedded images. Option D is wrong because Long Text Area stores up to 32,000 characters of plain text without rich formatting, tables, or inline image support.

33
Multi-Selecteasy

Universal Containers wants to track article utilization and effectiveness. Which TWO standard metrics or reports are available out-of-the-box for Salesforce Knowledge? (Choose two.)

Select 2 answers
A.Daily backup storage utilization per article.
B.Articles By Case report showing how many times articles were attached to cases.
C.Article View Statistics reporting view counts by channel.
D.Automated customer satisfaction survey score per individual paragraph.
E.Real-time agent keystroke analytics during article authoring.
AnswersB, C

Articles By Case is a standard Knowledge report type that counts article attachments to cases, directly satisfying the utilisation-tracking requirement. It measures how often agents attach articles while resolving cases, giving out-of-the-box visibility into which articles are actually used in service.

Why this answer

Option B is correct because Salesforce Knowledge provides the standard 'Articles By Case' report, which shows how often articles are attached to cases and helps measure article utilization in the case-resolution workflow. Option C is correct because Knowledge includes Article View Statistics, which reports article view counts broken down by channel (such as internal Salesforce Classic, Lightning Experience, and external channels), supporting effectiveness tracking. Option A is incorrect because Salesforce does not offer a standard metric for daily backup storage utilization per article; backups are handled at the org/data level, not per article.

Option D is incorrect because customer satisfaction is captured through surveys (e.g., Salesforce Feedback Management) and is not scored per individual article paragraph out of the box. Option E is incorrect because real-time agent keystroke analytics during article authoring is not a standard Salesforce Knowledge feature.

Exam trap

Service-Con-201 often tests whether candidates know the specific standard Knowledge reports (Articles By Case, Article View Statistics) versus fabricated metrics like per-paragraph CSAT or keystroke analytics.

34
MCQhard

Universal Containers uses Salesforce Knowledge and wants to ensure that when an article is archived, it is automatically removed from all customer-facing Experience Cloud sites immediately. How does Salesforce Knowledge handle archiving behavior regarding visibility?

A.Archived articles must be manually deleted from Experience Cloud workspace CMS spaces.
B.Archived articles stay visible to community users unless an explicit sharing rule is removed.
C.Archived articles remain visible in Experience Cloud sites until a batch job runs nightly.
D.Archived articles are immediately removed from all channels and search results, remaining accessible only to users with 'View Archived Articles' permission.
AnswerD

Archiving immediately strips the article from all channels and search results, leaving it visible only to users holding the 'View Archived Articles' permission. This satisfies the requirement for instant removal from customer-facing Experience Cloud sites.

Why this answer

When a Knowledge article is archived, Salesforce immediately removes it from all channels — including Experience Cloud sites, search results, and article lists — and it becomes accessible only to users with the 'View Archived Articles' permission. This is the native archiving behavior: archiving is a visibility control, not a deletion, and it takes effect immediately without batch jobs or manual CMS cleanup.

Exam trap

Service-Con-201 often tests the misconception that archiving is a delayed or manual process, when in fact it immediately removes articles from all channels and search results.

How to eliminate wrong answers

Option A is wrong because archiving does not require manual deletion from Experience Cloud CMS spaces; the article is automatically hidden from all channels upon archiving. Option B is wrong because archived articles do not stay visible to community users; visibility is revoked immediately regardless of sharing rules. Option C is wrong because there is no nightly batch job involved — the removal from channels and search is immediate upon archiving, not deferred.

35
Multi-Selecthard

Universal Containers is auditing its Salesforce Knowledge implementation and reviewing article lifecycle states. Which THREE article states exist natively in Salesforce Knowledge? (Choose three.)

Select 3 answers
A.Pending Review
B.Archived
C.Published
D.Deleted
E.Draft
AnswersB, C, E

Archived is a native Knowledge article lifecycle state, applied when an article is retired from active use but retained for reference. It satisfies the stem's requirement for a genuine native state, distinct from Draft, Published, and translation-related statuses.

Why this answer

Salesforce Knowledge natively supports the article lifecycle states Draft, Published, and Archived, so options B, C, and E are correct. Draft (E) is the initial state where an article is being authored and is not visible to end users through standard channels. Published (C) is the state in which an article is live and available to users, and Archived (B) is the terminal state used to retire an article from active use while retaining it for reference.

Pending Review (A) is not a native article lifecycle state; it is associated with approval processes that can be layered on top of Knowledge, not a built-in state. Deleted (D) is also not a lifecycle state; deletion is a record operation that removes the article rather than a status it can hold.

Exam trap

Service-Con-201 often tests whether candidates confuse custom workflow statuses (like 'Pending Review' or 'In Review') with the three native PublishStatus values, leading them to select non-existent states.

36
MCQhard

Universal Containers uses Salesforce Knowledge and requires that articles written in English are automatically translated to Spanish when submitted for review. What is the correct way to handle translation in Salesforce Knowledge?

A.Create a separate article type for Spanish and use workflow field updates to copy English content.
B.Set up a Process Builder flow that calls an external translation API to overwrite the Spanish article fields.
C.Configure Translation Management to automatically push articles to a localization vendor upon submission.
D.Enable Translation Management, define languages, and assign translation tasks manually or via assignment rules.
AnswerD

Translation Management is the native Salesforce Knowledge feature for multi-language content: enabling it, defining supported languages, and creating translation tasks (manually or via assignment rules) links translated versions to the master article. It does not auto-translate; humans or agencies complete the Spanish text.

Why this answer

Salesforce Knowledge Translation Management is the native feature for multilingual articles. You enable it, define the languages, and then assign translation tasks to translators either manually or through assignment rules. This workflow supports submitting articles for translation and tracking their status through review and publication.

Exam trap

The trap is assuming Translation Management automatically sends content to a vendor or that you need custom code — the native feature requires manual or rule-based task assignment, not automatic vendor push.

How to eliminate wrong answers

Option A is wrong because creating a separate article type for Spanish and copying content via workflow does not provide a true translation workflow and duplicates data, breaking the multilingual article model. Option B is wrong because Process Builder cannot call an external translation API to overwrite fields in the standard way described, and this is not the native translation mechanism. Option C is wrong because Translation Management does not automatically push articles to a localization vendor; it creates tasks that can be assigned to internal or external translators, but the push is not automatic.

37
MCQmedium

Universal Containers has a Lightning Knowledge article type called 'Troubleshooting Guide' that includes a custom rich text field named 'Steps to Resolve'. The field is currently not visible to agents when they view published articles. A consultant needs to make this field visible on the article detail page without changing the article type definition. What should the consultant do?

A.Add the 'Steps to Resolve' field to the article type's page layout for the 'Troubleshooting Guide' record type.
B.Modify the article type to mark the field as 'Required' so it appears on the article detail page.
C.Create a new article type that includes the 'Steps to Resolve' field and migrate existing articles to it.
D.Edit the field-level security for the 'Steps to Resolve' field to ensure the agent's profile has read access.
AnswerA

In Lightning Knowledge, the visibility of fields on an article detail page is controlled by the page layout assigned to the article type's record type. Adding the field to the page layout makes it visible to users who have access to that layout. This is the standard, declarative way to expose a custom field on an article without altering the article type itself, which defines the data structure. The other options either change the data model or do not directly control field visibility on the article detail page.

Why this answer

In Lightning Knowledge, article type page layouts determine which fields are displayed on the article detail page. To make the custom field visible, the consultant must add it to the page layout associated with the article type's record type. Changing the article type definition, creating a new article type, or adjusting field-level security does not control UI visibility.

The correct action is to modify the page layout, which is a declarative, non-disruptive change.

Exam trap

The trap here is confusing field-level security with page layout visibility, assuming that granting read access automatically displays the field on the article detail page.

38
MCQhard

Universal Containers is migrating its legacy FAQ system into Salesforce Knowledge. They have 15,000 published HTML documents with embedded metadata. Which migration tool or method should the consultant recommend?

A.Salesforce Files API with custom Apex batch classes.
B.Data Loader with the standard Knowledge Article Version object.
C.Salesforce Console Migration Wizard in Setup.
D.The Knowledge Import Tool using a zip file containing CSV/XML and a properties file.
AnswerD

The Knowledge Import Tool ingests a zip containing CSV or XML article data plus a properties file mapping fields, so the embedded metadata in all 15,000 HTML documents can be migrated in bulk. It satisfies the volume and metadata-mapping constraint that manual creation or single-record imports cannot handle.

Why this answer

The Knowledge Import Tool is the purpose-built migration utility for bulk-loading Knowledge articles from a zip file containing CSV or XML data plus a properties file that maps fields and defines article types. It is designed for large-volume imports of HTML documents with metadata, making it the correct recommendation for 15,000 legacy FAQ documents.

Exam trap

Service-Con-201 often tests whether candidates know the Knowledge Import Tool is the OOTB bulk migration utility for articles, so candidates who default to Data Loader or invent a migration wizard pick the wrong answer.

How to eliminate wrong answers

Option A is wrong because the Salesforce Files API with custom Apex is a generic file-handling approach, not a Knowledge-aware migration tool, and it would require extensive custom development to map metadata and article versions. Option B is wrong because Data Loader against KnowledgeArticleVersion is possible but cumbersome for HTML content and metadata, and it doesn't handle the rich article structure as cleanly as the Import Tool. Option C is wrong because there is no 'Salesforce Console Migration Wizard' in Setup for Knowledge migration — this is a fabricated option.

39
MCQeasy

A user is trying to create a new Knowledge article in the console, but the 'New' button is missing from the Lightning Knowledge component. What is the most likely reason?

A.The user's profile does not have 'Create' permission on the Knowledge object.
B.The article record type is assigned to a different app.
C.Knowledge has not been enabled in Service Setup.
D.The user needs a separate Salesforce CRM Content license.
AnswerA

Without Create permission on the Knowledge object, the Lightning Knowledge component suppresses the 'New' button entirely, so the user cannot initiate an article. Profile-level object permissions gate record creation before any article type or record type settings apply, making this the most likely cause.

Why this answer

The 'New' button on the Lightning Knowledge component is rendered based on the running user's object-level Create permission on the Knowledge object. If the profile (or a permission set) lacks 'Create' on Knowledge, the component suppresses the button entirely rather than showing a disabled state. This is the most common cause when a user can view articles but cannot author new ones.

Exam trap

Service-Con-201 often tests the difference between object-level CRUD permissions (which hide the New button) and record-type or article-type assignments (which affect which types appear), so candidates who pick 'record type assigned to a different app' confuse layout/app assignment with the actual permission gate.

How to eliminate wrong answers

Option B is wrong because record types are assigned to profiles and apps for layout/selection purposes; a record type assigned to a different app does not hide the New button on the Knowledge component. Option C is wrong because if Knowledge were not enabled in Service Setup, the Knowledge component and Knowledge tab would not appear at all, and no articles could be viewed either. Option D is wrong because Salesforce CRM Content licenses are only required for Salesforce CRM Content (Content libraries/workspaces), not for Lightning Knowledge article creation.

Ready to test yourself?

Try a timed practice session using only Knowledge Management questions.