Praxis Academy
Home › Business Analyst › Customer Discovery

Business Analyst practice questions: Customer Discovery

Customer Discovery is 17% of the Salesforce Certified Business Analyst exam. It covers current state, shadowing, workshops and org review. Try these 10 free questions, then open each answer to see why every option is right or wrong.

01

An outdoor gear retailer plans to adopt Salesforce in place of three unconnected spreadsheets that its merchandising buyers rely on. Before proposing any solution, the business analyst reviews the company's existing Salesforce org. What is the MAIN reason for doing this review ahead of any recommendation?

  1. To produce a project plan with milestones and cost estimates for stakeholders.
  2. To uncover the org's current constraints and opportunities, which determine which solution options are realistic.
  3. To catalog every open support ticket and user complaint about the spreadsheets in use today.
  4. To draw the future-state process map for the buyers' new way of working.
Show answer

Answer: B

A. To produce a project plan with milestones and cost estimates for stakeholders.Incorrect. A project plan is project management work that follows discovery; it is not why the environment is reviewed first.
B. To uncover the org's current constraints and opportunities, which determine which solution options are realistic. ✓Correct. Org-specific limits, automation, licenses and technical debt, plus untapped capabilities, decide which solutions are feasible. Skipping this risks proposing designs that clash with the org.
C. To catalog every open support ticket and user complaint about the spreadsheets in use today.Incorrect. Logging tickets describes the business problem's current state, not the Salesforce environment the question asks about.
D. To draw the future-state process map for the buyers' new way of working.Incorrect. Future-state mapping comes after current-state analysis; it is a later step, not the reason for the review.

Why: Reviewing the existing Salesforce environment first exposes constraints (org-wide defaults, governor limits, license types, current automation) and opportunities (underused features, AppExchange options). Recommendations made without that context tend to break down during implementation.

02

A business analyst at a footwear company must judge whether the current Salesforce org can support the new features planned for an upcoming release. Which activities belong in a Salesforce environment readiness assessment? (Choose 2)

  1. Checking API usage, storage consumption and record limits to spot possible capacity constraints.
  2. Designing the data model for every new custom object before the assessment finishes.
  3. Spotting possible conflicts between current automation (workflow rules, Process Builder, Flows) and the planned features to avoid unintended side effects.
  4. Writing every test case for the new features before the environment assessment finishes.
Show answer

Answer: A, C

A. Checking API usage, storage consumption and record limits to spot possible capacity constraints. ✓Correct. If the org is close to API limits, new integrations can cause performance problems; near-full storage can block data imports. Knowing this avoids failures.
B. Designing the data model for every new custom object before the assessment finishes.Incorrect. Data model design is future-state work that follows the assessment; doing it first can produce a design that conflicts with the current configuration.
C. Spotting possible conflicts between current automation (workflow rules, Process Builder, Flows) and the planned features to avoid unintended side effects. ✓Correct. Existing automation may fire twice, overwrite updates or slow performance once new features arrive. Finding these conflicts early prevents post-deployment problems.
D. Writing every test case for the new features before the environment assessment finishes.Incorrect. Test cases come later, after requirements and sprint planning; they are not part of a readiness assessment.

Why: A readiness assessment covers capacity (API limits, storage, record limits) and automation conflicts (existing workflow rules, Process Builder, Flows) that could interact badly with new features. Both shape which features are feasible and what must be fixed first.

03

A nonprofit is moving to Salesforce Nonprofit Success Pack (NPSP). In interviews, program staff explain that donation management today relies on manual spreadsheets, inconsistent data entry, and painful reporting for grant compliance. The business analyst wants to put a number on the impact of these problems. What is the BEST way to do that?

  1. Have program staff estimate the hours per week spent on manual spreadsheet work and convert that into an annual cost using their salary.
  2. Treat the qualitative descriptions of the pain points as enough evidence for the business case without quantifying them.
  3. Compare the pain points to generic industry benchmarks without collecting data specific to the organization.
  4. Ask the CFO to supply the financial impact estimate because they can see cost data.
Show answer

Answer: A

