CRT-251 Sample Questions & Answers

Einstein Activity Capture is designed specifically to solve this problem. It connects to Microsoft 365 (or Google) accounts and automatically syncs emails and calendar events with matching contacts and opportunities in Salesforce, eliminating the need for manual logging by sales reps. Salesforce for Outlook is a legacy product and is being retired.

Using standard, declarative features is a core Salesforce best practice. It keeps the solution within budget (less development cost), makes it easier to maintain and adapt by administrators ('future-proof'), and ensures compatibility with future Salesforce releases.

Designing for scalability is key to creating a 'future-proof' solution. This involves avoiding hard-coded IDs, considering large data volume implications, and building a flexible data model that can accommodate growth without requiring a complete redesign.

Account Teams are the standard mechanism for granting access to a specific Account (including Person Accounts) for a group of users who work on it together. This approach allows for granular control over access levels (e.g., Account Read/Write, Opportunity Read Only) for each team member on a record-by-record basis without affecting the overall sharing model. It is the most appropriate and scalable solution for collaborative, exception-based sharing.

Reporting Snapshots are designed for this exact purpose. They allow you to capture point-in-time data from a source report and save it to a custom object. By creating a source report filtered for opportunities in the 'Negotiation' stage and scheduling a snapshot to run on the first of each month, the system will build a historical record of the pipeline, which can then be reported on to show trends over time.

Product Schedules are the standard feature for managing products that are delivered or paid for over time. Enabling Revenue Schedules allows you to define how revenue from a product line item is recognized across a specific period (e.g., monthly). When used, the forecast will be based on the scheduled amounts for the given forecast period, rather than the total opportunity amount, directly meeting the complex forecasting requirement.

The standard, out-of-the-box process for a qualified lead handoff in Salesforce is Lead Conversion. When an SDR determines a lead is qualified, they click the 'Convert' button. This action creates a new Account, Contact, and optionally an Opportunity, and assigns ownership to the appropriate AE. This formally moves the record from the marketing/SDR pipeline to the sales pipeline.

Using Record Types is the best practice for segmenting a single object to support different business processes or data categorizations. By creating 'Direct Sale' and 'Partner Sale' record types, you create a definitive field on every opportunity that can be used for filtering reports and dashboards. This allows for easy comparison of KPIs like win rate and deal size across the two segments and can also be used to assign different page layouts or sales processes if needed in the future.

This is the most modern and robust solution. A before-save Flow is highly efficient and can query for existing, recently created opportunities against the same Account. The Custom Error element is specifically designed to prevent a DML operation (the save) and display a user-friendly, custom error message directly on the screen, meeting all requirements. A Validation Rule cannot perform the necessary queries on other records to check for existing opportunities, and an Apex trigger would be a programmatic solution for a problem solvable declaratively.

Given the integration with an external ERP, SIT is critical to ensure that data flows correctly between the two systems and that the end-to-end business process works as designed.

UAT is essential for any project. It involves end-users (the sales team) testing the system to confirm it meets their business requirements and is usable for their daily tasks. It's the final sign-off before go-live.

Because the project involves multiple complex components (automation, territories, integration), regression testing is crucial to ensure that a change or fix in one area does not inadvertently break existing functionality in another.

This is true. For Revenue Splits, which are used for crediting team members with a percentage of the total opportunity amount, Salesforce enforces that the total of all splits for a given opportunity must sum to exactly 100%. This ensures accurate crediting and reporting. Overlay splits, however, do not have this requirement and can total more than 100%.