Courseiva

Salesforce Certified Service Cloud Consultant (Service-Con-201) (Service-Con-201) (Service-Con-201) — Questions 226–250

250 questions total · 4 pages · All types, answers revealed

Take a mock examExam hub
Page 3

Page 4 of 4

226
Multi-Selecthard

An administrator is setting up Overflow Routing for high-volume queues. Which THREE considerations apply when configuring Overflow Routing in Omni-Channel? (Choose three.)

Select 3 answers
A.Overflow routing automatically bypasses all agent skill requirements on the secondary queue.
B.Overflow routing can redirect work when primary queue wait times or capacity thresholds are exceeded.
C.Overflow routing is configured declaratively in Setup without requiring custom Apex code.
D.Overflow routing is only available when using external third-party CTI connectors.
E.Secondary routing configurations or queues must be established to receive overflow work.
AnswersB, C, E

Overflow Routing triggers on queue-level thresholds: maximum wait time and maximum queue size. When either is exceeded, Omni-Channel diverts new work to a secondary queue, satisfying the stem's high-volume scenario by preventing unbounded waits. Capacity here means queue depth, not agent presence status.

Why this answer

Option B is correct because Overflow Routing in Omni-Channel is triggered by defined thresholds on the primary queue, such as maximum wait time or queue capacity being exceeded, at which point the work item is rerouted. Option C is correct because Overflow Routing is configured declaratively through Omni-Channel queue and routing configuration settings in Setup, without needing custom Apex code. Option E is correct because overflow work must have a destination: a secondary queue or routing configuration must already exist to receive the rerouted work items.

Option A is not correct because overflow routing does not bypass agent skill requirements; the receiving queue still applies its own routing and skill-based assignment rules. Option D is not correct because Overflow Routing is a native Omni-Channel capability and is not limited to external third-party CTI connectors.

Exam trap

Service-Con-201 often tests the misconception that overflow routing ignores skills or requires custom Apex/CTI, when it is declarative and respects the secondary queue's skill requirements.

Full explanation →
227
Multi-Selecteasy

A support supervisor wants to monitor agent performance and operational metrics in real time. Which TWO standard tools should the consultant recommend? (Choose two.)

Select 2 answers
A.Omni-Channel Supervisor for real-time agent status and queue tracking
B.Salesforce Content version history logs
C.Entitlement process audit trails
D.Salesforce Dashboards for visualized operational report metrics
E.Chatter user profile activity feeds
AnswersA, D

Omni-Channel Supervisor provides live agent status, capacity usage and queue depth, letting supervisors watch workload distribution as it changes. This satisfies the stem's real-time monitoring constraint, which static reports cannot meet because they refresh on a schedule.

Why this answer

Option A, Omni-Channel Supervisor, is correct because it is the standard Service Cloud console specifically designed for real-time monitoring of agent status, capacity, and queue/workload tracking, letting supervisors see who is available, busy, or overloaded and reassign work as needed. Option D, Salesforce Dashboards, is correct because dashboards provide visualized, near real-time metrics from source reports (with scheduled or dynamic refreshing), giving supervisors operational KPIs such as case volume, handle time, and backlog trends. Option B, Content version history logs, is not appropriate because it tracks versions of Salesforce Files/Content documents, not agent performance or operational metrics.

Option C, Entitlement process audit trails, is not appropriate because entitlement processes and their audit trails govern service-level milestone compliance, not real-time agent monitoring. Option E, Chatter user profile activity feeds, is not appropriate because Chatter feeds show social collaboration posts and updates, not structured real-time operational metrics.

Exam trap

Service-Con-201 often tests the difference between real-time operational tools (Omni-Channel Supervisor) and historical reporting tools (Dashboards), tricking candidates into selecting audit logs or Chatter feeds that do not provide performance monitoring.

Full explanation →
228
MCQhard

An administrator needs to implement Skills-Based Routing to route cases concerning specific product tiers to agents with matching certifications. Which setup step is mandatory before creating Skills-Based Routing Rules?

