Troubleshooting practice questions

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?

Trap 1: Knowledge translation is only supported for internal users with a…

Knowledge translation works for external Experience Cloud users; licence type does not gate the feature. Restricting translation to full internal licences would be the answer if the platform limited localisation by licence, but the actual cause lies in language settings, article visibility or data category access.

Trap 2: Translated articles automatically default to 'Archived' status when…

Translation status is independent of licence type; articles are not auto-archived on viewing by community users. Archiving is a deliberate lifecycle action, so this would explain invisibility only if an administrator had archived the translation, not as an automatic consequence of external access.

Trap 3: The Knowledge component in Experience Cloud must have hardcoded…

Experience Cloud Knowledge components resolve language from the user's locale and article translations, not hardcoded URL parameters. Hardcoding suits forcing a specific language for a single embedded article, but the likely cause here is missing translated article versions or language settings for external users.

A
Knowledge translation is only supported for internal users with a full Salesforce license.
Why it fails: Knowledge translation works for external Experience Cloud users; licence type does not gate the feature. Restricting translation to full internal licences would be the answer if the platform limited localisation by licence, but the actual cause lies in language settings, article visibility or data category access.
B
Translated articles automatically default to 'Archived' status when viewed by community license holders.
Why it fails: Translation status is independent of licence type; articles are not auto-archived on viewing by community users. Archiving is a deliberate lifecycle action, so this would explain invisibility only if an administrator had archived the translation, not as an automatic consequence of external access.
C
Language permissions and Data Category visibility for the specific language have not been granted to the Experience Cloud site profile or permission set.
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.
D
The Knowledge component in Experience Cloud must have hardcoded language codes defined in URL parameters.
Why it fails: Experience Cloud Knowledge components resolve language from the user's locale and article translations, not hardcoded URL parameters. Hardcoding suits forcing a specific language for a single embedded article, but the likely cause here is missing translated article versions or language settings for external users.

Question 2hardmultiple choice

An administrator is troubleshooting an issue where cases assigned to a queue are not being pushed to agents via Omni-Channel. The agents are online, have the correct presence status, and belong to the queue. Upon inspection, the administrator notices the Service Channel is inactive. What is the impact of an inactive Service Channel?

Trap 1: Queues are automatically deleted from the system.

Deactivating a Service Channel stops Omni-Channel routing work items for that channel; it does not delete queues, which exist independently of Omni-Channel. It is tempting because an inactive channel clearly breaks routing, but queue records persist regardless of channel activation state.

Trap 2: Agents cannot log into Omni-Channel.

An inactive Service Channel halts routing of its work items; it does not prevent agents logging into Omni-Channel, which depends on presence configuration and permissions. It is tempting because agents receiving nothing looks like a login failure, but the actual impact is routing suspension for that channel.

Trap 3: Existing open work items are automatically closed.

Inactivating a Service Channel suspends routing of new work items for that channel; existing open items are not automatically closed. It is tempting because inactive channels stop work flowing, but closure of open work requires agent or flow action, not channel deactivation.

A
Queues are automatically deleted from the system.
Why it fails: Deactivating a Service Channel stops Omni-Channel routing work items for that channel; it does not delete queues, which exist independently of Omni-Channel. It is tempting because an inactive channel clearly breaks routing, but queue records persist regardless of channel activation state.
B
Agents cannot log into Omni-Channel.
Why it fails: An inactive Service Channel halts routing of its work items; it does not prevent agents logging into Omni-Channel, which depends on presence configuration and permissions. It is tempting because agents receiving nothing looks like a login failure, but the actual impact is routing suspension for that channel.
C
Existing open work items are automatically closed.
Why it fails: Inactivating a Service Channel suspends routing of new work items for that channel; existing open items are not automatically closed. It is tempting because inactive channels stop work flowing, but closure of open work requires agent or flow action, not channel deactivation.
D
Work items associated with the object are no longer routed by Omni-Channel.
An inactive Service Channel stops Omni-Channel from routing any work items tied to that channel's object, regardless of agent presence or queue membership. Reactivating the channel restores routing, confirming the channel itself is the routing gate.

Question 3mediummultiple choice

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?

Trap 1: Modify the article type to mark the field as 'Required' so it…

