Question bank
Salesforce Certified Business Analyst
43 Salesforce Certified Business Analyst questions with the correct answer and a written explanation, organised across 6 exam domains.
- 43 questions
- 6 domains
- Foundation level
certilumQuestion index
Jump straight to any question. Answers and explanations are inline.
Business Process Mapping
5 questions in this domain
- Question 1Single Choice
In the MoSCoW method, which category represents requirements that are critical for a project's success?
- AMust haveCorrect answer
- BShould have
- CCould have
- DWon't have
Why this is the answer
Must-have requirements are critical to a project's success; omitting them means the project cannot launch.
- Question 2Multiple Select
According to the playbook, which of the following options are recognized prioritization traps that should be avoided?
- APrioritizing by Technical EaseCorrect answer
- BIgnoring DependenciesCorrect answer
- CStatic PrioritizationCorrect answer
- DWeighted Scoring Model
Why this is the answer
Technical ease, ignored dependencies, and static priorities are traps; weighted scoring is a structured prioritization technique.
- Question 3Interactive
Review the requirement in the code block. Which MoSCoW category does it match?
- AMust haveCorrect answer
- BShould have
- CCould have
- DWon't have
Why this is the answer
The requirement is mandatory for release, so it is a Must have item in the MoSCoW method.
- Question 4Single Choice
According to the Value vs. Effort Matrix, what is a 'Quick Win'?
- AHigh value, low effortCorrect answer
- BHigh value, high effort
- CLow value, low effort
- DLow value, high effort
Why this is the answer
A Quick Win appears in the quadrant for high business value and low implementation effort.
- Question 5Multiple Select
According to the playbook, which of the following are recognized prioritization traps that should be avoided?
- APrioritizing by Technical EaseCorrect answer
- BIgnoring DependenciesCorrect answer
- CStatic PrioritizationCorrect answer
- DWeighted Scoring Model
Why this is the answer
Technical ease, ignored dependencies, and static priorities are traps; weighted scoring is a structured prioritization technique.
Collaboration with Stakeholders
10 questions in this domain
- Question 6Single Choice
In the MoSCoW method, which category is used for requirements that are critical for project success?
- AMust haveCorrect answer
- BShould have
- CCould have
- DWon't have
Why this is the answer
MoSCoW defines 'Must have' as requirements that are critical for success. The other categories represent less critical or out-of-scope items.
- Question 7Multiple Select
Which of the following statements accurately describe the Weighted Scoring Model? Select all that apply.
- AStakeholders assign numerical weights to criteriaCorrect answer
- BIt reduces subjective bias with final priority scoresCorrect answer
- CIt plots value and effort in a quadrant
- DIt quantifies lost opportunity from delay
Why this is the answer
Weighted scoring uses numerical weights to reduce subjective bias. Quadrant plotting belongs to Value vs. Effort, and delay costing belongs to Cost of Delay.
- Question 8Interactive
Review the dependency mapping in the code. Which requirement should be high priority despite low standalone value?
- AR1Correct answer
- BR2
- CR3
- DR4
Why this is the answer
R1 is a prerequisite for R2, R3, and R4, making it a foundational blocker. Dependency mapping says a low-value requirement can be high priority when it enables multiple high-value features.
- Question 9Single Choice
According to the Value vs. Effort Matrix, which quadrant represents requirements known as 'Quick Wins'?
- AHigh business value and low technical effortCorrect answer
- BHigh business value and high technical effort
- CLow business value and low technical effort
- DLow business value and high technical effort
Why this is the answer
The playbook defines 'Quick Wins' as requirements with high business value and low effort in the Value vs. Effort Matrix.
- Question 10Multiple Select
Which of the following are explicitly identified as prioritization traps in the playbook? Select all that apply.
- APrioritizing by technical easeCorrect answer
- BIgnoring dependenciesCorrect answer
- CStatic prioritizationCorrect answer
- DUsing weighted scoring
Why this is the answer
The playbook lists prioritizing by technical ease, ignoring dependencies, and static prioritization as traps. Weighted scoring is a recommended technique, not a trap.
- Question 11Interactive
Review the Cost of Delay estimates in the code. Based on the Cost of Delay concept, which feature should be prioritized first?
- AFeature A
- BFeature B
- CFeature CCorrect answer
- DFeature D
Why this is the answer
Cost of Delay quantifies lost opportunity or increased risk. Feature C has the highest estimated cost of delay, so postponing it has the greatest negative impact.
- Question 12Single Choice
In economic terms, what does the Cost of Delay concept help a Business Analyst quantify?
- ALost opportunity or increased risk from delayCorrect answer
- BThe technical effort needed to build a feature
- CThe number of stakeholders needed for approval
- DThe dependency between two requirements
Why this is the answer
Cost of Delay is an economic concept that quantifies the lost opportunity or increased risk associated with postponing a specific feature.
- Question 13Multiple Select
According to the playbook, which criteria could stakeholders use in a Weighted Scoring Model? Select all that apply.
- ARevenue impactCorrect answer
- BRisk reductionCorrect answer
- CUser experienceCorrect answer
- DTechnical ease
Why this is the answer
The playbook names revenue impact, risk reduction, and user experience as examples of weighted scoring criteria. Technical ease is a prioritization trap, not a scoring criterion.
- Question 14Interactive
The code block shows a planned sprint sequence. Which prioritization trap is represented by ordering based on effort rather than business value?
- APrioritizing by technical easeCorrect answer
- BIgnoring dependencies
- CStatic prioritization
- DCost of Delay
Why this is the answer
The code places low-effort tasks before high-value work, matching the trap of prioritizing by technical ease to show progress instead of maximizing business value.
- Question 15Single Choice
In the context of requirements prioritization, what does dependency mapping identify about relationships between requirements?
- AIdentifying technical or logical relationships between requirementsCorrect answer
- BAssigning numerical scores to stakeholder criteria
- CCategorizing requirements into four MoSCoW groups
- DCalculating the financial cost of postponing a feature
Why this is the answer
Dependency mapping identifies technical or logical relationships between requirements, including cases where a low-value item is a prerequisite for high-value features.
Customer Discovery
7 questions in this domain
- Question 16Single Choice
In the MoSCoW method, what does the 'Must have' category represent in terms of project success and release scope?
- AMust haveCorrect answer
- BShould have
- CCould have
- DWon't have
Why this is the answer
The Must have category includes requirements that are critical for project success. MoSCoW uses these non-negotiable items to define the minimum release scope and manage scope creep.
- Question 17Multiple Select
Which of the following are recognized prioritization traps in requirements management that a business analyst should avoid? Select all that apply.
- APrioritizing by technical easeCorrect answer
- BIgnoring dependenciesCorrect answer
- CStatic prioritizationCorrect answer
- DUsing weighted scoring
Why this is the answer
The materials list prioritizing by technical ease, ignoring dependencies, and static prioritization as traps. Weighted scoring is a valid quantitative prioritization technique and is not a trap.
- Question 18Interactive
Examine the code block containing value and effort scores, then identify which requirement should be classified as a Quick Win.
- AReq-ACorrect answer
- BReq-B
- CReq-C
- DReq-D
Why this is the answer
A Quick Win has high business value and low technical effort. Req-A scores value 8 and effort 2, while Req-B is high effort and Req-C/Req-D are low value.
- Question 19Single Choice
How does the Weighted Scoring Model help business analysts reduce subjective bias during requirements prioritization?
- AAssigns numerical weights and calculates scoresCorrect answer
- BPlots requirements by value and effort
- CSorts requirements into four MoSCoW categories
- DMeasures urgency through lost opportunity
Why this is the answer
Weighted scoring assigns numerical weights to criteria such as revenue impact and risk reduction, then calculates a score. This structured approach reduces subjective bias.
- Question 20Multiple Select
Which two outcomes does Cost of Delay help a business analyst quantify when a requirement is postponed? Select all that apply.
- ALost opportunityCorrect answer
- BIncreased riskCorrect answer
- CUser satisfaction
- DTechnical effort
Why this is the answer
Cost of Delay quantifies the lost opportunity and increased risk caused by postponing a feature, helping analysts justify urgency in economic terms.
- Question 21Interactive
Review the dependency mapping in the code block and identify the feature that serves as a foundational blocker for other features.
- AFeature ACorrect answer
- BFeature B
- CFeature C
- DFeature D
Why this is the answer
Feature A is a dependency for Features B and C, making it a foundational blocker. Even low-value foundational requirements may become high priority when they enable other work.
- Question 22Single Choice
Which behavior best illustrates the trap of prioritizing by technical ease rather than by business value?
- AImplementing the easiest tasks first to show progressCorrect answer
- BImplementing the highest-value requirements first
- CDelaying requirements until dependencies are mapped
- DApplying weighted scoring to every requirement
Why this is the answer
Prioritizing by technical ease means choosing the easiest tasks first to show progress. This trap ignores business value and can lead to a roadmap full of low-impact work.
Requirements
8 questions in this domain
- Question 23Single Choice
In the MoSCoW method, which category is reserved for requirements that are critical to the success of the solution?
- AMust haveCorrect answer
- BShould have
- CCould have
- DWon't have
Why this is the answer
Must have requirements are critical for success and cannot be omitted from the release.
- Question 24Multiple Select
Which statements about MoSCoW categories are correct?
- AShould have requirements are important but not vital.Correct answer
- BCould have requirements are desirable but can be omitted.Correct answer
- CWon't have requirements are excluded from this release.Correct answer
- DMust have requirements are optional if time is short.
Why this is the answer
MoSCoW distinguishes critical must-haves, important should-haves, optional could-haves, and items explicitly out of scope.
- Question 25Interactive
Refer to the matrix in the block. Which quadrant represents \"Quick Wins\"?
- AHigh Value, Low EffortCorrect answer
- BHigh Value, High Effort
- CLow Value, Low Effort
- DLow Value, High Effort
Why this is the answer
Quick Wins are high business value and low implementation effort, making them attractive first priorities.
- Question 26Single Choice
What is the main purpose of a weighted scoring model in requirements prioritization?
- AIt reduces subjective bias by using numerical weights and scores.Correct answer
- BIt replaces all stakeholder judgment with technical analysis.
- CIt ranks requirements only by implementation sequence.
- DIt identifies dependencies between requirements.
Why this is the answer
Weighted scoring assigns numerical weights to criteria such as revenue impact, risk reduction, or UX to produce a final priority score and reduce bias.
- Question 27Multiple Select
Which of the following are quantitative approaches used to prioritize requirements?
- AValue vs Effort MatrixCorrect answer
- BWeighted Scoring ModelCorrect answer
- CCost of DelayCorrect answer
- DMoSCoW Method
Why this is the answer
Value vs Effort, weighted scoring, and cost of delay are quantitative approaches; MoSCoW is a qualitative categorization.
- Question 28Interactive
If a feature loses $10,000 in value per week and is delayed 3 weeks, what is the total cost of delay based on the formula in the block?
- A$30,000Correct answer
- B$10,000
- C$3,000
- D$0
Why this is the answer
Total CoD is $10,000 per week multiplied by 3 weeks, resulting in $30,000 of lost value or increased risk.
- Question 29Single Choice
Why can a low-value requirement become high priority during dependency mapping?
- AIt is a foundational blocker for multiple high-value features.Correct answer
- BIt is the cheapest requirement in the backlog.
- CIt requires the least technical effort to build.
- DIt has no relationship with other requirements.
Why this is the answer
A requirement may be low value on its own but becomes high priority if it is a prerequisite or blocker for high-value features.
- Question 30Multiple Select
Which options are common prioritization traps that business analysts should avoid?
- APrioritizing by technical easeCorrect answer
- BIgnoring dependenciesCorrect answer
- CTreating the backlog as staticCorrect answer
- DUsing weighted scoring
Why this is the answer
Prioritizing by ease, ignoring dependencies, and static prioritization are traps; weighted scoring is a recommended technique.
User Acceptance
5 questions in this domain
- Question 31Single Choice
In the MoSCoW method, what is the meaning of 'Should have'?
- ACritical for success and cannot be omitted
- BImportant but not vital for the releaseCorrect answer
- CDesirable but can be omitted
- DNot included in this release
Why this is the answer
In MoSCoW, 'Should have' means important but not vital, so the solution can still launch without it.
- Question 32Multiple Select
Which of the following are prioritization techniques described in the playbook? Select all that apply.
- AMoSCoW MethodCorrect answer
- BValue vs. Effort MatrixCorrect answer
- CDependency MappingCorrect answer
- DScope Creep Analysis
Why this is the answer
The playbook describes MoSCoW, Value vs. Effort Matrix, Weighted Scoring, Cost of Delay, and Dependency Mapping. Scope Creep Analysis is not one of them.
- Question 33Interactive
Based on the Weighted Scoring Model results in the code block, which requirement should receive the highest priority?
- ARequirement A
- BRequirement B
- CRequirement CCorrect answer
- DRequirement D
Why this is the answer
Requirement C has the highest score (91), so it should be prioritized first under the Weighted Scoring Model.
- Question 34Single Choice
In the Value vs. Effort Matrix, how are 'Quick Wins' defined?
- AHigh business value and low effortCorrect answer
- BHigh business value and high effort
- CLow business value and low effort
- DLow business value and high effort
Why this is the answer
'Quick Wins' are requirements plotted as High Value and Low Effort in the Value vs. Effort Matrix.
- Question 35Multiple Select
Which of the following are prioritization traps highlighted in the playbook? Select all that apply.
- APrioritizing by technical easeCorrect answer
- BIgnoring dependenciesCorrect answer
- CStatic prioritizationCorrect answer
- DUsing weighted scoring
Why this is the answer
The identified traps are Prioritizing by Technical Ease, Ignoring Dependencies, and Static Prioritization. Weighted Scoring is a recommended method, not a trap.
User Stories
8 questions in this domain
- Question 36Single Choice
What does the MoSCoW method primarily help a business analyst do?
- ACategorize requirements into four priority groupsCorrect answer
- BCalculate the return on investment of a project
- CIdentify all technical dependencies
- DAssign monetary values to user stories
Why this is the answer
MoSCoW categorizes requirements as Must have, Should have, Could have, or Won't have to establish priority boundaries.
- Question 37Multiple Select
Which statements about the Value vs. Effort Matrix are correct?
- AHigh value and low effort is a Quick WinCorrect answer
- BHigh value and high effort is a Major ProjectCorrect answer
- CLow value and low effort should always be avoided
- DIt plots business value against implementation effortCorrect answer
Why this is the answer
The Value vs. Effort Matrix plots business value against effort, with Quick Wins being high value/low effort and Major Projects being high value/high effort.
- Question 38Interactive
Review the four requirements in the code block. Which one should be classified as a Must have using MoSCoW?
- AThe requirement the system cannot launch withoutCorrect answer
- BThe requirement that is important but has a workaround
- CThe requirement that is desirable but optional
- DThe requirement that is explicitly out of scope
Why this is the answer
A Must have is critical for success, so the requirement without which the system cannot launch belongs in that category.
- Question 39Single Choice
What does Cost of Delay quantify in requirement prioritization?
- AThe lost opportunity or risk caused by postponing a featureCorrect answer
- BThe total monetary cost to build the feature
- CThe amount of effort needed to develop the requirement
- DThe number of dependencies blocked by the feature
Why this is the answer
Cost of Delay helps business analysts justify urgency by quantifying lost opportunity or increased risk from postponing a requirement.
- Question 40Multiple Select
Which of the following are prioritization traps described in the playbook?
- AChoosing tasks based on technical easeCorrect answer
- BTreating requirements as independent unitsCorrect answer
- CAssuming the backlog never changesCorrect answer
- DApplying a weighted scoring model
Why this is the answer
The traps are prioritizing by technical ease, ignoring dependencies, and static prioritization. Weighted scoring is a valid prioritization method.
- Question 41Interactive
Review the dependency relationships in the code block. Why should the low-value feature be considered a high priority?
- AIt is a prerequisite for multiple featuresCorrect answer
- BIt has the lowest implementation effort
- CIt is a Must have by definition
- DIt reduces the cost of delay
Why this is the answer
Dependency mapping shows that a low-value requirement becomes high priority when it blocks multiple high-value features.
- Question 42Single Choice
What is the main purpose of a Weighted Scoring Model?
- AIt assigns numerical weights to criteria to compute a priority scoreCorrect answer
- BIt maps requirements by value and effort
- CIt identifies dependencies between features
- DIt calculates the cost of delaying a requirement
Why this is the answer
A Weighted Scoring Model uses stakeholder-assigned weights for criteria to produce a priority score and reduce subjective bias.
- Question 43Multiple Select
Which statements about the MoSCoW method are correct?
- AIt provides clear development cycle boundariesCorrect answer
- BIt helps manage scope creepCorrect answer
- CIt eliminates the need to prioritize dependencies
- DIt groups requirements into four priority categoriesCorrect answer
Why this is the answer
MoSCoW creates clear boundaries for development cycles, manages scope creep, and groups requirements into four categories.
Frequently asked questions
Everything about the Salesforce Certified Business Analyst question bank and how to use it.