Sales-Con-201 Data Management — Timed 15 Questions

Question 1

An administrator needs to load 60,000 Lead records into Sales Cloud and wants a simple, web-based tool with a step-by-step interface. Which tool should be used?

Accepted Answer

Data Loader. The Data Import Wizard is a web-based tool built into Salesforce that handles up to 50,000 records. Wait, 60,000 records exceeds the 50,000 limit of the Data Import Wizard; therefore, Data Loader must be used.

Answer

Global Search

Answer

Mass Delete tool

Answer

Data Import Wizard

Question 2

A Consultant is importing Leads and needs to ensure that lead owners are assigned based on existing Assignment Rules rather than defaulting to the user performing the import. How should this be configured in Data Loader?

Accepted Answer

Check the 'Use Assignment Rules' box in Data Loader settings.. In Data Loader, checking the 'Use Assignment Rules' box in the settings ensures that active Lead Assignment Rules are applied during import, overriding the default owner (the importing user) and assigning leads based on rule criteria. This is the correct declarative configuration.

Answer

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

Answer

Write a Process Builder to change the owner after insert.

Answer

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

Question 3

Universal Containers uses Person Accounts. During data migration, the Consultant encounters errors when attempting to insert records with matching email addresses. What is the cause of this behavior?

Accepted Answer

Active duplicate rules are blocking record insertion based on matching contact data.. Person accounts combine Account and Contact fields. Duplicate rules or unique field constraints on standard fields (like email if configured as unique) apply to person accounts.

Answer

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

Answer

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

Answer

Person accounts do not support custom fields in Data Loader.

Question 4

A Sales Cloud Consultant is configuring a custom object to track competitor analysis. Sales reps should be able to view competitor records, but ownership should always remain with the Sales Operations team. Which field type ensures the record owner cannot be changed by sales reps?

Accepted Answer

Master-Detail relationship to Account. Record ownership is determined by the Owner ID field. While standard ownership can be transferred, sharing rules or restricting edit permissions govern access, but the owner field itself is standard. Wait, standard records are owned by users/queues. To restrict who can change ownership, Transfer permissions on profiles/permission sets control this, but the question asks about field type. Actually, ownership cannot be restricted by field type; however, standard object ownership behavior applies.

Answer

Lookup relationship to User

Answer

Auto-Number field

Answer

Checkbox field named 'Locked'

Question 5

A Consultant is loading Campaign Members into Salesforce. The CSV contains Contact IDs and Campaign IDs. Some rows fail with a 'Entity failed validation' error. What is the most likely cause?

Accepted Answer

The Contact is already a member of the specified Campaign, violating uniqueness.. Campaign Member records enforce a uniqueness constraint on the combination of Lead/Contact ID and Campaign ID — a Contact can only appear once per Campaign. When the CSV contains rows where the Contact is already a member of that Campaign, the insert fails with 'Entity failed validation' because it violates this built-in duplicate rule. This is the most common cause of this specific error during Campaign Member loads.

Answer

Campaign records must be locked before adding members.

Answer

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

Answer

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

Question 6

Universal Containers wants to ensure that a custom field 'Discount Percentage' cannot exceed 20% for standard sales reps. Which declarative feature should be used?

Accepted Answer

Validation Rule. A Validation Rule in Salesforce enforces data integrity by preventing records from being saved when specified criteria are met. To ensure 'Discount Percentage' cannot exceed 20% for standard sales reps, you create a validation rule with a formula like AND(Profile = 'Standard User', Discount_Percentage__c > 0.20) that fires an error message on save.

Answer

Escalation Rule

Answer

Sharing Rule

Answer

Assignment Rule

Question 7

Universal Containers wants to archive closed-won opportunities older than 5 years to maintain system performance. What is Salesforce's recommended approach for handling long-term data archiving?

Accepted Answer

