Courseiva

CCNA Sales Lifecycle Questions

50 questions · Sales Lifecycle · All types, answers revealed

Practice these questionsDomain overviewAll questions
1
MCQmedium

Sales reps are spending too much time manually entering meeting notes and logging emails into Salesforce. Management wants an automated solution that captures customer interactions from Microsoft Office 365 without requiring browser plugins. What should be implemented?

A.Einstein Activity Capture
B.Lightning Sync
C.Salesforce for Outlook Integration Pane
D.Sales Engagement Work Queue
AnswerA

Einstein Activity Capture automatically syncs emails and calendar events from Microsoft Office 365 into Salesforce, logging rep interactions without manual entry or browser plugins. This directly satisfies the no-plugin automation requirement for capturing customer touchpoints.

Why this answer

Einstein Activity Capture (EAC) syncs emails, events, and contacts between Microsoft or Google accounts and Salesforce automatically.

Practice this question →
2
MCQmedium

Universal Containers uses Collaborative Forecasting and wants sales managers to be able to adjust their team's forecast amounts up or down based on qualitative deal knowledge. Where is manager adjustment enabled and viewed?

A.By modifying the Opportunity Split configuration.
B.Using custom rollup summary fields on the User object.
C.In Forecasts Settings, enable Manager Adjustments for the specific forecast type.
D.On the User Detail page by checking 'Allow Forecast Adjustments'.
AnswerC

Manager Adjustments must be enabled per forecast type within Forecasts Settings, which then exposes an adjustment column directly on the forecasting grid. This satisfies the requirement that managers adjust their team's amounts up or down using qualitative deal knowledge, since adjustments apply only to the forecast type configured, not globally.

Why this answer

Manager adjustments in Collaborative Forecasting are enabled in Forecasts Settings for a specific forecast type. This allows managers to manually adjust their team's forecast amounts up or down. The setting is found in Setup under Forecasts, and must be enabled per forecast type.

Exam trap

Sales-Con-201 often tests the location of the manager adjustment setting, with candidates incorrectly assuming it is on the User record or via sharing rules, rather than in Forecasts Settings per forecast type.

How to eliminate wrong answers

Option A is wrong because Opportunity Split configuration is used to divide credit for opportunities among team members, not for forecast adjustments. Option B is wrong because custom rollup summary fields on the User object cannot be used to adjust forecasts; forecasts are based on opportunity data, not user fields. Option D is wrong because there is no 'Allow Forecast Adjustments' checkbox on the User Detail page; adjustments are configured at the forecast type level.

Practice this question →
3
MCQeasy

A Sales Operations manager wants to track the exact date an Opportunity stage changes from 'Prospecting' to 'Value Proposition' to measure pipeline velocity. Which feature should the Consultant utilize?

A.Opportunity Field History Tracking
B.Einstein Opportunity Scoring
C.Salesforce Surveys
D.Opportunity Stage Duration fields
AnswerA

Opportunity Field History Tracking records timestamped changes to the Stage field, capturing the precise date each transition occurs. This satisfies the requirement to measure pipeline velocity between 'Prospecting' and 'Value Proposition', since standard reporting cannot surface the exact historical moment a stage changed.

Why this answer

Opportunity Field History Tracking is the correct feature because it automatically records changes to specific fields, including the Stage field, capturing the date and time of each change. By enabling history tracking on the Stage field, the manager can see exactly when the stage moved from 'Prospecting' to 'Value Proposition', enabling precise pipeline velocity measurement. This is a standard Salesforce feature that requires no custom development and provides an audit trail of field changes.

Exam trap

Sales-Con-201 often tests the difference between historical tracking (which provides exact timestamps) and calculated duration fields (which provide aggregated time but not the specific date of change), causing candidates to confuse the two.

How to eliminate wrong answers

Option B is wrong because Einstein Opportunity Scoring uses predictive analytics to score opportunities based on likelihood to close, not to track stage change dates. Option C is wrong because Salesforce Surveys are used to collect feedback from customers or employees, not to track opportunity field history. Option D is wrong because Opportunity Stage Duration fields (such as 'Stage Duration' in Sales Cloud) calculate the time spent in a stage but do not provide the exact date of the stage change; they are derived metrics, not historical timestamps.

Practice this question →
4
MCQmedium

Universal Containers requires that whenever an opportunity is moved to 'Closed Won', a congratulatory post is automatically published to a specific Chatter group with key deal details. What is the most efficient declarative tool to achieve this?

A.Custom Report Notification subscription.
B.Record-Triggered Flow with a 'Post to Chatter' action.
C.Process Builder with Chatter publisher actions.
D.Apex Trigger utilizing ConnectApi.ChatterFeeds.
AnswerB

A record-triggered flow fires on the Closed Won update and its Post to Chatter action publishes the message to the specified group, embedding merge fields for deal details. This is declarative, needing no Apex trigger or Process Builder.

Why this answer

A Record-Triggered Flow with a 'Post to Chatter' action is the most efficient declarative tool because it directly supports posting to a specific Chatter group when a record meets the trigger condition (Opportunity Stage = 'Closed Won'). It requires no code, is built on the modern Flow automation engine, and the 'Post to Chatter' action can target a group by ID and include merge fields for deal details. This aligns with Salesforce's strategic direction, as Process Builder is deprecated for new automation.

Exam trap

Sales-Con-201 often tests the misconception that Process Builder can post to Chatter groups or that Apex is required for Chatter automation, when in fact Record-Triggered Flow with the 'Post to Chatter' action is the declarative standard.

How to eliminate wrong answers

Option A is wrong because Custom Report Notifications only send scheduled or condition-based notifications about report data to users, not publish posts to a Chatter group with dynamic record details. Option C is wrong because Process Builder cannot natively perform a 'Post to Chatter' action; it can only invoke Chatter publisher actions in the UI, not automate posts to a group, and Process Builder is also deprecated. Option D is wrong because an Apex Trigger using ConnectApi.ChatterFeeds is a programmatic solution, not declarative, and requires code maintenance, testing, and governor limit considerations, making it less efficient for this requirement.

Practice this question →
5
Multi-Selecteasy

Which TWO actions can a sales representative perform using the Kanban view on opportunities? (Choose two.)

Select 2 answers
A.Configure custom fiscal years.
B.View alerts on opportunities indicating missing tasks or overdue dates.
C.Drag and drop opportunities across columns to update their stage.
D.Build custom report types.
E.Modify organization-wide sharing settings.
AnswersB, C

Kanban cards surface alert icons flagging missing tasks or overdue dates, letting representatives spot stalled opportunities at a glance. This satisfies the stem's requirement by providing a view-level alerting action that highlights incomplete or late activities without opening each record.

Why this answer

Option B is correct because the Kanban view for opportunities surfaces visual alert icons on cards when a related activity is overdue or a required task is missing, helping reps spot at-risk deals at a glance. Option C is correct because Kanban is a drag-and-drop interface: moving an opportunity card from one column to another directly updates the opportunity's Stage field, with the columns representing stage values. Options A, D, and E are incorrect because configuring custom fiscal years, building custom report types, and modifying organization-wide sharing settings are all administrative setup tasks performed in Setup, not actions available to a sales representative from the opportunity Kanban view.

Exam trap

Sales-Con-201 often tests the confusion between sales rep actions in Kanban and administrative tasks like fiscal year setup or sharing settings, which are not available in that view.

Practice this question →
6
Multi-Selecthard

An administrator is troubleshooting a Sales Engagement deployment where sales reps are unable to add prospects to sales cadences. Which THREE factors could cause this issue? (Choose three.)

Select 3 answers
A.Collaborative Forecasting is disabled in the organization.
B.The Sales Cadence status is not set to 'Active'.
C.The users lack the 'Sales Engagement User' permission set license and assigned permission set.
D.The target records (Leads or Contacts) do not meet the criteria defined in the sales cadence target settings.
E.Einstein Activity Capture is uninstalled from AppExchange.
AnswersB, C, D

A cadence whose status is not 'Active' remains in Draft or Paused, so Sales Engagement blocks reps from enrolling prospects until it is activated. This directly satisfies the stem's enrolment failure: the cadence must be Active before any prospect can be added.

Why this answer

Option B is correct because a sales cadence must have its status set to 'Active' before reps can add prospects to it; a Draft or Inactive cadence cannot accept new targets. Option C is correct because Sales Engagement functionality requires the Sales Engagement User permission set license along with the assigned permission set; without both, users cannot access cadence actions such as adding prospects. Option D is correct because each cadence has target settings that define which Leads or Contacts qualify (for example, by record type, field criteria, or ownership), and records failing those criteria cannot be added.

Option A is not relevant because Collaborative Forecasting is a separate forecasting feature and does not govern cadence enrollment. Option E is not relevant because Einstein Activity Capture handles email and event syncing, not the ability to add prospects to cadences.

Exam trap

The trap is assuming unrelated features like Collaborative Forecasting or Einstein Activity Capture affect cadence enrollment, when the real gates are cadence status, licensing/permission sets, and target criteria.

Practice this question →
7
MCQeasy

Universal Containers wants to ensure that sales reps can view key Account metrics, open Opportunities, and relevant Einstein Insights directly on the mobile app without navigating through multiple tabs. Which Salesforce feature should the Consultant recommend configuring?

A.Lightning App Builder for Mobile
B.Global Actions
C.Mobile Publisher
D.Salesforce Console for iPad
AnswerA

Lightning App Builder for Mobile lets administrators compose a single mobile page combining Account metrics, related Opportunity lists and Einstein Insights components. This satisfies the no-navigation constraint by surfacing everything reps need on one screen instead of across multiple tabs.

