Home / crm-business-applications / Salesforce Certified Agentforce Sales Consultant (formerly Sales Cloud Consultant) / Cheat Sheet
Salesforce Certified Agentforce Sales Consultant (formerly Sales Cloud Consultant)

Sales-Con-201 Cheat Sheet

Sales-Con-201 Tests Least-Customization Sales Design — Not Feature Wish Lists

For consultants implementing Sales Cloud, renamed Agentforce Sales Consultant in July 2026 with the Sales-Con-201 code unchanged. Think like the consultant at each project stage: diagnose the process, then fit the standard feature.

Check Your Readiness →
Among the harder certs
Avg: Not published by Salesforce
Pass: 750 / 1000
Most candidates understand Salesforce Certified Agentforce Sales Consultant (formerly Sales Cloud Consultant) concepts — and still fail. This exam tests how you apply knowledge under pressure.

Sales-Con-201 Domain Map

Scenarios describe a project at a given stage or a sales leader's frustration. Wrong answers are often reasonable actions at the wrong time or with too much customization. Questions are based on the Summer '25 release, so live product names may differ from newer branding.

  1. 01
    Consulting and Implementation Strategies (25%) — sponsors, discovery, user stories, MoSCoW, change control, sandboxes, phased rollout
  2. 02
    Practical Application of Agentforce Sales Expertise (24%) — lead mapping, sales processes, price books, quotes, teams, splits
  3. 03
    Sales Lifecycle (20%) — Pipeline Inspection, Collaborative Forecasts, territories, Sales Engagement, Inbox, sales reporting
  4. 04
    Data Management (18%) — import tools and limits, external IDs, upsert, load order, data skew, duplicate management
  5. 05
    Predictive and Generative AI (13%) — Einstein scoring, global models, sales emails, Agentforce sales agents, Trust Layer

Wrong instinct vs correct approach

Two reps must share revenue credit on a large deal
✕ Wrong instinct

Enable opportunity splits and credit any user

✓ Correct approach

Opportunity splits require Opportunity Teams, and users receiving credit must be team members. Add both reps to the team with roles, then allocate revenue or overlay splits.

Marketing wants credit for every campaign that touched a closed deal
✕ Wrong instinct

Report on Primary Campaign Source

✓ Correct approach

Primary Campaign Source records a single campaign. Campaign Influence attributes revenue across several campaigns with customizable models, and it depends on opportunity contact roles linking buyers to the deal.

Three weeks after go-live, rep logins and opportunity updates are low
✕ Wrong instinct

Make more opportunity fields required on layouts

✓ Correct approach

Mandatory fields add friction and produce junk values. Use an adoption dashboard to diagnose the cause, then respond with targeted training, simpler layouts, change champions and executive sponsor reinforcement.

A newly implemented org wants Einstein Lead Scoring now but has little conversion history
✕ Wrong instinct

Wait until years of data accumulate

✓ Correct approach

Einstein Lead Scoring uses a global model trained on aggregated, anonymized data until the org has enough local history, so scoring can start immediately. Generated summaries never substitute for a predictive ranking.

Thousands of unmatched contacts need a home during migration
✕ Wrong instinct

Attach them all to one placeholder account

✓ Correct approach

More than roughly 10,000 children under one account causes account data skew, record locking and slow sharing recalculation. Spread records across accounts and keep any owner of huge record volumes outside deep role hierarchy positions.

Know these cold

  • ▸ Forecast categories, not probability, drive Collaborative Forecasts — ipeline, Best Case, Commit, Closed, Omitted
  • ▸ Pipeline Inspection highlights week-over-week amount and close date changes without custom reports
  • ▸ One sales process per opportunity record type controls which stages appear
  • ▸ Unmapped custom lead fields are lost on conversion; map them to account, contact or opportunity
  • ▸ Multi-currency cannot be disabled; advanced currency management applies dated rates to opportunities only
  • ▸ Sales Engagement runs high-volume cadences; Salesforce Inbox helps individual reps inside Gmail or Outlook
  • ▸ Permission set groups over cloned profiles; muting sets remove permissions inside a group
  • ▸ Matching rule finds similar records; duplicate rule blocks or alerts but never merges
  • ▸ Full sandbox for UAT and staging; Partial Copy for QA and training; Developer for building
  • ▸ Agentforce Sales Development qualifies and hands leads to reps; it does not close deals

Can you answer these without checking your notes?

In this scenario: "Two reps must share revenue credit on a large deal" — what should you do first?
Opportunity splits require Opportunity Teams, and users receiving credit must be team members. Add both reps to the team with roles, then allocate revenue or overlay splits.
In this scenario: "Marketing wants credit for every campaign that touched a closed deal" — what should you do first?
Primary Campaign Source records a single campaign. Campaign Influence attributes revenue across several campaigns with customizable models, and it depends on opportunity contact roles linking buyers to the deal.
In this scenario: "Three weeks after go-live, rep logins and opportunity updates are low" — what should you do first?
Mandatory fields add friction and produce junk values. Use an adoption dashboard to diagnose the cause, then respond with targeted training, simpler layouts, change champions and executive sponsor reinforcement.

Common Exam Mistakes — What candidates get wrong

Modelling overlapping sales territories in the role hierarchy

A user holds one role, so region-by-industry coverage explodes into roles that still cannot share an account across teams. Enterprise Territory Management assigns accounts by rules, independent of roles, with overlapping territories and multiple models.

Using the Data Import Wizard for opportunity history

The wizard handles up to 50,000 records for common objects and cannot import opportunities. Data Loader with the Bulk API handles millions. Load parents first: users, accounts, contacts, then opportunities and line items.

Rerunning a failed load as an insert

Insert duplicates every row that already loaded. Upsert matched on an indexed external ID updates existing rows and creates only missing ones, and external IDs also map relationships to parent records.

Calculating win rate with a formula field on each opportunity

Win rate is a ratio across many records, so it belongs in a report summary formula. Likewise, rely on Pipeline Inspection and Collaborative Forecasts for weekly changes before building custom snapshot reports.

Expecting every quote on an opportunity to sync its products

Only one quote syncs at a time; starting sync on another ends the previous one. Each opportunity uses a single price book, and changing it deletes existing products. A standard price must exist before custom price book entries.

Resources to help you pass Agentforce Sales Consultant on your first attempt

Sales-Con-201 rewards the right consulting move at each project stage. Measure yours.