10 free sample questions from a bank of 110, with the correct answers and explanations. No signup required — start practising right now.
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.
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.
When the stem asks how to get started breaking down a cycle, choose the answer that maps the current state first.
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.
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.
When the stem says competing priorities plus align teams, pick V2MOM, when it says document steps plus flow, pick process mapping.
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.
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.
When the question asks who secures alignment or drives adoption under resistance, choose executive sponsor and sales leadership over champions or builders.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
When UAT passes but sparks new asks, pass the test then story the change.
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.
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.
Remember persona accepts the story, team defines done, if an option swaps those perspectives or merges the artifacts, eliminate it.
B — A complex sharing model that must grow demands scalability first. Profiles, defaults and rules should stay manageable as headcount surges.
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.
When complexity meets growth, make scalability the deciding design test.
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.
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.
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.
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.
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.
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.
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.
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.