Salesforce Sales-Cloud-Consultant Certified Salesforce Sales Cloud Consultant (SP23) Exam Practice Test

A cross filter is a feature that allows users to filter a report by related objects and their fields, such as accounts with or without opportunities. A cross filter can be added to any report type that supports cross filters, such as accounts, contacts, leads, or opportunities. By using a cross filter, Universal Containers can build a report that shows accounts with opportunities that are missing contacts, such as accounts with opportunities without contacts.

Inbox is a suite of email productivity tools that integrates Salesforce with Outlook or Gmail. With Inbox, sales reps can sync their calender events between Salesforce and their email application, and log emails with related records in Salesforce without leaving their inbox. This way, they can easily track their customer interactions and report on them in Salesforce.

• The close date regardless of the opportunity stage is how the converted currency amount calculation on Opportunities is determined when using dated exchange rates and Advanced Currency Management. Dated exchange rates are exchange rates that are tied to specific dates or ranges of dates. Advanced Currency Management is a feature that allows users to enable dated exchange rates and track historical exchange rates in Salesforce. When using dated exchange rates and Advanced Currency Management, the converted currency amount on Opportunities is calculated based on the exchange rate that matches the close date of the Opportunity, regardless of whether the Opportunity is open or closed.

User stories are a way of capturing requirements using an Agile methodology. User stories describe what a user wants to do, why they want to do it, and how it will benefit them. User stories are written from the user’s perspective, using simple and clear language. User stories can help the consultant understand the customer’s needs and priorities, and deliver value in small and frequent increments. Verified References:

• https://developer.salesforce.com/resources2/certification-site/files/SGCertifiedSalesCloudConsultant.pdf (page 19)
• https://trailhead.salesforce.com/en/content/learn/modules/agile-development-with-salesforce-dx/write-user-stories

Lead to Opportunity Conversion Rate is a metric that measures how many leads are converted into opportunities in relation to the total number of leads generated or processed in a given period. This metric can help evaluate the quality of leads and the effectiveness of lead qualification processes by showing how well leads are turning into potential sales. A high Lead to Opportunity Conversion Rate indicates that the leads are well-targeted, qualified, and nurtured, and that the sales team is following up on them promptly and persuasively. A low Lead to Opportunity Conversion Rate may suggest that the leads are poorly sourced, unqualified, or neglected, and that the sales team is missing out on opportunities.

These three reasons could explain the sales rep’s experience of being able to edit some opportunities associated with accounts they own, but not others. If the organization-wide defaults for opportunities are set to Private, then the sales rep can only edit the opportunities that they own or that are explicitly shared with them. If all provisioned Opportunity object permissions enable Read access with all accounts the sales rep owns, then the sales rep can view but not edit any opportunity associated with their accounts, regardless of who owns the opportunity. If some opportunities associated with the sales rep’s account are owned by other users, then the sales rep can only edit those opportunities if they have been shared with them or if they have a higher role in the role hierarchy than the owner.

• Setting obtainable metrics, goals, and milestones for the deadline is the best way to meet the requirement of tracking accounts, contacts, and opportunities before the global conference in 4 months. Metrics are measures of performance or progress that can be quantified and tracked. Goals are desired outcomes or results that can be achieved by following a plan or strategy. Milestones are significant events or stages that mark the completion of a part of a project or a goal. By setting obtainable metrics, goals, and milestones for the deadline, the consultant can ensure that the Sales Cloud implementation is realistic, manageable, and aligned with the client’s expectations and needs.

The Salesforce Adoption Dashboards provide visibility into how users are adopting and interacting with Salesforce. The region chart shows the number of logins, page views, and other metrics by region. This can help the consultant determine if all regions are using Salesforce effectively. 

The Lightning Usage App is a tool that provides insights into how users are adopting and interacting with Salesforce features, such as Salesforce Files and multi-factor authentication. The app includes dashboards and reports that show metrics such as file views, downloads, uploads, previews, shares, multi-factor authentication logins, and more. The app can help admins monitor user behavior and identify areas for improvement or training.