A. Have program staff estimate the hours per week spent on manual spreadsheet work and convert that into an annual cost using their salary. ✓Correct. Time spent on manual work, converted to annual cost, makes the pain financially visible to decision-makers and is a sound quantification method.
B. Treat the qualitative descriptions of the pain points as enough evidence for the business case without quantifying them.Incorrect. Executives usually need numbers. Quantifying time saved, cost reduced or errors avoided makes the case for Salesforce much stronger.
C. Compare the pain points to generic industry benchmarks without collecting data specific to the organization.Incorrect. Generic benchmarks are less credible than 'your organization loses X hours a week.' The BA should collect organization-specific data.
D. Ask the CFO to supply the financial impact estimate because they can see cost data.Incorrect. The CFO holds financial data, but frontline staff know the time their manual work takes. Collect time-on-task data from them and involve finance to attach costs if needed.

Why: Turning frustrations into financial terms strengthens a business case. Estimating weekly time on manual tasks and converting it to annual cost (hours/week x 52 x salary) makes the ROI of automation concrete. Organization-specific numbers beat industry benchmarks, and the people doing the work give the most accurate time estimates.

04

Three months after a large Service Cloud go-live at a logistics firm, the operations director says agents are still working in the legacy system instead of Salesforce. The BA is asked to look into the adoption problem. What should the BA do FIRST?

  1. Book mandatory training for all agents and add Salesforce usage to their performance metrics.
  2. Run observation sessions and focus groups with agents to learn which specific barriers make them prefer the legacy system.
  3. Review the org's error logs and performance metrics to find technical defects.
  4. Ask the operations director to switch off the legacy system so agents must use Salesforce.
Show answer

Answer: B

A. Book mandatory training for all agents and add Salesforce usage to their performance metrics.Incorrect. Training before knowing the root cause may miss the real barriers; workflow, usability or data quality problems will not be solved by training alone.
B. Run observation sessions and focus groups with agents to learn which specific barriers make them prefer the legacy system. ✓Correct. Observing agents in their real environment and hearing them in focus groups reveals the specific barriers (usability gaps, missing data, slowness, trust) so the BA can propose targeted improvements.
C. Review the org's error logs and performance metrics to find technical defects.Incorrect. Technical issues may contribute, but log analysis is troubleshooting, not BA-led discovery. The BA first understands user behavior and routes technical issues to the right team.
D. Ask the operations director to switch off the legacy system so agents must use Salesforce.Incorrect. Shutting down the legacy system without addressing the cause of resistance risks major disruption and even more pushback.

Why: Poor adoption is a discovery and change management problem. The first move is to find the root cause by engaging users directly through observation and focus groups, rather than mandating training, forcing changes or jumping into technical analysis - understand the current state before recommending fixes.

05

To understand how a customer service operation really works today, a business analyst wants to go beyond stakeholder interviews and grasp the emotional experience of both agents and customers. Which approach BEST supports empathic discovery here?

  1. Send a 10-question satisfaction survey to agents and customers and analyze the scores.
  2. Sit alongside front-line agents during live customer interactions, observing their emotional reactions, workflow frustrations and coping behaviors as they happen.
  3. Study the service team's performance dashboards and KPI reports to see where metrics miss their targets.
  4. Interview the customer service director for their view on team performance and customer satisfaction.
Show answer

Answer: B

A. Send a 10-question satisfaction survey to agents and customers and analyze the scores.Incorrect. Surveys yield numbers but miss the emotional context and the 'why behind the numbers.' They supplement empathic research; they are not its main tool.
B. Sit alongside front-line agents during live customer interactions, observing their emotional reactions, workflow frustrations and coping behaviors as they happen. ✓Correct. Shadowing agents during live interactions captures authentic frustrations, emotions and coping behaviors that formal interviews would never reveal.
C. Study the service team's performance dashboards and KPI reports to see where metrics miss their targets.Incorrect. KPI dashboards show where performance lags, not why, and miss the emotional and behavioral context; they cannot replace direct observation.
D. Interview the customer service director for their view on team performance and customer satisfaction.Incorrect. A manager's view is top-down and filtered. Empathic discovery requires engaging directly with the people living the experience.

Why: Empathic research means observing stakeholders in their real work setting during real tasks. It uncovers emotional context, informal workarounds and unspoken frustrations that surveys, dashboards and manager interviews cannot, so the BA can co-create solutions for actual rather than assumed needs.

06

At the first stakeholder meeting of a new Sales Cloud project, the operations director states: 'Our reps lose 2 hours a day manually updating opportunity stages in the legacy CRM. Salesforce has to solve this.' How should the business analyst interpret and respond?

  1. Take the statement as a requirement and write: 'The system must reduce manual opportunity stage updates to eliminate 2 hours of daily effort per rep.'
  2. Dig deeper into the root cause: why do reps spend 2 hours updating opportunities? Is it too many manual fields, missing automation, complicated stage criteria, or data quality problems?
  3. Immediately recommend the Salesforce Opportunity Kanban view because it cuts manual stage updates.
  4. Escalate to the project sponsor because the statement implies the legacy CRM was set up badly.
