Sales-Con-201 · Domain 4 of 5

Sales-Con-201 Domain 4: Data Management

Data Management asks how you bring sales data into Salesforce, connect it to other systems, keep the design scalable as volumes grow and maintain the quality reps and leaders rely on.

Exam weight estimate
18%
Official objectives estimate
3
Estimated questions estimate
~11
Suggested study time estimate
10–12 hrs

About 11 min read Reviewed October 2026

Overview

Data Management is worth 18% of the Agentforce Sales Consultant exam and has three objectives. It covers the data work that surrounds a sales implementation rather than reporting on that data.

The first objective is about migrations and integrations: choosing between the Data Import Wizard, Data Loader and API-based tools, sequencing loads so parent records exist before children, using external IDs and upsert, and deciding when to copy data versus view it in place with Salesforce Connect or integrate through middleware such as MuleSoft. The second objective covers scalability, including large data volumes, account and ownership data skew, record locking and selective queries. The third covers sales data quality: duplicate and matching rules, validation rules, required fields used sparingly, standardized picklists, data enrichment and ongoing stewardship.

How it's tested

Data Management scenarios mention record counts, source systems, load frequency or data problems such as duplicates and stale values. You choose the tool, sequence or design that handles that volume and keeps data trustworthy. Read the numbers in the stem carefully, because volume thresholds often decide which answer is correct.

  • Tool by volume

    The number of records and objects decides between the Data Import Wizard, Data Loader or a Bulk API based tool.

  • Skew and locking

    Many child records under one parent or one owner cause slow loads or errors, and you identify the design fix.

  • Prevent, then clean

    Duplicate or inconsistent data appears, and you choose duplicate rules, validation or picklists to stop it plus a cleanup approach.

Reasoning it through

A company will migrate 2.5 million historical opportunities and their line items from a legacy CRM. The Data Import Wizard cannot load opportunities or volumes of that size. Data Loader using the Bulk API can, with accounts loaded first, external IDs on each object for upsert, and products and price book entries in place before opportunity products. Disabling nonessential automation during the load reduces lock contention and run time.

Objectives 3

Official objectives from the Salesforce outline, in outline order.