Move records to a custom object named 'Archived Opportunity' using Data Loader, then delete the originals.. Salesforce's recommended approach for long-term data archiving is to move records to a custom object (e.g., 'Archived Opportunity') using Data Loader, then delete the originals. This reduces the volume of active records, improving performance, while preserving the data in a separate object for reporting or compliance. The custom object can be designed to hold key fields and can be related to other objects if needed.

Answer

Change the record type of old opportunities to 'Archived' and apply a sharing rule to hide them.

Answer

Mark the opportunities as inactive using workflow field updates.

Answer

Contact Salesforce Support to delete the primary database indexes for those records.

Question 8

Universal Containers is migrating 2 million historical activities (Tasks and Events) linked to Accounts and Opportunities. To ensure high performance and avoid database locking errors, what should the Consultant do?

Accepted Answer

Use Data Loader with smaller batch sizes and map WhatId for Accounts/Opportunities and WhoId for Contacts/Leads.. When loading activities, breaking batches down, disabling parent-account automatic roll-ups where possible, and loading during maintenance windows ensures high throughput.

Answer

Load Tasks and Events using the parent Account ID directly in the WhoId field.

Answer

Perform a single bulk insert of 2 million records with a batch size of 2,000.

Answer

Convert all historical activities into custom object records to bypass standard activity limits.

Question 9

A Sales Cloud Consultant is asked to ensure that users cannot delete Opportunity records unless they possess a specific custom permission set. Which tool is appropriate?

Accepted Answer

Validation Rule utilizing the $Permission global variable. Custom permissions referenced in Validation Rules or Apex triggers can restrict deletion, or profile-based 'Delete' object permissions can be adjusted.

Answer

Duplicate Rule set to block on delete

Answer

Sharing Rule with Read-Only access

Answer

Escalation Rule

Question 10

Universal Containers wants to clean up duplicate Account records currently residing in Sales Cloud. Which TWO native Salesforce features can help identify and merge these duplicates? Choose 2 options.

Accepted Answer

Lightning Account Merge tool. Option A, the Lightning Account Merge tool, is correct because it is the native Salesforce feature that lets users compare up to three duplicate Account records side by side and merge them into a single surviving record, re-parenting related records and consolidating fields. Option D, Standard Duplicate Management (Matching and Duplicate Rules), is correct because Matching Rules define the criteria that determine when records are considered duplicates (for example, matching on Account Name and Billing Street), and Duplicate Rules alert users or block saves when those matches are detected, thereby identifying duplicates before or as they are created. Option B, the Mass Delete Wizard, is incorrect because it only deletes records in bulk and provides no duplicate detection or merge capability. Option C, the Data Import Wizard deduplication wizard, is incorrect because the Data Import Wizard is an import tool that can prevent new duplicates during import via matching, but it does not identify or merge existing duplicate records already residing in Sales Cloud. Option E, the Data Loader upsert operation, is incorrect because upsert matches on an external ID or Id field to insert or update records and does not detect or merge pre-existing duplicates based on business matching criteria.

Answer

Mass Delete Wizard

Answer

Data Import Wizard deduplication wizard

Answer

Data Loader upsert operation

Question 11

Universal Containers wants to ensure that specific fields (e.g., Tax ID) are masked or restricted so that only finance managers can view them, while sales reps cannot. Which TWO features should the Consultant implement? Choose 2 options.

Accepted Answer

Salesforce Shield Platform Encryption. Field-Level Security (FLS) is correct because it controls whether a user profile or permission set can view or edit specific fields such as Tax ID, so finance managers can be granted visibility while sales reps are denied access. Salesforce Shield Platform Encryption is also correct because it encrypts sensitive field data at rest and can be combined with FLS and permission sets to protect fields like Tax ID from unauthorized viewing. Web-to-Lead settings are not relevant because they only control how web form submissions create leads, not field visibility. Assignment Rules are not relevant because they route leads or cases to owners and do not restrict field access. Sharing Rules are not relevant because they extend record-level access, not field-level visibility.

Answer

Web-to-Lead settings

Answer

Assignment Rules

Answer