Show answer

Answer: B

A. Take the statement as a requirement and write: 'The system must reduce manual opportunity stage updates to eliminate 2 hours of daily effort per rep.'Incorrect. The director described a symptom and implied a solution; recording it directly as a requirement skips problem analysis.
B. Dig deeper into the root cause: why do reps spend 2 hours updating opportunities? Is it too many manual fields, missing automation, complicated stage criteria, or data quality problems? ✓Correct. The 2 hours are a symptom. Unclear stage criteria, too many required fields or lack of automation each lead to a different Salesforce answer - automated stage advancement, fewer required fields, Kanban view, or something else.
C. Immediately recommend the Salesforce Opportunity Kanban view because it cuts manual stage updates.Incorrect. Proposing a feature before knowing the root cause may miss the real issue; Kanban may or may not fit depending on why the time is spent.
D. Escalate to the project sponsor because the statement implies the legacy CRM was set up badly.Incorrect. The legacy configuration is background, not grounds for escalation. The BA's job is to understand the problem and turn it into future-state requirements.

Why: When stakeholders describe a symptom ('we spend 2 hours on X') or a presumed solution ('Salesforce will fix it'), the BA probes for the root cause. Knowing why the time is spent determines the right fix and keeps the team from building something that treats the symptom only.

07

Midway through a large Service Cloud implementation, the company announces a merger that will bring in a second Salesforce org from the acquired business. How should the business analyst adjust for the rest of the project?

  1. Carry on as planned because the merger does not affect the current implementation scope.
  2. Stop all development until the merger closes and the org strategy is settled.
  3. Expand the stakeholder map to include the acquired company's stakeholders, re-evaluate requirements that the org strategy decision might affect, and escalate the new constraints to the sponsor for a scope and timeline decision.
  4. Have developers build a solution that works with both org configurations at once without stakeholder input.
Show answer

Answer: C

A. Carry on as planned because the merger does not affect the current implementation scope.Incorrect. A second org fundamentally changes the technical landscape and stakeholder group; ignoring it risks a solution that does not fit the merged future state.
B. Stop all development until the merger closes and the org strategy is settled.Incorrect. An indefinite pause is impractical when mergers can take 6-18 months. Work in unaffected areas can continue; the BA should identify what is and is not affected.
C. Expand the stakeholder map to include the acquired company's stakeholders, re-evaluate requirements that the org strategy decision might affect, and escalate the new constraints to the sponsor for a scope and timeline decision. ✓Correct. The BA widens the stakeholder map, checks whether existing requirements still hold, and escalates the two-org constraint to the sponsor. The org strategy decision belongs to executives.
D. Have developers build a solution that works with both org configurations at once without stakeholder input.Incorrect. Building for both orgs without a business decision on org strategy wastes effort and may satisfy neither configuration; the decision must come first.

Why: Major mid-project changes (mergers, acquisitions, leadership changes, strategic pivots) require the BA to update stakeholder maps, reassess affected requirements, and escalate new constraints for executive decisions. The BA surfaces implications; they do not unilaterally continue, pause indefinitely or decide org architecture.

08

A company is beginning its third Salesforce implementation in five years. The new business analyst finds that a lessons-learned document from the second project was never reviewed; that project suffered major UAT failures caused by weak requirements documentation. What should the BA do BEFORE discovery starts on the current project?

  1. Disregard the lessons-learned document because it covers a different project, team and set of requirements.
  2. Study the lessons-learned document, pinpoint the root causes of the earlier UAT failures, and build concrete process improvements into this project's requirements and UAT approach so they do not happen again.
  3. Ask the earlier project's BA to join the team because they have relevant experience.
  4. Send the lessons-learned document to the sponsor and require them to read it before approving the current project.
Show answer

Answer: B

A. Disregard the lessons-learned document because it covers a different project, team and set of requirements.Incorrect. Lessons-learned documents hold proven insights; ignoring them invites a repeat of the same UAT failures.
B. Study the lessons-learned document, pinpoint the root causes of the earlier UAT failures, and build concrete process improvements into this project's requirements and UAT approach so they do not happen again. ✓Correct. Identifying why UAT failed lets the BA add preventive measures - stricter AC standards, earlier UAT planning, review gates - that directly reduce the risk of recurrence.
C. Ask the earlier project's BA to join the team because they have relevant experience.Incorrect. Bringing in the earlier BA may help if possible, but the current BA can and should review the document now rather than wait on staffing.
D. Send the lessons-learned document to the sponsor and require them to read it before approving the current project.Incorrect. Mandating the sponsor's reading is not the BA's role; the BA should apply the lessons to their own approach.

