Sign in
Home/Salesforce/Certified Sales Cloud Consultant/Free questions

Certified Sales Cloud Consultant — Free Practice Questions

10 free sample questions from a bank of 217, with the correct answers and explanations. No signup required — start practising right now.

1The sales management team at Northern Trail Outfitters (NTO) wants to analyze how the sales funnel is changing throughout the month. NTO wants to store the details of open opportunities weekly, and forecasts and closes business monthly. What should be recommended?
  • Schedule a custom forecast report to run weekly and store the results in a custom report folder.
  • Create a reporting snapshot to run weekly and store the results in a custom object.
  • Create a reporting snapshot to run daily and store the results in a custom object.
  • Schedule a custom forecast report to run daily and store the results in a custom report folder.
Answer: B

The short version

B — Weekly reporting snapshot stores funnel history. A snapshot runs a source report on schedule and writes point-in-time rows to a custom object for trend analysis. Forecast reports in folders cannot preserve weekly history for monthly closes.

Key concepts in this question

  • Funnel trending: comparing open pipeline week over week to see how stages and amounts shift through the month.
  • Reporting snapshots: analytic snapshots that map report results into custom object fields on a schedule.
  • Custom object storage: preserves historical values that would otherwise be overwritten as opportunities change.
  • Cadence alignment: weekly capture supports monthly forecast and close storytelling without daily noise.

Why B is correct

Management wants stored details of open opportunities each week plus monthly forecast context, which requires persisting report output over time. Creating a reporting snapshot to run weekly and store results in a custom object captures that weekly grain in a queryable form. It is the standard Salesforce pattern for pipeline history when native history tracking is insufficient.

Why the others are wrong

  • A. Scheduling a forecast report to a folder refreshes the view but does not write historical rows for trending.
  • C. Daily snapshots to a custom object overshoot the stated weekly need and add storage without benefit.
  • D. Daily forecast reports to a folder neither store trends nor match the weekly plus monthly rhythm.

Certified-Sales-Cloud-Consultant exam tip

For store pipeline weekly to show change, choose reporting snapshot to custom object.

2Universal Containers is planning to implement Salesforce Sales Cloud to support its professional services division. The Universal Containers sales team wants to easily see customer purchasing activity on account, contact, and contract detail pages. What should a consultant recommend to meet this requirement?
  • Enable Salesforce Console for Sales to see customer purchasing activity.
  • Create a custom object related to the account, contact, and contract objects.
  • Enable the Orders object in Salesforce to track customer purchases.
  • Create a global publisher action to view all customer purchasing activity.
Answer: C

The short version

C — Enable Orders to show purchasing activity. The standard Orders object links purchases to accounts, contacts and contracts for a unified customer view. Console, custom objects and publisher actions miss the native purchase model.

Key concepts in this question

  • Customer purchasing activity: line-level view of what was bought, when and under which contract or account.
  • Orders object: standard Salesforce record for committed purchases with products, quantities and fulfillment linkage.
  • Related lists on detail pages: expose orders directly on account, contact and contract layouts for easy discovery.
  • Native versus custom: standard objects bring reporting, sharing and lifecycle support without rebuild cost.

Why C is correct

The sales team needs purchasing activity visible on account, contact and contract detail pages in a professional services context. Enabling the Orders object provides a standard purchase record that relates across those parents and surfaces as related lists. It satisfies the requirement with supported tracking, reporting and contract association.

Why the others are wrong

  • A. Console for Sales improves agent productivity layout but does not itself create purchasing records.
  • B. A custom object related to three parents duplicates standard order capability with extra maintenance.
  • D. A global publisher action aids quick creation, it does not model or display purchase history.

Certified-Sales-Cloud-Consultant exam tip

When they ask see purchases on account contact contract, answer Orders.

3Cloud Kicks has a lengthy and complex sales cycle. Opportunities have twelve stages that sales reps must move a deal through, as well as indicate the probability of winning the sale. The sales manager presently uses sales stages and probability for forecasting and wants to simplify the process of reporting on projected sales for the sales team. Which approach should a Consultant recommend to streamline forecast reporting?
  • Align Opportunity stages with probability and use collaborative forecasts for reporting.
  • Reduce the number of Opportunity stages and report on forecast category.
  • Align forecast categories to multiple Opportunity stages and report on forecast category.
  • Reduce the number of Opportunity stages and report on probability.
Answer: C

The short version

