Service-Con-201 Practice Test 5 — 25 Questions

Question 1

Which TWO benefits does Split View offer to agents in the Lightning Service Console? (Choose two.)

Accepted Answer

Allows quick navigation between records without losing list context.. Split View in the Lightning Service Console is designed to keep a list view visible on one side of the screen while an agent opens and works on individual records on the other side. Option A is correct because this layout lets agents move quickly from record to record while the originating list remains in context, so they never lose their place in the queue. Option E is correct because the defining behavior of Split View is exactly that persistent list view that stays on screen as records are opened and worked. Options B, C, and D are incorrect because automated satisfaction surveys, duplicate case deletion, and real-time chat translation are unrelated capabilities not provided by Split View.

Answer

Sends automated customer satisfaction surveys.

Answer

Automatically deletes duplicate case records.

Answer

Translates incoming customer chat messages in real time.

Question 2

A support manager wants to view a real-time list of all cases currently sitting in the 'Tier 1 Support' queue. Where should the manager look?

Accepted Answer

Cases tab -> Select the 'Tier 1 Support' list view or Queue view. The Cases tab provides list views, including queue views, that show real-time case records. By selecting the 'Tier 1 Support' queue view (or a list view filtered by the queue), the manager sees all cases currently owned by that queue. Queue views are dynamic and reflect the current state of cases without delay.

Answer

Forecasts tab -> Queue Summary

Answer

Dashboards -> Chatter Feed

Answer

Reports tab -> Case Escalation History report

Question 3

An organization requires high availability and disaster recovery planning for their mission-critical Service Cloud implementation. Which THREE architectural practices should the consultant recommend? (Choose three.)

Accepted Answer

Design robust API rate-limiting and error-handling strategies for external integrations. Option A is correct because robust API rate-limiting and error-handling strategies (e.g., respecting Salesforce API request limits, implementing retry with exponential backoff, and using Platform Events or middleware queues) prevent external integrations from failing or cascading during peak loads or partial outages, which is essential for a mission-critical Service Cloud implementation. Option C is correct because rigorous sandbox testing (Developer, Full, or Partial Copy sandboxes) combined with CI/CD pipelines (e.g., Salesforce DX, Git-based deployment, and automated Apex/declarative tests) reduces the risk of defective releases that could cause downtime and ensures changes are validated before production deployment. Option D is correct because automated weekly/monthly data exports via Data Export Service or Data Loader, plus Salesforce Backup and Restore (or a third-party backup solution), provide point-in-time recovery and protect against data loss or corruption, directly supporting disaster recovery objectives. Option B is incorrect because disabling profile security settings to grant universal admin access would violate least-privilege and security best practices, creating a severe vulnerability rather than improving availability. Option E is incorrect because local browser caches are transient, client-side, and not a reliable or permanent disaster recovery storage mechanism; they cannot restore Salesforce data or configuration after an outage.

Answer

Disable all profile security settings to allow universal admin access during outages

Answer

Rely entirely on local browser caches for permanent disaster recovery storage

Question 4

Universal Containers wants to route VIP customer cases to agents who speak French and have advanced tier certifications. How should the administrator configure this requirement?

Accepted Answer

Skills-Based Routing with rules or an Omni-Channel Flow assigning multiple skills.. Skills-Based Routing allows an admin to define skills such as language and certification tier, then route cases to agents who possess the required combination. An Omni-Channel Flow or routing rule can require multiple skills simultaneously, ensuring VIP French-speaking certified agents receive the case. This is the standard, scalable way to meet multi-attribute routing requirements.

Answer

Status-Based capacity rules.

Answer

Queue-based routing with separate queues for every language and tier combination.

Answer

Routing Configurations with priority weighting.

Question 5

An administrator has created a macro that fails when executed by agents on Case records. The macro attempts to populate a custom field on the Case object, but the field is not available in the macro instruction builder. What is the most likely cause?

Accepted Answer

The field lacks Read/Write field-level security for the running user or is not on the page layout used by the console.. Macros run as the executing user and only expose fields the user can read/write via field-level security and that are present on the page layout used by the console. If the custom field is missing from the macro instruction builder, the most likely cause is FLS restriction for the running user or the field not being on the console page layout. Fixing FLS or adding the field to the layout restores it in the builder.