Why this answer

Lightning App Builder for Mobile lets consultants customize the mobile navigation and place components like Account metrics, related Opportunity lists, and Einstein Insights on a single mobile page, eliminating tab-hopping. It provides a drag-and-drop mobile-specific layout that surfaces key information directly on the record page. Global Actions, Mobile Publisher, and Console for iPad do not address consolidating record-level metrics and insights into one mobile view.

Exam trap

Sales-Con-201 often tests whether candidates confuse app packaging (Mobile Publisher) or legacy consoles with the actual layout tool (Lightning App Builder) that controls mobile page composition.

How to eliminate wrong answers

Option B is wrong because Global Actions are quick-create or custom actions available from the global actions menu, not a layout tool for composing record pages with metrics and insights. Option C is wrong because Mobile Publisher packages a Lightning app into a branded mobile app for distribution — it doesn't control page layout or component placement. Option D is wrong because Salesforce Console for iPad is a legacy console app for case management, not the modern tool for designing mobile record pages with Einstein Insights.

Practice this question →
8
Multi-Selecthard

An administrator is auditing report and dashboard security in Sales Cloud. Which THREE best practices should be followed to secure sensitive sales pipeline data? (Choose three.)

Select 3 answers
A.Regularly audit dashboard folder access and scheduled dashboard email recipients.
B.Ensure the organization-wide sharing default for Opportunities is public read/write for all community users.
C.Disable all role hierarchies so that managers cannot view subordinate reports.
D.Store reports and dashboards in private folders shared only with authorized roles or public groups.
E.Use dynamic dashboards with 'View Dashboard As: The Logged-in User' to respect data visibility rules.
AnswersA, D, E

Scheduled dashboard emails bypass interactive login, so recipients may receive data they could not otherwise view. Auditing folder access and subscription lists closes that leak, satisfying the requirement to continuously verify who can reach sensitive pipeline reports.

Why this answer

Option A is correct because dashboard folders and scheduled dashboard email recipients are common leak paths in Sales Cloud; auditing folder access and the running user/recipients of scheduled dashboard emails ensures sensitive pipeline data is not delivered to unauthorized users. Option D is correct because storing reports and dashboards in private folders shared only with authorized roles or public groups enforces least-privilege access, preventing broad visibility of sensitive sales pipeline data. Option E is correct because a dynamic dashboard set to 'View Dashboard As: The Logged-in User' runs under each viewer's own sharing rules, so users only see the Opportunities and records they are permitted to access.

Option B is incorrect because making the Opportunity organization-wide default public read/write exposes pipeline data to all community users, violating least privilege. Option C is incorrect because disabling role hierarchies removes legitimate manager visibility and does not secure data; role hierarchy access should be controlled, not universally disabled.

Exam trap

Sales-Con-201 often tests whether candidates equate 'sharing' with 'security' — the trap is picking a broad sharing default (public read/write) as if it improves collaboration when it actually violates least privilege.

Practice this question →
9
MCQhard

An organization utilizes Enterprise Territory Management. A sales rep changes departments and is removed from a territory. What happens to the manual sharing rules and open opportunities owned by that rep within that territory?

A.All opportunities owned by the rep are automatically deleted by the territory cleanup job.
B.Open opportunities are automatically transferred to the default territory manager user.
C.The user retains permanent manual sharing access to all historical opportunities regardless of territory unassignment.
D.Access to accounts and opportunities tied to the territory is removed when the user is unassigned from the territory, subject to territory model re-evaluation.
AnswerD

Unassigning a user from a territory removes territory-derived access to accounts and opportunities, since that access flows from territory membership rather than ownership. Territory model re-evaluation then recalculates assignments, so the rep loses access unless separately granted.

Why this answer

When a user is unassigned from a territory in Enterprise Territory Management, their access to the accounts and opportunities associated with that territory is revoked. The territory model re-evaluates assignments, and any manual sharing or opportunity access granted solely through territory membership is removed. This is the expected behavior — territory-based access is dynamic and tied to current membership, not historical ownership.

Exam trap

Sales-Con-201 often tests the misconception that territory unassignment deletes or permanently preserves access to records, when in fact it dynamically revokes access subject to model re-evaluation.

How to eliminate wrong answers

Option A is wrong because opportunities are never deleted by territory cleanup — ownership and access are adjusted, not the records themselves. Option B is wrong because there is no automatic transfer of open opportunities to a 'default territory manager user'; opportunity ownership remains with the rep unless manually reassigned or reassigned via territory rules. Option C is wrong because manual sharing access is not permanent — it is subject to territory re-evaluation and can be removed when the user is unassigned.

Practice this question →
10
MCQhard

An administrator is troubleshooting a discrepancy between Opportunity Pipeline standard reports and Collaborative Forecasting amounts. The forecast type is based on Opportunity Revenue, and the date range is set to the current quarter. What is a primary reason these two figures might differ?

A.Standard pipeline reports exclude partner-owned opportunities automatically.
B.Forecasts use Advanced Currency Management conversion rates while reports use static dated exchange rates.
C.Forecasts filter opportunities by forecast category and close date, whereas pipeline reports may include open opportunities with different forecast category mappings or date parameters.
D.Collaborative Forecasting excludes opportunities owned by inactive users, while reports include them.
AnswerC

Forecast amounts are restricted to opportunities in forecast categories included in the forecast type and to close dates within the quarter, while pipeline reports can include open opportunities across other categories or date ranges, so the two datasets legitimately diverge.

Why this answer

Collaborative Forecasting and standard pipeline reports use different filtering logic. Forecasts filter by forecast category (e.g., Pipeline, Best Case, Commit, Closed) and by the forecast period's close date, while pipeline reports typically show all open opportunities regardless of forecast category and may use different date field parameters (Close Date vs. Created Date).

This mismatch in both category mapping and date filtering is the primary reason the two figures diverge.

Exam trap

Sales-Con-201 often tests the misconception that forecasts and pipeline reports use identical filters, when in fact forecast category mapping and close-date period logic cause the divergence.

How to eliminate wrong answers

Option A is wrong because standard pipeline reports do not automatically exclude partner-owned opportunities — partner ownership is not a default filter in Opportunity reports. Option B is wrong because Advanced Currency Management applies to both forecasts and reports consistently; it is not a differentiator between the two. Option D is wrong because Collaborative Forecasting does not silently exclude opportunities owned by inactive users; ownership by inactive users is not a standard forecast exclusion criterion.

Practice this question →
11
Multi-Selecthard

Universal Containers utilizes Collaborative Forecasting. Which THREE components can be included in forecast calculations depending on the configured forecast type? (Choose three.)

Select 3 answers
A.Opportunity Revenue or Quantity amounts
B.Product Family revenue totals
C.Opportunity Splits (Revenue or Overlay splits)
D.Chatter feed post sentiment scores
E.Knowledge article view counts
AnswersA, B, C

Opportunity Revenue or Quantity amounts form the base measure that Collaborative Forecasting aggregates, and the configured forecast type determines which is used. This satisfies the stem's requirement by supplying the core values included in forecast calculations.

Why this answer

In Salesforce Collaborative Forecasting, the forecast type determines which measurable field is aggregated, and Opportunity Revenue or Quantity amounts (A) are the core values that can be summed into forecast totals, so A is correct. Forecasts can also be broken down by Product Family revenue totals (B), since forecast types can be configured to forecast by product family, making B correct. Additionally, Opportunity Splits (Revenue or Overlay splits) (C) can be included so that split owners see their portion of the forecast, which is a supported forecast type configuration, making C correct.

Chatter feed post sentiment scores (D) and Knowledge article view counts (E) are unrelated to opportunity forecasting data and cannot be included in forecast calculations, so they are incorrect.

Exam trap

The trap is assuming that any data point (like Chatter sentiment or Knowledge views) can be forecasted; only specific opportunity-related components are supported.

Practice this question →
12
MCQeasy

A sales rep needs to quickly check key metrics such as win rate, total pipeline, and closed-won revenue for the current quarter without navigating away from the Home page. What is the best way to provide this visibility?

A.Build an Apex page to query summary objects.
B.Embed a Lightning Dashboard component on the Home page.
C.Schedule a daily email report containing the metrics.
D.Create a custom list view with summary metrics.
AnswerB

Embedding a Lightning Dashboard component places the dashboard's charts directly on the Home page, so the rep sees win rate, pipeline, and closed-won revenue for the current quarter without navigating away. This satisfies the stem's in-place visibility constraint, unlike reports or list views that require opening a separate tab.

Why this answer

Embedding a Lightning Dashboard component directly on the Home page gives the rep immediate, in-context visibility into win rate, pipeline, and closed-won revenue without navigating away. Lightning Dashboards support dynamic filtering (e.g., 'This Quarter') and refresh automatically, making them the standard declarative solution for at-a-glance Home page metrics.

Exam trap

The trap is choosing a custom-code or asynchronous solution (Apex page, scheduled email) when a declarative, real-time component (embedded Lightning Dashboard) is the intended 'best' answer — candidates over-engineer the solution.

How to eliminate wrong answers

Option A is wrong because building an Apex page to query summary objects is a custom-code approach that is unnecessary, harder to maintain, and not the 'best' (simplest, declarative) way to surface standard metrics. Option C is wrong because a scheduled daily email report delivers metrics asynchronously and requires the rep to leave the Home page to open the email — it does not provide real-time visibility. Option D is wrong because a custom list view shows records, not aggregated summary metrics like win rate or total pipeline; list views cannot compute those KPIs.

Practice this question →
13
MCQeasy