A.Configure External Routing API
B.Enable Skills-Based Routing in Setup
C.Enable Omni-Channel in Setup
D.Create a Custom Skill Object
AnswerB

Skills-Based Routing must be enabled in Setup before any routing rules can be created; the feature toggle gates access to the rule builder. Without it, the mandatory prerequisite for matching product-tier certifications cannot be configured.

Why this answer

Before configuring Skills-Based Routing Rules via flows or Omni-Channel Flow, the administrator must enable Skills-Based Routing in Setup and ensure that Skill Requirements can be created and mapped dynamically.

Full explanation →
229
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.

Full explanation →
230
MCQhard

An enterprise organization requires that all customer interactions across Phone, Email, Chat, and Messaging are tracked within a unified timeline in the Service Cloud Console, allowing agents to see chronological touchpoints instantly. Which feature fulfills this requirement?

A.Standard related lists displayed in separate tabs
B.Account Hierarchy related lists
C.Case Feed with integrated Omni-Channel and Email-to-Case components
D.Chatter feed tracking custom field history only
AnswerC

Case Feed renders chronological touchpoints from Phone, Email, Chat and Messaging into one unified timeline, satisfying the unified-timeline constraint. Omni-Channel routes those interactions to agents while Email-to-Case converts inbound email into cases, so all four channels surface as feed entries in the Service Cloud Console.

Why this answer

Case Feed in the Service Cloud Console provides a unified, chronological timeline that aggregates all interactions — emails, chats, phone calls, messaging sessions, case comments, and field changes — into a single feed on the case record. When integrated with Omni-Channel and Email-to-Case, every touchpoint is automatically captured and displayed in order, giving agents instant visibility into the full customer journey.

Exam trap

Service-Con-201 often tests the difference between related lists and Case Feed — the trap is candidates picking related lists because they show the same data, missing that only Case Feed provides a unified chronological timeline.

How to eliminate wrong answers

Option A is wrong because standard related lists display records in separate tabs or sections, not as a unified chronological timeline — agents would have to switch between lists and manually correlate timestamps. Option B is wrong because Account Hierarchy related lists show parent-child account relationships, not interaction history, and have nothing to do with case timelines. Option D is wrong because Chatter feed tracking on custom fields only surfaces field change history, not the full set of customer interactions across channels.

Full explanation →
231
MCQhard

An organization has complex entitlement rules where response and resolution times vary based on the Account's service level agreement (SLA), the Case Priority, and whether the case occurs during regional holidays. How should the consultant architect the solution?

A.Configure multiple Entitlement Processes linked to Business Hours that account for regional holidays and customer SLAs.
B.Establish separate Case record types for each SLA tier and use workflow rules to update target dates.
C.Use standard Escalation Rules with custom formula fields for holiday calculations.
D.Write an Apex trigger on Case creation to calculate due dates using standard Calendar classes.
AnswerA

Entitlement Processes define the milestones and actions that vary by SLA and priority, while linking them to Business Hours that exclude regional holidays ensures response and resolution times are calculated correctly. This handles the three-variable complexity without custom code.

Why this answer

Configuring multiple Entitlement Processes linked to Business Hours that account for regional holidays and customer SLAs is correct because Entitlement Processes define milestone timelines, and Business Hours define the working hours and holidays used to calculate target dates. This declarative approach handles varying SLAs, priorities, and regional holidays.

Exam trap

Service-Con-201 often tests whether candidates default to custom code (Apex triggers) or workarounds (record types, workflow rules) when standard Entitlement Management with Business Hours fully satisfies complex SLA requirements.

How to eliminate wrong answers

Option B is wrong because separate Case record types with workflow rules to update target dates cannot dynamically calculate due dates based on business hours and holidays — workflow rules lack the time-based calculation engine of Entitlement Processes. Option C is wrong because standard Escalation Rules with custom formula fields for holiday calculations are brittle and do not integrate with Entitlement Milestones for SLA tracking. Option D is wrong because an Apex trigger on Case creation using standard Calendar classes is custom code that duplicates Entitlement Management functionality and is harder to maintain.