Sharing Rules

Question 12

Universal Containers needs to migrate attachments and notes associated with legacy accounts into Salesforce. Which TWO considerations should the Consultant keep in mind? Choose 2 options.

Accepted Answer

Salesforce Files (ContentVersion and ContentDocumentLink) is the modern recommended storage model for file migrations.. Option C is correct because Salesforce Files, built on the ContentVersion and ContentDocumentLink objects, is the modern recommended storage model for file migrations, replacing the legacy Attachment object and enabling sharing, versioning, and library features. Option E is correct because legacy attachments can still be loaded via the Attachment object, where the ParentId field must be mapped to the related Account ID to associate each attachment with its account. Option A is incorrect because Data Loader's file size limit is 100 MB (and the Attachment object itself allows up to 25 MB), not 5 MB. Option B is incorrect because attachments have no requirement to be converted into Campaign records; they relate to parent records such as Accounts via ParentId. Option D is incorrect because notes and attachments are not loaded into the User object; they are associated with parent records like Accounts.

Answer

Attachments cannot exceed 5 MB when loaded via Data Loader.

Answer

Attachments must be converted into Campaign records first.

Answer

Notes and attachments must be loaded into the User object.

Question 13

A Consultant is configuring Duplicate Management rules for Contacts. Which THREE actions can be configured when a duplicate is detected during manual creation or editing? Choose 3 options.

Accepted Answer

Report on duplicate creation by logging it in the duplicate record report.. In Salesforce Duplicate Management, when a matching rule flags a duplicate during manual creation or editing, the duplicate rule can take one of three actions: Allow (save the record), Block (prevent saving), or Alert (warn the user but let them save anyway). Option B is correct because the Alert action surfaces the duplicate to the user and records the event in the duplicate record report/duplicate record set for later reporting. Option D is correct because the Allow action lets the user proceed and save the duplicate record after being informed. Option E is correct because the Block action stops the user from saving the record until the duplicate is resolved. Options A and C are not valid duplicate rule actions: Salesforce does not auto-merge records in real time during manual entry, and it does not automatically delete the newly entered duplicate record.

Answer

Automatically merge the duplicate with the master record in real time.

Answer

Automatically delete the newly entered duplicate record.

Question 14

Universal Containers wants to ensure that all Accounts have a valid website URL format entered. Which TWO functions can be used in a Validation Rule formula to help validate this requirement? Choose 2 options.

Accepted Answer

CONTAINS(). In a Salesforce Validation Rule, CONTAINS() is correct because it lets the formula test whether the Website field includes required URL components such as 'http://' or 'www.', so an Account without a valid-looking URL can be flagged. NOT() is also correct because it inverts the result of such a check, allowing the rule to fire when the Website does not contain the expected URL pattern. ISCHANGED() is not appropriate here because it only detects whether a field value changed during the save, not whether the URL format is valid. VLOOKUP() is not suitable because it retrieves a value from a custom object relationship and cannot validate text format. PRIORVALUE() is not relevant because it references the previous value of a field, not the current URL's structure.

Answer

ISCHANGED()

Answer

VLOOKUP()

Answer

PRIORVALUE()

Question 15

A Consultant is preparing a data migration plan and needs to determine which standard objects support custom External IDs for upsert operations. Which THREE standard Sales Cloud objects support External IDs? Choose 3 options.

Accepted Answer

Lead. Options B, D, and E are correct because Lead, Account, and Contact are standard Sales Cloud objects that natively support custom External ID fields, which can be used as the matching key for upsert operations via the API (e.g., a SOAP/REST upsert with an externalIdFieldName). Lead supports External IDs, allowing leads to be upserted by a unique external key before conversion. Account and Contact both support External IDs, which is essential for integrating with external systems and preventing duplicate records during data migration. Options A and C are not correct: OpportunityLineItem and Task do not support custom External ID fields, so they cannot be used as the external ID match field for upsert operations.

Answer

OpportunityLineItem

Answer

Task