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

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]

To migrate all the sales data into CK’s Salesforce instance, the consultant should recommend the following data migration sequence for the objects:

• Accounts
• Opportunities
• Contacts
• Products
• Product Line Items
• Cases
• Leads
• Campaigns

This sequence ensures that all the parent records are created before their child records, and that all the lookup and master-detail relationships are preserved. For example, an opportunity must have an account before it can be created, and a product line item must have an opportunity and a product before it can be created.

The Data Import Wizard and the Data Loader are both tools that can import data into Salesforce and assign records to a queue or run an active assignment rule1. The Data Import Wizard can import up to 50,000 records at a time, while the Data Loader can import up to 5 million records at a time2. Both tools can also prevent duplicates by matching records based on external IDs or Salesforce record IDs3.

• Using Salesforce Maps, configure a Data Layer showing open opportunities is the best solution to meet the requirement of visualizing all open opportunities based on the location of the related Account. Salesforce Maps is a feature that allows users to view and manage their geographic data on an interactive map. A Data Layer is a layer of data that can be added to a map to show records from one or more objects based on filters and criteria. By using Salesforce Maps, configure a Data Layer showing open opportunities, Cloud Kicks sales representatives can see all open opportunities on a map based on the address fields of their related accounts, and perform actions such as creating tasks, logging calls, updating fields, etc.

Multiple Forecast Types must be created and activated to enable forecasting for different product lines that have different sales stages. 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. The Forecast tab should be visible to easily view the forecasts, as it allows users to see their forecast amounts, quotas, adjustments, and categories in a single page. Users can also drill down into forecast details, compare forecasts with other users or periods, and submit or approve forecasts from the Forecast tab.

Creating a junction object between Campaign and Opportunity is the best way to track which marketing activities influenced a customer to make a purchase. This junction object will allow you to track the influence of multiple Campaigns on a single Opportunity, which can be used to gain insights into which Campaigns are most effective.

• Adding specific users as Opportunity team members with a role that grants Read/Write access allows account executives to share their Opportunities with other users who can help them qualify marketing Opportunities on their Accounts. Opportunity team members can view, edit, and delete the Opportunity, as well as add products, quotes, and activities. Sales management can report on which users are assigned to Opportunities by using the Opportunity Team Member report type.

• Deploying after the Salesforce Release ensures that the configuration is compatible with the latest version of Salesforce and avoids any potential issues or errors that might arise from deploying during a release window.
• Testing new configurations in a Preview Sandbox allows the configuration to be validated against the upcoming Salesforce Release before deploying to production. A Preview Sandbox is a sandbox that is upgraded when the next release begins its preview period.

• 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.

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.

When Account Teams are enabled and used for an account, Sales Rep A can grant Read access on the account’s cases to Sales Rep B by adding Sales Rep B as a team member on the account and assigning a team role that has Read access to cases. Sales Rep A can also allow Sales Rep B to view one of the opportunities on the account by adding Sales Rep B as a team member on that opportunity and assigning a team role that has at least Read access to opportunities.

• Building in a Developer Sandbox and testing changes in a test release environment is the best practice for creating a new process that uses most of the objects that were deployed. A Developer Sandbox is a type of sandbox that provides an isolated copy of the production environment for development purposes. A test release environment is another type of sandbox that provides an isolated copy of the production environment for testing purposes before deploying changes to production.
• By building in a Developer Sandbox, the admin can create and modify configurations without affecting the production environment or other sandboxes. By testing changes in a test release environment, the admin can validate and verify the functionality and performance of the new process before deploying it to production.

These are two considerations that the consultant should take into account when deciding on the timing of the release. Testing changes in a Full Sandbox can help ensure that the changes work as expected and do not cause any errors or conflicts in Production. Installing a new incentive management package along with Territory Management changes may introduce high risk to the deployment, as both changes can affect sales performance, reporting, forecasting, and compensation. It may be advisable to stagger the releases or perform them during off-peak hours to minimize the impact on users and business operations.

To retain the company history of contractors who change companies often, the consultant should recommend implementing the Contacts to Multiple Accounts feature. This feature allows a contact to be related to multiple accounts without creating duplicate records. This way, CK can track the relationship between a contractor and all the companies they have worked with. The consultant can also create a custom role field on the account contact relationship object to indicate the role of the contractor at each company.

When you adjust the exchange rates in a multi-currency org, the new rates only apply to new opportunities that are created or updated after the change. The old opportunities will retain the conversion rate that was in effect when they were last modified. This can help you preserve historical data and avoid recalculating closed opportunities. Verified References:

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

Dividing the development team into three units/tracks can help each line of business have dedicated resources and avoid conflicts or delays in delivering their solutions. This also allows each unit/track to have more autonomy and flexibility in managing their own projects and releases. Proposing a monthly executive steering committee can help align the business and technology stakeholders on the strategic direction, budget allocation, and development capacity of each line of business. This can also help resolve any issues or disputes that arise among different groups and ensure that the development team is not overloaded or underutilized.

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.