Full explanation →
232
MCQmedium

A company wants to provide customers with an automated conversational agent on their website that can handle password resets by integrating with an external identity management system. Which feature should be implemented?

A.Web-to-Case with auto-response rules
B.Einstein Bots with Apex Actions
C.Live Agent chat deployment without a bot
D.Salesforce Knowledge article widgets
AnswerB

Einstein Bots with Apex Actions handle conversational password resets by invoking Apex to call the external identity management system. The Apex action supplies the integration capability the bot alone lacks, satisfying the external system requirement.

Why this answer

Einstein Bots with Apex Actions enables an automated conversational agent on a website that can integrate with external systems. The bot handles the dialogue, and Apex Actions call out to the external identity management system to perform password resets. This combination provides both the conversational interface and the backend integration required.

Exam trap

Service-Con-201 often tests the misconception that Web-to-Case or Knowledge widgets can provide conversational automation, when only Einstein Bots (with Apex Actions for integration) meet the requirement for an automated agent with external system integration.

How to eliminate wrong answers

Option A is wrong because Web-to-Case with auto-response rules creates cases from web forms and sends automated emails; it does not provide a conversational agent or real-time password reset integration. Option C is wrong because Live Agent chat without a bot requires a human agent to handle the conversation, which does not meet the requirement for an automated conversational agent. Option D is wrong because Knowledge article widgets surface help articles on a site; they do not conduct conversations or integrate with external identity systems for password resets.

Full explanation →
233
MCQmedium

A company wants to allow customers to search and view published Knowledge articles without logging into a community. Where should this be deployed?

A.Enterprise LDAP single sign-on portal
B.Salesforce Chatter internal groups
C.Experience Cloud site with public guest user access to Salesforce Knowledge
D.Private internal Service Cloud Console app
AnswerC

An Experience Cloud site with guest user access exposes published Knowledge articles to unauthenticated visitors, satisfying the no-login requirement. Guest user profiles and Knowledge object permissions must allow read access so customers can search and view articles publicly.

Why this answer

An Experience Cloud site (formerly Community) with a public guest user profile can expose published Knowledge articles to unauthenticated visitors. The guest user profile must be granted access to the Knowledge object and the relevant data categories, and the site must be configured to allow public access. This is the standard way to provide public-facing Knowledge without requiring login.

Exam trap

Service-Con-201 often tests the misconception that Chatter, SSO portals, or internal consoles can serve public Knowledge — candidates forget that only Experience Cloud guest user access provides unauthenticated article visibility.

How to eliminate wrong answers

Option A is wrong because an Enterprise LDAP SSO portal requires authentication and is for internal identity federation, not public anonymous access. Option B is wrong because Chatter internal groups are for internal collaboration and are not accessible to unauthenticated customers. Option D is wrong because a private internal Service Cloud Console app is for internal agents and has no public-facing capability.

Full explanation →
234
MCQmedium

Northern Trail Outfitters receives high volumes of routine inquiries regarding order status. The company wants to deploy a self-service community that automatically authenticates customers and displays their recent orders using standard components. Which architecture best meets this requirement?

A.Einstein Bot embedded on an external website using canvas apps
B.Salesforce Experience Cloud with standard Order History components and Salesforce Identity
C.Salesforce Sites with unauthenticated Visualforce pages displaying order details
D.Custom Heroku application integrated via REST API with a third-party portal framework
AnswerB

Experience Cloud provides the self-service community, standard Order History components surface recent orders without custom code, and Salesforce Identity handles automatic authentication of customers. This combination satisfies the low-effort, standard-component constraint for displaying order status.

Why this answer

Salesforce Experience Cloud (formerly Community Cloud) with standard Order History components and Salesforce Identity provides authenticated self-service access to order data. Salesforce Identity handles authentication (including SSO and social login), while standard Order History components display recent orders without custom development. This architecture meets the requirement for automatic authentication and standard components for order display.

