Courseiva

CCNA Service Console Questions

24 questions · Service Console · All types, answers revealed

Practice these questionsDomain overviewAll questions
1
MCQeasy

Which navigation style is foundational to the Lightning Service Console and allows users to open multiple records and their related items in tabs?

A.Standard Navigation
B.Console Navigation
C.Visualforce Navigation
D.Utility Navigation
AnswerB

Console navigation is the foundational style for the Lightning Service Console, letting agents open multiple records and related items simultaneously in tabs. This satisfies the stem's requirement for a navigation model built around multitasking across records, unlike standard app navigation, which shows one record at a time.

Why this answer

Console Navigation is the navigation style specifically designed for the Lightning Service Console, enabling users to open multiple records and their related items in tabs within a single workspace. It provides a tabbed interface that allows agents to work on several cases simultaneously without losing context. Standard Navigation, by contrast, is used for standard Lightning apps and does not support the multi-tab console experience.

Exam trap

Service-Con-201 often tests the distinction between Console Navigation and Standard Navigation, and candidates may confuse Utility Navigation (the utility bar) with the primary navigation style.

How to eliminate wrong answers

Option A is wrong because Standard Navigation is the default navigation for standard Lightning apps and does not provide the multi-tab, console-style workspace required for the Service Console. Option C is wrong because Visualforce Navigation is not a navigation style; Visualforce pages can be embedded but do not define the console navigation model. Option D is wrong because Utility Navigation refers to the utility bar at the bottom of the console, which provides quick access to tools, not the primary tabbed navigation for records.

Practice this question →
2
MCQhard

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?

A.The macro must be converted to a Lightning Web Component before custom fields can be referenced.
B.Macros only support standard Salesforce fields and reject all custom fields.
C.The field lacks Read/Write field-level security for the running user or is not on the page layout used by the console.
D.The console app has reached its maximum limit of custom field macro mappings.
AnswerC

Macro instruction builder only exposes fields the running user can read and edit and that appear on the record page layout. Missing field-level security or page layout placement hides the custom field, matching the stem's symptom.

Why this answer

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.

Exam trap

Service-Con-201 often tests the FLS/page-layout trap: candidates blame the macro engine or invent limits, when the real cause is almost always field-level security or the field missing from the console page layout.

How to eliminate wrong answers

Option A is wrong because macros do not require conversion to Lightning Web Components to reference custom fields — custom fields are supported natively subject to FLS and layout. Option B is wrong because macros absolutely support custom fields; the claim that they reject all custom fields is false. Option D is wrong because there is no documented 'maximum limit of custom field macro mappings' per console app; that is an invented constraint.

Practice this question →
3
MCQeasy

When configuring the Lightning Service Console, where does an administrator specify which user profiles have access to the console application?

A.App Manager in Setup
B.User Detail page layout assignment
C.Permission Set License overview
D.Company Settings
AnswerA

App Manager in Setup assigns the console app to selected profiles, satisfying the requirement to specify which profiles can access it. Profile-based app visibility is controlled through the app's assignment, not through permission sets or page layouts, so administrators add profiles directly within App Manager.

Why this answer

Access to a Lightning console app is controlled through the App Manager in Setup, where the administrator edits the app's properties and assigns it to specific profiles via the 'Assign to Profiles' or 'User Profiles' section. This is the standard mechanism for controlling which users see and can open a Lightning app, including console apps. The App Manager centralizes app metadata, navigation items, and profile assignments in one place.

Exam trap

Service-Con-201 often tests the confusion between app assignment (App Manager) and tab visibility (profiles/permission sets) — candidates incorrectly assume that assigning an app to a profile automatically grants access to all its tabs.

How to eliminate wrong answers

Option B is wrong because User Detail page layout assignment controls which page layouts a user sees for a given object, not which Lightning apps they can access. Option C is wrong because Permission Set License overview shows which licenses are available and assigned, but does not govern console app visibility. Option D is wrong because Company Settings contains org-wide defaults like fiscal year, language, and locale — not app access control.

Practice this question →
4
MCQeasy

A Service Cloud Consultant needs to add a custom Lightning component to the bottom footer of the Lightning Service Console. Which console feature accommodates footer items?

A.Utility Bar
B.Sidebar Layout
C.Navigation Bar
D.Highlight Panel
AnswerA