Configuring a new Forecast Type on Opportunity Product grouped by Product Family can improve CK’s forecasts by dividing them by footwear line. A Forecast Type is a set of settings that define how forecasts are calculated and displayed for a specific business scenario, such as product line, territory, or revenue type. A Forecast Type can use either standard or custom opportunity fields to group and filter forecast data, such as Type, Product Family, or Territory. By grouping forecast data by Product Family, CK can see how much revenue they expect to close for each footwear line, such as Formal or Athletic.

Adding the Lead Score field to the Lead Page layout is a necessary step to fix the issue of pilot users not being able to view the Lead Score field on the Lead record page. The Lead Score field is a standard field that shows how likely a lead is to convert based on Einstein’s analysis of historical data and predictive factors. The Lead Score field must be added to the Lead Page layout for users to see it on their lead records. Assigning the Einstein Lead Scoring permission set is another necessary step to fix the issue, as it grants users access to view and use Einstein Lead Scoring features, such as Lead Score, Lead Score Insights, and Lead Score Field History Tracking.

• Updating a custom field using automation and creating a report and dashboard are the two steps required to create a solution for showing the percentage of opportunities in a certain stage that were eventually closed won. A custom field is a field that can be added to an object to store additional information that is not available in the standard fields. Automation is a way of executing actions or tasks based on certain criteria or triggers, such as workflows, process builder, flows, etc. A report is a tool that displays data from one or more objects in a tabular or graphical format. A dashboard is a tool that displays data from one or more reports in a visual way, such as charts, gauges, tables, etc.
• By creating a custom field on the Opportunity object that stores the stage value when the Opportunity is closed won or closed lost, and updating this field using automation whenever the stage changes, sales managers can track the original stage of each closed Opportunity. By creating a report and dashboard that show the percentage of closed won Opportunities by their original stage, sales managers can see how effective each stage is in leading to successful deals.

This is the approach that the consultant should use for the source data migration. Accounts, Contacts, and Opportunities are related objects in Salesforce, and they have dependencies based on their lookup or master-detail relationships. Accounts are parent objects of Contacts and Opportunities, so they should be migrated first. Contacts are child objects of Accounts and parent objects of Opportunity Contact Roles, so they should be migrated second. Opportunities are child objects of Accounts and parent objects of Opportunity Products and Opportunity Splits, so they should be migrated last. Verified References: [Data Migration Best Practices]

Schedules on the Product object allow users to track the revenue and quantity of products over time, such as for subscription or installment payments. Schedules can be enabled for any product that has a schedule type of Revenue or Quantity, and they can be customized to match the payment terms of each opportunity.

• Enabling parenthetical currency conversion is the best way to allow the sales team to report on Australian deal values in U.S. Dollars (USD). Parenthetical currency conversion is a feature that displays converted currency amounts in parentheses next to the original currency amounts in reports and dashboards. For example, if an opportunity has an amount of 10,000 Australian Dollars (AUD), and the corporate currency is USD, enabling parenthetical currency conversion will show the amount as 10,000 AUD (7,500 USD) based on the exchange rate. By enabling parenthetical currency conversion, the sales team can easily see and compare Australian deal values in USD without having to manually calculate them.

This answer will allow CK to build a report that shows Accounts with open Opportunities that are missing Contacts, by using a cross filter to filter Accounts by related objects. A cross filter can show records that have or do not have related records, such as Accounts without Contacts. Official References: [Cross Filters]

This is how CK can revoke Opportunity team access on an ad-hoc basis. Opportunity teams are groups of users who work together on an opportunity and share access to it. Users can add or remove team members as needed, and specify different levels of access for each team member. By removing a user’s Opportunity team member, CK can revoke their access to the opportunity without affecting other team members or changing the sharing model. Verified References: [Opportunity Teams]