Exam trap

Service-Con-201 often tests whether candidates recognize that standard Experience Cloud components plus Salesforce Identity satisfy authenticated self-service requirements, while custom or unauthenticated solutions introduce security or complexity trade-offs.

How to eliminate wrong answers

Option A is wrong because Einstein Bot embedded via canvas apps on an external website does not provide authenticated access to order history; bots are conversational interfaces and canvas apps are for embedding external apps, not for standard order display. Option C is wrong because Salesforce Sites with unauthenticated Visualforce pages would expose order details without authentication, violating the requirement for automatic authentication and creating a security risk. Option D is wrong because a custom Heroku application with a third-party portal framework requires significant custom development and does not leverage standard Salesforce components, increasing complexity and maintenance overhead.

Full explanation →
235
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.

Full explanation →
236
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.

Full explanation →
237
MCQhard

An organization is designing a high-throughput customer service operation where agents handle multiple concurrent chat and messaging sessions. To prevent agent burnout, management wants system-enforced limits on simultaneous active chats based on agent skill tiers. How should this be configured?

A.Configure Omni-Channel Service Channels with custom Capacity Weights and Routing Configurations per tier.
B.Write an Apex trigger on AgentWork to prevent creation if active counts exceed limits.
C.Set up assignment rules with custom user workload formulas.
D.Use custom profile permissions to restrict chat tab limits in the console.
AnswerA

Omni-Channel capacity weights let each messaging or chat channel consume a defined share of an agent's total capacity, so skill-tier routing configurations enforce hard concurrency ceilings per tier. This directly satisfies the requirement for system-enforced limits on simultaneous active chats, rather than relying on manual supervision or agent self-regulation.

Why this answer

Omni-Channel Service Channels support Capacity Weights and Routing Configurations that let you assign different capacity costs per work item and route based on agent skill tiers, enforcing system-level limits on concurrent chats. This is the declarative, supported mechanism for capping simultaneous sessions per agent tier.

Exam trap

Service-Con-201 often tests whether candidates reach for custom Apex or profile settings to limit concurrent chats instead of the native Omni-Channel Capacity Weight and Routing Configuration controls.

How to eliminate wrong answers

Option B is wrong because an Apex trigger on AgentWork to block work creation is a fragile custom workaround that fights the routing engine rather than using supported capacity controls, and it risks orphaned work items. Option C is wrong because assignment rules and workload formulas apply to case/lead assignment, not to Omni-Channel concurrent chat capacity. Option D is wrong because profile permissions and console tab limits do not enforce simultaneous active chat counts — they only control UI access.

Full explanation →
238
MCQeasy

A support supervisor wants to view the current status, workload, and active Omni-Channel queues of all agents in a single real-time console view. Which tool should the supervisor use?

A.Service Cloud console workspace tabs
B.Standard Salesforce Dashboards refreshed hourly
C.Chatter analytics reports
D.Omni-Channel Supervisor
AnswerD

Omni-Channel Supervisor provides a real-time console showing agent status, capacity usage and active queue assignments across the service channel, satisfying the supervisor's need for one consolidated live view. Unlike historical reports, it streams current workload data, so supervisors can monitor and intervene as situations develop.

Why this answer

Omni-Channel Supervisor is a real-time console that provides supervisors with a unified view of agent status, workload, and active Omni-Channel queues. It allows supervisors to monitor agent capacity, reassign work, and view queue metrics in real time. This tool is specifically designed for supervisory oversight of Omni-Channel routing.

Exam trap

Service-Con-201 often tests the difference between real-time monitoring tools and historical reporting, causing candidates to choose dashboards or reports instead of Omni-Channel Supervisor.

How to eliminate wrong answers

Option A is wrong because Service Cloud console workspace tabs are for individual agent work, not for real-time supervisory monitoring of all agents. Option B is wrong because standard Salesforce Dashboards refreshed hourly provide historical data, not real-time status and workload. Option C is wrong because Chatter analytics reports are for collaboration analytics, not real-time Omni-Channel queue monitoring.