Cloud Kicks wants to track the progress of its sales deals through the stages of its sales lifecycle. The sales manager needs a visual representation of all opportunities by stage to identify bottlenecks. Which standard Salesforce feature should the consultant recommend?

A.Salesforce Kanban View on Opportunity List View
B.Opportunity Stage History Report
C.Opportunity Pipeline Chart on the Home Page
D.Custom Report with a Summary Formula
AnswerA

The Kanban View on an Opportunity list view provides a visual board where opportunities are grouped by stage. Each stage is represented as a column, and opportunities are cards that can be dragged between stages. This allows the sales manager to quickly see the distribution of deals across stages and identify bottlenecks where opportunities are piling up. It is a standard, built-in feature that requires no customization.

Why this answer

The Kanban View on an Opportunity list view is a standard Salesforce feature that visually organizes opportunities by stage. It allows users to see all opportunities in a board layout, with columns for each stage, and enables dragging opportunities from one stage to another. This makes it easy to identify bottlenecks where opportunities are stuck in a particular stage.

It is the ideal tool for the sales manager's requirement.

Exam trap

The trap here is assuming that a report or chart provides the same interactive visual representation as the Kanban view, which is specifically designed for stage-based pipeline management.

Practice this question →
14
MCQhard

An administrator is configuring Collaborative Forecasting for multiple sales teams with distinct sales processes. Team A forecasts on Revenue, while Team B forecasts on Quantity. How should the administrator set this up in Salesforce?

A.Build a single custom forecast type using a formula field that combines revenue and quantity.
B.Use custom report charts embedded on home pages to replace forecast tabs for Team B.
C.Create two distinct Forecast Types—one based on Opportunity Revenue and one based on Opportunity Quantity—and assign them to appropriate user roles or profiles.
D.Enable Advanced Currency Management to convert quantities into revenue equivalents.
AnswerC

Forecast Types define the underlying opportunity measure—Revenue or Quantity—and each is assigned to users via role or profile. Creating two distinct types satisfies the requirement that Team A and Team B forecast on different measures within their separate sales processes.

Why this answer

Collaborative Forecasting in Salesforce supports multiple forecast types, each defined by a forecast category (e.g., Revenue, Quantity, Product Quantity) and a forecast period. To allow Team A to forecast on Revenue and Team B on Quantity, the administrator must create two separate Forecast Types—one using Opportunity Revenue and one using Opportunity Quantity—and then assign each forecast type to the appropriate user roles or profiles. This ensures that each team sees the correct forecast metric without interfering with the other team's view.

Forecast Types are the native mechanism for supporting distinct forecasting needs across different sales processes.

Exam trap

Sales-Con-201 often tests the misconception that a single forecast type can be customized with formulas to combine metrics, or that reports can replace forecasting, when in fact distinct forecast types are required for different forecast metrics.

How to eliminate wrong answers

Option A is wrong because a single custom forecast type using a formula field cannot combine revenue and quantity into a meaningful forecast metric; Salesforce forecast types are based on standard fields (Revenue, Quantity, Product Quantity) and do not support formula fields for forecast calculations. Option B is wrong because custom report charts on home pages are not a substitute for Collaborative Forecasting; they do not provide the interactive forecasting, adjustments, and hierarchy rollups that forecast types offer. Option D is wrong because Advanced Currency Management is used for managing dated exchange rates in multi-currency organizations, not for converting quantities into revenue equivalents; it does not enable forecasting on quantity.

Practice this question →
15
MCQhard

An organization implements Sales Cloud Einstein Generative AI. Sales reps want to automatically generate a summary of long email threads on opportunity records to quickly catch up on customer communications. Which feature supports this requirement?

A.Einstein Discovery Story Generation
B.Einstein Work Summaries / Record Summary prompt templates
C.Einstein Activity Capture Sentiment Analysis
D.Sales Cadence Auto-Summarization
AnswerB

Einstein Work Summaries generate condensed summaries of lengthy email threads and records, letting reps catch up on opportunity communications without reading every message. This directly satisfies the stated requirement for automatic summarisation of long email threads on opportunity records.

Why this answer

Einstein Work Summaries, also known as Record Summary prompt templates, is a generative AI feature that automatically creates concise summaries of long email threads and other activities on records. This directly supports the requirement for sales reps to quickly catch up on customer communications on opportunity records.

Exam trap

Sales-Con-201 often tests the specific generative AI features and their capabilities, and candidates may confuse Work Summaries with other Einstein features like Discovery or Sentiment Analysis, which do not generate email thread summaries.

How to eliminate wrong answers

Option A is wrong because Einstein Discovery Story Generation is used to create narratives from data insights, not to summarize email threads. Option C is wrong because Einstein Activity Capture Sentiment Analysis analyzes the sentiment of emails and activities, but it does not generate summaries of email threads. Option D is wrong because Sales Cadence Auto-Summarization is not a standard feature; Sales Cadence is for managing sales sequences, and there is no auto-summarization of email threads within it.

Practice this question →
16
MCQeasy

Which feature allows a sales representative to update multiple opportunity stages and close dates simultaneously from a list view without opening each record individually?

A.List View Inline Editing
B.Global Quick Actions
C.Kanban View bulk update
D.Data Import Wizard
AnswerA

List View Inline Editing lets a sales representative modify field values, such as opportunity stage and close date, directly within the list view grid. Multiple records are updated in one action, avoiding the need to open each record individually.

Why this answer

List View Inline Editing allows users to edit field values directly within a list view without opening each record, and it supports editing multiple records at once by saving all changes in a single action. This is the native Salesforce Lightning feature designed for exactly this scenario — updating stages and close dates across many opportunities from one screen.

Exam trap

Sales-Con-201 often tests the distinction between interactive UI editing features (inline editing, Kanban) and batch/data tools (Data Import Wizard, Quick Actions), so candidates confuse 'bulk update' with 'data import' or assume Kanban supports multi-field edits.

How to eliminate wrong answers

Option B is wrong because Global Quick Actions create a single new record or log a task/event from anywhere in the app; they do not edit existing records in bulk. Option C is wrong because Kanban View allows drag-and-drop stage changes one card at a time and does not support editing close dates or multiple fields simultaneously. Option D is wrong because Data Import Wizard is a batch data-loading tool for inserting/updating records via CSV, not an interactive UI feature for updating records from a list view.

Practice this question →
17
MCQmedium

Northern Trail Outfitters wants to track the exact date and time an opportunity reaches the 'Proposal/Price Quote' stage for SLA reporting purposes. What is the most efficient way to capture this data?

A.Use Opportunity Stage History standard report types.
B.Write an Apex trigger that queries audit logs.
C.Create a Record-Triggered Flow that populates a custom Date/Time field when the stage changes to 'Proposal/Price Quote'.
D.Enable Field History Tracking on the StageName field.
AnswerC

A record-triggered flow fires on the stage change itself, writing the timestamp the moment the opportunity enters 'Proposal/Price Quote'. This satisfies the SLA requirement for exact date and time without manual entry or formula fields, which cannot reliably capture the transition moment.

Why this answer

A Record-Triggered Flow that populates a custom Date/Time field when StageName changes to 'Proposal/Price Quote' captures the exact timestamp declaratively and efficiently, with no code. It fires on the stage change, stamps the current date/time, and stores it on the Opportunity for SLA reporting.

Exam trap

The trap is choosing Field History Tracking or Stage History reports because they 'track stage changes,' but they do not produce a precise, reportable Date/Time field needed for SLA calculations — candidates miss the requirement for an exact timestamp on the record.

How to eliminate wrong answers

Option A is wrong because Opportunity Stage History report types show when stages changed but only at the date level (and via history records), not a precise, easily reportable Date/Time field for SLA calculations. Option B is wrong because writing an Apex trigger to query audit logs is overly complex, audit logs have retention limits, and this is not the efficient declarative approach. Option D is wrong because Field History Tracking on StageName records that the field changed and when, but the history data is not easily surfaced as a reportable Date/Time field on the Opportunity for SLA metrics.

Practice this question →
18
MCQmedium

Universal Containers uses Collaborative Forecasting and needs to track committed revenue separately from pipeline revenue. Which standard forecast categories are available in Collaborative Forecasting?

A.Pipeline, Best Case, Commit, Closed
B.Prospecting, Qualification, Proposal, Won
C.Forecast, Quota, Attainment, Variance
D.Open, Pending, Approved, Realized
AnswerA

Pipeline, Best Case, Commit and Closed are the four standard forecast categories in Collaborative Forecasting, with Commit isolating committed revenue from pipeline. This directly satisfies the requirement to track committed revenue separately, since Commit is a distinct category rather than a subset of the pipeline.

Why this answer

Salesforce Collaborative Forecasting provides four standard forecast categories: Pipeline, Best Case, Commit, and Closed. These categories allow sales teams to segment opportunities based on their likelihood of closing, enabling separate tracking of committed revenue (Commit) from pipeline revenue (Pipeline). The other options list stages, metrics, or custom terms that are not standard forecast categories.

Exam trap

Sales-Con-201 often tests the distinction between forecast categories and sales stages, causing candidates to confuse the two and select stage names as forecast categories.

How to eliminate wrong answers

Option B is wrong because Prospecting, Qualification, Proposal, and Won are typical sales stages in a sales process, not forecast categories. Option C is wrong because Forecast, Quota, Attainment, and Variance are forecasting metrics or terms used in reports and dashboards, not categories. Option D is wrong because Open, Pending, Approved, and Realized are not standard forecast categories in Salesforce; they might relate to other processes like approvals or custom fields.

Practice this question →
19
Multi-Selecteasy

Which TWO metrics are standard components typically tracked in Sales Cloud dashboards for pipeline management? (Choose two.)

