ADM-201 - Sales and Marketing Applications (10% of the exam) - Section 3.1

Configure the sales process using opportunities, opportunity stages, sales paths, products, price books, and opportunity productivity tools.

Configure opportunities with stages, sales paths, and forecast categories that move a deal through the pipeline, and attach products and price books to capture revenue. Apply opportunity productivity tools such as similar opportunities and Big Deal Alerts, and recognise how opportunity stage drives forecasting and reporting.

OpportunitiesOpportunity stagesSales pathPrice booksForecast categories

Practice question for this objective

Free sampleSales and Marketing Applicationsmedium

An administrator enables a sales path (Path) on the Opportunity object. What does the sales path actually provide to users working an opportunity?

AIt creates a second, independent set of stages that runs in parallel with the standard opportunity stage picklist.
BIt presents the existing stage picklist as a guided sequence, with key fields and guidance for success configurable per stage, without adding new stage values. Correct
CIt converts each opportunity stage into its own record type, each with a distinct page layout assigned to it.
DIt replaces the opportunity Amount with a weighted amount calculated from each stage's probability percentage.

Recognise that a sales path guides users through the existing opportunity stages with key fields and guidance, not by creating new stages. A path is a visual overlay on the opportunity stage picklist that lets the administrator define key fields and guidance for success per stage, improving adoption while the underlying stage values stay unchanged.

Why A is wrong: Tempting because the path looks like stages, but it is built on the existing stage picklist rather than introducing a separate parallel set of stages.

Why B is correct: Correct: a path sits on top of the stage picklist and surfaces the key fields and guidance for success for each stage, helping reps without changing the stages themselves.

Why C is wrong: This confuses paths with record types; a path guides users through stages but does not generate record types or reassign page layouts.

Why D is wrong: Weighted pipeline is a reporting concept; a path offers guidance and key fields and does not overwrite the Amount field with a probability calculation.

See more ADM-201 practice questions, answers explained.

Exam traps in Sales and Marketing Applications

Answers that look right on this material and are not. Each one is a distractor from a different question in the ADM-201 bank for this domain.

Forecast categories are set independently on every opportunity and are not influenced by the stage the record is currently in.
Why it is wrong: Tempting because the Forecast Category field can be edited on a record, but the field is driven by a stage-to-category mapping by default, so the stage does influence it.
Change the Probability percentage on the Negotiation/Review stage to 100 per cent
Why it is wrong: Probability drives expected-revenue calculations, not which forecast bucket a stage falls into; raising it does not move the stage from Best Case to Commit.
Build a record-triggered flow that updates a custom Forecast Amount field whenever an opportunity reaches the Verbal Agreement stage.
Why it is wrong: A flow can populate a custom field, but forecast rollups are driven by the stage's forecast category rather than a custom field, so the standard Commit total would still ignore these opportunities.

Examworthy is not affiliated with or endorsed by Salesforce. Original, blueprint-aligned practice material only.