The Utility Bar is the console feature that pins persistent, always-available components to the footer of the Lightning Service Console. It accommodates footer items, letting agents access tools without leaving their current record or tab.

Why this answer

The Utility Bar is the fixed footer area of the Lightning Service Console and is the only console feature designed to host footer items. Custom Lightning components can be added as utility items, making it the correct place to put a component at the bottom of the console.

Exam trap

Service-Con-201 often tests the difference between the Utility Bar (footer) and the Highlight Panel (header) — candidates see 'footer' and 'panel' and pick the wrong console region.

How to eliminate wrong answers

Option B is wrong because the Sidebar Layout controls the left/right sidebar components (such as the customer details or related lists), not the footer. Option C is wrong because the Navigation Bar is the top menu for switching between apps and objects. Option D is wrong because the Highlight Panel is the header area at the top of a record page showing key fields and actions, not a footer.

Practice this question →
5
MCQhard

A consultant is configuring a Lightning Service Console for a team that handles both Cases and Leads. The manager wants agents to be able to open a Lead record from a Case related list and have it appear as a subtab, while keeping the Case as the primary tab. The consultant has already added the Leads related list to the Case page layout. What should the consultant do next to ensure the Lead opens as a subtab?

A.Configure the Leads related list component to open records in a new browser window.
B.Create a navigation rule for the Lead object in the Lightning Console app that opens records as a subtab.
C.Enable "Split View" on the Case page and add the Leads related list to the secondary pane.
D.Add the Lead object to the console's Utility Bar and set it to open as a subtab.
AnswerB

Navigation rules in the console app control how record links open. Adding a rule for the Lead object set to subtab ensures that when an agent clicks a Lead from the Case related list, it opens as a subtab under the Case primary tab. This is the correct console-level configuration to achieve the desired behavior.

Why this answer

Navigation rules in the Lightning Console app define how record links open. Creating a rule for the Lead object that opens records as a subtab allows agents to click a Lead from the Case related list and see it as a subtab under the Case primary tab, preserving the Case context. This is the standard console configuration for this requirement.

Exam trap

The trap here is assuming that related list components or Split View control subtab behavior, when in fact navigation rules in the console app are what determine how record links open.

Practice this question →
6
MCQmedium

A service manager wants agents to see a Contact's open Cases and recent Activity history side-by-side on the Case record page without navigating away. The consultant adds the appropriate components to the Lightning page in Lightning App Builder. Which console feature should the consultant configure to let agents open the Contact record in a new subtab while keeping the Case open?

A.In the Lightning Console app's navigation rules, add a rule for the Contact object that opens records as a subtab.
B.Configure a Navigation Item in the Lightning Console app and set its behavior to open records in a new subtab.
C.Enable the "Open in new subtab" navigation rule on the Contact related list in the Lightning page.
D.Add the Contact object to the console's Utility Bar and enable "Pin as subtab" on the utility item.
AnswerA

Navigation rules in the Lightning Console app settings define how record links open, including as a primary tab, subtab, or new window. Adding a rule for the Contact object and choosing subtab makes Contact links from the Case related list open in a subtab, which is exactly the side-by-side behavior the manager wants for reviewing related Cases and Activity.

Why this answer

Navigation rules in the Lightning Console app determine how record links behave, including whether they open as a primary tab, subtab, or new window. Creating a rule for the Contact object that opens records as a subtab allows agents to view the Contact alongside the open Case, matching the requirement for side-by-side access without leaving the Case.

Exam trap

The trap here is assuming that record-link behavior is set on the related list component in Lightning App Builder rather than in the console app's navigation rules.

Practice this question →
7
Multi-Selecteasy

Which TWO productivity tools are typically utilized alongside the Lightning Service Console to enhance agent efficiency? (Choose two.)

Select 2 answers
A.Einstein Vision
B.Salesforce Billing
C.Territory Management
D.Macros
E.Quick Text
AnswersD, E

Macros automate repetitive multi-step agent tasks within the Lightning Service Console, such as updating fields and sending emails in one click. They directly reduce handling time and manual errors, satisfying the requirement for productivity tools that enhance agent efficiency alongside the console.

Why this answer

Macros (D) are correct because they let agents execute a predefined series of actions—such as sending an email, updating a field, or changing status—with a single click in the Lightning Service Console, directly reducing handle time and repetitive work. Quick Text (E) is correct because it provides prewritten, reusable message snippets that agents can insert into emails, chats, and case comments, speeding up responses and improving consistency. Both are standard Service Cloud productivity features surfaced in the console's utility bar and feed, so they are the tools typically paired with the console to boost agent efficiency.

