SASC

Free SASC practice questions

10 questions from our SASC practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.

Back to the SASC practice exams

Question 1 of 10, Consulting and Implementation Strategies

A company acquires a smaller competitor that also uses Agentforce Sales. Both sell to the same customers, and leadership wants a single view of each account and combined pipeline reporting within a year. The acquired company's processes are simple. What should the consultant recommend?

  1. AKeep both orgs permanently and build a nightly integration that copies every account between them
  2. BConsolidate into the acquiring company's org after aligning processes and deduplicating accounts Correct answer
  3. CKeep both orgs and have finance combine pipeline exports in a spreadsheet each week
  4. DCreate a new third org for the combined company and migrate both existing orgs into it from scratch

Answer and explanation: With shared customers, a simple acquired process, and a need for single account views and combined reporting, consolidating into the existing org after alignment and deduplication meets the goal at the lowest ongoing cost. Permanent bidirectional sync is complex and fragile. Spreadsheet consolidation does not give a single view, and building a new org from scratch adds cost and risk without a clear benefit.

Question 2 of 10, Consulting and Implementation Strategies

Three months after go-live, the sales director reports that reps still log deals in personal spreadsheets and opportunity data is stale. Login history shows most reps sign in daily. What is the MOST effective next step for the consultant?

  1. AInterview reps and observe their workflow to find which steps in Salesforce are slower than the spreadsheet Correct answer
  2. BAdd validation rules that block opportunity saves unless every field on the page layout has been completed by the rep
  3. CCreate a dashboard that ranks reps by weekly opportunity edits and share it with the team
  4. DSchedule a mandatory two-day refresher training for all reps that repeats the original go-live curriculum in full

Answer and explanation: Daily logins with continued spreadsheet use point to a usability or value gap, so the consultant should find the root cause by talking to and observing users. More required fields add friction and usually make adoption worse. Repeating the same training ignores why reps avoid the system, and ranking edit counts encourages meaningless updates rather than accurate data.

Question 3 of 10, Consulting and Implementation Strategies

A global company plans to roll out Agentforce Sales to North America, EMEA, and APAC. EMEA has strict data residency reviews that will take four extra months, while North America has the most mature processes. Leadership wants value quickly with the lowest risk. Which deployment approach should the consultant recommend?

  1. AA single big-bang go-live for all three regions on the same weekend so that the data model is identical everywhere
  2. BA separate production org for each region so that EMEA reviews cannot delay the other two regions in any way
  3. CA parallel run in every region where reps keep spreadsheets and Salesforce updated for six months before switching
  4. DA phased rollout that starts with North America and then adds APAC and EMEA using the lessons learned there Correct answer

Answer and explanation: A phased rollout delivers value early in the most ready region, reduces risk, and lets the team refine the approach before EMEA joins. A big-bang launch would be blocked by the EMEA review and concentrates risk. A long parallel run doubles rep effort and hurts adoption, and separate orgs add integration and reporting complexity that the requirements do not justify.

Question 4 of 10, Practical Application of Agentforce Sales Expertise

Account executives own accounts, but solution engineers and partner managers need edit access to specific opportunities and must receive overlay credit in forecasts. Which configuration meets these requirements?

  1. AAdd solution engineers above account executives in the role hierarchy so they inherit opportunity access
  2. BEnable Opportunity Teams plus opportunity splits that use an overlay split type so that engineers get credit Correct answer
  3. CUse account teams with edit access and report on credit with a custom percentage field on each account record
  4. DCreate sharing rules that give solution engineers read/write access to all opportunities in their region

Answer and explanation: Opportunity Teams grant per-opportunity access to the people working the deal, and overlay splits give them credit that can total more than 100% for forecasting. Region-wide sharing rules grant far more access than needed. Moving engineers above executives in the hierarchy distorts reporting lines, and an account-level percentage field does not feed overlay forecasts.

Question 5 of 10, Practical Application of Agentforce Sales Expertise

Leads arrive from many sources. Leads from the US go to regional queues, enterprise-size leads from any country go to a strategic team, and everything else goes to a general queue. Enterprise leads from the US must go to the strategic team. How should the lead assignment rule be structured?

  1. ACreate three separate active lead assignment rules, one for each routing outcome
  2. BUse one entry for all criteria with OR logic and assign the result to the general queue
  3. CPut the enterprise-size entry first, then the US regional entries, then a catch-all Correct answer
  4. DPut the US regional entries first, then the enterprise-size entry, then a catch-all