Select 2 answers
A.Case First Response Time
B.Total Pipeline Value by Stage
C.API Call Consumption Count
D.Win Rate Percentage
E.Server CPU Utilization Rate
AnswersB, D

Total Pipeline Value by Stage aggregates opportunity amounts across each sales stage, exposing where deals stall or concentrate. This satisfies the stem's pipeline-management requirement by tracking progression and forecasting revenue, a standard Sales Cloud dashboard component alongside conversion metrics.

Why this answer

Option B, Total Pipeline Value by Stage, is correct because pipeline management dashboards in Sales Cloud track the monetary value of open opportunities grouped by their sales stage, allowing managers to see how much revenue sits at each phase of the funnel. Option D, Win Rate Percentage, is correct because it is a standard sales metric measuring the proportion of closed opportunities that were won, which is essential for evaluating pipeline health and rep performance. Option A, Case First Response Time, is a Service Cloud metric tied to case management, not pipeline management.

Option C, API Call Consumption Count, is a technical/administrative usage metric, not a sales pipeline KPI. Option E, Server CPU Utilization Rate, is an infrastructure monitoring metric unrelated to Sales Cloud dashboards.

Exam trap

Sales-Con-201 often tests whether candidates can distinguish sales pipeline metrics from unrelated Service Cloud or system metrics, so distractors like Case First Response Time and API Call Consumption are included to lure candidates who don't read the domain carefully.

Practice this question →
20
MCQeasy

A sales manager wants to see a report showing all opportunities closing this month, sorted by amount in descending order. Which report feature should the administrator use?

A.Cross Filters
B.Matrix Report Groupings
C.Bucket Fields
D.Report Sorting by Amount column in descending order
AnswerD

Sorting the Amount column in descending order satisfies the requirement to rank opportunities by value, placing the largest first. Combined with a closing-date filter for the current month, this report feature delivers exactly the view the sales manager requested.

Why this answer

To show opportunities closing this month sorted by amount in descending order, the administrator should use report sorting on the Amount column in descending order. This directly fulfills the requirement of sorting by amount. Additionally, a filter would be needed to show only opportunities closing this month, but among the options, sorting is the key feature.

Exam trap

The trap is that candidates might overcomplicate the solution by choosing advanced features like cross filters or bucket fields when simple sorting is sufficient.

How to eliminate wrong answers

Option A is wrong because cross filters are used to filter related records, not for sorting. Option B is wrong because matrix report groupings are for summarizing data in a matrix format, not for simple sorting. Option C is wrong because bucket fields are used to categorize data into ranges, not for sorting.

Practice this question →
21
Multi-Selecteasy

Which TWO actions can sales managers take within Collaborative Forecasting to manage their team's pipeline? (Choose two.)

Select 2 answers
A.Change the organization-wide sharing model for opportunities.
B.Make manager adjustments to subordinate forecast amounts.
C.Reassign user territory ownership models without administrator rights.
D.Modify company fiscal year settings directly from the forecast tab.
E.Drill down into forecast items to view the underlying opportunities contributing to the forecast.
AnswersB, E

Manager adjustments let a sales manager override a subordinate's submitted forecast amount directly, satisfying the requirement to manage team pipeline figures. This operates on the forecast hierarchy's roll-up values rather than the underlying opportunity records, so the manager's revised number flows into aggregated totals without altering the rep's own deal data.

Why this answer

Option B is correct because Collaborative Forecasting allows managers to apply manager adjustments, overriding or tweaking a subordinate's forecast category amounts to reflect their own judgment of the pipeline without altering the underlying opportunity data. Option E is correct because the forecast tab supports drill-down functionality, letting managers expand a forecast category to see the individual opportunities that roll up into a subordinate's or team's forecast total. Option A is incorrect because changing the organization-wide sharing model for opportunities is an administrative setup task done in Setup, not a pipeline management action available on the forecast tab.

Option C is incorrect because reassigning territory ownership models requires administrator permissions and is a configuration task, not a standard manager forecasting action. Option D is incorrect because fiscal year settings are configured by an administrator in Setup and cannot be modified directly from the forecast tab.

Exam trap

Sales-Con-201 often tests the distinction between sales manager capabilities and system administrator permissions in Collaborative Forecasting, causing candidates to confuse administrative configuration tasks with manager-level actions.

Practice this question →
22
MCQhard

An enterprise customer has a sales structure spanning multiple geographic regions. Accounts are assigned to territories. The VP of Global Sales needs to see a forecast that aggregates all regional territories without double counting. How should the forecast hierarchy be structured?

A.Use User Role forecasting and map all regional managers under the Global VP role.
B.Build a single territory model with a multi-level territory hierarchy, where regional child territories roll up into a global parent territory, and enable Territory Forecasting.
C.Create separate territory models for each region and merge them using custom roll-up summary fields.
D.Assign the VP of Global Sales to every regional territory as a secondary user and use Collaborative Forecast adjustments.
AnswerB

A single territory model with multi-level hierarchy lets regional child territories roll up into one global parent, so Territory Forecasting aggregates without double counting. This satisfies the VP's need for a consolidated global forecast, since each account belongs to exactly one territory branch.

Why this answer

A single territory model with a multi-level hierarchy (regional child territories rolling into a global parent) is the native Salesforce design for Territory Forecasting, and it aggregates forecasts up the hierarchy without double counting because each account belongs to exactly one territory node. Enabling Territory Forecasting on that model lets the VP see a consolidated global roll-up.

Exam trap

The trap is assuming the user role hierarchy and the territory hierarchy are interchangeable for forecasting — they are separate structures, and only territory hierarchy supports geographic roll-ups without double counting.

How to eliminate wrong answers

Option A is wrong because User Role forecasting is based on the role hierarchy, not territory assignments — it cannot represent a geographic territory structure and would misattribute accounts that don't align with the role tree. Option C is wrong because separate territory models cannot be merged via roll-up summary fields; roll-up summaries work on object relationships (master-detail/lookup), not across territory models, and this approach would double count accounts in overlapping regions. Option D is wrong because assigning the VP as a secondary user on every territory and using Collaborative Forecast adjustments is a manual workaround that does not produce a clean hierarchical aggregation and invites double counting.

Practice this question →
23
MCQeasy

An administrator wants to ensure that sales reps record the competitor name whenever an opportunity is closed-lost. Which feature is best suited for this?

A.A Validation Rule checking if the 'StageName' is 'Closed Lost' and the 'Competitor' field is blank.
B.Einstein Opportunity Scoring
C.Sales Process dependent picklists
D.Custom Fiscal Year settings
AnswerA

A Validation Rule enforces data entry at save time, blocking closure of an opportunity as Closed Lost while the Competitor field remains blank. This directly satisfies the stem's requirement that reps must record the competitor name, since the rule cannot be bypassed through the UI.

Why this answer

A Validation Rule is the correct tool because it enforces data-entry integrity at the record level: it can fire when StageName equals 'Closed Lost' and the Competitor field is blank, blocking the save and prompting the rep to enter the competitor. This guarantees the data is captured at the moment of closing, which is exactly the requirement.

Exam trap

Sales-Con-201 often tests whether candidates reach for declarative data-integrity tools (Validation Rules) versus automation or AI features — the trap is picking Einstein or picklists because they sound 'smarter' than a simple rule.

How to eliminate wrong answers

Option B is wrong because Einstein Opportunity Scoring is a predictive AI feature that ranks opportunities by likelihood to close — it has no capability to enforce required field entry. Option C is wrong because Sales Process dependent picklists control which stage values are available based on the sales process, not whether a competitor field is populated. Option D is wrong because Custom Fiscal Year settings only affect how time periods are defined for reporting and forecasting, not data-entry validation.

Practice this question →
24
Multi-Selectmedium

A Sales Director wants to leverage Sales Cloud Einstein and generative AI features to improve rep productivity and deal closure rates. Which THREE capabilities are natively provided by Sales Cloud Einstein and Einstein generative AI? (Choose three.)

Select 3 answers
A.Automatic creation of enterprise accounting ledger entries from closed-won opportunities
B.Generative AI tools to draft personalized follow-up emails based on opportunity context
C.Einstein Call Summaries and key point extraction from recorded sales calls
D.Automated lead scoring based on historical conversion patterns
E.Automatic routing of customer support cases to tier-3 escalation queues
AnswersB, C, D

Einstein generative AI drafts follow-up emails grounded in opportunity context such as stage, products and prior activity. This satisfies the productivity and deal-closure aim, since reps send personalised outreach faster without leaving Sales Cloud, using native generative capabilities rather than third-party tooling.

Why this answer

Option B is correct because Einstein generative AI in Sales Cloud includes tools like Einstein Copilot and Sales Email that draft personalized follow-up emails grounded in opportunity context and CRM data. Option C is correct because Einstein Call Summaries (part of Einstein Conversation Insights) transcribes recorded sales calls and extracts key points, topics, and next steps natively. Option D is correct because Einstein Lead Scoring automatically scores leads using historical conversion patterns and predictive models built on Sales Cloud data.

Option A is not a Sales Cloud Einstein capability; creating accounting ledger entries is ERP/financials functionality (e.g., Accounting Seed or ERP integrations), not native Sales Cloud AI. Option E is incorrect because case routing and tier-3 escalation are Service Cloud features (e.g., Omni-Channel, Escalation Rules), not Sales Cloud Einstein generative AI capabilities.

Exam trap

Sales-Con-201 often tests the misconception that Sales Cloud Einstein includes ERP or Service Cloud functions, when its native scope is sales productivity, predictive scoring, and generative AI for sales content.

Practice this question →
25
MCQmedium