Salesforce Trust is a website that provides information about the performance, security, compliance, and maintenance of the Salesforce platform. Users can check for scheduled system maintenance on Salesforce Trust by selecting their instance and viewing the maintenance calendar. Users can also subscribe to receive notifications about maintenance events via email or RSS feed.

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

• Mass transferring the records to another role in the role hierarchy and removing the users from the role hierarchy are two solutions that can resolve the issue of making changes to the sharing model taking increasingly more time for users who own more than 10,000 records. A mass transfer is an operation that allows users to transfer ownership of multiple records from one user to another user at once. A role hierarchy is a structure that defines how users are organized and how data access is granted based on their roles. By mass transferring the records to another role in the role hierarchy, Cloud Kicks can reduce the number of records owned by each user and distribute them more evenly among other users in different roles. By removing the users from the role hierarchy, Cloud Kicks can prevent these users from inheriting access to records owned by other users in their role or below their role, which can slow down the sharing model changes.

Moving the invoice related list to a separate tab on the Lightning page can solve the issue of long rendering time, as it allows the account record to load faster without loading the invoice related list at the same time. The user can then click on the tab to view the invoice related list when needed. This also improves the user experience and the page layout by reducing clutter and scrolling.

• 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.

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. 

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.

Advanced Currency Management allows you to specify different conversion rates for different time periods, such as monthly or quarterly, and use them in reports and forecasts. This can help you generate accurate reporting that reflects the currency fluctuations over time. Org-wide reporting can also display deal values in different currencies based on the user’s preference or the corporate currency. Verified References:

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

Changing the Account organization-wide defaults to Public/Read-Only will allow reps to view any Account but not edit them. Enabling Account Teams will allow owners to grant Read/Write access to specific reps who are responsible for those Accounts. This will ensure that only the relevant reps can edit the Accounts they are assigned to1

• Using quotation marks operator around contact’s first and last name is a recommendation that can yield better search results when searching for contacts in global search. Global search is a feature that allows users to search for records or information across multiple objects and fields in Salesforce. Quotation marks operator is an operator that can be used in global search to find an exact phrase or match in a record or field. For example, searching for “John Smith” will return only records or fields that contain John Smith as an exact phrase or match, not John Doe or Adam Smith or John Smithson. By using quotation marks operator around contact’s first and last name, Cloud Kicks users can narrow down their search results and find the contacts they are looking for more easily and quickly.

• EAC a two-way sync for events and contacts means that EAC can synchronize events and contacts between Salesforce and the connected email and calendar applications, such as Gmail or Outlook. This minimizes the need for sales reps to manually create meetings and events that are stored on their calendars, as they will be automatically captured and displayed in Salesforce.
• EAC supports emails, events, and contacts means that EAC can capture these types of activities from the connected email and calendar applications and display them in Salesforce. This allows sales reps to view and track their interactions with customers without having to manually log them in Salesforce.

• Territory Management is the best solution for assigning sales Opportunities based on ZIP codes. Territory Management is a feature that allows sales organizations to structure their sales territories based on criteria such as geography, industry, product line, etc. A territory is a group of accounts and users that share common characteristics or business needs. By using Territory Management, sales teams can define territories based on ZIP codes and assign accounts and Opportunities to those territories automatically or manually.

• Using the Related List - Single component to display the Account’s Contracts on the Opportunity Lightning page is the best way to meet the requirement of viewing all contracts for the Account on the Opportunity record. A Related List - Single component is a Lightning component that shows a single related list of records from another object on a record page. A Contract is a record that represents an agreement between an Account and an organization for products or services sold or delivered by an organization. By using the Related List - Single component to display the Account’s Contracts on the Opportunity Lightning page, sales reps can easily see all contracts for the Account related to an Opportunity without having to navigate to another page or create another lookup field.

Path is a feature that helps users visualize and update key fields for each stage of a process, such as an opportunity sales process. By checking the Key Field Required checkbox, the consultant can make sure that users enter the data that managers expect at each stage before moving to the next stage. This can improve data quality and reporting accuracy.

These are three steps that a consultant should complete to prepare for a successful engagement during the Discovery phase of a project. Establishing project goals can help align the expectations and priorities of the stakeholders and the project team, and provide a clear direction for the project. Defining sales processes can help understand the current and desired state of the customer’s business operations, and identify the gaps and opportunities for improvement. Defining success metrics can help measure the impact and value of the project, and evaluate the progress and outcomes of the project. Verified References:

• https://developer.salesforce.com/resources2/certification-site/files/SGCertifiedSalesCloudConsultant.pdf (page 18)
• https://trailhead.salesforce.com/en/content/learn/modules/consulting_skills_for_salesforce_professionals/discover-the-customer-situation

• 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.

To set sales quotas for all sales reps, the consultant should consider the following solutions:

• Enable Forecast Quotas from Setup. This allows the administrator to enable quotas for users and assign them to forecast types.
• Use the API. This allows the administrator to import quota data from external sources using SOAP or REST API calls.
• Use Data Loader. This allows the administrator to import quota data from CSV files using a graphical user interface.