Einstein Vision (A) is an image-recognition/AI service, not an agent productivity tool for the console; Salesforce Billing (B) is a revenue/order management product unrelated to console agent efficiency; and Territory Management (C) is a sales org structure feature for segmenting accounts and territories, not a console productivity tool.

Exam trap

Service-Con-201 often tests whether candidates confuse AI or sales tools (Einstein Vision, Territory Management) with agent productivity features — the trap is picking a well-known Salesforce product that doesn't actually enhance console efficiency.

Practice this question →
8
MCQmedium

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?

A.Right-click the workspace tab and select Pin Tab
B.Add the tab to the utility bar
C.Click the lock icon in the global header
D.Configure the tab behavior in User Settings
AnswerA

Pinning locks the workspace tab in place, so it persists when the console reaches its maximum tab limit and cannot be closed accidentally. Right-clicking the tab exposes the Pin Tab action, directly satisfying the agent's requirement to protect the active Case tab.

Why this answer

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.

Exam trap

Service-Con-201 often tests the distinction between pinning tabs and other console customization features like utility bar items or user settings, so candidates might confuse the right-click method with configuration options.

How to eliminate wrong answers

Option B is wrong because the utility bar is used for tools like softphones or notes, not for pinning workspace tabs. Option C is wrong because the lock icon in the global header is unrelated to tab management; it typically indicates a secure connection or session lock. Option D is wrong because User Settings do not include a configuration for pinning individual tabs; tab behavior is managed directly on the tab itself.

Practice this question →
9
MCQhard

Northern Trail Outfitters wants to ensure that when a Support Agent opens a Contact from a Case workspace tab, the Contact always opens as a subtab rather than replacing the Case tab. How should the consultant configure this?

A.Update the User Profile tab permissions
B.Modify the Case object page layout related lists
C.Configure Console Navigation Rules in App Manager
D.Set the component visibility filter on the Contact record page
AnswerC

Console Navigation Rules in App Manager define how records open within the console, letting the consultant force Contact to open as a subtab instead of replacing the Case tab. This satisfies the subtab constraint without custom code.

Why this answer

Console Navigation Rules in the Lightning App Builder or App Manager allow administrators to define that certain objects open as subtabs of specific parent objects.

Practice this question →
10
MCQmedium

Agents complain that when they open too many tabs in the Lightning Service Console, performance degrades and they lose track of context. What should the administrator configure to mitigate this issue?

A.Cache and Permanent Storage settings
B.Maximum Workspace Tab limits in App Manager
C.Session Timeout settings in Security Controls
D.List View filter limits
AnswerB

Maximum Workspace Tab limits in App Manager cap how many console tabs an agent can open simultaneously. This directly addresses the degradation caused by excessive tabs and preserves context by preventing unbounded tab accumulation within the Lightning Service Console.

Why this answer

Administrators can set maximum workspace tab limits in the App Manager console configuration settings to automatically close oldest unpinned tabs.

Practice this question →
11
MCQeasy

An administrator is setting up the Lightning Service Console and needs to provide agents with a one-click method to populate standard field values and send an email to a customer. Which feature should be implemented?

A.Pre-chat Forms
B.Flow Actions
C.Macros
D.Quick Text
AnswerC

Macros execute a defined sequence of actions—setting standard field values and sending an email—from a single click in the Lightning Service Console. This directly satisfies the stem's requirement for one-click population of fields plus customer email, unlike Quick Text, which only inserts predefined text snippets.

Why this answer

Macros in Lightning Service Console let agents execute a predefined set of instructions — such as updating fields, sending emails, and posting to Chatter — with a single click from the case feed or action bar. They are purpose-built for repetitive agent actions like populating standard fields and firing off a templated email, which matches the requirement exactly.

Exam trap

Service-Con-201 often tests the macro-vs-flow-vs-quick-text trap: candidates pick Flow Actions or Quick Text because they sound more powerful or simpler, but the question's 'one-click populate fields and send email' is the textbook macro use case.

How to eliminate wrong answers