4.1 Explain the use cases and considerations for data migrations and integrations.Moving data in and connecting other systems.
What it means
Migration moves existing records from legacy systems into Salesforce, usually once or in waves, while integration keeps Salesforce and other systems in sync on an ongoing basis. Both require choosing tools, mapping fields and planning load order.
What to understand
The Data Import Wizard suits up to 50,000 records for accounts, contacts, leads, solutions, campaign members and custom objects, with built-in duplicate matching for some objects. Data Loader supports all standard objects and millions of records through the Bulk API. Load parents before children, use external IDs and upsert to relate records and rerun safely, and plan record ownership and record types. For integrations, decide between real-time API calls, scheduled batch, platform events, middleware such as MuleSoft, or Salesforce Connect when data should stay in the source system.
How it shows up
A migration or integration requirement is stated with volumes and timing, and you pick the tool or approach.
Common confusion
Choosing the Data Import Wizard for opportunities or loads beyond 50,000 records.
4.2 Given a scenario, outline the scalability implications of a solution.Designing for large volumes and avoiding performance issues.
What it means
As record counts grow, design choices that worked in a pilot can slow down saves, reports, sharing calculations and data loads. A consultant anticipates these issues during design and recommends patterns that keep the org responsive.
What to understand
Account data skew occurs when one account has more than about 10,000 child records, causing record locking and long sharing recalculations. Ownership skew occurs when one user owns very large numbers of records, often an integration user, and that user should sit outside or at the top of the role hierarchy. Use selective filters on indexed fields, archive old data, consider skinny tables and custom indexes through Salesforce Support, defer sharing calculations for large changes, and keep automation bulk-safe.
How it shows up
A design will hold millions of records or concentrate many children under one parent, and you identify the risk or mitigation.
Common confusion
Placing all unassigned leads or accounts under one owner in a low role, which creates ownership skew.
4.3 Discuss approaches for managing sales data quality in Salesforce.Keeping sales records complete, accurate and free of duplicates.
What it means
Data quality covers completeness, accuracy, consistency, uniqueness and timeliness. Poor quality damages forecasts, routing and reporting, so the consultant designs preventive controls and an ongoing stewardship process.
What to understand
Matching rules define how records are compared, and duplicate rules decide whether to block or alert on a match. Validation rules enforce formats and dependencies, picklists and dependent picklists standardize values, and required fields should be limited to what is truly needed. Data enrichment tools can fill firmographic gaps. Assign data stewards, schedule duplicate jobs or merges, and track quality with reports or dashboards on incomplete records and aging opportunities.
How it shows up
Data inconsistency or duplicates are described, and you choose preventive controls and a cleanup plan.
Common confusion
Thinking duplicate rules alone define what counts as a match; matching rules provide the comparison logic.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Data Import Wizard

    Browser-based import for common objects.

    Remember
    Up to 50,000 records; no opportunity import.
    Tested as
    Small, simple loads.
    Trap
    Using it for large or opportunity loads.

  • Data Loader

    Client tool for insert, update, upsert, delete and export.

    Remember
    Handles millions of records with the Bulk API.
    Tested as
    Migration questions.
    Trap
    Assuming it deduplicates automatically.

  • External ID

    Indexed field holding the source system key.

    Remember
    Enables upsert and relationship mapping.
    Tested as
    Repeatable migrations.
    Trap
    Matching on record names instead.

  • Upsert

    Insert or update based on an ID or external ID.

    Remember
    Rerunning a load does not create duplicates.
    Tested as
    Incremental migration.
    Trap
    Using insert for reruns.

  • Load order

    Parents before children.

    Remember
    Users, accounts, contacts, then opportunities and line items.
    Tested as
    Failed relationship scenarios.
    Trap
    Loading child records first.

  • Account data skew

    Too many child records under one account.

    Remember
    Roughly over 10,000 children causes locking.
    Tested as
    Slow saves and lock errors.
    Trap
    Using one placeholder account for everything.

  • Ownership skew

    One user owns a very large share of records.

    Remember
    Keep that user out of deep role hierarchy positions.
    Tested as
    Integration user scenarios.
    Trap
    Assigning orphan records to a sales rep.

  • Salesforce Connect

    Views external data as external objects without copying.

    Remember
    Data stays in the source.
    Tested as
    Large or volatile external data.
    Trap
    Copying data that changes constantly.

  • Matching rule

    Logic that compares records for similarity.

    Remember
    Used by duplicate rules and jobs.
    Tested as
    Duplicate detection setup.
    Trap
    Confusing it with the duplicate rule.

  • Duplicate rule

    Action taken when a match is found.

    Remember
    Can block or allow with alert.
    Tested as
    Prevention scenarios.
    Trap
    Expecting it to merge records.

  • Validation rule

    Formula that blocks saves with invalid data.

    Remember
    Keep messages clear and logic focused.
    Tested as
    Data format and dependency checks.
    Trap
    Adding too many and blocking integrations.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Data load tools

ConceptMeaningKey differenceCommon trap
Data Import Wizard Guided import in Setup. Up to 50,000 records, limited objects. Using it for opportunities.
Data Loader Desktop or CLI tool. Up to millions of records, all objects. Skipping external IDs.
Bulk API through middleware Programmatic high-volume loads. Automation and scheduling. Over-engineering a one-time small import.

Integration approaches

ConceptMeaningKey differenceCommon trap
Real-time API Immediate request and response. Low latency, more calls. Using it for nightly bulk sync.
Batch sync Scheduled bulk transfer. Efficient for volume. Expecting instant updates.
Salesforce Connect External objects queried on demand. No data copy. Expecting full reporting parity.

Duplicate management parts