The best way for the consultant to present the information about how sales reps use Salesforce to work a deal is to utilize a Business Process Map. This map will provide an overview of the process, and can be used to explain how each step of the process works. Additionally, a Business Process Map can also be used to identify areas of optimization and improvement, as well as to document any changes that need to be made. A Sales Architecture Map, System Landscape Diagram, and Entity Relationship Diagram are not suitable for this purpose.

Opportunity Splits is a Salesforce feature that allows users to allocate credit to multiple sales reps who collaborate on an opportunity. Users can define different types of splits, such as revenue splits or overlay splits, and assign percentages or amounts to each team member. Opportunity Splits can help track individual and team performance against sales quotas and goals. Verified References: [Opportunity Splits]

• Implementing sales processes that map to each Opportunity record type and creating Opportunity record types for each product line are the two actions that can meet these requirements. A sales process is a set of stages that represent the steps in your sales cycle for a specific product line or business unit. An Opportunity record type is a way to offer different business processes, picklist values, and page layouts to different users based on their profiles. By creating Opportunity record types for each product line and mapping them to different sales processes, sales reps can follow the product-specific sales cycle once they qualify a prospect.

Using a validation rule on Opportunity Products can prevent a sales rep from adding Products marked as requiring the myTrailhead badge if the rep has yet to complete the badge. The validation rule can check the value of a custom field on the Product object that indicates whether the myTrailhead badge is required, and compare it with a custom field on the User object that tracks whether the sales rep has completed the badge. If the validation rule evaluates to true, it can display an error message and block the addition of the Product. Using a separate price book for the Products requiring the myTrailhead badge and only sharing the price book with sales reps who have completed the badge can also validate that sales reps have completed the myTrailhead badge. The price book can contain only the Products that require the badge, and it can be shared with sales reps who have a custom field on their User record that indicates they have completed the badge. This way, only those sales reps can access and add those Products to their Opportunities.

To convert a lead into a Person Account, the Company field must be populated with ‘Person’. This indicates that the lead is an individual consumer and not a business account. If the Company field is left blank, the lead conversion will fail.

Revenue Schedules allow you to recognize revenue from a product over a period of time, rather than at the time of sale. You can create revenue schedules for products that are paid in instalments, and specify the amount and date of each instalment. This can help the finance department forecast the revenue more accurately and easily. Verified References:

• https://developer.salesforce.com/resources2/certification-site/files/SGCertifiedSalesCloudConsultant.pdf (page 15)
• https://help.salesforce.com/s/articleView?id=sf.forecasts3_revenue_schedule.htm&type=5

• Setting up Account Teams with defaults for each sales rep is the best solution to meet the requirement of ensuring that the assigned sales ops specialist and sales engineer have access to the correct Accounts. An Account Team is a group of users who work together on an Account, such as sales reps, sales engineers, managers, etc. Each Account Team member has a role and a level of access to the Account and its related records, such as Contacts, Opportunities, Cases, etc. By setting up Account Teams with defaults for each sales rep, the admin can automatically add the sales ops specialist and the sales engineer to the Account Team whenever a sales rep creates or owns an Account. This way, the sales ops specialist and the sales engineer can view and edit the Account and its related Contacts.

These two groups should provide content for the use cases for Sales Processes for Cloud Kicks. Sales reps are the primary users of the Sales Processes and they can provide information about their daily activities, challenges, needs, and expectations. Sales operations are responsible for designing, implementing, and managing the Sales Processes and they can provide information about the business requirements, best practices, metrics, and goals.

These are two actions that the consultant should recommend to work around the issue of internet unavailability on the Salesforce mobile app. Enabling the system permission to store offline data in Salesforce allows users to access cached data on their mobile devices when they are offline. Enabling offline create, edit, and delete in Salesforce allows users to perform these actions on their cached data when they are offline, and sync them back to Salesforce when they are online. Verified References: [Work Offline in the Salesforce Mobile App]

Salesforce Connect allows you to access data from external sources without copying it to Salesforce. You can create external objects that map to the data in the external system, and use them in Salesforce like any other objects. This can help you view and update customer billing information from another Salesforce org within your current org. Verified References:

• https://developer.salesforce.com/resources2/certification-site/files/SGCertifiedSalesCloudConsultant.pdf (page 16)
• https://help.salesforce.com/s/articleView?id=sf.data_access_salesforce_connect.htm&type=5

Salesforce Maps is a feature that allows users to visualize and optimize their sales territories and activities on interactive maps. Users can also access various data sources to enrich their maps with additional information, such as demographics, weather, traffic, or business data. The Demographic Context data source is one of the data sources that users can add to their maps to display income ranges for regions within their territories, such as zip codes, counties, or states. This can help sales reps determine the best neighborhoods to canvas based on the household income range of their potential customers.

This is the step that the consultant should take to troubleshoot the issue of inaccurate sales forecasting. Stage to Forecast Category Mappings are settings that determine how each opportunity stage is mapped to a forecast category, such as Pipeline, Best Case, Commit, or Closed. These mappings affect how opportunities are rolled up and calculated in forecasts. If some opportunities appear in the incorrect forecast category, it may indicate that the mappings are not configured correctly or consistently for each stage. Verified References: [Set Up Stage to Forecast Category Mappings]

• Gaining buy-in during the Analyze phase is the best way to avoid user adoption issues in the future when working on a new system at Cloud Kicks. Buy-in is the acceptance or support of an idea or proposal by stakeholders or decision-makers who have influence or authority over its implementation or outcome. The Analyze phase is a stage of a project where requirements are gathered and validated, business processes are mapped and optimized, and solutions are designed and evaluated. By gaining buy-in during the Analyze phase, the consultant can ensure that the new system meets the needs and expectations of the users and stakeholders, and that they are involved and engaged in the project from the start. This can increase user satisfaction and adoption of the new system.

Contact roles on the Opportunity object allow sales executives to identify the contacts who are involved in the sales process and their roles, such as decision maker or influencer4. This helps sales executives prioritize their interactions with existing contacts and track their influence on the opportunity.

Opportunity Splits allow users to divide credit for an opportunity among multiple sales reps who contribute to closing it. Users can specify how much revenue or quantity each sales rep receives from an opportunity, either as a percentage or an amount. Opportunity Splits can be enabled from Setup, and they require that Opportunity Teams are also enabled. Users can then add or edit Opportunity Splits from the Opportunity Splits related list on Opportunity page layouts.

• Setting up an External ID field on the Account object with Read Only on the field security settings for all profiles except the admin profile ensures data integrity between the data warehouse and Salesforce. An External ID field is a custom field that has the “External ID” attribute, meaning that it contains unique record identifiers from a system outside of Salesforce. By making it Read Only for all profiles except the admin profile, the field value can only be updated by the integration or by the admin, preventing any accidental or intentional changes by other users. The External ID field can also be used to match records during data import or update operations, avoiding duplicate records or incorrect data.

• Confirming that the custom matching rule is activated is the best way to resolve the issue of duplicate leads in Salesforce. A matching rule is a rule that defines how records are compared for duplicates based on fields and fuzzy logic. A custom matching rule is a matching rule that can be created and customized by users based on their needs and preferences. A custom matching rule must be activated before it can be used by duplicate rules or other features that prevent or allow duplicates. By confirming that the custom matching rule is activated, the admin can ensure that leads are matched according to their criteria and duplicates are detected and handled accordingly.

These are the prerequisites for enabling Person Accounts in a Salesforce org, as stated in the documentation. Person Accounts are a special type of account that combines account and contact data into a single record. They are useful for B2C scenarios where individuals are customers rather than organizations.

These are two aspects that a consultant should consider for migrating Territory Management to a new structure for the upcoming fiscal year. Territories can inherit assignment rules from other territories higher in the model, which can simplify the process of assigning accounts and users to multiple territories. Only one territory model can be active at any given time, which means that you need to deactivate the current model before activating the new one, and ensure that there is no gap in territory coverage. Verified References:

• https://developer.salesforce.com/resources2/certification-site/files/SGCertifiedSalesCloudConsultant.pdf (page 22)
• https://help.salesforce.com/s/articleView?id=sf.customize_territories.htm&type=5

This solution will meet the requirement by allowing Universal Containers to divide the revenue of the closed Opportunities between sales reps that worked on the deal and credit technical sales managers for their support. Enabling Opportunity splits will allow sales reps to share credit for an Opportunity with other team members based on their contribution or involvement in closing a deal. Revenue splits will allow sales reps to divide a percentage of an Opportunity’s amount among team members who helped generate revenue for that Opportunity. Overlay splits will allow sales reps to give credit to team members who provided assistance or support for that Opportunity without generating revenue directly.

• Account Roll-up Summary fields will update from the Opportunity object is something that Cloud Kicks should consider when enabling Advanced Currency Management in its Salesforce org. A Roll-up Summary field is a field that calculates values from related records, such as count, sum, min, max, etc. Advanced Currency Management is a feature that allows users to enable dated exchange rates and track historical exchange rates in Salesforce. By enabling Advanced Currency Management, Cloud Kicks can use dated exchange rates to convert currency amounts based on specific dates or ranges of dates. When using dated exchange rates, Account Roll-up Summary fields will update from the Opportunity object based on the close date of the opportunities, regardless of whether the opportunities are open or closed.

• The data update will cause sharing recalculations and should be completed during off-peak hours and the team can defer sharing calculations to decrease the risk of lock errors during the data update are two factors that should be considered when updating the sales territories and Account owners for 400,000 accounts with Private organization-wide defaults. Sharing recalculations are processes that update record access based on changes to sharing settings or ownership. Off-peak hours are times when there is less user activity or system load on Salesforce. Deferring sharing calculations is an option that allows users to postpone or schedule sharing recalculations for later times instead of running them immediately. Lock errors are errors that occur when two or more processes try to access or modify the same record at the same time.
• By considering these two factors, Universal Containers can ensure that the data update is performed efficiently and effectively without affecting user experience or data integrity. By completing the data update during off-peak hours, Universal Containers can avoid impacting user performance or availability during peak hours when there is more user activity or system load on Salesforce. By deferring sharing calculations, Universal Containers can reduce the risk of lock errors during the data update by running them at a later time when there is less concurrent access or modification of records.

Deploying the changes from the sandbox to production once both environments are on the same version is the safest and most reliable option, as it ensures that there are no compatibility issues or errors due to different versions of Salesforce. The fix requires functionality in the sandbox version, which means that it cannot be deployed to production until production is upgraded to the same version. Deploying before or during the upgrade window may result in failures or conflicts.

These are two steps that the consultant should take to meet the requirement of tracking closed won opportunities generated by a campaign over the last 30 days using standard functionality. Customizable Campaign Influence is a feature that allows users to measure and report on how campaigns influence opportunities throughout the sales cycle. Users can define different influence models, such as first touch, last touch, or custom rules, and assign percentages or amounts of credit to each campaign that influenced an opportunity. Auto-association settings are options that determine how campaigns are automatically associated with opportunities based on criteria such as contact roles, time frames, or record types. By adding criteria to limit the matches to the past 30 days, CK can ensure that only recent campaigns are associated with opportunities. By enabling Customizable Campaign Influence, CK can use reports and dashboards to analyze how many closed won opportunities a campaign has generated based on different influence models. Verified References: [Customizable Campaign Influence]; [Auto-Association Settings for Customizable Campaign Influence]

• Creating an Opportunity History report for open pipeline Opportunities in a given date range is the best way to meet the requirement of providing visibility on sales pipeline changes on a monthly basis. An Opportunity History report is a report that shows how opportunities have changed over time based on historical data, such as stage, amount, probability, etc. An open pipeline Opportunity is an opportunity that has not been closed yet and has a positive amount and probability. A date range is a filter that limits the report data to a specific period of time, such as last month, this month, next month, etc. By creating an Opportunity History report for open pipeline Opportunities in a given date range, Universal Containers’ sales operations team can track and compare how the sales pipeline has changed from month to month based on different metrics and dimensions.