C — Map many stages to forecast categories for simpler reporting. Keeping twelve operational stages while grouping them under standard categories preserves process detail and streamlines projections. Cutting stages or reporting on raw probability loses needed granularity.

Key concepts in this question

  • Twelve-stage sales cycle: detailed rep workflow that captures complex progression but complicates rollups.
  • Forecast categories: standard buckets like Pipeline, Best Case, Commit and Closed that drive Collaborative Forecasts.
  • Stage-to-category mapping: assigns each Opportunity stage to one category so detail rolls into a few forecast lines.
  • Probability alignment: stage probabilities inform weighting, but categories provide the stable reporting spine.

Why C is correct

The manager uses stages plus probability today and wants simpler projected-sales reporting without destroying the detailed process. Aligning forecast categories to multiple Opportunity stages lets all twelve stages remain while reports group by category. That delivers streamlined forecast reporting with minimal change to rep behavior.

Why the others are wrong

  • A. Aligning stages to probability and using forecasts keeps the complex stage sprawl in reporting.
  • B. Reducing stages and reporting on category discards operational detail the long cycle likely needs.
  • D. Reducing stages and reporting on probability creates volatile forecasts tied to per-stage estimates.

Certified-Sales-Cloud-Consultant exam tip

For many stages but simple forecasts, group stages under forecast categories.

4When an Opportunity Stage is marked as Closed Won, Cloud Kicks wants an email to be sent to a team of Executives. This email should include details about the Opportunity along with the related Opportunity Products and the Account. Which solution should the Consultant recommend to achieve this requirement?
  • Develop a custom Apex Trigger that uses custom email messaging.
  • Use Process Builder and HTML Email Templates.
  • Develop an Inbound Email Service.
  • Use Workflow rules and HTML Email Templates.
Answer: A

The short version

Cloud Kicks needs an executive email on Closed Won that includes Opportunity details plus related Opportunity Products and Account context in one message, so the solution must be able to query child and parent records and compose them reliably every time the stage changes.

Key concepts in this question

This question tests automation choice for Closed Won notifications, limits of declarative email alerts and templates, related list visibility in email, and when custom Apex messaging is justified to meet a multi-object requirement without fragile workarounds.

Why A is correct

Option A is correct because a custom Apex trigger with custom email messaging can query the Opportunity, its OpportunityLineItems, and its Account in one transaction, then build a single executive-ready email that always includes products and account context. Declarative alerts are constrained by template merge scope and related entity rules, so code is the dependable way to guarantee the full payload.

Why the others are wrong

Option B using Process Builder plus HTML templates cannot reliably render child product rows because merge scope is limited and cross-object merges are unsupported, so executives would get an incomplete summary. Option C for inbound email service is for receiving and processing incoming mail, not for sending Closed Won notifications. Option D with workflow rules plus HTML templates has the same related-list and merge limits as B and cannot guarantee products every time.

Certified-Sales-Cloud-Consultant exam tip

On the exam, when the requirement explicitly says include Opportunity Products in the email, favor the solution that can query child records. Declarative alerts are great for simple field merges, but multi-object product summaries point to Apex or Flow with careful template design.

5Cloud Kicks wants to utilize Opportunities to report and track subscription to its Shoe of the Month club. Subscribers can pay in full (all at one time), weekly, monthly, or quarterly. Which solution should the Consultant recommend to meet Cloud Kicks' needs?
  • Enable schedules on the Opportunity object.
  • Enable schedules on the Product object.
  • Configure the use of contracts with a lookup to the Opportunity object.
  • Configure the use of assets with a lookup to the Opportunity object.
Answer: B

The short version

Cloud Kicks sells a Shoe of the Month subscription with full, weekly, monthly, or quarterly payment patterns, so it needs installment tracking that spreads quantity and revenue over time and supports reporting by due date rather than a single Opportunity amount.

Key concepts in this question

This question tests product schedules versus Opportunity-level settings, quantity schedules versus revenue schedules, default schedules on the Product, and how reps establish line-level schedules to model subscriptions with flexible billing frequencies.

Why B is correct

Option B is correct because Salesforce product schedules are enabled in Setup under Product Schedules Settings and then defaulted per Product, letting each subscription product define weekly, monthly, or quarterly installments. Reps then establish the schedule on each Opportunity line, which creates dated payment rows for reporting and forecasting while keeping full-pay and installment models consistent.

Why the others are wrong