Full explanation →
239
MCQmedium

A company wants agents to follow a consistent 5-step checklist every time a high-severity case is opened. The steps must be visually tracked on the record page. Which feature should the consultant implement?

A.Custom HTML web tabs embedded in utility bars
B.Entitlement processes with milestone steps
C.Chatter polls assigned to case teams
D.Path (Guidance for Success) configured on the Case object
AnswerD

Path renders a guided checklist of stages directly on the Case record page, giving agents visual tracking of the five required steps for high-severity cases, which is exactly the consistent, on-record guidance the company needs.

Why this answer

Path (Guidance for Success) is a feature that provides a visual, step-by-step guide on a record page. It allows the consultant to configure a 5-step checklist for high-severity cases, with each step representing a key stage. The path appears at the top of the record page, and agents can click each step to update the record and track progress.

This meets the requirement for visual tracking of a consistent checklist.

Exam trap

Service-Con-201 often tests the difference between process guidance tools and automation, causing candidates to choose entitlement processes or macros instead of Path for visual step tracking.

How to eliminate wrong answers

Option A is wrong because Custom HTML web tabs embedded in utility bars are for displaying external web content, not for guiding users through a checklist on a record page. Option B is wrong because Entitlement processes with milestone steps are for tracking service level agreements and entitlements, not for a visual checklist on a case record. Option C is wrong because Chatter polls are for gathering opinions, not for guiding a process or tracking steps.

Full explanation →
240
MCQeasy

Which tool in the Lightning Service Console allows supervisors to monitor agent workloads, queue backlogs, and real-time operational metrics?

A.Lightning Usage App
B.Omni-Channel Supervisor
C.Service Analytics App
D.Console Performance Dashboard
AnswerB

Omni-Channel Supervisor provides supervisors with real-time dashboards covering agent capacity, queue backlogs and operational metrics directly within the Lightning Service Console, satisfying the monitoring requirement. Unlike standard Omni-Channel routing, which only assigns work, Supervisor exposes live workload visibility, letting supervisors monitor and intervene as the stem demands.

Why this answer

Omni-Channel Supervisor is the real-time monitoring tool built into the Lightning Service Console that gives supervisors visibility into agent presence, capacity, active work, and queue backlogs. It is purpose-built for live operational metrics and workload balancing.

Exam trap

Service-Con-201 often tests the distinction between real-time monitoring (Omni-Channel Supervisor) and historical reporting (Service Analytics, Lightning Usage App) — candidates pick the analytics tool when the question asks for live supervisor visibility.

How to eliminate wrong answers

Option A is wrong because the Lightning Usage App reports adoption and usage metrics (logins, page views) over time, not real-time agent workload. Option C is wrong because Service Analytics App provides historical reporting and dashboards on service KPIs, not live supervisor monitoring. Option D is wrong because 'Console Performance Dashboard' is not a standard Salesforce tool — it is a fabricated distractor.

Full explanation →
241
MCQhard

An enterprise service desk receives high volumes of emails that frequently contain malicious attachments or executable files. The security team mandates that inbound email attachments must be scanned and stripped before being saved to Salesforce cases. Which architectural approach satisfies this requirement?

A.Create a validation rule on the Attachment object checking file extensions.
B.Implement an enterprise email security gateway before Email-to-Case, or use Apex Email Services to intercept and cleanse attachments.
C.Disable attachments globally on Email-to-Case and require customers to upload via Experience Cloud.
D.Rely on standard Salesforce File security and antivirus settings in Setup.
AnswerB

An email security gateway before Email-to-Case, or Apex Email Services intercepting messages, scans and strips attachments before cases are created. This satisfies the mandate that inbound attachments be cleansed prior to being saved to Salesforce cases, rather than after.

Why this answer

