Knowledge Management practice questions

Embed custom Lightning Web Components directly into the Knowledge object page layout via Object Manager.

Why wrong: D-LWC components are placed via Lightning App Builder, not Object Manager page layouts.

Create separate database tables for each page layout configuration.

Why wrong: Incorrect. Salesforce manages the underlying object schema automatically.

Automatic real-time translation of the article text before approval routing.

Why wrong: Incorrect. Approval processes do not perform automated translation.

Create a separate article type for Spanish and use workflow field updates to copy English content.

Why wrong: Incorrect. Salesforce Knowledge uses a unified article type structure across languages, not separate article types.

Set up a Process Builder flow that calls an external translation API to overwrite the Spanish article fields.

Why wrong: Incorrect. Process Builder cannot dynamically call external APIs and write structured translated content natively.

Configure Translation Management to automatically push articles to a localization vendor upon submission.

Why wrong: Incorrect. Translation Management manages the workflow and assignment of tasks, but does not automatically push to vendors natively.

Knowledge Article View Count dashboard component.

Why wrong: Incorrect. View count tracks how many times an article was viewed, not attached to cases.

Service Analytics App embedded Einstein dashboard.

Why wrong: Incorrect. While analytics apps can show metrics, the standard reports provide this out-of-the-box without extra licensing.

Article Feedback related list on the Case layout.

Why wrong: Incorrect. Article feedback tracks user ratings and comments, not case attachment frequency.

Create a Global Action for Knowledge and place it on the global publisher layout.

Why wrong: Incorrect. Global actions do not provide the contextual article recommendation features needed for Cases.

Modify the Case page layout in Object Manager to include the Knowledge Related List.

Why wrong: Incorrect. While a related list can show attached articles, the interactive component is added via Lightning App Builder.

Enable Article Recommendations in the Service Cloud Setup Assistant.

Why wrong: Incorrect. Article recommendations rely on the Lightning Knowledge component placed in the Lightning App Builder.

Process Builder automation that changes status from Draft to Published only after QA field is checked.

Why wrong: Incorrect. Bypassing approval processes with automation circumvents the multi-step approval history and auditing.

Validation Rule on the Knowledge object checking the publication status.

Why wrong: Incorrect. Validation rules cannot route records for approval or pause the publication workflow interactively.

Sharing rules restricting the Publish action to the QA profile.

Why wrong: Incorrect. Sharing rules control record access, not workflow approvals.

Publish Articles

Why wrong: Incorrect. Publish Articles allows users to make draft articles public, but does not inherently grant archive viewing.

Edit Draft Articles

Why wrong: Incorrect. This permission allows modification of drafts, not viewing archived historical versions.

Manage Articles

Why wrong: Incorrect. Manage Articles grants broad administrative control over creating, editing, publishing, and archiving.

Salesforce Files API with custom Apex batch classes.

Why wrong: Incorrect. While custom code could technically build articles, the native Knowledge Import Tool is the recommended path for standard migrations.

Data Loader with the standard Knowledge Article Version object.

Why wrong: Incorrect. Data Loader cannot handle the complex parent-child relationships between Knowledge base articles and their localized versions as cleanly as the native import tool.

Salesforce Console Migration Wizard in Setup.

Why wrong: Incorrect. No such feature exists under this name.

Set the organization-wide default for Knowledge to Private and create a sharing rule for HR.

Why wrong: Incorrect. Knowledge object-level sharing is controlled via public read/write settings, while visibility is driven by data categories.

Use validation rules to prevent support profiles from querying HR record types.

Why wrong: Incorrect. Validation rules cannot block visibility of records based on user profiles in this manner.

Create a separate Knowledge object and assign it to the HR profile.

Why wrong: Incorrect. There is only one Knowledge object in Salesforce, though multiple record types can be created.

Create a custom approval process that routes to tier-2 agents upon submission for publication.

Why wrong: Incorrect. Approval processes handle the review workflow, not the fundamental permission to publish within data categories.

Set the sharing model for Knowledge to Private and use manual sharing rules.

Why wrong: Incorrect. Knowledge uses Data Categories and sharing rules rather than standard object-level manual sharing for publishing permissions.

Modify the record types assigned to the tier-1 support profile to exclude hardware articles.

Why wrong: Incorrect. Record types control layout and picklist values, not category-level publishing permissions.

The agent cannot edit a published article directly and must archive it first.