A sales team wants to ensure that all outbound emails sent through Sales Engagement automatically log against the related Contact and Opportunity records. Where is this behavior managed?

A.Through Workflow Rules on the Task object.
B.By creating an Apex trigger on the EmailMessage object.
C.In the user's personal Email Integration settings under 'Auto-Log Outbound Emails'.
D.In Sales Engagement Settings and Einstein Activity Capture configuration.
AnswerD

Sales Engagement Settings govern activity logging behaviour for cadence and outbound emails, while Einstein Activity Capture configuration controls how email and event data sync to related records. Together they determine whether outbound emails automatically log against the associated Contact and Opportunity.

Why this answer

Sales Engagement's automatic email logging is governed centrally through Sales Engagement Settings combined with Einstein Activity Capture (EAC) configuration. EAC captures email and event activity and syncs it to the appropriate Contact, Lead, and Opportunity records based on matching email addresses, while Sales Engagement Settings control whether outbound emails from cadences are logged automatically. This is an org-wide admin configuration, not a per-user or code-based behavior.

Exam trap

Sales-Con-201 often tests the misconception that email auto-logging is a per-user preference or a code-level customization, when it is actually an org-wide admin setting tied to Einstein Activity Capture.

How to eliminate wrong answers

Option A is wrong because Workflow Rules on the Task object cannot intercept outbound emails sent through Sales Engagement's email infrastructure — they only fire on Task record create/update events and have no visibility into the email send pipeline. Option B is wrong because EmailMessage records are created after the fact by Email-to-Case or standard email sending, and an Apex trigger there would be a custom workaround, not the native mechanism Sales Engagement uses for auto-logging. Option C is wrong because 'Auto-Log Outbound Emails' is not a per-user Email Integration setting — email logging in Sales Engagement is controlled at the org level via Sales Engagement Settings and EAC, not through individual user preferences.

Practice this question →
26
MCQhard

Cloud Kicks is utilizing Collaborative Forecasting and needs to ensure that forecast adjustments made by regional sales managers are auditable and do not overwrite the underlying opportunity amounts. How should the Consultant configure forecasting?

A.Create a custom currency field on the Opportunity object and use workflow rules to update amounts.
B.Enable Manager Adjustments in Collaborative Forecasts setup and configure forecast history tracking.
C.Enable Custom Opportunity Split types and apply forecast overrides at the product level.
D.Enable Pipeline Inspection and apply custom stage probabilities.
AnswerB

Manager Adjustments let regional managers override forecast categories without altering opportunity amounts, preserving the underlying data. Forecast history tracking then records each adjustment, giving the audit trail the stem demands. Together they satisfy both constraints: non-destructive adjustments and full auditability of who changed what.

Why this answer

Manager Adjustments in Collaborative Forecasts is the correct configuration because it lets managers override forecast numbers at the forecast-rollup level without modifying the underlying opportunity amounts, and enabling forecast history tracking makes those adjustments auditable over time. This satisfies both the auditability and the non-destructive override requirements.

Exam trap

Sales-Con-201 often tests the distinction between adjusting the forecast (non-destructive, auditable) and editing the opportunity (destructive) — the trap is choosing a workflow or custom field solution that silently mutates opportunity data.

How to eliminate wrong answers

Option A is wrong because creating a custom currency field and using workflow rules to update opportunity amounts would actually mutate the opportunity records, violating the requirement that adjustments not overwrite underlying amounts. Option C is wrong because Opportunity Split types and product-level forecast overrides address revenue attribution across team members, not manager-level forecast adjustments with audit history. Option D is wrong because Pipeline Inspection and custom stage probabilities affect how the pipeline is analyzed and weighted, not how manager adjustments are captured and audited.

Practice this question →
27
MCQhard

An administrator is configuring Generative AI features using Einstein Prompt Builder. The sales operations team wants sales reps to generate personalized outreach emails based on recent opportunity notes and customer industry data. Which prompt type should the administrator select in Prompt Builder?

A.Record Summary prompt type
B.Sales Email prompt type
C.Field Generation prompt type
D.Apex Guided Prompt type
AnswerB

The Sales Email prompt type is purpose-built for generating outreach emails, grounding output in CRM records such as opportunity notes and account industry fields. Selecting it satisfies the requirement for personalised emails drawn from recent opportunity and customer data.

Why this answer

The Sales Email prompt type in Einstein Prompt Builder is purpose-built to generate personalized outreach emails using CRM context such as opportunity notes and account industry data. It produces a ready-to-send email draft grounded in the record's fields, which is exactly what the sales ops team requested.

Exam trap

The trap is selecting a prompt type based on its name similarity to the task (e.g., 'Record Summary' sounds like it summarizes the record for outreach) rather than matching the prompt type's actual output format to the requirement.

How to eliminate wrong answers

Option A is wrong because a Record Summary prompt generates a narrative summary of a record (e.g., an account overview) rather than an outbound email. Option C is wrong because Field Generation prompts populate a specific field value (e.g., a custom text field) and are not designed to compose full email bodies. Option D is wrong because Apex Guided Prompt is a developer-oriented prompt type for programmatic/guided flows, not the standard sales email generation use case.

Practice this question →
28
Multi-Selecthard

Universal Containers is designing a complex sales process involving multiple product lines and wants to ensure accurate pipeline reporting and revenue distribution. Which TWO configuration steps should the Consultant recommend? (Choose two.)

Select 2 answers
A.Configure Opportunity Splits to distribute credit and revenue among multiple sales team members.
B.Enforce mandatory Global Actions for every stage transition.
C.Create a single global Sales Process with all possible stages for all product lines.
D.Assign different Sales Processes to different Opportunity Record Types.
E.Use custom roll-up summary fields on the Account to aggregate opportunity product revenue.
AnswersA, D

Opportunity Splits divide credit and revenue across sales team members, directly meeting the revenue distribution requirement. Each member's split percentage drives reporting, so pipeline and revenue figures reflect genuine contribution rather than attributing the full amount to one owner.

Why this answer

Option A is correct because Opportunity Splits allow revenue and credit to be distributed across multiple sales team members, directly supporting the requirement for accurate revenue distribution in a complex sales process. Option D is correct because assigning different Sales Processes to different Opportunity Record Types lets each product line follow its own tailored stages and picklist values, which improves pipeline reporting accuracy per product line. Option B is incorrect because Global Actions are quick-action buttons (such as Log a Call or Create a Task) and do not enforce stage-transition rules; validation rules or Flow are used for that.

Option C is incorrect because a single global Sales Process with all possible stages for every product line creates a bloated, confusing picklist and undermines accurate pipeline reporting. Option E is incorrect because roll-up summary fields on Account cannot aggregate Opportunity Product revenue directly, since OpportunityLineItem is not a direct child of Account in the roll-up summary relationship.

Exam trap

Sales-Con-201 often tests the distinction between configuration steps that directly impact pipeline reporting and revenue distribution versus those that are tangential or incorrect, such as using a single sales process for all product lines.

Practice this question →
29
MCQeasy

A sales rep is working with a prospective client who prefers communicating via phone calls and automated emails over a 14-day period. What Sales Engagement tool should the rep add the prospect to?

A.Einstein Opportunity Split
B.Enterprise Territory Model
C.Campaign Hierarchy
D.Sales Cadence
AnswerD

A Sales Cadence sequences multi-channel touchpoints—calls, automated emails and tasks—across a defined period, directly satisfying the 14-day, phone-and-email preference in the stem. It schedules each step automatically, ensuring consistent outreach without manual tracking, unlike static lists or one-off email sends.

Why this answer

Sales cadences organize multi-channel outreach steps over time.

Practice this question →
30
Multi-Selectmedium

Sales management at Cloud Kicks wants to improve pipeline visibility and accuracy using Sales Cloud Einstein features. Which TWO Einstein features should be implemented? (Choose two.)

Select 2 answers
A.Einstein Opportunity Scoring to evaluate win probability on open deals.
B.Einstein Activity Capture to automatically log emails and calendar events.
C.Einstein Discovery for writing Apex triggers on opportunity stages.
D.Einstein Next Best Action to generate email templates.
E.Einstein Bot for automated lead qualification chats on the website.
AnswersA, B

Einstein Opportunity Scoring applies predictive analytics to open deals, generating a win-probability score from historical patterns. This directly satisfies the pipeline accuracy requirement by surfacing which opportunities are likely to close, letting management forecast with data rather than rep sentiment.

Why this answer

Einstein Opportunity Scoring (A) is correct because it applies AI to open opportunities and produces a score reflecting win probability, directly improving pipeline visibility and forecast accuracy for sales management. Einstein Activity Capture (B) is correct because it automatically syncs and logs emails and calendar events to related records, giving a more complete and accurate view of deal activity without manual data entry. Together these features address both the accuracy of the pipeline (scoring) and the completeness of activity data (capture).

Einstein Discovery (C) is not for writing Apex triggers; it surfaces insights and predictions from data, and Apex triggers are code, not an Einstein feature. Einstein Next Best Action (D) delivers recommendations, not email template generation. Einstein Bot (E) handles conversational lead qualification on web channels, which is unrelated to pipeline visibility and accuracy for existing opportunities.

Exam trap

Sales-Con-201 often tests the specific capabilities of Einstein features, and candidates may confuse Einstein Discovery with automation tools or assume Next Best Action generates content rather than recommendations.

Practice this question →
31
MCQhard

An enterprise organization has a complex sales structure where regional managers need to view forecasts for all subordinate territories in the hierarchy, regardless of account ownership. How should Collaborative Forecasting be configured?