Email-to-Case does not natively scan or strip attachments before they are saved to Salesforce cases, so the security requirement must be met upstream. An enterprise email security gateway (e.g., Proofpoint, Mimecast, Barracuda) can inspect and sanitize inbound messages before they reach Salesforce's Email-to-Case endpoint, or Apex Email Services can be used to intercept inbound email, programmatically strip or quarantine attachments, and then create cases via the API. Both approaches satisfy the mandate because they act before the attachment is persisted to Salesforce.

Exam trap

Service-Con-201 often tests the misconception that Salesforce natively scans and strips email attachments, when in fact attachment security must be enforced upstream or via custom Apex Email Services.

How to eliminate wrong answers

Option A is wrong because a validation rule on the Attachment object can only block records based on field values after the attachment has already been uploaded — it cannot scan file contents for malware, and it does not prevent the file from being transmitted to Salesforce in the first place. Option C is wrong because disabling attachments on Email-to-Case and forcing Experience Cloud uploads does not scan or strip malicious files; it merely shifts the attack surface to a different channel and degrades the customer experience. Option D is wrong because Salesforce's standard File security and antivirus settings provide platform-level malware scanning for Files but do not strip attachments from inbound email before case creation, nor do they satisfy a mandate to remove executables prior to persistence.

Full explanation →
242
Multi-Selecthard

An administrator is configuring console tab limits and warning behaviors in App Manager. Which THREE behaviors occur when an agent reaches the maximum workspace tab limit? (Choose three.)

Select 3 answers
A.Salesforce automatically logs the user out of the console session.
B.Agents receive a warning notification when approaching the configured tab limit.
C.Pinned workspace tabs are protected from automatic closure when the limit is reached.
D.The oldest unpinned workspace tab may be automatically closed when a new tab is opened.
E.All open subtabs are permanently deleted from the database.
AnswersB, C, D

App Manager issues a warning notification as an agent's open workspace tabs approach the configured maximum, giving them the chance to close tabs before hitting the hard limit. This satisfies the stem's requirement for warning behaviours tied to console tab limits.

Why this answer

Option B is correct because App Manager's console tab limit settings include a warning threshold that notifies agents as they approach the configured maximum number of workspace tabs. Option C is correct because pinned tabs are exempt from the automatic tab-closing behavior, ensuring agents retain tabs they have deliberately pinned. Option D is correct because when the limit is reached and a new tab is opened, the system closes the oldest unpinned workspace tab to make room.

Option A is incorrect because reaching the tab limit does not terminate the user's session; it only manages tab count. Option E is incorrect because closing a tab is a UI action and does not delete subtab records from the database.

Exam trap

Service-Con-201 often tests the specific behaviors of tab limits — candidates incorrectly assume tabs are deleted from the database or that users are logged out, when in fact only the workspace tab is closed and pinned tabs are protected.

Full explanation →
243
MCQhard

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?

A.Cases created outside business hours immediately trigger escalation actions upon creation.
B.The escalation rule will throw a system exception due to timezone mismatch.
C.Escalation rules ignore business hours entirely and always use 24/7 calendar time.
D.The escalation timer will only increment during the defined business hours associated with the case.
AnswerD

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.

Why this answer

Escalation rules calculate business hours based on the business hours specified on the case (either from the account, contact, or default). If set to use specific business hours, the timer only ticks during those active business hours.

Full explanation →
244
MCQmedium

Universal Containers wants to ensure that support cases follow different SLAs depending on whether the customer purchased a Gold, Silver, or Bronze support package. How should the consultant structure the Entitlement Processes?

A.Create separate Entitlement Processes for Gold, Silver, and Bronze, and associate them with corresponding Entitlements.
B.Create a single Entitlement Process and use assignment rules to change the SLA timers dynamically.
C.Configure multi-currency settings to scale the SLA target times.
D.Use workflow rules to update the milestone target time based on the customer tier.
AnswerA

Entitlement Processes define milestone timelines, so each support tier needs its own process with distinct targets. Associating each process with the matching Gold, Silver, or Bronze Entitlement ensures the correct SLA milestones apply to that customer's cases.

Why this answer

