Sales Lifecycle practice questions

Change the forecast display setting from 'Amount' to 'Expected Revenue'.

Why it fails: Expected revenue multiplies by probability, which doesn't resolve structural double counting.

Disable the standard Revenue forecast type and ensure only one split-based forecast type is active.

Why it fails: Overlay splits double-count when both a revenue-based and a split-based forecast type run concurrently, since each independently aggregates the same opportunity amounts. Deactivating the standard Revenue forecast type leaves a single split-based forecast type as the sole aggregation path, eliminating the duplicate attribution in quota attainment rollups.

Enable Advanced Currency Management to handle overlay conversion rates.

Why it fails: Currency management affects exchange rates, not split calculations.

Einstein Email Insights

Why it fails: Insights provide sentiment and content analysis, not message authoring.

Einstein Generative AI Prompt Builder

Why it fails: Prompt builder generates dynamic text, but predefined approved templates are best for strict compliance.

Salesforce Surveys

Why it fails: Surveys are for gathering feedback.

Create a Record-Triggered Flow with a Custom Error element.

Why it fails: While flows can show custom errors, validation rules are the standard declarative tool for field-level edit restrictions based on stage.

Set up Field-Level Security to make all fields read-only for later stages.

Why it fails: FLS applies profile-wide, not conditionally based on stage.

By overriding user personal currency in the User Detail record.

Why it fails: That changes user currency, not forecast display globally.

Using custom report types with currency conversion formulas.

Why it fails: Forecasts do not rely on custom report types.

In the Company Information settings under Default Corporate Currency.

Why it fails: Corporate currency affects standard rollups, but forecast display currency has specific configuration options in forecast settings.

At least 24 months of historical data across all active sales stages.

Why it fails: 24 months is not the minimum requirement.

At least 3 months of closed opportunities and 500 closed-won deals.

Why it fails: Einstein Forecasting requires 24 months of closed opportunity history, not 3 months, so this threshold is far too low to train a seasonal revenue model. Three months is tempting because it matches the minimum pipeline duration many sales teams track, but that is a reporting window, not a forecasting data requirement.

At least 6 months of historical data and active Collaborative Forecasting enabled.

Why it fails: Six months of history is insufficient; Einstein Forecasting needs 24 months of closed opportunities to model quarterly seasonality. Enabling Collaborative Forecasting affects how forecasts are rolled up and shared, not whether the underlying model has enough training data, so it cannot resolve the insufficient-data message.

Custom Territory Sharing Sets

Why it fails: Sharing sets are for community users.

Territory Hierarchy Rollup Summaries

Why it fails: Rollup summaries do not handle assignment.

Enterprise Territory Management Account-to-Opportunity Synchronization Flow

Why it fails: Account-to-opportunity mapping is handled via filter rules or Apex, not a standard sync flow by that exact name.

Create a custom report type for 'Opportunities with or without Activities' and export to Excel.

Why it fails: Exporting is not a declarative reporting filter solution.

Build a summary report grouped by Last Modified Date with conditional highlighting.

Why it fails: Last modified date changes when emails are synced or background jobs run, which might not reflect genuine sales activity.

Use a joined report combining Opportunity details and Task details with a custom formula.

Why it fails: Joined reports cannot easily flag missing records across blocks without complex formulas.

Set up Enterprise Territory Management rules.

Why it fails: Territory management handles assignment, not stage gating.

Enable Sales Engagement Cadence branching logic.

Why it fails: Cadences manage outreach tasks, not stage transition gating.

Use custom Apex triggers to check training completion objects.

Why it fails: Path settings offer a declarative mechanism for key field validation during stage movement.

Einstein Activity Capture has not been enabled for the forecast owners.

Why it fails: Activity capture is separate from forecasting data.

Advanced Currency Management conversion rates are missing for historical dates.

Why it fails: Currency rates affect amounts, not the presence of forecast records.

Enterprise Territory Management is turned on, which disables role-based forecasting entirely.

Why it fails: Role-based forecasting can coexist with territory forecasting if separate forecast types are used.

Enable automatic opportunity sharing in Sharing Settings.

Why it fails: Sharing settings do not control territory assignment.

Run the 'Assign Accounts to Territories' batch job, which automatically cascades to child opportunities.

Why it fails: Account batch jobs only assign accounts, not automatically cascade to opportunities without filter rules.

Write an Apex scheduled job to generate PDF reports and email them.

Why it fails: Dashboards handle scheduled emails declaratively.

Export reports to CSV manually every week.

Why it fails: Manual export is not automated.

Set up Process Builder to email dashboard charts.

Why it fails: Process builder cannot email dashboards.

Create a workflow rule that emails management when unapproved discounts occur.

Why it fails: Workflows send emails; they do not fulfill reporting requirements.

Export opportunity data to Tableau CRM (CRM Analytics) for complex approval logic.

Why it fails: Tableau CRM is overkill when standard custom report types support Opportunities with Approval History.

Use the standard Opportunity Audit report type with cross-filters for approvals.

Why it fails: No standard Opportunity Audit report type exists with built-in approval cross-filters.

Configure a Sales Process to lock opportunity fields upon winning.

Why it fails: Sales processes don't lock fields.

Enable Field-Level Security for Closed Won profiles.

Why it fails: FLS is profile-based, not conditional on winning.

Donut Chart

Why it fails: Donut charts show proportions of a whole.

Scatter Plot

Why it fails: Scatter plots show correlation between two numerical variables.

Configure Lead Conversion Mapping settings to include task creation parameters.

Why it fails: Lead mapping only maps fields between lead and account/contact/opportunity.

Enable Einstein Lead Conversion Task Automation in Setup.

Why it fails: No such specific standalone toggle exists by that exact name.

Use Workflow Rules on the Lead object to trigger task creation on converted leads.

Why it fails: Workflow rules are largely retired in favor of flows and cannot easily target post-conversion opportunity owners.

Creating custom formula fields on the User object to concatenate all related data before prompting.

Why it fails: Prompt builder allows direct relationship traversal via merge resources.

Using Apex invocable methods to inject string variables into the prompt payload.

Why it fails: While Apex prompt templates exist, standard prompt templates support direct relationship traversal.

Writing SOQL queries inside the Prompt Builder text editor window.

Why it fails: Prompt Builder does not execute inline SOQL queries.

By enabling Lightning Email Reply tracking.

Why it fails: Email tracking tracks opens/clicks, not cadence exit triggers.

Through Workflow Rules on Lead and Contact objects.

Why it fails: Workflows do not control cadences.

In Einstein Activity Capture sync filters.

Why it fails: EAC syncs emails; it does not control cadence branching rules.

Set up monthly recurring revenue (MRR) schedules on Opportunity Products.

Why it fails: Product schedules track revenue schedules, not user sales quotas.

Build custom rollup summary fields on the Quotas object linked to users.

Why it fails: Quotas are natively supported in Collaborative Forecasting without custom rollups.

Create custom fiscal periods spanning one month each.

Why it fails: Custom fiscal years affect organization-wide reporting and should not be used merely for quota scheduling.

Use public groups with manual sharing on the Territory object.

Why it fails: Territories use specific sharing and model structures, not standard manual sharing rules.

Add the managers as delegates in Company Information.

Why it fails: Company information delegates have different scopes.

Enable Multi-Currency on Campaigns.

Why it fails: Multi-currency has nothing to do with lead conversion attribution.

Use standard Lead History reports grouped by Campaign ID.

Why it fails: Lead history tracks field changes, not campaign relationships.

Build a joined report with Lead block and Campaign block linked by owner ID.

Why it fails: Campaigns and leads are linked via Campaign Members, not owner IDs.