Sign in
Home/Salesforce/Certified Business Analyst/Free questions

Certified Business Analyst — Free Practice Questions

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

1Cloud Kicks (CK) wants its sales team to use Sales Cloud to decrease its lead conversion time. The business analyst (BA) will analyze and break down CK's typical sales cycle. How can process mapping help the BA get started on this project?
  • It can show the relationship between the steps and actions in the sales cycle to communicate and understand the current state, and to identify areas for improvement.
  • It can model changes in the current customer experience, analyze each change's potential for impact, and help visualize potential improvements in the sales cycle in advance of the solution design.
  • It can display complex ideas in a consistent format, highlight blockers and impediments to help stakeholders quickly assess issues in the sales cycle, and see the project timeline at a glance.
Answer: A

The short version

A — Process mapping reveals the as-is sales cycle and where time is lost. It creates a shared visual of steps, handoffs and decisions so the BA can baseline lead conversion time before proposing Sales Cloud changes.

Key concepts in this question

  • Process mapping: visual model of steps, actors, inputs and outcomes used to build shared understanding of how work actually flows.
  • Current state analysis: documented baseline of the as-is process that makes delays, rework and handoffs measurable before future-state design.
  • Lead conversion: staged progression from lead to opportunity that depends on entry criteria, activities and ownership at each step.
  • Continuous improvement: practice of finding friction in the current flow first, then targeting automation and guidance where it shortens cycle time.

Why A is correct

A is correct because the BA first needs to see relationships between steps and actions in the CK sales cycle, not yet design a solution. A current-state map communicates how sellers work today, surfaces wait time and rework, and points to concrete areas where Sales Cloud automation, guidance or data quality can reduce conversion time. That discovery-before-design sequence is core BA practice.

Why the others are wrong

  • B. Describes journey modeling or impact simulation of future experience changes, which comes after the as-is baseline is understood.
  • C. Describes status reporting or timeline visuals focused on blockers and schedule, not step-by-step flow relationships and improvement targeting.

Certified-Business-Analyst exam tip

When the stem asks how to get started breaking down a cycle, choose the answer that maps the current state first.

2Northern Trail Outfitters has a large Salesforce org with sales, marketing, and billing teams pushing for the development of a large number of items in the backlog. Which management process should the business analyst suggest to help the teams align on their competing priorities?
  • Vision, Values. Methods, Obstacles, and Measures (V2MOM)
  • Business Process Modeling Notation (BPMN)
  • Integrated DEFinition for Process Description Capture Method (IDEF3)
Answer: A

The short version

A — V2MOM aligns competing teams around shared vision. Northern Trail Outfitters has three strong teams pushing competing backlog items, so the business analyst needs an alignment and prioritization method first. V2MOM gives every team one shared page for vision, priorities, and success measures.

Key concepts in this question

  • V2MOM: Salesforce management process built on Vision, Values, Methods, Obstacles, and Measures that creates enterprise-wide alignment and transparent priorities.
  • Backlog prioritization: ranking many requested items by business value, urgency, capacity, and fit to vision so delivery follows strategy rather than loudest voice.
  • BPMN: Business Process Modeling Notation, a standard for documenting process flows and gateways.
  • IDEF3: Integrated DEFinition method for process description capture, used to record process behavior and object states for analysis.
  • Cross-functional alignment: getting sales, marketing, and billing to agree on what matters most and how each initiative supports company goals.

Why A is correct

V2MOM is the Salesforce-native way to resolve exactly this conflict, because it starts with shared vision and values before debating methods and measures. Each team socializes its V2MOM so leaders can sequence the backlog against one strategy. Measures then make priorities testable, so funding flows to work that advances agreed outcomes.

Why the others are wrong

  • B. BPMN documents how a single process executes step by step, but it does not reconcile competing goals across teams.
  • C. IDEF3 captures process descriptions for analysis and design, but it provides no mechanism for value-based prioritization or executive alignment.

Certified-Business-Analyst exam tip

When the stem says competing priorities plus align teams, pick V2MOM, when it says document steps plus flow, pick process mapping.

3Universal Containers (UC) uses a Salesforce org. UC is merging with a sister company that uses a different CRM. The incoming sales team is reluctant to change to a different process. The business analyst (BA) has been asked to help reach consensus and drive adoption. Which group is well positioned to help the BA secure alignment for the initiative?
  • Power users and top sales earners
  • Executive sponsors and sales leadership
  • System admin and project manager
Answer: B

The short version

B — Executive sponsors and sales leadership secure alignment. When an incoming sales team resists a new CRM and process after a merger, visible executive backing drives consensus and adoption.