Different service tiers require distinct timeframes, actions, and milestones, which are best managed by creating separate Entitlement Processes for each tier.

Full explanation →
245
MCQhard

An enterprise service desk has strict compliance requirements. Case records containing Personally Identifiable Information (PII) must be encrypted at rest with keys managed exclusively by the customer. Which Salesforce feature satisfies this requirement?

A.Standard field-level security profile restrictions
B.Classic encrypted text custom fields using Salesforce-managed keys
C.Secure Server-Side HTTPS transport layer encryption
D.Salesforce Shield Platform Encryption with BYOK
AnswerD

Platform Encryption with BYOK (Bring Your Own Key) lets the customer supply and control the tenant secret via a Hardware Security Module, so Salesforce cannot decrypt PII at rest. This directly satisfies the stem's requirement that encryption keys be managed exclusively by the customer.

Why this answer

Salesforce Shield Platform Encryption with Bring Your Own Key (BYOK) allows organizations to manage their own tenant secret encryption keys securely.

Full explanation →
246
MCQeasy

A service team uses Knowledge articles extensively. Agents need to search articles using natural language queries and receive relevant results ranked by user engagement and text match. Which search feature should be leveraged?

A.Standard list view filters on the Case object
B.Custom SOQL queries with LIKE operators in a Visualforce page
C.Salesforce Knowledge Search with relevance ranking
D.Global search with object filters set to Contacts
AnswerC

Salesforce Knowledge Search applies relevance ranking that blends text match with user engagement signals such as views and ratings, returning the most useful articles for natural language queries. Basic keyword search lacks this engagement-weighted ordering, so it cannot satisfy the ranking requirement.

Why this answer

Salesforce Knowledge Search uses a relevance-ranked search engine that scores articles by text match and user engagement signals (views, likes, case usage), which is exactly what agents need for natural-language queries. It is purpose-built for Knowledge and returns the most relevant articles first.

Exam trap

Service-Con-201 often tests whether candidates confuse object-level list views or SOQL LIKE queries with the dedicated Knowledge Search relevance engine that ranks by text match and engagement.

How to eliminate wrong answers

Option A is wrong because list view filters on Case only filter case records, not Knowledge articles, and provide no relevance ranking. Option B is wrong because custom SOQL with LIKE operators does simple substring matching with no ranking, stemming, or engagement weighting, and requires custom code. Option D is wrong because global search with a Contacts filter searches contacts, not Knowledge articles, and does not apply Knowledge relevance ranking.

Full explanation →
247
MCQmedium

A service team receives customer emails that frequently reference existing cases. The organization wants incoming emails to automatically attach to the correct open case rather than creating duplicate cases. How should this be configured?

A.Use Macros to merge duplicate cases after creation.
B.Set up Apex email services with custom regex parsing for case numbers.
C.Rely solely on standard Assignment Rules to reassign emails.
D.Configure Email-to-Case threading settings to match inbound emails using subject line tokens and headers.
AnswerD

Email-to-Case threading matches inbound messages to existing cases using subject tokens and the case thread ID header, so replies attach to the open case instead of spawning duplicates. This satisfies the requirement that referenced emails route to the correct case automatically.

Why this answer

Email-to-Case threading uses tokens in the subject line and email headers to match inbound emails to existing cases. By configuring threading settings, the system can automatically associate replies with the correct case, preventing duplicates. This is the standard functionality for email case threading.

Exam trap

Service-Con-201 often tests the confusion between assignment rules and threading; candidates may think assignment rules can match emails to existing cases, but they only assign new cases.

How to eliminate wrong answers

Option A is wrong because Macros are for automating actions after case creation, not for preventing duplicates. Option B is wrong because Apex email services are custom and not the standard threading mechanism; they would require custom development. Option C is wrong because Assignment Rules only assign cases to users or queues; they do not match emails to existing cases.

Full explanation →
248
MCQeasy

A support agent wants to create a related task to follow up with a customer next Tuesday directly from the open case record. Which feature should they use?