Option A is wrong because Pre-chat Forms are used in Experience Cloud/Embedded Service chat to collect visitor information before a chat session starts, not to perform agent-side field updates and emails. Option B is wrong because Flow Actions are invocable flows exposed as actions; they can update fields and send emails but are not the one-click macro feature the question describes, and they require building a flow rather than configuring a macro. Option D is wrong because Quick Text inserts reusable text snippets into fields or emails but does not populate multiple field values or send an email by itself.

Practice this question →
12
MCQmedium

A Service Cloud Consultant needs to configure the Lightning Service Console so that support agents can quickly access the Knowledge base while assisting customers over phone or chat. Where should the Knowledge component be added to achieve this?

A.Global Actions Menu
B.Utility Bar
C.Pinned List View
D.Navigation Menu
AnswerB

The Utility Bar renders components persistently across the console footer, so agents reach Knowledge instantly without navigating away from the active case. That persistent, one-click access satisfies the requirement for quick reference during phone or chat interactions.

Why this answer

The Utility Bar is a persistent, fixed footer area in the Lightning Service Console designed to provide agents with one-click access to frequently used tools such as Knowledge, History, Notes, and Softphone without leaving the current record. Adding the Knowledge component to the Utility Bar lets agents search and attach articles while on a call or chat, which is exactly the use case described.

Exam trap

Service-Con-201 often tests the distinction between the Utility Bar (persistent footer for tools) and the Navigation Menu (top-level app switcher) — candidates confuse 'footer' with 'navigation' and pick the wrong container.

How to eliminate wrong answers

Option A is wrong because the Global Actions Menu only exposes quick actions (Create Case, Log a Call, etc.) and cannot host a Knowledge search component. Option C is wrong because a Pinned List View pins a filtered list of records to the console's list area, not a Knowledge search panel. Option D is wrong because the Navigation Menu is the top-level app menu used to switch between objects and apps, not a place to embed interactive components.

Practice this question →
13
MCQeasy

Universal Containers wants to enable support agents to view a list of cases while simultaneously seeing the workspace tab details for a selected case without navigating away. Which feature should the administrator enable in the Lightning Service Console?

A.Split View
B.Omni-Channel Supervisor
C.Console Navigation Rules
D.Pinned Regions
AnswerA

Split View lets agents keep the case list visible in one pane while the selected case's workspace tabs open alongside it, so no navigation away occurs. This directly satisfies the stem's requirement for simultaneous list-and-detail visibility within the Lightning Service Console, unlike standard console navigation that replaces the list view.

Why this answer

Split View allows agents to work on a list view on the left side of the screen while opening records in workspace tabs without losing their place in the list.

Practice this question →
14
MCQmedium

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?

A.Rich Text Component
B.Email Templates
C.Quick Text
D.Custom Buttons
AnswerC

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.

Why this answer

Quick Text is a Salesforce feature purpose-built for inserting pre-approved, reusable text snippets into case comments, emails, and chat messages via a searchable picker or keyboard shortcut. It is distinct from macros because it inserts static text rather than executing a sequence of actions, which matches the agents' stated need to avoid macros. Quick Text is deployable through the Service Console and can be organized into folders and shared with specific profiles.

Exam trap

Service-Con-201 often tests the distinction between Quick Text (static reusable text) and Macros (automated action sequences) — candidates confuse the two because both speed up case handling, but only Quick Text inserts pre-approved text without executing actions.

How to eliminate wrong answers

Option A is wrong because Rich Text Components are used to embed formatted content (images, links, styled text) into Lightning pages or CMS content, not to insert reusable snippets into case comments at runtime. Option B is wrong because Email Templates are designed for outbound email composition and cannot be inserted into case comment fields. Option D is wrong because Custom Buttons execute URLs, JavaScript, or Visualforce actions — they do not provide a text-insertion picker for agents.

Practice this question →
15
MCQmedium

A service manager wants agents to be able to see a customer's open Cases, recent Orders, and Entitlements side-by-side with the Case record they are working on in the Lightning Service Console, without leaving the primary record. Which configuration should a consultant use to meet this requirement?

A.Configure a custom Console component that queries the related records via Apex
B.Add the related lists to the Case page layout and enable them in the Console's Related Lists component
C.Add the related records to the Console's Highlights Panel
D.Use the Console's Split View feature to show related records in a secondary tab
AnswerB

The Related Lists component in the Lightning Service Console can display related lists configured on the page layout. By adding the desired related lists (Cases, Orders, Entitlements) to the Case page layout and placing the Related Lists component in the console, agents can view them alongside the primary record without leaving the page.

Why this answer