A. Create criteria-based opportunity sharing rules for each product line. This allows you to specify criteria for sharing an Opportunity with a specific user or group of users. For example, you could create a rule that shares an Opportunity with the product engineer when the Opportunity has a certain product line assigned to it. B. Enable Default Opportunity Teams for the Opportunity. This allows you to set a default Opportunity Team for an Opportunity, which will automatically assign the product engineer to the Opportunity when it is created. This is useful when you need to assign a specific user to multiple Opportunities.

Revenue Schedules are a feature that allow users to track the revenue and quantity of products over time, such as for subscription or installment payments. Revenue Schedules can be enabled for any product that has a schedule type of Revenue or Quantity, and they can be customized to match the payment terms of each opportunity. By using Revenue Schedules, Universal Containers can capture the installment payment plan details for each product, such as the number of installments, the amount per installment, and the frequency of installments. This can help the finance department forecast the revenue and cash flow from each opportunity more accurately.

Configuring Path by checking the key field required checkbox can ensure that opportunity stage reports always contain the data managers expect, as it makes certain fields mandatory for users to fill in before they can move an opportunity to a specific stage. Path is a feature that guides users through a set of stages for a particular business process, such as opportunity sales stages. Users can see key fields and guidance for each stage, and update them as they progress along the path. Marking fields as required on the page layout can also ensure that opportunity stage reports always contain the data managers expect, as it prevents users from saving an opportunity record without entering values for those fields. Page layouts control how fields, related lists, and other components are arranged on a record detail or edit page.

• Approach and Scope are two sections of a SOW that the consultant should discuss further with Cloud Kicks to meet the requirement of clearly stating who will train users on new features and how the training will be delivered. A SOW is a document that defines the project objectives, deliverables, timeline, costs, and responsibilities of both parties involved in a project. The Approach section describes the methodology and strategy that will be used to achieve the project objectives and deliverables. The Scope section defines the specific work items and activities that will be performed as part of the project, as well as any assumptions, exclusions, or dependencies. By discussing these two sections with Cloud Kicks, the consultant can specify who will be responsible for providing user training (e.g., consultant or client), what type of training will be offered (e.g., online or onsite), how many sessions will be conducted (e.g., one or multiple), what topics will be covered (e.g., new features or best practices), etc.

Record types allow you to assign different page layouts, picklist values, and business processes to different users based on their profiles. You can create three record types for the three product lines, and assign them to the appropriate sales teams. You can also create three sets of opportunity stages that reflect the unique sales methodologies for each product line, and associate them with the corresponding record types. This can help you customize the Sales Cloud functionality for each product line and track their progress separately. Verified References:

• https://developer.salesforce.com/resources2/certification-site/files/SGCertifiedSalesCloudConsultant.pdf (page 17)
• https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.customize_opptystages.htm&type=5

• The Opportunity’s Account will be implicitly Read for the team is something that the consultant should consider when rolling out Opportunity Teams with Private Account organization-wide defaults. An Opportunity Team is a group of users who work together on an Opportunity, such as sales reps, sales engineers, managers, etc. Each Opportunity Team member has a role and a level of access to the Opportunity and its related records, such as Products, Quotes, Activities, etc. Organization-wide defaults are the baseline level of access that users have to records they do not own or share. Private organization-wide defaults mean that only the record owner and users above them in the role hierarchy can view and edit the records. Implicit sharing is a type of sharing that grants additional access to records based on relationships between objects or users. Implicit Read means that users can view but not edit a record.
• By rolling out Opportunity Teams with Private Account organization-wide defaults, the consultant should consider that the Opportunity Team members will have implicit Read access to the Opportunity’s Account, meaning that they can view but not edit the Account record related to the Opportunity they are working on.