Answer

The macro must be converted to a Lightning Web Component before custom fields can be referenced.

Answer

Macros only support standard Salesforce fields and reject all custom fields.

Answer

The console app has reached its maximum limit of custom field macro mappings.

Question 6

An enterprise service center is designing a multi-channel support strategy incorporating Email-to-Case, Messaging for In-App and Web, and Voice. Which THREE architectural best practices should the consultant recommend for scalability and maintainability? (Choose three.)

Accepted Answer

Implement unified Omni-Channel presence and routing across all communication channels. Option A is correct because unified Omni-Channel presence and routing lets the service center manage agent capacity, skills, and work distribution consistently across Email-to-Case, Messaging for In-App and Web, and Voice, which is essential for scalability and maintainability in a multi-channel strategy. Option C is correct because Record-Triggered Flows are the current declarative automation standard for routing logic, replacing legacy Workflow Rules and reducing complex Apex trigger maintenance, making routing easier to scale and support. Option D is correct because a dedicated Service Console app with channel-specific utility items and record pages gives agents the right tools and layouts per channel, improving maintainability and user efficiency across Email, Messaging, and Voice. Option B is not appropriate because hardcoding agent queue assignments in Apex is brittle, hard to maintain, and bypasses declarative routing and Omni-Channel configuration. Option E is not appropriate because storing all historical case attachments in custom rich text fields on the Account object is a poor data model, ignores standard attachment/File storage, and does not support scalability or maintainability.

Answer

Hardcode individual agent queue assignments directly in Apex classes for maximum performance

Answer

Store all historical case attachments in custom rich text fields on the Account object

Question 7

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

Accepted Answer

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

Answer

Google Analytics integration setup logs.

Answer

Case Comment History related list.

Answer

Chatter feed analytics on the article record.

Question 8

A company plans to launch a multilingual customer support portal in English, Spanish, and French. They want agents to author and translate help articles efficiently while maintaining a single article ID. Which Knowledge feature supports this?

Accepted Answer

Enable Salesforce Knowledge Multi-Language with translated article versions tied to a master article.. Salesforce Knowledge Multi-Language is the native feature that lets you maintain one master article with a single article ID and create translated versions for each supported language. Agents author in their own language, and the translated versions stay linked to the master, so the article ID remains consistent across English, Spanish, and French. This is exactly the requirement described.

Answer

Use custom translation fields on a single article layout with language-specific validation rules.

Answer

Create separate Knowledge object instances for each language using custom record types.

Answer

Deploy separate Experience Cloud sites for each language pointing to distinct categories.

Question 9

What is the primary benefit of using Split View in the Lightning Service Console?

Accepted Answer

It allows agents to browse list views without leaving their active workspace tabs.. Split View in the Lightning Service Console allows agents to view a list view alongside a record detail page within the same tab, so they can browse list views without leaving their active workspace. This is the primary benefit: it enables agents to work with lists and records simultaneously, improving productivity. It does not relate to utility bar components, AI case resolution, or phone call splitting.

Answer

It displays multiple utility bar components at the same time.

Answer

It automatically resolves cases using Einstein AI.

Answer

It splits incoming phone calls between two agents simultaneously.

Question 10

An agent is working on a Case workspace tab and wants to pin the tab so that it cannot be accidentally closed when reaching the maximum tab limit. How can the agent achieve this?

Accepted Answer

Right-click the workspace tab and select Pin Tab. In Salesforce Service Cloud, agents can pin a workspace tab to prevent it from being closed when the maximum tab limit is reached. Right-clicking the tab and selecting 'Pin Tab' locks it in place, ensuring it stays open regardless of how many other tabs are opened. This is a standard feature of the Service Console and is the direct method to achieve the requirement.

Answer

Add the tab to the utility bar

Answer

Click the lock icon in the global header

Answer

Configure the tab behavior in User Settings

Question 11

Universal Containers wants to implement Salesforce Knowledge to improve agent efficiency and customer self-service. Which TWO key design considerations should the consultant address during the solution design phase? (Choose two.)