The Related Lists component is the standard console component that surfaces related lists from the page layout. By adding the relevant related lists to the Case page layout and including the component in the console, agents can see open Cases, Orders, and Entitlements without navigating away. This is a declarative, no-code solution that meets the requirement.

Exam trap

The trap here is confusing the Highlights Panel, which shows fields from the primary and parent records, with the Related Lists component, which shows child records.

Practice this question →
16
MCQmedium

Support agents need to execute a macro that sends an email using a specific email template and then changes the case status. When running the macro, the email action fails to populate the template. What should the consultant verify?

A.Confirm the email template is stored in the public unfiled folder only.
B.Ensure the user has Modify All data access on the Case object.
C.Check that the macro has administrative approval for bulk email delivery.
D.Verify that the email quick action is configured on the page layout and supports the selected email template type.
AnswerD

Email quick actions must be added to the case page layout and their template type must match the macro's selected template. If the quick action is absent from the layout or its supported template type differs, the macro cannot populate the template, causing the email action to fail.

Why this answer

The most likely cause is that the email quick action is not configured on the page layout or does not support the selected email template type. Macros rely on quick actions, and if the action is missing or misconfigured, the template will not populate.

Exam trap

Service-Con-201 often tests whether candidates overlook the dependency between macros and quick actions, assuming that any email template can be used without verifying the quick action configuration on the page layout.

How to eliminate wrong answers

Option A is wrong because the folder location of the email template (public unfiled) does not affect whether the macro can use it; what matters is the template type and accessibility. Option B is wrong because Modify All Data is not required to send an email via macro; standard object permissions suffice. Option C is wrong because there is no such thing as administrative approval for bulk email delivery in the context of macros.

Practice this question →
17
MCQhard

A consultant is configuring a Lightning Service Console for a team that handles high-priority Cases. The manager wants agents to be able to quickly identify which Cases are approaching their entitlement milestone and take action. Which feature should the consultant configure to provide a visual indicator and countdown for the milestone directly on the Case record?

A.Entitlement Milestone Tracker component
B.Path Assistant on the Case
C.Service Console's Utility Bar with a custom timer
D.Case Timeline component
AnswerA

The Entitlement Milestone Tracker component displays a visual timeline of milestones for a Case, including status and time remaining. It helps agents see which milestones are approaching or breached, enabling proactive action. This component is specifically designed for this purpose and can be added to the Case page layout in the console.

Why this answer

The Entitlement Milestone Tracker component is a standard Lightning component that visualizes entitlement milestones on a Case. It shows each milestone's status, target time, and time remaining, allowing agents to prioritize and act before breaches. Adding it to the Case page layout in the console directly addresses the requirement without custom development.

Exam trap

The trap here is assuming that any timeline or path component can display milestone countdowns, when only the Entitlement Milestone Tracker is purpose-built for entitlement milestones.

Practice this question →
18
Multi-Selecteasy

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

Select 2 answers
A.Allows quick navigation between records without losing list context.
B.Sends automated customer satisfaction surveys.
C.Automatically deletes duplicate case records.
D.Translates incoming customer chat messages in real time.
E.Maintains a persistent list view on the screen while working on records.
AnswersA, E

Split View presents a list and a record side by side in the console, so agents open records without navigating away from the list. This preserves list context and enables quick movement between records, satisfying the stated navigation benefit.

Why this answer

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.

Exam trap

The trap here is confusing console productivity features (Split View) with automation or AI features (surveys, deduplication, translation), leading candidates to pick plausible-sounding but unrelated benefits.

Practice this question →
19
MCQeasy

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

A.It allows agents to browse list views without leaving their active workspace tabs.
B.It displays multiple utility bar components at the same time.
C.It automatically resolves cases using Einstein AI.
D.It splits incoming phone calls between two agents simultaneously.
AnswerA

Split View renders a list view alongside the active record tab, so agents can browse and select records without navigating away from their open workspace tabs. This directly satisfies the stem's constraint of preserving the active workspace while working through list views.

Why this answer

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.

Exam trap

Service-Con-201 often tests the specific purpose of Split View, and candidates may incorrectly associate it with utility bar or AI features.

How to eliminate wrong answers

Option B is wrong because displaying multiple utility bar components is a function of the utility bar configuration, not Split View. Option C is wrong because automatic case resolution via Einstein AI is a separate feature (Einstein Case Classification/Article Recommendations) and not related to Split View. Option D is wrong because splitting incoming phone calls between two agents is not a feature of Split View; call routing is handled by Omni-Channel and telephony integration.