A.Use tabular reports grouped by territory with forecast quotas enabled.
B.Set up Opportunity Splits across all regional user profiles.
C.Configure Territory-based Collaborative Forecasting and assign regional managers to the parent territory nodes.
D.Create custom role hierarchies that mirror the territory structure and use User Role forecasting.
AnswerC

Territory-based Collaborative Forecasting with managers assigned to parent territory nodes grants visibility down the entire hierarchy, satisfying the requirement to view all subordinate territories regardless of account ownership. Manager hierarchies alone would not aggregate forecasts across territories, so parent-node assignment is the mechanism that delivers hierarchical roll-up.

Why this answer

Territory-based Collaborative Forecasting is designed for organizations with territory hierarchies, and assigning regional managers to parent territory nodes lets them roll up and view forecasts for all subordinate territories regardless of who owns the accounts. This matches the requirement of hierarchical forecast visibility independent of account ownership.

Exam trap

The trap is assuming the role hierarchy drives forecast rollups when the org's structure is territory-based — candidates pick 'custom role hierarchies' because it sounds like it mirrors the territory structure, but forecasting must be configured on the actual territory hierarchy.

How to eliminate wrong answers

Option A is wrong because tabular reports grouped by territory show historical data, not Collaborative Forecasting rollups, and enabling forecast quotas does not create the hierarchical forecast view required. Option B is wrong because Opportunity Splits distribute credit/revenue among users but do not provide hierarchical forecast rollup visibility across territories. Option D is wrong because custom role hierarchies with User Role forecasting rely on the role hierarchy, not territory structure, and would not reflect the territory-based hierarchy the org uses.

Practice this question →
32
MCQeasy

Which feature allows sales reps to view an interactive graphical representation of campaign hierarchy performance metrics, including total value of opportunities won across child campaigns?

A.Campaign Hierarchy Statistics
B.Enterprise Territory Hierarchy
C.Sales Path Guidance
D.Einstein Campaign Scoring
AnswerA

Campaign Hierarchy Statistics renders an interactive graphical view of metrics across a campaign tree, aggregating the total value of opportunities won from every child campaign. This directly satisfies the requirement for a visual hierarchy-wide performance representation, which flat campaign reports cannot provide.

Why this answer

Campaign Hierarchy Statistics provides an interactive graphical representation of campaign hierarchy performance, including metrics such as total value of opportunities won across child campaigns. It aggregates data from the campaign hierarchy and displays it in a visual format, allowing users to drill down into specific campaigns. This feature is specifically designed for analyzing campaign performance across parent-child relationships.

Exam trap

The trap here is confusing campaign hierarchy statistics with territory hierarchy or other analytics features; candidates may pick Enterprise Territory Hierarchy due to the word 'hierarchy'.

How to eliminate wrong answers

Option B is wrong because Enterprise Territory Hierarchy is used for managing territories and their associated accounts and opportunities, not for campaign performance metrics. Option C is wrong because Sales Path Guidance provides step-by-step guidance for sales processes, not campaign analytics. Option D is wrong because Einstein Campaign Scoring is an AI-driven scoring feature for campaigns, not a graphical hierarchy performance viewer.

Practice this question →
33
MCQeasy

Sales reps at Cloud Kicks frequently forget to log follow-up tasks after completing a discovery call. Which Sales Engagement feature can automatically create and queue follow-up tasks based on predefined cadences?

A.Sales Cadences
B.Einstein Activity Capture
C.High Velocity Sales Work Queue
D.Next Best Action
AnswerA

Sales Cadences automatically generate and queue follow-up tasks from predefined step schedules, removing reliance on rep memory. When a discovery call completes, the cadence advances and creates the next task, directly satisfying the stem's requirement for automatic task creation and queuing after each call.

Why this answer

Sales Cadences is the Sales Engagement feature that automatically creates and queues follow-up tasks based on predefined sequences of steps, including calls, emails, and tasks. When a rep completes a discovery call, the cadence can advance to the next step and generate the follow-up task automatically, ensuring nothing is forgotten.

Exam trap

Sales-Con-201 often tests the difference between logging activity (Einstein Activity Capture) and driving activity (Sales Cadences) — the trap is picking the logging tool when the requirement is automatic task creation.

How to eliminate wrong answers

Option B is wrong because Einstein Activity Capture automatically logs emails and events to Salesforce but does not create or queue follow-up tasks based on cadence logic. Option C is wrong because High Velocity Sales Work Queue is a prioritized list of leads and opportunities for reps to work, not an engine that generates follow-up tasks from cadence steps. Option D is wrong because Next Best Action surfaces recommendations via a strategy engine but does not itself create and queue cadence-driven tasks.

Practice this question →
34
MCQeasy

Which feature allows sales reps to view predefined steps, key guidance, and required fields for each stage of the sales cycle directly on an Opportunity record?

A.Kanban View
B.Sales Cadence
C.Sales Path
D.Einstein Next Best Action
AnswerC

Sales Path surfaces stage-specific guidance, predefined steps and required fields directly on the Opportunity record, satisfying the requirement to display these inline. It is driven by the opportunity's stage field, so reps see the correct checklist for each stage without leaving the record.

Why this answer

Sales Path is a feature that provides a visual guide for sales reps, showing the key stages of the sales process along with guidance for success, including required fields and predefined steps for each stage. It appears directly on the Opportunity record, helping reps navigate the sales cycle efficiently.

Exam trap

Sales-Con-201 often tests the specific features that provide on-record guidance, and candidates may confuse Sales Path with Kanban View or Einstein Next Best Action, which serve different purposes.

How to eliminate wrong answers

Option A is wrong because Kanban View is a visual representation of records in a board layout, typically used for pipeline management, but it does not show predefined steps or required fields for each stage on the record itself. Option B is wrong because Sales Cadence is a tool for managing sequences of sales activities (calls, emails) to prospects, not for displaying stage guidance on Opportunity records. Option D is wrong because Einstein Next Best Action provides recommendations for next steps based on business rules and predictive models, but it does not display predefined steps and required fields for each stage in a structured path.

Practice this question →
35
MCQmedium

Sales reps at Northern Trail Outfitters frequently send the same sequence of emails, phone calls, and LinkedIn outreach tasks to new prospects. Management wants to standardize this process to ensure consistency. Which feature should the Consultant configure?

A.Entitlement Processes
B.Opportunity Workflows
C.Marketing Cloud Account Engagement (Pardot) Engagement Studio
D.Sales Engagement Cadences
AnswerD

Sales Engagement Cadences automate a repeatable, multi-channel sequence of emails, calls and LinkedIn tasks, enforcing identical step order and timing for every prospect. This directly satisfies management's standardisation requirement, since reps follow the cadence rather than improvising their own outreach.

Why this answer

Sales Engagement (formerly High Velocity Sales) allows administrators to build Sales Cadences to standardize outreach steps for reps.

Practice this question →
36
MCQmedium

Sales leadership at Cloud Kicks wants to identify which marketing campaigns are driving the highest revenue closed-won deals. Which feature should be configured to track this multi-touch attribution?

A.Lead Conversion Mapping
B.Campaign Influence (Custom Models or Standard Models)
C.Campaign Hierarchy
D.Sales Cloud Einstein Opportunity Scoring
AnswerB

Campaign Influence models attribute revenue across every campaign touching an opportunity, using either standard or custom multi-touch models. This directly satisfies the requirement to identify which campaigns drive the highest closed-won revenue, since attribution credits each influencing campaign rather than only the primary source.

Why this answer

Campaign Influence is the Salesforce feature designed to track multi-touch attribution, allowing multiple campaigns to receive credit for influencing an opportunity. It supports both standard models (e.g., Primary Campaign Source) and custom models that define how revenue credit is distributed across campaigns. This enables sales leadership to see which campaigns contributed to closed-won revenue, directly answering the requirement.

Exam trap

Sales-Con-201 often tests the confusion between campaign hierarchy (for organizational roll-ups) and campaign influence (for multi-touch attribution), leading candidates to choose hierarchy when attribution is required.

How to eliminate wrong answers

Option A is wrong because Lead Conversion Mapping only maps lead fields to account, contact, and opportunity fields during conversion; it does not track campaign influence or attribution. Option C is wrong because Campaign Hierarchy organizes campaigns into a parent-child structure for roll-up reporting, but it does not provide multi-touch attribution or revenue credit allocation. Option D is wrong because Sales Cloud Einstein Opportunity Scoring predicts the likelihood of an opportunity closing, not which campaigns influenced it or how revenue should be attributed.

Practice this question →
37
MCQmedium

Cloud Kicks wants to measure the average duration deals spend in each sales stage to identify bottlenecks in the sales funnel. Which standard report type provides this metric?

A.Sales Pipeline Report Type
B.Opportunity History Report Type
C.Activities with Opportunities Report Type
D.Lead Conversion Time Report Type
AnswerB

The Opportunity History report type captures stage-duration data because Salesforce creates an OpportunityHistory record each time a stage changes, storing CreatedDate and the prior stage. This lets you calculate average time spent per stage, directly satisfying the requirement to identify funnel bottlenecks through stage-by-stage duration analysis.

Why this answer

The Opportunity History report type tracks stage changes over time, including how long an opportunity spent in each stage, which is exactly the metric needed to find funnel bottlenecks. It exposes stage duration and historical stage transitions.

Exam trap

The trap is choosing a report type based on its name (e.g., 'Sales Pipeline') rather than its underlying object and metric — candidates assume pipeline reports include historical duration when they only show current state.

How to eliminate wrong answers

Option A is wrong because the Sales Pipeline report type shows current pipeline by stage and value, not historical duration in each stage. Option C is wrong because Activities with Opportunities reports on activity volume and outcomes, not stage duration. Option D is wrong because Lead Conversion Time measures time from lead creation to conversion, not time spent in opportunity stages.