Key concepts in this question

  • Executive sponsorship: authority and influence that sets expectations and enforces new ways of working.
  • Stakeholder alignment: getting merging teams to agree on vision, benefits and expectations.
  • Adoption: turning reluctant users into consistent users of the new process.

Why B is correct

Executive sponsors and sales leadership have the authority to communicate vision, set expectations and address resistance. Salesforce adoption guidance stresses securing executive support early and asking execs to visibly support use, which is decisive when a team prefers its old CRM.

Why the others are wrong

  • A. Power users and top earners can champion use, but they lack authority to secure org-level alignment across a merger.
  • C. System admin and project manager build and coordinate the solution; they do not carry the business authority to drive adoption.

Certified-Business-Analyst exam tip

When the question asks who secures alignment or drives adoption under resistance, choose executive sponsor and sales leadership over champions or builders.

4The business analyst (BA) at Universal Containers is writing user stories for its Salesforce Field Service implementation. What should the BA evaluate to understand the risk level of the user stories?
  • Team, budget, and timeline impact
  • Scope, resource, and documentation impact
  • Technical, operational, and regulatory impact
Answer: C

The short version

Banked answer A is not supported by official material, so the verdict flips to C. Risk for user stories is assessed through technical feasibility, operational impact, and regulatory or compliance exposure, not through team, budget, and timeline resourcing alone.

Key concepts in this question

User story risk versus estimation, INVEST quality checks, technical feasibility, operational handoffs and adoption impact, regulatory and compliance constraints, Field Service safety and data rules, and why business analysts separate risk from scheduling.

Why C is correct

C names the classic risk dimensions a business analyst must evaluate before committing a story to a sprint. Technical impact covers integration, automation, and platform limits in Field Service. Operational impact covers dispatch, mobile, and service handoffs. Regulatory impact covers privacy, safety, and audit needs. Official UPN material explicitly calls out support for regulatory and compliance considerations and context for metrics and management decisions, which is exactly a risk lens.

Why the others are wrong

A describes estimation and resourcing inputs such as team capacity, budget, and timeline, which help with planning and prioritization but do not define risk level. A risky story can still be small and cheap yet fail compliance or break operations. B mixes scope, resource, and documentation impact, which are discovery and governance concerns, not a standard risk model. Neither A nor B appears in official guidance as the risk evaluation for user stories, while technical, operational, and regulatory factors do.

Certified-Business-Analyst exam tip

When the stem says risk level, look for technical, operational, regulatory language. When the stem says size, effort, or timeline accuracy, look for small, estimable, and INVEST language. Do not pick budget or timeline options for risk questions, even if they sound like project management.

5New Interns at Universal Containers have been tasked with following a new process to import leads from a spreadsheet into Salesforce. A business analyst Is mapping the process to document the overall lead creation process. What should the process map look like?
  • A somewhat detailed process map that is easy to remember and self- explanatory
  • A very detailed process map that is unambiguous and version controlled
  • A simple process map that is high-level and covers key aspects
Answer: B

The short version

B — New operational processes need a detailed, unambiguous, version-controlled map. Repeated intern imports shape pipeline data, so the map must remove guesswork. Exact clicks, validations, and ownership make the process teachable and auditable.

Key concepts in this question

  • Process mapping fidelity: choosing the right level of detail for audience risk, where novices performing data loads need precision rather than high-level summaries.
  • Unambiguous documentation: every step, decision, input format, and error path spelled out so two interns produce the same correct result.
  • Version control: tracked revisions with dates and owners so updates to lead objects, validation rules, or import tools do not leave stale instructions in circulation.
  • Lead import risk: duplicates, wrong owners, bad field mapping, and failed compliance checks that follow from casual spreadsheet handling.
  • Self-explanatory versus controlled: memorable simplicity helps orientation, but operational repeatability demands controlled exactness.

Why B is correct

The settled key requires rigor because lead creation is a recurring data-quality control point, not a one-time orientation topic. Detailed mapping captures file standards, field mappings, deduplication checks, and exception handling interns would otherwise improvise. Version control keeps that detail trustworthy as configuration evolves.

Why the others are wrong

  • A. A somewhat detailed and memorable map aids quick learning but leaves room for interpretation that creates inconsistent lead data.
  • C. A simple high-level map covering only key aspects is suited to executive scoping, not to guiding novices through a system-sensitive import.

Certified-Business-Analyst exam tip

Match map detail to risk and repetition, novices plus data loads means very detailed and version-controlled, executives plus scoping means simple and high-level.