Practice this question →
20
MCQhard

An organization wants agents to use keyboard shortcuts within the Lightning Service Console to navigate efficiently. Where can an administrator enable and view the available keyboard shortcuts for the console?

A.Keyboard Shortcuts utility component in the utility bar
B.Chatter Settings
C.Company Information setup page
D.User Detail page settings
AnswerA

The Keyboard Shortcuts utility component in the utility bar is the only place administrators enable console shortcuts and view the full list of available key combinations. It satisfies the requirement to both activate shortcuts and display them for agents, which no other console setting provides.

Why this answer

The Keyboard Shortcuts utility component can be added to the utility bar in the Lightning Service Console. Once added, it provides a list of available keyboard shortcuts and allows the administrator to enable or disable them. This is the central place to manage console keyboard shortcuts.

Exam trap

Service-Con-201 often tests where console-specific settings are located, causing candidates to choose general setup pages instead of the utility bar component.

How to eliminate wrong answers

Option B is wrong because Chatter Settings control Chatter features, not console keyboard shortcuts. Option C is wrong because the Company Information setup page contains org-wide settings like default locale and fiscal year, not keyboard shortcuts. Option D is wrong because User Detail page settings are for individual user preferences, not for enabling or viewing console keyboard shortcuts.

Practice this question →
21
Multi-Selectmedium

Which TWO configuration options are available when setting up Console Navigation Rules in App Manager? (Choose two.)

Select 2 answers
A.Define which object opens as a subtab of a parent workspace tab.
B.Configure automatic tab closure timers based on user inactivity.
C.Set automated background refresh intervals for open subtabs.
D.Define color-coding rules for high-priority workspace tabs.
E.Specify whether related lists open records as workspace tabs or subtabs.
AnswersA, E

Console Navigation Rules govern how objects open within the workspace tab hierarchy, so specifying that an object opens as a subtab of a parent workspace tab is a supported configuration. This satisfies the stem's requirement for available Console Navigation Rule settings in App Manager, controlling nested tab placement rather than standalone window behaviour.

Why this answer

Option A is correct because Console Navigation Rules in App Manager let you define which object opens as a subtab of a parent workspace tab, controlling the tab hierarchy when users drill into records from a console. Option E is correct because these rules also specify whether related lists open records as workspace tabs or subtabs, governing how related records are presented within the console. Options B, C, and D are incorrect because automatic tab closure timers, background refresh intervals, and color-coding rules for workspace tabs are not configuration options provided by Console Navigation Rules in App Manager.

Exam trap

Service-Con-201 often tests the specific capabilities of Console Navigation Rules, causing candidates to select options that sound plausible but are not actually configurable, such as tab closure timers or color-coding.

Practice this question →
22
Multi-Selecteasy

Which TWO features are characteristic of the Lightning Service Console navigation model? (Choose two.)

Select 2 answers
A.Workspace tabs allow agents to view primary records.
B.Subtabs can exist independently without a parent workspace tab.
C.Subtabs organize related records beneath a parent workspace tab.
D.Standard navigation replaces the entire browser window content.
E.Console apps cannot include utility bars.
AnswersA, C

Workspace tabs let agents keep multiple primary records open simultaneously, each in its own tab, so they can switch between cases, accounts, or contacts without losing context. This satisfies the Lightning Service Console's requirement for efficient, side-by-side record handling during service work.

Why this answer

In the Lightning Service Console navigation model, workspace tabs are the primary-level containers that let agents open and work with primary records such as cases, accounts, or contacts, which is exactly what option A describes. Option C is also correct because subtabs are the secondary-level tabs that appear nested under a parent workspace tab and are used to organize related records, such as a case's related contact or a child case, without losing the context of the primary record. Options B, D, and E are incorrect: subtabs cannot exist independently of a parent workspace tab, standard navigation (as opposed to console navigation) replaces the entire browser window content rather than using the console's tabbed workspace model, and console apps can indeed include utility bars for tools like notes, recent items, and macros.

Exam trap

Service-Con-201 often tests the parent-child dependency between workspace tabs and subtabs, tricking candidates who assume subtabs can float independently like browser tabs.

Practice this question →
23
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.

Practice this question →
24
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.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Service Console questions.

Start 20-question session