Practice this question →
38
MCQmedium

A multinational enterprise uses Enterprise Territory Management. The sales operations team needs to automatically assign accounts to territories based on custom postal code matching rules. What is the correct sequence of actions to achieve this?

A.Write an Apex trigger on Account to evaluate postal codes against custom territory metadata types.
B.Assign postal codes via sharing rules, then map sharing rules to territories.
C.Create a territory model, define rule criteria on the territory, run rule evaluation, and activate the model.
D.Activate the territory model first, define assignment rules, and schedule an automatic batch job.
AnswerC

Territory rule evaluation assigns accounts by matching custom criteria, here postal codes, against territory rules. Running evaluation while the model stays in Planning status lets sales ops verify assignments before activation, satisfying the requirement for automatic, rule-based assignment without prematurely exposing territories to users.

Why this answer

Territory models must be created, rules defined and run, and then activated.

Practice this question →
39
MCQhard

An administrator is setting up Collaborative Forecasting and needs to include pipeline contributions from partner channels using partner user accounts. Which forecast configuration step is required to support partner forecasting?

A.Convert all partner accounts to standard enterprise accounts with partner profiles.
B.Enable partner user forecasting in Forecasts Settings and include partner roles in the forecast hierarchy.
C.Use Experience Cloud sharing sets to roll up partner opportunities into internal user forecasts.
D.Create custom Opportunity Split types specifically for partner community licenses.
AnswerB

Enabling partner user forecasting in Forecasts Settings activates the partner-account pipeline rollup, while adding partner roles to the forecast hierarchy ensures those contributions aggregate correctly. This directly satisfies the stem's requirement to include partner-channel pipeline via partner user accounts, which standard internal-only hierarchies exclude.

Why this answer

Collaborative Forecasting in Salesforce allows partner users to contribute to forecasts when partner forecasting is explicitly enabled. The required step is to enable partner user forecasting in Forecasts Settings and ensure partner roles are included in the forecast hierarchy. This makes partner pipeline data visible and rollable into the forecast.

Without this configuration, partner opportunities are excluded from forecasts even if they are in the system.

Exam trap

Sales-Con-201 often tests the misconception that partner forecasting requires converting partner accounts or using sharing sets, when the actual requirement is enabling partner user forecasting in Forecasts Settings and including partner roles in the hierarchy.

How to eliminate wrong answers

Option A is wrong because converting partner accounts to standard enterprise accounts is unnecessary and would break the partner community model; partner forecasting works with partner accounts and partner profiles. Option C is wrong because sharing sets are used for Experience Cloud data access, not for forecast rollups; they do not integrate with Collaborative Forecasting. Option D is wrong because Opportunity Splits are for splitting credit on opportunities, not for enabling partner forecasting; custom split types are irrelevant to partner forecast inclusion.

Practice this question →
40
MCQeasy

An administrator is asked to report on the conversion rate of Leads to Opportunities by lead source. Which report type should be used?

A.Campaigns with Converted Leads
B.Leads with Converted Lead Information
C.Lead History Reports
D.Opportunities with Leads
AnswerB

Leads with Converted Lead Information joins each converted lead to its resulting opportunity, exposing both the originating lead source and the conversion outcome in one dataset. That direct lead-to-opportunity linkage satisfies the stem's requirement to calculate conversion rate by lead source, which separate lead and opportunity reports cannot correlate.

Why this answer

The 'Leads with Converted Lead Information' report type is specifically designed to report on leads and includes fields from the converted Account, Contact, and Opportunity records. This allows an admin to calculate conversion rates by grouping on Lead Source and comparing total leads to converted leads. It is the standard report type for lead conversion analysis because it joins lead data with post-conversion data.

Exam trap

The trap here is confusing lead history tracking (which shows field changes) with conversion reporting; candidates often pick 'Lead History Reports' thinking it captures conversion, but it only tracks field audit history.

How to eliminate wrong answers

Option A is wrong because 'Campaigns with Converted Leads' focuses on campaign membership and converted leads, not on lead source conversion rates across all leads. Option C is wrong because Lead History Reports track field change history (e.g., status changes) but do not provide conversion linkage to opportunities. Option D is wrong because 'Opportunities with Leads' is not a standard report type and would not correctly represent the lead-to-opportunity conversion funnel by source.

Practice this question →
41
MCQmedium

Universal Containers uses Opportunity Splits to credit multiple sales reps for a single deal. The sales operations team needs to ensure that the split amounts are automatically calculated based on the opportunity amount and the split percentage assigned to each rep. Which configuration is required to enable this?

A.Enable Opportunity Teams and add the Team related list to the page layout.
B.Use the Opportunity Amount field with a roll-up summary to calculate splits.
C.Enable Opportunity Splits and add the Splits related list to the Opportunity page layout.
D.Create a custom object to track splits and use a Flow to calculate amounts.
AnswerC

Enabling Opportunity Splits in Setup allows users to add splits to opportunities. The Splits related list must be added to the Opportunity page layout so that users can view and edit splits. Once enabled, users can assign split percentages to multiple reps, and the split amounts are automatically calculated based on the opportunity amount. This is the standard configuration to meet the requirement.

Why this answer

Opportunity Splits is a standard feature that allows crediting multiple reps for an opportunity. When enabled, and the Splits related list is added to the page layout, users can assign split percentages to each rep. Salesforce automatically calculates the split amount based on the opportunity amount and the percentage.

This meets the requirement without custom development.

Exam trap

The trap here is confusing Opportunity Teams with Opportunity Splits; Teams are for collaboration, while Splits are for revenue crediting and require the Splits related list.

Practice this question →
42
Multi-Selecthard

An administrator is preparing to implement Sales Cloud Einstein Generative AI Prompt Builder. Which THREE capabilities does Prompt Builder provide for sales users? (Choose three.)

Select 3 answers
A.Creating custom prompt templates infused with CRM merge fields and Apex grounding.
B.Training deep learning neural networks on raw database backups.
C.Automatically writing custom Apex triggers for backend integrations.
D.Populating specific CRM record fields using field generation prompt templates.
E.Generating personalized sales emails using customer and opportunity context.
AnswersA, D, E

Prompt Builder lets admins build reusable prompt templates that merge CRM record fields and ground responses in Apex-defined data, satisfying the stem's capability requirement. This grounding constrains generative output to trusted Salesforce data rather than relying on the model's general knowledge.

Why this answer

Prompt Builder lets sales users build reusable prompt templates that blend free-text instructions with CRM merge fields (and Apex-defined grounding) to inject record context, so option A is correct. It also supports field generation prompt templates, which write AI-generated values directly into specified CRM record fields, making option D correct. Additionally, Prompt Builder includes email prompt templates that produce personalized sales emails using customer and opportunity context, so option E is correct.

Option B is wrong because Prompt Builder does not train deep learning neural networks on raw database backups, and option C is wrong because it does not auto-generate Apex triggers for backend integrations.

Exam trap

The trap is confusing Prompt Builder's generative capabilities with broader AI/ML features like model training or code generation — candidates may overestimate what Prompt Builder can do and pick options B or C.

Practice this question →
43
Multi-Selectmedium

Northern Trail Outfitters wants to track campaign ROI and multi-touch attribution. Which THREE features should the administrator configure? (Choose three.)

Select 3 answers
A.Einstein Opportunity Scoring weight parameters.
B.Campaign Hierarchy to roll up metrics across parent and child campaigns.
C.Campaign Member Status values to track engagement stages (e.g., Sent, Responded).
D.Enterprise Territory Assignment rules.
E.Campaign Influence models to attribute revenue across multiple touchpoint campaigns.
AnswersB, C, E

Campaign Hierarchy rolls child campaign metrics up to parent campaigns, aggregating responses, revenue and costs across related initiatives. This satisfies multi-touch attribution and ROI tracking by letting Northern Trail Outfitters report performance at programme level rather than per isolated campaign.

Why this answer

Option B is correct because Campaign Hierarchy lets you roll up metrics such as responses, leads, and revenue from child campaigns into parent campaigns, which is essential for tracking ROI across related campaigns. Option C is correct because Campaign Member Status values define the engagement stages (e.g., Sent, Responded) that let you measure response rates and conversion progress for each campaign. Option E is correct because Campaign Influence models enable multi-touch attribution by assigning revenue credit across multiple campaigns that touched an opportunity, directly supporting multi-touch attribution.

Option A is not correct because Einstein Opportunity Scoring weights affect opportunity scoring, not campaign ROI or attribution. Option D is not correct because Enterprise Territory Assignment rules manage territory-based record assignment, not campaign attribution or ROI tracking.

Exam trap

Sales-Con-201 often tests the confusion between campaign analytics features and unrelated tools like Einstein Scoring or Territory Assignment, which do not address ROI or attribution.

Practice this question →
44
MCQeasy

Which feature in Sales Cloud allows managers to view a visual pipeline board where sales reps can drag and drop opportunities across different stages?

A.Kanban View
B.Dashboard Component
C.Sales Path
D.Work Queue
AnswerA

Kanban View renders opportunities as draggable cards arranged in columns by stage, giving managers the visual pipeline board described. Dragging a card updates the opportunity's stage, matching the stem's requirement for drag-and-drop movement across stages.

Why this answer

Kanban View in Sales Cloud displays opportunities as cards in columns by stage, and users can drag and drop cards between columns to change the stage. It is the standard visual pipeline board feature for Opportunity list views.

Exam trap

The trap is confusing Sales Path (record-level guidance) with Kanban View (list-level drag-and-drop board) — both relate to stages, but only Kanban provides the visual board with drag-and-drop across records.

