Overview
Practical Application of Agentforce Sales Expertise carries 24% of the exam and five objectives. Some study guides split it into two parts, a first set on end-to-end process design, extensibility and security, and a second on products, quotes and campaign, lead and opportunity scenarios, but the weight is reported as one section.
You are expected to configure a complete sales process from Lead to Opportunity to Quote to Close, using record types, sales processes, paths, assignment rules and conversion mapping. You decide when declarative tools are not enough and custom development, AppExchange apps, other Salesforce products or productivity tools such as email integration, Slack and the mobile app should be added. You also select a security model from organization-wide defaults, roles, sharing rules, teams and permission sets, and design the product catalog, price books, quotes and multi-currency setup.
How it's tested
Scenarios give a set of business requirements and ask you to design or fix part of the sales data model or process. You choose the object, feature or sharing mechanism that meets the requirement with the least customization. Distractors often describe features that exist but do not fit the stated volume, ownership or currency constraint.
-
Object behavior detail
Questions test precise rules for leads, opportunities, products, price books, quotes, schedules and currencies, such as which records sync or convert.
-
Least privilege access
A team needs access to specific records, and you choose the narrowest sharing tool that satisfies the requirement.
-
Declarative versus extend
A requirement exceeds standard configuration, and you decide between flow, Apex, an AppExchange app, another Salesforce product or a productivity tool.
A manufacturer quotes the same opportunity three ways and wants the chosen quote's line items reflected on the opportunity. Only one quote can sync with an opportunity at a time, and syncing copies quote line items to opportunity products in both directions while synced. So the rep should start sync on the chosen quote, which automatically ends any earlier sync, rather than copying products by hand or building a flow.
Objectives 5
Official objectives from the Salesforce outline, in outline order.
3.1 Given a set of requirements, construct an end-to-end sales process within Salesforce that supports the business from Lead to Opportunity to Quote to Close.Configuring the full sales flow on standard objects.
- What it means
- You design how a lead is captured, qualified, assigned and converted, how the resulting opportunity moves through stages, how a quote is produced and how the deal closes. Each step uses standard objects and declarative features wherever possible.
- What to understand
- Capture leads through web-to-lead, imports or integrations, and route them with assignment rules and queues. Use lead processes and record types for different qualification paths. Map custom lead fields to account, contact and opportunity fields for conversion. Define sales processes that control available stages per opportunity record type, and add a path with guidance. Generate quotes with templates, use approval processes for discounts, and close with Closed Won or Closed Lost reasons captured for reporting.
- How it shows up
- Requirements describe several sales teams and steps, and you choose the record types, processes and automation that model them.
- Common confusion
- Forgetting that custom lead fields need field mapping before their values carry over at conversion.
3.2 Given a scenario, determine when it's appropriate to extend declarative development with custom development, third-party applications, Salesforce products, or productivity tools (email integrations, Slack, Salesforce Mobile).Choosing when to go beyond clicks and which extension fits.
- What it means
- Most sales requirements are met with flows, validation rules, formulas and page configuration. Some need more: complex logic or integrations may require Apex, a gap may already be solved by an AppExchange app, and some needs point to other Salesforce products or to productivity tools.
- What to understand
- Use the order of preference: standard feature, declarative automation, AppExchange or other Salesforce product, then custom code. Choose Apex when logic is too complex for flow or when bulk processing and callouts need fine control. Consider Revenue Cloud for complex configure-price-quote needs, Salesforce Maps for route planning, Slack for deal rooms and alerts, Outlook or Gmail integration for email-centric reps, and the Salesforce mobile app for field sellers. Weigh cost, maintenance and upgrade impact.
- How it shows up
- A requirement goes beyond a simple configuration, and you pick the extension type that solves it with the least long-term burden.
- Common confusion
- Writing custom code for a capability that an existing Salesforce product or AppExchange app already provides.
3.3 Given a set of business requirements, identify the appropriate security model (sharing rules, role hierarchy, Account Teams, Opportunity Teams, permission sets, permission set groups).Designing record and object access for sales teams.
- What it means
- Sales data access combines object and field permissions with record-level sharing. Organization-wide defaults set the baseline, the role hierarchy opens access upward, sharing rules widen it for groups, and teams grant access on individual records. Permission sets and groups add object and feature permissions.
- What to understand
- Set opportunity organization-wide defaults to Private when reps should not see each other's deals, then open access with roles and sharing rules. Owner-based and criteria-based sharing rules widen access for groups, not individuals. Account Teams and Opportunity Teams add named collaborators with defined access per record, and Opportunity Teams are required for opportunity splits. Permission set groups bundle permissions by job, and muting permission sets can remove specific permissions within a group.
- How it shows up
- A collaboration or confidentiality requirement is given, and you choose the sharing layer that meets it most narrowly.
- Common confusion
- Using a sharing rule to give one rep access to one opportunity, where an Opportunity Team member is the right tool.
3.4 Outline the capabilities, use cases, and design considerations when implementing Opportunity Products, Products, Price Books, Quotes, and the impact of multi-currency.Product catalog, pricing, quoting and currency design.
- What it means
- Products are added to price books through price book entries, and opportunities use one price book to add opportunity products. Quotes hold line items and can sync with their opportunity. Multi-currency lets records carry different currencies converted to a corporate currency.
- What to understand
- Every product needs a standard price in the standard price book before it can appear in a custom price book. An opportunity can use only one price book, and changing it removes existing products. Product schedules spread quantity or revenue over time. Only one quote syncs with an opportunity at a time. Once multi-currency is enabled it cannot be turned off, each price book entry is per currency, and advanced currency management with dated exchange rates applies to opportunities and related products, not to all objects.
- How it shows up
- A pricing, catalog or currency requirement is stated, and you pick the configuration or explain its consequence.
- Common confusion
- Expecting dated exchange rates to apply to every currency field in the org rather than mainly to opportunity data.
3.5 Given a set of requirements, determine how to support different business and sales process scenarios for Campaigns, Leads, and Opportunities.Campaign attribution, lead handling and opportunity variations.
- What it means
- Businesses run several kinds of campaigns, receive leads from many sources and sell through different processes, such as new business, renewals and partner deals. The consultant configures campaigns, leads and opportunities to support each variation and measure results.
- What to understand
- Use campaign hierarchies to roll up results, campaign member statuses to track responses, and Campaign Influence to attribute revenue across several touches; the Primary Campaign Source field supports simple single-touch attribution. Use lead queues and assignment rules for routing, and auto-response rules for acknowledgment. Use opportunity record types and sales processes for different deal types, contact roles to capture buying committees, and Big Deal Alerts or flows to notify on high-value opportunities.
- How it shows up
- A marketing or sales variation is described, and you choose the campaign, lead or opportunity setup that supports it.
- Common confusion
- Relying only on Primary Campaign Source when the requirement asks for credit across multiple campaigns.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Lead field mapping
Maps custom lead fields to account, contact and opportunity fields.
- Remember
- Unmapped custom fields do not carry over at conversion.
- Tested as
- Lead conversion scenarios.
- Trap
- Assuming all fields transfer automatically.
-
Sales process
Defines the opportunity stages available to a record type.
- Remember
- One sales process per opportunity record type.
- Tested as
- Multiple selling motions.
- Trap
- Creating separate objects per deal type.
-
Standard price book
Master list of products with standard prices.
- Remember
- A standard price is required before custom price book entries.
- Tested as
- Catalog setup questions.
- Trap
- Adding products straight to a custom price book.
-
Opportunity price book
One price book per opportunity.
- Remember
- Changing it deletes existing products.
- Tested as
- Pricing change scenarios.
- Trap
- Mixing products from two price books.
-
Quote sync
Keeps one quote's line items aligned with opportunity products.
- Remember
- Only one quote syncs at a time.
- Tested as
- Multiple quote scenarios.
- Trap
- Expecting all quotes to sync.
-
Product schedules
Spread quantity or revenue over installments.
- Remember
- Must be enabled and set per product.
- Tested as
- Subscription or delivery timing.
- Trap
- Using separate opportunities per month.
-
Multi-currency
Records hold their own currency with conversion to corporate currency.
- Remember
- Cannot be disabled once enabled.
- Tested as
- Global sales scenarios.
- Trap
- Treating it as a reversible test setting.
-
Advanced currency management
Dated exchange rates for opportunities and related items.
- Remember
- Not applied to all objects.
- Tested as
- Historical rate accuracy.
- Trap
- Assuming every currency field uses dated rates.
-
Opportunity Teams
Named users with roles and access on an opportunity.
- Remember
- Required for opportunity splits.
- Tested as
- Shared deal collaboration.
- Trap
- Using sharing rules for one deal.
-
Permission set group
Bundle of permission sets assigned as one.
- Remember
- Muting sets can remove permissions inside it.
- Tested as
- Role-based access design.
- Trap
- Creating more profiles.
-
Campaign Influence
Attributes opportunity revenue across several campaigns.
- Remember
- Customizable models support multi-touch credit.
- Tested as
- Marketing ROI questions.
- Trap
- Relying on Primary Campaign Source only.
-
Opportunity contact roles
Links contacts to an opportunity with a buying role.
- Remember
- Needed for campaign influence and buyer mapping.
- Tested as
- Buying committee scenarios.
- Trap
- Using related contacts on account instead.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Record sharing tools
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Organization-wide defaults | Baseline access for each object. | Most restrictive starting point. | Setting Public when deals are confidential. |
| Role hierarchy | Managers inherit subordinates' access. | Vertical access only. | Expecting peer visibility. |
| Sharing rules | Group-based access by owner or criteria. | Applies to many records at once. | Using it for one-off access. |
| Account and Opportunity Teams | Named collaborators per record. | Record-specific and role labeled. | Expecting automatic assignment. |
Catalog and quoting objects
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Product | Item or service sold. | Catalog record only. | Expecting a price on the product. |
| Price book entry | Price of a product in a price book and currency. | One entry per currency. | Forgetting the standard price. |
| Opportunity product | Line item on an opportunity. | Drives opportunity amount. | Editing amount manually when products exist. |
| Quote line item | Line on a quote. | Syncs with opportunity products when synced. | Expecting unsynced quotes to update the deal. |
Extension options
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Flow | Declarative automation. | Fast to build and maintain. | Pushing very complex logic into it. |
| Apex | Custom code. | Fine control and complex logic. | Writing code for standard features. |
| AppExchange or Salesforce product | Prebuilt solution. | Vendor maintained. | Ignoring license and fit costs. |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Sync every quote
- What candidates pick
- Expect all quotes on an opportunity to update its products.
- Why it looks right
- Quotes belong to the opportunity.
- Why it's wrong
- Only one quote syncs at a time, and starting sync on another quote ends the previous sync.
Clue to watch for Several quotes exist for one deal.
-
Profile per team
- What candidates pick
- Clone profiles for each sales team with different access.
- Why it looks right
- Profiles feel complete.
- Why it's wrong
- Permission sets and permission set groups layer access with less maintenance and fewer profiles.
Clue to watch for Access differs slightly between teams.
-
Public opportunity defaults
- What candidates pick
- Set opportunities to Public Read Only to help collaboration.
- Why it looks right
- It removes access requests.
- Why it's wrong
- It exposes confidential deals to every user; keep Private and open access with roles, rules or teams.
Clue to watch for Reps must not see each other's pipeline.
-
Code for CPQ
- What candidates pick
- Build custom Apex quoting for bundles and discount tiers.
- Why it looks right
- It fits any rule.
- Why it's wrong
- Complex configure-price-quote needs are better met by Revenue Cloud or an AppExchange solution with lower maintenance.
Clue to watch for Bundled products, guided selling and tiered discounts.
-
Primary campaign only
- What candidates pick
- Use Primary Campaign Source to show credit across touches.
- Why it looks right
- It is standard and simple.
- Why it's wrong
- Primary Campaign Source records one campaign; multi-touch credit needs Campaign Influence.
Clue to watch for Several campaigns influenced the deal.
-
Splits without teams
- What candidates pick
- Enable opportunity splits and assign credit to any user.
- Why it looks right
- Splits seem standalone.
- Why it's wrong
- Splits require Opportunity Teams, and users receiving credit must be team members.
Clue to watch for Revenue credit shared between reps.
Answer framework
Use these steps when a scenario asks you to design or correct part of the sales data model.
- Identify the objects involved, such as lead, opportunity, product, price book, quote or campaign, and the behavior the requirement depends on.
- Recall the standard rule for that behavior, for example quote sync limits, standard price requirements or conversion mapping, before considering custom work or a different product.
- For access needs, start from restrictive organization-wide defaults and pick the narrowest tool: role, sharing rule, team or permission set.
- If configuration cannot meet the need, consider an AppExchange app or another Salesforce product before writing Apex.
- Check for irreversible or wide-reaching consequences, such as enabling multi-currency or changing an opportunity price book, and plan for them before go-live.
Practice question
Want more like this? The Sales-Con-201 practice test has questions for every domain.
Checklist
0 of 13
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Allow sixteen to eighteen hours, most of them in a trial or Developer Edition org. Build a full sales process: a web-to-lead form, assignment rules into two queues, a lead conversion with mapped custom fields, two opportunity record types with different sales processes and paths, a product catalog with standard and custom price books, and quotes generated from a template.
Next, work through access. Set opportunities to Private, add roles, create an owner-based and a criteria-based sharing rule, then add an Opportunity Team and enable splits to see how they depend on each other. Assign a permission set group and test a muting permission set.
Use a separate scratch org to enable multi-currency and advanced currency management, since the change cannot be reversed. Set dated rates and watch how an opportunity amount converts. Finally, practice questions that compare similar tools, and keep a table of object rules, such as quote sync and price book limits, to review the day before the exam.
FAQ
What share of the Agentforce Sales Consultant exam is Practical Application of Agentforce Sales Expertise?
Practical Application of Agentforce Sales Expertise is 24% of the exam, close to fourteen of the 60 scored questions when used as a planning estimate.
Why do some guides show two Practical Application sections?
Some third-party guides split the objectives into parts one and two. The current outline reports a single 24% section with five objectives covering both parts.
Is Salesforce CPQ or Revenue Cloud configuration tested?
Detailed CPQ configuration is not in scope. You should know when complex quoting needs point toward Revenue Cloud or an AppExchange solution instead of standard quotes.
Can an opportunity use more than one price book?
No. An opportunity uses a single price book, and changing it removes the products already added, so price book design must suit the deal types involved.
Which sharing settings matter most?
Opportunity and account organization-wide defaults, role hierarchy, owner and criteria sharing rules, Account Teams, Opportunity Teams and permission set groups appear most often in scenarios.
Do I need to know Slack features in depth?
You should know when Slack adds value for sales, such as deal channels, record alerts and approvals, rather than detailed Slack administration.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- HubSpot Inbound Marketing Certification Study guide
- Salesforce Certified Platform Developer I Study guide
- Google Ads Search Certification Study guide
- ServiceNow Certified System Administrator Study guide
- Salesforce Certified Platform Administrator Study guide
- ServiceNow Certified Application Developer Study guide
Test your Domain 3 knowledge
You have covered lead-to-close design, extension choices, sharing, the product catalog, quotes, multi-currency and campaign scenarios. Practice questions that hinge on precise object behavior.
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 Sales-Con-201 AI tutor Get any concept explained your way