SCBA

Free SCBA practice questions

10 questions from our SCBA 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 SCBA practice exams

Question 1 of 10, Customer Discovery

While reviewing an existing org, a business analyst finds that several custom fields on the Opportunity object appear to be unused. What is the BEST next step before recommending that they be removed?

  1. ACheck field usage data and dependencies, then confirm with the field owners whether any process still needs them Correct answer
  2. BAdd the fields to the project risk log and leave them in place until the next major Salesforce release is installed
  3. CDelete the fields in a sandbox and wait to see whether any user reports a missing value during the next sprint
  4. DHide the fields from all page layouts in production immediately so that users stop relying on them going forward

Answer and explanation: Evidence of usage plus a dependency check (reports, automation, integrations) and confirmation from owners prevents removing data that a hidden process still needs. Deleting in a sandbox and waiting for complaints relies on luck, because sandbox users may not exercise every process. Hiding fields in production is a change without analysis, and parking the issue in a risk log until a release has no bearing on whether the fields are needed.

Question 2 of 10, Customer Discovery

A business analyst is starting discovery for a regional insurance broker that wants to move its policy renewal tracking into Salesforce. Before running any requirements workshops, what should the analyst do FIRST to understand the context of the request?

  1. AReview the company's strategic goals, org chart and the business problem the renewal project is meant to solve Correct answer
  2. BDraft user stories for the renewal team from the existing spreadsheet columns so the backlog can be estimated early
  3. CBuild a prototype renewal object in a Developer sandbox so that stakeholders have something concrete to react to
  4. DSend a survey to all renewal agents asking them which Salesforce features they would like to see in the new system

Answer and explanation: Discovery starts by understanding the organization: its strategy, structure and the problem behind the request, so later elicitation is anchored to business value. Building a prototype first jumps to a solution before the problem is understood. Asking agents which features they want invites solution-first answers rather than needs, and drafting stories from spreadsheet columns assumes the current data structure is the requirement.

Question 3 of 10, Collaboration with Stakeholders

A business analyst plots project stakeholders on a power/interest grid. How should the analyst engage stakeholders who have high power but low interest in the project?

  1. AKeep them satisfied with concise updates and involve them in key decisions Correct answer
  2. BManage them closely with weekly detailed working sessions on every requirement
  3. CMonitor them with minimal effort because they are unlikely to affect the project
  4. DKeep them informed through the same detailed newsletters sent to all end users

Answer and explanation: High-power, low-interest stakeholders can affect the project but do not want detail, so they should be kept satisfied with targeted updates and brought in for key decisions. Detailed weekly sessions suit high-power, high-interest stakeholders, minimal monitoring suits low-power, low-interest ones, and detailed newsletters suit high-interest, low-power groups.

Question 4 of 10, Collaboration with Stakeholders

A systems integrator delivers configuration, while the client's business analyst owns requirements. The integrator's team keeps interpreting stories differently from the client's intent. Which change will MOST reduce misinterpretation?

  1. AAsk the client's analyst to write longer stories that include detailed configuration instructions for each field and automation
  2. BMove all communication between the two teams to a single weekly status email sent by the integrator's project manager
  3. CRun joint refinement sessions where both teams review stories and acceptance criteria with the client's experts Correct answer
  4. DRequire the integrator to submit a written change request for every question about a user story, with approval from the steering committee

Answer and explanation: Joint refinement creates a shared understanding of intent and acceptance criteria before work starts, which addresses the root cause. Formal change requests for every question slow delivery, prescriptive configuration instructions turn stories into designs and remove the integrator's expertise, and a weekly email reduces communication when more is needed.

Question 5 of 10, Business Process Mapping

A company has four regional order processes that differ slightly. Leadership wants one Salesforce process. After mapping all four, what is the BEST next step for the business analyst?

  1. AAverage the steps across all four maps so that the future process contains a balanced mix of each region's current activities
  2. BPick the region with the most mature process and require the other three regions to adopt its process exactly as it stands today
  3. CBuild four separate processes in Salesforce using record types so each region can keep its current process with no changes
  4. DSeparate genuine regional requirements, such as legal rules, from habits, then design one process with justified variations Correct answer