A.Activity Timeline component on the Case Record Page
B.Entitlement milestone checklist
C.Global Action menu in the navigation bar
D.Case Comments related list
AnswerA

The Activity Timeline component on the Case Record Page lets agents create tasks, events, and logged calls directly against the case, with due dates such as next Tuesday. This satisfies the requirement to create a follow-up task from the open case record without navigating elsewhere.

Why this answer

The Activity Timeline component on the Case Record Page allows agents to view and create tasks, events, and logged calls directly from the case record. Creating a follow-up task for next Tuesday is a standard activity management action available through this component.

Exam trap

Service-Con-201 often tests whether candidates confuse activity management (Activity Timeline) with case commenting or global actions — the trap is picking a feature that creates a record but doesn't link it to the case or provide the same contextual efficiency.

How to eliminate wrong answers

Option B is wrong because an Entitlement milestone checklist tracks SLA milestones, not ad-hoc follow-up tasks. Option C is wrong because the Global Action menu creates records not necessarily related to the open case, and it's less efficient than using the case's activity timeline. Option D is wrong because Case Comments are text notes on the case, not tasks with due dates.

Full explanation →
249
MCQhard

A service manager needs to ensure that when a Case is closed, a summary record is sent to an external data warehouse. The warehouse exposes a REST API that accepts JSON payloads. The integration must be reliable and must not block the user from closing the Case. Which approach should the consultant use?

A.Write an Apex trigger on Case that performs a synchronous callout to the warehouse API in an after update context.
B.Create a Process Builder that makes an HTTP callout to the warehouse API when the Case status changes to Closed.
C.Publish a Platform Event when the Case is closed and have an Apex subscriber make an asynchronous callout to the warehouse API.
D.Use an Outbound Message on the Case object to send the summary to the warehouse API.
AnswerC

Platform Events enable asynchronous, reliable communication. Publishing an event when a Case is closed decouples the user transaction from the callout. An Apex subscriber processes the event and makes the REST callout asynchronously, so the user is not blocked. This pattern also supports retries and error handling, meeting the reliability requirement.

Why this answer

The requirement for non-blocking, reliable integration with a REST API is best met by using Platform Events. Publishing an event on Case closure triggers an asynchronous subscriber that performs the callout. This avoids blocking the user and allows for robust error handling.

Synchronous callouts and Outbound Messages do not fit due to blocking or protocol mismatch.

Exam trap

The trap here is assuming that any asynchronous mechanism like Outbound Messages can send JSON to a REST API, when in fact Outbound Messages use SOAP and cannot natively produce JSON payloads.

Full explanation →
250
MCQmedium

Universal Containers wants to integrate Service Cloud with an external knowledge base. When an agent views a Case, relevant knowledge articles from the external system should appear in a sidebar without being stored in Salesforce. Which feature should the consultant use?

A.Einstein Article Recommendations with external data sources.
B.Apex callouts triggered by a Process Builder to fetch articles and display them in a custom component.
C.Salesforce Knowledge with article syndication to the external system.
D.Salesforce Connect with a custom adapter to create an external object for knowledge articles.
AnswerD

Salesforce Connect allows real-time access to external data via external objects. A custom adapter can connect to the external knowledge base's API. The external articles can then be displayed in a related list or custom Lightning component on the Case page without being stored in Salesforce. This meets the requirement.

Why this answer

Salesforce Connect is designed to surface external data in real time without storing it in Salesforce. By creating an external object with a custom adapter for the external knowledge base, articles can be displayed on the Case page. This satisfies the no-storage and real-time requirements.

Exam trap

The trap here is assuming that Salesforce Knowledge can be used to display external articles, but Knowledge stores articles internally and does not natively pull from external sources.

Full explanation →
Page 3

Page 4 of 4

All pages

1234

Practice Service-Con-201 by domain

Target a specific domain to shore up weak areas.

Integration And Data ManagementCase ManagementService Cloud Solution DesignKnowledge ManagementOmni ChannelEntitlement ManagementService Console
See all domains with question counts →