ConceptMeaningKey differenceCommon trap
Matching rule Defines how records are compared. Comparison logic. Thinking it acts on its own.
Duplicate rule Defines the action on a match. Block or alert. Expecting automatic merging.
Duplicate job Scans existing records for duplicates. Cleans historical data. Assuming rules fix existing records.

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Wizard for everything

    What candidates pick
    Use the Data Import Wizard because it is simpler.
    Why it looks right
    No install and guided steps.
    Why it's wrong
    It is limited to 50,000 records and certain objects, and cannot import opportunities.

    Clue to watch for Opportunity history or millions of rows.

  2. Insert on rerun

    What candidates pick
    Insert the corrected file again after a failed load.
    Why it looks right
    It seems quickest.
    Why it's wrong
    Insert creates duplicates of rows that already loaded; upsert on an external ID updates them instead.

    Clue to watch for A load must be rerun safely.

  3. Catch-all account

    What candidates pick
    Attach all unmatched contacts to one generic account.
    Why it looks right
    It satisfies required relationships.
    Why it's wrong
    Tens of thousands of children under one account cause lock contention and slow sharing recalculation.

    Clue to watch for Very large numbers of orphan records.

  4. Copy external data

    What candidates pick
    Replicate a huge, frequently changing external table into custom objects.
    Why it looks right
    Native reporting is easier.
    Why it's wrong
    Storage and sync effort grow quickly; Salesforce Connect shows the data on demand without copying.

    Clue to watch for Data must stay in the source system.

  5. Duplicate rule merges

    What candidates pick
    Expect duplicate rules to merge matching records.
    Why it looks right
    The name implies cleanup.
    Why it's wrong
    Duplicate rules block or alert on new or edited records; merging needs duplicate jobs, manual merge or tools.

    Clue to watch for Existing duplicates must be removed.

  6. Validation everywhere

    What candidates pick
    Add strict validation rules to every field.
    Why it looks right
    More rules seem to mean better data.
    Why it's wrong
    Excess rules frustrate users and break integrations; target rules at critical data only.

    Clue to watch for Integration loads start failing.

Answer framework

Use these steps when a scenario involves moving, scaling or cleaning sales data.

  1. Note the record counts, objects and frequency in the stem, since they decide which load tool or integration pattern is valid.
  2. Plan load order from users and accounts through contacts, products and price book entries to opportunities and line items, using external IDs for relationships.
  3. Check the design for account or ownership skew and lock contention, and spread records or adjust role placement where volumes concentrate.
  4. Decide whether data must be copied into Salesforce or can remain external and be accessed through Salesforce Connect or middleware.
  5. Add preventive quality controls such as matching and duplicate rules, validation and picklists, then schedule ongoing stewardship and cleanup.

Practice question

After an integration went live, a sales operations team finds that a nightly job assigns all new prospect accounts to a single integration user. Saves on these accounts are slowing and sharing recalculations take hours. What should the consultant recommend?

Want more like this? The Sales-Con-201 practice test has questions for every domain.

Checklist

0 of 11

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Plan ten to twelve hours. Start with tools: in a Developer Edition org, import a few hundred leads with the Data Import Wizard, then use Data Loader to upsert accounts and contacts using an external ID field. Try loading opportunities before accounts to see the relationship errors, then fix the order.

Next, read the Salesforce guidance on large data volumes and data skew, and write a short note on each risk: what causes it, the symptom a stem would describe and the mitigation. Memorize the thresholds that appear in questions, such as 50,000 records for the Data Import Wizard and about 10,000 child records for account skew.

Finish with data quality. Create a matching rule and a duplicate rule on accounts that alerts rather than blocks, add a validation rule for a phone format, and build a report showing opportunities missing a next step. Then answer practice questions, checking whether each wrong choice failed on volume, order, skew or quality.

FAQ

How much of the Agentforce Sales Consultant exam is Data Management?

Data Management is 18% of the exam per third-party copies of the guide, roughly eleven of the 60 scored questions as a planning estimate.

Do I need to know the Bulk API in detail?

No. Know that Data Loader can use the Bulk API for large volumes and when that matters, not how to write Bulk API code.

Which thresholds should I memorize?

Remember 50,000 records for the Data Import Wizard and about 10,000 child records per account as the point where account data skew becomes a concern.

Is MuleSoft tested?

Only as an integration option. You should recognize when middleware suits multiple system connections, but MuleSoft configuration is not part of this exam.

What is the difference between a matching rule and a duplicate rule?

A matching rule defines how records are compared. A duplicate rule uses a matching rule and decides whether to block the save or allow it with an alert.

Does Data Management include reporting?

Sales reporting sits in the Sales Lifecycle section. This section focuses on getting data in, keeping it scalable and keeping it clean.

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 4 knowledge

You have covered migration tools and order, integration choices, data skew, large volumes and data quality controls. Try questions where record counts decide the answer.

Take the Sales-Con-201 practice test Check your Sales-Con-201 readiness

Keep going