Last Updated On : 17-Nov-2026
Salesforce Agentforce Sales Consultant - Sales-Con-201 Practice Test
Prepare with our free Salesforce Agentforce Sales Consultant - Sales-Con-201 sample questions and pass with confidence. Our Sales-Cloud-Consultant practice test is designed to help you succeed on exam day.
Salesforce 2026
Data Management
The sales director at Cloud Kicks wants to prevent users from viewing each other’s Opportunities but wants them to check to see that the Account already exists prior to creating a new Account. Which organization-wide default should the consultant recommend?
A. Set Account and Opportunity to Public Read Only.
B. Set Account to Public Read Only and use & criteria-based sharing rule on Opportunity.
C. Set Account to Public Read Only and set Opportunity to Private.
Explanation
Why This Option Is Correct:
Account Requirement: Sales reps need to check if an Account already exists before creating a new one. Setting the Account Organization-Wide Default (OWD) to Public Read Only allows all users to search, view, and verify existing Accounts without allowing them to edit Accounts owned by others.
Opportunity Requirement: The sales director wants to prevent users from viewing each other's Opportunities. Setting the Opportunity OWD to Private restricts access so users can only view and manage Opportunities that they own (or that are shared with them via role hierarchy or explicit sharing).
Why the Other Options Are Incorrect:
Set Account and Opportunity to Public Read Only: Setting Opportunity OWD to Public Read Only would allow all users to see all Opportunities across the organization, directly violating the requirement to prevent users from viewing each other's Opportunities.
Set Account to Public Read Only and Use a Criteria-Based Sharing Rule on Opportunity: Sharing rules can only grant additional access—they can never restrict access below the Organization-Wide Default setting. If Opportunity OWD is not set to Private, you cannot restrict users from seeing each other's Opportunities.
References:
Organization-Wide Defaults (OWD): OWD defines the baseline level of access for records that a user does not own. It is the most restrictive setting in Salesforce's security architecture.
Implicit Sharing & Object Relationships: While Opportunity access in Salesforce defaults to being controlled by parent Accounts in some setups, setting Opportunity OWD explicitly to Private isolates Opportunity visibility regardless of Account access.
Sharing Model Principle: In Salesforce security design, you always start with the most restrictive baseline (OWD) and open access up using Role Hierarchy, Sharing Rules, and Manual Sharing.
Universal Containers has implemented Salesforce for all of its sales reps. All sales reps are required to select the win or loss stage on every closed opportunity. Managers like to measure the win ratio for all of the sales reps. How should a consultant meet the requirement?
A. Ensure that all managers have access to the standard Win report.
B. Build a custom report on Opportunity with custom summary formulas to show win ratio.
C. Create 3 custom formula field on Opportunity to capture the win ratio for opportunities.
Explanation:
Salesforce reports allow managers to analyze closed opportunities and calculate the win ratio for sales representatives using summary formulas.
The consultant should create an Opportunity report that includes closed opportunities and groups them by sales representative. A custom summary formula can calculate the win ratio by dividing the number of Closed Won opportunities by the total number of closed opportunities (Closed Won + Closed Lost).
Win Ratio Formula:
Win Ratio = (Number of Closed Won Opportunities / Total Number of Closed Opportunities) × 100
This approach allows managers to compare win ratios across representatives in a single report without creating unnecessary custom fields.
Why the Other Options Are Incorrect:
A. Ensure that all managers have access to the standard Win report. A standard report may provide information about won opportunities, but it does not necessarily calculate the win ratio by comparing won opportunities against all closed opportunities for each representative.
C. Create 3 custom formula fields on Opportunity to capture the win ratio for opportunities. Formula fields calculate values for individual records. They are not the most efficient way to calculate an aggregate win ratio across multiple opportunities. A summary formula in a report is better suited to this requirement.
Reference: Salesforce Help – Summary Formulas
Exam Tip: When a requirement involves calculating and comparing performance metrics across sales representatives, consider custom summary formulas in reports before adding custom fields to objects.
A consultant is implementing a new Sales Cloud instance for Cloud Kicks (CK) that has a public sharing model for Accounts. Different sales reps own local accounts that create a multi-level Account Hierarchy. CK needs to see the total number of closed won opportunities and the revenue value for all accounts in the hierarchy when viewing a parent account. Which recommendation meets this requirement?
A. Configure after-save flow to update a custom field on the parent account with the total value of won opportunities from the child accounts.
B. Reference the revenue totals on the parent accounts in the Account Hierarchy view.
C. Create a roll-up summary field on the Account with the total value of won opportunities from the child accounts.
Explanation:
CK needs aggregated closed-won opportunity counts and revenue across an entire multi-level account hierarchy, shown on the parent account. Standard declarative features can’t do this aggregation, so automation is needed. A record-triggered flow (after save) on Opportunity can:
- Fire when an Opportunity is created or updated to Closed Won (or when its amount changes).
- Find the related account and walk up the hierarchy through the parent accounts.
- Recalculate the total count and amount of won opportunities for the child accounts.
- Write those values to custom fields (for example, Total Won Opportunities and Total Won Revenue) on the parent account.
With a public sharing model, the sales reps who own the local accounts don’t need to share records for this to work. The flow can run in system context and update the parent regardless of who owns it.
Why the Other Options Are Wrong:
Roll-Up Summary Field on the Account: Roll-up summary fields work only on the master side of a master-detail relationship. Opportunity is related to Account by a lookup, not a master-detail relationship. The Account hierarchy (Parent Account) is also a lookup, so a roll-up summary can’t aggregate opportunities from child accounts through the hierarchy.
Reference Revenue Totals on the Parent Accounts in the Account Hierarchy View: The Account Hierarchy view only displays field values from each individual account in the tree, with columns configured by the admin. It doesn’t calculate or aggregate opportunity data, so it can’t show hierarchy-wide won opportunity totals unless a field already holds that data.
References:
- Salesforce Help: Roll-Up Summary Field Considerations (requires a master-detail relationship).
- Salesforce Help: Record-Triggered Flows and Account Hierarchy View.
- Trailhead: Flow Builder and Data Management modules.
When a lead is created, Cloud Kicks wants to implement rules to assign the lead to the appropriate user. The new record should have the assignee ' s default record type. Which approach should the consultant recommend to meet the requirement most efficiently?
A. Match the record type of assignee in the User settings.
B. Use Lead settings to set the record type of the assignee.
C. Create a flow to update the lead record type of the assignee.
Explanation:
In Salesforce, a user’s default record type is configured in their profile or assigned permission sets, depending on the object and Salesforce configuration. When a lead is assigned to a user, Salesforce does not automatically change the lead’s record type to match that user’s default record type.
To meet this requirement efficiently, the consultant should configure the appropriate lead record type settings for the users who may receive leads and ensure the lead creation and assignment process selects the intended record type. This avoids unnecessary automation.
Why the Other Options Are Incorrect:
B. Use Lead Settings to Set the Record Type of the Assignee: Lead settings control lead-related behavior, such as assignment rules, but do not automatically set a lead’s record type based on the assigned user’s default record type.
C. Create a Flow to Update the Lead Record Type of the Assignee: A flow could automate record-type selection, but it adds unnecessary complexity if the requirement can be addressed through appropriate configuration.
Reference:
Salesforce Help – Record Types
Exam Tip:
Salesforce lead assignment rules determine who receives a lead. Record types determine which business process and page layout apply. Assigning a lead to a user does not, by itself, make the lead inherit that user’s default record type.
Universal Containers has implemented a lead qualification process that uses a lead scoring
formula. Upon review, many of the converted leads with the highest scores had little
interest in making a
purchase.
Which modification to the current lead qualification process should a consultant
recommend?
A. Include a measure for the number of marketing touches.
B. Increase points for actions that Indicate Intent.
C. Evaluate each record against the target marketing persona.
Explanation:
🔍 Why This Is Correct:
The issue described is that high-scoring leads aren't converting into real opportunities — meaning the scoring model is likely overvaluing superficial engagement (e.g., email opens, page views) and undervaluing true buying signals.
By increasing points for intent-based actions — such as requesting a demo, visiting pricing pages, downloading product specs, or attending sales webinars — the scoring model becomes more predictive of actual purchase behavior.
This aligns the lead score more closely with sales readiness, improving conversion quality.
❌ Why Not the Others?
A. Include a measure for the number of marketing touches
More touches might indicate interest, but it could also reflect indecision or lack of clarity. Quantity ≠ quality.
C. Evaluate each record against the target marketing persona
Helpful for segmentation, but not a direct fix for scoring logic. Personas guide messaging, not necessarily scoring accuracy.
🧠 Consultant Tip:
When refining lead scoring, always ask:
Are we measuring engagement or intent?
Are we aligning scoring criteria with sales feedback?
Are we continuously validating scoring against conversion outcomes?
| Page 1 out of 38 Pages |