Question bank
Salesforce Certified Sales Cloud Consultant
42 Salesforce Certified Sales Cloud Consultant questions with the correct answer and a written explanation, organised across 5 exam domains.
- 42 questions
- 5 domains
- Foundation level
certilumQuestion index
Jump straight to any question. Answers and explanations are inline.
Consulting and Implementation Strategies
8 questions in this domain
- Question 1Single Choice
Before the first import into Sales Cloud, what standard must be defined to ensure clean, trustworthy data?
- AGolden Record standardCorrect answer
- BRole Hierarchy
- CDashboard running user
- DManual sharing rule
Why this is the answer
A Golden Record standard defines the deduplicated, correctly formatted target state for each account or contact. Establishing it before import protects forecasting accuracy and rep productivity.
- Question 2Multiple Select
Which statements correctly describe the Extract, Transform, Load process when migrating data into Sales Cloud?
- AMaps legacy values to Salesforce picklists.Correct answer
- BPreserves deep hierarchy relationships.Correct answer
- COnly exports data from Salesforce.
- DEliminates need to map parent IDs.
Why this is the answer
ETL transforms legacy values into Salesforce picklist values and field types. For complex hierarchies, ETL tools are preferred over simple imports because they preserve relationships and parent IDs.
- Question 3Interactive
The JSON below defines a migration plan. Based on the code block, which statement is correct?
- AOpportunities load before Accounts via external IDs.
- BAccounts load first; child records use external IDs.Correct answer
- CExternal IDs are only needed for Contacts.
- DThe order shown creates orphaned opportunities.
Why this is the answer
The order loads Accounts, then Contacts, then Opportunities. Parent IDs are mapped with External IDs, preventing orphaned child records.
- Question 4Single Choice
What is the recommended migration approach when a client wants to avoid dual data entry and can accept higher cutover risk?
- ABig Bang migrationCorrect answer
- BPhased migration
- CIncremental validation
- DReconciliation only
Why this is the answer
Big Bang migration moves all data in a single cutover window, minimizing dual-entry time but increasing risk. Phased migration reduces risk but requires synchronization and more dual-entry time.
- Question 5Multiple Select
Which tasks should be included in post-migration reconciliation for a successful Sales Cloud data implementation?
- ACompare record counts with legacy system.Correct answer
- BCompare Opportunity Amount totals.Correct answer
- CVerify dashboard color schemes.
- DEnsure picklists have many values.
Why this is the answer
Post-migration reconciliation checks record counts and financial totals, such as Opportunity Amount, against the legacy system to confirm no data was lost or corrupted.
- Question 6Interactive
The code block shows a duplicate rule configured for Account. What happens when a user tries to save a duplicate record?
- ARecord is blocked from being saved.
- BUser sees a warning but can save.Correct answer
- CDuplicate is automatically merged.
- DUser bypassed with no warning.
Why this is the answer
An Alert action warns the user but allows the save to continue, while a Block action would prevent the record from being saved.
- Question 7Single Choice
Which element in the Salesforce sharing model establishes the most restrictive baseline for object access?
- AOrganization-Wide DefaultsCorrect answer
- BRole Hierarchy
- CSharing Rule
- DPermission Set
Why this is the answer
OWD is the most restrictive, foundational layer of record access, applying to records users do not own. Sharing Rules and Role Hierarchy extend access beyond OWD.
- Question 8Multiple Select
Which two statements correctly explain the difference between Profiles and Permission Sets versus Sharing Rules?
- AControls CRUD access to objects.Correct answer
- BGrants access to specific records.Correct answer
- CGrants access to one record.
- DGrants field-level permissions.
Why this is the answer
Profiles and Permission Sets define object-level CRUD permissions; Sharing Rules grant visibility to specific records. They operate at different layers of the security model.
Data Management
5 questions in this domain
- Question 9Single Choice
What does the acronym ETL stand for when migrating data from a legacy system into a Sales Cloud implementation?
- AExtract, Transform, LoadCorrect answer
- BEvaluate, Test, Launch
- CExport, Transfer, Leverage
- DEncode, Translate, Locate
Why this is the answer
ETL is defined as extracting data from legacy systems, transforming it to match Salesforce field types and picklist values, and loading it into the target organization.
- Question 10Multiple Select
Which actions are typically part of scrubbing and deduplicating data before a Sales Cloud migration is performed?
- ARemove duplicatesCorrect answer
- BCorrect formattingCorrect answer
- CFill missing mandatory fieldsCorrect answer
- DLoad records in any order
Why this is the answer
Data must be scrubbed to remove duplicates, correct formatting, and fill missing mandatory fields before import. This improves forecast accuracy and sales rep productivity.
- Question 11Interactive
Based on the configuration shown in the code block, what happens when a user saves a duplicate Account record?
- AA warning appears and the record is saved
- BThe save is blocked and no duplicate is createdCorrect answer
- CThe duplicate is converted into a lead
- DThe duplicate is shared with the manager
Why this is the answer
The code block displays a Duplicate Rule with the Block action, so a detected duplicate prevents the record from being saved.
- Question 12Single Choice
What is the purpose of a Matching Rule in Salesforce when managing duplicate records and data quality?
- ADefines logic to identify potential duplicatesCorrect answer
- BBlocks all users from creating records
- CAssigns record ownership to managers
- DControls fields on page layouts
Why this is the answer
Matching Rules define logic, using fuzzy or exact matching, to identify potential duplicate records based on predefined criteria such as name or address.
- Question 13Multiple Select
Which of the following are common duplicate management traps that a consultant should avoid in Salesforce implementations?
- AMatching Rule alone can block savesCorrect answer
- BOver-reliance on exact matchingCorrect answer
- CApplying Block rules too aggressivelyCorrect answer
- DUsing fuzzy matching for name variations
Why this is the answer
Matching Rules alone cannot block saves; only the Block action can. Exact matching fails on real-world variations, and aggressive Block rules create adoption problems.
Practical Application of Sales Cloud Expertise
14 questions in this domain
- Question 14Single Choice
What is the primary purpose of establishing a 'Golden Record' standard before a Sales Cloud data migration?
- AEnsures clean, deduplicated, complete data with required fields.Correct answer
- BAssigns sales territories automatically.
- CRemoves the need for data transformation.
- DCreates a backup of legacy records.
Why this is the answer
A Golden Record is the single high-quality version of a record. Data must be deduplicated, formatted correctly, and have mandatory fields populated before the first import to protect forecasting and rep productivity.
- Question 15Multiple Select
Which statements accurately describe ETL in a Sales Cloud migration?
- AExtracts data from legacy systems.Correct answer
- BTransforms data to match Salesforce field types and picklist values.Correct answer
- CIs preferred for complex, hierarchical relationships.Correct answer
- DEliminates the need to load data into the target org.
Why this is the answer
ETL means Extract, Transform, and Load. It extracts data, transforms it to match Salesforce field types and picklist values, and loads it. ETL tools are preferred when deep hierarchies must be maintained.
- Question 16Interactive
A consultant reviews the migration script in the code block. What does the script demonstrate?
- AParent records before children via External IDs.Correct answer
- BChild records before parent records.
- CUses standard Salesforce IDs for parent lookups.
- DMigrates all objects without sequencing.
Why this is the answer
The script loads Account before Contact and Opportunity and uses External IDs for parent lookups. This follows the required migration sequence and prevents orphaned child records.
- Question 17Single Choice
What is a major risk of using a Big Bang migration approach?
- AMoves all data at once, increasing risk.Correct answer
- BRequires long-term dual-entry between systems.
- CPrevents post-migration reconciliation.
- DMust be done by business unit.
Why this is the answer
Big Bang migration moves all data in a single cutover window. It avoids long dual-entry but increases risk because there is no iterative validation before the cutover completes.
- Question 18Multiple Select
Which tasks are part of post-migration data reconciliation?
- ACompare record counts between source and target.Correct answer
- BVerify Opportunity Amount totals match legacy values.Correct answer
- CConfirm standard Salesforce IDs match legacy primary keys.
- DCheck for data loss or corruption during transformation.Correct answer
Why this is the answer
Reconciliation compares record counts and key totals such as Opportunity Amount. Legacy primary keys should be mapped with External IDs, not standard Salesforce IDs, and data loss must be checked.
- Question 19Interactive
A consultant configures external ID fields as shown in the code block. What does this configuration enable during migration?
- AMaps legacy primary keys to parent-child records.Correct answer
- BReplaces the need for loading parent records.
- CAllows loading opportunities before accounts.
- DUses standard Salesforce IDs for record matching.
Why this is the answer
External ID fields store legacy primary keys and allow parent-child links to be created before new Salesforce record IDs are known, preventing orphaned records.
- Question 20Single Choice
What is the function of a Matching Rule in Salesforce duplicate management?
- AIdentifies possible duplicates using exact or fuzzy logic.Correct answer
- BBlocks duplicate records before they are saved.
- CMerges duplicate records automatically.
- DControls user access to duplicate records.
Why this is the answer
Matching Rules define the logic used to identify potential duplicates by comparing fields. They can use exact or fuzzy matching but do not take action on their own.
- Question 21Multiple Select
Which statements about Duplicate Rules are true?
- AUse Matching Rules to detect duplicate records.Correct answer
- BAlert action warns users but allows saving.Correct answer
- CBlock action prevents saving duplicate records.Correct answer
- DMatching Rules alone can block a record.
Why this is the answer
Duplicate Rules use Matching Rules as their enforcement engine. An Alert displays a warning, while Block prevents the save operation entirely.
- Question 22Interactive
A rule is configured as shown in the code block. What happens when a user saves a duplicate Account?
- AThe duplicate Account save is blocked.Correct answer
- BThe Account name is changed automatically.
- CThe Account is saved with an alert.
- DThe user is assigned a new Profile.
Why this is the answer
The action is set to Block. When a matching record is found, Salesforce prevents the duplicate Account from being saved.
- Question 23Single Choice
When is a custom Matching Rule most appropriate?
- AWhen standard rules do not cover the client's unique business logic.Correct answer
- BWhen no duplicate records exist in the legacy system.
- CWhen a Block action is required.
- DWhen exact matching is the only requirement.
Why this is the answer
Custom Matching Rules are needed when standard rules cannot represent the client's unique identifier logic, such as industry-specific account matching requirements.
- Question 24Multiple Select
Which methods can be used to manage existing duplicate records in Sales Cloud?
- ARun reports to identify duplicate records.Correct answer
- BUse mass-merge tools to consolidate duplicates.Correct answer
- CRely only on real-time Alerts to clean old duplicates.
- DDelete all suspected duplicates without review.
Why this is the answer
Reports can identify historical duplicates, and mass-merge tools consolidate them. Real-time rules prevent future duplicates but do not clean existing data.
- Question 25Interactive
A consultant creates only the configuration in the code block. Why can a duplicate Account still be saved?
- AA Matching Rule alone cannot block saves; a Duplicate Rule is required.Correct answer
- BFuzzy matching is unable to identify possible duplicates.
- CMatching Rules only work on Leads.
- DAccounts cannot be included in Matching Rules.
Why this is the answer
A Matching Rule only identifies potential duplicates. Without a Duplicate Rule configured with a Block action, the user can still save the record.
- Question 26Single Choice
What is the purpose of Organization-Wide Defaults in Sales Cloud?
- ASet baseline access to records not explicitly owned by a user.Correct answer
- BExtend access horizontally to groups or territories.
- CGrant object-level CRUD permissions.
- DDefine field-level security for each profile.
Why this is the answer
OWD is the baseline record access level for records not explicitly shared. Profiles and Sharing Rules build on top of it.
- Question 27Multiple Select
Which statements about Role Hierarchy and Sharing Rules are accurate?
- ARole Hierarchy gives managers access to subordinates' records.Correct answer
- BSharing Rules extend visibility across groups or territories.Correct answer
- CRole Hierarchy assigns object-level permissions.
- DSharing Rules can restrict access below OWD.
Why this is the answer
Role Hierarchy extends access vertically so managers see subordinates' records. Sharing Rules extend access horizontally to groups, territories, or criteria.
Predictive and Generative AI
4 questions in this domain
- Question 28Single Choice
In Duplicate Rules, what does the 'Block' action do when a duplicate record is detected?
- AIt prevents the record from being saved.Correct answer
- BIt displays a warning and still allows saving.
- CIt automatically merges the duplicate records.
- DIt sends an email alert to the system admin.
Why this is the answer
The Block action is the enforcement engine that stops the save operation, while the Alert action only warns and lets the user proceed. Merging and email alerts are not functions of Duplicate Rule actions.
- Question 29Multiple Select
Which statements about data migration using ETL and relational sequencing are correct? Select all that apply.
- AETL tools are preferred for deep hierarchies to preserve complex relationships.Correct answer
- BOpportunities should be loaded before Accounts to speed up migration.
- CExternal IDs should be used to map legacy keys to Salesforce records.Correct answer
- DAccounts must be migrated first, followed by Contacts and then Opportunities.Correct answer
Why this is the answer
ETL tools maintain complex relationships, and migration must follow parent-before-child order: Accounts first, Contacts next, Opportunities last. External IDs map legacy primary keys to Salesforce records.
- Question 30Interactive
The code block contains a proposed migration order. Based on relational mapping and sequencing, what is the key issue?
- AOpportunities cannot be loaded before their parent Accounts exist.Correct answer
- BContacts must always be migrated before Accounts because they are child records.
- CUsing external IDs invalidates the migration sequence.
- DThe sequence is valid as long as external IDs are used.
Why this is the answer
Parent records must exist before child records. Accounts are parents of Contacts and Opportunities, so they must be loaded first; loading Opportunities before Accounts creates orphaned records.
- Question 31Single Choice
Which security component controls CRUD operations on records a user can already see?
- AProfiles and Permission SetsCorrect answer
- BOrganization-Wide Defaults
- CSharing Rules
- DRole Hierarchy
Why this is the answer
Profiles and Permission Sets control object-level CRUD permissions. OWD, Sharing Rules, and Role Hierarchy control record visibility, not what users can do with accessible records.
Sales Lifecycle
11 questions in this domain
- Question 32Single Choice
In a Sales Cloud migration project, what is the main purpose of establishing a Golden Record standard before the first import?
- AEnsures clean and consistent dataCorrect answer
- BCreates an exact legacy copy
- CReplaces the need for ETL
- DAssigns Salesforce record IDs
Why this is the answer
A Golden Record standard defines a benchmark for clean data. It ensures duplicates are removed, formatting is corrected, and required fields are filled before the first import.
- Question 33Multiple Select
Which three data preparation tasks should be performed before legacy sales records are loaded into a Salesforce Sales Cloud org?
- ARemove duplicate recordsCorrect answer
- BCorrect field formattingCorrect answer
- CFill missing mandatory fieldsCorrect answer
- DDeactivate user profiles
Why this is the answer
Data cleansing includes removing duplicate records, correcting field formatting, and filling missing mandatory fields so the imported data meets quality standards before migration.
- Question 34Interactive
The pseudo-code below models a duplicate rule action in a Salesforce Sales Cloud configuration. What will the else branch do for the end user?
- ASaves record with warningCorrect answer
- BBlocks record from saving
- CSaves record silently
- DDeletes duplicate record
Why this is the answer
The else branch represents the Alert action. The user sees a warning that a duplicate exists, but the save operation is still allowed to continue.
- Question 35Single Choice
In a Salesforce Sales Cloud implementation, which order should be used to migrate records so parent-child relationships are preserved?
- AAccounts, Contacts, OpportunitiesCorrect answer
- BOpportunities, Accounts, Contacts
- CContacts, Opportunities, Accounts
- DAll objects in one batch
Why this is the answer
Parent records must exist before child records are loaded. Migrating Accounts first, then Contacts, then Opportunities preserves lookups and avoids orphaned records.
- Question 36Multiple Select
Which two characteristics correctly describe a Phased migration approach when moving data into a Salesforce Sales Cloud org?
- AAll data in one cutover
- BReduces migration riskCorrect answer
- CMigrates data in stagesCorrect answer
- DMinimizes dual-entry time
Why this is the answer
Phased migration moves data in stages, reducing risk and allowing iterative validation. It requires synchronization between old and new systems during the transition.
- Question 37Interactive
The code snippet uses an External ID to map a legacy account key. Why is this technique important when loading child records during migration?
- AMaps legacy IDs to child recordsCorrect answer
- BImproves field formatting
- CPrevents all duplicate records
- DChanges organization-wide defaults
Why this is the answer
External IDs retain legacy primary keys so child records can link to parent records without relying on Salesforce-generated record IDs. This prevents orphaned records during migration.
- Question 38Single Choice
Which migration tool is recommended for a complex Salesforce Sales Cloud implementation that must maintain deep record hierarchies?
- AETL toolsCorrect answer
- BData Import Wizard
- CLightning Email Templates
- DDashboard Builder
Why this is the answer
ETL tools are preferred for complex Sales Cloud implementations because they can transform data and maintain deep relational structures more reliably than basic import wizards.
- Question 39Multiple Select
Which two activities are part of post-migration data validation and reconciliation in a Salesforce Sales Cloud implementation?
- ACompare record countsCorrect answer
- BCompare Opportunity Amount totalsCorrect answer
- CCreate a public dashboard
- DConfigure sharing rules
Why this is the answer
Post-migration reconciliation checks that record counts and financial totals, such as Opportunity Amount, match the legacy system. This confirms no data was lost or corrupted.
- Question 40Interactive
The migration configuration shown below uses a simple import tool for a high-volume, deep-relationship Sales Cloud migration. What trap does this represent?
- ARelies on an all-in-one toolCorrect answer
- BIgnores field history
- CUses too many External IDs
- DEnables duplicate rules
Why this is the answer
Using the Data Import Wizard for high-volume, complex relational data is a common trap. ETL tools should be used when deep hierarchies must be preserved.
- Question 41Single Choice
Which configuration should a consultant create when a client needs custom duplicate matching logic on a custom Salesforce object?
- ACustom Matching RuleCorrect answer
- BStandard Email Template
- CRole Hierarchy
- DManual Share
Why this is the answer
Salesforce provides standard matching rules for objects like Accounts and Leads, but custom objects require custom matching rules to meet bespoke business requirements.
- Question 42Multiple Select
Which two statements about Duplicate Rules in Salesforce Sales Cloud are correct when used with Matching Rules?
- AUses Matching Rules to find duplicatesCorrect answer
- BCan only compare exact names
- CCan alert or block on duplicateCorrect answer
- DSets object-level security
Why this is the answer
Duplicate Rules rely on Matching Rules to identify potential duplicates and then enforce an action, either alerting the user or blocking the record save.
Frequently asked questions
Everything about the Salesforce Certified Sales Cloud Consultant question bank and how to use it.