Einstein Forecasting uses machine learning to analyze historical opportunity data and generate predictions for how much revenue a sales team can expect to close in a given period. The predictions are based only on the standard Close Date and Amount fields of the opportunities, so any custom fields or other factors are not taken into account. The predictions are only shown when the user is in the forecasting hierarchy, which means that they have a forecast role assigned to them and they can view forecasts for themselves or their subordinates.

The Insert Availability feature in Salesforce Inbox allows sales reps to share their available time slots with prospective clients via email, and let them book a meeting with a single click. This eliminates the back-and-forth communication and manual coordination of finding a suitable time for both parties. The booked meeting is then automatically added to the sales reps’ Salesforce calendar and synced with their Outlook or Gmail calendar.

• Running the updated assignment rules in Planning State and viewing the accounts on the territory detail page is the best way to show sales operations what the data will look like after changing the territories. Assignment rules are rules that determine how accounts are assigned to territories based on criteria such as account fields, address fields, etc. Planning State is a mode of Territory Management that allows users to preview how changes to territories or assignment rules will affect account assignments before activating them. The territory detail page is a page that shows information about a specific territory, such as name, description, users, accounts, etc.
• By running the updated assignment rules in Planning State, sales operations can see how accounts will be reassigned to new territories based on the ZIP codes. By viewing the accounts on the territory detail page, sales operations can verify the accuracy of the account assignments and make any adjustments if needed.

Deploying with Change Sets is a way to migrate Account Team configuration to Production. A Change Set is a collection of metadata components that can be moved from one Salesforce org to another, such as custom objects, fields, workflows, or profiles. Account Team configuration is a type of metadata component that defines how users can share access to accounts and related records with other users based on their team roles and responsibilities. Users can create an outbound Change Set in their source org (such as Sandbox), add Account Team configuration components to it, upload it to their target org (such as Production), and deploy it in their target org after validating it.

Account Teams are groups of users who work together on an account and its related records, such as opportunities, contracts, and cases. Account Teams allow users to share different levels of access to accounts and associated records based on their team roles and responsibilities. For example, a sales rep may have full access to an account and its opportunities, while a customer service agent may have read-only access to the account and full access to its cases.

• Adoption Dashboards Pack is the best feature to measure core Sales Cloud record data and track data trends and adoption after implementing Sales Cloud for a mid market sales team. Adoption Dashboards Pack is a package that contains pre-built dashboards and reports that show how users are adopting and using Salesforce features and functionalities, such as creating and updating records, logging activities, running reports, etc. By using Adoption Dashboards Pack, Universal Containers sales management can monitor and analyze core Sales Cloud record data such as accounts, contacts, opportunities, etc., and see how they change over time and across different dimensions.

These are the actions that can meet the requirement of restricting access to opportunities based on ownership and account association. Setting opportunity access on the role allows users to see opportunities owned by users below them in the role hierarchy, as well as opportunities associated with accounts they can access. Setting organization-wide defaults for opportunities to Private means that users can only access opportunities they own, unless they are granted access by other means, such as sharing rules or manual sharing. 

• Implementing Platform Events to publish opportunity wins to the ESB, which will call back for account, contact, and opportunity information and automatically update the ERP accordingly is the best option to meet the requirement of updating the ERP system with information from Salesforce when a new Account has its first closed/won opportunity. Platform Events are events that are published and consumed by applications inside or outside of Salesforce using an event-driven architecture. An ESB (Enterprise Service Bus) is a software component that connects different applications and systems using common standards and protocols. By implementing Platform Events to publish opportunity wins to the ESB, Cloud Kicks can trigger an event whenever an opportunity is closed/won for a new Account in Salesforce, and send it to the ESB. The ESB can then call back for account, contact, and opportunity information from Salesforce using APIs (Application Programming Interfaces), and automatically update the ERP system with this information accordingly. This way, Cloud Kicks can ensure data synchronization and accuracy between Salesforce and the ERP system without having to use third-party tools or manual processes.

When a Salesforce admin assigns User A as the owner of an opportunity related to User B’s account, User A will have Read-Write access to the opportunity’s Account and its related contact records. This is because of the implicit sharing rules that grant access to parent and child records based on the organization-wide default settings. Since the organization-wide default setting for Account is set to Private, users are unable to see each other’s accounts by default. However, when a user owns an opportunity that is related to another user’s account, the user gains Read-Write access to that account and its related contacts, regardless of the sharing settings for those objects. This ensures that the user can view and edit the account and contact information that is relevant to their opportunity.

Enhanced Folder Sharing is a feature that allows users to share reports and dashboards with other users, groups, roles, or territories based on different access levels, such as view, edit, or manage. This can help sales reps find the reports and dashboards that are relevant to them by organizing them into folders and granting access to the appropriate users. Enhanced Folder Sharing also supports inheritance, which means that users who have access to a folder also have access to its subfolders.