6Universal Containers is currently doing user acceptance testing for a global customer service project that leverages Service Cloud. A stakeholder is executing a test case for a specific user story. The stakeholder has provided this feedback: The functionality described in the test case is working as expected. The stakeholder wants to change the label of several fields described in the test case. The stakeholder wants to add two new fields that were excluded from the test case Which step should the business analyst take next?
  • Acknowledge the feedback, create a new test case that includes the field changes, and assign the test case back to the stakeholder for immediate testing.
  • Acknowledge the feedback, update the existing user story to include the field changes, and assign the user story back to the technical team for immediate development.
  • Acknowledge the feedback, create a new user story that includes the field changes, and ask the stakeholder to update the existing test case to show it was successfully tested.
Answer: C

The short version

C — Passing function plus new field asks means protect the test, story the delta. Confirm the tested story stands, then capture label and field changes as new work.

Key concepts in this question

  • User acceptance testing: business confirmation that described behavior works as expected.
  • Test case integrity: preserving evidence of what passed without rewriting history to include new asks.
  • Scope control: treating label tweaks plus two new fields as change to size and prioritize, not free edits.
  • User story evolution: new story carries added fields through estimation, build and testing discipline.

Why C is correct

C is correct per the settled key because the stakeholder confirms the test case works, so the existing test should be marked successful rather than reopened. The label changes and two excluded fields are new expectations that deserve a fresh user story for impact review and scheduling. That split keeps UAT truth clean while routing enhancements properly.

Why the others are wrong

  • A. Creating a new test case for immediate testing blurs pass evidence and pushes unestimated scope straight into test.
  • B. Updating the existing story for immediate development rewrites agreed scope mid-UAT and bypasses prioritization.

Certified-Business-Analyst exam tip

When UAT passes but sparks new asks, pass the test then story the change.

7A business analyst (BA) at Northern Trail Outfitters has been asked to prepare documentation Including acceptance criteria and definition of done for a Heroku project. Which way should the BA approach creation of this documentation?
  • Include the overall perspective for acceptance criteria and the persona's perspective for definition of done.
  • Include the persona's perspective for acceptance criteria and the overall perspective for definition of done.
  • Create one consolidated set of documentation as the two terms are synonymous and used interchangeably.
Answer: B

The short version

B — Acceptance criteria speak for the persona, definition of done speaks for the whole. A Heroku build still needs Salesforce discipline around who gets value and what shippable means. Keeping the two lenses separate prevents feature sign-off from being confused with release readiness.

Key concepts in this question

  • Acceptance criteria: persona-specific, testable conditions that prove a single user story delivers its intended outcome for that user.
  • Definition of done: overall checklist applied to every story, covering code quality, testing, security, documentation, and deployability.
  • Persona perspective: written from the viewpoint of the end user or stakeholder who will judge whether the behavior is acceptable.
  • Overall perspective: system-level standards owned by the delivery team that protect maintainability and operations on Heroku and connected clouds.
  • Heroku delivery context: apps, pipelines, and add-ons still require shared gates before promotion.

Why B is correct

The settled pattern assigns acceptance criteria to the persona because only that user can confirm fit for purpose through observable behavior and edge cases. Definition of done stays overall because architects, developers, testers, and operations all contribute criteria such as peer review, automated tests, performance, logging, and release notes. Separation lets owners accept value while the team enforces shippable quality.

Why the others are wrong

  • A. Reversing the lenses makes acceptance generic and definition of done narrow, so stories pass without proving persona value.
  • C. Treating the terms as synonymous collapses story-level validation into release-level quality, leaving gaps in both test design and governance.

Certified-Business-Analyst exam tip

Remember persona accepts the story, team defines done, if an option swaps those perspectives or merges the artifacts, eliminate it.

8Northern Trail Outfitters (NTO) plans to significantly grow its workforce and wants to increase the overall security of Its Sales Cloud instance. NTO has previously implemented a complex security solution with organization-wide defaults, criteria-based sharing rules, and dozens of user profiles. NTO has asked a business analyst (BA) for recommendations on how to proceed. Which aspect of a potential solution is most important for a BA to consider?
  • User adoption
  • Scalability
  • System downtime
Answer: B

The short version

B — A complex sharing model that must grow demands scalability first. Profiles, defaults and rules should stay manageable as headcount surges.

Key concepts in this question

  • Scalability: ability to add users and data without rework, slowdowns or admin sprawl.
  • Security model: organization-wide defaults, sharing rules and profiles that together control access.
  • Growth pressure: significantly larger workforce multiplying exceptions and maintenance load.
  • BA solution lens: weighing long-term maintainability alongside immediate security tightening.