Answer and explanation: Separating true requirements from habit lets the analyst design a standard process with only justified variations, which meets leadership's goal. Imposing one region's process ignores legitimate differences, four processes defeat standardization, and averaging steps produces a process nobody designed for purpose.

Question 6 of 10, Requirements

A company needs to keep five years of field-level change history on its Contract object for audit purposes, and auditors need to query it on demand. During requirements analysis, what should the business analyst do?

  1. ARemove the audit need from scope, because history requirements are the responsibility of the auditors and not of the Salesforce project team
  2. BAsk the users to copy every contract change into a notes field manually so that the history is always available for auditors to read
  3. CAssume standard field history tracking meets the need, because it records every change to every field on every object for an unlimited period of time
  4. DState the retention and audit access needs as non-functional requirements and confirm with an architect how to meet them Correct answer

Answer and explanation: Retention period and auditor access are critical non-functional requirements that may exceed what standard field history tracking provides, so they should be stated explicitly and confirmed with an architect (for example, considering Field Audit Trail). Standard tracking is limited in fields and retention, the project must address audit needs, and manual notes are unreliable.

Question 7 of 10, Requirements

A global sales team requires opportunity amounts in local currencies and consolidated reports in USD using dated exchange rates. During requirements validation, which point should the business analyst confirm with stakeholders and the admin?

  1. AThat multi-currency and advanced currency management are acceptable, given their effect on reporting and on enabling them in the org Correct answer
  2. BThat a single corporate currency is enough, because consolidated USD reports remove the need for any local currency values at all
  3. CThat a custom exchange rate object will be built, because Salesforce cannot store more than one currency in a single organization
  4. DThat reps will convert every opportunity amount to USD by hand before saving it, so reports can be consolidated without any org changes at all

Answer and explanation: Multi-currency with dated exchange rates is supported but has implications (for example, it cannot be turned off once enabled and affects reports and roll-ups), so stakeholders and the admin should confirm the approach. Manual conversion is error-prone, a single currency ignores the local currency requirement, and Salesforce does support multiple currencies.

Question 8 of 10, User Stories

A team's stories regularly fail at sprint review because stakeholders expected different behavior. Acceptance criteria were written by the business analyst alone. Which change is MOST likely to fix this?

  1. AMake the acceptance criteria much longer and more detailed, still written by the business analyst alone, so nothing can be misunderstood
  2. BAsk developers to add any criteria they think are missing during the sprint, without informing the stakeholders
  3. CSkip the sprint review and let stakeholders test stories on their own after deployment so they see the final behavior
  4. DWrite and review acceptance criteria together with the product owner, a stakeholder, a developer and a tester before planning Correct answer

Answer and explanation: Collaborative criteria, sometimes called a three amigos session with business, development and testing perspectives, build shared understanding before work starts. Longer solo-written criteria keep the same blind spots, skipping reviews delays feedback, and silent developer additions bypass stakeholders.

Question 9 of 10, User Stories

A stakeholder writes: 'As a user, I want the system to work better.' What should the business analyst do?

  1. AEstimate the story as large and add it to the next sprint as it is written
  2. BAccept the story and let the developers decide what better means in practice
  3. CReject the story and ask the stakeholder to stop submitting backlog items
  4. DWork with the stakeholder to identify the specific role, need and benefit Correct answer

Answer and explanation: The story lacks a specific role, a concrete capability and a benefit, so the analyst should help shape it into something valuable and testable. Letting developers interpret it invites misalignment, rejecting the stakeholder harms collaboration, and estimating a vague story is meaningless.

Question 10 of 10, User Acceptance

How does system integration testing differ from user acceptance testing?

  1. ASIT checks that systems work together; UAT checks the solution meets business needs Correct answer
  2. BSIT happens after go-live; UAT happens before any development starts
  3. CSIT tests only reports; UAT tests only page layouts and record types
  4. DSIT is done by end users in production; UAT is done only by the development team

Answer and explanation: System integration testing verifies interactions between systems and components, while UAT confirms that the solution supports business processes. SIT is usually done by technical testers, both happen before go-live, and neither is limited to reports or layouts.