Answer and explanation: Assignment rule entries are evaluated in order and the first match wins, so the enterprise entry must come before the US regional entries to capture US enterprise leads. Placing US entries first would send those leads to regional queues. Only one lead assignment rule can be active at a time, and a single OR entry cannot route to different destinations.

Question 6 of 10, Sales Lifecycle

A software company sells new business through account executives and renewals through a renewals team. Leadership wants separate forecasts and pipeline reporting, but the same customers appear in both processes. What is the BEST solution?

  1. AOne sales process for both teams with a checkbox to mark renewals and manual report filters
  2. BA separate Agentforce Sales org for the renewals team integrated with the main org by API
  3. CSeparate opportunity record types and sales processes, plus a forecast type filtered by type Correct answer
  4. DA separate custom object for renewals that links to the account and has its own stage field

Answer and explanation: Record types with separate sales processes model the two motions on the standard opportunity, and forecast types can be filtered by opportunity type to give separate forecasts. A custom object loses standard forecasting and pipeline features. A checkbox with manual filters forces both teams through the same stages, and a second org adds cost and integration overhead.

Question 7 of 10, Sales Lifecycle

A sales director needs a single report showing each account with both its open opportunities and its open support cases side by side. Which report format should be used?

  1. AA joined report with an opportunities block and a cases block Correct answer
  2. BA summary report on opportunities with a cross filter on cases
  3. CA tabular report using a custom report type with opportunities and cases
  4. DA matrix report on accounts grouped by opportunity stage and case status

Answer and explanation: A joined report combines blocks from different report types and groups them by a common field such as account. A cross filter only filters opportunities by whether cases exist, without showing case details. A matrix on one report type cannot show two unrelated child objects side by side, and a report type cannot join two sibling children of account.

Question 8 of 10, Data Management

After migration, one integration user owns 300,000 accounts that will be reassigned later. Sharing recalculations are slow, and record locking errors occur during nightly updates. What should the consultant recommend?

  1. APlace the integration user in a mid-level regional sales role so that regional managers inherit access
  2. BRun the nightly updates in parallel Bulk API mode so that locks are released more quickly between batches
  3. CChange the account organization-wide default to Public Read/Write and add sharing rules for each region
  4. DDistribute ownership across multiple users and keep any remaining owner outside the role hierarchy Correct answer

Answer and explanation: A single user owning a very large number of records causes ownership skew, which slows sharing and causes lock contention; spreading ownership and leaving any remaining owner without a role (or in an isolated role) reduces recalculation. Placing the user inside a regional branch makes every role above it recalculate access for those records. Opening the sharing model weakens security without fixing skew, and parallel mode tends to increase lock errors.

Question 9 of 10, Data Management

During migration, many legacy opportunities are owned by reps who have left the company. The business still wants to report on historical win rates by the original rep. What should the consultant recommend?

  1. ACreate active licensed users for each departed rep and freeze them once the migration is done
  2. BAssign all departed reps' opportunities to the sales VP and note the original rep in Description
  3. CCreate the departed reps as inactive users and assign ownership to them during the load Correct answer
  4. DSkip any opportunity owned by a departed rep, since it adds no forecast value

Answer and explanation: Records can be owned by inactive users when loaded with the right permissions, which preserves historical ownership without consuming active licenses. Reassigning to the VP distorts rep-level reporting, and free text is hard to report on. Skipping the records loses history, and activating licenses for departed staff adds cost and security exposure.

Question 10 of 10, Predictive and Generative AI

Which statement correctly distinguishes predictive AI from generative AI in Agentforce Sales?

  1. APredictive AI is built from prompt templates; generative AI is trained on win/loss outcomes
  2. BPredictive AI scores likely outcomes; generative AI creates new content such as emails Correct answer
  3. CPredictive AI writes call summaries; generative AI calculates opportunity win scores
  4. DPredictive AI is used only on leads; generative AI is used only on opportunities

Answer and explanation: Predictive AI analyzes historical data to forecast outcomes, such as lead or opportunity scores, while generative AI produces new text such as emails and summaries. Writing call summaries is a generative task and win scores are predictive, so that statement reverses them. Prompt templates belong to generative AI and outcome training to predictive AI, and both kinds of AI apply across leads, opportunities, and other records.