How to eliminate wrong answers

Option B is wrong because a Dashboard Component displays aggregated charts/metrics, not an interactive drag-and-drop pipeline board. Option C is wrong because Sales Path is a guidance component that shows key fields and tips for each stage on a record page; it does not provide a drag-and-drop board across records. Option D is wrong because Work Queue is not a standard Sales Cloud pipeline board feature for dragging opportunities across stages (it relates to task/lead assignment in some contexts).

Practice this question →
45
Multi-Selectmedium

When configuring Collaborative Forecasting, which THREE configurations can an administrator customize? (Choose three.)

Select 3 answers
A.Automatic generation of Apex test classes for forecast models.
B.Custom Date Ranges or Fiscal Periods for forecasting
C.Forecast Currency Display (Corporate vs User currency)
D.The underlying database schema for forecast rollup tables.
E.Forecast Types (e.g., Revenue, Quantity, Splits)
AnswersB, C, E

Custom date ranges and fiscal periods let administrators align forecasts with the organisation's actual reporting calendar rather than the default Gregorian periods. This satisfies the stem's requirement for customisable forecasting configuration, since Collaborative Forecasting supports defining fiscal year settings and date-range options that determine how pipeline projections are bucketed and rolled up.

Why this answer

In Collaborative Forecasting, administrators can customize the forecast hierarchy's time dimension by selecting Custom Date Ranges or Fiscal Periods (B), which determines whether forecasts are calculated using standard fiscal periods or custom date ranges defined in the org. Administrators can also configure Forecast Currency Display (C), choosing whether forecast amounts are shown in the corporate currency or the user's personal currency, which is essential for global organizations. Additionally, Forecast Types (E) such as Revenue, Quantity, Product Family, and Opportunity Splits can be enabled and customized, allowing different forecast metrics to be tracked.

Options A and D are incorrect because Collaborative Forecasting does not auto-generate Apex test classes for forecast models, nor does it expose the underlying database schema of forecast rollup tables for administrator customization.

Exam trap

Sales-Con-201 often tests whether candidates know the boundary between admin-configurable forecast settings and platform-internal mechanics — the trap is selecting database schema or Apex options that sound technical but are not admin-facing.

Practice this question →
46
MCQeasy

A sales manager wants to view a breakdown of pipeline stages by sales representative in a single visual component. Which dashboard component type is most appropriate?

A.Gauge Component
B.Line Chart
C.Stacked Bar Chart
D.Metric Component
AnswerC

A stacked bar chart plots each sales representative on one axis and segments each bar by pipeline stage, showing both totals and stage composition in a single visual. This satisfies the requirement to break down pipeline stages by representative within one dashboard component.

Why this answer

A stacked bar chart plots each pipeline stage as a bar segment and stacks segments per sales representative, letting the manager compare both total pipeline per rep and the stage-by-stage composition in one visual. This directly satisfies the 'breakdown of pipeline stages by sales representative' requirement in a single component.

Exam trap

The trap is picking a chart type based on familiarity rather than matching the component's dimensional capability to the question — candidates often choose line charts for anything 'over categories' when the requirement is really compositional breakdown.

How to eliminate wrong answers

Option A is wrong because a gauge component displays a single value against a target or threshold (e.g., quota attainment percentage) and cannot show a multi-category, multi-stage breakdown. Option B is wrong because a line chart is designed for trends over time, not categorical composition across reps and stages. Option D is wrong because a metric component shows one aggregated KPI number (e.g., total pipeline value) with no dimensional breakdown.

Practice this question →
47
MCQeasy

A sales representative needs to know the probability of winning an open opportunity based on historical win rates of similar deals. Which feature provides this insight directly on the Opportunity record page?

A.Einstein Activity Capture Insights
B.Sales Path Guidance
C.Collaborative Forecasting Quotas
D.Einstein Opportunity Scoring
AnswerD

Einstein Opportunity Scoring applies predictive analytics to historical opportunity data, generating a score that reflects likelihood of winning. It surfaces this directly on the Opportunity record page, satisfying the requirement for win-probability insight without manual calculation.

Why this answer

Einstein Opportunity Scoring uses historical data and AI to assign a score (0–100) to open opportunities, indicating the likelihood of winning. This score appears directly on the Opportunity record page, giving sales reps immediate insight into deal health. It analyzes patterns from closed-won and closed-lost deals to predict outcomes, making it the correct choice for probability-based insights.

Exam trap

Sales-Con-201 often tests the confusion between activity capture insights and predictive scoring, leading candidates to choose Einstein Activity Capture Insights when asked about win probability.

How to eliminate wrong answers

Option A is wrong because Einstein Activity Capture Insights focuses on logging and analyzing email and calendar activities, not on predicting win probability. Option B is wrong because Sales Path Guidance provides a visual guide for stages and key fields, but does not calculate win probability. Option C is wrong because Collaborative Forecasting Quotas are used for setting and tracking sales targets, not for scoring individual opportunities.

Practice this question →
48
MCQeasy

A sales rep wants to quickly log a completed phone call against an opportunity and schedule a follow-up task for next Tuesday. Which feature should the rep use?

A.Global Search quick filter
B.Sales Cadence Work Queue
C.Einstein Activity Capture dashboard
D.Activity Composer (Log a Call / New Task tabs)
AnswerD

Activity Composer presents Log a Call and New Task tabs in one interface, letting the rep record the completed call against the opportunity and create the follow-up task without navigating away. This single-screen flow satisfies both the logging and Tuesday scheduling requirements efficiently.

Why this answer

Activity Composer provides Log a Call and New Task tabs directly on the record page, letting the rep log a completed call and create a follow-up task in one place. It is the standard, efficient way to capture activity and schedule follow-ups against an opportunity.

Exam trap

The trap is selecting an automation or search feature (Sales Cadence, Global Search) when the question asks for manual, immediate activity logging plus task scheduling — candidates overlook the simple Activity Composer in favor of more 'advanced' sounding options.

How to eliminate wrong answers

Option A is wrong because Global Search quick filter is for finding records, not for logging calls or creating tasks. Option B is wrong because Sales Cadence Work Queue is for executing predefined outreach sequences, not ad-hoc logging of a completed call plus a one-off follow-up task. Option C is wrong because Einstein Activity Capture dashboard displays captured email/calendar activity; it does not let the rep manually log a call and schedule a task.

Practice this question →
49
Multi-Selecthard

Universal Containers is implementing Enterprise Territory Management and needs to define how users are assigned to territories and how forecasts relate to those territories. Which TWO statements are true regarding Enterprise Territory Management functionality? (Choose two.)

Select 2 answers
A.Territory types are mandatory and restrict the number of child territories allowed.
B.Collaborative Forecasts can be configured to use territory hierarchies for forecast rollups.
C.Territory assignment rules can only be executed manually by system administrators.
D.Account sharing rules must be manually coded using Apex when using Enterprise Territory Management.
E.A user can be assigned to multiple territories within the same territory model.
AnswersB, E

Collaborative Forecasts supports territory-based forecast rollups, letting forecast amounts aggregate through the territory hierarchy rather than only the role hierarchy. This directly satisfies the requirement that forecasts relate to territories, so managers see projections aligned to their territory structure.

Why this answer

Option B is correct because Collaborative Forecasts in Salesforce can be configured with territory hierarchies as the forecast rollup source, so forecasts aggregate up the territory model's parent-child structure rather than only through the role hierarchy. Option E is correct because Enterprise Territory Management allows a single user to be assigned to multiple territories within the same territory model, which is a core benefit of the feature for matrixed or overlapping coverage. Option A is incorrect because territory types are not mandatory and do not restrict the number of child territories; they are optional labels used to categorize and filter territories.

Option C is incorrect because territory assignment rules can run automatically on a schedule or on account/user changes, not only manually by admins. Option D is incorrect because Enterprise Territory Management provides declarative territory-based sharing and does not require hand-coded Apex sharing rules.

Exam trap

Sales-Con-201 often tests the misconception that territory types are mandatory or that assignment rules must be run manually, when in fact types are optional and rules can be scheduled.

Practice this question →
50
MCQeasy

Which Salesforce feature uses machine learning to score leads based on historical conversion data, showing sales reps which leads are most likely to convert?

A.Lead Assignment Rules
B.Sales Cadence Scoring
C.Web-to-Lead Auto-Response Rules
D.Einstein Lead Scoring
AnswerD

Einstein Lead Scoring applies machine learning to historical conversion and loss data, producing a score that ranks leads by likelihood to convert. This directly satisfies the requirement to surface the most promising leads to reps.

Why this answer

Einstein Lead Scoring uses machine learning models trained on an org's historical Lead conversion data to assign each Lead a score from 0 to 99, indicating the likelihood of conversion. Sales reps use these scores to prioritize outreach, focusing on Leads most likely to convert.

Exam trap

The trap is confusing deterministic routing features (Assignment Rules, Auto-Response Rules) with predictive ML scoring — candidates must recognize that only Einstein Lead Scoring uses historical conversion data and machine learning.

How to eliminate wrong answers

Option A is wrong because Lead Assignment Rules are deterministic routing rules that assign Leads to owners/queues based on field criteria — they do not use machine learning or predict conversion likelihood. Option B is wrong because 'Sales Cadence Scoring' is not a Salesforce feature; sales cadences are sequences of touchpoints, and while High Velocity Sales tracks cadence engagement, it does not score Leads via ML for conversion probability. Option C is wrong because Web-to-Lead Auto-Response Rules simply send an automated email to Leads captured from web forms — they have no predictive scoring capability.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Sales Lifecycle questions.

Start 20-question session