Option A to enable schedules on the Opportunity object misplaces the setting, since the org-level enablement and default cadence live with Product Schedules and the Product record. Option C with contracts plus lookup adds overhead for renewals and entitlements but does not create installment revenue rows. Option D with assets plus lookup tracks owned products after sale, not upcoming subscription payments, so it cannot report pipeline or due revenue by period.

Certified-Sales-Cloud-Consultant exam tip

Remember the path as Setup enablement plus Product default plus line-level establish. If the exam mentions weekly, monthly, quarterly, or full payment options for the same product, think product schedules immediately and check quantity versus revenue schedule choice.

6Cloud Kicks wants sales representatives to be able to share key documents directly with customers who are not Community users. Which Salesforce feature satisfies this requirement?
  • CRM Content
  • Chatter links
  • Documents
  • Attachments
Answer: A

The short version

A — CRM Content enables external document sharing. It publishes versioned sales collateral with links that non-community customers can open directly. Chatter, Documents and Attachments lack that controlled external path.

Key concepts in this question

  • External sharing with customers: sending key files to buyers who have no portal or community login.
  • CRM Content: library-based content delivery with sharing links, versioning and engagement tracking.
  • Chatter links: internal collaboration references that assume Salesforce access.
  • Legacy storage: Documents tab and record Attachments are internal and poorly suited for customer distribution.

Why A is correct

Reps must share key documents directly with customers who are not Community users, so the solution must generate an externally accessible link with governance. CRM Content satisfies this by letting reps share curated files outside the org while retaining version control. It is the Salesforce feature designed for that rep-to-customer handoff.

Why the others are wrong

  • B. Chatter links target internal followers and require access the external customer lacks.
  • C. The Documents tab stores internal templates and images, not customer-facing shared links.
  • D. Attachments cling to single records and offer no managed external sharing experience.

Certified-Sales-Cloud-Consultant exam tip

For share files with non-community customers, pick CRM Content.

7The Sales Manager at Cloud Kicks has asked an analyst to create a report when Opportunities reach a certain stage with an amount equal to $100,000 dollars. The analyst saves the report to the sales team's subfolder called Big Deals. The Big Deals folder is a subfolder of the sales team folder, with View access to the Sales Manager roles. The Sales Manager wants to subscribe to the report. Which permission does the Sales Manager need in order to subscribe to the report created by the analyst?
  • Subscribe to Reports permission
  • Subscribe to Reports: Run Reports permission
  • Chatter Subscribe to Reports permission
  • Subscribe to Reports: Set Running User permission
Answer: A

The short version

A — Subscribe to Reports permission is the requirement. The manager already has View access to the Big Deals subfolder, so folder access is satisfied and only the user permission to subscribe remains. With it, the manager can subscribe and control frequency and conditions.

Key concepts in this question

  • Report subscription: a personal schedule that runs a report and emails results, requiring both folder access and a user permission.
  • Folder sharing: View access on the report folder lets a user run and view the report, but does not by itself allow subscriptions.
  • Subscribe to Reports permission: the base user permission that enables the Subscribe button and scheduled report emails for oneself.
  • Extended subscription permissions: separate rights for subscribing others or setting another running user, needed only for admin-style distribution.

Why A is correct

The scenario states the Big Deals subfolder already grants View access to Sales Manager roles, so the run and visibility precondition is met. Salesforce still requires the Subscribe to Reports user permission before the Subscribe option and frequency controls appear. Granting that single base permission therefore unlocks self-subscription without changing folder sharing or delegating to others.

Why the others are wrong

  • B. Subscribing others or using Run Reports style distribution is unnecessary when the manager subscribes for self only.
  • C. Chatter feed tracking or Chatter-based follow is a different notification path and does not enable report subscriptions.
  • D. Setting another running user is an administrator capability for sending as someone else, not needed for personal subscription.

Certified-Sales-Cloud-Consultant exam tip

Remember folder View plus Subscribe to Reports equals self-subscription, while Subscribe for others and Set Running User are add-on rights.

8Management at Northern Trail Outfitters wants to see forecast numbers by all sales representatives and by multiple product groups. Which two actions should a consultant recommend to meet these requirements? (Choose two.)
  • Build a custom forecast report showing product groups.
  • Implement Collaborative Forecasting with quota attainment.
  • Build a forecast list view by product family group.
  • Implement Collaborative Forecasting with product family.
Answer: B, D

The short version