Marking a field as required in the article type definition enforces data entry at creation or edit time, but it does not control whether the field is displayed on the article detail page for viewers. Required fields are a validation mechanism, not a layout mechanism. Changing the field to required could also disrupt existing publishing processes. The correct approach is to update the page layout, not the article type's field properties.

Trap 2: Create a new article type that includes the 'Steps to Resolve'…

Creating a new article type would require migrating all existing articles, which is unnecessary and disruptive. The field already exists in the current article type; the issue is only its visibility. Article types define the structure of an article, but page layouts control the user interface. This approach does not address the visibility problem and introduces data migration overhead. The consultant should simply adjust the page layout instead.

Trap 3: Edit the field-level security for the 'Steps to Resolve' field to…

Field-level security determines whether a user can view or edit a field's data, but it does not control whether the field appears on a page layout. Even with read access, the field will not show on the article detail page unless it is added to the page layout. Field-level security is a permission control, not a layout control. Therefore, this action alone would not make the field visible to agents in the Knowledge component.

A
Add the 'Steps to Resolve' field to the article type's page layout for the 'Troubleshooting Guide' record type.
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.
B
Modify the article type to mark the field as 'Required' so it appears on the article detail page.
Why it fails: Marking a field as required in the article type definition enforces data entry at creation or edit time, but it does not control whether the field is displayed on the article detail page for viewers. Required fields are a validation mechanism, not a layout mechanism. Changing the field to required could also disrupt existing publishing processes. The correct approach is to update the page layout, not the article type's field properties.
C
Create a new article type that includes the 'Steps to Resolve' field and migrate existing articles to it.
Why it fails: Creating a new article type would require migrating all existing articles, which is unnecessary and disruptive. The field already exists in the current article type; the issue is only its visibility. Article types define the structure of an article, but page layouts control the user interface. This approach does not address the visibility problem and introduces data migration overhead. The consultant should simply adjust the page layout instead.
D
Edit the field-level security for the 'Steps to Resolve' field to ensure the agent's profile has read access.
Why it fails: Field-level security determines whether a user can view or edit a field's data, but it does not control whether the field appears on a page layout. Even with read access, the field will not show on the article detail page unless it is added to the page layout. Field-level security is a permission control, not a layout control. Therefore, this action alone would not make the field visible to agents in the Knowledge component.

Question 4hardmultiple choice

A consultant is troubleshooting an issue where cases created for a customer with an active entitlement are not receiving any milestones. The entitlement process is active and assigned. What is the most likely cause?

Trap 1: Business hours are not assigned to the User profile.

Milestone timers run against the entitlement's business hours, but missing hours on the User profile do not stop milestones from being created — they only affect target calculations. It tempts because business hours govern milestone timing, yet the failure here is that no milestone record is generated at all.

Trap 2: The Entitlement is associated with a Service Contract instead of an…

Entitlements attach to Accounts or Products, not Service Contracts, so this association cannot exist as described. It tempts because Service Contracts also define support coverage, but milestone generation depends on the entitlement's channel and SLA, not on contract linkage.

Trap 3: The Entitlement Template has not been applied to the Contact record.

Entitlement Templates seed default entitlements when a Contact or Account is created; they are not applied afterwards to activate an existing entitlement. It tempts because templates sound like the assignment step, but the stem already states the entitlement is active and assigned, so template application is irrelevant.

A
Business hours are not assigned to the User profile.
Why it fails: Milestone timers run against the entitlement's business hours, but missing hours on the User profile do not stop milestones from being created — they only affect target calculations. It tempts because business hours govern milestone timing, yet the failure here is that no milestone record is generated at all.
B
The Entitlement is associated with a Service Contract instead of an Account.
Why it fails: Entitlements attach to Accounts or Products, not Service Contracts, so this association cannot exist as described. It tempts because Service Contracts also define support coverage, but milestone generation depends on the entitlement's channel and SLA, not on contract linkage.
C
The Entitlement Template has not been applied to the Contact record.
Why it fails: Entitlement Templates seed default entitlements when a Contact or Account is created; they are not applied afterwards to activate an existing entitlement. It tempts because templates sound like the assignment step, but the stem already states the entitlement is active and assigned, so template application is irrelevant.
D
The Milestone's criteria are not met by the newly created case's field values.
Milestones fire only when their criteria evaluate true against the case's field values, so a mismatch silently suppresses them even with an active, assigned entitlement process. Since the stem confirms the process itself is active and assigned, the remaining constraint is criteria evaluation, making unmet milestone criteria the likely cause.