Why wrong: Incorrect. Agents with appropriate permissions can edit published articles, which automatically generates a draft.

A copy of the article is created as a brand-new record with a different URL name.

Why wrong: Incorrect. It remains the same article record with a new version number.

The article is automatically unpublished and set to draft for all users until re-published.

Why wrong: Incorrect. Published articles remain available to users while a draft version is being edited.

Create a custom Lightning component override for the New Article button.

Why wrong: Incorrect. Overriding standard buttons with custom components is unnecessary since feed actions support mapping.

Use Workflow Rules with field updates on the Knowledge object.

Why wrong: Incorrect. Workflow rules execute after save and cannot pre-populate values during the creation dialog.

Write an Apex trigger on the Case object that inserts a Knowledge record on creation.

Why wrong: Incorrect. Triggers cannot easily launch interactive console article creation workflows.

Use custom hierarchical custom metadata types for geography and standard picklists for product lines.

Why wrong: Incorrect. Custom metadata types are not designed for article categorization and filtering.

Create separate object record types for each geography and a multi-select picklist for product lines.

Why wrong: Incorrect. Data categories should be used for hierarchical categorization rather than record types and picklists.

Create a single Data Category Group with dependent picklist fields mapping product to geography.

Why wrong: Incorrect. Data category groups do not function as dependent picklists in this manner.

Languages cannot be added after initial setup.

Why wrong: Incorrect. Additional languages can be enabled in Knowledge Settings at any time.

Approval processes become mandatory for all articles.

Why wrong: Incorrect. Approval processes are entirely optional.

Data categories cannot be modified after creation.

Why wrong: Incorrect. Data categories can be updated, added, and reorganized over time.

Google Analytics integration setup logs.

Why wrong: Incorrect. Salesforce provides native article view tracking without requiring Google Analytics.

Case Comment History related list.

Why wrong: Incorrect. Case comments track communication on cases, not article views.

Chatter feed analytics on the article record.

Why wrong: Incorrect. Chatter feed analytics track internal collaboration, not customer views.

Use field-level security to hide the 'Internal Notes' field from the Experience Cloud guest user profile.

Why wrong: Incorrect. Field-level security applies to profiles, but Knowledge page layouts combined with channel mappings provide precise layout control per channel.

Create a validation rule that checks if the viewing user is external and clears the field.

Why wrong: Incorrect. Validation rules prevent saving data, not viewing data.

Use custom CSS in the Experience Cloud site builder to hide the field DOM element.

Why wrong: Incorrect. CSS hiding is insecure as the data is still transmitted to the browser.

Archived articles must be manually deleted from Experience Cloud workspace CMS spaces.

Why wrong: Incorrect. Knowledge archiving handles channel removal natively without separate CMS deletion.

Archived articles stay visible to community users unless an explicit sharing rule is removed.

Why wrong: Incorrect. Sharing rules do not override the archived status of a Knowledge article.

Archived articles remain visible in Experience Cloud sites until a batch job runs nightly.

Why wrong: Incorrect. Archiving removes articles from public channels immediately.

In Service Console App Navigation Rules.

Why wrong: Incorrect. Navigation rules define how tabs open in the console, not component capabilities.

In Knowledge Settings under Feature Settings in Setup.

Why wrong: Incorrect. Global knowledge settings control broad features like validation status and multiple languages, not component-level action buttons.

In Object Manager under Case Page Layouts.

Why wrong: Incorrect. Case page layouts manage standard fields and related lists, not Lightning component internals.

The translated articles are automatically unpublished until the master article is approved.

Why wrong: Incorrect. Published translations remain visible to users until a new translation is published.

The translations are automatically deleted and must be recreated from scratch.

Why wrong: Incorrect. Translations are never automatically deleted when a master article is updated.

The translated versions are automatically overwritten with machine-translated English text.

Why wrong: Incorrect. Salesforce does not perform automated machine translation out of the box.

Enable Chatter Questions on the Knowledge article feed.

Why wrong: Incorrect. Chatter questions are for community collaboration, not native article feedback.

Create a custom object linked to Knowledge and place a related list on the page layout.

Why wrong: Incorrect. Salesforce provides native article feedback features without requiring custom objects.

Configure Case milestones to prompt agents for article ratings upon case closure.

Why wrong: Incorrect. Milestones track time-dependent steps, not article feedback.