BD — Collaborative Forecasting with product family plus quotas covers both asks. Rep-level forecasts with quota attainment show who delivers while family grouping shows what delivers.

Key concepts in this question

  • Collaborative Forecasting: rollups by rep, territory, and hierarchy with commit, best case, and quota views.
  • Product family forecasting: forecast types by family let leaders slice pipeline by product group.
  • Quota attainment: comparing forecast to quota reveals coverage gaps per sales representative.
  • Custom report limits: standalone forecast reports lack commit workflow and live rollup behavior.
  • List view limits: list views filter records but do not provide forecast rollups or quota math.

Why BD is correct

Implementing Collaborative Forecasting with quota attainment gives management live forecast numbers by each sales representative with attainment context, supporting coaching and capacity calls. Adding product family as a forecast dimension lets the same forecast break out by multiple product groups without separate spreadsheets. Together they deliver rep plus product visibility in one governed forecasting motion.

Why the others are wrong

  • A. Custom forecast report showing product groups is static reporting and misses commit, rollup, and quota workflow.
  • C. Forecast list view by product family filters rows but cannot roll up commits or compare to quota.

Certified-Sales-Cloud-Consultant exam tip

Rep plus product group forecasting equals Collaborative Forecasting with family and quotas.

9Cloud Kicks requires sales associates to record all activities within Salesforce. Which sales metric can be derived from these activities?
  • Close Rate
  • Marketing Influence
  • Forecast Accuracy
  • Rate of Contact
Answer: D

The short version

D — Logged activities yield Rate of Contact. Complete task and event capture lets managers measure outreach tempo per rep, account or period. Close rate, marketing influence and forecast accuracy depend on outcomes beyond activity volume.

Key concepts in this question

  • Activity capture: tasks, calls, emails and meetings recorded consistently inside Salesforce.
  • Rate of Contact: frequency metric showing how often reps touch customers over a defined interval.
  • Outcome metrics: close rate and forecast accuracy blend activity with stage movement and judgment.
  • Attribution metrics: marketing influence needs campaign linkage, not just raw activity counts.

Why D is correct

The premise is that every associate records all activities in Salesforce, creating a complete interaction dataset. From that foundation the directly derivable sales metric is how frequently contacts are being touched, expressed as Rate of Contact. The other options require opportunity results, campaign association or prediction logic that activities alone cannot prove.

Why the others are wrong

  • A. Close Rate needs won versus total opportunities, not merely activity counts.
  • B. Marketing Influence needs campaign member attribution beyond logged sales tasks.
  • C. Forecast Accuracy compares predicted versus actual revenue, not activity frequency.

Certified-Sales-Cloud-Consultant exam tip

If the input is only logged activities, the output is contact rate.

10Cloud Kicks wants to allow a single view of Contacts that belong to the same Account Hierarchy chain. How should the Consultant meet this requirement?
  • Navigate to the default Contact Hierarchy Lightning Component on the parent Account.
  • Enable the View All Child Contacts feature.
  • Navigate to the Account Hierarchy page to view all related Contacts.
  • Create a report to display all related Contacts.
Answer: A

The short version

A — Use the Contact Hierarchy component on the parent Account. The Lightning component shows Contacts across the hierarchy chain in one place. Reports, hierarchy pages and unproven features do not give the same single view.

Key concepts in this question

  • Account Hierarchy chain: parent plus child accounts linked for enterprise selling and service context.
  • Contacts across accounts: buyers and stakeholders scattered on different hierarchy nodes.
  • Contact Hierarchy Lightning Component: standard component that aggregates related Contacts for the viewed hierarchy.
  • Single-view requirement: one screen that avoids hopping between child accounts.

Why A is correct

The consultant must surface every Contact belonging to the same Account Hierarchy chain without custom development. Navigating to the default Contact Hierarchy Lightning Component on the parent Account presents those Contacts together in the intended hierarchy context. That meets the single-view ask with standard Lightning capability.

Why the others are wrong

  • B. A View All Child Contacts toggle is not the standard mechanism for this hierarchy-wide contact view.
  • C. The Account Hierarchy page focuses on account structure, not the consolidated contact list.
  • D. A report can list Contacts but lacks the embedded single-view hierarchy experience requested.

Certified-Sales-Cloud-Consultant exam tip

For one view of hierarchy contacts, go to the Contact Hierarchy component.

Want the full bank of 217 questions for Certified Sales Cloud Consultant? See all practice exams.