Question 5mediummulti select

A consultant is troubleshooting data synchronization failures between an external ERP and Service Cloud. Which TWO diagnostic tools should the consultant use to investigate API errors? (Choose two.)

Trap 1: Omni-Channel Supervisor real-time metrics dashboard.

Omni-Channel Supervisor metrics report agent presence, capacity and work-item routing in real time; they expose nothing about API callouts or ERP synchronisation errors. API failures are diagnosed through API Usage notifications and debug logs. Supervisor metrics are correct for live queue and agent performance monitoring.

Trap 2: Knowledge article version history.

Knowledge article version history tracks revisions to article content and publication state; it holds no record of inbound API requests or their error responses. ERP synchronisation failures are investigated with API Usage notifications and debug logs. Version history is correct when auditing Knowledge article changes.

Trap 3: Standard Case History related lists on individual records.

Case History related lists record field changes made to a Case record over time; they do not capture API request payloads, status codes or integration errors. API failures require API Usage notifications and debug logs. Case History is correct for auditing user edits to individual case fields.

A
Event Monitoring REST API and log files to analyze API usage and failures.
Event Monitoring's REST API exposes API usage and failure events, while log files capture request details, letting the consultant trace synchronisation errors between the ERP and Service Cloud. This satisfies the need to investigate API failures diagnostically.
B
Omni-Channel Supervisor real-time metrics dashboard.
Why it fails: Omni-Channel Supervisor metrics report agent presence, capacity and work-item routing in real time; they expose nothing about API callouts or ERP synchronisation errors. API failures are diagnosed through API Usage notifications and debug logs. Supervisor metrics are correct for live queue and agent performance monitoring.
C
Knowledge article version history.
Why it fails: Knowledge article version history tracks revisions to article content and publication state; it holds no record of inbound API requests or their error responses. ERP synchronisation failures are investigated with API Usage notifications and debug logs. Version history is correct when auditing Knowledge article changes.
D
Salesforce Debug Logs with refined database and callout trace flags.
Debug logs with database and callout trace flags capture the exact SOQL, DML and HTTP callout activity during synchronisation, revealing where ERP API requests fail. This satisfies the requirement to diagnose API errors at the transaction level.
E
Standard Case History related lists on individual records.
Why it fails: Case History related lists record field changes made to a Case record over time; they do not capture API request payloads, status codes or integration errors. API failures require API Usage notifications and debug logs. Case History is correct for auditing user edits to individual case fields.

Question 6hardmultiple choice

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?

Trap 1: It relies entirely on manual tagging performed by agents when…

Recommendations are generated by matching case fields against article content, not by agent tagging. Manual tagging is tempting because tags do aid search, and it would be correct where agents curate a controlled vocabulary for article findability rather than relying on automated matching.

Trap 2: It requires custom Apex triggers that query articles using SOSL and…

The Lightning Knowledge component surfaces recommendations natively, so no Apex or SOSL query is required. Custom Apex is tempting because SOSL searches article text, and it would be correct for bespoke search behaviour the standard component cannot deliver.

Trap 3: It uses Assignment Rules configured in Setup to match case…

Assignment Rules route cases to owners or queues; they do not surface article recommendations. They are tempting because they match case fields to criteria, and they would be correct for distributing incoming cases to the right support queue.

A
It uses keyword matching from the Case Subject and Description against article titles and body content.
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.
B
It relies entirely on manual tagging performed by agents when closing previous cases.
Why it fails: Recommendations are generated by matching case fields against article content, not by agent tagging. Manual tagging is tempting because tags do aid search, and it would be correct where agents curate a controlled vocabulary for article findability rather than relying on automated matching.
C
It requires custom Apex triggers that query articles using SOSL and push them to a custom related list.
Why it fails: The Lightning Knowledge component surfaces recommendations natively, so no Apex or SOSL query is required. Custom Apex is tempting because SOSL searches article text, and it would be correct for bespoke search behaviour the standard component cannot deliver.
D
It uses Assignment Rules configured in Setup to match case categories to data categories.
Why it fails: Assignment Rules route cases to owners or queues; they do not surface article recommendations. They are tempting because they match case fields to criteria, and they would be correct for distributing incoming cases to the right support queue.