Accepted Answer

Article lifecycle management, review cycles, and publication permissions. Option C is correct because Salesforce Knowledge requires a defined article lifecycle with states such as Draft, In Review, Published, and Archived, along with scheduled review cycles and publication permissions, to keep content accurate and govern who can publish. Option E is correct because data categories form the architecture that controls article visibility to internal users, partner users, and public/guest users, so mapping categories to profiles, roles, and channels must be designed up front. Option A is not required because historical case attachments are not automatically articles and migrating them is an optional data-migration decision, not a core Knowledge design consideration. Option B is incorrect because Omni-Channel capacity weights apply to work items such as cases, leads, and chats, not to reading Knowledge articles. Option D is incorrect because replacing all email templates with static Knowledge URLs is neither required nor advisable, since templates and dynamic article links serve different purposes.

Answer

Migrating all historical closed case attachments into article attachments

Answer

Configuring Omni-Channel capacity weights for article reading

Answer

Replacing all email communication templates with static knowledge URLs

Question 12

Universal Containers has a complex data model where Case ownership frequently shifts between regional queues and individual agents. To audit historical ownership changes for compliance reporting, which data management feature should be leveraged?

Accepted Answer

Case History tracking. Case History related lists track standard field changes including Owner, Status, and Priority automatically.

Answer

Chatter Feed tracking on Owner changes

Answer

Outbound messaging on every field update

Answer

Custom Big Object logging via Apex triggers

Question 13

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?

Accepted Answer

Configure Omni-Channel Service Channels with custom Capacity Weights and Routing Configurations per tier.. 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.

Answer

Write an Apex trigger on AgentWork to prevent creation if active counts exceed limits.

Answer

Set up assignment rules with custom user workload formulas.

Answer

Use custom profile permissions to restrict chat tab limits in the console.

Question 14

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?

Accepted Answer

Salesforce Connect with a custom adapter to create an external object for knowledge articles.. 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.

Answer

Einstein Article Recommendations with external data sources.

Answer

Apex callouts triggered by a Process Builder to fetch articles and display them in a custom component.

Answer

Salesforce Knowledge with article syndication to the external system.

Question 15

An enterprise customer service desk requires high-volume data integration from an external legacy ticket system. Which THREE considerations are vital when using the Salesforce Bulk API? (Choose three.)

Accepted Answer

External ID fields must be specified when performing upsert operations.. Option C is correct because Bulk API upsert operations require an External ID field to match incoming records against existing Salesforce records, since the legacy ticket system's identifiers are not Salesforce record IDs. Option D is correct because Bulk API is designed for asynchronous, batch-based processing, splitting jobs into batches that are queued and processed in the background, which is what enables handling of millions of records without hitting synchronous API limits. Option E is correct because Bulk API supports both CSV and JSON payload formats for job data, with CSV being the traditional format and JSON supported in Bulk API 2.0. Option A is not correct because Bulk API is asynchronous and not intended for real-time synchronous UI updates such as agent screen pops; those would use Streaming API, Platform Events, or a synchronous API. Option B is not correct because Bulk API does not automatically bypass Apex triggers or validation rules; those still execute unless explicitly disabled or unless the operation uses a mechanism that skips them, so this blanket statement is false.

Answer

Bulk API supports real-time synchronous UI updates for agent screen pops.

Answer

Bulk API jobs bypass all Apex triggers and validation rules automatically.

Question 16

Universal Containers runs Omni-Channel with a single queue for all support cases. Managers report that high-priority cases sit behind low-priority password-reset cases in the same queue, so urgent work is not handled first. The administrator must ensure that within the same queue, cases with Priority = High are offered to agents before cases with Priority = Low. What should the administrator configure?

Accepted Answer

Create a Queue Routing Configuration with Priority set to the Case Priority field and assign it to the queue.. Queue Routing Configurations let an administrator override routing settings at the queue level, and they include a Priority field that determines the order in which work items are offered to agents. Pointing that priority at the Case Priority field makes High-priority cases surface before Low-priority cases within the same queue, which is precisely what managers are asking for.

Answer

Set the queue's Routing Configuration to Most Available and enable Presence Status-based capacity.

Answer

