Overview
Sales and Marketing Applications covers the standard Sales Cloud features an administrator configures. It starts with the sales process itself: lead statuses, opportunity stages with their probabilities and forecast categories, and Path to guide reps through each stage. It extends to sales productivity tools such as forecasting, territory management, Einstein lead and opportunity scoring and the Assistant on the home page, and to marketing features such as lead assignment rules, lead conversion and campaigns with campaign members.
The section exists because most orgs start with sales, and admins are expected to translate a sales manager's request into the correct standard feature rather than custom build. It draws on record types and business processes from Object Manager, on assignment and approval logic from Automation, and on dashboards from Data and Analytics Management.
How it's tested
Questions describe a sales or marketing manager's request: route web leads to the right team, keep data during conversion, forecast by region, or measure which campaign influenced a deal. You choose the standard feature or setting that delivers it, usually with the least custom work, and predict what a feature will do with existing records.
-
Standard feature first
A request sounds like it needs custom work, and the answer is a built-in feature such as lead field mapping, Path, campaign hierarchy or territory assignment rules.
-
What happens on conversion
You predict which records lead conversion creates or updates and where each lead field's data ends up.
-
Which hierarchy applies
A forecasting or visibility request forces a choice between the role hierarchy, the forecast hierarchy and the territory model.
A sales director wants forecasts rolled up by geographic territory, while account access should follow territories rather than the management chain. The role hierarchy follows reporting lines, so it cannot represent territories that cut across managers. Enterprise Territory Management assigns accounts to territories with rules, grants territory users access, and can drive territory-based forecasts. Recognizing that two different hierarchies are in play is what eliminates role-based answers.
Objectives 3
Official objectives from the Salesforce outline, in outline order.
3.1 Given a scenario, identify the capabilities and implications of the sales process (for example: leads, opportunities, path).Lead statuses, opportunity stages and guided selling with Path.
- What it means
- The sales process runs from leads (unqualified prospects with a status) to opportunities (deals with a stage, amount and close date). Each opportunity stage carries a default probability and forecast category, and Path displays the stages of a record type as a visual track with key fields and guidance for success at each step.
- What to understand
- Stage values come from the sales process of the opportunity's record type, so different teams can have different stages. Changing a stage updates probability and forecast category by default, which feeds forecasts and pipeline dashboards. Path is configured per object and record type and does not enforce anything by itself; required progress still needs validation rules or automation.
- How it shows up
- A manager wants reps to see what to do at each stage and the critical fields to complete, and the answer is Path with key fields and guidance rather than a custom component.
- Common confusion
- Path guidance is advice shown to users; candidates sometimes pick it as a way to block skipping stages, which it cannot do.
3.2 Given a scenario, apply the appropriate sales productivity features using opportunity tools (for example: dashboards, lead scoring, Einstein for Sales, opportunity scoring, grading, and home page assistant, forecasting, territory management).Prioritizing, forecasting and organizing the sales team's work.
- What it means
- Productivity tools help reps focus and managers plan: Einstein Lead Scoring and Opportunity Scoring rank records by likelihood to convert or win from historical data, grading (in marketing automation) rates prospect fit, the Assistant on the Lightning home page surfaces items such as deals with no recent activity, Collaborative Forecasts roll up opportunity amounts by forecast category, and Enterprise Territory Management organizes accounts into territories.
- What to understand
- Forecasts roll up through a forecast hierarchy based on the role hierarchy, or through territories when territory forecasting is used, grouped by forecast category such as Pipeline, Best Case, Commit and Closed. Territory models assign accounts by rules and grant access independent of the role hierarchy, with only one model active at a time. Einstein scoring needs enough historical data to build a model, and scores are guidance, not automation.
- How it shows up
- A director wants regional forecasts that do not match reporting lines, or reps want to know which leads to call first, and you match the request to territories or Einstein scoring.
- Common confusion
- Scoring and grading measure different things: a score reflects likelihood or engagement, while a grade reflects how well the prospect fits the ideal customer profile.
3.3 Describe the capabilities of lead automation tools and campaign management (for example: leads, lead convert, lead assignment rules, campaign, and campaign members).Routing and converting leads, and tracking marketing campaigns.
- What it means
- Lead assignment rules route new leads to users or queues by rule entries evaluated in order, with one active rule per org. Lead conversion turns a qualified lead into an account and contact, optionally an opportunity, and copies mapped custom fields. Campaigns track marketing initiatives, with leads and contacts added as campaign members that each carry a member status such as Sent or Responded.
- What to understand
- Only fields mapped in the lead field mapping carry over during conversion, and the converted lead is no longer available as a normal record. Assignment rules run for web-to-lead and imports when selected, and for manual edits only when the assignment checkbox is used. Creating and editing campaigns requires the Marketing User feature license, and campaign hierarchies roll statistics up from child to parent campaigns.
- How it shows up
- Data entered on leads disappears after conversion, or marketing wants to see total responses across a program of events, and you choose field mapping or a campaign hierarchy.
- Common confusion
- A campaign member is a link between a campaign and a lead or contact, not a copy of that person, so updating the member status does not change the lead or contact record.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Lead conversion
Converting a qualified lead creates or matches an account and contact and can create an opportunity, carrying campaign history and activities to the new records.
- Remember
- Custom lead fields copy over only if they are mapped to custom fields on account, contact or opportunity in the lead field mapping.
- Tested as
- Appears in data-loss and duplicate scenarios after conversion.
- Trap
- Assuming every custom lead field transfers automatically.
-
Lead assignment rules
Rules with ordered entries that assign new leads to a user or queue based on field criteria, with only one rule active at a time.
- Remember
- Entries are evaluated in order and the first match wins, so put specific criteria above general ones.
- Tested as
- Scenarios about routing web leads by region or product interest.
- Trap
- Placing a catch-all entry first, which captures every lead before the specific entries run.
-
Opportunity stage, probability and forecast category
Each stage value has a default probability and maps to a forecast category such as Pipeline, Best Case, Commit, Closed or Omitted.
- Remember
- Moving the stage changes probability and forecast category, which drives forecasts and weighted pipeline reports.
- Tested as
- Questions about why a deal appears in a forecast bucket.
- Trap
- Editing probability by hand and expecting the forecast category to follow.
-
Path
A visual stage track on records for a chosen object and record type, with key fields and guidance for success at each step.
- Remember
- Path guides; it does not enforce stage order or required fields.
- Tested as
- The usual answer when managers want reps coached through a process.
- Trap
- Choosing Path to prevent stage skipping, which needs a validation rule.
-
Collaborative Forecasts
Forecasting that rolls opportunity amounts or quantities up a forecast hierarchy by forecast category, with manager adjustments and quotas.
- Remember
- Users must be enabled in the forecast hierarchy, and forecast types define which measure and date are used.
- Tested as
- Scenarios about managers reviewing and adjusting team forecasts.
- Trap
- Expecting forecasts to appear for users who were never added to the forecast hierarchy.
-
Enterprise Territory Management
A territory model of territory types and territories with account assignment rules that grant access and support territory-based forecasting.
- Remember
- Only one territory model can be active, and it operates separately from the role hierarchy.
- Tested as
- Requests where sales coverage follows geography or segment rather than reporting lines.
- Trap
- Rebuilding the role hierarchy to represent territories.
-
Einstein Lead Scoring and Opportunity Scoring
AI models that score leads by likelihood to convert and opportunities by likelihood to close, showing the top contributing factors.
- Remember
- They need enough historical records to train and they inform prioritization rather than change records.
- Tested as
- Questions asking how reps can prioritize without manual scoring rules.
- Trap
- Treating a score as an assignment or automation trigger with no further configuration.
-
Score vs. grade
Scoring measures interest or likelihood; grading measures how closely a prospect matches the ideal customer profile.
- Remember
- A prospect can be highly engaged but a poor fit, so both are used together.
- Tested as
- Appears as a terminology distinction in marketing scenarios.
- Trap
- Using the terms interchangeably.
-
Assistant on the home page
A Lightning home page component that surfaces timely updates such as overdue tasks, new leads and opportunities with no recent activity.
- Remember
- It is a productivity aid configured on the home page, not a report.
- Tested as
- Scenarios about helping reps see what needs attention each morning.
- Trap
- Building a custom dashboard when the standard Assistant meets the need.
-
Campaign member status
Each campaign has its own list of member statuses, and at least one must count as responded.
- Remember
- Responded statuses drive campaign response metrics and statistics.
- Tested as
- Questions about tracking responses per event or email.
- Trap
- Expecting one global status list shared by all campaigns.
-
Campaign hierarchy and Marketing User
Campaigns can be organized in a parent-child hierarchy with roll-up statistics, and creating or editing campaigns requires the Marketing User feature license.
- Remember
- Missing campaign permissions are often the Marketing User checkbox on the user record.
- Tested as
- Program-level reporting and permission troubleshooting scenarios.
- Trap
- Adding object permissions repeatedly while the feature license is still unchecked.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Role hierarchy vs. forecast hierarchy vs. territory model
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Role hierarchy | Record visibility by reporting line | Opens access upward to managers | Reshaping it to represent territories |
| Forecast hierarchy | Who sees and adjusts whose forecasts | Built from roles; users must be forecast-enabled | Assuming every role member appears automatically |
| Territory model | Accounts grouped by rule-based territories | Grants access and forecasts outside reporting lines | Activating two models at once |
Lead assignment rule vs. lead conversion vs. campaign member
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Lead assignment rule | Routes new leads to a user or queue | Runs on creation when triggered; first match wins | Expecting it to reassign every edit automatically |
| Lead conversion | Turns a lead into account, contact and optional opportunity | Copies only mapped fields | Losing unmapped custom field data |
| Campaign member | Links a lead or contact to a campaign with a status | Status tracks response per campaign | Thinking status edits change the lead itself |
Einstein scoring vs. grading vs. Path
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Einstein scoring | Model-based likelihood to convert or close | Learns from historical outcomes | Expecting it to work without enough data |
| Grading | Fit against the ideal customer profile | Measures fit, not interest | Treating a high grade as high engagement |
| Path | Guidance and key fields per stage | Coaches users without enforcing rules | Using it as a stage-control mechanism |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Custom automation for conversion data
- What candidates pick
- Build a flow to copy lead data to the contact after conversion.
- Why it looks right
- Flows can copy almost anything, so it looks robust.
- Why it's wrong
- Lead field mapping already copies custom lead fields to mapped custom fields on account, contact and opportunity without automation to maintain.
Clue to watch for The scenario says lead data is missing after conversion and asks for the most efficient fix.
-
Path as enforcement
- What candidates pick
- Configure Path so reps cannot skip stages or leave fields blank.
- Why it looks right
- Path displays key fields at each stage, which sounds like control.
- Why it's wrong
- Path offers guidance only; preventing a stage change without data needs a validation rule.
Clue to watch for Words such as prevent, require or must not appear in the request.
-
Roles for territories
- What candidates pick
- Add regional roles to the role hierarchy so regional teams share accounts.
- Why it looks right
- The role hierarchy is the familiar sharing tool.
- Why it's wrong
- Territories often cut across management lines and an account can sit in more than one territory; Enterprise Territory Management models this with rules and its own access.
Clue to watch for Coverage is defined by geography, segment or named accounts rather than who reports to whom.
-
Catch-all entry first
- What candidates pick
- Put the default queue entry at the top of the lead assignment rule for safety.
- Why it looks right
- It seems to guarantee no lead is unassigned.
- Why it's wrong
- Entries are evaluated in order and the first match wins, so a catch-all at the top captures every lead and the specific entries never run.
Clue to watch for Leads are all landing in one queue despite detailed criteria.
-
Object permissions for campaigns
- What candidates pick
- Grant Create on Campaign through a permission set and stop there.
- Why it looks right
- Object permissions usually control creation.
- Why it's wrong
- Campaign management also requires the Marketing User feature license on the user record.
Clue to watch for A user with object access still cannot create or edit campaigns.
-
Score equals fit
- What candidates pick
- Route leads with the highest score straight to senior reps as the best-fit prospects.
- Why it looks right
- A high number feels like the best lead.
- Why it's wrong
- A score reflects interest or likelihood, while a grade reflects fit, so a high score alone does not mean an ideal customer.
Clue to watch for The scenario distinguishes engagement from match to the target profile.
Answer framework
When a sales or marketing request appears, trace it along the lead-to-revenue cycle and pick the standard feature for that stage.
- Place the request in the cycle: lead capture and routing, qualification and conversion, opportunity progress, forecasting and coverage, or campaign measurement.
- For routing, use lead assignment rules with specific entries ordered before general ones, assigning to users or queues.
- For conversion problems, check the lead field mapping and converted status values before considering automation.
- For stages and forecasts, confirm the sales process, stage probabilities and forecast categories, and decide whether roles or territories define the rollup.
- For marketing, use campaigns with member statuses and hierarchies, and confirm users hold the Marketing User feature license. Only then consider a flow or custom field, and only for the part of the request no standard feature covers.
Practice question
Want more like this? The Salesforce Admin practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Work through the cycle in the order a lead moves. Create a web-to-lead form or import a few leads, route them with an assignment rule, convert one with mapped custom fields, and watch which records are created. Then advance the resulting opportunity through stages with Path enabled and look at how probability and forecast category change.
High-priority concepts are lead conversion mapping, assignment rule ordering, stage to forecast category mapping, and the Marketing User license for campaigns. Build a parent campaign with two child campaigns, add members with different statuses, and confirm how the hierarchy statistics roll up.
Commonly underestimated areas are forecasting and territories, because many candidates have never configured them. Read how forecast types and the forecast hierarchy work, and compare territory assignment with the role hierarchy until you can explain why a territory model exists. Also know the purpose and data needs of Einstein scoring and the difference between score and grade.
Afterwards, practice scenarios phrased as a sales manager's complaint and name the standard feature before reading the options.
FAQ
How many questions come from Sales and Marketing Applications?
The section is 10% of the exam, which suggests about six of the 60 scored questions as a planning estimate.
What happens to a lead when it is converted?
Salesforce creates or matches an account and contact, optionally creates an opportunity, and moves related activities and campaign history over. Only mapped custom fields carry their values, and the lead is marked converted rather than staying as a working record.
Do I need hands-on experience with forecasting and territories?
It helps, because scenarios ask which feature fits a coverage or rollup requirement. At minimum, know that forecasts roll up by forecast category through a forecast hierarchy and that territory models assign accounts by rules independently of roles.
Why can't a user create campaigns even with object permissions?
Campaign management requires the Marketing User feature license, enabled with a checkbox on the user record, in addition to object permissions.
Is Einstein covered in depth?
The guide names Einstein for Sales and lead and opportunity scoring as productivity tools. Focus on what each one helps users do and what it needs, not on model internals.
What is the difference between Path and a validation rule?
Path shows stages, key fields and guidance to coach users, while a validation rule blocks a save that breaks a condition. Use Path to guide and a validation rule to enforce.
How does this section connect to Automation?
Lead assignment rules appear here as a sales feature and in Automation as one tool among several. Know when an assignment rule is enough and when a flow is needed for routing logic it cannot express.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 3 knowledge
You have covered stages and Path, forecasting and territories, Einstein scoring, lead routing and conversion, and campaigns. Check whether you can pick the standard feature over a custom build in timed scenarios.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the Salesforce Admin AI tutor Get any concept explained your way