Question 7mediummultiple choice

Support agents frequently copy and paste the same greeting and troubleshooting steps into case comments. They want a faster way to insert this pre-approved text without using macros. What should the consultant recommend?

Trap 1: Rich Text Component

A Rich Text Component displays formatted content on a record page but provides no insertion mechanism into case comments, so agents would still copy manually. It is tempting as reusable formatted content, and would be correct for displaying guidance or instructions on a page.

Trap 2: Email Templates

Email Templates populate outbound email bodies, not case comment fields, so they cannot insert pre-approved text into comments. They are tempting because they store reusable text, and would be the right choice when agents send standardised replies by email.

Trap 3: Custom Buttons

Custom Buttons execute URLs, JavaScript or Visualforce actions, not text insertion into a comment field, so they cannot paste pre-approved wording. They are tempting as one-click automation, and would suit launching an action or navigating elsewhere rather than inserting text.

A
Rich Text Component
Why it fails: A Rich Text Component displays formatted content on a record page but provides no insertion mechanism into case comments, so agents would still copy manually. It is tempting as reusable formatted content, and would be correct for displaying guidance or instructions on a page.
B
Email Templates
Why it fails: Email Templates populate outbound email bodies, not case comment fields, so they cannot insert pre-approved text into comments. They are tempting because they store reusable text, and would be the right choice when agents send standardised replies by email.
C
Quick Text
Quick Text stores pre-approved greetings and troubleshooting snippets that agents insert into case comments via a picklist, avoiding macros entirely. It satisfies the requirement for faster insertion of standardised text, and admins can control which users access each Quick Text folder.
D
Custom Buttons
Why it fails: Custom Buttons execute URLs, JavaScript or Visualforce actions, not text insertion into a comment field, so they cannot paste pre-approved wording. They are tempting as one-click automation, and would suit launching an action or navigating elsewhere rather than inserting text.

Question 8hardmultiple choice

An administrator is troubleshooting a Case Escalation Rule that is failing to trigger. The rule criteria are met, and the time triggers are set correctly. However, the organization uses custom business hours, and cases are created outside of these business hours. What is the impact on the escalation rule?

Trap 1: Cases created outside business hours immediately trigger escalation…

Cases created outside business hours do not escalate immediately; the age clock starts only when business hours resume. It is tempting because creation is the obvious event, but escalation age accrues against the business-hours calendar, so the trigger fires later than the raw creation timestamp suggests.

Trap 2: The escalation rule will throw a system exception due to timezone…

No exception is thrown; escalation rules simply evaluate against the business-hours calendar without erroring. It is tempting because timezone and business-hours settings are related configuration, but the real effect is that the age clock excludes non-business time, delaying the trigger rather than failing.

Trap 3: Escalation rules ignore business hours entirely and always use 24/7…

Escalation rules respect the business hours defined in your org, so they do not run on 24/7 calendar time. It is tempting because escalation age calculations can appear continuous, but the actual behaviour is that the clock pauses outside business hours, delaying the trigger.

A
Cases created outside business hours immediately trigger escalation actions upon creation.
Why it fails: Cases created outside business hours do not escalate immediately; the age clock starts only when business hours resume. It is tempting because creation is the obvious event, but escalation age accrues against the business-hours calendar, so the trigger fires later than the raw creation timestamp suggests.
B
The escalation rule will throw a system exception due to timezone mismatch.
Why it fails: No exception is thrown; escalation rules simply evaluate against the business-hours calendar without erroring. It is tempting because timezone and business-hours settings are related configuration, but the real effect is that the age clock excludes non-business time, delaying the trigger rather than failing.
C
Escalation rules ignore business hours entirely and always use 24/7 calendar time.
Why it fails: Escalation rules respect the business hours defined in your org, so they do not run on 24/7 calendar time. It is tempting because escalation age calculations can appear continuous, but the actual behaviour is that the clock pauses outside business hours, delaying the trigger.
D
The escalation timer will only increment during the defined business hours associated with the case.
Escalation timers accrue only while the associated business hours are open, so cases created outside those hours do not advance until the next business-hours window. This satisfies the constraint that custom business hours govern escalation timing.