Why: Reviewing earlier lessons learned before a new project is professional BA practice. Past UAT failures from weak requirements documentation are a direct, avoidable risk. The BA should read the lessons, identify root causes, and add specific safeguards (e.g., AC review gates, earlier UAT preparation, requirements quality checklists).

09

A Salesforce project is being delivered with Agile, and a new stakeholder asks the business analyst to compare Agile and Waterfall. In which situation would Waterfall be MORE suitable than Agile for a Salesforce project?

  1. When several teams in different time zones must coordinate releases.
  2. When requirements are clearly defined, stable and unlikely to change during the project.
  3. When the customer wants working software delivered incrementally at the end of every two-week sprint.
  4. When the team needs freedom to reprioritize the backlog after each iteration based on stakeholder feedback.
Show answer

Answer: B

A. When several teams in different time zones must coordinate releases.Incorrect. Distributed, multi-team projects can run under either model; scaled Agile frameworks often handle them well, so this does not favor Waterfall.
B. When requirements are clearly defined, stable and unlikely to change during the project. ✓Correct. With requirements known upfront and unlikely to change, a sequential phase-gate model (discover, design, build, test, deploy) works well without Agile's feedback loops.
C. When the customer wants working software delivered incrementally at the end of every two-week sprint.Incorrect. Incremental delivery each sprint is the hallmark of Agile (Scrum); Waterfall delivers the full solution at the end.
D. When the team needs freedom to reprioritize the backlog after each iteration based on stakeholder feedback.Incorrect. Reprioritizing the backlog after each iteration is a core Agile practice that Waterfall does not support.

Why: Waterfall fits when requirements are stable and well understood from the start with little expected change. Agile fits when requirements evolve, iterative customer feedback is needed, and early working functionality matters. The BA recommends the model that matches the project's characteristics.

10

The business analyst is asked which deliverables the BA owns in each phase of a Salesforce implementation lifecycle. Which option maps BA outputs to phases CORRECTLY?

  1. Discovery: Apex code; Requirements: process diagrams; Build: user stories; UAT: project plan.
  2. Discovery: current-state process maps and stakeholder analysis; Requirements: documented, prioritized requirements; Build: sprint support and story clarification; UAT: test case validation and a go/no-go recommendation.
  3. Discovery: product roadmap; Requirements: sprint plan; Build: architecture diagram; UAT: training materials.
  4. Discovery: wireframes; Requirements: database schema; Build: status reports; UAT: deployment scripts.
Show answer

Answer: B

A. Discovery: Apex code; Requirements: process diagrams; Build: user stories; UAT: project plan.Incorrect. Apex code is a developer deliverable, and the remaining pairings are also wrong.
B. Discovery: current-state process maps and stakeholder analysis; Requirements: documented, prioritized requirements; Build: sprint support and story clarification; UAT: test case validation and a go/no-go recommendation. ✓Correct. Each phase is paired with a genuine BA output: current-state documentation and stakeholder maps, prioritized traceable requirements, sprint clarification and grooming, and UAT validation with go/no-go support.
C. Discovery: product roadmap; Requirements: sprint plan; Build: architecture diagram; UAT: training materials.Incorrect. Roadmaps belong to product management, sprint plans to the Scrum Master or PM, architecture diagrams to architects, and training materials to change management.
D. Discovery: wireframes; Requirements: database schema; Build: status reports; UAT: deployment scripts.Incorrect. Wireframes are mainly UX output, schemas come from architects, status reports from the PM, and deployment scripts from developers or admins.

Why: Typical BA outputs by phase: Discovery produces stakeholder analysis and current-state process maps (for example SIPOC or swimlane diagrams); Requirements produces categorized, traceable, prioritized requirements; Build involves sprint support such as story clarification, backlog grooming, and refining acceptance criteria; UAT covers test case validation, defect classification, and a go/no-go recommendation.

Find out if you're ready to pass

Take the free Business Analyst diagnostic: 20 questions, no account needed. Then unlock all 180 questions, full practice exams and the study guide.

Start the free diagnosticSee plans

Other sections of this exam