Sales-Con-201 Data Management Practice Test 2 — 15 Questions

Question 1

Universal Containers wants to ensure that when a Lead is converted, the Account record created is automatically assigned a specific Record Type based on the lead source. Where is this configured in Setup?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Lead Settings / Lead Processes and Conversion Mapping. Lead Conversion settings in Setup allow administrators to map lead fields to Account, Contact, and Opportunity fields and set default record types.

Answer

Duplicate Rule configuration

Answer

Data Import Wizard

Answer

Territory Management rules

Question 2

A Sales Cloud Consultant is migrating opportunities and needs to ensure that closed-won opportunities retain their historical closed dates without being overwritten by automation. What must the Consultant ensure during data loading?

Accepted Answer

Enable 'Set Audit Fields upon Record Creation' and map the historical CloseDate.. System fields like Closedate and CreatedDate can be populated with historical values if 'Create Audit Fields' is enabled and mapped correctly in Data Loader.

Answer

Rely on workflow rules to backdate the opportunity automatically.

Answer

Map CloseDate to the SystemModstamp field.

Answer

Convert opportunities as closed-lost first, then reopen them.

Question 3

A Sales Cloud Consultant is configuring data cleansing rules. They want to ensure that all user-entered phone numbers are stripped of formatting symbols (like dashes and parentheses) and saved in standard E.164 format. Which tool is best suited for real-time formatting?

Accepted Answer

Before-save Record-Triggered Flow. A before-save Record-Triggered Flow runs before the record is committed to the database, allowing it to modify field values (like reformatting a phone number to E.164) in real time without an additional DML operation. This is the only declarative tool that can transform field values on save for user-entered data.

Answer

Data Import Wizard

Answer

Assignment Rule

Answer

Web-to-Lead auto-response rule

Question 4

Universal Containers has complex business logic where Opportunity creation requires validating custom data against an external ERP system in real time. If the ERP validation fails, the Opportunity must not be created in Salesforce. Which architectural approach should the Consultant recommend?

Accepted Answer

Synchronous Apex Trigger with callout exception handling to roll back the transaction if ERP validation fails.. An after-trigger or synchronous outbound callout (via Apex or external services) combined with custom exception handling can validate and block record saves if external checks fail. Wait, synchronous callouts cannot be made from triggers directly without queueable/future unless using External Services / Apex REST, but a synchronous trigger block can use custom validation or Apex.

Answer

Data Loader export-import loop.

Answer

Standard Validation Rule referencing external ERP database tables via formula.

Answer

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

Question 5

Universal Containers is migrating 2 million legacy contact records into Sales Cloud. The legacy system contains many duplicate contacts identified by matching email addresses, but the company wants to import all records and then consolidate duplicates later. Which approach should the consultant recommend to prevent duplicate blocking during the initial load?

Accepted Answer

Disable duplicate rules and matching rules before the import, then re-enable them after the load completes.. Duplicate rules and matching rules are enforced during record creation, including Data Loader imports. To load all records without interruption, the consultant must deactivate these rules temporarily. After the load, reactivating them and using duplicate management tools to merge records achieves the desired consolidation. This approach balances the need for a complete initial load with post-load data quality.

Answer

Use the Data Loader 'Allow Duplicates' setting in the import wizard to bypass duplicate rules.

Answer

Import the records using the Bulk API in parallel mode, which automatically skips duplicate checks.

Answer

Set the duplicate rule action to 'Allow' and the alert to 'No Alert' for the migration user's profile.

Question 6

A consultant is loading 500,000 opportunity records into Sales Cloud using Data Loader. The organization has a validation rule on Opportunity that requires the Close Date to be in the future for open opportunities. The legacy data includes many open opportunities with past close dates that must be loaded as-is for historical reporting. What should the consultant do to successfully load these records?

Accepted Answer

Temporarily deactivate the validation rule, perform the load, and then reactivate the rule.. Validation rules are enforced on all record saves, including those from Data Loader. To import records that violate a validation rule, the consultant must temporarily deactivate the rule. After the load, reactivating it ensures future data quality. This is the only reliable method to load non-conforming legacy data without altering it, and it is a common step in data migration projects.

Answer

Load the records with a future Close Date, then update the Close Date to the historical value using a subsequent update.

Answer

Set the 'Close Date' field to a future date and then use a workflow rule to change it after insertion.

Answer

Use Data Loader's 'Bypass Validation Rules' option in the settings.

Question 7

A sales manager reports that when importing new leads using the Data Import Wizard, some records are failing due to duplicate rules. The manager wants to import all leads without duplicates being blocked, but still wants to be alerted to potential duplicates. What should the consultant recommend?

Accepted Answer