Review the full routing breakdown →

Question 9hardmulti select

An administrator is troubleshooting an Omni-Channel Flow that is failing to route work items correctly. Which THREE debugging or configuration best practices should the administrator check? (Choose three.)

Trap 1: Check that the Debug Log level for Workflow is set to Maximum.

Debug Log levels apply to Apex, Visualforce and process logs, not to Omni-Channel routing configuration, so raising Workflow to Maximum captures nothing about why work items fail to route. It is tempting because Maximum logging is genuinely useful when diagnosing Apex execution or flow interview errors in a developer sandbox.

Trap 2: Verify that external API endpoints are configured for native queue…

External API endpoints belong to Omni-Channel integrations and custom routing, not native queue routing, which relies on routing configurations, presence statuses and capacity settings. It is tempting because endpoint configuration genuinely matters when work items arrive through external systems, so it would be the right check for an API-driven integration scenario rather than this queue-routing failure.

A
Verify that the active version of the flow contains the correct Route Work action parameters.
Flow routing failures often stem from the wrong flow version being active, so verifying that the active version's Route Work action contains correct parameters ensures the intended routing logic actually executes rather than an outdated or misconfigured version.
B
Check that the Debug Log level for Workflow is set to Maximum.
Why it fails: Debug Log levels apply to Apex, Visualforce and process logs, not to Omni-Channel routing configuration, so raising Workflow to Maximum captures nothing about why work items fail to route. It is tempting because Maximum logging is genuinely useful when diagnosing Apex execution or flow interview errors in a developer sandbox.
C
Verify that external API endpoints are configured for native queue routing.
Why it fails: External API endpoints belong to Omni-Channel integrations and custom routing, not native queue routing, which relies on routing configurations, presence statuses and capacity settings. It is tempting because endpoint configuration genuinely matters when work items arrive through external systems, so it would be the right check for an API-driven integration scenario rather than this queue-routing failure.
D
Confirm that the target queue and service channel are active and correctly referenced.
Routing fails silently when the target queue or service channel is inactive or the flow references a stale ID, so verifying both are active and correctly referenced satisfies the stem's requirement to check configuration integrity before deeper debugging.
E
Ensure the Record ID variable correctly receives the work item ID from the triggering context.
Omni-Channel routing depends on the work item ID being passed into the flow; if the Record ID variable is unbound or mis-mapped from the triggering context, routing cannot resolve the correct record, directly addressing the stem's routing failure.

Question 10easymultiple choice

An agent is responding to a customer via email from the Case Feed and wants to attach a troubleshooting guide PDF stored in Salesforce CRM Content. How should the agent accomplish this?

Trap 1: Use Web-to-Case to automatically attach knowledge articles.

Web-to-Case creates new cases from web forms; it does not attach CRM Content files to an outbound agent email. It is tempting because it does link knowledge to cases automatically, and would be correct when capturing inbound web submissions rather than replying from Case Feed.

Trap 2: Paste the file URL into the subject line of the email.

A URL in the subject line is plain text, not an attachment, and recipients cannot open the PDF from it. It is tempting because sharing a link is a common workaround, and would be correct if the guide were hosted on an externally accessible site and a link sufficed.

Trap 3: Use a Macro to upload the file from the agent's desktop.

A Macro inserts predefined text or performs quick actions; it cannot pull a PDF from Salesforce CRM Content into an email. It is tempting because Macros do speed up Case Feed replies, and would be correct for inserting canned response text, not for attaching a stored content file.

A
Use Web-to-Case to automatically attach knowledge articles.
Why it fails: Web-to-Case creates new cases from web forms; it does not attach CRM Content files to an outbound agent email. It is tempting because it does link knowledge to cases automatically, and would be correct when capturing inbound web submissions rather than replying from Case Feed.
B
Paste the file URL into the subject line of the email.
Why it fails: A URL in the subject line is plain text, not an attachment, and recipients cannot open the PDF from it. It is tempting because sharing a link is a common workaround, and would be correct if the guide were hosted on an externally accessible site and a link sufficed.
C
Click the attach file icon within the Email publisher in the Case Feed and select the file from Salesforce.
The Email publisher in Case Feed includes an attach file icon that browses Salesforce Files and CRM Content, inserting the PDF as a link or attachment. This keeps the troubleshooting guide within the email without leaving the case.
D
Use a Macro to upload the file from the agent's desktop.
Why it fails: A Macro inserts predefined text or performs quick actions; it cannot pull a PDF from Salesforce CRM Content into an email. It is tempting because Macros do speed up Case Feed replies, and would be correct for inserting canned response text, not for attaching a stored content file.

