Service-Con-201 Knowledge Management Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Create distinct Lightning Record Pages for each product line and embed separate Knowledge components filtered by hardcoded record types.

  Why it's wrong here

  Creating separate pages per product line does not scale and misuses Lightning Record Pages when dynamic filtering via Data Category Mapping is standard practice.

• ✓

  Map Data Categories to the Case object and configure the Knowledge component to use 'Case Data Categories' filter.

  Why this is correct

  Mapping Data Categories to Cases is the correct mechanism to automatically filter Knowledge search results based on the context of the active Case.

• ✗

  Create a custom formula field on the Case object that pushes product line values directly into article version fields via Process Builder.

  Why it's wrong here

  Process Builder cannot dynamically map fields onto published Knowledge article versions in this manner, and this does not utilize Data Categories.

• ✗

  Assign every agent a specific profile that restricts Data Category visibility using role hierarchies.

  Why it's wrong here

  Role hierarchies control record access for standard objects, but Data Category visibility is managed via Data Category Visibility settings on Profiles or Permission Sets, not purely by role hierarchies.