Data Management practice questions

Global Search

Why wrong: Global Search is for finding existing records, not importing new ones.

Mass Delete tool

Why wrong: Mass Delete is for removing records, not importing.

Data Import Wizard

Why wrong: Data Import Wizard has a strict limit of 50,000 records per import.

Lookup relationship to User

Why wrong: A custom user lookup does not govern record ownership or standard transfer capabilities.

Auto-Number field

Why wrong: Auto-Number is for naming/numbering, not ownership control.

Checkbox field named 'Locked'

Why wrong: A checkbox does not inherently restrict ownership transfers without validation rules or Apex.

Data Loader export-import loop.

Why wrong: Manual or scheduled batch exports do not provide real-time creation checks.

Standard Validation Rule referencing external ERP database tables via formula.

Why wrong: Validation rules cannot query external systems or ERP databases directly.

Scheduled Flow running nightly to check ERP status and delete invalid opportunities.

Why wrong: A nightly schedule leaves invalid opportunities in the system for up to 24 hours, failing the real-time requirement.

Blank Value Match

Why wrong: Blank value match evaluates whether fields are empty, not string similarity.

Exact Match

Why wrong: Exact match requires the text to be identical character-for-character, missing typos and variations.

Numeric Range Match

Why wrong: Numeric range match is used for numbers and currency, not text names.

Convert all custom fields to text fields to avoid data type mismatch.

Why wrong: Converting fields degrades data integrity and breaks reporting structures.

Increase the batch size in Data Loader to the maximum limit of 10,000.

Why wrong: Excessively large batch sizes often lead to locking issues and payload timeout errors.

Enable all validation rules and triggers to catch bad data early.

Why wrong: Enabling rules during a large data load drastically slows down performance and causes transaction failures.

Insert

Why wrong: Insert only creates new records and will fail if the external ID already exists.

Update

Why wrong: Update only modifies existing records and will fail for records that do not yet exist in Salesforce.

Import

Why wrong: Import is not a standard operation name in Data Loader; the tool uses Insert, Update, and Upsert.

Use workflow field updates to overwrite text entries.

Why wrong: Workflow rules cannot dynamically map arbitrary text strings to standardized picklist values across diverse inputs.

Write a trigger to format text fields upon insert.

Why wrong: Writing custom code is unnecessary and harder to maintain when native picklist features exist.

Rely on users to manually select the correct picklist value post-migration.

Why wrong: Manual cleanup post-migration is prone to human error and low data adoption.

Data Integration Rule

Why wrong: Data Integration Rules are used for syncing third-party data like Dun & Bradstreet, not for internal duplicate prevention.

Mass Delete Wizard

Why wrong: Mass Delete is a cleanup tool, not a preventive tool.

Data Loader with matching criteria

Why wrong: Data Loader is a bulk migration tool, not a real-time user interface prevention tool.

Use the Data Import Wizard with the 'Parent Account Name' match key to establish relationships in a single pass.

Why wrong: Data Import Wizard does not support complex hierarchy matching via Account Name due to potential uniqueness and matching conflicts.

Perform a bulk insert on a self-referential CSV file where parent and child rows are interleaved.

Why wrong: Interleaving rows in a single file will still cause database constraint errors for children whose parents have not yet been inserted.

Load child accounts first using the legacy parent identifier, and Salesforce will automatically resolve the hierarchy.

Why wrong: Salesforce cannot resolve parent relationships if the parent records do not yet exist in the database.

Duplicate Rule

Why wrong: Duplicate Rules are designed to identify and block duplicate records, not to enforce field data entry.

Workflow Rule

Why wrong: Workflow rules can update fields or send alerts, but cannot block record creation based on blank field values.

Data Import Wizard

Why wrong: Data Import Wizard is used for loading and updating data, not for real-time enforcement of field population on user creation.

Increase the Salesforce API timeout limit in Company Information.

Why wrong: API timeout limits cannot be adjusted by administrators to bypass CPU limits.

Convert the Leads to Contacts instead of deleting them.

Why wrong: Converting leads does not delete them and leaves unnecessary data in the system.

Switch from Data Loader to Data Import Wizard for deletions.

Why wrong: Data Import Wizard does not support delete operations.

The External ID field on the parent object is missing.

Why wrong: External IDs affect upsert operations, not master-detail parent linkage rules.

The child record is owned by a queue instead of a user.

Why wrong: Ownership has no bearing on master-detail reparenting restrictions.

Data Loader is attempting to insert child records before parent records.

Why wrong: Inserting children before parents results in a missing parent ID error, not a reparenting error.

Map the Owner ID column to a blank value in the CSV file.

Why wrong: Leaving Owner ID blank without checking assignment rules will cause records to default to the integration user.

Write a Process Builder to change the owner after insert.

Why wrong: Process Builder is unnecessary when standard assignment rule processing is built into Data Loader settings.

Use Data Import Wizard, which ignores assignment rules by default.

Why wrong: Data Import Wizard has an optional checkbox for trigger-based assignment rules, but Data Loader requires explicit configuration.

A single lookup field on the Account object pointing to Product.

Why wrong: A single lookup represents a one-to-many relationship, not many-to-many.

A multi-select picklist containing product IDs on the Account object.

Why wrong: Multi-select picklists are poor for reporting and data integrity in many-to-many scenarios.

A hierarchical relationship field on the Product object.

Why wrong: Hierarchical relationships are strictly for User object self-references.

Workbench REST API explorer

Why wrong: While Workbench can do this, Data Import Wizard is the native admin-friendly tool designed for this volume.

Salesforce CLI

Why wrong: Salesforce CLI is overly complex for a simple 500-record CSV update.

Developer Console

Why wrong: Developer Console requires writing anonymous Apex code or SOQL queries to perform updates.

Data Import Wizard

Why wrong: Data Import Wizard is an ad-hoc import tool, not an export scheduler.

Mass Transfer Tool

Why wrong: Mass Transfer is used for changing ownership of records, not exporting data.

Data Loader CLI

Why wrong: Data Loader CLI requires external task scheduler setup (like Windows Task Scheduler or cron) and scripts, rather than being a native scheduled setup feature.

Data Loader cannot process Person Accounts without a parent Business Account.

Why wrong: Person accounts represent individual consumers and do not require a parent account.

Person accounts require a separate insert for the Contact object first.

Why wrong: Person accounts are stored in the Account table and do not require a separate Contact record insert.

Person accounts do not support custom fields in Data Loader.

Why wrong: Person accounts fully support custom fields.

Data Integration Rule

Why wrong: Data Integration Rules update data from external sources, not delete internal records.

Data Export Service

Why wrong: Data Export Service creates backups, it does not delete records.

Sandbox Refresh

Why wrong: Sandbox refresh recreates the sandbox entirely, which may be overkill when simple mass deletion suffices.

Currency amounts must include the currency symbol ($, €).

Why wrong: Currency fields in Salesforce expect numeric values; symbols cause data type conversion failures.

Multi-currency must be temporarily disabled in Company Information during data loads.

Why wrong: Disabling multi-currency is generally not permitted if historical data depends on it.

Currency values must be converted to corporate currency manually before loading.

Why wrong: Salesforce handles conversion automatically if the correct CurrencyIsoCode is provided.

Campaign records must be locked before adding members.

Why wrong: Locking campaigns is not a prerequisite for adding members.

Campaign Status is a required field that was omitted from the mapping.

Why wrong: While status is important, default values typically apply if omitted; duplicate membership is the primary failure cause.

Campaign members cannot be loaded via Data Loader; they require Data Import Wizard.

Why wrong: Data Loader fully supports Campaign Member inserts and updates.