Sales Cloud Consultant Practice Questions

Actions available in the Salesforce Mobile App and Lightning Experience are controlled by the 'Salesforce Mobile and Lightning Experience Actions' section on the page layout. Even if a user has the correct object permissions, if the specific action (like the standard 'New Account' quick action) is not included in this section of the assigned page layout (either global or object-specific), it will not be visible to the user on mobile or in Lightning's dynamic action bar.

Contact Roles on the Opportunity object allow sales reps to specify the role each contact plays in a specific deal (e.g., 'Decision Maker', 'Influencer'). This data then feeds into the Contact Relationship Map, which provides a visual hierarchy or org chart of these contacts, fulfilling the requirement for a visual representation of stakeholders and their roles.

With a Private OWD, you need to open up access. Since SDRs and AEs are likely in different branches of the role hierarchy, a sharing rule is required. Creating a Public Group for each role allows the sharing rule to be defined based on record ownership ('Records owned by members of AE Group') and shared to the target users ('Share with members of SDR Group'). Setting the access level to 'Read-Only' meets the specific requirement. This is a standard and scalable pattern for cross-team visibility.

This is the core definition. Leads are 'raw' prospects that have not yet been vetted or qualified. They sit at the top of the sales funnel. The process of qualification involves determining if there is a genuine potential for a sale. If so, the Lead is converted, creating a Contact (the person), an Account (their company), and an Opportunity (the potential deal) to be managed through the rest of the sales cycle.

The standard Partner Community role hierarchy is designed for this exact use case. By default, Salesforce creates three roles for each partner account (User, Manager, Executive). When a Reseller is a child account of a Distributor account in the Account Hierarchy, placing the Distributor's users in a higher role (e.g., Executive) on their own account will grant them access to records owned by users in lower roles (e.g., User, Manager) at the child Reseller accounts. This uses standard, scalable functionality without needing custom code or complex sharing rules.

Collaborative Forecasts is the standard Salesforce feature designed for this exact scenario. Enabling forecast adjustments allows managers to change the forecast numbers submitted by their subordinates. The 'Manager Judgments' feature specifically allows them to provide a rationale for their adjustments, and the system retains visibility of both the original forecast and the adjusted amount, meeting all business requirements.

Sales Processes are designed to control the picklist values available for the Opportunity Stage field. Creating three separate Sales Processes allows the consultant to define the unique stages for each division.

Record Types are the mechanism that ties together different business processes, page layouts, and picklist values for different users. By creating a record type for each division, the consultant can assign the unique Sales Process (for stages) and a unique Page Layout (for division-specific fields) to each, providing a tailored user experience.

This is false. When you define a territory assignment rule, you can specify whether it should apply to accounts that already have a manual territory assignment. The default behavior is to not overwrite manual assignments, preserving any specific exceptions made by users. The administrator must explicitly configure the rule to clear existing manual assignments if that is the desired behavior.

The Bulk API is specifically designed for loading or deleting large sets of data. For volumes in the millions of records, it is the most performant and reliable option. Using it in 'Parallel mode' further enhances speed by processing multiple batches concurrently, which directly addresses the client's primary requirement of minimizing cutover downtime. The Data Import Wizard has a limit of 50,000 records, and the SOAP API processes records one at a time or in small batches, making it too slow for this scale.

Flow is the recommended tool for this scenario because it can be triggered by a record update (Contract status change) and can create a new, unrelated record (a new Opportunity). Workflow Rules and Process Builder are being retired, and Flow is the declarative future. A Workflow Rule cannot create new records (other than tasks). An Approval Process is not relevant. Flow can handle the conditional logic, record creation, and field calculations (Close Date = Contract End Date - 30 days) in a single, declarative process.