Enable Omni-Channel Skills-Based Routing and create skills for High and Low priority cases.

Answer

Configure a Work Item Size on the Case object so high-priority cases have a larger size value.

Question 17

Universal Containers utilizes both Queue-Based and Skills-Based Routing. Which TWO statements are true regarding how Omni-Channel handles these two routing methods? (Choose two.)

Accepted Answer

Skills-Based Routing matches required skill sets on work items to agent skill profiles.. Option C is correct because Skills-Based Routing works by defining required skills on the work item (such as a Case or Lead) and matching them against the skills configured in each agent's skill profile, so Omni-Channel can route the work to agents who possess the needed competencies. Option E is correct because Queue-Based Routing relies on Salesforce queues: work items are routed to the queue, and Omni-Channel delivers that work to agents who are members of that specific queue. Option A is incorrect because Queue-Based Routing can absolutely be combined with Omni-Channel flows; flows are commonly used to set up routing configurations, including queue-based ones. Option B is incorrect because Skills-Based Routing does not require agents to belong to every queue; it uses skill profiles rather than queue membership to determine routing. Option D is incorrect because service channels are still required in Omni-Channel to define how different types of work (cases, chats, leads, etc.) are routed, regardless of whether skills-based or queue-based routing is used.

Answer

Queue-Based Routing cannot be used in conjunction with Omni-Channel flows.

Answer

Skills-Based Routing requires agents to be members of every queue in the organization.

Answer

Skills-Based Routing eliminates the need for service channels.

Question 18

A support supervisor notes that when a case milestone violates, an email alert should be sent to the case owner, and the case priority should be automatically escalated to High. Which feature allows this combination of actions when a milestone is violated?

Accepted Answer

Milestone Violation Actions configured within the Entitlement Process.. Milestone Violation Actions are a native configuration within the Entitlement Process that let you define what happens when a milestone's target time is breached. You can configure them to send an email alert to the case owner and simultaneously update the case priority to High, all without code. This is the only declarative feature in the list that directly binds actions to a milestone violation event.

Answer

Entitlement Template automation rules.

Answer

Case Assignment Rules triggered upon milestone violation.

Answer

Apex Triggers listening to Case Milestone status changes.

Question 19

An enterprise customer service department has multiple business units sharing a single Salesforce org. Each business unit has distinct service workflows, unique case fields, and separate escalation rules. Which THREE features should the consultant use to segregate and manage these business units effectively? (Choose three.)

Accepted Answer

Sharing Rules and Role Hierarchies to ensure data security and visibility boundaries. Option C is correct because Sharing Rules and Role Hierarchies are the standard Salesforce mechanisms for enforcing record-level visibility boundaries, letting each business unit see only its own cases while still allowing controlled cross-unit access where needed. Option D is correct because Page Layout Assignment (via profiles or permission sets) controls which fields and sections each business unit's users see, satisfying the requirement for unique case fields without building separate objects. Option E is correct because Case Record Types let you define distinct business processes, picklist values, and page layout assignments per business unit, which is exactly how you model separate service workflows and escalation rules in one org. Option A is wrong because disabling sharing rules would expose all cases globally, destroying the required segregation and violating data security. Option B is wrong because hardcoding all validation logic into one global Apex trigger creates a monolithic, hard-to-maintain design and does not provide any segregation of workflows, fields, or visibility.

Answer

Disabling all sharing model rules to make every case visible to all users globally

Answer

Hardcoding all business unit validation checks into a single global Apex trigger

Question 20

An enterprise service organization uses Omni-Channel. During peak holiday hours, inbound chat volume exceeds agent capacity. Management wants overflow chats to be automatically routed to a secondary external partner organization's Salesforce org. How should this architecture be designed?

Accepted Answer

Architect a cross-org integration using Omni-Channel API and Salesforce-to-Salesforce or REST APIs. Omni-Channel API combined with Salesforce-to-Salesforce or cross-org REST integrations allows routing overflow work across org boundaries.

Answer

Configure standard queue overflow rules to external email addresses

Answer

Deploy an unauthenticated Web-to-Case form on the external partner's website

Answer

Use standard assignment rules with external IP endpoints