Modify the duplicate rule to change the action from 'Block' to 'Allow' and set the alert to 'Alert'.. Duplicate rules have an action (Allow, Block, or Report) and an alert. To import all leads while still being alerted, the action should be set to 'Allow' and the alert should be enabled. This allows records to be created but notifies users of potential duplicates. Changing the rule is a declarative configuration that can be done in Setup, and it directly addresses the manager's requirements.

Answer

Create a new duplicate rule with no matching rules and assign it to the import user.

Answer

Use Data Import Wizard's 'Allow Duplicates' checkbox to override the rule.

Answer

Deactivate the duplicate rule and rely on manual review after import.

Question 8

Universal Containers tracks customer accounts globally. Sales reps frequently create duplicate accounts by entering minor spelling variations in company names. Which matching rule component should be configured to catch phonetic variations or typos?

Accepted Answer

Fuzzy Match. Fuzzy Match is the matching rule component designed to identify records that are similar but not identical, such as those with minor spelling variations, typos, or phonetic differences. It uses algorithms like Levenshtein distance or Soundex to compare field values and assign a match score. This directly addresses the problem of duplicate accounts created due to slight name variations. Other match methods require exact or specific conditions, which would not catch these near-duplicates.

Answer

Blank Value Match

Answer

Exact Match

Answer

Numeric Range Match

Question 9

A Sales Cloud Consultant is preparing to migrate millions of records. To optimize performance and prevent API timeout errors, what should the Consultant do before initiating the data load?

Accepted Answer

Temporarily disable unnecessary validation rules, triggers, and workflows.. Disabling triggers, validation rules, workflow rules, and assignment rules reduces database overhead and speeds up bulk data loads significantly.

Answer

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

Answer

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

Answer

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

Question 10

A Sales Cloud Consultant is migrating legacy accounts into Salesforce using Data Loader. The legacy system uses a custom External ID field. Which operation should be used to update existing records and insert new ones simultaneously?

Accepted Answer

Upsert. Upsert is the Data Loader operation that updates existing records and inserts new ones in a single operation. It matches records based on an External ID field, which the legacy system uses. This avoids duplicates and ensures data integrity during migration.

Answer

Insert

Answer

Update

Answer

Import

Question 11

Universal Containers has thousands of legacy Account records containing messy address data. They want to standardize state and country values to ISO codes automatically during migration. What is the best approach?

Accepted Answer

Enable State and Country Picklists and use Data Loader to map standard values.. Enabling State and Country Picklists and mapping the legacy values to the integration values via the user interface or Data Loader ensures data integrity and adherence to standard formats.

Answer

Use workflow field updates to overwrite text entries.

Answer

Write a trigger to format text fields upon insert.

Answer

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

Question 12

A sales manager is concerned about duplicate Contact records being created manually by sales reps. Which tool should the Consultant configure to alert users and prevent duplicate creation in real time?

Accepted Answer

Duplicate Rule and Matching Rule. Standard Duplicate Management allows administrators to define matching rules and duplicate rules that alert users or block creation when a potential duplicate is detected.

Answer

Data Integration Rule

Answer

Mass Delete Wizard

Answer

Data Loader with matching criteria

Question 13

Universal Containers needs to map complex hierarchies during data migration. They have parent and child accounts across multiple legacy systems. What is the recommended best practice for loading hierarchical account data?

Accepted Answer

Load parent accounts, export the resulting Salesforce IDs, map them to child records using an External ID, and then load child accounts.. When loading accounts with parent-child relationships, you must load parent accounts first, export their generated Salesforce IDs, map those IDs to the child records' Parent Account field using an External ID or Salesforce ID, and then load the child records.

Answer

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

Answer

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

Answer

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

Question 14

Universal Containers wants to ensure that all newly created Accounts have an industry classification populated before saving. Which declarative tool should the Consultant recommend?

Accepted Answer

Validation Rule. A Validation Rule is the only declarative tool that can enforce data entry requirements at the point of saving a record. It evaluates a formula condition (e.g., ISBLANK(Industry)) and prevents the save if the condition is true, displaying a user-defined error message. This ensures that no Account can be created or updated without an Industry value, directly meeting the requirement that industry be populated before saving.

Answer

Duplicate Rule

Answer

Workflow Rule

Answer

Data Import Wizard

Question 15

An administrator is deleting a large volume of obsolete Lead records using Data Loader. Some deletions fail due to 'Apex CPU time limit exceeded' errors caused by cascading triggers. How should this be resolved?

Accepted Answer

Reduce the batch size in Data Loader and temporarily disable unnecessary triggers.. The 'Apex CPU time limit exceeded' error occurs when triggers consume too much CPU time during a single transaction. Reducing the Data Loader batch size decreases the number of records processed per transaction, lowering CPU usage. Temporarily disabling unnecessary triggers further reduces CPU load, allowing deletions to succeed.

Answer

Increase the Salesforce API timeout limit in Company Information.

Answer

Convert the Leads to Contacts instead of deleting them.

Answer

Switch from Data Loader to Data Import Wizard for deletions.