Why B is correct

B is correct because NTO already runs intricate defaults, criteria sharing and dozens of profiles. Adding many users will magnify rule interactions, profile proliferation and troubleshooting cost unless the design scales cleanly. Prioritizing scalability steers toward simplified roles, hierarchical or group-based sharing, and automation that remains governable.

Why the others are wrong

  • A. User adoption matters for success, yet it does not address whether the permission architecture can grow without breaking.
  • C. System downtime is a delivery risk to manage, not the core design criterion for an expanding security model.

Certified-Business-Analyst exam tip

When complexity meets growth, make scalability the deciding design test.

9A business analyst (BA) is working with the support team at Cloud Kicks (CK) on a Service Cloud implementation. The BA has decided to create a process map to understand CK's current merchandise return process. What are the top three benefits of creating a process map?
  • Builds accountability, increases revenue, and decreases overall time spent on requirements
  • Identifies improvements, decreases project costs, and starts the change process
  • Engages stakeholders, identifies improvements, and starts the change process
Answer: C

The short version

Banked answer C is kept. The top benefits of a process map are shared understanding with stakeholders, identification of flaws and improvements, and a catalyst for change, which matches official Trailhead guidance on why business analysts map processes.

Key concepts in this question

Process mapping purpose, stakeholder communication, as-is visualization, flaw and bottleneck identification, improvement and change enablement, Service Cloud return process discovery, and difference between primary benefits and secondary effects like cost reduction.

Why C is correct

C captures the two primary uses stated in official material plus their natural outcome. Engages stakeholders reflects making understanding and communicating much easier among teams, stakeholders, or customers. Identifies improvements reflects helping identify flaws and where improvements should be made. Starts the change process reflects using the map to foster quality management and focus strategic planning. Together they explain why a BA maps the merchandise return process before solutioning.

Why the others are wrong

A is wrong because builds accountability and increases revenue overstate what a map alone delivers, and decreases overall time spent on requirements is not listed as a top benefit. B is partly right about identifies improvements and starts the change process, but decreases project costs is described as a secondary also-helps effect alongside improved team performance and satisfaction, not one of the two most important uses. Only C pairs both primary uses together, so B is incomplete as a top-three list.

Certified-Business-Analyst exam tip

For benefits questions, choose stakeholder understanding plus flaw identification first. Treat reduce costs, improve performance, and increase satisfaction as secondary helpers. If an option omits stakeholder engagement or communication, it is usually missing the most tested benefit.

10As part of the digital transformation at Cloud Kicks, company leaders have decided to adopt Service Cloud as its CRM platform for customer service and support. Executive directors are supportive of the initiative, but end users are unconvinced and prefer to remain on the current platform. What should the business analyst do to gam the end users' cooperation?
  • Identity key stakeholders and develop relationships with them as a trusted advisor; involve stakeholders and end users in the design of the new solution; and act as a liaison between business and technical teams.
  • Use an assertive influencing style; demonstrate authority and expertise; outline the project objectives; and make sure end users know that the decision has been made and the time to make changes has passed.
  • Respond to end users with empathy and accommodate their needs; translate the end users' needs into technical requirements; and deliver the project to the developers to implement the solution.
Answer: A

The short version

A — Trusted-advisor engagement plus co-design turns unconvinced users into owners. Involving end users in Service Cloud design while bridging business and technical teams builds cooperation that mandates cannot.

Key concepts in this question

  • Stakeholder engagement: building relationships and shared ownership so affected users support rather than tolerate the new platform.
  • Trusted advisor: BA posture of listening, transparency and follow-through that earns permission to guide difficult change.
  • Co-design: involving end users in shaping workflows and usability so the solution reflects real service work.
  • Business-technical liaison: translating needs both ways so expectations stay realistic and feedback actually lands in the build.

Why A is correct

A is correct because executive support alone does not resolve end-user doubt rooted in daily effort and habit. Identifying key stakeholders, investing in relationships, involving agents in design choices, and actively liaising between business and technical teams gives users voice and visibility. That participation increases fit, reduces fear, and creates advocates who will help peers adopt Service Cloud.

Why the others are wrong

  • B. Assertive, authority-led pressure and declaring debate closed deepens resistance and hides usability issues until after go-live.
  • C. Empathy without genuine co-design plus handing off to developers skips joint problem solving and leaves ownership with IT rather than agents.

Certified-Business-Analyst exam tip

When users prefer the old platform, choose involve plus liaise over assert or accommodate alone.

Want the full bank of 110 questions for Certified Business Analyst? See all practice exams.