Question 11easymultiple choice

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?

Trap 1: Create a validation rule that prevents articles from being…

A validation rule can block saving or publishing based on field values, but it does not route the article to a reviewer or trigger a review step automatically. An author could type any name into the field to satisfy the rule, bypassing genuine legal review. This enforces data entry, not an approval workflow, so it does not meet the requirement.

Trap 2: Build a Flow that sets the article status to Published whenever the…

Automatically publishing on save removes the legal review entirely, which is the opposite of what is required. The articles must be gated behind review before agents can use them, and this automation would expose unreviewed content immediately. Setting status to Published by flow is therefore a direct violation of the stated process.

Trap 3: Assign the articles a Draft validation status and manually notify…

Draft status keeps an article unpublished, but relying on manual email notification means the review is not triggered by the author's submission and can easily be skipped. The requirement explicitly calls for an automatic trigger when the author submits, which manual notification cannot guarantee. This leaves the process error-prone and does not satisfy the automation requirement.

A
Create a validation rule that prevents articles from being published unless the legal reviewer's name is entered in a field.
Why it fails: A validation rule can block saving or publishing based on field values, but it does not route the article to a reviewer or trigger a review step automatically. An author could type any name into the field to satisfy the rule, bypassing genuine legal review. This enforces data entry, not an approval workflow, so it does not meet the requirement.
B
Build a Flow that sets the article status to Published whenever the author saves the record.
Why it fails: Automatically publishing on save removes the legal review entirely, which is the opposite of what is required. The articles must be gated behind review before agents can use them, and this automation would expose unreviewed content immediately. Setting status to Published by flow is therefore a direct violation of the stated process.
C
Configure a Knowledge article approval process with an assigned approver and enable it for the article type.
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.
D
Assign the articles a Draft validation status and manually notify the legal team by email when each draft is finished.
Why it fails: Draft status keeps an article unpublished, but relying on manual email notification means the review is not triggered by the author's submission and can easily be skipped. The requirement explicitly calls for an automatic trigger when the author submits, which manual notification cannot guarantee. This leaves the process error-prone and does not satisfy the automation requirement.

Question 12easymultiple choice

A tier-one support team needs to capture structured troubleshooting steps during phone interactions. The questions change dynamically based on the customer's previous answers. Which feature should the consultant implement?

Trap 1: Standard Case Comment related list

Case comments are unstructured text boxes and do not provide dynamic step-by-step guidance.

Trap 2: Quick Actions with predefined field values

Quick actions execute predefined field updates or record creations, not interactive conditional questionnaires.

Trap 3: Entitlement Processes

Entitlement Processes define milestone and entitlement timelines for service contracts, not interactive question branching. They cannot present dynamically changing questions based on prior answers. A guided flow or Omni-Channel script is required for adaptive troubleshooting steps. Entitlement Processes would be correct when enforcing support term milestones and actions.

A
Standard Case Comment related list
Why it fails: Case comments are unstructured text boxes and do not provide dynamic step-by-step guidance.
B
Quick Actions with predefined field values
Why it fails: Quick actions execute predefined field updates or record creations, not interactive conditional questionnaires.
C
Entitlement Processes
Why it fails: Entitlement Processes define milestone and entitlement timelines for service contracts, not interactive question branching. They cannot present dynamically changing questions based on prior answers. A guided flow or Omni-Channel script is required for adaptive troubleshooting steps. Entitlement Processes would be correct when enforcing support term milestones and actions.
D
Screen Flow embedded on the Lightning Record Page
A Screen Flow embedded on the Lightning Record Page presents guided questions whose subsequent steps branch on earlier answers, capturing structured troubleshooting data during the call. This satisfies the dynamic, answer-dependent questioning requirement that static fields cannot.