Professional Documents
Culture Documents
me/PrMaB
https://t.me/PrMaB
PMI-PBA® EXAM PREP
Questions, Answers & Explanations
www.PMTraining.com
https://t.me/PrMaB
PMI-PBA® Exam Prep
Questions, Answers & Explanations
Christopher Scordo, PMP
www.PMTraining.com
https://t.me/PrMaB
Copyrighted Material
© Copyright 2020 by SSI Logic. Printed and bound in
the United States of America. All rights reserved. No
part of this book may be reproduced or transmitted in
any form or by any means, electronic or mechanical, or
incorporated into any information retrieval system,
electronic or mechanical, without the written
permission of the copyright owner.
Edition 2020.
Although the author and publisher of this work have
made every effort to ensure accuracy and completeness
of content entered in this book, we assume no
responsibility for errors, inaccuracies, omissions, or
inconsistencies included herein. Any similarities of
people, places, or organizations are completely
unintentional. Published by PMTraining Press.
DLI&M&V.
ISBN - 9798694541756
Looking for more PMI-PBA exam prep, courseware,
and classes?
Visit us at www.PMTraining.com
All inquiries should be addressed via email to:
support@pmtraining.com
or by mail post to:
PMTraining
2093 Philadelphia Pike #9038
Claymont, DE 19703
https://t.me/PrMaB
“PMI”, “PMI-PBA”, “PMP”, and “PMBOK Guide” are
registered marks of Project Management Institute, Inc.
https://t.me/PrMaB
TABLE OF CONTENTS
Introduction
Welcome
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) - 12
https://t.me/PrMaB
Introduction
https://t.me/PrMaB
WELCOME
Thank you for selecting SSI Logic’s PMI-PBA® Exam Prep –
Questions, Answers, and Explanations for your PMI
Professional in Business Analysis (PMI-PBA)® study needs.
The goal of this book is to provide condensed mock exams and
practice tests which allow you to become comfortable with the
pace, subject matter, and difficulty of the PMI-PBA exam.
The content in this book is designed to optimize the time you
spend studying in multiple ways.
1. Practice exams in this book are condensed to be
completed in one hour; allowing you to balance your
time between practice tests and offline study.
https://t.me/PrMaB
Please note: The PMBOK ® Guide – Sixth Edition, Business
Analysis for Practitioners: A Practice Guide, and The PMI
Guide to Business Analysis, are the three PMI publications
listed as reference texts for the PMI-PBA® certification
exam. Exam candidates should be aware that the PMI-
PBA® examination is not only written according to these
three references. The PMI-PBA® is a competency-based
credential which assesses the integrated set of knowledge,
skills and abilities as gained from both practical and
learned experiences.
https://t.me/PrMaB
postgraduate degree from a GAC accredited
program.
36 months of professional experience for
individuals with a bachelor’s degree or global
equivalent (within the past 8 years)
60 months of professional experience for
individuals without a bachelor’s degree or
equivalent (within the past 8 years)
https://t.me/PrMaB
25 randomly placed “pretest questions” are included,
and do not count towards the pass/fail determination
Individuals have four hours to complete the exam
Only correct answers count, and a passing score is
determined by “sound psychometric analysis”. This
method indicates that scores reflect the difficulty of
the questions answered.*
https://t.me/PrMaB
Practice Exams and Quizzes
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) - 1
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 1
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. The agile technique of on-demand scheduling is not
suitable when:
A. Project requirements can be decomposed into
smaller chunks that are relatively similar in size
and scope.
https://t.me/PrMaB
primarily uses the Internal Rate of Return (IRR) of all
opportunities as a financial viability measure. Which of
the following statements regarding Internal Rate of Return
(IRR) is correct?
A. IRR is the rate at which the total cash inflow is
higher than the total cash outflow.
https://t.me/PrMaB
months in elicitation planning activities. What is your
opinion about this?
A. The business analyst is doing a commendable job.
The more robust the planning, the more robust the
output.
https://t.me/PrMaB
All of the following activities may be performed to
prepare for an elicitation activity EXCEPT:
A. Identifying supporting materials
B. Gemba
https://t.me/PrMaB
C. Kaizen
D. Five-whys
https://t.me/PrMaB
to find out that nobody has a clear idea regarding “who
does what?” in the sales pipeline management and rather
react to sales opportunities as they come. You call a
workshop and invite some key stakeholders to define a
new process flow. What should you do next?
A. Conduct a 5S workshop.
https://t.me/PrMaB
B. Horizontally, setup the story map to show what will
be developed by the product team; and vertically,
depict what will be outsourced to the vendor.
B. Traceability matrix
https://t.me/PrMaB
C. Context diagram
D. Activity diagram
B. Majority
C. Plurality
https://t.me/PrMaB
D. Autocracy
B. Scope creep
C. Progressive elaboration
D. Rolling-wave planning
B. Business case
C. Product backlog
D. Situation statement
https://t.me/PrMaB
A. A product lifecycle may consist of multiple project
life cycles.
B. Definition of Ready
C. Team Charter
D. Definition of Done
https://t.me/PrMaB
A. Evaluating acceptance results from product
releases.
https://t.me/PrMaB
D. This is a valid adaptive technique called Real
Options.
B. Statistical sampling
C. Check sheets
D. Checklists
B. Retrospectives
C. Feature injection
https://t.me/PrMaB
D. Burndown charts
C. Fishbone diagram
B. Implementation dependency
C. Value dependency
D. Discretionary dependency
https://t.me/PrMaB
procurement processes. He has asked you to digitize the
processes using the latest technology. You are currently
performing Needs Assessment processes. How will you
determine the expected business value that would be
provided by the proposed solution?
A. By conducting system usability testing.
B. State diagram
C. Use case
D. Context diagram
B. Brainstorming
C. Document analysis
D. Benchmarking
https://t.me/PrMaB
34. What does the term INVEST stand for?
A. Independent, negotiable, valuable, estimable, small,
and testable
B. Benchmarking
C. 80/20 analysis
D. Gap analysis
https://t.me/PrMaB
B. Stakeholder analysis
D. SWOT analysis
B. Decision table
D. Affinity diagram
https://t.me/PrMaB
39. Agile teams identify project risks and determine
respective mitigation actions during which of the
following events?
A. Daily standups and retrospectives
B. Retrospectives
D. Daily standups
B. Observation
C. Interviews
D. Facilitated workshop
41. Early in the project, you are meeting with your team
and would like to address all the strengths, weaknesses,
opportunities, and threats the project is facing. What tool
should be used?
A. SWOT Analysis
B. Interviewing
C. Delphi Technique
D. Brainstorming
https://t.me/PrMaB
42. Which of the following techniques does not help in
identifying underlying root cause of a given problem?
A. Brainstorming
B. Fishbone Diagrams
C. Burndown charts
D. Five Whys
43. You have recently taken over a project that has been
struggling to keep key project stakeholders engaged since
inception. The project requires developing an ERP system
for your organization and the project currently is in the
design phase. A number of stakeholders are complaining
that the current design doesn’t match their stated
requirements. Which of the following tools will help you
trace the design to the requirements?
A. Design traceability matrix
B. RACI
C. PERT
D. OBS
https://t.me/PrMaB
45. You are leading the business analysis activities for a
product team developing a software application for a
client organization. All product requirements and design
documents need to be approved by the client prior to
development. Further, these need to be updated to
correspond to each product release. These updated
documents are known as:
A. Non-functional requirements
B. Prototypes
C. Obligations
D. As-built documentation
B. Document analysis
C. Facilitated workshops
D. Focus group
https://t.me/PrMaB
A. Develop a feature model
B. Storyboarding
C. MoSCoW
D. Kanban
B. Business Case
C. Business Need
D. Situation Statement
https://t.me/PrMaB
collaboration tool. Given the uncertainty with the product
requirements, the team has decided to develop the project
using Agile practices. On this project, you cannot
implement a formal requirements approval process. In this
situation, which of the following can be used in place of
approval?
A. Definition of done
B. Product backlog
C. Definition of ready
D. Retrospectives
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) - 1
Answer Key and Explanations
1. B - If the use of a predictive lifecycle is mandated by
the customer, no other project life cycles can be selected.
Hence most of the agile techniques will be inapplicable in
those scenarios. [PMBOK® Guide 6th edition, Page 177]
[Planning]
2. B - The Internal Rate of Return (IRR) gives the
projected annual yield of an investment (rate of return)
considering the time value of money. The IRR value
signifies the interest rate at which the net present value of
all cash flows will equal zero.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
3. C - Elicitation is more than collecting or gathering
product information. Stakeholders do not always have
product information readily available with them. A
business analyst has to work out ways to elicit product
information from the stakeholders.
[The PMI Guide to Business Analysis, page 154]
[Analysis]
4. D - Spending two months off time for elicitation
planning does not look all right for a six-month project. In
the current situation, you have less than four months to do
the actual elicitation and product development. The
business analyst should have been more aware that
elicitation consumes project resources; therefore, there is a
cost for each facilitated workshop completed, each
interview conducted, and every survey sent.
[Business Analysis for Practitioners: A Practice Guide,
page 53; The PMI Guide to Business Analysis, page 127]
[Planning]
5. C - When stakeholders work remotely, it is helpful to
identify the methods used for connectivity. This
https://t.me/PrMaB
information can be used when determining the best
approach for collaboration, for example, conference calls,
desktop sharing, web conferencing, etc. Limiting the
business analysis activities to one location or deploying
the system with standard configurations will be bad
choices. Requesting additional budget and time are
irrelevant here.
[Business Analysis for Practitioners: A Practice Guide,
page 44; The PMI Guide to Business Analysis, page 115-
116] [Planning]
6. D - Decomposing epics into smaller user stories is a
task the development team needs to assist you with; this is
not an elicitation activity. The rest of choices are all valid
activities performed to prepare for an elicitation activity.
[The PMI Guide to Business Analysis, page 161]
[Analysis]
7. D - Solution evaluation activities are performed to
assess whether a solution has achieved the desired
business results. Solution evaluation consists of the work
done to analyze measurements obtained for the solution by
comparing the actual results of acceptance testing to the
expected or desired results.
[The PMI Guide to Business Analysis, page 278]
[Traceability & Monitoring]
8. A - Kanban is an adaptive technique in which items
are pulled from a backlog and started when other product
backlog items are completed. Kanban also establishes
work-in-progress limits to constraint the number of
product backlog items that can be in progress at any point
in time.
[The PMI Guide to Business Analysis, page 400]
[Analysis]
9. A - The user story is not wanted at this stage.
However, it has not been established that it is unwanted.
The best course of action is to move the story back into the
product backlog where it will be reprioritized.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 264]
[Traceability & Monitoring]
10. A - An activity diagram is a type of process model
that visually shows the complex flow of use cases.
Activity diagrams are like process flows in syntax;
however, they commonly show user and system
interactions in one diagram and mirror the textual
descriptions of use cases.
[The PMI Guide to Business Analysis, page 387]
[Analysis]
11. C - The problem at hand was that there was no agreed
and documented sales pipeline management process. To
resolve this problem, you called a stakeholder workshop
to define the sales pipeline process flow. As the next step,
you need to perform the Confirm Elicitation Results
process to validate this process with a wider stakeholder
group, i.e., all involved and relevant stakeholders.
[The PMI Guide to Business Analysis, pages 170]
[Analysis]
12. D - The feature mode can be used in combination with
brainstorming techniques to help stakeholders identify
features by focusing on the groupings, similar to an
affinity diagram. Affinity diagrams provide a sample
format for the development of a feature model.
[The PMI Guide to Business Analysis, page 193]
[Analysis]
13. D - Story mapping is a technique used to sequence
user stories based upon their business value and the order
in which their users typically perform them. Regarding
the setup: horizontally, setup the story map to show what
will be delivered within an iteration; and vertically, depict
the higher-level groupings of the user stories.
[The PMI Guide to Business Analysis, page 261]
[Traceability & Monitoring]
14. A - Creating a Pareto chart does not make any sense.
Using IRR as a primary valuation technique and using the
https://t.me/PrMaB
payback period as a tie breaker or vice versa does not
mean that you are combining the results from these two
valuations techniques. A weighted ranking matrix is used
to weight, rate, and score each criterion against a set of
options. This table can be used to combine the results of
the two valuation techniques by using these as criteria and
assigning weights to these criteria.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
15. D - Activity diagrams are types of process flows that
can be used for general workflow modeling, but
commonly are used to visually show the complex flow of
use cases.
[The PMI Guide to Business Analysis, page 198]
[Analysis]
16. D - Solution Evaluation often requires early
preparation, so that what is needed to perform this work is
in place later when evaluation is conducted.
[The PMI Guide to Business Analysis, pages 277, 279]
[Evaluation]
17. D - Since the only product owner has the authority to
prioritize the user stories, this is the autocratic style of
decision making.
[The PMI Guide to Business Analysis, page 267]
[Traceability & Monitoring]
18. A - Story mapping is a technique used to sequence
user stories, based upon their business value and the order
in which their users typically perform them, so that teams
can arrive at a shared understanding of what will be built.
[The PMI Guide to Business Analysis, page 101] [Needs
Assessment]
19. C - Although the situation statement, the business
case, and the project charter should all contain a high-
level product scope, these documents are generally not
referred to by the developers as the reference for product
development. The product backlog lists all the product
https://t.me/PrMaB
backlog items—typically user stories, requirements, or
features—that need to be delivered for a solution. The
product backlog is used by the developers as a reference
for all product development activities.
[The PMI Guide to Business Analysis, page 213]
[Analysis]
20. B - A product lifecycle encompasses one or more
project lifecycles; it doesn’t succeed a project lifecycle. If
a project is all about creating a new product, that project
lifecycle is part of the overall product lifecycle.
[The PMI Guide to Business Analysis, page 15] [Needs
Assessment]
21. B - Story elaboration is the process by which user
stories are further detailed with additional information
until they are ready for development. The rest of the
choices are all irrelevant to the context.
[The PMI Guide to Business Analysis, page 214]
[Analysis]
22. B - “Definition of ready” is a series of conditions that
the entire team agrees to complete before a user story is
considered sufficiently understood for work to begin to
construct it.
[The PMI Guide to Business Analysis, page 394]
[Analysis]
23. D - Evaluating the product team’s productivity is part
of project performance evaluation and not post-
implementation solution evaluation. The rest of the
choices are ways to determine whether value has been
delivered by the released product.
[The PMI Guide to Business Analysis, page 281]
[Evaluation]
24. C - The business analyst does not decide which
features are built and which are not. The authority lies
with the stakeholders, and in adaptive projects, with the
product owner to approve or reject requirements. As the
business analyst, you are responsible for first trying to
https://t.me/PrMaB
resolve this conflict through negotiation. If consensus is
not possible among the immediate team, the authority
levels governing the requirements approval process set
forth in the stakeholder engagement approach need to be
followed.
[The PMI Guide to Business Analysis, page 264]
[Traceability & Monitoring]
25. D - Scope creep means uncontrolled changes.
Progressive elaboration involves continuously detailing
project scope as more detailed and specific information
become available. The scenario presents a valid adaptive
technique that insists on reducing the number of decisions
a team must make at any given point in time by delaying
all decision making as late as possible.
[The PMI Guide to Business Analysis, page 89] [Needs
Assessment]
26. A - Control chart is a monitoring tool, while the rest
of the choices are valid data gathering tools used during
Control Quality process. [PMBOK® Guide 6th edition,
Pages 302, 303] [Traceability & Monitoring]
27. C - A point of diminishing returns is reached when
additional value that could be obtained from the solution
does not justify the additional effort needed to achieve
that value.
[The PMI Guide to Business Analysis, page 279]
[Evaluation]
28. C - Feature injection, mostly used in an adaptive
development, challenges the traditional product
requirements management approaches by guiding the
product teams to analyze only those features that are
deemed to be of the highest value and reduce the time
spent on analyzing low-value requirements.
[The PMI Guide to Business Analysis, page 88] [Needs
Assessment]
29. D - Monte Carlo analysis and the fishbone diagram
are risk management and quality management tools
https://t.me/PrMaB
respectively. Stakeholder register is a project artifact and
not a tool or technique. The correct answer is “stakeholder
engagement assessment matrix” which helps a project
manager in mapping the current and desired stakeholder
engagement levels. [PMBOK® Guide 6th edition, Page
521] [Analysis]
30. A - The requirements have a subset relationship. A
subset requirement generally adds further detail to a
higher-level requirement.
[The PMI Guide to Business Analysis, page 259]
[Traceability & Monitoring]
31. C - In business analysis, business value refers to the
time, money, goods or intangibles in return for something
exchanged. In this scenario, the goal is to reduce the
procurement processing times and the business value can
be demonstrated by reduction in this processing time.
[The PMI Guide to Business Analysis, page 59] [Needs
Assessment]
32. B - A state diagram is a data model. None of the other
choices are data models.
[The PMI Guide to Business Analysis, page 185]
[Analysis]
33. A - The business analyst may choose to elicit
requirements through facilitated workshops when key
stakeholders are local but use interviews or surveys when
key stakeholders are dispersed or when time zone
differences make scheduling conference calls difficult.
Documentation analysis may be used when stakeholders
are not available at all. Brainstorming is a wrong choice
as that requires facilitated sessions. Benchmarking
requirements will not give you your stakeholders’
requirements.
[Business Analysis for Practitioners: A Practice Guide,
page 44; The PMI Guide to Business Analysis, page 115-
116] [Planning]
https://t.me/PrMaB
34. A - The term INVEST describes the characteristics
that user stories need to demonstrate to be considered
“good” and “ready” for development in adaptive
approaches. INVEST is an acronym for independent,
negotiable, valuable, estimable, small, and testable.
[The PMI Guide to Business Analysis, page 223]
[Analysis]
35. A - Document analysis is an elicitation technique used
to analyze existing documentation to identify information
relevant to the requirements. While identifying problems
or opportunities, this technique involves reviewing
information relevant to the business need. For example,
strategic goals and objectives, performance goals and
results, customer survey results, documentation about
current processes, and business rules might be analyzed.
[The PMI Guide to Business Analysis, page 61] [Needs
Assessment]
36. B - Stakeholder analysis is a technique used to
systematically gather and analyze quantitative and
qualitative information to determine whose interests
should be taken into account throughout the project.
[Business Analysis for Practitioners: A Practice Guide,
page 39; The PMI Guide to Business Analysis, page 115]
[Planning]
37. A - In adaptive projects, there is no formal change
request process. All of the other choices are correct.
[The PMI Guide to Business Analysis, page 272]
[Traceability & Monitoring]
38. D - The feature mode can be used in combination with
brainstorming techniques to help stakeholders identify
features by focusing on the groupings, similar to an
affinity diagram. Affinity diagrams provide a sample
format for the development of a feature model.
[The PMI Guide to Business Analysis, page 193]
[Analysis]
https://t.me/PrMaB
39. C - Risks can be identified at any time: daily
standups, retrospectives and/or demonstrations.
[The PMI Guide to Business Analysis, page 244]
[Planning]
40. D - Facilitated workshops are viable elicitation
techniques to be used when defining the future state
because these support interactivity, collaboration and
work towards a stated objective.
[The PMI Guide to Business Analysis, page 79] [Needs
Assessment]
41. A - A SWOT Analysis chart would be the best
choice. SWOT is an acronym for strengths, weakness,
opportunities and threats. [PMBOK® Guide 6th edition,
Page 415] [Planning]
42. C - Brainstorming can be used to identify root causes
by generating a number of divergent ideas. This is usually
an underpinning technique for more accurate root cause
analysis techniques such as Five Whys and Fishbone
diagrams.
[The PMI Guide to Business Analysis, page 131]
[Analysis]
43. C - The requirements traceability matrix provides a
structure to trace requirements to product design.
[PMBOK® Guide 6th edition, Page 148] [Traceability &
Monitoring]
44. B - RACI (Responsible, Accountable, Consult,
Inform) analysis is performed in business analysis when
determining roles and responsibilities for the business
analysis effort. The rest of the choices are tools that
cannot help in analyzing roles and responsibilities.
[Business Analysis for Practitioners: A Practice Guide,
page 63; The PMI Guide to Business Analysis, page 111]
[Planning]
45. D - The as-built documentation is the analysis and
design documentation that has been updated to correspond
to a released product.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 388]
[Analysis]
46. B - Document analysis is a viable technique to use to
gain an understanding of the business environment and
situation prior to engaging directly with stakeholders. The
rest of the choices all require stakeholder engagement.
[The PMI Guide to Business Analysis, page 167]
[Analysis]
47. C - You need to develop a sequence diagram to meet
the team’s requirement. Sequence diagrams describe how
user or system processes interact with one another across
any involved users or systems and the order in which the
processes or steps are performed.
[The PMI Guide to Business Analysis, page 199]
[Analysis]
48. B - Storyboarding is a prototyping technique that
shows the sequence or navigation of events through a
series of images or illustrations. Wireframes, on the other
hand, are static blueprints or schematics of a user interface
and are basically used to identify functionality. The other
two options are irrelevant.
[The PMI Guide to Business Analysis, page 168]
[Analysis]
49. D - The situation statement is an output of the Identify
Problem or Opportunity process that is an input to the
Assemble Business Case process. You must request for
the situation statement of the project.
[The PMI Guide to Business Analysis, page 58] [Needs
Assessment]
50. C - The definition of ready can be used in place of
approval in adaptive life cycles to help the project team
know that the user story is sufficiently elaborated and
ready to be brought into an iteration for the development
team to work on.
[The PMI Guide to Business Analysis, page 265]
[Traceability & Monitoring]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) - 2
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 2
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. You have been asked to analyze the current sales and
marketing capabilities of your organization and design and
implement a sales pipeline management process. In order
to proceed, you need an initial list of key stakeholders to
start your conversations. Which of the following
techniques could be used to quickly generate an initial list
of stakeholders?
A. Observing the process
https://t.me/PrMaB
understand their needs and expectations from the project.
The datacenter currently serves a number of business
critical applications and attention to risk management is
critical. Which of these is not a data gathering technique
used in the Identify Risks process?
A. Brainstorming
B. Checklists
C. Delta technique
D. Interviewing
C. Kano model
D. MoSCoW
https://t.me/PrMaB
B. Participants feed off each other’s inputs to generate
additional ideas.
C. Stakeholder register
B. Sailboat
C. Speedboat
D. Kayak
https://t.me/PrMaB
recommended to write one much larger user story for such
features rather than multiple fine-grained user stories.
Such stories are called:
A. Tales
B. Macro-stories
C. Epics
D. Micro-stories
B. CRUD matrix
C. Organizational charts
https://t.me/PrMaB
C. Not ready, ready, and done
B. Kanban board
C. Product backlog
https://t.me/PrMaB
D. Develop a rollover schedule.
https://t.me/PrMaB
15. A product team has recently developed a new product.
Several performance issues were reported by the
stakeholders during the UAT sessions. You have collected
the necessary data regarding the reported issues and want
to analyze the results. Which of the following techniques
would you use to analyze the performance divergence
from the acceptance criteria?
A. MoSCoW analysis
B. Sensitivity analysis
C. Kano analysis
D. Variance analysis
https://t.me/PrMaB
B. Elicitation preparation and determining elicitation
approach are just two names of the same process.
B. Product backlog
C. Definition of done
D. Burndown chart
https://t.me/PrMaB
the project and the highly regulated project environment,
you are considering using a requirements management
tool on this project. All the following are typical features
of a requirements management tool except:
A. MoSCoW analysis
B. Traceability support
D. Configuration management
https://t.me/PrMaB
A. Pareto diagram
B. Ishikawa diagram
C. Capability table
D. Kano diagram
B. Prioritized requirements
C. Validated requirements
D. Verified requirements
B. Acceptance Testing
C. Penetration Testing
D. Preproduction Testing
https://t.me/PrMaB
project. Which of the following techniques will help you
group the stakeholders based on their behaviors?
A. Job analysis
C. RACI
D. Persona analysis
B. Context diagram
C. Event list
D. PERT diagram
https://t.me/PrMaB
in the next three weeks. Which Agile planning meeting is
this?
A. Daily scrum
B. Retrospective
C. Release planning
D. Iteration planning
B. Indifferent
C. Reverse
D. Delighters
https://t.me/PrMaB
31. You are analyzing your product requirements and
defining product use cases. You want to develop a one use
case diagram that would show the user and use case
interactions. In a use case diagram, people or other
systems that interact with the solution are known as:
A. Actors
B. Roles
C. Stakeholders
D. Players
https://t.me/PrMaB
environment, which of the following business analysis
techniques will you use?
A. Fishbone analysis
B. 80/20 analysis
C. Five-whys
D. SWOT analysis
https://t.me/PrMaB
B. The relevant business goals and objectives might be
associated with one or more KPIs.
https://t.me/PrMaB
would take you to recover your investment in the
complimentary product?
A. PBP
B. NPV
C. IRR
D. ROI
B. Trigger
C. Alternate course
https://t.me/PrMaB
D. Exception
B. Story Points
C. KLOC
D. Velocity
B. Iterative
https://t.me/PrMaB
C. Incremental
D. Agile
https://t.me/PrMaB
testing session, the project team finds out that a
component in the product is not responding to commands
as documented in the specifications causing integration
testing to fail. This has caused a major embarrassment for
the project team in front of the customer. What should you
do to resolve this defect?
A. Conduct a root cause analysis; identify and fix the
issue.
46. During the first iteration, the Agile team realizes that
the project is not as easy as they earlier estimated. There
is an immediate need for review of the project
management approach. What should you do?
https://t.me/PrMaB
A. Re-estimate the backlog.
B. Call a retrospective.
https://t.me/PrMaB
D. A predictive business analysis planning is required
on all Agile projects.
A. 5S
B. 7Ws
C. 80/20
D. 3Cs
50. You and your Agile team are currently analyzing your
project’s backlog. You want to identify the stories that
have historically delighted the users but now have become
their basic requirements. Which Agile techniques are you
applying?
A. Value stream mapping
B. Fishbone analysis
C. Kano analysis
D. Backlog grooming
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) - 2
Answer Key and Explanations
1. D - Since you are designing a new process, you can
observe the process or review the process documentation.
Developing RACI matrix is irrelevant here. However,
reviewing the organizational charts will help you identify
the initial list of stakeholders.
[Business Analysis for Practitioners: A Practice Guide,
page 40; The PMI Guide to Business Analysis, page 111]
[Planning]
2. C - Delta technique is not a valid type of data
gathering technique. [PMBOK® Guide 6th edition, Page
409] [Planning]
3. A - A salience model is used to classify stakeholders
and not product features. The rest of the choices can all be
used to classify product features.
[The PMI Guide to Business Analysis, pages 79, 81, 234]
[Needs Assessment]
4. B - During brainstorming sessions, participants feed
off each other’s input to generate additional ideas. This is
not possible through questionnaires and surveys.
[Business Analysis for Practitioners: A Practice Guide,
page 39; The PMI Guide to Business Analysis, page 111]
[Planning]
5. D - A change request form is used to initiate a change
in the project baselines. The risk management plan does
not document the stakeholder engagement strategy.
Although the stakeholder register contains stakeholder
identification, classification and assessment information, it
does not record the stakeholder engagement strategy.
James should search for a stakeholder engagement plan
template where all this information can be updated.
[PMBOK® Guide 6th edition, Page 522] [Needs
Assessment]
https://t.me/PrMaB
6. C - Speedboat is an elicitation technique that uses
game play to elicit information about product features that
customers/stakeholders find problematic.
[The PMI Guide to Business Analysis, page 166]
[Analysis]
7. C - Larger user stories are known as epics.
[The PMI Guide to Business Analysis, page 95]
[Planning]
8. B - CRUD, defined as create (C), read (R), update (U),
and delete (D), represents the operations that can be
applied to data or objects. CRUD matrices describe who or
what has permission to perform each of the CRUD
operations on elements, such as data or user interface
screens.
[The PMI Guide to Business Analysis, page 197]
[Analysis]
9. B - The requirements life cycle on predictive projects
represents the various phases or states through which a
requirement moves as it is defined, elaborated, verified,
validated and prioritized. When using an adaptive delivery
approach, the requirement states may be more implicit.
User stories may be states as not ready, ready, or done.
[The PMI Guide to Business Analysis, page 179]
[Analysis]
10. A - A requirements management tool allows
requirements and other product information to be captured
and stored in a repository. This tool will help you not only
to manage your requirements by their individual
requirement lifecycle stages, it will help you maintain a
change log and an audit trail.
[The PMI Guide to Business Analysis, page 213]
[Analysis]
11. A - Once the training and other transition
requirements have been identified, the next logical step is
to define the transition plan.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 297]
[Planning]
12. C - In adaptive life cycles, the requirements are
documented in user stories that are then prioritized and
refined. The product features are developed using time-
boxed periods of work. [PMBOK® Guide 6th edition,
Page 177] [Analysis]
13. C - Depending on organizational norms, obtaining a
release decision may include obtaining signoff. For an
iterative or adaptive project life cycle, informal signoff
generally occurs at the end of each sprint or iteration, with
formal signoff, when required, occurring prior to each
release of the solution to the production environment.
[The PMI Guide to Business Analysis, page 296]
[Evaluation]
14. D - Time-boxed periods are durations during which
the team works steadily toward completion of a goal.
Time-boxing helps to minimize scope creep as it forces
the teams to process essential features first, then other
features when time permits. [PMBOK® Guide 6th
edition, Page 182] [Planning]
15. D - Variance is a quantifiable deviation, departure, or
divergence from a known baseline or expected value.
Variance analysis is a technique for determining the cause
and degree of difference between the baseline and actual
performance.
[The PMI Guide to Business Analysis, page 293]
[Evaluation]
16. D - Features that are neither differentiating nor
mission critical to the organization and generally not built.
[The PMI Guide to Business Analysis, page 82] [Needs
Assessment]
17. C - Elicitation preparation is the planning performed
prior to the start of each elicitation activity, while
determining elicitation approach is the planning
performed prior to commencing the elicitation stage.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 160]
[Analysis]
18. A - Ecosystem maps are most useful when they are
created at the beginning of projects to understand all the
systems that may be affected by or that will impact the in-
scope systems.
[The PMI Guide to Business Analysis, page 190]
[Analysis]
19. D - You need to have a look at the burndown chart.
The burndown chart will tell the number of story points
remaining and the current team’s velocity. Teams might
update velocity on a Kanban board, but this is not a
common practice.
[The PMI Guide to Business Analysis, page 131, 148]
[Planning]
20. C - Requirements management tools allow
requirements and other product information to be captured
and stored in a repository. These tools help maintain audit
trails and perform version control to assist with change
management. These tools also facilitate review and
approval processes thorough workflow functionality.
Requirements management tools catered to adaptive
projects may include additional functionality to create and
manage product and iteration backlogs, and produce
burndown charts. Cost performance management is not a
typical component of a requirements management tool.
[The PMI Guide to Business Analysis, page 260]
[Traceability & Monitoring]
21. A - On projects using an adaptive life cycle, the
product team may choose to develop an interaction matrix
which is a lightweight version of a traceability matrix that
is used to determine whether requirements are sufficiently
detailed or if any entities are missing. Interaction matrix is
a temporary artifact that represents a snapshot in time,
whereas a traceability matrix is typically maintained
throughout a project.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 261]
[Traceability & Monitoring]
22. D - A Kano diagram is used to analyze a product’s
features. The rest of the choices can all be used to
communicate the results of a root cause analysis.
[The PMI Guide to Business Analysis, pages 67, 69, 70,
79] [Needs Assessment]
23. A - Approving requirements is performed to obtain
agreement that the requirements accurately depict what
the product team is being asked to build. Requirements
that are approved establishes the requirements baseline.
[The PMI Guide to Business Analysis, page 264]
[Traceability & Monitoring]
24. D - Preproduction Testing involves testing a solution
in a separate environment that is identical or nearly
identical to the production environment, so that adverse
interactions with other products in the production
environment can be observed and addressed before the
solution is released to production.
[The PMI Guide to Business Analysis, page 405]
[Analysis]
25. D - A persona is a fictional character created to
represent an individual or group of stakeholders, termed a
user class. For an individual class, a persona can include
any number of descriptive features the team decides are
worth capturing; for example, goals, behaviors,
motivations, demographics, and high-level requirements,
etc.
[The PMI Guide to Business Analysis, page 117]
[Planning]
26. C - An event list is a scope model that describes any
external events that trigger solution behavior. Event lists
help define the in-scope events that the solution must
react to or handle.
[The PMI Guide to Business Analysis, page 192]
[Analysis]
https://t.me/PrMaB
27. A - Although anyone can write a user story, the
product owner decides whether and where to place the
story in the backlog.
[The PMI Guide to Business Analysis, page 216]
[Analysis]
28. D - Iteration planning is conducted at the start of each
iteration. During iteration planning we talk about the tasks
that will be needed to transform a feature request into
working and tested software during the iteration, which is
typically two to six weeks in duration.
[The PMI Guide to Business Analysis, page 233]
[Planning]
29. D - You cannot resolve this issue unless you get to the
root cause of this. You need to set up a meeting with the
sponsor and try to understand the reason behind her
disengagement. The project might have lost its business
value so you need to re-evaluate that before you walk in
to that meeting. [PMBOK® Guide 6th edition, page 528]
[Analysis]
30. D - Delighters are the new features that provide great
satisfaction to the customers if provided, but if not
provided, will not cause any dissatisfaction since the
customers do not expect them to be present in a solution.
[The PMI Guide to Business Analysis, page 80] [Needs
Assessment]
31. A - In a use case diagram, the people or other systems
that interact with the solution are known as actors.
[The PMI Guide to Business Analysis, page 387]
[Analysis]
32. D - Creating a comprehensive but generic product
training to ensure all users are trained on all system
components will not only be an expensive and time-
consuming activity, but most of the content will be
irrelevant for most of the users. You need to be specific
over here; ideally you should conduct a detailed gap
https://t.me/PrMaB
analysis for each user role and identify user group specific
training requirements.
[The PMI Guide to Business Analysis, page 398]
[Analysis]
33. D - SWOT analysis is a technique for analyzing the
strengths, weaknesses, opportunities and threats of an
organization. This technique focuses on the organization
as a whole rather than specific business areas. The other
options are root cause analysis techniques that are useful
when analyzing some specific area of the business.
[The PMI Guide to Business Analysis, page 72] [Needs
Assessment]
34. D - Agile approaches spend less time on upfront
project planning. Requirements are gathered on the go and
these are added to the product backlog where these get
prioritized. [PMBOK® Guide 6th edition, page 131]
[Traceability & Monitoring]
35. C - Many product support business goals and
objectives can be associated with one or more key
performance indicators (KPIs), which are target
performance levels that are usually defined by an
organization’s executives. For organizations that already
define and measure KPIs, it may sometime be possible to
use one or more of these KPIs to evaluate the solution.
[The PMI Guide to Business Analysis, page 282]
[Evaluation]
36. D - If the subordinates are delegated to attend on
behalf of their seniors, they come with the authority to
validate the requirements. The risk is that these
participants do not have the exposure of working at the
level that you require, and they might not be experienced
enough to provide the information being sought.
[The PMI Guide to Business Analysis, page 161]
[Analysis]
37. A - Payback period (PBP) is the time needed to
recover an investment. Return on Investment (ROI) is the
https://t.me/PrMaB
percentage return on an initial investment. The Internal
Rate of Return (IRR) gives the projected annual yield of
an investment (rate of return) considering the time value
of money. On the other hand, the NPV (net present value)
of an investment is the difference between the present
value of cash inflows and the present value of cash
outflows over a period of time considering the time value
of money.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
38. C - Project should never be prioritized based on their
budgets. Selecting the projects that maximize
organizational revenue or selecting the projects that
maximize the business value seem good options.
However, adding to business value takes precedence over
adding the organizational revenue, since there can be
projects that add more to the revenue but add less to the
business value. [PMBOK® Guide 6th edition, Page 7]
[Needs Assessment]
39. C - The alternate course of a use case defines the
alternate set of steps an actor or system can take to
achieve the goal other than what is described in the main
flow. In this scenario, the report is being sent to the
procurement manager in case the warehouse supervisor
does not read it in time. This is the alternate course of the
use case.
[The PMI Guide to Business Analysis, page 214]
[Analysis]
40. B - Story points are a unit of measure for expressing
the overall size of a user story, feature, or other piece of
work.
[The PMI Guide to Business Analysis, pages 213, 413]
[Planning]
41. A - The walking skeleton section of a story map
contains the full set of end-to-end functionality that the
stakeholders require for the solution to be accepted or
considered functional. This set is usually described by a
https://t.me/PrMaB
set of user stories and is sometimes called the minimum
marketable features (MMF).
[The PMI Guide to Business Analysis, page 204]
[Analysis]
42. A - Once the system is successfully designed and
built, user training may be an extensive task but this can
be planned well in advance. Predictive life cycle should
be the most structured approach for this phase of the
project.
[The PMI Guide to Business Analysis, page 15]
[Planning]
43. D - This seems like a feasibility issue. It is likely that
this was missed otherwise the operational feasibility of the
system would have been thoroughly considered. Your job
as an auditor is to investigate and report. However, prior
to finalizing your report, you must compile all relevant
evidence supporting your report.
[The PMI Guide to Business Analysis, page 86]
[Evaluation]
44. B - If the product doesn’t meet the specifications, it
needs to be rejected and fixed. However, if this requires
any of the project baselines to change, a change request
needs to be issued before making the updates to the
baselines. [PMBOK® Guide 6th edition, page 83]
[Analysis]
45. D - Persona analysis is a technique that is conducted
to analyze a class of users for understanding their needs
and behaviors. During stakeholder analysis, this technique
is used to analyze how a user class interacts with a system
or how a user class would use a product. As the first step,
you need to identify the personas you need to analyze;
fictional characters that will represent the stakeholder
groups.
[The PMI Guide to Business Analysis, page 117]
[Planning]
https://t.me/PrMaB
46. B - Reprioritizing or re-estimating the backlog will
not produce any desirable results if review of the project
management approach is required. In this case, you need
to call a retrospective.
[The PMI Guide to Business Analysis, page 149]
[Planning]
47. B - You can choose whatever format for the definition
of the process. However, you need to ensure that the
process is practical and makes it easy to implement
necessary changes.
[The PMI Guide to Business Analysis, page 254]
[Traceability & Monitoring]
48. C - There is no one approach to business analysis
planning that will work for every project. The business
analyst should understand the context and project
characteristics to ensure the planning activities are
sufficiently sized for the situation.
[Business Analysis for Practitioners: A Practice Guide,
page 37; The PMI Guide to Business Analysis, page 127-
129] [Planning]
49. D - A measure of quality, in the absence of standards
or in addition to them, at a basic level, includes verifying
the information for the 3Cs: correct, complete, and
consistent.
[The PMI Guide to Business Analysis, page 222]
[Analysis]
50. C - The Kano model gives us an approach to separate
features into three categories: must-have features, linear
features, and delighters. According to the Kano model,
features that delight customers eventually become their
basic requirements.
[The PMI Guide to Business Analysis, page 79]
[Planning]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) - 3
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 2
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. You are auditing a product team that is developing a
new accounting system. You want to map out all the use
cases against all developed UI wireframes. Which of the
following tools can you use to quickly map out these
relationships and identify any gaps?
A. Interaction matrix
B. Decision tree
C. Product backlog
D. Feature model
https://t.me/PrMaB
review your consolidated notes while you help them
through this item by item. This technique is known as:
A. Delphi
B. Estimation poker
C. Walkthrough
D. Brainstorming
B. Project charter
https://t.me/PrMaB
D. Stakeholder register
C. Stakeholder register
D. Persona analysis
https://t.me/PrMaB
7. Return on investment (ROI) is commonly used to
measure the financial benefits of an investment.
Economists and financial analysts, especially for long-
term investments, generally do not prefer this method
because:
A. The formula doesn’t factor in the risk associated
with the investment.
https://t.me/PrMaB
A. Use case
B. User story
C. Process flow
D. Display-action-response model
B. CRUD matrix
C. Process flow
B. Use Case
C. Event List
D. State Diagram
https://t.me/PrMaB
developing a number of project management templates
and checklists. Which of the following is typically
documented prior to initiating a project?
A. Scope statement
B. Business requirement
D. Project charter
C. Pareto analysis
B. Affinity diagram
C. Mind mapping
https://t.me/PrMaB
D. Six thinking hats
C. Context Diagram
D. Decision Tree
B. Employee turnover
https://t.me/PrMaB
C. Scope creep
https://t.me/PrMaB
stakeholders are willing to approve it. What decision-
making style have you adopted?
A. Unanimity
B. Autocracy
C. Majority
D. Plurality
B. Hot State
C. Current State
D. Ready State
B. Traceability matrix
C. Decision matrix
https://t.me/PrMaB
23. You are leading a requirement review and approval
workshop with some senior project stakeholders. During
the workshop, a conflict developed between the
stakeholders over some requirements and you decide to
use Delphi technique to find common ground. What
should be your first step in using this technique?
A. Create a traceability matrix
C. Create a questionnaire
https://t.me/PrMaB
delivered 70% of the solution requirements. What should
you do next?
A. Allocate additional funds to the project to overturn
the point of diminishing returns.
B. Kanban
C. Spike
D. Andon
https://t.me/PrMaB
D. Conduct a 5S workshop with senior executives and
develop an action plan.
C. Autonomy
D. Plurality
https://t.me/PrMaB
However, these stakeholders were not quite sure about the
accuracy of these requirements. Which of the following
could help you confirm these requirements?
A. By meeting these stakeholders separately and
asking them to review the requirements.
B. Scope Statement
C. Product Backlog
D. Business Case
https://t.me/PrMaB
B. Call a stakeholder conference to judge their
interests.
C. PDCA
D. ISO
B. Decomposition
C. Scope baseline
D. Requirements documentation
https://t.me/PrMaB
the stakeholders by common characteristics. Which of the
following processes should you perform?
A. Identify Stakeholders
https://t.me/PrMaB
you were not able to identify which project requirements
have been approved. You are now reviewing the meeting
minutes of all stakeholder engagements during the
requirement elicitation stage. Which of the following
requirements are safe to be considered as approved?
A. All requirements that are verified.
B. Backlog grooming
C. MoSCoW
D. Kano Analysis
https://t.me/PrMaB
B. Facilitate Product Roadmap Development
41. You have been asked to analyze the current sales and
marketing capabilities of your organization and design
and implement a sales pipeline management process. To
proceed, you need an initial list of key stakeholders to
start your conversations. Which of the following
processes should you perform next to quickly generate an
initial list of stakeholders?
A. Identify Stakeholders
https://t.me/PrMaB
project.
C. Report table
D. Decision table
45. You are leading the business analysis activities for the
development of a new inventory management software
product. You have developed the ER model and now want
to develop a model that lists the data fields and attributes
https://t.me/PrMaB
of those fields for each data object in the ER model.
Which of the following models should you develop?
A. Use Case
B. Process Flow
C. Data Dictionary
D. Dataflow Diagram
B. Walkthrough
C. Fishbone diagram
D. Affinity diagram
https://t.me/PrMaB
D. Perform a cost/benefit analysis for the project.
B. Document review
C. Sensitivity diagram
D. Brainstorming
49. If you are creating a new WBS for your project, what
should you do to save time during the creation process?
A. Create a less detailed WBS.
B. Kanban board
C. Daily standup
https://t.me/PrMaB
D. Requirements management tool
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) - 3
Answer Key and Explanations
1. A - An interaction matrix is a lightweight version of a
traceability matrix that is used to figure out whether
requirements are sufficiently detailed or if any entities are
missing. In an interaction matrix, the rows are one type of
product information, typically in the form of use cases,
user stories, or process flows. The columns of the matrix
are the names of a different type of product information,
such as data entity, business rule, or user interface.
[The PMI Guide to Business Analysis, page 196]
[Analysis]
2. C - A walkthrough is a peer review in which the
author of the materials walks the peer reviewers through
the authored information.
[The PMI Guide to Business Analysis, page 172]
[Analysis]
3. A - During planning for analysis, the business analyst
will begin to think about which analysis techniques will be
best suited to meet stakeholder and project needs. The
other choices are the business needs analysis and planning
for elicitation considerations.
[Business Analysis for Practitioners: A Practice Guide,
page 54; The PMI Guide to Business Analysis, page 177]
[Planning]
4. A - The business analysis approach is simply the
method a business analyst uses when managing and
performing the business analysis activities on a project.
The business analysis approach is documented in the
business analysis plan.
[Business Analysis for Practitioners: A Practice Guide,
page 37; The PMI Guide to Business Analysis, page 127-
129] [Planning]
https://t.me/PrMaB
5. C - Grouping the stakeholders based on their power,
interest and influence is important for managing
stakeholders and their expectations. However, such
groupings do not offer any advantages to the requirements
elicitation process. A persona is a fictional character
created to represent an individual or group of stakeholders,
termed a user class. For an individual class, a persona can
include any number of descriptive features the team
decides are worth capturing; for example, goals,
behaviors, motivations, demographics, and high-level
requirements, etc. Creating personas will help you
understand stakeholder requirements better and remove
the complexity of overlapping requirements.
[The PMI Guide to Business Analysis, page 117]
[Planning]
6. D - Persona analysis is a technique that can be used to
analyze a class of users or process workers, to understand
their needs or product design and behavior requirements.
Note that the outcome of this analysis can be documented
in the stakeholder register by assigning each stakeholder to
their relevant class. Stakeholder register is a project
artifact and not a technique.
[The PMI Guide to Business Analysis, page 118]
[Planning]
7. C - Economists and financial analysts generally use
alternative approaches to measure financial benefits such
as IRR and NPV since the ROI measure doesn’t factor in
the time value of money.
[The PMI Guide to Business Analysis, page 90]
[Planning]
8. C - When the business analysis plan has been reviewed
by the key stakeholders and all concerns have been
resolved, the business analyst should take the next steps to
obtain approval on the plan.
[Business Analysis for Practitioners: A Practice Guide,
page 68; The PMI Guide to Business Analysis, page 127]
[Planning]
https://t.me/PrMaB
9. D - The display-action-response model is an interface
model and not a process model. The rest of the choices are
all process models.
[The PMI Guide to Business Analysis, page 185]
[Analysis]
10. B - CRUD, defined as create (C), read (R), update
(U), and delete (D), represents the operations that can be
applied to data or objects. CRUD matrices describe who
or what has permission to perform each of the CRUD
operations on elements, such as data or user interface
screens. The entity relationship diagram does not need to
change as no new data element has been introduced.
[The PMI Guide to Business Analysis, page 197]
[Analysis]
11. B - A Use Case is a process model. The rest of the
choices are not process models.
[The PMI Guide to Business Analysis, page 185]
[Analysis]
12. B - A business requirement describes the higher-level
needs of an organization such as business issues or
opportunities and reasons why an initiative has been
undertaken. These are typically analyzed and documented
prior to the project initiation. The rest of the project
artifacts are developed during the project lifecycle.
[The PMI Guide to Business Analysis, page 10] [Needs
Assessment]
13. A - Discounted cash flow analysis uses future free
cash flow projections and discounts them to arrive at a
present value estimate, which is used to evaluate the
potential for investment. The rest of the choices are
incorrect because Pareto analysis is carried out to identify
the most significant factors out of many; earned value
management is carried out to monitor and control cost of
an ongoing project; while the Monte Carlo is a simulation
technique used to analyze project risks. [PMBOK® Guide
6th edition, Page 473] [Needs Assessment]
https://t.me/PrMaB
14. A - The nominal group technique enhances
brainstorming with a voting process. This then allows the
most useful ideas to be prioritized and taken up for further
brainstorming. [PMBOK® Guide 6th edition, Page 144]
[Analysis]
15. C - Noise is anything that compromises the original
meaning of a message. It gets either introduced during the
transmission itself or during decoding (when the receiver
of the message doesn’t fully comprehend). [PMBOK®
Guide 6th edition, Page 371] [Analysis]
16. D - A decision table and decision tree are rule models
that show a series of decisions and the outcomes to which
the decisions lead. Decision trees and tables are often used
to model business rules. Both models can be used here,
however, decision trees are usually easier for stakeholders
to review than decision tables.
[The PMI Guide to Business Analysis, page 189]
[Analysis]
17. C - Since the project has significant uncertainties, this
can contribute to high rate of change and project
complexity. [PMBOK® Guide 6th edition, page 397]
[Planning]
18. D - Projects with adaptive life cycles are intended to
respond to high levels of change and require ongoing
stakeholder engagement. All other choices are predictive
life cycles which are designed to be plan driven rather
than being change driven. [PMBOK® Guide 6th edition,
Page 131] [Planning]
19. B - The business analysis plan developed by the
business analyst should be integrated into the overall
project management plan managed by the project
manager.
[Business Analysis for Practitioners: A Practice Guide,
page 38; The PMI Guide to Business Analysis, page 127-
129] [Planning]
https://t.me/PrMaB
20. C - This is example of majority; you reach a decision
when support is obtained from more than 50% of the
members of the group.
[The PMI Guide to Business Analysis, page 267]
[Traceability & Monitoring]
21. C - Before the project begins, the organization is
commonly referred to as being in the current state. The
desired result of the change derived by the project is
described as the future state. [PMBOK® Guide 6th
edition, Page 6] [Traceability & Monitoring]
22. B - A traceability matrix is a table that connects or
traces links between items. Most commonly, business
analysts use traceability matrices to trace requirements
backward to features and business objectives. A business
analyst can repurpose the traceability matrix to analyze
models to ensure that they are complete.
[The PMI Guide to Business Analysis, page 195]
[Analysis]
23. C - Delphi is a consensus-building technique.
Stakeholders participate in this technique anonymously.
For this exercise, you first need a questionnaire to elicit
ideas about the important points related to the conflict and
then use rounds of anonymous voting till common ground
is found.
[The PMI Guide to Business Analysis, page 265]
[Traceability & Monitoring]
24. A - The WBS represents all product and project work,
including the project management work. The total of the
work at the lowest levels should roll up to the higher
levels so that nothing is left out and no extra work is
performed. This is called the 100 percent rule. [PMBOK®
Guide 6th edition, Page 161] [Needs Assessment]
25. C - A point of diminishing returns is the point where
additional value that could be obtained from a solution
does not justify the additional effort needed to achieve
that value. In this case, Solution Evaluation gives teams
https://t.me/PrMaB
the ability to “end early” even if there is still additional
functionality that could be built, allowing funds to be
reallocated to work on higher-priority projects.
[The PMI Guide to Business Analysis, page 279]
[Evaluation]
26. B - A Kanban board provides a means to visualize the
flow of work, make impediments easily visible, and allow
flow to be managed by adjusting the work in process
limits.
[The PMI Guide to Business Analysis, page 233]
[Analysis]
27. C - Competitive analysis is a technique for obtaining
and analyzing information about an organization’s
external environment. Results from competitive analysis
may identify competitor strengths that impose threats or
may uncover an area of weakness an organization has in
comparison to its competition.
[The PMI Guide to Business Analysis, page 60] [Needs
Assessment]
28. D - A planning package is a work breakdown structure
component below the control account and above the work
package with known work content but without detailed
schedule activities. [PMBOK® Guide 6th edition, Page
161] [Planning]
29. A - The method where a single individual makes the
decision on behalf of a group is termed autocratic. Other
group decision-making techniques are unanimity
(everyone agrees on a course of action), majority (support
from more than 50% of members), and plurality (the
largest block decides even if a majority is not achieved).
[PMBOK® Guide 6th edition, Page 144] [Planning]
30. B - If the stakeholders are not sure about the accuracy
of some requirements, these need to be confirmed by
some other source. Reviewing the technical
documentation and verifying the integration requirements
is one way to confirm these requirements.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 172]
[Analysis]
31. D - The business case describes pertinent information
to determine whether the initiative is worth the required
investment. It is an authoritative source where expected
benefits have been stated.
[The PMI Guide to Business Analysis, page 281]
[Evaluation]
32. D - When a large number of stakeholders has been
identified, the next logical step in stakeholder analysis is
to group the stakeholders by common characteristics
which helps to streamline further analysis.
[Business Analysis for Practitioners: A Practice Guide,
page 39; The PMI Guide to Business Analysis, page 111]
[Planning]
33. B - The correct response is Voice of the Customer.
This is one of the non-proprietary approaches to quality
management. In this planning technique, the customer’s
requirements are exactly met in the finished product
during each phase of the project. [PMBOK® Guide 6th
edition, Pages 145, 726] [Needs Assessment]
34. C - The scope baseline is an output of the Create WBS
process. The other choices are either inputs or tools and
techniques of the process. [PMBOK® Guide 6th edition,
Page 156] [Planning]
35. C - When many stakeholders have been identified, the
next logical step in stakeholder analysis is to group the
stakeholders by common characteristics which helps to
streamline further analysis. The most relevant PMI Guide
to Business Analysis process is Conduct Stakeholder
Analysis.
[The PMI Guide to Business Analysis, page 115]
[Planning]
36. A - The problem at hand is unmanageable WIP. The
solution is to limit the WIP based on team capacity. A
Kanban board can be really helpful in setting this up. A
https://t.me/PrMaB
Kanban board provides a means to visualize the flow of
work, make impediments easily visible, and allow flow to
be managed by adjusting the work in process limits.
[The PMI Guide to Business Analysis, page 233]
[Analysis]
37. B - The business analyst does not decide which
features are built and which are not. The authority lies
with the stakeholders, and in adaptive projects, with the
product owner to approve or reject requirements. As the
business analyst, you are responsible for resolving this
conflict by negotiation with the people in the authority to
approve these requirements.
[The PMI Guide to Business Analysis, page 264]
[Traceability & Monitoring]
38. C - An approved requirement is a requirement that is
verified and validated and has been deemed an accurate
reflection of what the product development team should
build. You need to review the minutes to identify such
requirements.
[The PMI Guide to Business Analysis, page 388]
[Analysis]
39. A - Buy a feature is a type of collaborative game used
to enable a group of stakeholders to agree on prioritization
by giving each stakeholder an amount of pretend money
to buy their choice of features, splitting the money
received across features however desired.
[The PMI Guide to Business Analysis, page 391]
[Analysis]
40. B - The Facilitate Product Roadmap Development is
the process of supporting the development of a product
roadmap. None of the other choices is a valid PMI Guide
to Business Analysis process.
[The PMI Guide to Business Analysis, page 92] [Needs
Assessment]
41. A - Identify Stakeholders is the process of identifying
the individuals, groups, or organizations that may impact,
https://t.me/PrMaB
are impacted by, or are perceived to be impacted by the
area under assessment.
[The PMI Guide to Business Analysis, page 111]
[Planning]
42. B - A Use Case is a process model that uses textual
narrative to describe the system-user interactions to
achieve successful completion of a goal.
[The PMI Guide to Business Analysis, page 214]
[Analysis]
43. D - Story slicing is a technique to split epics or user
stories from a higher level to a lower level. The reason to
split stories is that sometimes stories are too big to
construct in an iteration.
[The PMI Guide to Business Analysis, page 214]
[Analysis]
44. D - A decision table is a rule model. None of the rest
of the choices are example of a rule model.
[The PMI Guide to Business Analysis, page 185]
[Analysis]
45. C - A data dictionary is a data model that lists the data
fields and attributes of those fields for a data object. The
data fields are additional details for the data objects in an
entity relationship diagram.
[The PMI Guide to Business Analysis, page 187]
[Analysis]
46. B - Fishbone diagram is a root cause analysis
technique and not a requirements confirmation technique.
Brainstorming and affinity diagrams are idea generation
techniques and are not applicable for confirming
requirements. A walkthrough is a peer review in which
the author of the materials walks the peers or stakeholders
through the authored information. A walkthrough may be
conducted to review the results of elicitation to obtain
confirmation that the results are accurate.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 172]
[Analysis]
47. D - If a 50% cost increase is expected, you need to re-
evaluate the project’s feasibility and reconfirm the validity
of the business case, even if the project is in the planning
stage. [PMBOK® Guide 6th edition, page 30] [Planning]
48. D - The feature mode can be used in combination with
brainstorming technique to help stakeholders identify
features by focusing on the groupings, similar to an
affinity diagram. The other techniques are not idea
generation techniques.
[The PMI Guide to Business Analysis, page 193]
[Analysis]
49. D - Creating the WBS is a very important process, but
often a previous WBS can be used as a template to save
time and avoid the risk of forgetting something important.
[PMBOK® Guide 6th edition, Page 157] [Planning]
50. D - Requirements management tools allow
requirements and other product information to be captured
and stored in a repository. These tools help maintain audit
trails and perform version control to assist with change
management. These tools also facilitate review and
approval processes thorough workflow functionality.
Requirements management tools catered to adaptive
projects may include additional functionality to create and
manage product and iteration backlogs, and produce
burndown charts.
[The PMI Guide to Business Analysis, page 260]
[Traceability & Monitoring]
https://t.me/PrMaB
PMI-PBA
Domain Area Test: Evaluation
Test Name: Domain Area Test: Evaluation
Total Questions: 20
Correct Answers Needed to Pass:
14 (70.00%)
Time Allowed: 30 Minutes
Test Description
This practice quiz specifically targets your knowledge of the
Evaluation PMI-PBA Domain area.
Test Questions
1. You have recently delivered a product to a customer
that took you over 18 months to build. The product was
built specifically for this customer under a contract with
specific product specifications. Testing missed a defect
and the product went into production causing customer
complaints. The product meets the specifications in the
contract as the contract only specified high-level product
requirements and didn’t specify design details. What
should you do first?
A. Notify the customer that the product is compliant
but you are willing to consider fixing this issue.
https://t.me/PrMaB
2. Regardless of the project lifecycle, scope and
magnitude, a business analyst performs a number of tasks
during the Solution Evaluation stage. All of the following
are tasks that are typically performed during this stage
EXCEPT:
A. Evaluating nonfunctional characteristics of the
solution.
B. Increase in productivity
D. Reduction in costs
https://t.me/PrMaB
B. Terminate the project and reallocate the remaining
funds to other higher-priority projects.
C. Traceability matrix
D. Sensitivity analysis
B. System design
C. Product backlog
D. Acceptance criteria
https://t.me/PrMaB
A. Context for evaluating solution performance.
https://t.me/PrMaB
B. The ROI value of 9% cannot demonstrate financial
performance.
https://t.me/PrMaB
D. Long-term evaluation focuses on evaluating the
product or solution during the penetration testing.
C. Need to be discontinued.
https://t.me/PrMaB
C. Add the defects to the scope statement.
B. PERT analysis
D. Growth-share matrix
https://t.me/PrMaB
C. By demonstrating performance against the feature
model
C. Analysis
D. Elicitation
https://t.me/PrMaB
velocity measure for the comparison. What is your
opinion regarding this?
A. Velocity is a good measure for this exercise, but
story points are a better measure.
https://t.me/PrMaB
PMI-PBA
Domain Area Test: Evaluation
Answer Key and Explanations
1. C - If there is a defect in the product, it is your
responsibility to fix it even if the product meets the
documented specifications. You must issue a change
request to fix this defect but prior to that, you need to
investigate the issue and determine the root cause. Only
once the root cause is known, you will be able to issue a
change request. [PMBOK® Guide 6th edition, page 292]
[Evaluation]
2. D - Collecting and analyzing functional and non-
functional solution requirements are part of the Elicitation
and Analysis stages. The rest of the tasks are all typically
performed during the Solution Evaluation stage.
[The PMI Guide to Business Analysis, page 278]
[Evaluation]
3. A - You will assess the risk management approach to
assess the efficiency of the project team and not the
product. The rest of the choices can all be used to
demonstrate value delivery by the system to the business.
[The PMI Guide to Business Analysis, page 282]
[Evaluation]
4. B - A point of diminishing returns is reached when
additional value that could be obtained from the solution
does not justify the additional effort needed to achieve that
value. At this point, it is recommended to “end early” and
reallocate remaining funds to other higher-priority
projects.
[The PMI Guide to Business Analysis, page 279]
[Evaluation]
5. B - A Product portfolio matrix, also known as a
growth-share matrix, is a market analysis quadrant
https://t.me/PrMaB
diagram used by organizations to qualitatively analyze
their products and product lines. One axis reflects market
growth (or demand for a product) while the other reflects
the market share of the organization. The matrix provides
a quick visual way to evaluate which products are meeting
or exceeding performance expectations in the marketplace.
[The PMI Guide to Business Analysis, page 283]
[Evaluation]
6. D - Solution evaluation activities are performed to
assess whether a solution has achieved the desired
business results. Solution evaluation consists of the work
done to analyze measurements obtained for the solution by
comparing the actual results of acceptance testing to the
expected or desired values, as defined by the acceptance
criteria.
[The PMI Guide to Business Analysis, page 278]
[Evaluation]
7. A - Business goals and objectives specify stated targets
that the busines is seeking to achieve. They provide the
context for evaluating solution performance because they
are a measurable description of the expected business
value.
[The PMI Guide to Business Analysis, page 281]
[Evaluation]
8. C - When measuring benefits is difficult or costly,
organizations could use next-best-alternative ways to
measure business value. Proxies for value might be used in
these situations. You need to support the auditor with her
assignments.
[The PMI Guide to Business Analysis, page 281]
[Evaluation]
9. A - The higher the ROI, the better. During the post-
implementation review we consider the result of an actual
versus expected cost-benefit analysis to assess the
business value of the solution. In this case, the product
could not meet its target financial performance.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 283]
[Evaluation]
10. C - Analyzing the results from surveys, focus groups,
or the results of exploratory testing of functionality are
examples of qualitative or coarsely quantitative evaluation
activities. Other evaluation activities involve obtaining
more precise quantitative measurements, such as directly
looking at data from a solution.
[The PMI Guide to Business Analysis, page 278]
[Evaluation]
11. A - Long-term evaluation focuses on evaluating the
business value delivered by the product or solution.
Product or solution evaluation during the acceptance
testing is the short-term focus. The other two choices are
irrelevant.
[The PMI Guide to Business Analysis, page 275]
[Evaluation]
12. A - A Product portfolio matrix, also known as a
growth-share matrix, is a market analysis quadrant
diagram used by organizations to qualitatively analyze
their products and product lines. One axis reflects market
growth while the other reflects the market share of the
organization. The matrix provides a quick visual way to
evaluate which products are meeting or exceeding
performance expectations in the marketplace. The
products that provide the most significant benefits to the
organization would be found in the upper left quadrant,
because these are the products where the organization has
a high market share in a market with a high growth rate.
Those in the upper right quadrant are regarded as having
good potential because, although they have a low market
share, they are in a market that is continuing to grow.
Those in the lower left quadrant, with a high market share
in a low growth market, are considered a dependable
income stream.
[The PMI Guide to Business Analysis, page 284]
[Evaluation]
https://t.me/PrMaB
13. B - Some of the benefits and value of the solution may
seem to be intangible, and therefore, not possible to
measure. For intangible benefits, it may be necessary to
define measurements that provide indirect evidence that
the benefits have been achieved.
[The PMI Guide to Business Analysis, page 279]
[Evaluation]
14. B - Adaptive projects do not have formal change
control processes. On such projects, all product defects
are added to the product backlog.
[The PMI Guide to Business Analysis, page 294]
[Evaluation]
15. A - Evaluation of an implemented solution may be
used to identify new or changed requirements, which may
lead to solution refinement or new solutions. Doing
nothing and ignoring the new and changed requirements is
not recommended. The other two choices are extremes.
[The PMI Guide to Business Analysis, page 279]
[Evaluation]
16. D - A Product portfolio matrix, also known as a
growth-share matrix, is a market analysis quadrant
diagram used by organizations to qualitatively analyze
their products and product lines. One axis reflects market
growth (or demand for a product) while the other reflects
the market share of the organization. The matrix provides
a quick visual way to evaluate which products are meeting
or exceeding performance expectations in the
marketplace.
[The PMI Guide to Business Analysis, page 283]
[Evaluation]
17. A - Acceptance criteria are concrete and demonstrable
conditions that must be met for the business stakeholders
or customers to accept the item.
[The PMI Guide to Business Analysis, page 292]
[Evaluation]
https://t.me/PrMaB
18. A - Solution Evaluation knowledge area involves tools
and techniques for validating a solution that is about to be
or has already been implemented to determine how well
the solution meets the business needs.
[The PMI Guide to Business Analysis, page 22]
[Evaluation]
19. B - Analyzing the results from surveys, focus groups,
or the results of exploratory testing of functionality are
examples of qualitative or coarsely quantitative evaluation
activities. Other evaluation activities involve obtaining
more precise quantitative measurements, such as directly
looking at data from a solution.
[The PMI Guide to Business Analysis, page 278]
[Evaluation]
20. D - Any measure can be used to compare performance
if the measure is used consistently on all projects.
However, the velocity measure is a relative measure.
Velocity is measured as story points that are delivered per
iteration on average. Since there is no universal standard
for measuring story points and different teams measure
user stories differently, similar effort user stories may
have different story points on two projects. Neither story
points nor velocity can be used for comparison.
[The PMI Guide to Business Analysis, pages 148, 213,
416] [Evaluation]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) - 4
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 4
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. You are leading the business analysis activities for a
software application development project. The project is
following an adaptive delivery approach. You are currently
planning the requirements management approach for the
project. Which of the following requirement lifecycle
states should you select for the project?
A. Defined, elaborated, verified, validated, and
prioritized
https://t.me/PrMaB
developed for your current organization. Most of the
processes being digitized by this initiative are currently
manual paper-based processes. You want to collect system
user interface requirements, but the stakeholders are
struggling to visualize the system. Which of the following
technique can help you elicit the required information?
A. Fishbone diagrams
B. Mainframes
C. Pareto charts
D. Wireframes
https://t.me/PrMaB
C. Efficient use of stakeholder time.
B. Plurality
C. Majority
D. Dictatorship
B. Ecosystem Map
https://t.me/PrMaB
C. Entity Relationship Diagram
D. State Diagram
B. Technical teams
C. Product owners
D. Project stakeholders
https://t.me/PrMaB
as a histogram. The leadership team is happy with your
analysis but has asked you to sort the histogram by
frequency of occurrence in a descending order. What type
of chart has been requested by the leadership team?
A. Onion diagram
B. Tornado diagram
C. Pareto chart
D. Scatter chart
B. DuPont analysis
D. PERT analysis
B. Process model
C. RACI model
https://t.me/PrMaB
D. SWOT model
B. Retrospectives
C. Backlog
D. User stories
B. Issue log
C. Risk register
D. Sprint backlog
B. Organizational Chart
C. Context Diagram
https://t.me/PrMaB
16. You are analyzing the requirements for a complex
ERP system development project. As your next business
analysis deliverable, you are required to develop a model
that visually shows the complex flow of system use cases.
The model is expected to show the user and system
interactions and mirror the textual district descriptions of
the system use cases. Which of the following diagrams
should you develop?
A. Context diagram
B. Activity diagram
C. Decision table
D. Kano diagram
https://t.me/PrMaB
D. Pay attention to this group and address their
concerns; stakeholders in this group may represent
those expected to adapt to the implemented solution
once it is built.
B. Definition of Ready
C. Definition of Done
D. Exit clause
https://t.me/PrMaB
identify key stakeholders. Which of the following
techniques can help you quickly identify some key
stakeholders?
A. Developing to-be process flow models
B. Document analysis
C. Surveys
D. Brainstorming
https://t.me/PrMaB
D. Adopting Agile practices
https://t.me/PrMaB
A. Prepare for Transition to Future-State
D. Determine Future-State
B. Ground rules
C. Glossary
D. Data dictionary
B. Sailboat
C. Feature model
https://t.me/PrMaB
carefully analyzed and developed. Which of the following
is a tool-supported validation that can now be used after
changes have been made to ensure that these changes did
not unintentionally alter the system in some other way?
A. Unit testing
B. Regression testing
C. Integration testing
D. Acceptance testing
29. You are auditing a product team and find out that the
team has missed several requirements during the design of
the solution. Although a traceability process was agreed
by the team, it was not adequately followed. Which of the
following could be the real cause of this?
A. The process was time-consuming and considered
wasteful to maintain.
B. Interrelationship diagram
C. Context diagram
https://t.me/PrMaB
D. Interface model
B. Capability Framework
C. SWOT Analysis
D. Observation
B. Business analyst
https://t.me/PrMaB
C. Development lead
D. Product owner
B. Use Case
C. Wireframe
D. Ecosystem Map
https://t.me/PrMaB
B. Fishbone diagram
C. Traceability matrix
D. Decision table
C. Context diagram
D. State diagram
https://t.me/PrMaB
organization’s PMO in collaboration with the impacted
department or business units. In this scenario, which of
the following statements could be true?
A. Each proposed transformation project needs to be
initiated by the PMO.
B. Costs
C. Customer
D. Scope
https://t.me/PrMaB
B. Observe the process and assess the suitability of the
requirements.
B. Corrective Action
C. Acceptance criteria
D. Defect Repair
https://t.me/PrMaB
44. You are leading a product team developing the new
website for your organization. Due to some technical
reasons, you believe one user story cannot be developed at
this stage and this user story needs to be terminated from
the current iteration. The product owner is willing to
terminate the story on technical grounds only if all
product team members believe the story cannot be
completed in the current iteration. What decision-making
style has been used by the product owner?
A. Plurality
B. Autocracy
C. Majority
D. Unanimity
B. Implementation dependency
https://t.me/PrMaB
C. Subsets
D. Value dependency
B. Business case
B. Alternative nodes
C. Checkpoints
D. Question points
B. Iteration zero
https://t.me/PrMaB
C. Once the first prototype is ready
D. First standup
B. Business case
C. Product roadmap
D. Capability model
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) - 4
Answer Key and Explanations
1. C - The requirements life cycle on predictive projects
represents the various phases or states through which a
requirement moves as it is defined, elaborated, verified,
validated and prioritized. When using an adaptive delivery
approach, the requirement states may be more implicit.
User stories may be states as not ready, ready, or done.
[The PMI Guide to Business Analysis, page 179]
[Analysis]
2. D - Wireframes are diagrams that represent a static
blueprint or schematic of a user interface used to identify
basic functionality. This will help you obtain UI
requirements from the stakeholders rather than discussing
abstract requirements.
[The PMI Guide to Business Analysis, page 168]
[Analysis]
3. D - You need to perform the Evaluate Acceptance
Results and Address Defects process. This process
compares the acceptance criteria and the actual results of
acceptance testing to provide recommendations on how to
deal with situations where aspects of a solution do not
meet the acceptance criteria specified for it.
[The PMI Guide to Business Analysis, page 291]
[Evaluation]
4. A - Stakeholders may have positive or negative
interests associated with the project which cannot be
influenced by performing the Determine Elicitation
Approach process. The rest of the statements are valid
benefits that can be realized.
[The PMI Guide to Business Analysis, page 156]
[Planning]
5. A - As the business analyst you are responsible for the
product and value delivery. A product that does not meet
https://t.me/PrMaB
expectations may have defects, which will necessitate
analysis of the cost to address the defects and the business
impact of addressing them or accepting them.
[The PMI Guide to Business Analysis, page 282]
[Evaluation]
6. B - This group decision-making technique is called
Plurality. Even if a majority (where more than 50% of the
members support the decision) is not achieved, the largest
block in the group makes the decision. [PMBOK® Guide
6th edition, Page 144] [Planning]
7. C - An entity relationship diagram, also called a
business data diagram, is a data model that shows the
business data objects or pieces of information of interest in
a product and the cardinality relationship between those
objects.
[The PMI Guide to Business Analysis, page 191]
[Analysis]
8. C - Contingency funds are used to handle cost
uncertainty due to unforeseen events during a project.
These funds are generally used for items that are likely to
occur but are not certain to occur. If the team has no prior
experience of similar projects, there is a risk that the team
has overestimated the reserves to compensate for their lack
of experience. [PMBOK® Guide 6th edition, Page 245]
[Planning]
9. B - Sequence diagram is a modeling technique that
describes how user or system processes interact with one
another across any involved users or systems and the order
in which the processes or steps are performed. Sequence
diagrams are most useful for communicating with
technical teams about the flow of information between
systems, the delegation of functionality to where it will be
performed, and the flow of control from step to step.
[The PMI Guide to Business Analysis, page 199]
[Analysis]
https://t.me/PrMaB
10. C - The leadership team has asked for a Pareto chart
which is a histogram that has been ordered by the
frequency of occurrence, that shows how many issues
were reported by each identified category.
[The PMI Guide to Business Analysis, page 403]
[Analysis]
11. A - Business analysts can conduct job analysis to
understand how particular roles are performed by
stakeholder. The rest of the choices are not stakeholder
analysis techniques.
[Business Analysis for Practitioners: A Practice Guide,
page 45; The PMI Guide to Business Analysis, page 115-
116] [Planning]
12. A - A decomposition mode is used to identify business
analysis tasks, activities, and deliverables by detailing out
the business analysis work. The rest of the tools cannot be
used to meet this objective.
[Business Analysis for Practitioners: A Practice Guide,
page 63; The PMI Guide to Business Analysis, page 127]
[Planning]
13. B - Recurring retrospectives regularly check on the
effectiveness of the quality process. They look for the root
cause of issues then suggest trials of new approaches to
improve quality. [PMBOK® Guide 6th edition, Page 276]
[Analysis]
14. A - Since the most effective and efficient way of
conveying information to and within a team is face-to-
face conversation, Agile teams report all work in process
issues during the daily standups.
[The PMI Guide to Business Analysis, page 144, 244]
[Traceability & Monitoring]
15. A - A user interface flow is an interface model that
displays specific user interfaces and commonly used
screens within a functional design and plots out how to
navigate between them. These can accompany process
https://t.me/PrMaB
flows or use cases to help visually show the users’
interactions within the system.
[The PMI Guide to Business Analysis, page 207]
[Analysis]
16. B - An activity diagram is a type of process model that
visually shows the complex flow of use cases. Activity
diagrams are similar to process flows in syntax; however,
they commonly show user and system interactions in one
diagram and mirror the textual descriptions of use cases.
[The PMI Guide to Business Analysis, page 387]
[Analysis]
17. C - Stakeholders who are expected to adapt to the
implemented solution once it is built are from the “low
influence/high impact” group. Stakeholders that are just
being monitored to ensure their behavior does not change
over time are from the “low influence/low impact” group.
Stakeholders who are decision-makers have “high
influence”, and the stakeholders who are a critical source
for requirements are “high impact”.
[The PMI Guide to Business Analysis, page 119-120]
[Planning]
18. A - Spending more time with non-supportive
stakeholders may uncover unspoken business needs,
requirements, training issues, resource constraints, or past
and current experiences important for the project team to
understand.
[Business Analysis for Practitioners: A Practice Guide,
page 40; The PMI Guide to Business Analysis, page 115-
116] [Planning]
19. B - The definition of ready is a series of conditions
that the entire team agrees to complete before a user story
is considered sufficiently understood so that work can
begin to construct it.
[The PMI Guide to Business Analysis, page 212]
[Analysis]
https://t.me/PrMaB
20. B - While all given techniques are valid approaches to
stakeholder identification, reviewing the organization
chart will help you quickly identify stakeholder groups or
individuals who have been impacted by the restructure.
The rest of the options will require more time to produce
the similar information.
[The PMI Guide to Business Analysis, page 113]
[Planning]
21. B - Brainstorming and surveys would require
interaction with stakeholders which, according to the
scenario, is not possible. Benchmarking with other similar
deployments will not give you your client’s data migration
requirements. In this scenario, document analysis, i.e.
analysis of the tender documents, will give you your
stakeholder requirements.
[Business Analysis for Practitioners: A Practice Guide,
page 44; The PMI Guide to Business Analysis, page 115-
116] [Planning]
22. C - Preparing the agenda for the elicitation event is an
example of preparation of elicitation materials. This is
neither an Agile practice nor document analysis.
Confirming elicitation is irrelevant to the context of this
question.
[The PMI Guide to Business Analysis, page 163]
[Analysis]
23. A - Adaptive lifecycles use prioritization techniques
for each iteration in order to determine the features to be
provided in the next release of the product. Projects using
a predictive or waterfall lifecycle will conduct
prioritization up-front before project execution.
[Business Analysis for Practitioners: A Practice Guide,
page 55; The PMI Guide to Business Analysis, page 127]
[Planning]
24. A - The backbone of a story map is the minimum set
of capabilities that absolutely must be in the first release
https://t.me/PrMaB
for the solution to serve its purpose. This set of
capabilities is called the minimum viable product (MVP).
[The PMI Guide to Business Analysis, page 204]
[Analysis]
25. C - Evaluating the current capabilities of the
organization is a significant focus during a current state
assessment. Documentation on the Assess Current State
process is most relevant to the given scenario.
[The PMI Guide to Business Analysis, page 64] [Needs
Assessment]
26. C - In business analysis, a glossary provides a list of
definitions for terms and acronyms about a product. A
glossary should be started as early as possible in portfolio,
program, or project analysis to support common language.
[The PMI Guide to Business Analysis, page 69] [Needs
Assessment]
27. C - Feature models are helpful to show how features
are grouped together and which features are sub-features
of other ones. Feature models are useful because they can
easily display many features across different levels on a
single page, which may represent an entire solution’s
feature set.
[The PMI Guide to Business Analysis, page 193]
[Analysis]
28. B - Automated regression testing is a tool-supported
validation used after changes have been made to a
software system to ensure that these changes did not
intentionally alter the system in some other way.
[The PMI Guide to Business Analysis, page 388]
[Analysis]
29. A - Each team member does not need to sign and
approve the process. If the team has agreed to it, they
should have stuck to it. It seems like that the team did not
have confidence in the process or that they thought it was
time-consuming and wasteful to maintain.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 254]
[Traceability & Monitoring]
30. B - An interrelationship diagram is a special type of
cause-and-effect diagram that depicts related causes and
effects for a given situation. Interrelationship diagrams
help to uncover the most significant causes and effects
involved in a situation.
[The PMI Guide to Business Analysis, page 399]
[Analysis]
31. D - Observation is an elicitation technique that
provides a direct way of eliciting information about how a
process is performed or a product is used, by viewing
individuals in their own environment performing their
jobs. This is known as a Gemba walk in lean terminology.
[The PMI Guide to Business Analysis, page 68] [Needs
Assessment]
32. A - Changes can occur in the project at any time. The
Perform Integrated Change Control process is valuable for
managing and tracking those changes. [PMBOK® Guide
6th edition, Page 115] [Traceability & Monitoring]
33. B - The business analysis responsibilities entail
choosing items for the iteration backlog that are
sufficiently elaborated upon and most important in terms
of delivering business value.
[The PMI Guide to Business Analysis, page 233]
[Analysis]
34. C - A wireframe is a representation of the expected
solution before it is built. A wireframe is a type of
prototype, specifically a mockup of a user interface
design, used to show what a screen should look like.
[The PMI Guide to Business Analysis, page 199]
[Analysis]
35. C - Determine Future State is the process of
determining gaps in existing capabilities and a set of
proposed changes necessary to attain a desired future state
that addresses the problem or opportunity under analysis.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 74] [Needs
Assessment]
36. C - A traceability matrix is a table that connects or
traces links between items. Most commonly, business
analysts use traceability matrices to trace requirements
backward to features and business objectives. A business
analyst can repurpose the traceability matrix to analyze
models to ensure that they are complete.
[The PMI Guide to Business Analysis, page 195]
[Analysis]
37. D - Since you are conducting acceptance testing, your
objective at this stage is neither to train the users nor elicit
the requirements. Acceptance testing is conducted to
ensure that the customer is happy with the product.
Verification and validation are often confused.
Verification is the evaluation of whether the product
complies with regulation, requirement, specification, or
imposed conditions. Validation is the assurance that the
product meets the needs of the customer.
[Business Analysis for Practitioners: A Practice Guide,
page 58; The PMI Guide to Business Analysis, page 127]
[Planning]
38. D - The state table and state diagram are data models
that show the valid states of an object and any allowed
transitions between those states. Objects can be business
data items or any piece of information of interest when
analyzing a solution.
[The PMI Guide to Business Analysis, page 203]
[Planning]
39. B - Given that a number of departments and business
units exits in the organization, this doesn’t look like a
highly projectized organization. The PMO should analyze
all the proposed initiatives and, based on the
organization’s capabilities and available resources, only
the viable transformation projects must be selected.
Further, each project work must include its specific
business analysis work. In this scenario the current state
https://t.me/PrMaB
assessment is frequently conducted by the Strategy and
Planning department, so it is most likely that the business
analyst on each transformation project might skip
performing this again and rather reuse the available
knowledge.
[The PMI Guide to Business Analysis, page 65] [Needs
Assessment]
40. C - Product box is an elicitation technique that uses
game play to focus on the features of a product that are
important to the customer. It divides the participants into
teams, asking each team to design a box that represents
how the product would be packaged.
[The PMI Guide to Business Analysis, page 166]
[Analysis]
41. B - Escalating the matter to the steering committee is
not necessary at this stage. However, you should keep
them informed. Since several elicitation workshops have
been arranged already, and these requirements have been
approved, the only way to test the suitability of these
requirements is to observe the process being performed
firsthand.
[The PMI Guide to Business Analysis, page 168]
[Analysis]
42. B - The higher the NPV, then greater the amount of
value an option is expected to provide. Hence, if the
organization has to choose one between these two
projects, project A must be selected. Note that NPV value
is not the cost to execute the projects; it is the future value
of expected benefits expressed in the value that those
benefits have at the time of investment. The organization’s
capital budget is irrelevant to this question.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
43. C - Direct and Manage Project Work implements
approved change requests. This includes corrective action,
https://t.me/PrMaB
preventive action and defect repair. [PMBOK® Guide 6th
edition, Page 93] [Analysis]
44. D - This is example of unanimity; you reach a
decision by everyone agreeing on a single course of
action.
[The PMI Guide to Business Analysis, page 267]
[Traceability & Monitoring]
45. B - The process of developing a business analysis
work plan is: Identify the deliverables -> Determine the
business analysis tasks and activities -> Determine the
timing and sequencing of tasks ->Determine the roles and
responsibilities -> Identify the resources -> Estimate the
work.
[Business Analysis for Practitioners: A Practice Guide,
page 61-65; The PMI Guide to Business Analysis, page
111] [Planning]
46. B - This is an example of an implementation
dependency; some requirements are dependent on the
implementation of other requirements before they can be
implemented.
[The PMI Guide to Business Analysis, page 259]
[Traceability & Monitoring]
47. D - The two inputs to the Confirm Elicitation Results
process are elicitation preparation materials and
unconfirmed elicitation results.
[The PMI Guide to Business Analysis, page 170]
[Analysis]
48. A - The decision points are known as Decision nodes.
The decision tree incorporates the cost of each available
choice, the possibilities of each of the available choices,
and possible scenarios. It shows how to make a decision
among alternative capital strategies (decision nodes) when
the environment is not known with certainty. [PMBOK®
Guide 6th edition, Page 435] [Planning]
49. B - In adaptive projects, elicitation of high-level
product information occurs within iteration zero.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 163]
[Analysis]
50. B - Much of the analysis completed during Needs
Assessment is used in the development of a business case.
[The PMI Guide to Business Analysis, page 98] [Needs
Assessment]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) – 5
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 5
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. You will soon be leading a complex project. Project
communication is critical to the success of the project;
specifically, all team members need to be kept updated on
project progress. Which of the following approaches will
produce the best results?
A. Discuss progress during sprint planning events.
https://t.me/PrMaB
of potential system requirements and aligned these with
the approved business requirements. What should you do
next?
A. Pass these requirements on to the development
team.
https://t.me/PrMaB
A. Demonstration
B. Spike
C. Planning poker
D. Retrospective
B. Burndown chart
C. Product roadmap
D. Sprint backlog
B. Scrum master
C. Project sponsor
D. Agile coach
https://t.me/PrMaB
information will then be consolidated at the respective
managers, senior managers and vice presidents’ levels,
where reports will be updated at each level and pushed
upwards. After a detailed analysis, you found out that the
product is not able to provide its intended business value
because the factory workers are unable to key-in their
daily progress due to the nature of their jobs and
availability of the supporting technologies. As a result,
some of these guys are reporting on a weekly, and at times,
on a bi-weekly basis. You do not think that this situation
can be improved, and this limitation should have been
seriously considered prior to the product implementation.
Which of the following most likely happened on this
project?
A. The implementation team lacked the skills to
successfully roll out the product.
B. Spider web
C. Tornado diagram
https://t.me/PrMaB
On the other hand, projects with adaptive lifecycles use:
A. Backlogs
B. Scope statement
C. WBS dictionary
D. WBS
B. Data Dictionary
C. Ecosystem Map
B. Accountable
C. Responsible
https://t.me/PrMaB
D. Consult
13. Which of the following models will help you test your
user stories regarding their suitability and completeness
prior to assigning them to an upcoming sprint?
A. Estimation poker
B. Kanban
C. INVEST
D. Kano analysis
B. Alternatives analysis
https://t.me/PrMaB
D. Progressive elaboration
B. Bottom-up estimation
C. Top-down estimation
D. Parametric estimation
B. Decode
https://t.me/PrMaB
C. Noise
D. Medium
B. Leading by example
https://t.me/PrMaB
B. Stakeholder Engagement
C. Needs Assessment
D. Analysis
B. Indifferent
C. Basic
D. Reverse
B. Project activities
C. Portfolio activities
https://t.me/PrMaB
A. Determine business value -> spot examples ->
inject features
B. Risk
C. Assumption
D. Product requirement
B. Process mapping
D. Backlog refinement
https://t.me/PrMaB
into multiple teams and provides a plain box and art
supplies to each team. Each team is then asked to decorate
the box, marketing the product in a manner that would
entice a customer to purchase it. Which technique is this?
A. Pareto
B. Product box
C. Context diagram
D. Fishbone
B. Facilitated workshops
C. Brainstorming
https://t.me/PrMaB
D. Focus groups
B. Process Flow
C. QFD
D. PERT
B. SWOT Analysis
C. PESTLE Analysis
D. PERT Analysis
https://t.me/PrMaB
that links product requirements from their origin to the
deliverables that satisfy them. This grid is an example of:
A. Product roadmap
C. Traceability matrix
D. Feature model
https://t.me/PrMaB
B. Design and develop a minimally viable product.
https://t.me/PrMaB
36. A product team is halfway through the development
of a product. A new technology has recently become
available in the market that can enhance the product.
However, incorporating this technology at this stage
means significant rework. The product team believes that
effort spent on the development of the deliverables that
would require rework is sunk cost and should not be a
factor in making the right decision at this stage. Before
you make any decision, you want to analyze the level of
support from the stakeholders who would support such a
decision against the level of resistance by the stakeholder
who would not tolerate any delay on the project. Which of
the following tools can help you conduct this assessment?
A. Force field analysis
B. Alternatives analysis
D. Feasibility analysis
https://t.me/PrMaB
B. Adopt an iterative life cycle.
B. Display-action-response model
C. Report table
D. Feature model
https://t.me/PrMaB
40. During which of the following Agile events does an
Agile team meet to discuss the ongoing work plan and
make any adjustment to the work plan as required and
address any impediments to work?
A. Daily Scrum
B. Retrospectives
C. Spikes
D. Planning poker
B. Time-boxing
C. User epics
D. User stories
https://t.me/PrMaB
A. Make necessary adjustments to the business
analysis processes.
B. Discount rate
D. Interest rate
https://t.me/PrMaB
45. Your firm has recently acquired a project management
tool that hasn’t been doing well in the market. You have
been asked to analyze its features and study its major
facets to determine the possible changes or upgrades to
the product to enable its success. What have you been
asked to perform?
A. Opportunity analysis
https://t.me/PrMaB
which are documented in the agreement with the
contractor. When you escalate this issue to the contractor,
they tell you that a slump test is not a true measure of
concrete strength as it only measures the wetness of
concrete and not the concrete strength. They are insisting
that you instead conduct a compressive cube test to
measure the concrete strength. You know for a fact that a
cube test provides a better idea about all the
characteristics of concrete and through this test you can
better judge whether concreting has been done properly or
not. What should you do?
A. Reject the deliverables as they do not conform to
the agreed standard.
B. Ishikawa diagram
C. Interrelationship diagram
D. Five-Whys
https://t.me/PrMaB
49. You have been asked to conduct a post-
implementation evaluation of a system. The product
owner has asked you to quantitatively evaluate the
system. How would you conduct a quantitative evaluation
of the system?
A. By analyzing the result from surveys
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) – 5
Answer Key and Explanations
1. B - The most effective method would be to use a
Kanban board as that would provide a continuous means
to visually communicate project status to the team.
[The PMI Guide to Business Analysis, page 233]
[Planning]
2. D - You cannot pass these requirements on to the
development team prior to having these reviewed and
approved by the relevant stakeholders. As the next step,
you should schedule a workshop with the stakeholders to
have these requirements reviewed.
[The PMI Guide to Business Analysis, page 167]
[Analysis]
3. A - The PMI Guide to Business Analysis recommends
the Identify Problem or Opportunity -> Assess Current
State -> Determine Future State sequence. It is clear that
you have decided to skip the Assess Current State process.
In situations where the current state has recently been
assessed in sufficient detail, it is sometimes possible to use
that knowledge as the basis for defining the future-state
without conducting yet another current state assessment.
[The PMI Guide to Business Analysis, pages 64, 65]
[Needs Assessment]
4. A - In iteration-based Agile, the team demonstrates all
completed work items at the end of the iteration.
[The PMI Guide to Business Analysis, page 294]
[Planning]
5. C - Product roadmaps are used internally, but they also
provide valuable information to customers, vendors, and
others who are external to the organization. However, the
product backlog, the sprint backlog and the associated
burndown charts are always kept internal.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 94] [Needs
Assessment]
6. B - On Scrum projects, it’s the responsibility of the
Scrum master to help the team remove impediments from
the project.
[The PMI Guide to Business Analysis, page 51]
[Planning]
7. D - This seems like a feasibility issue. It is likely that
this was missed otherwise the operational feasibility of the
system would have been thoroughly considered. There is
no information provided to ascertain that any of the other
choices is true.
[The PMI Guide to Business Analysis, page 86] [Needs
Assessment]
8. B - The spider web is an elicitation technique used to
discover unknown relationships between the product being
analyzed and other products. Entity relationship diagrams
are used to design databases and not to discover
interrelationships. Similarly, tornado and Pareto diagrams
are tools used in other contexts.
[The PMI Guide to Business Analysis, page 166]
[Analysis]
9. A - In projects with adaptive life cycles, the overall
scope of the project will be decomposed into a set of
requirements and work to be performed, referred to as a
product backlog. [PMBOK® Guide 6th edition, Page 131]
[Planning]
10. B - Ecosystem maps and context diagrams are
typically developed early in a product life cycle; these
models are developed to show the high-level scope of the
product. Data dictionaries are often created after other
data models have first been used to identify the data
objects and when those objects need more details
specified. The data dictionary details the data objects in an
entity relationship diagram.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 187]
[Analysis]
11. C - RACI (Responsible, Accountable, Consult,
Inform) analysis is performed in business analysis when
determining roles and responsibilities for the business
analysis effort. The responsible role for a task indicates
the person who will perform that task.
[The PMI Guide to Business Analysis, page 118]
[Planning]
12. A - “Criteria of declaring a user story as understood
by the team” is the “definition of ready” for the user
stories, not the “definition of done”. The definition of
ready is a series of conditions that the entire team agrees
to complete before a user story is considered sufficiently
understood so that work can being to construct it. The rest
of the choices are all valid items included in the definition
of done.
[The PMI Guide to Business Analysis, pages 212, 219]
[Analysis]
13. C - The term INVEST describes the characteristics
that user stories need to demonstrate to be considered
“good” and “ready” for development in adaptive
approaches. INVEST is an acronym for independent,
negotiable, valuable, estimable, small, and testable.
[The PMI Guide to Business Analysis, page 223]
[Analysis]
14. D - This is an example of progressive elaboration.
Progressive elaboration allows a project management
team to define work and manage it to a greater level of
detail as the project evolves. [PMBOK® Guide, 6th
edition, Pages 131, 158] [Planning]
15. A - The definition of done (DoD) is a series of
conditions that the entire team agrees to complete before
an item is considered sufficiently developed to be
accepted by the business stakeholders.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 219]
[Analysis]
16. A - Relative estimation is a technique that creates
estimates that are derived from performing a comparison
against a similar body of work rather than estimating
based on absolute units of cost or time. The rest of the
choices are more thorough estimation techniques that are
based on absolute units of cost or time.
[The PMI Guide to Business Analysis, page 409]
[Analysis]
17. C - In a sender-receiver model, the key components
include: Encoding of thoughts or ideas, a message as the
output of encoding, a medium to convey the message, and
decoding of the message back into meaningful thoughts or
ideas. Anything that interferes with the transmission and
understanding of the message is termed noise (such as
distance, for example). [PMBOK® Guide 6th edition,
Page 372] [Needs Assessment]
18. A - The sailboat method is similar to the speedboat
method but uses sails to encourage the recognition of
positive influences rather than anchors to identify the
negative ones.
[The PMI Guide to Business Analysis, page 166]
[Analysis]
19. C - Withdrawing from a conflict may temporarily
alleviate the conflict, but it cannot influence the team
members. The other choices are effective team
influencing techniques. [PMBOK® Guide 6th edition,
Page 349] [Analysis]
20. B - The processes in the Stakeholder Engagement
Knowledge Area are used throughout all business analysis
efforts and interact with all other Business Analysis
Knowledge Areas.
[The PMI Guide to Business Analysis, pages 22, 23]
[Needs Assessment]
https://t.me/PrMaB
21. C - The basic features of a Kano model are the ones
that provide little satisfaction to the customers, but if not
available, will cause significant dissatisfaction to them.
[The PMI Guide to Business Analysis, page 80] [Needs
Assessment]
22. A - Post-implementation evaluation of solution
performance occurs after a solution has been released.
Therefore, it is more likely that the evaluation of solution
performance will occur during program activities rather
than project activities. In case a project is directly
managed under a portfolio, rather than a program, the
solution evaluation will be part of portfolio activities.
[The PMI Guide to Business Analysis, page 281]
[Evaluation]
23. B - The typical three-step approach followed by the
feature injection method is: Determine business value ->
inject features -> spot examples.
[The PMI Guide to Business Analysis, page 89] [Needs
Assessment]
24. A - The scenario has given an elicitation constraint as
the elicitation periods have been imposed and this affects
elicitation sequencing. Since this limitation is already
imposed, this cannot be a risk as risks are uncertain
events. Further this is neither an assumption nor a product
requirement.
[Business Analysis for Practitioners: A Practice Guide,
page 54; The PMI Guide to Business Analysis, page 156]
[Planning]
25. D - Backlog refinement refers to the progressive
elaboration of project requirements and the ongoing
activity in which the team collaboratively reviews,
updates, and writes requirements to satisfy the needs of
the customer request.
[The PMI Guide to Business Analysis, pages 214, 388]
[Planning]
https://t.me/PrMaB
26. B - Product box is an elicitation technique that uses
game play to focus on the features of a product that are
important to the customer. It divides the participants into
teams, asking each team to design a box that represents
how the product would be packaged.
[The PMI Guide to Business Analysis, page 166]
[Analysis]
27. D - Since this is an Agile project, you don’t need a
formal change request to incorporate the change. There
has been a change in scope, so the product backlog must
be updated and reprioritized.
[The PMI Guide to Business Analysis, page 133]
[Planning]
28. A - From the given choices, only interviews would
allow you to maintain the privacy and confidentiality of
the stakeholders. The privacy and confidentiality of
individual interviews may reveal considerations that
might not otherwise be expressed in a facilitated
workshop or focus group.
[The PMI Guide to Business Analysis, page 283]
[Evaluation]
29. A - Some common techniques for determining
priority are MoSCoW, multivoting, timeboxing, and
weighted ranking.
[Business Analysis for Practitioners: A Practice Guide,
page 56; The PMI Guide to Business Analysis, page 127]
[Planning]
30. B - Porter’s Five Forces and PESTLE analysis are
used to analyze the competitive environment within an
industry, while a SWOT analysis tends to look more
deeply within an organization to analyze its internal
potential. SWOT analysis is used to assess organization’s
strategy, goals, and objectives and to facilitate discussions
with stakeholders when discussing high-level and
important aspects of an organization.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 72] [Needs
Assessment]
31. C - A traceability matrix is a grid that links product
requirements from their origin to the deliverables that
satisfy them. The rest of the tools do not show this
traceability.
[The PMI Guide to Business Analysis, page 261]
[Traceability & Monitoring]
32. A - As the next logical step, after developing or
refining the stakeholder list, the business analyst analyzes
the characteristics for the stakeholders identified. The rest
of the choices and stakeholder identification do not have
any scheduling dependencies.
[Business Analysis for Practitioners: A Practice Guide,
page 40; The PMI Guide to Business Analysis, page 115]
[Planning]
33. A - The issue here is over the ability of the
stakeholders to provide detailed requirements during
brainstorming sessions. Stakeholders who do not have
prior experience in using similar systems often struggle to
articulate their requirements. In such situations,
prototyping is often used to elicit and validate stakeholder
requirements. Hiring an SME or a BA won’t resolve the
problem at hand as the scenario doesn’t tell us that the
team doesn’t have required elicitation and management
skills. [PMBOK® Guide 6th edition, page 147] [Analysis]
34. B - You cannot just produce the product requirements
on your own; these need to come from the stakeholders. If
you already have a scheduled event, you need to prepare
for it. Sending the agenda alone is not enough; you need
to schedule resources and prepare necessary materials for
the event.
[The PMI Guide to Business Analysis, page 155]
[Analysis]
35. A - Observation is an elicitation technique that
provides a direct way of obtaining information about how
https://t.me/PrMaB
a process is performed. Observation can help uncover
information that stakeholders are not able or willing to
provide. The main drawback of the technique is that
people may act differently when they are being observed.
[The PMI Guide to Business Analysis, page 168]
[Analysis]
36. A - Force field analysis is a decision-making
technique that can be used to help product teams analyze
whether there is sufficient support to pursue a change.
Using this model, a team identifies the forces for or
against a proposed change.
[The PMI Guide to Business Analysis, page 266]
[Traceability & Monitoring]
37. D - In a predictive life cycle, the project planning is
completed in the early phases of the project. Although the
use of the waterfall life cycle is mandated by the client,
the project manager can still customize the approach to
obtain benefits offered by the adaptive approaches. In this
case, dividing the project into multiple phases and
organizing phase gates with the customer can help achieve
this. [PMBOK® Guide 6th edition, Pages 19, 21] [Needs
Assessment]
38. D - A feature model is a scope mode and not an
interface model. The rest of the choices are all interface
models.
[The PMI Guide to Business Analysis, page 185]
[Analysis]
39. A - An ecosystem map is a scope model that shows all
the relevant systems, the relationships between the
systems, and optionally, any data objects passed between
them.
[The PMI Guide to Business Analysis, page 190]
[Analysis]
40. A - Daily Scrums are brief, daily collaboration
meetings in which the team reviews progress from the
previous day, declares intentions for the current day, and
https://t.me/PrMaB
highlights any obstacles encountered or anticipated. Also
known as daily standups.
[The PMI Guide to Business Analysis, page 144, 244]
[Planning]
41. B - Time-boxed periods are durations during which
the team works steadily toward completion of a goal.
Time-boxing helps to minimize scope creep as it forces
the teams to process essential features first, then other
features when time permits. [PMBOK® Guide 6th
edition, Page 182] [Needs Assessment]
42. A - Consider the cultural diversity that exists among
the stakeholders and make necessary adjustments to the
business analysis process to ensure these differences are
considered. As a seasoned business analyst, you should
rule out the other given choices.
[Business Analysis for Practitioners: A Practice Guide,
page 42; The PMI Guide to Business Analysis, page 115-
116] [Planning]
43. A - Economists and financial analysts generally use
alternative approaches to measure financial benefits such
as IRR and NPV since the accounting rate of return
measure doesn’t factor in the time value of money.
[The PMI Guide to Business Analysis, page 90]
[Planning]
44. A - Partner features are the ones that are not
considered mission critical, but if provided, they would
enable the organization to differentiate itself in the
market. As a result, an organization will look externally
for a partner company to provide these features but will
not invest in these features itself.
[The PMI Guide to Business Analysis, page 82] [Needs
Assessment]
45. A - Once a situation is discovered, it needs to be
analyzed before being acted upon. Some analysis piece
needs to be carried out prior to collecting functional or
non-functional requirements for the future product
https://t.me/PrMaB
upgrades. What you have been asked to perform is
analyzing the opportunity to make the recently acquired
product a success.
[The PMI Guide to Business Analysis, pages 70] [Needs
Assessment]
46. A - The CEO’s engagement of the consultant for a
process improvement job identified by the executive
leadership team indicates that the Identify Problem or
Opportunity process was completed in some shape or
form. The next step is to assess the current state which
seems to be ignored by the hired consultant. You need to
communicate your concern to the relevant authority rather
than conducting this step yourself and sharing the
outcomes with the consultant. The other two choices are
extreme.
[The PMI Guide to Business Analysis, page 63] [Analysis]
47. A - You have the right to reject the deliverables if they
fail to conform to the agreed standards. Whether a cube
test is better and more accurate than a slump test is
irrelevant. If the deliverables are of low quality and below
the agreed standards, these need to be rejected.
[PMBOK® Guide 6th edition, page 498] [For those
interested in what slump and cube tests are: Wetness of
concrete is measured by the slump test and this
measurement is directly related to the concrete’s
compressive strength. Compressive strength of concrete
by cube test provides a better idea about all the
characteristics of concrete. By this single test one judges
whether concreting has been done properly or not.]
[Traceability & Monitoring]
48. D - The fishbone diagram (also known as Ishikawa
diagram) and interrelationship diagrams are both root
cause analysis techniques. However, these are not
sufficient for understanding all root causes. The Five-
Whys technique thoroughly analyzes a problem’s causes.
[The PMI Guide to Business Analysis, pages 70-72]
[Needs Assessment]
https://t.me/PrMaB
49. B - Analyzing the results from surveys, focus groups,
or the results of exploratory testing of functionality are
examples of qualitative or coarsely quantitative evaluation
activities. Other evaluation activities involve obtaining
more precise quantitative measurements, such as directly
looking at data from a solution.
[The PMI Guide to Business Analysis, page 278]
[Evaluation]
50. C - The RACI classifications are as follows: R – Role
or person “responsible” for performing the task; A – Role
or person “accountable” for the completion/quality of the
task. C – Role or person who may be “consulted” to
obtain information to complete the task. I – Role or
person who is in some manner impacted by the task and
hence needs to be “informed”. In this scenario, the
purchase order check is accountable for the task since she
is providing quality assurance.
[The PMI Guide to Business Analysis, page 118]
[Planning]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) - 6
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 6
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. You have recently initiated an organizational process
transformation project. Due the low risk tolerance levels
of the key stakeholder, you need to pay special attention to
project costs. Which of the following structures helps
track project costs and can align with the organization’s
accounting system?
A. Organizational breakdown structure (OBS)
https://t.me/PrMaB
within existing document repositories, such as process
maps and procedure reports, so that the total amount of
elicitation time needed with the stakeholder can be
reduced. Which elicitation technique are you considering?
A. Focus groups
B. Elicitation planning
C. Document analysis
D. Brainstorming
B. Histogram
C. Context diagram
D. Ishikawa diagram
https://t.me/PrMaB
5. Which of the following Agile concepts implies
“smallest possible deliverable that meets customer
requirements”?
A. Theme
B. Epic
D. User story
https://t.me/PrMaB
D. Conduct a Kano analysis.
B. Gap Analysis
D. Benchmarking
C. Agendas
https://t.me/PrMaB
system before building it. Which of the following
techniques would you use?
A. Observation
B. Interviews
C. Facilitate workshop
D. Prototyping
B. Subsets
C. Implementation dependency
D. Value dependency
C. Stakeholders requirements
https://t.me/PrMaB
Which of the following is one of the reasons why
elicitation results must be confirmed?
A. Elicitation results must be confirmed if this is not a
time-consuming activity.
B. Focus Groups
C. Surveys
D. Prototypes
https://t.me/PrMaB
B. Power/influence grid
C. Influence/impact grid
D. Power/interest grid
B. Agile team
C. Scrum master
D. Product owner
https://t.me/PrMaB
agreement, the team is considering decomposing the
scope into fixed-price micro-deliverables. Which of the
following can be used as micro-deliverables for the
agreement?
A. Team charter
B. User stories
C. Kanban board
B. Active listening
C. Decision-making
D. Problem-solving
https://t.me/PrMaB
C. During the Perform Quantitative Risk Analysis
process
B. Product scope
C. Feasibility study
https://t.me/PrMaB
B. Demonstration
C. Retrospective
D. Iteration planning
B. Acceptance criteria
C. Deliverables
D. Scope description
B. An adaptive lifecycle
C. An incremental lifecycle
D. A predictive lifecycle
https://t.me/PrMaB
defects into categories and now want to conduct a detailed
root-cause analysis. Which of the following techniques
will help you conduct this analysis?
A. Five Whys
B. SIPOC
C. Process Flow
27. The chief financial officer of your firm has asked your
team to develop an online billing and payment system for
the organization’s customers. You are required to present
your product roadmap to the chief financial officer before
she could approve the funding. Which of the following
techniques should you use to develop your product
roadmap?
A. Kano analysis
B. Surveys
C. Facilitated workshop
D. Observation
https://t.me/PrMaB
D. Identifying alternatives to the proposed solution
and conducting cost benefit analysis.
C. RACI matrix
D. Conduct Elicitation
https://t.me/PrMaB
A. Project A
B. Project D
C. Project B
D. Project C
B. Affinity diagrams
C. Control charts
D. Scatter chart
https://t.me/PrMaB
view of resource requirements is available. You are
currently working with your project management team to
develop the project’s WBS. The WBS structure can be
created in a number of forms except which of the
following?
A. Using subcomponents, which may be developed by
organizations outside the project team, such as
contracted work
https://t.me/PrMaB
A. Prototype
D. Data Dictionary
B. Pareto chart
C. Fishbone diagram
D. Control chart
B. Burndown charts
C. Feasibility study
https://t.me/PrMaB
workflow, you need to obtain feedback of key
stakeholders on your findings. Which of the following is
the most appropriate technique to be used to obtain this
feedback?
A. Interviews
B. Document analysis
C. Questionnaires
D. Observation
B. Feature model
C. Traceability matrix
D. Gantt chart
B. Iterative
C. Incremental
https://t.me/PrMaB
D. Predictive
B. Growth-share matrix
C. Fishbone diagram
D. MoSCoW chart
D. Product backlog
https://t.me/PrMaB
45. You are leading a complex project with a huge list of
features. Due to schedule and budget constraints, you
might not be able to develop all of the features. Which of
the following would help in developing the feature set that
maximizes business value?
A. Feasibility analysis
C. Analysis of variance
D. MoSCoW analysis
https://t.me/PrMaB
provide product requirements but may serve as
product champions.
B. Ishikawa Diagram
C. Control Chart
D. Inspection
C. Process Flow
https://t.me/PrMaB
C. The total cash inflow in present value terms will be
$100,000.
B. Carrot diagram
C. Ginger diagram
D. Onion diagram
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) - 6
Answer Key and Explanations
1. C - The Work Breakdown Structure (WBS) provides
the framework for the cost management plan. The WBS
contains control accounts, which link directly to the
performing organization’s accounting system. [PMBOK®
Guide 6th edition, Page 239] [Planning]
2. C - This is an example of document analysis which
can be used to obtain information that is readily available
within existing document repositories.
[The PMI Guide to Business Analysis, page 162]
[Analysis]
3. B - It is true that predictive projects provide a better
case for formal traceability than adaptive projects. It is not
true that you would never have formal traceability in
adaptive projects. Other factors such as, project
environment, organizational standards or the regulatory
framework can dictate formal traceability.
[The PMI Guide to Business Analysis, page 259]
[Traceability & Monitoring]
4. C - A context diagram is a graphical technique that
visually depicts the product scope by showing a business
system and how other systems interact with it. The other
choices are graphical techniques designed to achieve other
objectives. [PMBOK® Guide 6th edition, Page 146]
[Planning]
5. C - A minimum viable product (MVP) is a product or
a project outcome that contains sufficient features to
satisfy project stakeholders.
[The PMI Guide to Business Analysis, page 204]
[Planning]
6. C - The requirements change process is performed
differently depending on the selected project lifecycle. For
a project following a predictive life cycle, the project team
https://t.me/PrMaB
may use a formal change control process, where a project
following an adaptive life cycle may not. A hybrid project
may have a formal or informal change control process that
should be document in its project management plan.
[Business Analysis for Practitioners: A Practice Guide,
page 58; The PMI Guide to Business Analysis, page 269]
[Planning]
7. C - A readiness assessment is an evaluation of how
well an organization is prepared for a change. It provides
an evaluation of the ability of an organization to transition
to the future state enabled by the solution.
[The PMI Guide to Business Analysis, page 297]
[Evaluation]
8. D - Benchmarking is a comparison of an organization’s
practices, processes, and measurements or results against
established standards or against what is achieved by a
“best in class” organization within its industry or across
industries.
[The PMI Guide to Business Analysis, page 60] [Needs
Assessment]
9. B - Agendas, meeting minutes, parking lot lists, and
some types of models, although necessary to organize
work and perform effectively, are not considered business
analysis deliverables. These items are often called work
products and are created in order to perform the work but
are not a promised deliverable that will be tracked and
managed.
[Business Analysis for Practitioners: A Practice Guide,
page 62; The PMI Guide to Business Analysis, page 127]
[Planning]
10. D - Prototyping is a method of obtaining early
feedback on requirements by providing a model of the
expected solution before building it. None of the other
given choices are techniques that benefit from building a
model.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 168]
[Analysis]
11. A - Discretionary dependency is a concept in project
scheduling, and it exists between project tasks and not
product requirements. The rest of the choices are all valid
product requirement relationship types.
[The PMI Guide to Business Analysis, page 259]
[Traceability & Monitoring]
12. A - The stakeholder register is the only output of the
Identify Stakeholders process. At this stage it is usually
early to analyze the related risks, requirements and the
engagement strategies; these areas are explored more
during the Conduct Stakeholder Analysis process.
[The PMI Guide to Business Analysis, Page 111]
[Planning]
13. B - Confirm Elicitation Results is the process of
performing follow-up activities on the elicitation results.
If this process is not performed correctly, a significant risk
of rework gets introduced to the project. One of the
reasons for performing this process is to refine and correct
the elicitation results.
[The PMI Guide to Business Analysis, page 171]
[Analysis]
14. A - Both product and project requirements are
gathered from stakeholders during the Collect
Requirements process. This effort is undertaken during
project planning. Focus groups, surveys, and prototypes
are some of the tools used to define and analyze
requirements. Decomposition is used only to break down
the work and not to gather requirements. Therefore,
decomposition is the correct answer. [PMBOK® Guide
6th edition, Pages 138, 158] [Analysis]
15. A - The salience model is used to analyze classes of
stakeholders based on their power (ability to impose their
will), urgency (need for immediate attention), and
https://t.me/PrMaB
legitimacy (their involvement is appropriate). [PMBOK®
Guide 6th edition, Page 513] [Planning]
16. B - Obtaining approval on the plan helps to reduce the
risk of stakeholders not supporting the business analysis
process once it starts. You need to come up with a solid
business analysis plan, and have it reviewed and approved
by the key stakeholders to minimize this risk.
[Business Analysis for Practitioners: A Practice Guide,
page 68; The PMI Guide to Business Analysis, page 127]
[Planning]
17. D - Product owners have the ultimate responsibility of
the project success. They prioritize the project backlog
and authorize change requests on an Agile project.
[The PMI Guide to Business Analysis, page 216, 264]
[Planning]
18. B - Rather than lock an entire project scope and
budget into a single agreement, a team can decompose the
scope into fixed-price micro-deliverables, such as user
stories. Team charter and Kanban board are tools used by
the team to manage the team’s WIP. WBS and WBS
dictionary are used in predictive approaches.
[The PMI Guide to Business Analysis, page 133]
[Planning]
19. B - Active listening is a communication technique that
requires the listeners to feedback what they hear to the
speaker, by way of re-stating or paraphrasing what they
have heard in their own words. This confirms what they
have heard and moreover, confirms the understanding of
both parties. Active listening is of prime importance
during the collection and analysis of stakeholders’ needs
and expectations.
[The PMI Guide to Business Analysis, Page 373]
[Planning]
20. A - Identify Risks is the process of determining what
risks can affect the project. Many different stakeholders
usually participate in the Identify Risks process. The
https://t.me/PrMaB
process of Identify Risks is iterative because unknown
risks can be discovered throughout the life cycle of the
project. [PMBOK® Guide 6th edition, Page 409]
[Planning]
21. B - If you want the team to immediately dedicate
some time to address these risks, you need to start a risk
spike. A risk spike is a sprint or iteration specifically
designated for research to address product risks. Risk
registers and burndown charts are some of the tools that
can be used during this sprint. Adding risks to the lessons
learned library doesn’t make any sense; however, you
would update the lesson learned library if the team learns
something new as part of actioning the risk response
strategies.
[The PMI Guide to Business Analysis, page 410]
[Analysis]
22. B - The outputs of the Assemble Business Case
process are business case and product scope.
[The PMI Guide to Business Analysis, pages 101, 102]
[Needs Assessment]
23. D - In adaptive approaches, iteration planning, or
sprint planning, is the activity used to identify the subset
of product backlog items from the product backlog that
the development team will work on for the current
iteration or sprint.
[The PMI Guide to Business Analysis, page 267]
[Traceability & Monitoring]
24. A - Project exclusions identify what is excluded from
the project. Explicitly stating what is out of scope for the
project helps manage stakeholders’ expectation and can
reduce scope creep. Other choices cannot help more in
this regard. [PMBOK® Guide 6th edition, Page 154]
[Needs Assessment]
25. D - The scenario is implying a firm sequence of
requirements management processes, this is typical of
https://t.me/PrMaB
predictive projects. Predictive projects provide a better
case for formal traceability than adaptive projects.
[The PMI Guide to Business Analysis, page 259]
[Traceability & Monitoring]
26. A - Five Whys is a technique that suggests anyone
trying to understand a problem needs to ask why it is
occurring up to five times in order to thoroughly
understand the problem’s causes. The rest of the choices
are not valid root-cause analysis techniques.
[The PMI Guide to Business Analysis, page 72] [Needs
Assessment]
27. C - Facilitated workshops use a structured meeting led
by a skilled neutral facilitator and a group of SMEs to
collaborate and work towards developing a product
roadmap. None of the other choices involve facilitated
sessions.
[The PMI Guide to Business Analysis, page 95] [Needs
Assessment]
28. D - Identifying alternatives to the proposed solution
and conducting cost benefit analysis is part of the
feasibility study of a solution, and not post-
implementation solution evaluation. The rest of the
choices are all solution evaluation good practices.
[The PMI Guide to Business Analysis, page 279]
[Evaluation]
29. B - A solution capability matrix could be used to
extend a capability table: A capability table is generally
applied to depict the relationship between a situation, its
root causes, and the capabilities needed to address the
situation. A solution capability matrix identifies where
these capabilities will be addressed in the new solution.
[The PMI Guide to Business Analysis, pages 67, 82]
[Needs Assessment]
30. A - The Confirm Elicitation Results process
transforms the unconfirmed elicitation results (input to the
https://t.me/PrMaB
process) to confirmed elicitation results (output of the
process).
[The PMI Guide to Business Analysis, page 170]
[Analysis]
31. D - According to PMI’s Pulse of the Profession® In-
Depth Report: Navigating Complexity, the presence of
multiple stakeholders and ambiguity of project features
are the top two contributors to the project complexity.
[Business Analysis for Practitioners: A Practice Guide,
page 42; The PMI Guide to Business Analysis, page 115-
116] [Planning]
32. B - An affinity diagram is similar to a mind map in
that it is used to generate ideas that can be linked to form
organized patterns of thought about a problem. It allows a
large number of ideas to be classified into groups for
review and analysis. The other choices are not similar to
mind maps. [PMBOK® Guide 6th edition, Page 144]
[Analysis]
33. C - Since this will be an official project document, it
should be formal. Additionally, since you are requesting
money from someone higher up in the organization, you
are creating an upward communication. [PMBOK®
Guide 6th edition, Page 361] [Analysis]
34. D - The work packages are at the lowest level of a
WBS. The other statements are correct regarding the
structure of the WBS. [PMBOK® Guide 6th edition, Page
159] [Planning]
35. B - A minimum viable product (MVP) is a product or
a project outcome that contains sufficient features to
satisfy project stakeholders. The product owner is
essentially asking you to develop the MVP.
[The PMI Guide to Business Analysis, page 204]
[Planning]
36. A - A prototype is an early model, or release of a
product built to test a concept. A prototype is generally
used to evaluate a new design to enhance precision by
https://t.me/PrMaB
system analysts and users. Developing and showcasing a
working prototype will help you regain the lost
stakeholder confidence.
[The PMI Guide to Business Analysis, page 199]
[Analysis]
37. C - This is an example of a fishbone diagram. A
fishbone diagram, also called a cause and effect diagram
or Ishikawa diagram, is a visualization tool for
categorizing the potential causes of a problem in order to
identify its root causes. [PMBOK® Guide, 6th edition,
Page 294] [Traceability & Monitoring]
38. A - Story mapping is a technique used to sequence
user stories based upon their business value and the order
in which their users typically perform them, so that teams
can arrive at a shared understanding of what will be built.
[The PMI Guide to Business Analysis, page 95] [Needs
Assessment]
39. A - Document analysis and observation will be of no
use in this context. Questionnaires and interviews are both
good candidates for the correct answer. However,
interviews are more interactive and allow you to clarify
ambiguous feedback, hence more appropriate for
soliciting an accurate feedback.
[The PMI Guide to Business Analysis, page 68] [Needs
Assessment]
40. C - A traceability matrix is a table that connects or
traces links between items. Most commonly, business
analysts use traceability matrices to trace requirements
backward to features and business objectives.
[The PMI Guide to Business Analysis, page 195]
[Analysis]
41. D - Since the project requirements are fixed and the
goal is to manage cost, a predictive approach is most
suitable in this case. [PMBOK® Guide 6th edition, page
19] [Needs Assessment]
https://t.me/PrMaB
42. B - A product portfolio matrix, also known as a
growth-share matrix, is a market analysis quadrant
diagram used by organizations to qualitatively analyze
their products or product lines. One axis reflects market
growth while the other reflects the market share.
[The PMI Guide to Business Analysis, page 283]
[Evaluation]
43. C - A traceability matrix is a grid that links product
requirements from their origin to the deliverables that
satisfy them. The matrix can support linkages among
many different types of objects, providing a mechanism
for tracking product information through the project and
product life cycles. Establishing these links manages
scope creep by ensuring that only relevant product
information is incorporated into the solution.
[The PMI Guide to Business Analysis, page 261]
[Traceability & Monitoring]
44. B - Some project teams use visual management tools,
rather than written plans and other documents, to capture
and oversee critical project elements. Making key project
elements visible to the entire team provides a real-time
overview of the project status. [PMBOK® Guide 6th
edition, Page 73] [Traceability & Monitoring]
45. D - MoSCoW stands for must have, should have,
could have, and won’t have. Applying MoSCoW rules to
project requirements ensure that the highest valued
business requirements/features are developed first.
[The PMI Guide to Business Analysis, page 234]
[Planning]
46. D - Stakeholders who are expected to adapt to the
implemented solution once it is built are from the “low
influence/high impact” group. Stakeholders that are just
being monitored to ensure their behavior does not change
over time are from the “low influence/low impact” group.
Stakeholders who are decision-makers have “high
influence”, and the stakeholders who are a critical source
for requirements are “high impact”.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 119-120]
[Planning]
47. B - All the choices are tools and techniques in quality
control; however, the best choice would be the Ishikawa
or cause-and-effect diagram. [PMBOK® Guide 6th
edition, Page 293] [Traceability & Monitoring]
48. B - Data flow diagrams are usually created during the
analysis phase. Entity relationship diagrams, process
flows, and ecosystem maps are generally created first to
identify the data objects, processes, and systems to show
in a data flow diagram.
[The PMI Guide to Business Analysis, page 188]
[Analysis]
49. B - The Return on Investment (ROI) is the percentage
return on an initial investment disregarding the time value
of money, however the NPV value cannot be used to
calculate the ROI. The NPV is the difference of total
inflows and outflows expressed in today’s value for
money. If the NPV is a positive value, the investment
decision is profitable.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
50. D - An onion diagram is a technique that can be used
to model relationships between different aspects of a
subject. This is a valid business analysis technique while
the rest of the choices are not.
[The PMI Guide to Business Analysis, page 121]
[Analysis]
https://t.me/PrMaB
PMI-PBA DOMAIN AREA
TEST: TRACEABILITY &
MONITORING
Practice Questions
Test Name: Domain Area Test: Traceability &
Monitoring
Total Questions: 20
Correct Answers Needed to Pass:
14 (70.00%)
Time Allowed: 30 Minutes
Test Description
This practice quiz specifically targets your knowledge of the
Traceability & Monitoring PMI-PBA Domain area.
Test Questions
1. You are managing a construction project for a
government organization. As part of your contractual
obligations, you need to invite your customer for progress
inspections at predefined construction stages. Customers
visiting a construction site to ensure the completed work is
the same work specified in the contractual requirements is
an example of:
A. Scope validation
B. Requirements traceability
C. Variance Analysis
D. Milestone
https://t.me/PrMaB
2. A project team member finds that the color scheme of
the webpage he is designing appears too gaudy and
decides to change it to a mellowed-down color scheme.
The customer approved the original color scheme and the
color palette. The independent testing team flags this as a
defect, and a heated discussion ensues between the team
member and the testing team. What is your view?
A. The testing team is not right in flagging this. The
color scheme is a simple matter, and the new colors
are definitely more pleasing than the old ones.
https://t.me/PrMaB
4. A project team’s recent deliverable to a client has been
rejected. The team is now sitting together to discuss this
situation and they prepare the following diagram. What is
the team doing?
A. Initiating a defect repair
https://t.me/PrMaB
C. The traceability and the change control processes
must satisfy regulatory requirements.
B. RACI matrix
C. CRUD matrix
D. Interaction matrix
https://t.me/PrMaB
According to the PMBOK® Guide, who is responsible for
reviewing, evaluating, and approving documented changes
to the project?
A. Change Control Board (CCB)
B. Kano model
C. Feature model
D. Fishbone diagram
https://t.me/PrMaB
12. You are currently auditing a struggling project
following an adaptive lifecycle. You find out that the
project team was trying Agile methods for the first time
and doesn’t have a common understanding on some
critical concepts. For adaptive projects, which of the
following statements is incorrect?
A. Additional details can be added to stories within an
iteration.
B. Subsets
C. Discretionary dependency
D. Implementation dependency
https://t.me/PrMaB
recently resigned and now you are responsible for all
business analysis activities on the project. The previous
analyst has done a good job collecting, analyzing and
documenting the requirements. However, you are worried
that, given the number of requirements and the agility
required by the project environment, maintaining audit
trails and managing version control will be difficult.
Which of the following should you consider at this stage?
A. Using a stakeholder engagement register
B. Burndown chart
C. Control chart
D. Histogram
https://t.me/PrMaB
D. A chart that shows the root cause of a problem
B. Fishbone analysis
C. Pareto analysis
D. Kano analysis
B. $34,500
C. $46,200
D. $44,000
https://t.me/PrMaB
C. Conduct a root cause analysis
https://t.me/PrMaB
PMI-PBA Domain Area Test: Traceability
& Monitoring
Answer Key and Explanations
1. A - Inspection is a scope validation technique that
includes activities (such as measuring, examining, and
verifying) to determine whether work and deliverables
meet requirements and product acceptance criteria.
[PMBOK® Guide 6th edition, Page 163] [Traceability &
Monitoring]
2. C - The testing team is correct in their findings. Even
though the new color scheme might be a better choice than
the old one, all changes need to follow the change
management process and go through the appropriate
change and approval process. [PMBOK® Guide 6th
edition, Page 115] [Traceability & Monitoring]
3. D - The scenario describes neither the root cause
behind the conflict nor the nature of the conflict. Hence,
the choices of transferring the stakeholders to another
group and reviewing the stakeholder management plan can
easily be eliminated. Avoiding conflict resolution in the
future could well lead to disaster; this choice can also be
eliminated. It is clear in the scenario that the conflict was
resolved by the project manager. The next thing that needs
to be done is updating the lessons learned documentation
with the appropriate conflict and resolution details.
[PMBOK® Guide 6th edition, Page 351] [Traceability &
Monitoring]
4. C - This is an example of a fishbone diagram. A
fishbone diagram, also called a cause and effect diagram
or Ishikawa diagram, is a visualization tool for
categorizing the potential causes of a problem in order to
identify its root causes. [PMBOK® Guide, 6th edition,
Page 293] [Traceability & Monitoring]
5. B - A traceability matrix doesn’t track a project’s cost
and schedule performance, hence cannot help track the
https://t.me/PrMaB
CPI and SPI. The rest of the choices are all valid reasons
for keeping the traceability matrix up to date.
[The PMI Guide to Business Analysis, page 258]
[Traceability & Monitoring]
6. B - You need some sort of traceability and change
control process on any project. These can be formally or
informally defined. The rest of the choices are valid
considerations for designing a change control or a
traceability process.
[The PMI Guide to Business Analysis, page 254]
[Traceability & Monitoring]
7. D - A traceability matrix is a grid that links product
requirements from their origin to the deliverables that
satisfy them. The matrix can support linkages among
many different types of objects, providing a mechanism
for tracking product information through the project and
product life cycles. On projects using an adaptive life
cycle, the product team may choose to develop an
interaction matrix which is a lightweight version of a
traceability matrix that is used to determine whether
requirements are sufficiently detailed or if any entities are
missing.
[The PMI Guide to Business Analysis, page 261]
[Traceability & Monitoring]
8. B - Documenting both the success stories and the
failed attempts are important as these can be very
important inputs for future projects. Only focusing on the
negatives and analyzing failures will paint half of the
picture. The best practice is to ask “What went right”
when asking “What went wrong?”. [PMBOK® Guide 6th
edition, Page 104] [Traceability & Monitoring]
9. A - The Change Control Board is a group of formally
constituted stakeholders responsible for reviewing,
evaluating, approving, delaying or rejecting changes to the
project. [PMBOK® Guide 6th edition, Page 115]
[Traceability & Monitoring]
https://t.me/PrMaB
10. B - A burndown chart is a graphical representation
used to count the remaining quantity of work over time.
The burndown chart hitting the x-axis means all product
backlog items will be completed during the current sprint.
[The PMI Guide to Business Analysis, page 131]
[Traceability & Monitoring]
11. C - A feature model is a scope model that visually
represents all the features of a solution arranged in a tree
or hierarchical structure. The feature model shows
relationships between features and which features are sub-
features of other ones.
[The PMI Guide to Business Analysis, page 260]
[Traceability & Monitoring]
12. D - While it is true that there are no formal change
control processes on adaptive projects, it is incorrect to
say that when a change is requested, no impact analysis is
conducted; scaled impact analysis is typically conducted.
All other choices are correct statements.
[The PMI Guide to Business Analysis, page 275]
[Traceability & Monitoring]
13. D - This is an example of an implementation
dependency; you will not be able to produce the list-view
until the system is able to capture and store the requests.
[The PMI Guide to Business Analysis, page 259]
[Traceability & Monitoring]
14. C - A requirements management tool allows
requirements and other product information to be captured
and stored in a central repository. Such a tool typically has
the ability to maintain audit trails and perform version
control to assist with change management. None of the
other choices have the capability or ability to perform this.
[The PMI Guide to Business Analysis, page 260]
[Traceability & Monitoring]
15. B - An iteration burndown chart tracks the work that
remains to be completed in the iteration backlog. The rest
https://t.me/PrMaB
of the choices quality management tools. [PMBOK®
Guide 6th edition, Page 226] [Traceability & Monitoring]
16. C - A control chart shows the stability of a process
over time. [PMBOK® Guide 6th edition, Page 304]
[Traceability & Monitoring]
17. A - Force field analysis is a decision-making
technique that can be used to help teams analyze whether
there is enough support to pursue a change. Forces FOR
the change are compared with forces AGAINST the
change to determine the overall impact of the change
initiative.
[The PMI Guide to Business Analysis, page 266]
[Traceability & Monitoring]
18. C - The cost baseline is the approved version of the
project budget that includes contingency reserves, but
excludes management reserves. The sum of individual
activity cost estimates comes up to be $44,000 (sum of all
planned values). Adding a 5% contingency reserve we get
a cost baseline of $46,200. [PMBOK® Guide 6th edition,
page 248] [Traceability & Monitoring]
19. B - The definition and implementation of a
traceability process will minimize the likelihood of
missing requirements in the final product.
[The PMI Guide to Business Analysis, page 254]
[Traceability & Monitoring]
20. D - The product owner has the authority to terminate
the user stories. When user stories are terminated, they
can be moved back onto the product backlog for future
consideration or marked as no longer needed. Since no
reason for termination was provided, it is safer to move
the stories back to the product backlog then to delete these
from the scope.
[The PMI Guide to Business Analysis, page 264]
[Traceability & Monitoring]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) – 7
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 7
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. You have recently joined a team that is developing a
new information management system for your
organization. You reviewed the entire product backlog and
are satisfied with the alignment of all backlog items to the
stated business needs. How can you extend your existing
traceability matrix to ensure that the system design is
compliant to the agreed requirements?
A. PERT analysis
B. Backward traceability
C. Forward traceability
https://t.me/PrMaB
business has also been significantly impacted. In order to
have a plan during this tough time, you need to better
understand your new environment and conditions. Which
of the following business analysis techniques should you
use?
A. Prototyping
B. Competitive Analysis
C. Market Analysis
D. Document Review
B. Pareto model
C. Andon
D. Kanban
https://t.me/PrMaB
D. Use an Agile life cycle
B. Document Analysis
C. Walkthroughs
D. Interviews
B. Stakeholder register
C. Business case
https://t.me/PrMaB
D. Work breakdown structure
B. Functional requirement
C. Transition requirement
D. Business requirement
https://t.me/PrMaB
C. Market share of the organization
B. Scope creep
C. Prompt list
D. Process mapping
https://t.me/PrMaB
your department. During the Assess Current State process,
the focus of a business analyst is primarily on:
A. Developing the business case for the opportunity
being analyzed.
https://t.me/PrMaB
B. PERT
C. SWOT
D. WIDE
B. Simulation
C. Prototyping
B. Context diagram
D. Ecosystem map
https://t.me/PrMaB
diagram was included in the project’s business case. What
does this diagram tell us?
A. Scope of the project
B. User requirements
C. Data model
D. Integration requirements
https://t.me/PrMaB
second project release. If you can substantiate this
analysis you can demonstrate:
A. The break-even point on the project
B. Kanban board
D. Silos
B. Analogous estimating
C. Estimation poker
D. Affinity estimating
https://t.me/PrMaB
environment. You have asked the development team to
trace the root cause of this application failure. Which of
the following can be used to help determine the cause(s)
of the failure?
A. Threading analysis
C. Ishikawa diagram
D. Deming chart
https://t.me/PrMaB
A. Review the solution evaluation process in the
business analysis plan.
B. PBP
C. ROI
D. NPV
B. User stories
C. Fishbone diagrams
D. Decision trees
https://t.me/PrMaB
28. A certain project was in the Collect Requirements
phase. The product’s eventual users could not define their
requirements. In this scenario, which of the following
tools could have helped determine the requirements?
A. Surveys
B. Prototypes
C. Questionnaires
D. Interviews
B. Sprint planning
C. Retrospectives
D. Daily standups
https://t.me/PrMaB
to his project. During the project initiation, he produced
the stakeholder register and impressed his project sponsor.
Rob is now about to develop the stakeholder engagement
plan for his project. This has made the project sponsor a
bit uncomfortable because he thinks Rob is spending too
much time doing paperwork instead of actually executing
the project work. The project sponsor has asked Rob to
explain the difference between the stakeholder register
and the stakeholder engagement plan. How should Rob
respond?
A. The stakeholder register only contains basic
stakeholder assessment information, while the
stakeholder engagement plan includes detailed
stakeholder engagement strategy that ensures
project success.
https://t.me/PrMaB
B. Prioritize Requirements and Other Product
Information
C. Validate Requirements
D. Verify Requirements
B. Delphi
C. Walkthroughs
D. Affinity diagrams
B. 0.05
C. 0.1
https://t.me/PrMaB
D. This cannot be determined from the information
provided.
C. Decomposition
https://t.me/PrMaB
37. You are the sponsor of an enterprise transformation
program. You are currently participating in a major
product requirements elicitation event that your lead
business analyst is facilitating. You have observed that
most of the stakeholders are confused with the objective
of the event and the business analyst had to spend a
considerable amount of time explaining the agenda. In
your opinion, how could this situation have been avoided?
A. By having the project manager facilitate.
https://t.me/PrMaB
A. Investment requirement
D. Conduct Elicitation
https://t.me/PrMaB
techniques is ideal in this situation and would allow you
to quickly obtain the feedback?
A. Interviews
B. Observation
C. Questionnaires
D. Virtual meetings
https://t.me/PrMaB
C. Conduct detailed user acceptance testing of the
enhanced functionality.
B. Scope creep
C. Gold plating
D. Agile approach
https://t.me/PrMaB
B. Story sizing
B. Ishikawa diagrams
C. Pareto diagrams
https://t.me/PrMaB
D. Process diagrams
C. Conduct a 5S workshop.
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) – 7
Answer Key and Explanations
1. C - Backward traceability is performed from the
requirements to the scope features and business goals and
objectives that triggered them. Forward traceability is
performed from the requirements to design and test
components and ultimately, the final product.
[The PMI Guide to Business Analysis, page 253]
[Traceability & Monitoring]
2. C - Prototyping and document review are irrelevant to
the problem at hand. Competitive analysis and market
analysis are good candidates for the correct answer.
However, market analysis is the best answer as it covers a
broader area for analysis which includes competitive
analysis.
[The PMI Guide to Business Analysis, pages 60, 61]
[Needs Assessment]
3. D - A Kanban board is used in adaptive approaches to
track work that is in progress by the project team.
[The PMI Guide to Business Analysis, page 233]
[Traceability & Monitoring]
4. B - Since the scope cannot be accurately defined
upfront on the project, delivering the project in small
increments is recommended. Predictive and Agile
approaches will most likely not help in this situation.
[PMBOK® Guide 6th edition, page 19] [Needs
Assessment]
5. A - Collaborative games are used during the Conduct
Elicitation process and not during the Confirm Elicitation
Results process. The rest of the choices are valid tools and
techniques of the Confirm Elicitation Results process.
[The PMI Guide to Business Analysis, pages 164, 170]
[Analysis]
https://t.me/PrMaB
6. D - A use case diagram is a scope model that shows all
the in-scope use cases for a solution. Creating use case
diagrams involves identifying a list of both the users of the
solution and the possible scenarios of how each user will
use the solution.
[The PMI Guide to Business Analysis, page 206]
[Analysis]
7. B - Job analysis is conducted during the Conduct
Stakeholder Analysis process. Once this analysis is
complete, the results are then documented in the
stakeholder register.
[The PMI Guide to Business Analysis, page 117, 122]
[Planning]
8. C - This is an example of a transition requirement.
Transition requirements describe temporary capabilities,
such as data conversion and training requirements; and
operational changes needed to transition from the current
state to the future state.
[The PMI Guide to Business Analysis, page 10] [Needs
Assessment]
9. D - Nonfunctional characteristics of a solution are
evaluated with measurements. For example, performance
standards in service-level-agreements can be measured for
actual compliance. On the other hand, acceptance testing
is used to evaluate the functional characteristics of a
solution.
[The PMI Guide to Business Analysis, page 278]
[Evaluation]
10. C - A Product portfolio matrix, also known as a
growth-share matrix, is a market analysis quadrant
diagram used by organizations to qualitatively analyze
their products and product lines. One axis reflects market
growth (or demand for a product) while the other reflects
the market share of the organization.
[The PMI Guide to Business Analysis, page 283]
[Evaluation]
https://t.me/PrMaB
11. B - Observation is an elicitation technique that
provides a direct way of obtaining information about how
a process is performed. Observation can help uncover
information that stakeholders are not able or willing to
provide. The main drawback of the technique is that
people may act differently when they are being observed.
The other choices are not generic disadvantages of this
technique.
[The PMI Guide to Business Analysis, page 168]
[Analysis]
12. A - In quality management, customer needs and
requirements are also known as voice of the customer
(VOC). [PMBOK® Guide 6th edition, Page 145] [Needs
Assessment]
13. B - Evaluating the current capabilities of the
organization is a significant focus during a current state
assessment. Identifying the problems and opportunities
are the focus of the Identify Problem or Opportunity
process, while the business case is put together during the
Assemble Business Case process.
[The PMI Guide to Business Analysis, page 63] [Needs
Assessment]
14. B - Project champions are the stakeholders who assist
the project team in building excitement and support for
the project. In order to identify them, you need to find out
the positive stakeholders who support the project the
most.
[Business Analysis for Practitioners: A Practice Guide,
page 40; The PMI Guide to Business Analysis, page 115]
[Planning]
15. A - DEEP stands for: Detailed, estimated, emergent,
and prioritized. DEEP describes the characteristics that a
product backlog needs to demonstrate to be considered
well-refined.
[The PMI Guide to Business Analysis, page 213]
[Analysis]
https://t.me/PrMaB
16. C - Prototyping is a method of obtaining early
feedback on requirements by providing a model of the
expected solution before building it.
[The PMI Guide to Business Analysis, page 61] [Needs
Assessment]
17. C - An entity relationship diagram is a business
analysis model that shows the business data objects or
pieces of information of interest and the relationships
between those objects, including the cardinality of those
relationships. None of the other choices are the tools that
can supply this information at this level.
[The PMI Guide to Business Analysis, page 396]
[Analysis]
18. A - This is an example of a context diagram. A
context diagram defines the boundary between the system
and its environment. This diagram is a high-level view of
a system. The context diagram is an example of a scope
model. In this case, the context diagram is showing the
scope of the project. [PMBOK® Guide, 6th edition, Page
146] [Planning]
19. B - Some of the benefits and value of the solution may
seem to be intangible, and therefore, not possible to
measure. For intangible benefits, it may be necessary to
define measurements that provide indirect evidence that
the benefits have been achieved.
[The PMI Guide to Business Analysis, page 279]
[Evaluation]
20. C - A point of diminishing returns is the point where
additional value that could be obtained from a solution
does not justify the additional effort needed to achieve
that value. If you can substantiate your analysis, you can
demonstrate that the “nice-to-have” supporting
requirements should not be developed and the remaining
funds need to be allocated to other higher-priority
projects.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 279]
[Evaluation]
21. B - The team should consider making work visible
using Kanban boards and experimenting with limits for
the various areas of the work process in order to improve
flow.
[The PMI Guide to Business Analysis, page 233]
[Planning]
22. C - Estimation poker is a collaborative relative
estimation technique in which there is an agreed-upon
scale used for the relative estimates. Each person
participating in estimating poker is given a series of cards
with the agreed-upon scale.
[The PMI Guide to Business Analysis, page 133]
[Planning]
23. C - Cause-and-effect diagrams, also called Ishikawa
diagrams, illustrate how various factors might be linked to
potential problems or effects. [PMBOK® Guide 6th
edition, Page 293] [Analysis]
24. D - Variances assess the magnitude of variation from
the original cost baseline. The percentage range of
acceptable variances will tend to decrease as more work is
accomplished and the project nears completion.
[PMBOK® Guide 6th edition, Page 262] [Traceability &
Monitoring]
25. A - The level of detail you are looking for is usually
planned and documented in the business analysis plan.
You need to review the solution evaluation process in the
business analysis plan.
[Business Analysis for Practitioners: A Practice Guide,
page 60; The PMI Guide to Business Analysis, page 286]
[Planning]
26. A - The Internal Rate of Return (IRR) gives the
projected annual yield of an investment (rate of return)
considering the time value of money. On the other hand,
the NPV (net present value) of an investment is the
https://t.me/PrMaB
difference between the present value of cash inflows and
the present value of cash outflows over a period of time
considering the time value of money. Payback period
(PBP) is the time needed to recover an investment. Return
on Investment (ROI) is the percentage return on an initial
investment. Both PBP and ROI do not consider time value
of money.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
27. B - User stories are short, textual descriptions of
required functionality often developed during a
requirements gathering workshop. The rest of the choices
are graphical formats. [PMBOK® Guide 6th edition, Page
145] [Needs Assessment]
28. B - Prototypes are working models of the expected
product before actually building it. The tangible nature of
prototypes allows users to experiment with a model of
their final product early in the project life cycle and to
generate clear feedback. Interviews, questionnaires and
surveys were unlikely to help in this case since the users
were struggling to define their requirements. [PMBOK®
Guide 6th edition, Page 147] [Planning]
29. A - User stories are progressively elaborated via
backlog refinement sessions.
[The PMI Guide to Business Analysis, page 216]
[Analysis]
30. C - Technical debt refers to the deferred cost of work
not done at an earlier point in the product life cycle. This
is sunk cost and cannot be recovered. However, the team
must ensure that the current product backlog is updated
with current organizational priorities.
[The PMI Guide to Business Analysis, pages 297, 414]
[Planning]
31. A - It must be noted that the project manager is
responding to the project sponsor in order to defend a
position. The sponsor is asking for the difference between
https://t.me/PrMaB
the two documents. The best response should not only
clarify the difference between the two, it should also make
some business sense. All of the statements are technically
correct, but having a stakeholder engagement strategy to
ensure success makes more business sense. [PMBOK®
Guide 6th edition, Page 522] [Planning]
32. C - Verification is the process of reviewing the
requirements and other product information for errors,
conflicts, and adherence to quality standards. Verification
also involves evaluating whether requirements and other
product information complies with a regulation,
specification, or imposed condition. On the other hand,
Validate Requirements is the process of checking that the
requirements meet business goals and objectives. The key
benefit of this process is that it minimizes the risk of
missing stakeholder expectations or delivering the wrong
solution.
[The PMI Guide to Business Analysis, pages 221, 225]
[Analysis]
33. B - Delphi is a consensus-building method that
consolidates anonymous input from subject matter experts
(SMEs) using rounds of voting. This method reduces peer
pressure or groupthink in the validation process and
avoids having the team give in to a voice of authority with
which they might disagree.
[The PMI Guide to Business Analysis, page 228]
[Analysis]
34. C - The Internal Rate of Return (IRR) gives the
projected annual yield of an investment (rate of return)
considering the time value of money. The IRR value
signifies the discount rate at which the net present value
of all cash flows will equal zero. Since at 10% discount
rate the NPV is zero, the project’s IRR is 10%.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
35. D - Proxy performance data could include
measurements that describe the effectiveness or quality of
https://t.me/PrMaB
the product, such as the average duration of a task while
using the product, response time for solutions involving
software, or counts of errors made while performing a
task.
[The PMI Guide to Business Analysis, page 282]
[Evaluation]
36. C - The manager requested the team to divide the
work packages into more manageable components for
estimating the resources. The Define Activities process is
used to divide the work packages into more manageable
activities for estimating, scheduling, and executing the
project work. Decomposition is the technique used during
this process to divide the work packages into activities.
[PMBOK® Guide 6th edition, Page 185] [Planning]
37. C - Since this is an elicitation event, the business
analyst is in the right position to facilitate the event. The
confusion of the stakeholders implies that they were
surprised with the expectation from them. This could have
been avoided if these stakeholders would have been
consulted in advance, so they were more aware of the
agenda, objectives, and the expectations.
[The PMI Guide to Business Analysis, page 163]
[Analysis]
38. D - The budget of the project must be irrelevant to the
design of the traceability process. The rest of the choices
are all valid considerations for designing an effective
traceability process.
[The PMI Guide to Business Analysis, page 254]
[Traceability & Monitoring]
39. B - Projects help in achieving organizational goals
whey they are aligned with the organization’s strategy. If
the projects are misaligned with the organizational
strategic goals, they are most likely to produce
undesirable results either in the short-term or the long-
term. NPV and IRR calculations are great measures,
however, these are not applicable since these projects will
not contribute to any of the revenue streams. Investment
https://t.me/PrMaB
requirement is important but is useless on the projects that
are not aligned with the strategic goals of the
organization. [PMBOK® Guide 6th edition, Pages 34, 35]
[Needs Assessment]
40. A - Determine Elicitation Approach is the process of
thinking through how elicitation activities will be
conducted, which stakeholders will be involved, which
techniques may be used, and the order in which the
elicitation activities are best performed.
[The PMI Guide to Business Analysis, page 156]
[Planning]
41. D - A measure of quality, in the absence of standards
or in addition to them, at a basic level, includes evaluating
the information for the 3Cs: correct, complete, and
consistent.
[The PMI Guide to Business Analysis, page 222]
[Analysis]
42. C - Questionnaires and surveys are written sets of
questions designed to quickly accumulate information
from a large number of respondents. The rest of the
techniques will demand a lot of time to gather feedback
from 500 employees.
[The PMI Guide to Business Analysis, page 114]
[Analysis]
43. B - Conflict is inevitable in a project environment.
The other statements are incorrect. [PMBOK® Guide 6th
edition, Page 348] [Analysis]
44. B - You must conduct thorough acceptance testing
with the client. However, prior to do that, you must ensure
that the newly added functionality has not impacted the
existing functionality of the product. As the next step, you
need to conduct regression testing.
[The PMI Guide to Business Analysis, page 408]
[Analysis]
45. D - In adaptive life cycles, the requirements are
documented in user stories that are then prioritized and
https://t.me/PrMaB
refined. The product features are developed using time-
boxed periods of work. This approach is often used to
deliver incremental value to the customer. [PMBOK®
Guide 6th edition, Page 177] [Analysis]
46. B - Although Agile approaches are change friendly,
this does not mean that the changes do not need to be
controlled. The uncontrolled expansion of a product or
project scope without adjustments to time, cost, and
resources is known as scope creep.
[The PMI Guide to Business Analysis, page 411]
[Analysis]
47. C - Rolling Wave Planning is an iterative planning
technique in which the work to be accomplished in the
near term is planned in detail, while the work in the future
is planned at a higher level.
[The PMI Guide to Business Analysis, page 134]
[Planning]
48. D - The business analyst is correct: business analysis
planning is iterative and much of the information will not
be known or uncovered until the elicitation work is
underway.
[Business Analysis for Practitioners: A Practice Guide,
page 53; The PMI Guide to Business Analysis, page 127]
[Planning]
49. B - Cause and Effect diagrams are also called
Ishikawa diagrams. [PMBOK® Guide 6th edition, Page
293] [Analysis]
50. A - The problem at hand is that there is no agreed and
documented sales pipeline management process. In order
to resolve this problem, you need to call a stakeholder
workshop to define and agree on the sales pipeline
process flow.
[The PMI Guide to Business Analysis, pages 70] [Needs
Assessment]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) - 8
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 8
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. You are leading the business analysis activities for a
software development project. As your first deliverable,
you need to submit your business analysis plan for
approval. You have identified your business analysis
activities and now have to estimate expected durations and
cost. Which of the following techniques can be used for
the estimation of duration and cost for your business
analysis activities using historical data from similar
projects?
A. Analogous estimation
B. Bottom-up estimation
C. Top-down estimation
D. Linear estimation
https://t.me/PrMaB
2. A project team is currently investigating an issue on
your project. The team wants to setup a visual
management tool to track and monitor the work in
progress and to understand scheduling demands of the
project. Which of the following tools will you recommend
to be used?
A. Fishbone diagram
B. Kanban board
C. WBS
D. Product backlog
B. Kano model
D. MoSCoW model
https://t.me/PrMaB
D. Option B since the NPV is $85,000
B. Fishbone diagram
C. Waterfall chart
https://t.me/PrMaB
8. You are in charge of a troubled project. The project
includes producing widgets for your customer. You
collected production data to help identify the causes of
defects in the overall process. Which technique should you
use to analyze this data to determine the main source of
defects?
A. Statistical sampling
B. Kaizen
C. Fishbone diagram
B. Grouping by location
C. Grouping by interest
D. Grouping by authority
https://t.me/PrMaB
B. 12 years
C. 10 years
D. 2 years
B. Additional cost
C. Scope creep
D. Waste of time
B. Use cases
C. Requirement statements
D. User stories
https://t.me/PrMaB
A. Comparing the business problems to the identified
root causes.
B. Analysis processes
C. Elicitation processes
https://t.me/PrMaB
C. Build the factory for the client
C. Product specifications
D. Work location
https://t.me/PrMaB
C. Investigate the team qualification and skills and
identify where the team communications channels
are being compromised.
https://t.me/PrMaB
techniques to determine stakeholder engagement and
communication approach EXCEPT:
A. Brainstorming
B. Facilitated workshops
C. Interviews
D. Persona analysis
B. Report Table
C. Display-action-response model
https://t.me/PrMaB
23. Your organization is a regional water distribution
company. So far, the organization has enjoyed a
monopoly. The new managing director wants the business
to get into the bottled water market. Since there are a
number of players already in the bottled water market, the
organization’s current sales and marketing processes and
procedures might not be fit for the new competition. In
order to compare the organization’s current processes with
that of the competitors’, you need to utilize which of the
following techniques?
A. PEST analysis
B. SWOT analysis
C. Benchmarking
D. Digitization
https://t.me/PrMaB
and slice the stories in collaboration with the product
team. What should you do next?
A. Increase the sprint size to accommodate all epics.
B. Project requirements
C. Functional requirements
D. Business requirements
https://t.me/PrMaB
D. Inspection
B. Kanban board
D. Feature model
B. Pareto diagram
D. Stakeholder register
https://t.me/PrMaB
A. Brainstorming
B. Control chart
C. Venn diagram
D. Affinity diagram
32. You and your Agile team are currently analyzing your
project’s backlog. You want to identify the stories that
have historically delighted the users but now have become
their basic requirements. What would be your
development approach for these basic items?
A. Prioritize these after the current delighters.
https://t.me/PrMaB
an Agile approach but the request was turned down by the
program manager. Instead, she advised that you use
Rolling Wave Planning on the project. When is Rolling
Wave Planning useful in a project?
A. You should use Rolling Wave Planning to help you
organize team members’ activities within a large
project group.
B. Dataflow Diagram
C. Context Diagram
D. Data Dictionary
https://t.me/PrMaB
project team in building excitement and support for the
project are known as:
A. Scrum masters
B. Project champions
C. Agile gurus
D. Black belts
36. You have just been advised by the project sponsor that
the new student management system your project team is
developing must be available 24x7 and must be able to
handle up to 500 concurrent connections at any given
point in time. This is an example of:
A. Non-functional requirement
B. Transition requirement
C. Functional requirement
D. Business requirement
B. Kanban
C. Gemba
D. Andon
https://t.me/PrMaB
decisions. Which of the following techniques can help
you overcome this problem and obtain quality feedback
from all SMEs?
A. Fishbone
B. Weighted Ranking
C. 80/20 Rule
D. Delphi
https://t.me/PrMaB
A. Beginning of a project
B. Delphi
C. Backlog grooming
D. Affinity diagram
https://t.me/PrMaB
43. You are automating a warehouse stock replenishment
and reordering system. The reorder quantity and the
selection of the supplier depend upon several variables.
You have collected all the rules that define this logic.
Which of the following models should you develop next
to document this logic?
A. Data Dictionary
B. Report Table
C. Decision Table
D. Process Flows
B. State table
D. Ecosystem map
B. Product box
C. Box plot
D. Traceability matrix
https://t.me/PrMaB
improving their performance. Which of the following is
an Agile improvement technique that allows the team to
evaluate its past performance on a regular basis?
A. Kanban
B. Retrospectives
C. RACI analysis
D. Planning Poker
47. You and your Agile team are currently making team
commitments regarding what features will be progressed
or completed prior to the next stand-up. Which meeting is
this?
A. Backlog grooming
B. Sprint retrospective
C. Daily meeting
D. Iteration planning
https://t.me/PrMaB
business applications that are currently hosted on-site and
migrate them over to a private cloud offered by a leading
vendor. Since the expected number of project stakeholders
is high, you will be relying on multiple techniques to
identify all impacted stakeholders. Which of the following
is NOT a technique that is used for stakeholder
identification?
A. Brainstorming
B. Interviews
C. Organizational charts
D. Five-whys analysis
B. Retrospectives
D. Backlog grooming
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) - 8
Answer Key and Explanations
1. A - Analogous estimation is a technique for estimating
the duration or cost of an activity or portfolio component,
program, or project using historical data from an item
having similar characteristics.
[The PMI Guide to Business Analysis, page 387]
[Analysis]
2. B - Kanban boards are visual management tools that
help manage the flow of the project work and scheduling
demands. None of the other choices are visual
management tools. [PMBOK® Guide 6th edition, page
117] [Traceability & Monitoring]
3. C - Requirements management tools allow
requirements and other product information to be captured
and stored in a repository. These tools help maintain audit
trails and perform version control to assist with change
management. These tools also facilitate review and
approval processes thorough workflow functionality.
[The PMI Guide to Business Analysis, page 260]
[Traceability & Monitoring]
4. A - If you disregard the risk, option A is more
favorable as it has a higher NPV. However, since the
management’s risk tolerance is low, option B must be
selected as its payback period is shorter.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
5. D - A release burndown chart shows a team’s progress
by showing the number of story points remaining in the
project. The vertical axis shows the number of story points
remaining and the iterations are shown across the
horizontal axis.
[The PMI Guide to Business Analysis, page 131]
[Analysis]
https://t.me/PrMaB
6. A - A traceability matrix is a grid that links product
requirements from their origin to the deliverables that
satisfy them. The matrix can support linkages among
many different types of objects, providing a mechanism
for tracking product information through the project and
product life cycles. Establishing these links manages scope
creep by ensuring that only relevant product information is
incorporated into the solution. All the rest of the choices
are irrelevant to the problem at hand.
[The PMI Guide to Business Analysis, page 261]
[Traceability & Monitoring]
7. D - Since this is an elicitation workshop, the goal can
be nothing but eliciting product requirements. Developing
the cost estimates and identifying the critical path is the
job of the project manager. Further brainstorming cannot
be used to validate a business case.
[The PMI Guide to Business Analysis, page 165]
[Analysis]
8. C - Cause-and-effect diagrams, also known as fishbone
diagrams, why-why diagrams, or Ishikawa diagrams,
break down the causes of the problem statement into
discrete branches, helping to identify the main or root
cause of the problem. [PMBOK® Guide 6th edition, Page
293] [Traceability & Monitoring]
9. A - Stakeholders should be grouped based on their
characteristics. Stakeholder groupings can be structured by
similar interests, common needs, level of importance, by
roles, motivations, complexity level, location or many
other stakeholder qualities. Grouping by project scope
doesn’t make any sense.
[Business Analysis for Practitioners: A Practice Guide,
page 44; The PMI Guide to Business Analysis, page 115-
116] [Planning]
10. B - The payback period is the time needed to recover
an investment. For this scenario, the payback period is 12
years; 2 years of development time + 10 years to recover
the initial investment.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
11. B - If the information is critical for Solution
Evaluation, this need to be obtained. There might be some
cost disadvantages there but this cannot be ignored. All
other options are irrelevant.
[The PMI Guide to Business Analysis, page 279]
[Evaluation]
12. A - A burndown chart is a graphical representation of
work left to do versus time. This cannot be used to
document product requirements. The rest of the choices
are all acceptable forms of requirements documentation.
[The PMI Guide to Business Analysis, page 9] [Analysis]
13. A - Comparing the business problems to the identified
root causes is carried out during a typical root cause
analysis and the results are typically displayed on a
fishbone diagram. A traceability matrix is generally not
suitable for this exercise. All the rest of the choices are
valid examples of the use of a traceability matrix.
[The PMI Guide to Business Analysis, page 196]
[Analysis]
14. A - Needs Assessment processes guide the investment
decisions made by organizations. Processes from the
Needs Assessment knowledge area are used to ensure that
new initiatives align with organizational strategy.
[The PMI Guide to Business Analysis, page 57] [Needs
Assessment]
15. A - In this scenario you are considering investing your
money in the bank or building a factory. Since all
transactions are not happening at the same point in time,
we need to discount the cash flows and then determine the
return on investment. Since the bank is offering a 30%
annual interest rate (the opportunity cost if you decide to
build the factory), you need to discount all the cash flows
for the factory project by 2.5% (30% / 12) on a monthly
basis. The discount formula is: Present Value (PV) =
https://t.me/PrMaB
Future Value / (1 + interest rate)^period. Let’s use this
formula to determine the net present value of all cash
outflows: Month 1: PV = 1,000,000/(1+2.5%)^1 =
975,610 Month 2: PV = 1,000,000/(1+2.5%)^2 = 951,814
Month 3: PV = 1,000,000/(1+2.5%)^3 = 928,599 Month
4: PV = 1,000,000/(1+2.5%)^4 = 905,951 Month 5: PV =
1,000,000/(1+2.5%)^5 = 883,854 Month 6: PV =
1,000,000/(1+2.5%)^6 = 862,297 Month 7: PV =
1,000,000/(1+2.5%)^7 = 841,265 Month 8: PV =
1,000,000/(1+2.5%)^8 = 820,747 Month 9: PV =
1,000,000/(1+2.5%)^9 = 800,728 Month 10: PV =
1,000,000/(1+2.5%)^10 = 781,198 Month 11: PV =
1,000,000/(1+2.5%)^11 = 762,145 Month 12: PV =
1,000,000/(1+2.5%)^12 = 743,556 Adding these up we
get the total PV of outflows = 10,257,765 Now let’s
calculate the PV of all inflows using the same formula:
Quarter 1: PV = 3,900,000/(1+2.5%)^3 = 3,621,538
Quarter 2: PV = 3,900,000/(1+2.5%)^6 = 3,362,958
Quarter 3: PV = 3,900,000/(1+2.5%)^9 = 3,122,841
Quarter 4: PV = 3,900,000/(1+2.5%)^12 = 2,899,868
Adding these up we get the total PV of inflows =
13,007,204 The return on investment (today) =
(13,007,204 - 10,257,765)*100 / 10,257,765 = 27% Since
the bank is offering an annual 30% return on investment,
it is advisable not to undertake the project and leave the
money in the bank account. [PMBOK® Guide 6th edition,
Page 34, https://www.mathsisfun.com/money/net-present-
value.html] [Needs Assessment]
16. B - The procurement statement of work (SOW) does
not usually reference the business case. The business case
may contain cost sensitive information that may not be
made available to a wider audience. The rest of the
choices are valid components of a procurement statement
of work. [PMBOK® Guide 6th edition, Page 477] [Needs
Assessment]
17. B - A Scope Management Plan documents how the
project and product scope will be defined, validated, and
controlled. It appears that multiple requirements
management approaches have been tested on the project
https://t.me/PrMaB
without proper change control. This leads to a basic
question; doest an agreed and approved scope
management plan exits? If the answer to this question is a
yes, then further investigations will be required to identify
the root cause of the problem. [PMBOK® Guide 6th
Edition, Page 134] [Planning]
18. D - A burndown chart shows a team’s progress by
showing the number of story points remaining in the
project. The vertical axis shows the number of story
points remaining and the iterations are shown across the
horizontal axis. A steadily declining burndown chart
indicates that the velocity is constant; the same number of
story points are being delivered in each project iteration.
[The PMI Guide to Business Analysis, page 131, 148]
[Planning]
19. A - If the situation statement is not properly
understood, or if the stakeholders have a different idea of
the situation, there is a risk that a wrong solution will be
identified. All other options are irrelevant to the issue
presented.
[The PMI Guide to Business Analysis, page 59] [Needs
Assessment]
20. D - Persona analysis is a stakeholder analysis
technique that can help you understand the stakeholders,
their needs, and requirements better. However, this is not
an elicitation technique.
[The PMI Guide to Business Analysis, pages 125, 126]
[Analysis]
21. D - A goal model and business objectives model are
scope models that organize and reflect the goals and
business objectives in relation to other product
information.
[The PMI Guide to Business Analysis, page 194]
[Analysis]
22. B - SIPOC stands for Suppliers, inputs, process,
outputs, and customers. [PMBOK® Guide 6th edition,
https://t.me/PrMaB
Page 284] [Analysis]
23. C - Benchmarking is a comparison technique used to
compare one set of practices, processes, and
measurements of results against another. This technique
provides a way to determine new capabilities by
conducting a comparison against benchmarking studies of
external organizations.
[The PMI Guide to Business Analysis, page 78] [Needs
Assessment]
24. D - Unconfirmed elicitation results consist of the
information obtained from completed elicitation activities.
These results of elicitation activities may be documented
either formally or informally. Since you are gathering
notes and artifacts produced during the workshop, these
are considered as informally documented.
[The PMI Guide to Business Analysis, page 169]
[Analysis]
25. D - Story slicing is a technique to split epics or user
stories from a higher level to a lower level. The reason to
split stories is that sometimes stories are too big to
construct in an iteration. Once the stories have been
sliced, these need to be added to the product backlog
where they will be prioritized for development.
[The PMI Guide to Business Analysis, page 214]
[Planning]
26. D - Business requirements describe the higher-level
needs of the organization as a whole, such as the business
issues or opportunities. Other choices are much lower
level requirements. [PMBOK® Guide 6th edition, Page
148] [Analysis]
27. C - Skipping the peer review is not recommended.
The rest of the choices are all peer reviewing methods. A
peer desk check is an informal peer review completed by
one or more peers simultaneously to look over the
materials. The other two methods are more formal and
rigorous.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 224]
[Analysis]
28. A - Requirements management tools allow
requirements and other product information to be captured
and stored in a repository. These tools help maintain audit
trails and perform version control to assist with change
management.
[The PMI Guide to Business Analysis, page 260]
[Traceability & Monitoring]
29. A - A RACI model is a common type of responsibility
assignment matrix that uses Responsible, Accountable,
Consult, and Inform designation to define the involvement
of stakeholders in activities. The rest of the choices do not
have this capability.
[The PMI Guide to Business Analysis, page 118]
[Planning]
30. D - The affinity diagram enables a large number of
ideas to be sorted into groups for further review and
analysis. It is a tool used in gathering of requirements.
[PMBOK® Guide 6th edition, Page 144] [Analysis]
31. D - Changes are inevitable. Acquiring more than
required resources will put a strain on the budget and
might compromise the project’s financial goals. Fast-
tracking always introduces risk to the project. However,
active management of stakeholders almost always
guarantees a decrease in project risk. [PMBOK® Guide
6th edition, Pages 504-506] [Analysis]
32. C - Basic features provide little satisfaction to
stakeholders, but, when missing from the end solution,
cause extreme dissatisfaction. These features need to be
prioritized for development.
[The PMI Guide to Business Analysis, page 80]
[Planning]
33. C - Rolling Wave Planning is a technique used to
create a more detailed work plan while keeping the right
level of detail for each activity; activities happening
https://t.me/PrMaB
sooner have more detail than those further in the future.
[PMBOK® Guide 6th edition, Page 185] [Planning]
34. A - You have already identified the use cases and
developed a use case diagram. The next step is to
complete the definitions of each of the use cases.
[The PMI Guide to Business Analysis, page 214]
[Analysis]
35. B - Project champions are the stakeholders who assist
the project team in building excitement and support for
the project.
[Business Analysis for Practitioners: A Practice Guide,
page 40; The PMI Guide to Business Analysis, page 115]
[Planning]
36. A - These are examples of non-functional
requirements. A non-functional requirement describes the
environmental conditions or qualities required for the
product to be effective. Examples of non-functional
requirements include reliability, security, performance,
safety level of service.
[The PMI Guide to Business Analysis, page 10] [Needs
Assessment]
37. B - The on-demand scheduling approach used in agile
environments is based on the theory-of-constraints and
pull-based scheduling concepts from lean manufacturing
to limit a team’s work in progress. This is also called
Kanban system. [PMBOK® Guide 6th edition, Page 177]
[Traceability & Monitoring]
38. D - You want to solicit the feedback from the SMEs
anonymously to overcome the problem of some SMEs
overpowering the others. The Delphi technique is a
consensus-building method that consolidates anonymous
input from subject matter experts using rounds of voting.
[The PMI Guide to Business Analysis, page 394]
[Analysis]
39. A - A Kano diagram is used to analyze a product’s
features from the viewpoint of the customer. It must be
https://t.me/PrMaB
noted that a Kano diagram does not focus on the reported
issues and defects.
[The PMI Guide to Business Analysis, pages 79]
[Analysis]
40. A - Feature models are typically started at the
beginning of a project to show all the features that are in
scope for a project and is updated as additional features
are identified during elicitation and analysis.
[The PMI Guide to Business Analysis, page 193]
[Analysis]
41. D - The leadership team has asked for a Pareto chart
which is a histogram that has been ordered by the
frequency of occurrence; that shows how many issues
were reported by each identified category. Since you
already have developed a histogram, this implies that you
already have the frequency of occurrence data.
[The PMI Guide to Business Analysis, page 403]
[Analysis]
42. B - Delphi is a consensus-building method that
consolidates anonymous input from subject matter experts
using rounds of voting.
[The PMI Guide to Business Analysis, page 228]
[Analysis]
43. C - A decision table and decision tree are rule models
that show a series of decisions and the outcomes to which
the decisions lead. Decision trees and tables are often used
to model business rules.
[The PMI Guide to Business Analysis, page 189]
[Analysis]
44. B - State table and state diagrams are useful for
solutions involving workflows and can help with the
discovery of business rules that relate to an object moving
from one state to another. The rest of the tools will be
irrelevant to this analysis.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 203]
[Analysis]
45. B - Product box is an elicitation technique that uses
game play to focus on the features of a product that are
important to the customer. None of the rest of the options
are elicitation techniques.
[The PMI Guide to Business Analysis, page 166]
[Analysis]
46. B - In adaptive projects, retrospectives are meetings
that are scheduled on a regular basis or conducted when a
body of work is completed, such as the conclusion of an
iteration or at the end of a project phase. The purpose of a
retrospective is to task the project team with identifying
those areas where team performance can be improved.
[Business Analysis for Practitioners: A Practice Guide,
page 51; The PMI Guide to Business Analysis, page 149]
[Planning]
47. C - During daily planning/stand-ups teams make,
assess, and revise their daily plans. During daily meetings,
teams constrain the planning horizon to be no further
away than the next day, when they will meet again. Daily
meetings are also used to make team commitments.
[The PMI Guide to Business Analysis, page 144, 244]
[Planning]
48. A - Clearly the senior leadership is asking you to
conduct a detailed feasibility study and assemble a
business case demonstrating the alignment with the
organizational strategy. The other choices will become
more important once the project is authorized.
[The PMI Guide to Business Analysis, page 98] [Needs
Assessment]
49. D - Five-whys analysis is a root cause analysis
technique and not a stakeholder identification technique.
The rest of the choices are all valid examples of
stakeholder identification techniques.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, Page 111]
[Planning]
50. B - An Agile team benefits from traditional project
management approaches such as lessons learned
gathering, analysis and documentation; and Lean
approaches such as Kaizen (continuous improvement)
during retrospectives.
[The PMI Guide to Business Analysis, page 149]
[Planning]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) - 9
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 9
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. Your organization has recently adopted Agile practices
and all new internal projects are being managed using
Agile methods. If you want to compare the performance of
three projects, which of the following measures cannot be
used?
A. Actual cost
B. Velocity
D. Percent-completion
https://t.me/PrMaB
her with available options. Assuming you haven’t carried
out any of the following options, what must you do next?
A. Carry out a fresh assessment of project priorities
and present it to the sponsor.
B. Interviews
C. Facilitated workshop
D. Surveys
B. Gantt charts
C. Sprint diagrams
https://t.me/PrMaB
D. Burndown charts
B. Kano analysis
C. 80/20 analysis
D. SWOT analysis
https://t.me/PrMaB
A. You need to spend a considerable amount of time
correcting the business analysis plan.
B. Product backlog
C. Feature model
D. Decision table
https://t.me/PrMaB
D. The project scheduler did not allow enough time
for elicitation.
B. Guinea pig
C. Persona
D. Subject
12. You are analyzing a set of risks and their impacts. You
want to develop a model that will force you to consider
each combination of the risks and document an
appropriate mitigation strategy for each combination.
Which of the following models should you use?
A. Decision Tree
B. Risk Register
C. Decision Table
https://t.me/PrMaB
project stakeholder engagement levels with his project
team on a regular basis. Which of the following is the best
platform where Robert can review this with his team?
A. Phase gates
B. Kill points
C. Validate requirements
https://t.me/PrMaB
16. There are several communication methods used to
share and distribute information to stakeholders, team
members, and management. Which of the following
communication methods is used when you notify the
public about environmental effects from your project after
implementation by posting reports on the project’s
website?
A. Pull communication
B. Interactive communication
C. Push communication
D. Informal communication
https://t.me/PrMaB
C. Request the project sponsor to provide guidance
over the right approach.
C. Business case
D. Project charter
B. Feature Model
C. Data dictionary
D. Decision Tree
https://t.me/PrMaB
A. Assess Current State is a process from the Initiating
Process Group.
B. Decision-making
C. Expert judgment
D. Meetings
23. You are the business analyst for a CRM system design
and development project. The project stakeholders are
time constrained and you want to make best use of their
time in an upcoming elicitation event. Which of the
following would help you make best use of your
stakeholder’s time?
A. Share the agenda and elicitation materials with the
stakeholders and request some prework prior to the
event.
https://t.me/PrMaB
C. Start the elicitation event with a well-defined
agenda and set the ground rules.
B. Backward traceability
C. Regression traceability
D. Periodic traceability
https://t.me/PrMaB
required by the developers to build and test the system. A
number of stakeholder workshops have been conducted in
the past to collect these detailed requirements but the
stakeholders seem to change their mind regarding the
design specifics on almost every occasion as they have no
prior experience of using such a system and are struggling
to specify requirements. How should you resolve this
issue?
A. Apply waterfall-based methods such as use cases to
capture and document system requirements.
C. Backlog refinement
D. Backward traceability
https://t.me/PrMaB
of the following scope analysis techniques can be
utilized?
A. Burndown chart
B. Retrospective
C. Story mapping
https://t.me/PrMaB
C. Engage a third-party facilitator or help the
stakeholders define their requirements.
https://t.me/PrMaB
B. MoSCoW
C. PERT
D. SWOT
B. Value dependency
C. Implementation dependency
D. Subsets
36. Joe has been managing a project for Exton Oil Corp.
This project involves redesigning filling stations across
the state. The redesign involves new gas pumps, security
cameras, convenience stores, and use of environmentally
friendly materials in the construction. While the
redesigning work proceeds, Joe’s design engineer
https://t.me/PrMaB
suggests a secondary alarm system for gas pumps to alert
the attendant in case of a spill. Although this suggestion is
not in the project requirements, Joe is impressed with the
engineer’s recommendation. What should be the next step
for Joe with regard to the engineer’s suggestion?
A. Approve his recommendation and allocate
resources and funds
B. Management style
C. Risk tolerance
D. Communications
https://t.me/PrMaB
B. Commence the development of the product
breakdown structure.
B. Definition of done
C. Kanban board
D. Delphi technique
B. Solution requirement
C. Functional requirement
D. Non-functional requirement
https://t.me/PrMaB
your elicitation results in a concise manner. Which of the
following is the best thing to do?
A. Develop models for the elicited information.
B. Retrospective
C. Spike
D. Sprint planning
https://t.me/PrMaB
44. You are the lead business analyst on a supply chain
management system implementation project in your
organization. The project sponsor tells you that the new
system must be available to all employees so that they
may submit their requisitions. All requisitions must be
approved by the line managers through the system. This is
an example of a:
A. Non-functional requirement
B. Transition requirement
C. Functional requirement
D. Business requirement
D. Validate requirements
https://t.me/PrMaB
D. The affinity diagram will rank the ideas into their
respective priorities.
B. System interactions
C. System requirements
B. Decision Tree
C. Wireframe
D. Ecosystem Map
https://t.me/PrMaB
C. The IRR value of 30% is misleading as you cannot
measure this at this stage.
B. Three years
C. Five years
D. Six years
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) - 9
Answer Key and Explanations
1. B - Any measure can be used to compare performance
as long as the measure is used consistently on all projects.
There is no issue with actual cost as that will be absolute
values. Percent-completion, regardless of how that is
measured, can be used for comparison; i.e., which project
is near completion, etc. SPI and CPI are ratios and can be
used for comparison. However, velocity is relative.
Velocity is measured as story points are delivered per
iteration on average. Since there is no universal measure
for story points and different teams measure user stories
differently, similar effort user stories can have different
story points on two projects. Neither story points nor
velocity can be used for comparison.
[The PMI Guide to Business Analysis, pages 148, 213,
416] [Planning]
2. C - You should meet these executives and try to
understand their expectations prior to escalating this issue
to the sponsor. However, if this hasn’t been done yet, this
needs to be done next. [PMBOK® Guide 6th edition, page
523; PMI Code of Ethics and Professional Responsibility]
[Analysis]
3. B - A facilitated workshop might not be possible
because of the stakeholders’ schedule conflicts and
document analysis is irrelevant to this context. Surveys
and interview are two viable choices, however, interviews,
being face-to-face interactive sessions, will give you better
results in this situation.
[The PMI Guide to Business Analysis, page 61] [Needs
Assessment]
4. D - A burndown chart is the most commonly used
project’s progress presentation tool used by Agile teams.
[The PMI Guide to Business Analysis, page 131]
[Analysis]
https://t.me/PrMaB
5. B - Approved requirements are requirements that are
verified and validated. This doesn’t mean that when
requirements are approved, they are automatically
considered to be verified and validated. The Select and
Approve Requirements process is performed after the
Verify Requirements and Validate Requirements
processes.
[The PMI Guide to Business Analysis, pages 263, 268]
[Traceability & Monitoring]
6. C - The 80/20 principle means that typically 80% of
problems can be related back to 20% of the causes.
Identifying the top 20% of the causes and addressing these
causes will approximately resolve 80% of your problems.
[The PMI Guide to Business Analysis, pages 69] [Needs
Assessment]
7. C - There are a number of factors to consider when
planning for elicitation. Selection of techniques that are
familiar to the business analyst and key stakeholders
involved is acceptable.
[Business Analysis for Practitioners: A Practice Guide,
page 53; The PMI Guide to Business Analysis, page 127]
[Planning]
8. A - A business rule catalog maps each business rule to
the related processes or process steps that enforce the rule
or data models that apply the rules.
[The PMI Guide to Business Analysis, page 212]
[Analysis]
9. C - What is clear from the scenario is that George did
not plan his elicitation activities, otherwise requirements
relating to the higher value features would have been
elicitated first. While the rest of the choices could be true,
the scenario does not provide any evidence that any of
these are true.
[Business Analysis for Practitioners: A Practice Guide,
page 54; The PMI Guide to Business Analysis, page 127]
[Planning]
https://t.me/PrMaB
10. A - Maximizing the business value of the project is an
important skill required of a project manager. However,
this is a business management skill and not considered a
technical project management skill. [PMBOK® Guide,
6th edition, Page 58] [Needs Assessment]
11. C - A persona defines an archetypical user of a
system, an example of the kind of person who would
interact with it. The idea is that if you want to design
effective software, then it needs to be designed for a
specific person.
[The PMI Guide to Business Analysis, page 117]
[Planning]
12. C - A decision table and decision tree are rule models
that show a series of decisions or conditions and their
outcomes. Decision trees visually show the flow of
decisions or conditions. On the other hand, decision tables
are useful for ensuring that the business analyst has
considered all possible combinations of decision or
condition scenarios and related outcomes. This can also
be used to analyze the different combinations of risks as
mentioned in the question.
[The PMI Guide to Business Analysis, page 189]
[Analysis]
13. C - The phase gates and the kill points are the project
reviews that are done at the closure of each phase of the
project. Managing stakeholder engagement levels should
be a continuous process that does not wait for a project
phase to complete. Information management systems can
be used for the exchange of project information, but
project status review meetings are interactive
communication sessions among the project team
members. A project status review meeting provides the
best platform to discuss the current engagement levels of
the project stakeholders. [PMBOK® Guide 6th edition,
Page 535] [Traceability & Monitoring]
14. C - Validate requirements is the process of checking
that the requirements meet business goals and objectives.
https://t.me/PrMaB
Validation is the assurance that a product meets the needs
of the customer and other identified stakeholders.
[The PMI Guide to Business Analysis, page 221]
[Analysis]
15. C - In predictive projects, change control typically
begins after the requirements are approved and not just
when these are just verified or validated.
[The PMI Guide to Business Analysis, page 275]
[Traceability & Monitoring]
16. A - Push communication is used to send information
to specific recipients who need to know. Push
communication is done using letters, faxes, memos, etc.
Pull communication is used for large volumes of
information. The methods for this type of communication
include internet sites and blogs. Since you want to notify
the general public about environmental effects by posting
reports on the project’s website, this is an example of pull
communication methods. [PMBOK® Guide 6th edition,
Page 374] [Planning]
17. B - Throughout the business analysis process, there
are a number of decisions that need to be made before
work can commence. Once the team determines the
decision process, it is documented within the business
analysis plan.
[Business Analysis for Practitioners: A Practice Guide,
page 68; The PMI Guide to Business Analysis, page 127]
[Planning]
18. D - Elicitation is highly cyclical. Even when
elicitation is being performed to understand a single
concept, such as the current state of an existing process,
the processes are iterated through multiple times to obtain
perspectives from different sources.
[The PMI Guide to Business Analysis, page 155]
[Analysis]
19. A - A business analysis plan is created to document
how the business analysis process will be performed,
https://t.me/PrMaB
including the plan decisions agreed to by the project team.
[Business Analysis for Practitioners: A Practice Guide,
page 46; The PMI Guide to Business Analysis, page 129]
[Planning]
20. B - A feature model is a scope model that visually
represents all the features of a solution arranged in a tree
or hierarchical structure.
[The PMI Guide to Business Analysis, page 193]
[Analysis]
21. D - The Assess Current State process belongs to the
Needs Assessment Knowledge Area and the Defining and
Aligning Process Group. This process is performed after
the Identify Problem or Opportunity process. The correct
answer is: The Assess Current State process often occurs
in conjunction with Conduct Elicitation process.
[The PMI Guide to Business Analysis, pages 24, 64]
[Needs Assessment]
22. A - ‘Interpersonal skills’ is not a tool or technique of
the Plan Stakeholder Engagement process. The rest of the
choice are valid tools or techniques. [PMBOK® Guide
6th edition, Page 516] [Planning]
23. A - As the business analyst, you need to set the
agenda and you need to facilitate the event. Starting the
event with a clear agenda and setting the ground rules is a
good practice, but if you want to maximize the value of
your stakeholder’s time, sharing the agenda and elicitation
materials with them prior to the event will be a great idea.
You may also request them to do some prework, for
example, investigate the current system, brainstorm some
requirements, or gather and bring some relevant material
to the workshop.
[The PMI Guide to Business Analysis, page 161]
[Analysis]
24. C - The discounted payback period method removes
the primary disadvantage of the payback period method
by applying appropriate discount factors to each item in
https://t.me/PrMaB
the cash flow stream. All other choices are made-up
terms.
[The PMI Guide to Business Analysis, page 90]
[Planning]
25. B - Backward traceability is performed from the
requirements to the scope features and business goals and
objectives that triggered them. Forward traceability is
performed from the requirements to design and test
components and ultimately, the final product.
[The PMI Guide to Business Analysis, page 253]
[Traceability & Monitoring]
26. C - You have a very specific issue at hand; the
stakeholders are struggling to specify their requirements
through workshops. In projects with such uncertainty,
Agile methods come in handy. Prototyping is used to elicit
and validate stakeholder needs through an iterative
process that creates a model for design of requirements.
[PMBOK® Guide 6th edition, page 133] [Planning]
27. D - Backward traceability is a technique that
establishes the relationship of a requirement to the scope,
business goals, or business objectives from which it
originated.
[The PMI Guide to Business Analysis, page 388]
[Analysis]
28. D - Work Breakdown Structure (WBS) is a planning
technique for projects using a predictive lifecycle. WBS is
a hierarchical decomposition of the total scope of work.
Story mapping is a technique used for adaptive projects.
The other two choices are not scope analysis techniques.
[The PMI Guide to Business Analysis, page 134]
[Planning]
29. C - Adjourning the meeting will be an extreme step.
Seems like the stakeholders have not read or properly
understood the situation statement. It is advisable to walk
them through the situation statement to set the context for
the meeting.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 162]
[Analysis]
30. B - It is not uncommon for business stakeholders to
struggle in trying to articulate their requirements in detail
required for product development. Agile methods solve
this problem by allowing a business analyst to document
the stakeholders needs as user stories and work on
elaborating these stories later.
[The PMI Guide to Business Analysis, page 215]
[Analysis]
31. B - In adaptive life cycles, the requirements are
documented in user stories that are then prioritized and
refined. The product features are developed using time-
boxed periods of work. [PMBOK® Guide 6th edition,
Page 177] [Analysis]
32. B - The outcome of business analysis activities will
give you your lessons learned but the business analysis
plan itself is not updated to the lessons learned library.
Recalling, discarding and including this in the project’s
final report do not make any sense. You need to store this
as an organizational process asset so that future project
and product teams may benefit from it.
[Business Analysis for Practitioners: A Practice Guide,
page 67; The PMI Guide to Business Analysis, page 111]
[Planning]
33. B - Prioritization schemes such as MoSCoW can help
decide which metrics must, should, could, and won’t be
collected.
[The PMI Guide to Business Analysis, page 289]
[Evaluation]
34. D - Sharing lessons learned information on mistakes,
innovations and outcomes from projects can have a
positive impact on your next project. The procurement
specialist came up with a cost- and time-saving technique
and this will prove to be valuable for future projects.
https://t.me/PrMaB
[PMBOK® Guide 6th edition, Page 484] [Traceability &
Monitoring]
35. D - All sliced stories have a subset relationship with
the original story. Other relationship types may or may not
exist, but you need to document the subset links.
[The PMI Guide to Business Analysis, page 261]
[Traceability & Monitoring]
36. B - Change requests should always be recorded in
written form and entered in the change management
system to determine the impact of the change on the
scope, budget, schedule and quality. Thus, Joe must
initiate the formal change control process. After approval
from the change control board, Joe can allocate resources
and funds to implementing the change. Hence, Joe must
initiate the change first. [PMBOK® Guide 6th edition,
Page 113] [Traceability & Monitoring]
37. D - An effective stakeholder engagement plan
recognizes the diverse information needs of the project’s
stakeholders. Stakeholder engagement relies on
continuous communication with stakeholders to
understand their needs and expectations, addressing issues
as they occur, managing conflicts and fostering
stakeholder engagement. [PMBOK® Guide 6th edition,
Page 518] [Needs Assessment]
38. C - Once the business analysis plan is completed, the
business analyst reviews the plan with the key project
stakeholders. The objective for the review is to reduce the
risk of stakeholders failing to support business analysis
activities when the work begins. Commencing the
requirements elicitation process or developing the product
breakdown structure without having the business plan
reviewed and approved will be risky.
[Business Analysis for Practitioners: A Practice Guide,
page 67; The PMI Guide to Business Analysis, page 127]
[Planning]
39. D - Delphi is a consensus-building technique.
Stakeholders participate in this technique anonymously.
https://t.me/PrMaB
This uses rounds of anonymous voting till common
ground is found.
[The PMI Guide to Business Analysis, page 265]
[Traceability & Monitoring]
40. A - A business requirement describes the higher-level
needs of an organization such as business issues and
opportunities. On the other hand, solution requirements
describe the features, functions and characteristics of a
product that will meet a business requirement. Functional
and non-functional requirements are types of solution
requirements. In this case, the requirement to implement
an ERP system is a business requirement.
[The PMI Guide to Business Analysis, page 10] [Needs
Assessment]
41. A - Models are visual representations of information,
in the form of diagrams, tables, or structured text, that
effectively arrange and convey a lot of information in a
concise manner. Developing models for the elicited
information is the best option for you.
[The PMI Guide to Business Analysis, page 184]
[Analysis]
42. B - The business analysis work plan is a
subcomponent of the business analysis plan. The business
analysis work plan is ultimately integrated with the
project management plan. The first step in building the
plan is identifying the deliverables that the business
analyst is responsible for producing.
[Business Analysis for Practitioners: A Practice Guide,
page 61; The PMI Guide to Business Analysis, page 146]
[Planning]
43. A - Story elaboration is the process by which user
stories are supplemented with additional information from
conversation with business stakeholders, until they are
sufficiently detailed for product development to begin.
[The PMI Guide to Business Analysis, page 219]
[Analysis]
https://t.me/PrMaB
44. C - This is an example of a functional requirement.
Functional requirements describe the functionality and the
behavior of the system.
[The PMI Guide to Business Analysis, page 10] [Needs
Assessment]
45. A - Verify requirements is the process of checking
that requirements are of sufficient quality.
[The PMI Guide to Business Analysis, page 221]
[Analysis]
46. B - Affinity diagrams display categories and
subcategories of ideas that cluster or have an affinity to
one another. These are used to process a large amount of
information or ideas into a manageable set of data
organized by categories.
[The PMI Guide to Business Analysis, page 77] [Analysis]
47. C - This is an example of a context diagram. A
context diagram defines the boundary between the system
and its environment. This diagram is a high-level view of
a system. The context diagram is an example of a scope
model. It shows the system boundary, the actors and their
interactions. However, the context diagram doesn’t
capture system requirements. [PMBOK® Guide, 6th
edition, Page 146] [Planning]
48. D - An ecosystem map is a scope model that shows all
the relevant systems, the relationships between the
systems, and optionally, any data objects passed between
them. None of the other choices are the models that are
relevant in this context.
[The PMI Guide to Business Analysis, page 190]
[Analysis]
49. B - The higher the IRR, the better. During the post-
implementation review we consider the result of an actual
versus expected cost-benefit analysis to assess the
business value of the solution. In this case, the product
exceeded its targeted financial performance.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 283]
[Evaluation]
50. C - The total returns at the end of fourth year =
$22,961 x 4 = 91,844, while the total returns at the end of
the fifth year = $22,961 x 5 = $114,805. In order to
recover the full initial investment, you need to wait till the
end of fifth year.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
https://t.me/PrMaB
PMI-PBA DOMAIN AREA
TEST: ANALYSIS
PRACTICE QUESTIONS
Test Name: Domain Area Test: Analysis
Total Questions: 20
Correct Answers Needed to Pass:
14 (70.00%)
Time Allowed: 30 Minutes
Test Description
This practice quiz specifically targets your knowledge of the
Analysis PMI-PBA Domain area.
Test Questions
1. You are leading the business analysis activities for a
new product development project. You have collected all
business requirements and are ready to transform these
into solution requirements. Which of the following models
will help you transform the business requirements into
solution requirements?
A. Use cases
B. Fishbone diagram
C. Context diagram
D. Decision trees
https://t.me/PrMaB
you want to show the steps and tasks different people
perform in this workflow?
A. Swim lane diagram
B. Sailboat diagram
C. Waterfall diagram
D. Speedboat diagram
B. Neutral stakeholders
C. Leading stakeholders
D. Unaware stakeholders
https://t.me/PrMaB
The metrics will be used to describe who or what has
permission to perform each of the CRUD operations on
elements, such as data or user interfaces. CRUD stands
for:
A. Customizability, Reliability, Uniformity, and
Durability
C. Sensitivity Analysis
D. Process Analysis
B. Feedback-based skills
C. Soft skills
D. Ad hoc skills
https://t.me/PrMaB
8. Which of the following is the Elicitation process of
organizing and scheduling resources and preparing
necessary materials for an individual elicitation activity?
A. Conduct Elicitation
B. Pareto chart
D. Data dictionary
B. Fishbone diagram
C. Business case
D. Interaction matrix
https://t.me/PrMaB
11. Which of the following is a correct format to
document acceptance criteria for user stories in a
behavior-driven development approach?
A. Given-when-then format
C. If-then-else format
D. Left-middle-right format
B. Sailboat
C. Speedboat
D. Spider web
https://t.me/PrMaB
A. Introduction, body, and close
B. Process Flow
C. Report Table
B. SWOT analysis
D. Context diagram
https://t.me/PrMaB
C. A team’s burndown is rarely perfectly smooth.
https://t.me/PrMaB
items that exist on the organizational product catalog.
However, if the request is regarding a non-catalog item, a
secondary approval workflow is required to be appended
to the primary approval workflow. Which section of the
use case will you use to document the primary approval
workflow?
A. Postconditions
B. Alternative flow
C. Preconditions
D. Normal flow
https://t.me/PrMaB
PMI-PBA Domain Area Test: Analysis
Answer Key and Explanations
1. A - Use case modeling is frequently used to identify
and elaborate requirements, especially when moving from
business requirements to stakeholder requirements or
solution requirements.
[The PMI Guide to Business Analysis, page 214]
[Analysis]
2. A - Process flows are in the process model category
and are used to visually document the steps or tasks that
people perform in their jobs or when they interact with a
system. Other names for process flows are swim lane
diagrams, process maps, process diagrams, or process flow
charts.
[The PMI Guide to Business Analysis, page 198]
[Analysis]
3. A - Encode -> Transmit -> Decode -> Acknowledge -
> Feedback is the right sequence. [PMBOK® Guide 6th
edition, Page 371, 372] [Analysis]
4. A - Neutral and unware stakeholders usually don’t
pose any serious threat but they are volatile and can sway
in any direction as more information becomes available to
them. Leading stakeholders are beneficial for the project
as long as they are limited in number. If the size of the
group is large this can be damaging. The supportive
stakeholders are usually low in potential to affect the
project but high in potential for collaboration. This is an
ideal stakeholder group that supports the project’s goals
and objectives. [PMBOK® Guide 6th edition, Page 521]
[Analysis]
5. D - CRUD stands for (C) Create, (R) Read, (U)
Update, and (D) Delete.
[The PMI Guide to Business Analysis, page 393]
[Analysis]
https://t.me/PrMaB
6. D - Process Analysis examines problems, constraints,
and non-value-added activities that occur during project
work. [PMBOK® Guide 6th edition, Page 292] [Analysis]
7. C - Interpersonal skills, sometimes known as “soft
skills,” are particularly important to team development. By
understanding the sentiments of project team members,
anticipating their actions, acknowledging their concerns,
and following up on their issues, the project management
team can significantly reduce problems and increase
cooperation. [PMBOK® Guide 6th edition, Page 357]
[Analysis]
8. B - Prepare for Elicitation is the process of organizing
and scheduling resources and preparing necessary
materials for an individual elicitation activity. This should
not be confused with the Determine Elicitation Approach
process which is the process of thinking through how
elicitation activities will be conducted, which stakeholders
will be involved, which techniques may be used, and the
order in which the elicitation activities are best performed.
[The PMI Guide to Business Analysis, page 159]
[Analysis]
9. A - A feature model is a scope model that visually
represents all the features of a solution arranged in a tree
or hierarchical structure. The other choices do not show
the hierarchy of a product’s features.
[The PMI Guide to Business Analysis, page 193]
[Analysis]
10. D - An interaction matrix is a lightweight version of a
traceability matrix that is used to figure out whether
requirements are sufficiently detailed or if any entities are
missing. In an interaction matrix, the rows are one type of
product information, typically in the form of use cases,
user stories, or process flows. The columns of the matrix
are the names of a different type of product information,
such as data entity, business rule, or user interface. You
can use an interaction matrix to validate that all approved
requirements are covered in one or more use cases.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 196]
[Analysis]
11. A - The behavior-driven development approach
includes a commonly accepted syntax to write acceptance
criteria for user stories; the given-when-then format.
[The PMI Guide to Business Analysis, page 219]
[Analysis]
12. D - Executing Process Group involves processes
performed to elicit, analyze, model, define, verify,
validate, prioritize, and approve all types of product
information, ranging from backlogs to user stories and
requirements to constraints.
[The PMI Guide to Business Analysis, page 21] [Analysis]
13. A - Product box is an elicitation technique that uses
game play to focus on the features of a product that are
important to the customer. It divides the participants into
teams, asking each team to design a box that represents
how the product would be packaged.
[The PMI Guide to Business Analysis, page 166]
[Analysis]
14. A - There are three stages during an elicitation
activity that are applicable regardless of the elicitation
technique used: introduction, body, and close.
[The PMI Guide to Business Analysis, page 165]
[Analysis]
15. C - A report table is an interface model that describes
detailed requirements for a single report. Report tables
contain both information about the report, such as the
report name or decisions made from the report, and field-
level information, such as which data fields are displayed
and any calculations.
[The PMI Guide to Business Analysis, page 201]
[Analysis]
16. C - The goal model and business objectives models
describe the business objectives that the solution is meant
https://t.me/PrMaB
to achieve, along with the high-level features for the
solution. Either model can be used as a tool to help
prioritize the requirements according to how much they
support or achieve the objectives.
[The PMI Guide to Business Analysis, page 233]
[Analysis]
17. B - A release burndown chart shows the number of
story points or ideal days remaining in the project as of
the start of each iteration. A team’s burndown is never
perfectly smooth. It will vary because of inaccurate
estimates, changed estimates, and changes in scope. A
burndown chart can help in forecasting the project
completion but the forecast is usually not very accurate.
[The PMI Guide to Business Analysis, page 131]
[Analysis]
18. C - CRUD, defined as create (C), read (R), update
(U), and delete (D), represents the operations that can be
applied to data or objects. CRUD matrices describe who
or what has permission to perform each of the CRUD
operations on elements, such as data or user interface
screens.
[The PMI Guide to Business Analysis, page 197]
[Analysis]
19. D - If the number of story points added offsets the
number of story points delivered, the remaining story
points on the project will not change. The slope of the
burndown line will become zero and the line will become
perfectly flat in the horizontal direction.
[The PMI Guide to Business Analysis, page 131]
[Analysis]
20. D - Each use case contains a normal flow, which is the
most common scenario of interactions between the system
and user, as well as alternative and exception flows, where
the scenario diverges from the normal flow. In this
scenario, the primary approval workflow needs to be
documented as the normal flow of the use case.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 214]
[Analysis]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) – 10
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 10
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. Your project’s scope was earlier represented by epics.
However, these have now been replaced with user stories.
What is the relationship between epics and user stories?
A. Discretionary dependency
B. Subsets
C. Implementation dependency
D. Value dependency
https://t.me/PrMaB
B. Kanban boards and daily stand-ups
https://t.me/PrMaB
key difference between Validate Scope and Control
Quality is:
A. Validate Scope can never be performed in parallel
with Control Quality.
B. Validate requirements
D. Verify requirements
https://t.me/PrMaB
You find out there are several uncertainties associated with
the product requirements. An uncertainty that can affect
success in definition, development, and expected results of
the product or solution is called:
A. Product risk
B. Assumption
C. Constraints
D. Feasibility
https://t.me/PrMaB
C. Scope Verification Plan
D. Project Charter
B. Pareto charts
C. Fishbone diagram
D. Burndown charts
B. Curing
C. Harvesting
D. Tailoring
https://t.me/PrMaB
12. You are the business analyst on a new product
development project. You have completed all product
requirements elicitation activities and recently developed
an entity relationship diagram for the product. Which of
the following artifacts should you send to the database
designer alongside the ERD so that she can start designing
the database for the product?
A. Interaction matrix
B. CRUD matrix
C. Traceability matrix
D. Feature model
B. Autocracy
C. Plurality
D. Unanimity
https://t.me/PrMaB
requirements from your stakeholders. Proof of concept is
an example of:
A. Prototyping
B. Multi-voting
D. Brainstorming
https://t.me/PrMaB
C. Increase the budget and timeline for all projects so
that the resources can be efficiently shared.
B. Project charter
C. Business case
https://t.me/PrMaB
projects, which of the following artifacts can be used to
initiate the project?
A. Project management plan
B. Project charter
C. Scope statement
B. Functional requirements
C. Project requirements
D. Non-functional requirements
https://t.me/PrMaB
need to gather performance data. When would you collect
system performance data for this exercise?
A. Performance data during the release
B. Requirements documentation
D. WBS Dictionary
https://t.me/PrMaB
project and identify the root cause of this failure. The
review of the acceptance testing results disclosed that the
product requirements were not adequately prioritized
before the development started. Which of the following
project documents should you review next to review the
product’s requirements prioritization criteria?
A. The organization strategy
B. Plan-Act-Check-Do
C. Plan-Do-Check-Act
D. Check-Plan-Do-Act
https://t.me/PrMaB
D. This will be helpful when the team will be
requesting an extension of time for the project.
B. Prototyping
C. Interviews
D. Facilitated workshops
https://t.me/PrMaB
well-received by your customers. You have invited a few
SMEs for a workshop to identify the product features that
customers find problematic. You are planning to use the
speedboat technique during the workshop to identify these
problems. On a speedboat diagram, where do you
document the problems?
A. Sails of the boat
https://t.me/PrMaB
B. Transformational
C. Servant leader
D. Laissez-faire
https://t.me/PrMaB
35. You are conducting a product requirement review
workshop and seeking approval of some key
requirements. During the workshop, a conflict has
emerged between the stakeholders with regards to the
approval of a specific product requirement. Some
stakeholders are in favor or the requirement and some are
against. There is also a small number of stakeholders who
are indifferent. You ask the stakeholders to vote for or
against the requirement. You will consider the
requirement approved if the biggest group of stakeholders
is willing to approve it. What decision-making style have
you adopted?
A. Plurality
B. Unanimity
C. Majority
D. Autocracy
B. Job analysis
C. Seven wastes
D. Kaizen
https://t.me/PrMaB
not appreciate the tool. Which of the following is a
potential root cause of this situation?
A. The product was released early
https://t.me/PrMaB
C. Since the project is in execution, tell the project
manager to take the necessary steps.
B. Iteration risk
C. Developer-hours
D. Sprint duration
https://t.me/PrMaB
42. You are a lead business analyst in a team that is
developing a new technological system. The team has just
completed the first sprint of the project and preparing to
start the second. You think that it is the right time for the
team to reflect and review current stakeholder
engagement and communication approach. What should
you do next?
A. Update the stakeholder register.
B. Progressive Elaboration
C. Expert Judgment
D. Regressive Elaboration
B. Definition of Ready
C. Assumptions
D. Definition of Done
https://t.me/PrMaB
45. You are writing an auto report generation use case. In
case the inventory levels fall below a certain point, the
system is required to automatically generate a report
containing the current stock levels to the warehouse
supervisor. If the warehouse supervisor does not read the
report in the next twenty-four hours, a copy of the report
is sent to the procurement manager. Details regarding the
report’s auto-generation event needs to be documented as
the:
A. Normal flow
B. Alternate course
C. Trigger
D. Precondition
B. Event List
C. State Diagram
https://t.me/PrMaB
D. Display-action-response model
B. Context diagram
C. User stories
D. Persona analysis
D. CRUD matrix
B. Iteration planning
C. Daily standups
D. Retrospectives
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) – 10
Answer Key and Explanations
1. B - Discretionary dependency is a concept in project
scheduling; this dependency exists between project tasks
and not product requirements. The rest of the choices are
all valid product requirements relationship types. Epics are
broken down into smaller user stories, hence the
relationship between them is “subsets”.
[The PMI Guide to Business Analysis, page 259]
[Traceability & Monitoring]
2. B - Help the team learn that they self-manage their
work. Consider Kanban boards to see the flow of work.
Consider a daily stand-up to walk the board and see what
work is where.
[The PMI Guide to Business Analysis, page 144, 233,
244] [Planning]
3. C - The change request needs to be approved through
the Perform Integrated Change Control process prior to
making the change through the Control Procurements
process. Approved change requests from the Perform
Integrated Change control process are inputs of the
Control Procurements process. [PMBOK® Guide 6th
edition, Page 493] [Traceability & Monitoring]
4. D - Validate Scope differs from Control Quality in that
Validate Scope is primarily concerned with the acceptance
of the deliverables, whereas Control Quality is primarily
concerned with meeting the quality requirements specified
for the deliverables. [PMBOK® Guide 6th edition, Page
131] [Traceability & Monitoring]
5. D - Verify requirements is the process of checking that
requirements are of sufficient quality.
[The PMI Guide to Business Analysis, page 221]
[Analysis]
https://t.me/PrMaB
6. D - The scope of the project should be of your least
concern during the design of a change control process. The
rest of the choices are all valid considerations for the
design of this process.
[The PMI Guide to Business Analysis, page 255]
[Traceability & Monitoring]
7. A - Product risk is an uncertainty that can affect
success in definition, development, and expected results of
the product or solution.
[The PMI Guide to Business Analysis, page 406]
[Analysis]
8. C - Minimum Viable Product (MVP) is a prioritization
mechanism to define the scope of the first release of a
solution to customers by identifying the fewest number of
features or requirements that would constitute a solution
that the customer would obtain value from.
[The PMI Guide to Business Analysis, page 401]
[Analysis]
9. B - The project scope statement documents and
addresses the characteristics and boundaries of the project
and its associated products and services, as well as product
acceptance criteria and scope control. [PMBOK® Guide
6th edition, Page 154] [Planning]
10. D - A burndown chart is a graphical representation
used to count the remaining quantity of some trackable
aspect of a project over time, such as user stories. The rest
of the tools are not capable of showing progress over
time.
[The PMI Guide to Business Analysis, page 131]
[Traceability & Monitoring]
11. D - PMI calls this tailoring business analysis.
[The PMI Guide to Business Analysis, page 25] [Needs
Assessment]
12. B - CRUD, defined as create (C), read (R), update
(U), and delete (D), represents the operations that can be
https://t.me/PrMaB
applied to data or objects. CRUD matrices describe who
or what has permission to perform each of the CRUD
operations on elements, such as data or user interface
screens.
[The PMI Guide to Business Analysis, page 197]
[Analysis]
13. C - Majority is reached when more than 50% of
people are in support of an outcome. Plurality is obtained
by the taking the most common answer received from the
decision makers; the number of votes are more than any
other but does not receive a majority.
[The PMI Guide to Business Analysis, page 267]
[Traceability & Monitoring]
14. A - Group decision-making techniques, brainstorming
and multi-voting techniques do not involve any visual
communication approach. Prototyping uses models that
provide a visual representation of what may eventually
evolve into a product’s design. Prototypes are also known
as proofs of concept (PoC).
[The PMI Guide to Business Analysis, page 168]
[Planning]
15. B - The indifferent features are the ones that neither
satisfied nor dissatisfied the customers.
[The PMI Guide to Business Analysis, page 80] [Needs
Assessment]
16. D - Projects compete for resources and the solution to
this problem is prioritization. However, project
prioritization is not always dependent on ROI (e.g., for
some projects the ROI calculation is difficult due to
intangible benefits). It is recommended to prioritize the
projects based on business value. [PMBOK® Guide 6th
edition, page 7] [Traceability & Monitoring]
17. C - The business case describes pertinent information
to determine whether the initiative is worth the required
investment. It is an authoritative source where expected
benefits have been stated.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 281]
[Evaluation]
18. D - INVEST is an acronym for Independence,
Negotiable, Valuable, Estimable, Small and Testable.
[The PMI Guide to Business Analysis, page 223]
[Analysis]
19. B - Not all business problems or opportunities require
a formal business case. In the absence of a formal
business case, a project charter can be used to initiate a
project.
[The PMI Guide to Business Analysis, page 98] [Needs
Assessment]
20. C - Project and project quality requirements are not
part of the business analysis effort and are not considered
to be product requirements.
[The PMI Guide to Business Analysis, page 10] [Needs
Assessment]
21. A - Obtain Solution Acceptance for Release is the
process of facilitating a decision on whether to release a
partial or full solution into production and eventually to
an operational team.
[The PMI Guide to Business Analysis, page 294]
[Evaluation]
22. C - Performance data are used to determine the actual
business value of a product by assessing the performance
data before and after a release.
[The PMI Guide to Business Analysis, page 282]
[Evaluation]
23. D - For complex projects, where progressive
elaboration is required, elicitation is performed iteratively
with analysis, and this is done throughout the project
lifecycle. However, you can consider your elicitation
activities completed at a point in time when the team does
not need any further information or clarification from the
stakeholders.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 155]
[Analysis]
24. B - Project requirements documentation is used as an
input to define the project’s scope baseline. However, the
requirements documentation is not a part of the scope
baseline. [PMBOK® Guide 6th edition, Page 161]
[Planning]
25. B - When building the business analysis plan, the
business analyst should include an explanation as to how
prioritization will be conducted for the project. You
should review the business analysis plan to determine the
product’s requirements prioritization criteria.
[Business Analysis for Practitioners: A Practice Guide,
page 55; The PMI Guide to Business Analysis, page 127]
[Planning]
26. C - Deming’s model is Plan-Do-Check-Act.
[PMBOK® Guide 6th edition, Page 275] [Traceability &
Monitoring]
27. A - Business analysis planning achieves buy-in and
support for the business analysis process before the work
begins. Although a project’s success is dependent on
adequate business analysis, having a business plan alone
cannot guarantee the success of the project. The other two
choices are absurd.
[Business Analysis for Practitioners: A Practice Guide,
page 38; The PMI Guide to Business Analysis, page 127-
129] [Planning]
28. B - On projects that use a predictive life cycle, once
the baseline has been established, changes can only be
made by performing the change management procedures
defined for the project.
[The PMI Guide to Business Analysis, page 264]
[Traceability & Monitoring]
29. A - Since the stakeholders are struggling to envision
how the future system will work, conducting workshops
and interviews will not provide the desired results.
https://t.me/PrMaB
Further, since you are also struggling to understand how
the current system works, you will not be able to develop
a prototype. Your best bet, in this case, is to observe the
current manual system and see how the current processes
are performed.
[The PMI Guide to Business Analysis, page 168]
[Analysis]
30. D - Speedboat is an elicitation technique that uses
game play to elicit information about product features that
customers/stakeholders find problematic. All identified
problems are documented on the anchors of the boat.
[The PMI Guide to Business Analysis, page 166]
[Analysis]
31. C - In a predictive project, the Collect Requirements,
Define Scope and Create WBS processes are performed
toward the beginning of the project and updated as
necessary, using the integrated change control process.
[PMBOK® Guide 6th edition, Page 131] [Analysis]
32. D - Laissez-faire leadership, also known as delegated
leadership, is a type of leadership style in which leaders
are hands-off and allow group members to make the
decisions. Researchers have found that this is generally
the leadership style that leads to the lowest productivity
among group members. [PMBOK® Guide 6th edition,
Page 65] [Analysis]
33. D - High-fidelity prototypes are functional
representations of the final finished solution to the user.
High-fidelity prototyping is performed using a
programming language or a pseudo language of the
solution to be demonstrated.
[The PMI Guide to Business Analysis, page 398]
[Analysis]
34. A - On projects using an adaptive life cycle,
requirements are effectively baselined when they are
identified as planned work to be addressed in the next or
subsequent iteration.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 264]
[Traceability & Monitoring]
35. A - This is example of plurality; you reach a decision
by taking the most common answer received from among
the decision makers.
[The PMI Guide to Business Analysis, page 267]
[Traceability & Monitoring]
36. B - The scenario is asking about a technique that will
help you understand how the work is currently performed.
The business analyst used the job analysis to understand
how the existing job is currently performed. Seven wastes
and Kaizen are process improvement techniques. Personal
analysis is irrelevant.
[Business Analysis for Practitioners: A Practice Guide,
page 44; The PMI Guide to Business Analysis, page 115-
116] [Planning]
37. B - Acceptance criteria are concrete and demonstrable
conditions that must be met for the business stakeholders
or customers to accept the item. Since the product team
developed the product in isolation, stakeholder
dissatisfaction at the time of UAT is not a surprise.
[The PMI Guide to Business Analysis, page 292]
[Evaluation]
38. B - Organizational goals define the measurable targets
that a business establishes in order to deliver on its
strategy. Objectives are the statements aimed at directing
the actions of the organization to reach its goals.
[The PMI Guide to Business Analysis, page 65] [Needs
Assessment]
39. A - As soon as you are made aware of such changes,
you need to reconduct stakeholder analysis and update the
stakeholder register with the changes. These changes must
also be discussed with the project manager.
[The PMI Guide to Business Analysis, page 115]
[Planning]
https://t.me/PrMaB
40. A - The amount of effort required to deliver a user
story is known as story size. Teams consider story size so
that they do not try to commit to more stories than there is
team capacity.
[The PMI Guide to Business Analysis, page 133]
[Planning]
41. C - The Kano analysis explores a product’s features
from the viewpoint of the customer. Basic features
provide little satisfaction to the customers, but, when
missing from the end solution, cause extreme
dissatisfaction. On the other hand, the absence of
delighters and indifferent features do not cause
dissatisfaction. Features in the reverse category should not
be developed at all.
[The PMI Guide to Business Analysis, page 80] [Analysis]
42. D - Retrospectives and lessons learned use past
experience to plan for future work. An optimal
stakeholder engagement and communication approach
may consider recommendations provided from past
projects or prior iterations. You need to call a
retrospective meeting so that the team can review the
current stakeholder engagement and communication
approach.
[The PMI Guide to Business Analysis, page 126]
[Planning]
43. B - Rolling wave is a form of progressive elaboration
planning, where the near-term work is planned in detail
and the work for the far future is planned at a much higher
level. As the project progresses, the subsequent
milestones are planned in greater and greater detail.
[PMBOK® Guide 6th Edition, Page 185] [Planning]
44. D - Definition of Done (DoD) is a series of conditions
that the entire team agrees to complete before an item is
considered sufficiently developed to be accepted by the
business stakeholders.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 394]
[Analysis]
45. C - The trigger of a use case describes the event that
causes the use case to start.
[The PMI Guide to Business Analysis, page 214]
[Analysis]
46. D - The focus of configuration control is on
specification of both the deliverables and the processes.
The rest of the choices are incorrect. [PMBOK® Guide
6th edition, Page 118] [Analysis]
47. A - The state table and state diagram are data models
that show the valid states of an object and any allowed
transitions between those states. State tables model all
states as both a column and a row in a table that allows a
business analyst to systematically consider each potential
state transition (from row to column) to determine if the
transition should be allowed or is not capable of being
transitioned to/from other states. State diagrams, on the
other hand, visually depict the states and transitions, but
only show valid transitions for the object.
[The PMI Guide to Business Analysis, page 203]
[Analysis]
48. D - Persona analysis is a technique that is conducted
to analyze a class of users for understanding their needs
and behaviors. During stakeholder analysis, this technique
is used to analyze how a user class interacts with a system
or how a user class would use a product. The results of
persona analysis can then be used in context diagrams,
user stories and epics.
[Business Analysis for Practitioners: A Practice Guide,
page 45; The PMI Guide to Business Analysis, page 115-
116] [Planning]
49. C - Value stream maps are a variation of process
flows. In addition to information in a traditional process
flow, a value stream map shows delays, queues, or
handoffs that occur during the process. The purpose of a
https://t.me/PrMaB
value stream map is to identify any time spent in the
process that does not add value so it can be streamlined.
[The PMI Guide to Business Analysis, page 198]
[Analysis]
50. B - In adaptive approaches, iteration planning or sprint
planning is the activity used to identify the subset of
product backlog items that the product development team
will work on for the current iteration or sprint.
[The PMI Guide to Business Analysis, page 233]
[Analysis]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) – 11
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 11
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. You have recently taken over leadership of an Agile
team that is halfway through a complicated project. You
have recently examined project requirements and now
want to get an idea of team velocity. Which document
should provide some insight on the team’s velocity?
A. Product backlog
B. Kanban board
C. Definition of done
D. Burndown chart
https://t.me/PrMaB
of user stories have been increasing overtime. This
phenomenon is known as:
A. Scope creep
B. Backsliding
C. Gold plating
D. Change control
B. RACI matrix
C. Spider web
D. Sailboat
C. Manage Communications
D. Monitor Communications
https://t.me/PrMaB
The existing system has specific integration requirements.
Which of the following models should you develop to
document these integration requirements?
A. System Interface Table
B. Context Diagram
C. State Diagram
D. User Story
B. Feature model
D. Project charter
B. Java
C. COBOL
D. Visual C++
https://t.me/PrMaB
8. You recently completed all product requirements
elicitation activities for your project. You have
documented all the requirements as user stories and added
them to the product backlog. Which of the following
techniques will now help you sequence these stories based
upon their business value and the order in which their
users typically perform them?
A. MoSCoW analysis
B. Prototyping
C. Story mapping
D. Kano analysis
B. The Agile team will select the stories for the sprint.
B. Five Whys
https://t.me/PrMaB
C. Pareto diagram
D. Fishbone diagram
D. User Stories
B. Data dictionary
https://t.me/PrMaB
C. Context diagrams
D. Ecosystem maps
B. Project charter
C. Stakeholder register
D. Business case
https://t.me/PrMaB
following is the correct sequence of conducting a
retrospective meeting?
A. Plan -> Do -> Act -> Check
B. Set the stage -> Gather data -> Generate insights ->
Decide what to do
18. You project is under audit. The lead auditor has asked
you to demonstrate that all product backlog items are
aligned with the business goals and objectives. What do
you need to do next to meet this requirement?
A. Conduct a root cause analysis of the business needs
and backlog items.
https://t.me/PrMaB
19. You have been recently hired as a PMO Expert in an
organization that has historically delivered projects under
functional managers. You were able to gather necessary
resources to establish a central PMO in the organization
and now you have shifted your attention on standardizing
project management processes. Historically the
organization has stressed quality control processes instead
of scope validation processes. You now have a stiff
challenge to convince the senior leadership that scope
validation is equally important. Why must the Validate
Scope process be completed in a project?
A. To determine whether the scope is at the correct
complexity level
B. Stakeholder register
https://t.me/PrMaB
21. Which of the following techniques can ensure that the
stakeholders are engaged at appropriate project phases
and to obtain or confirm their continued commitment to
the success of the project?
A. Managing project team
D. Performance audits
B. Context diagram
C. Feature model
D. Traceability matrix
https://t.me/PrMaB
C. Commence the requirements elicitation
D. Project charter
https://t.me/PrMaB
26. Your organization is currently planning to develop a
new product. The product, if successful, could provide
significant competitive advantage to your organization.
Which of the following techniques would you use if you
want to determine the dollar value of the investment in the
product in today’s dollar value considering the cash
inflows, outflows, the time value of these flows?
A. NPV
B. ROI
C. IRR
D. PBP
B. Definition of Scrum
C. Definition of Done
D. Definition of Ready
https://t.me/PrMaB
D. The biggest features that do not add any customer
value.
B. Feature Model
C. Context Diagram
D. Ecosystem Map
https://t.me/PrMaB
A. Nominal group
B. Brainstorming
C. Affinity diagram
D. Delphi
B. Kano model
D. Kanban board
C. Waterfall development
https://t.me/PrMaB
34. You are responsible for managing the upgrade of an
assets management system. You want to determine the
access requirements for a large number of users. These
users are geographically dispersed and in different time
zones. Which of the following is the best tool to be used if
you need to quickly elicit some basic access requirements
from this group?
A. Focus groups
B. Interviews
C. Facilitated workshops
D. Questionnaires
D. Prototype
https://t.me/PrMaB
37. You have recently taken over a project that is in the
execution phase. The first set of deliverables is ready for
customer inspection and you are now looking for the
approved process that needs to be followed. A process
that states how formal validation and acceptance of the
completed project deliverables will be achieved is
documented in the:
A. Scope Management plan
B. Formal
C. External
D. Horizontal
39. You are working for a consulting firm that has been
engaged by a fast-moving consumer goods company to
assess its manufacturing processes. A number of defects
have been reported in the manufacturing process and you
have conducted a thorough root cause analysis of the
situation. Which of the following diagrams can be used to
communicate the results of your root cause analysis?
A. Kano diagram
B. WBS
https://t.me/PrMaB
C. Pareto diagram
D. PERT charts
B. Feature model
C. PERT diagram
D. Fishbone diagram
https://t.me/PrMaB
A. Schedule these between the Needs Assessment and
the Analysis stages.
D. Context Diagram
https://t.me/PrMaB
cases for specifying all product requirements. Which of
the following is a limitation of use cases?
A. Use cases are not well-suited for capturing non-
interaction-based requirements.
C. RACI matrix
D. Interaction matrix
https://t.me/PrMaB
B. Have each change approved or rejected through a
formal change control process.
B. Decision tree
D. Wireframe
https://t.me/PrMaB
50. You have been hired to review a business analysis
guide an organization has developed to uplift their
business analysis skills and to standardize their business
development activities. You are not happy with some of
the recommended product requirements prioritization
techniques given in the guide. Which of the following
technique is irrelevant when it comes to product
requirements prioritization?
A. Multivoting
B. WBS
C. Timeboxing
D. MoSCoW
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) – 11
Answer Key and Explanations
1. D - You need to have a look at the burndown chart.
The burndown chart will tell the number of story points
remaining and the current team’s velocity. Teams might
update velocity on a Kanban board, but this is not a
common practice.
[The PMI Guide to Business Analysis, page 131]
[Analysis]
2. B - Backsliding is a circumstance in a burndown chart
with the remaining quantity of what is being tracked
increases overtime.
[The PMI Guide to Business Analysis, page 388]
[Analysis]
3. A - Speedboat is an elicitation technique that uses
game play to elicit information about product features that
customers/stakeholders find problematic. None of the rest
of the choices facilitate such type of analysis.
[The PMI Guide to Business Analysis, page 166]
[Analysis]
4. B - Project change logs are an output of the Perform
Integrated Change Control process. [PMBOK® Guide 6th
edition, Page 113] [Analysis]
5. A - A system interface table is an interface model that
captures all the detailed level requirements for a single
system interface. System interface tables are created for
each system that interfaces to the solution system.
[The PMI Guide to Business Analysis, page 205]
[Analysis]
6. C - A decomposition mode is used to identify business
analysis tasks, activities, and deliverables by detailing out
the business analysis work. These outputs are ultimately
sequenced into a business analysis work plan.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 132]
[Planning]
7. A - From the given choices, only Business Process
Modeling Notation (BPMN) is a modeling language. The
rest are programming languages.
[The PMI Guide to Business Analysis, page 402]
[Analysis]
8. C - Story mapping is a technique used to sequence
user stories based upon their business value and the order
in which their users typically perform them.
[The PMI Guide to Business Analysis, page 261]
[Traceability & Monitoring]
9. A - The product owner prioritizes and ranks the
product backlog. Neither the team, nor the scrum master
has the authority to reprioritize this list. Unless there are
any technical limitations, stories from the top of the
backlog are always selected for the next sprint.
[The PMI Guide to Business Analysis, page 273]
[Traceability & Monitoring]
10. C - A Pareto diagram helps demonstrate the 80/20
principle whereby 80% of the problems can be related
back to 20% of the causes. Fishbone diagrams and Five
Whys analysis are root cause analysis techniques, which
might be helpful in analyzing the opportunities further.
However, since the question is asking you to identify the
tool that would help you with the 80/20 analysis, the
correct answer is Pareto diagram.
[The PMI Guide to Business Analysis, page 69] [Needs
Assessment]
11. D - User stories are a method to document stakeholder
requirements from the user’s point of view with a focus
on the value or benefit achieved by the user with the
completion of that story.
[The PMI Guide to Business Analysis, page 215]
[Analysis]
https://t.me/PrMaB
12. C - Each user story should have its own acceptance
criteria.
[The PMI Guide to Business Analysis, page 215]
[Analysis]
13. A - Context diagrams and ecosystem maps are
developed at a high-level which is generally not suitable
for test case development. Decision tables and decision
trees are useful as a foundation for test case creation, with
each combination of decision and outcome being a test
case.
[The PMI Guide to Business Analysis, page 189]
[Analysis]
14. C - Confirming elicitation results directly during
elicitation is not preferred when key stakeholders send
delegates or subordinates to participate in the elicitation
activity on their behalf. All other choices are incorrect. If
the key stakeholders lack the product knowledge, other
tools such as prototyping should be used. Project’s cost
and schedule performance should not dictate the
performance of this process.
[The PMI Guide to Business Analysis, page 171]
[Analysis]
15. C - Stakeholder analysis is a technique used to
systematically gather and analyze quantitative and
qualitative information to determine whose interests
should be taken into account throughout the project. The
results of stakeholder analysis are documented in the
stakeholder register.
[The PMI Guide to Business Analysis, page 122]
[Planning]
16. B - In adaptive projects, retrospectives are meetings
that are scheduled on a regular basis or conducted when a
body of work is completed, such as the conclusion of an
iteration or at the end of a project phase. The purpose of a
retrospective is to task the project team with identifying
those areas where team performance can be improved.
https://t.me/PrMaB
Typically, retrospectives use the following steps: Set the
stage -> Gather data -> Generate insights -> Decide what
to do -> Close the Retrospective. Note that retrospectives
are closed with an action plan; these do not include the
action themselves and measuring the results.
[Business Analysis for Practitioners: A Practice Guide,
page 52; The PMI Guide to Business Analysis, page 149]
[Planning]
17. B - A traceability matrix is a grid that links product
requirements from their origin to the deliverables that
satisfy them. The matrix can support linkages among
many different types of objects, providing a mechanism
for tracking product information through the project and
product life cycles.
[The PMI Guide to Business Analysis, page 261]
[Traceability & Monitoring]
18. D - Backward traceability is performed from the
requirements to the scope features and business goals and
objectives that triggered them. Forward traceability is
performed from the requirements to design and test
components and ultimately, the final product.
[The PMI Guide to Business Analysis, page 253]
[Analysis]
19. B - Validate Scope is the process of formalizing
acceptance of the completed project deliverables by the
customer or sponsor of the project. [PMBOK® Guide 6th
edition, Page 163] [Traceability & Monitoring]
20. D - Both the communications and stakeholder
management plans are detailed textual documents. They
are not presentation tools. On the other hand, both the
stakeholder register and the stakeholders engagement
assessment matrix contain the required information.
However, the stakeholders engagement assessment is the
best tool to be selected in this situation since it presents
the information required by the project sponsor in a
tabular format. [PMBOK® Guide 6th edition, Page 521]
[Analysis]
https://t.me/PrMaB
21. C - Stage gate or phase review meetings give project
stakeholders a chance to review project progress and
planned future actions. This gives them a chance to have
their voice heard and recorded. The rest of the choices are
techniques that are internal to a project. [PMBOK® Guide
6th edition, Page 21] [Analysis]
22. A - Process flows can be compared to organizational
charts to ensure that all stakeholders are covered in some
process flow and all people who perform the steps are
covered in the organizational charts.
[The PMI Guide to Business Analysis, page 195]
[Analysis]
23. D - Stakeholder lists can quickly become long and
difficult to manage; therefore, placing stakeholders into
groups based on their characteristics will allow for easier
management of the information. Once this analysis is
complete, the results are then documented in the
stakeholder register.
[The PMI Guide to Business Analysis, page 122]
[Planning]
24. B - The project scope statement is the correct
response. This document describes the project’s
deliverables in detail and the work that is required to
create those deliverables. It also forms the baseline for
evaluating whether requests for changes are within or
outside the project’s boundaries. [PMBOK® Guide 6th
edition, Page 154] [Planning]
25. A - The process of developing a business analysis
work plan is: Identify the deliverables -> Determine the
business analysis tasks and activities -> Determine the
timing and sequencing of tasks ->Determine the roles and
responsibilities -> Identifying the resources -> Estimate
the work. Konrad must get agreement on the list of
business analysis deliverables with the key stakeholders
prior to planning any further business analysis work.
[Business Analysis for Practitioners: A Practice Guide,
page 61-65; The PMI Guide to Business Analysis, page
https://t.me/PrMaB
111] [Planning]
26. A - The Internal Rate of Return (IRR) gives the
projected annual yield of an investment (rate of return)
considering the time value of money. On the other hand,
the NPV (net present value) of an investment is the
difference between the present value of cash inflows and
the present value of cash outflows over a period of time
considering the time value of money. Payback period
(PBP) is the time needed to recover an investment. Return
on Investment (ROI) is the percentage return on an initial
investment. Both PBP and ROI do not consider time value
of money.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
27. C - The definition of done (DoD) is a series of
conditions that the entire team agrees to complete before
an item is considered sufficiently developed to be
accepted by the business stakeholders.
[The PMI Guide to Business Analysis, page 219]
[Analysis]
28. A - Minimum Marketable Features (MMF) is a
prioritization mechanism in which the smallest piece of
functionality that still delivers value to the customer is
identified.
[The PMI Guide to Business Analysis, page 401]
[Analysis]
29. A - The Entity Relationship Model is a data model
and not a scope model. The rest of the choices are all
examples of scope model.
[The PMI Guide to Business Analysis, page 185]
[Analysis]
30. B - Capability tables are used for analyzing
capabilities in a current or future-state. Within future-state
analysis, the mode can be used to display the capabilities
needed to solve a problem or seize an opportunity.
https://t.me/PrMaB
However, capability tables are not very useful in
identifying system defects and bugs.
[The PMI Guide to Business Analysis, page 67] [Analysis]
31. D - Delphi is a consensus-building method that
consolidates anonymous input from subject matter experts
using rounds of voting. The rest of the choices are group
decision-making techniques and do not keep SMEs’
inputs anonymous.
[The PMI Guide to Business Analysis, page 228]
[Analysis]
32. A - Configuration management system helps ensure
that the solution being built conforms to its approved
product information. It provides a process for verifying
this conformance, documenting changes, and reporting the
status of each change throughout the project life cycle.
[The PMI Guide to Business Analysis, page 273]
[Traceability & Monitoring]
33. B - Behavior-driver development (BDD) is an
approach that suggests that the team should begin with
understanding how the user will use a product (its
behavior), write tests for that behavior, and then construct
solutions against the tests.
[The PMI Guide to Business Analysis, page 218]
[Analysis]
34. D - Questionnaires are written sets of questions
designed to quickly accumulate information from a large
number of respondents. Since you want to elicit basic
access requirements form a large group, this technique
will provide you the required result faster than the rest.
[The PMI Guide to Business Analysis, page 168]
[Analysis]
35. A - Those stakeholders whose workload is likely to
increase may never become supportive of the project.
Understand the concerns of the disinterested stakeholders
and look for ways to obtain their engagement despite the
https://t.me/PrMaB
lack of support the stakeholders may have toward the
project.
[Business Analysis for Practitioners: A Practice Guide,
page 40; The PMI Guide to Business Analysis, page 115]
[Planning]
36. B - A data flow diagram is a data model that is used to
describe the movement of data between entities, data
stores, and processes. These entities can be actors or
systems. Data flow diagrams show the data inputs and
outputs for each process.
[The PMI Guide to Business Analysis, page 188]
[Analysis]
37. A - The correct response is the Scope Management
Plan. This plan provides guidance on how project scope
will be defined, documented, validated, managed and
controlled by the project management team. [PMBOK®
Guide 6th edition, Page 137] [Planning]
38. A - In this case, your communication is with your
supervisor who has a different level of responsibility and
authority. This is an example of an upward dimension of
communications. [PMBOK® Guide 6th edition, Page
361] [Analysis]
39. C - A Pareto diagram is a histogram that can be used
to communicate the results of root cause analysis. Pareto
diagrams are a special form of vertical bar chart used to
emphasize the most significant factor among a set of data.
The rest of the choices do not have this capability.
[The PMI Guide to Business Analysis, pages 69] [Needs
Assessment]
40. B - A feature model is a scope model that visually
represents all the features of a solution arranged in a tree
or hierarchical structure. The feature model helps teams
establish and communicate relationships between different
features.
[The PMI Guide to Business Analysis, page 260]
[Traceability & Monitoring]
https://t.me/PrMaB
41. B - The definition of ready is a series of conditions
that the entire team agrees to complete before a user story
is considered sufficiently understood so that work can
begin to construct it. The source of the conflict in this
scenario indicates the absence of the definition of ready
for the user stories.
[The PMI Guide to Business Analysis, page 212]
[Analysis]
42. D - Elicitation processes are repeated throughout the
product and project life cycle. You need to schedule these
throughout the project.
[The PMI Guide to Business Analysis, page 155]
[Analysis]
43. B - Iterative scheduling with a backlog is a form of
rolling wave planning based on adaptive life cycles. The
rest of choices are made up responses. [PMBOK® Guide
6th edition, Page 177] [Planning]
44. C - ERDs are typical inputs for database designers and
architects to use in database design. The rest of the
choices are not of much use in this regard.
[The PMI Guide to Business Analysis, page 191]
[Analysis]
45. A - A use case is a process model that uses textual
narrative to describe the system-user interactions to
achieve successful completion of a goal. Each use case
contains a normal flow and an alternative flow. However,
uses cases are not well-suited for capturing non-
interaction-based requirements of a system such as
algorithms or mathematical requirements.
[The PMI Guide to Business Analysis, page 214]
[Analysis]
46. D - Interaction matrix is a lightweight version of a
traceability matrix that is used to figure out whether
requirements are sufficiently detailed or if any entities are
missing.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 399]
[Analysis]
47. B - The change control procedure varies from project
to project. However, every change request must be
processed through a formal change control process.
[PMBOK® Guide 6th edition, Page 113] [Traceability &
Monitoring]
48. B - An affinity diagram is a technique that allows
large numbers of ideas to be classified into groups for
review and analysis.
[The PMI Guide to Business Analysis, page 77] [Analysis]
49. D - A wireframe is an interface model and not a rule
model. The rest of the choices are all rule models.
[The PMI Guide to Business Analysis, page 185]
[Analysis]
50. B - Some common techniques for determining
priority are MoSCoW, multivoting, timeboxing, and
weighted ranking.
[Business Analysis for Practitioners: A Practice Guide,
page 56; The PMI Guide to Business Analysis, page 127]
[Planning]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) – 12
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 12
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. To communicate with stakeholders on the resolved
issues and the issues that are hard to resolve, you use an
issue log in your project. Since you assign an owner for
every issue and resolve it by working on it, your
stakeholders actively support all your efforts in managing
the project. This method of actively resolving issues and
reducing risks to the project is known as:
A. Communications management
B. Scope Management
C. Stakeholder management
D. Quality management
https://t.me/PrMaB
organizational project. The analyst wants to schedule the
stakeholder engagements in advance and has asked you to
provide him with some details regarding the sequence of
the elicitation activities. What do you do?
A. Share the elicitation approach with the analyst.
B. Mind mapping
C. Decision trees
D. Storyboarding
https://t.me/PrMaB
5. You are developing the business analysis plan for your
project and what to document the requirements
verification and validation processes for all elicited
requirements. The product team is struggling to
understand the differences between the two processes.
What is the difference between requirements verification
and requirements validation?
A. Product requirements assurance is called validation
while the project requirements assurance is called
verification.
D. scope statement
https://t.me/PrMaB
7. Your organization is currently automating its core
business processes. This is the CEO’s dream project and
was initiated in a hurry. As a result, insufficient time was
spent on requirements gathering and project planning. You
have recently taken over this project and have immediately
realized that the missing requirements are now leading to
scope creep on the project. The developers are prototyping
system components and as a result of the user feedback,
they are adding their own product features that aren’t
documented anywhere. What should you do first?
A. Encourage the developers to fix the issues as they
occur and add features requested by the users.
https://t.me/PrMaB
A. Stakeholder impact analysis
B. Document analysis
C. Facilitated workshop
D. Retrospective
B. Benchmarking
C. Criminal act
D. Cheating
https://t.me/PrMaB
12. You are leading a process automation project.
Although the key project requirements are fixed, the
detailed solution requirements are continuously being
changed by the stakeholders. What do you need to do to
ensure that each introduced change is aligned with the
business and project objectives?
A. Establish a Kanban board
C. Need to be discontinued.
B. Communication technology
C. Communication methods
https://t.me/PrMaB
D. Communication requirements analysis
B. Normal flow
C. Post-conditions
D. Alternate flow
https://t.me/PrMaB
18. You started a software development company a couple
of years ago and have successfully launched a product
into the market. Now you are looking for a venture capital
firm to invest in the product so that it could be sold to a
much wider customer segment. If the venture capital firm
is risk averse, most probably, they will be looking for an
investment that:
A. Has the highest IRR.
B. Data Dictionary
C. State Table
D. Feature Model
https://t.me/PrMaB
B. Acceptance testing
C. Unit testing
D. Exploratory testing
B. Verify Requirements
D. Validate Requirements
https://t.me/PrMaB
following models should you develop to accompany these
wireframes to show the navigation between the screens?
A. Use case diagram
C. Use cases
D. Process flow
B. Story mapping
C. Storyboarding
D. Story slicing
https://t.me/PrMaB
responsibilities on the project. The project manager is not
sure how the outcomes of the business analysis effort will
be integrated with their project planning. Which of the
following is the point of integration between business
analysis and project management?
A. The business analysis work plan
B. Developer-hours
C. Story size
D. Iteration risk
https://t.me/PrMaB
29. Your software development project is currently
struggling due to a number of recently reported defects.
The project team spent significant amount of time
planning for this project and special effort was made to
collect, validate and document the customer requirements.
You and your team now want to analyze these events in
detail and conduct a cause-and-effect analysis. All of the
following statements are true about a cause-and-effect
diagram except:
A. A maximum of six causes are listed on the cause-
and-effect diagram.
https://t.me/PrMaB
31. You are currently facilitating an elicitation workshop.
During the first half of the workshop you have used the
speedboat elicitation to elicit information about product
features that customers/stakeholders find problematic. In
the second half, you want to focus on the positive
influences. Which of the following is a variation of the
speedboat technique that focuses on positive influences
rather than identifying negative ones?
A. Kayak
B. Canoe
C. Sailboat
D. Yacht
B. Kano model
C. Andon
D. Pareto model
C. Control Scope
D. Monitor Risks
https://t.me/PrMaB
34. You are leading the business analysis activities for a
software development project for a client organization.
You are currently developing a story map for the entire
project. Which of the following is a foundational part of a
story map that represents the minimum set of capabilities
that absolutely are required to be in the first release for the
solution to serve its purpose?
A. Story point
B. Backlog
C. Use case
D. Backbone
B. Affinity Diagram
C. Context Diagram
https://t.me/PrMaB
D. Interrelationship Diagram
B. Affinity diagram
C. Affinity estimating
D. Poka-yoke
https://t.me/PrMaB
B. Burndown charts
C. Kanban board
D. User stories
B. MoSCoW analysis
C. Project scoping
D. Story estimating
https://t.me/PrMaB
42. A complicated software project was authorized by a
project sponsor. However, the users who were intended to
use the product found it extremely difficult to articulate
their requirements. What technique can be employed to
elicit requirements for such a project?
A. Job shadowing
B. Job duplication
C. Hidden participant
D. Job overlaying
B. Context diagram
C. Decision tree
B. Waterfall methods
C. Agile methods
D. Kanban methods
https://t.me/PrMaB
45. Sometimes a requirement is not able to be satisfied in
a solution without including the other requirements to
which it is related. All the following are examples of such
requirement relationships EXCEPT:
A. Discretionary dependency
B. Value dependency
C. Subsets
D. Implementation dependency
B. Sensitivity analysis
C. PERT analysis
https://t.me/PrMaB
following techniques will now help the team demonstrate
that all user stories are good and ready for development?
A. INVEST
B. PEST
C. SWOT
D. KANO
B. Variable sampling
C. Stratified sampling
D. Attribute sampling
D. Identify Stakeholders
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) – 12
Answer Key and Explanations
1. C - Actively working with project stakeholders and
resolving their issues relate to project stakeholder
management. [PMBOK® Guide 6th edition, Pages 504-
506] [Analysis]
2. A - The elicitation plan documents how and when to
elicit, which techniques to use, and the sequence of the
elicitation activities. You should share this document with
the analyst. The project charter doesn’t have this
information and so it is not helpful. The WBS will be
developed only once the product requirements have been
elicited and analyzed. Sharing the stakeholder list will be
useless.
[Business Analysis for Practitioners: A Practice Guide,
page 53; The PMI Guide to Business Analysis, page 127]
[Planning]
3. D - Storyboarding is an agile prototyping technique
that shows sequence or navigation through a series of
images or illustrations. The rest of the choices are
graphical techniques designed to achieve other objectives.
[PMBOK® Guide 6th edition, Page 147] [Planning]
4. A - Procedures for accepting and rejecting change
requests are related to change management rather than
configuration management. [PMBOK® Guide 6th edition,
Pages 118, 119] [Needs Assessment]
5. C - Verification is the evaluation of whether the
product complies with regulation, requirement,
specification, or imposed conditions. Validation is the
assurance that the product meets the needs of the
customer.
[Business Analysis for Practitioners: A Practice Guide,
page 58; The PMI Guide to Business Analysis, page 127]
[Planning]
https://t.me/PrMaB
6. C - Business analysts who begin elicitation sessions
without a well thought out road map of how they will
address the work will often find themselves pressed for
time and rushing through activities. In this scenario, one
should first investigate whether a business analysis plan
exists, and if it does, how good is it.
[Business Analysis for Practitioners: A Practice Guide,
page 37; The PMI Guide to Business Analysis, page 127-
129] [Planning]
7. B - First of all, you need to ask the developers to stop
gold plating the solution. Then you need to re-visit the
planning processes and properly document the project
scope. [PMBOK® Guide 6th edition, page 168]
[Traceability & Monitoring]
8. B - From the given options, only Kano analysis
explores a product’s features from the viewpoint of the
customer. Kano analysis can be used to help a product
team understand the level of importance of features being
considered for the future state.
[The PMI Guide to Business Analysis, page 79] [Needs
Assessment]
9. B - Note that you are currently analyzing a document
to identify stakeholders that will be impacted by the new
system; you are not analyzing the impact of the new
system on these stakeholders.
[The PMI Guide to Business Analysis, page 106] [Needs
Assessment]
10. A - Assuming that none of the given actions have
been undertaken in the past, the first thing to do is to set
expectations. Once the expectations are set, the behavior
need to be managed. Persuasion, motivation and conflict
resolution should follow this. [PMBOK® Guide 6th
edition, Page 319, 320] [Analysis]
11. B - Benchmarking is a comparison technique used to
compare one set of practices, processes, and
measurements of results against another. Benchmarking
https://t.me/PrMaB
studies of external organizations that have solved similar
problems is an accepted technique and there is nothing
wrong about it.
[The PMI Guide to Business Analysis, page 78] [Needs
Assessment]
12. B - A change management process will help you
ensure that changes align with the business and/or project
objectives.
[The PMI Guide to Business Analysis, page 254]
[Traceability & Monitoring]
13. B - A Product portfolio matrix, also known as a
growth-share matrix, is a market analysis quadrant
diagram used by organizations to qualitatively analyze
their products and product lines. One axis reflects market
growth while the other reflects the market share of the
organization. The matrix provides a quick visual way to
evaluate which products are meeting or exceeding
performance expectations in the marketplace. The
products that provide the most significant benefits to the
organization would be found in the upper left quadrant,
because these are the products where the organization has
a high market share in a market with a high growth rate.
Those in the upper right quadrant are regarded as having
good potential because, although they have a low market
share, they are in a market that is continuing to grow.
Those in the lower left quadrant, with a high market share
in a low growth market, are considered a dependable
income stream.
[The PMI Guide to Business Analysis, page 284]
[Evaluation]
14. D - The question is asking for a tool and technique
that is not part of the Manage Communications process.
Communication requirements analysis is a tool and
technique of the Plan Communications Management
process and not the Manage Communications process.
[PMBOK® Guide 6th edition, Page 379] [Analysis]
https://t.me/PrMaB
15. D - The is no point in defining “definition of done” for
the stories that have been already completed. A product
team should define the “definition of done” (DoD) for
each user story and iteration.
[The PMI Guide to Business Analysis, page 219]
[Analysis]
16. D - Evaluate Solution Performance is the process of
evaluating a solution to determine whether the
implemented solution or solution component is delivering
the business value as intended. This PMI Guide to
Business Analysis process will help you with your current
task.
[The PMI Guide to Business Analysis, page 280]
[Evaluation]
17. A - The errors or disruptions in the normal flow that
require an actor or system to perform a different action to
respond to the exception are documented in the exceptions
section of the use case.
[The PMI Guide to Business Analysis, page 214]
[Analysis]
18. B - If the venture company is risk averse, they would
be looking to reduce their investment risk by investing in
a company that offers the shortest payback period making
it the least risky company to invest in. IRR, NPV and ROI
do not indicate the level of risk involved.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
19. A - An organizational chart, or org chart, is a scope
model that shows the reporting structure within an
organization or within a part of an organization.
[The PMI Guide to Business Analysis, page 197]
[Analysis]
20. D - Unit and integration testing are done by the
product team. The team want some SMEs to validate the
system before the release is presented to the users who
https://t.me/PrMaB
will then perform acceptance testing. You need to conduct
exploratory testing with the selected SMEs.
[The PMI Guide to Business Analysis, page 397]
[Analysis]
21. B - The first thing you need to do is to conduct a
detailed variance analysis to understand the root cause of
the issue. Once the root cause is identified, appropriate
corrective and preventive measures can be planned.
[The PMI Guide to Business Analysis, page 150]
[Traceability & Monitoring]
22. C - Select and Approve Requirements is the process of
facilitating discussions with stakeholders to negotiate and
confirm which requirements should be incorporated
within an iteration, release, or project. Note that this
process is performed after the Verify Requirements and
Validate Requirements processes.
[The PMI Guide to Business Analysis, page 263]
[Traceability & Monitoring]
23. B - A user interface flow is an interface model that
displays specific user interfaces and commonly used
screens within a functional design and plots out how to
navigate between them.
[The PMI Guide to Business Analysis, page 207]
[Analysis]
24. A - Observation and document analysis are not
collaborative techniques. Techniques such as
brainstorming and collaborative games can be used in
facilitated workshops to help achieve the objectives of the
meeting.
[The PMI Guide to Business Analysis, page 167]
[Analysis]
25. D - Story slicing is a technique used to split
requirements or user stories from a higher level to a lower
level. Story mapping is a technique used to sequence user
stories. The other two choices are not user story
management techniques.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 261]
[Traceability & Monitoring]
26. A - Once the business analysis deliverables, task and
activities, and required resources for completing the work
are known, the information is assembled into the business
analysis work plan. This is the point of integration
between business analysis and project management.
[Business Analysis for Practitioners: A Practice Guide,
page 65; The PMI Guide to Business Analysis, page 146]
[Planning]
27. C - The amount of effort required to deliver a user
story is known as story size. Teams consider story size so
that they do not try to commit to more stories than there is
team capacity.
[The PMI Guide to Business Analysis, page 133]
[Planning]
28. C - The product owner is ultimately responsible and
accountable for the product being developed. If the
product owner has requested to drop a feature from the
current iteration plan, that decision needs to be honored.
To manage the stakeholder expectation at compliance,
notifying compliance of the change is a good idea.
[The PMI Guide to Business Analysis, page 45, 216]
[Planning]
29. A - While listing six causes is possible, there is no
rule that states a maximum of six causes can be listed.
You could list four or eight, for example. [PMBOK®
Guide 6th edition, Page 293] [Analysis]
30. D - You need to conduct a job analysis based on the
future-state process. The output of job analysis may
include details such as a high-level description of the
work; a depiction of the work environment; a detailed list
of the activities a person is expected to perform; a list of
the preferred interpersonal skills; or a list of required
training, degrees, and certifications.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 117]
[Planning]
31. C - Sailboat is a variation of the speedboat technique
that focuses on positive influences rather than identifying
negative ones.
[The PMI Guide to Business Analysis, page 166]
[Analysis]
32. A - A Kanban board is used in adaptive approaches to
track work that is in progress by the project team.
[The PMI Guide to Business Analysis, page 233]
[Analysis]
33. B - Approved and rejected change requests are outputs
of the Perform Integrated Change Control process.
[PMBOK® Guide 6th edition, Page 113] [Traceability &
Monitoring]
34. D - The backbone is a foundational part of a story map
representing the minimum set of capabilities that
absolutely are required to be in the first release for the
solution to serve its purpose. That set of capabilities or
user stories is sometimes called the minimum viable
product.
[The PMI Guide to Business Analysis, page 388]
[Analysis]
35. D - DEEP stands for: Detailed, estimated, emergent,
and prioritized. DEEP describes the characteristics that a
product backlog needs to demonstrate to be considered
well-refined.
[The PMI Guide to Business Analysis, page 213]
[Analysis]
36. B - Affinity diagrams display categories and
subcategories of ideas that cluster or have an affinity to
one another. These are used to process a large amount of
information or ideas into a manageable set of data
organized by categories.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 77] [Needs
Assessment]
37. B - Instead of linking the product releases to the
organizational strategic objectives you should remove
these if already present in the product roadmap. External
customers may not need to know or be interested in how
products align to the organizational strategy. The rest of
the option are all valid activities.
[The PMI Guide to Business Analysis, page 94] [Needs
Assessment]
38. C - Affinity estimating is a form of relative estimation
in which team members organize product backlog items
into groups where each product backlog item is about the
same size.
[The PMI Guide to Business Analysis, page 132]
[Planning]
39. D - In adaptive approaches, user stories are
commonly the method to represent requirements.
[The PMI Guide to Business Analysis, page 215]
[Analysis]
40. C - You must take the sponsor’s recommendation on
board. Gathering all relevant documents and conducting a
thorough analysis for these documents is your best bet.
Once you update yourself with all the relevant
information, context, and background, you will be in a
better position to engage these negative stakeholders.
Developing the product without consulting the
stakeholders is not advisable for any project. Escalating
the matter seems unnecessary.
[The PMI Guide to Business Analysis, page 167]
[Analysis]
41. B - During MoSCoW analysis, requirements are
sorted into four categories: must have, should have, could
have, and won’t have.
[The PMI Guide to Business Analysis, page 234]
[Planning]
https://t.me/PrMaB
42. A - Job shadowing is a technique that can be
employed in this case. It is done externally by an observer
who views the user doing his or her job. This technique is
also called observation. [PMBOK® Guide 6th edition,
Page 145] [Analysis]
43. D - ERDs are typically input for database designers
and architects to use in database design. The rest of the
choices are not direct inputs to database design.
[The PMI Guide to Business Analysis, page 191]
[Analysis]
44. C - Agile methods deliberately spend less time trying
to define and lock project scope early during the project
and spend more time establishing the process for
requirements gathering, scope definition and refinement.
[PMBOK® Guide 6th edition, Page 133] [Planning]
45. A - Discretionary dependencies are usually based
upon best practices and are not mandatory. All the rest are
valid examples of requirement relationships that exhibit
some sort of parent-child relationship.
[The PMI Guide to Business Analysis, page 259]
[Traceability & Monitoring]
46. C - If a team has planned 50 story points to be
completed in the upcoming project sprint, this implies that
the expected velocity is 50 story points. The aspirational
velocity should be higher than this and the actual velocity
might be different at the end of the iteration. On Agile
projects, there is no such thing as benchmark velocity.
[The PMI Guide to Business Analysis, page 416]
[Planning]
47. A - Gap analysis compares the current state to the
future state and is performed to identify the required
capabilities against the existing capabilities and
identifying the differences and missing capabilities that
the organization needs to acquire to address the business
need.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 79] [Needs
Assessment]
48. A - INVEST model gives the characteristics that user
stories need to demonstrate to be considered “good” and
“ready” for development. INVEST is an acronym for
independent, negotiable, valuable, estimable, small, and
testable.
[The PMI Guide to Business Analysis, page 399]
[Analysis]
49. D - Attribute sampling measures the quality of items
in a sample on a pass/fail basis; variable sampling
measures the quality on a continuous scale. [PMBOK®
Guide 6th edition, Page 274] [Traceability & Monitoring]
50. B - The question is asking about the Stakeholder
Management process from the executing process group.
The Manage Stakeholder Engagement process executes
the stakeholder engagement strategy developed during the
Plan Stakeholder Engagement process. The Monitor
Stakeholder Engagement process deals with making the
necessary adjustments to the stakeholder engagement
strategy. [PMBOK® Guide 6th edition, Page 523]
[Analysis]
https://t.me/PrMaB
PMI-PBA
Domain Area Test: Planning Practice
Questions
Test Name: Domain Area Test: Planning
Total Questions: 20
Correct Answers Needed to Pass:
14 (70.00%)
Time Allowed: 30 Minutes
Test Description
This practice quiz specifically targets your knowledge of the
Planning PMI-PBA Domain area.
Test Questions
1. You are managing a project to lengthen a runway at a
major airport. However, after you worked on the project
for six months and held weekly status meetings, many of
your stakeholders are dissatisfied with the deliverables,
even with a CPI of 1.0 and an SPI of 1.0. Which of the
following phases has probably not been done properly?
A. Identify Stakeholders
B. Control Scope
C. Define Scope
D. Identify Risks
https://t.me/PrMaB
will also be required to move. Although the high-level
scope of the project is known, due to the complexity of the
project, the detailed requirements can only be determined
as the project progresses. Which of the following planning
tools should you use for this project?
A. Change control
B. Change requests
C. Progressive elaboration
D. Predictive approaches
B. IRR
C. ROI
D. DCF
B. Predictive lifecycles
C. Adaptive lifecycles
D. Waterfall lifecycles
https://t.me/PrMaB
obtained from conducting a job analysis different than the
results obtained from conducting a persona analysis?
A. Persona analysis is a stakeholder analysis
technique, but the job analysis cannot be used to
analyze stakeholders.
B. Product requirements
C. Business needs
https://t.me/PrMaB
A. Helps in determining how to best conduct the
business analysis activities.
B. External consultant
C. A PMO
D. Colocation
https://t.me/PrMaB
announcements and messages with an extremely large
audience. What communication method would be
appropriate under such circumstances?
A. Verbal communication
B. Two-way communication
C. Pull communication
D. Interactive communication
https://t.me/PrMaB
B. Collaborating closely with the project sponsor
during stakeholder identification.
B. Persona analysis
C. Stakeholder maps
D. Fishbone diagram
B. Story mapping
C. Stakeholder maps
D. Tornado diagram
https://t.me/PrMaB
stakeholders. You develop an interaction matrix for the
stakeholders to consume and identify whether the product
requirements have been adequately defined. An
interaction matrix is a lightweight version of a:
A. Traceability matrix
D. RACI matrix
B. Risk register
C. Daily standups
D. Issue log
B. Usability testing
C. Estimation poker
D. Demonstration
https://t.me/PrMaB
B. A backlog or intermediate queue of work to be
done.
B. Discrete
C. Effort-driven
D. Qualitative
https://t.me/PrMaB
PMI-PBA Domain
Area Test: Planning
Answer Key and Explanations
1. C - With a CPI of 1.0 and an SPI of 1.0, the project is
on time and on budget, but the stakeholders are
dissatisfied with the deliverables. This indicates that the
project scope statement was not accurate which gets
developed during the Define Scope process. [PMBOK®
Guide 6th Edition, Page 150] [Planning]
2. C - Since detailed requirements can only be
determined later in the project, this calls for progressive
elaboration of project requirements. The rest of the
choices are irrelevant. [PMBOK® Guide 6th edition, page
185] [Planning]
3. B - IRR determines the interest rate of a cash flow
stream at which the present value of the cash flow stream
becomes zero.
[The PMI Guide to Business Analysis, page 90]
[Planning]
4. C - Concurrent elicitation and confirmation are
considered a common practice in adaptive life cycles.
[The PMI Guide to Business Analysis, page 171]
[Planning]
5. C - Persona analysis and job analysis can both be used
to analyze stakeholders. However, the information
provided in the persona is behavioral in nature while the
information obtained from a job analysis is descriptive in
nature.
[Business Analysis for Practitioners: A Practice Guide,
page 45; The PMI Guide to Business Analysis, page 115-
116] [Planning]
6. B - Performance requirements such as the loading time
of websites are usually considered as part of product
https://t.me/PrMaB
requirements and scope. Project requirements include
business requirements, project management requirements
and delivery requirements, whereas product requirements
include technical, security, and performance requirements.
[PMBOK® Guide 6th edition, Page 131] [Planning]
7. A - Business analysts use the results from the
stakeholder analysis to understand how the stakeholders
will impact the business analysis process. The business
analyst considers a number of stakeholder characteristics
before determining how to best conduct the business
analysis activities.
[Business Analysis for Practitioners: A Practice Guide,
page 39; The PMI Guide to Business Analysis, page 115]
[Planning]
8. A - Creating the WBS is an important process in a
project, and it is done as a part of Project Scope
Management. [PMBOK® Guide 6th edition, Page 129]
[Planning]
9. C - A PMO coordinates between product teams by
communicating between projects. It facilitates sharing
items such as progress, issues, retrospective findings and
improvement experiments.
[The PMI Guide to Business Analysis, page 41]
[Planning]
10. C - The situation in the project would call for pull
communication. This is suitable for a large audience, and
it allows them to access information at their own
discretion. [PMBOK® Guide 6th edition, Page 374]
[Planning]
11. A - The business analyst assesses complexity to
understand how best to approach business analysis
activities and to understand the impact that the change
will have on stakeholders. The rest of the choices are all
responsibilities of the project manager.
[Business Analysis for Practitioners: A Practice Guide,
page 41; The PMI Guide to Business Analysis, page 115-
https://t.me/PrMaB
116] [Planning]
12. A - Uncovering stakeholder likes and dislikes may
bring to the forefront unspoken concerns about the
proposed business analysis process. Conducting a
retrospective at the conclusion of the business analysis
activities will be too late. The other two choices are
irrelevant.
[Business Analysis for Practitioners: A Practice Guide,
page 41; The PMI Guide to Business Analysis, page 115-
116] [Planning]
13. D - Fishbone diagrams are used to conduct root-cause
analysis. The rest of the choices are all valid stakeholder
analysis and grouping techniques.
[Business Analysis for Practitioners: A Practice Guide,
page 44; The PMI Guide to Business Analysis, page 115-
116] [Planning]
14. C - Stakeholder maps help with the analysis of
stakeholder characteristics such as the power, influence,
impact, and interest of stakeholder groups. The other
given choices are not applicable as these are not
stakeholder analysis techniques.
[The PMI Guide to Business Analysis, page 126]
[Planning]
15. A - An interaction matrix is a lightweight version of a
traceability matrix that is used to figure out whether
requirements are sufficiently detailed or if any entities are
missing.
[The PMI Guide to Business Analysis, page 196]
[Planning]
16. C - Since the most effective and efficient way of
conveying information to and within a team is face-to-
face conversation, Agile teams report all work in process
issues during the daily standups.
[The PMI Guide to Business Analysis, page 144, 244]
[Planning]
https://t.me/PrMaB
17. C - Estimation poker is an Agile estimating technique
and not a feedback solicitation technique. Estimation
poker combines expert opinion, analogy, and
disaggregation into an enjoyable approach to estimating
that results in a quick but reliable estimate.
[The PMI Guide to Business Analysis, page 133]
[Planning]
18. B - On-demand scheduling does not rely on a schedule
that was developed previously for the development of the
product or product increments, but rather pulls work from
a backlog or intermediate queue of work to be done
immediately as resources become available. [PMBOK®
Guide 6th edition, Page 177] [Planning]
19. A - Identify Risks is an iterative process, because new
risks may become known as the project progresses
through its lifecycle. [PMBOK® Guide 6th edition, Page
409] [Planning]
20. B - A Kanban board provides a continuous means to
visually communicate project status to the team. It is a
visual representation of what work is in progress.
[The PMI Guide to Business Analysis, page 233]
[Planning]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) - 13
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 13
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. On Agile projects, who is primarily responsible for
developing product roadmaps and decides whether and
where to place the user stories in the backlog?
A. Servant-leader
B. Agile team
C. Agile coach
D. Product owner
https://t.me/PrMaB
B. Desk check
C. Kanban
D. Acceptance test
https://t.me/PrMaB
between the system and external entities. Which of the
following models should you develop?
A. Prototype
B. Context Diagram
D. Organizational Chart
B. Deming chart
C. Ishikawa diagram
https://t.me/PrMaB
8. Which of the following describes the characteristics
for a user story to demonstrate that it is good and ready for
development?
A. PEST
B. INVEST
C. PESTLE
D. SWOT
B. Scatter diagram
C. Fishbone diagram
D. Pareto diagram
https://t.me/PrMaB
11. You have gathered all business requirements regarding
a product being developed by your team. You are now
ready to transform these business requirements to system
requirements. The product team has selected use case
models for this requirements transformation. A junior
business analyst will assist you with the drafting of these
use cases. Which of the following sections would you
request the analyst to include in each use case?
A. Supplier, Inputs, Process, Outputs, and Customer
D. Reporting requirements
https://t.me/PrMaB
A. The customer
B. The market
C. The organization
D. The product
C. Process analysis
D. Affinity diagrams
https://t.me/PrMaB
16. You are automating a complex network of manual
workflows that has many touchpoints. You need to
understand how and when different system functionalities
will be initiated. You decide to document the outcomes of
this analysis in an event list. What does a typical event list
describe?
A. Any internal events that would require a change
request to the system functionality
https://t.me/PrMaB
18. You are leading the business analysis efforts on an
information system development project. The technical
architect on the team needs to understand the involved
business data objects and the relationships between them
to design the backend database for the system. You decide
to develop an entity relationship diagram (ERD) and
supply this to her. An ERD is a:
A. Scope model
B. Ecosystem model
C. Data model
D. Process model
B. Capability table
C. RACI chart
D. 80/20 table
https://t.me/PrMaB
B. Complete your business analysis plan and ask the
project manager to accommodate that in their
schedule.
B. Decision tree
C. Prototype
D. Ecosystem map
B. Product backlog
C. Sprint retrospective
D. Kanban board
https://t.me/PrMaB
23. You have scheduled a three-day product requirements
elicitation workshop and have invited around thirty
stakeholders to attend the workshop. The stakeholders are
day-to-day process workers and have no business analysis
experience. For such a large product requirements
elicitation event, which of the following is NOT
advisable?
A. Consider collaborative games to help elicit
requirements.
B. Organizational structure
C. Product scope
https://t.me/PrMaB
B. The backend features of the system
26. You have been asked to develop a new website for one
of your clients. The website is required to be browser
independent and delivered within a month. Although the
website has a simple design, the requirement of browser
independence has added some complexity to the project.
Which of the following approaches would you
recommend for this project?
A. Incremental
B. Predictive
C. Iterative
D. Agile
B. Fishbone diagram
C. Flowchart
D. PERT
https://t.me/PrMaB
28. Evaluation of a solution performance typically
occurs:
A. Prior to the development of a solution
B. Brainstorming
C. Affinity diagram
D. Nominal group
D. Context Diagram
https://t.me/PrMaB
Which of the following statements is true regarding
projects using adaptive lifecycles?
A. Elicitation stories are added to the product backlog.
https://t.me/PrMaB
A. Observation
B. Brainstorming
C. Interview
D. Focus groups
https://t.me/PrMaB
D. Close all risks and update the project file.
https://t.me/PrMaB
business, the staff is well aware of quality management
processes but is not aware of scope management
processes. Which of the following best describes the
Validate Scope process?
A. Validating that all of the project’s objectives are
met
B. Product scope
C. Program scope
D. Project scope
https://t.me/PrMaB
A. It encourages stakeholders to participate in the
prioritization process who otherwise would not
participate.
B. Story estimation
D. Daily standups
B. Process map
https://t.me/PrMaB
C. SWOT analysis
D. Architecture
https://t.me/PrMaB
45. You are leading the business analysis activities for an
ERP implementation project. This is a major project that
is expected to take two years to complete. You have
recently circulated your project’s situation statement to
the key stakeholders. To your surprise, the project
stakeholders look confused and seem to have different
ideas of the situation. You are now not sure whether the
situation statement is accurate and there is a risk of
developing a wrong solution. What should you do next?
A. Revisit the Assess Current State process
https://t.me/PrMaB
47. You and your project team are inspired to deliver a
project in an Agile setting. Although the concept of a self-
organizing team sounds appealing, not clearly defining the
roles, responsibilities and accountabilities might introduce
significant risk to the project. What should you do?
A. Use a hybrid model
B. Feature model
C. Report tables
D. Business case
B. Multiple stakeholders
https://t.me/PrMaB
C. Project duration
B. Validate requirements
C. Verify requirements
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) - 13
Answer Key and Explanations
1. D - A product roadmap shows the anticipated
sequence of deliverables over time. Product owners are
primarily responsible for developing product roadmaps.
[The PMI Guide to Business Analysis, page 216]
[Planning]
2. B - Peer desk check is an informal peer review
completed by one or more peers simultaneously to look
over the work in process items.
[The PMI Guide to Business Analysis, page 404]
[Analysis]
3. B - The main reason for controlling the project scope
is to deal with the impact of changes on the project. This is
done by managing approved changes and disregarding
rejected changes. This reduces the risk of scope creep on
the project. [PMBOK® Guide 6th edition, Page 168]
[Planning]
4. C - The analyst is currently gathering information
regarding stakeholder preferences for the Elicitation
process and techniques; the analyst has not actually started
the Elicitation yet. This is the Determine Elicitation
Approach process.
[The PMI Guide to Business Analysis, page 158]
[Planning]
5. B - A context diagram defines the boundaries of a
system. It also identifies the flows of information between
the system and external entities. A context diagram is a
scope model that you can use in this context. None of the
rest of the choices are scope models.
[The PMI Guide to Business Analysis, page 186]
[Analysis]
https://t.me/PrMaB
6. C - Cause-and-effect diagrams, also called Ishikawa
diagrams, illustrate how various factors might be linked to
potential problems or effects. [PMBOK® Guide 6th
edition, Page 293] [Traceability & Monitoring]
7. B - The data objects shown in an ER model are not
meant to be exact data objects in a database, but rather a
conceptual view of the data in the solution from the
perspective of the business. The rest of the statements are
all correct.
[The PMI Guide to Business Analysis, page 191]
[Analysis]
8. B - The term INVEST describes the characteristics that
user stories need to demonstrate to be considered “good”
and “ready” for development in adaptive approaches.
INVEST is an acronym for independent, negotiable,
valuable, estimable, small, and testable.
[The PMI Guide to Business Analysis, page 223]
[Analysis]
9. C - A fishbone diagram is a version of a cause-and-
effect diagram used to depict a problem and its root causes
in a visual manner. None of the rest of the choices have
the capability of showing the outcome of a root cause
analysis.
[The PMI Guide to Business Analysis, page 70] [Needs
Assessment]
10. D - Product box is an elicitation technique that uses
game play to focus on the features of a product that are
important to the customer. It divides the participants into
teams, asking each team to design a box that represents
how the product would be packaged. The technique
provides insights into the benefits and features that
customer finds most valuable.
[The PMI Guide to Business Analysis, page 166]
[Analysis]
11. C - Typical sections of a use case are: Name, ID,
description, actors, organizational benefits, triggers,
https://t.me/PrMaB
preconditions, post conditions, normal flow, alternative
flow, and exceptions.
[The PMI Guide to Business Analysis, page 215]
[Analysis]
12. B - Non-functional requirements express the
environmental conditions or quality requirements for the
product to be effective. System availability and reliability
are non-functional requirements. The rest of the choices
are functional requirements.
[The PMI Guide to Business Analysis, page 402]
[Analysis]
13. D - The spider web is an elicitation technique used to
discover unknown relationships between the product
being analyzed and other products. The technique is
performed by drawing a circle in the middle of a large
sheet of paper to represent the product.
[The PMI Guide to Business Analysis, page 166]
[Analysis]
14. B - A project lifecycle is the series of phases through
which a project passes from its initiation to its closure.
The phases can be sequential, or they may overlap.
[The PMI Guide to Business Analysis, pages 15,16]
[Needs Assessment]
15. C - Process analysis examines problems experienced,
constraints experienced, and non-value-added activities
identified during process operation. [PMBOK® Guide 6th
edition, Page 292] [Analysis]
16. D - An event list is a scope model that describes any
external events that trigger solution behavior. Event lists
help define the in-scope events that the solution must
react to or handle.
[The PMI Guide to Business Analysis, page 192]
[Analysis]
17. D - You should not hold the payment if the deliverable
meets the agreed specifications. You need to release the
https://t.me/PrMaB
payment but conduct a detailed root cause analysis
regarding why the integration testing failed. You need to
determine if there is a bigger issue with the overall design
that needs to be fixed or some key specifications that were
somehow excluded in the contract. [PMI Code of Ethics
and Professional Conduct] [Traceability & Monitoring]
18. C - An entity relationship diagram is a business
analysis model that shows the business data objects or
pieces of information of interest and the relationships
between those objects, including the cardinality of those
relationships. An ERD is a data model.
[The PMI Guide to Business Analysis, page 191]
[Planning]
19. B - Capability tables can be used to depict the
relationship between a situation, its root causes, and the
capabilities needed to address the situation. Capability
framework, on the other hand, is used to rank the maturity
levels of business capabilities. The other two choices are
irrelevant to the question.
[The PMI Guide to Business Analysis, page 67] [Needs
Assessment]
20. C - It is a best practice to have the project manager
and business analyst working together while the business
analysis approach and plan are formulated. The rest of the
choices are incorrect.
[Business Analysis for Practitioners: A Practice Guide,
page 38; The PMI Guide to Business Analysis, page 127-
129] [Planning]
21. D - The ecosystem map allows the business analyst to
see where there are possible interface requirements or data
requirements for systems directly interfacing to the
solution and for those up- or downstream from the
solution.
[The PMI Guide to Business Analysis, page 190]
[Analysis]
https://t.me/PrMaB
22. D - A Kanban board provides a means to visualize the
flow of work, make impediments easily visible, and allow
flow to be managed by adjusting the work-in-process
limits.
[The PMI Guide to Business Analysis, page 233]
[Analysis]
23. D - You need to facilitate and help the stakeholders
articulate their requirements. Asking them to come
prepared with their list of requirements is not reasonable.
All the rest are great ideas.
[The PMI Guide to Business Analysis, page 160]
[Analysis]
24. C - The five inputs to the Prepare for Elicitation
process are elicitation approach, requirements and other
product information, situation statement, stakeholder
engagement and communication approach, and the
product scope.
[The PMI Guide to Business Analysis, page 160]
[Analysis]
25. D - The walking skeleton is the full set of end-to-end
functionality that the stakeholders require for the solution
to be accepted or considered functional.
[The PMI Guide to Business Analysis, page 204]
[Analysis]
26. C - The project requires a single final delivery.
However, project work might require repetitions until all
browsers are supported. An iterative approach is ideal in
this situation. [PMBOK® Guide 6th edition, page 19]
[Needs Assessment]
27. C - A flowchart is a visual representation of the
sequence of steps and decisions needed to perform a
process. From the given choices, this is the only tool you
can use to model the current and future state processes.
[PMBOK® Guide 6th edition, page 284] [Planning]
28. D - Evaluation of solution performance typically
occurs after a solution has been released.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 281]
[Evaluation]
29. A - Delphi is a consensus-building method that
consolidates anonymous input from subject matter experts
using rounds of voting. The rest of the choices are group
decision-making techniques and do not keep SMEs’
inputs anonymous. The Delphi method reduces peer
pressure or groupthink in the validation process.
[The PMI Guide to Business Analysis, page 228]
[Analysis]
30. B - A business rules catalog is a type of rule model. It
is a table of business rules and related attributes. Business
rules are not processes or procedures; rather, they describe
how to constrain or support behaviors within the
operations of the business.
[The PMI Guide to Business Analysis, page 212]
[Analysis]
31. B - Projects using adaptive life cycles go through the
elicitation and analysis processes within each project
iteration. The rest of the choices are all inaccurate; user
stories are added to the backlog and not the elicitation
stories; Agile projects do not follow a strict analysis and
design sequence; there is no Agile tool known as
Elicitation results board.
[The PMI Guide to Business Analysis, page 155]
[Planning]
32. B - A readiness assessment is an evaluation of how
well an organization is prepared for a change. It provides
an evaluation of the ability of an organization to transition
to the future state enabled by the solution.
[The PMI Guide to Business Analysis, page 297]
[Evaluation]
33. A - You can use the observation technique to identify
the workarounds being used by the product users to
compensate for the gaps in the product performance. Such
workarounds could be missed when using interviews and
https://t.me/PrMaB
other verbal communication techniques, because it may
not occur to users who are familiar with using the product
for a long time to mention how they compensate for a lack
of functionality.
[The PMI Guide to Business Analysis, page 283]
[Evaluation]
34. D - Some aspects of a solution that reflect the benefits
and value may not be measurable until well after a
solution is released. In these situations, the operational
business area responsible for the product may take
responsibility for identifying and measuring leading
indicators.
[The PMI Guide to Business Analysis, page 279]
[Evaluation]
35. A - Product risks not addressed within the duration of
the project may be transferred to operational teams to
manage going forward. None of the other choices are
reasonable actions to take.
[The PMI Guide to Business Analysis, page 296]
[Evaluation]
36. D - Project managers use stakeholder analysis to
assess how the stakeholder groups will influence and
impact the project work. Business analysts use the results
to understand how the stakeholders will impact the
business analysis process. Both roles assess stakeholders
to understand how to communicate, collaborate, manage
and set expectations.
[Business Analysis for Practitioners: A Practice Guide,
page 39; The PMI Guide to Business Analysis, page 115]
[Planning]
37. C - Excessive decomposition can lead to inefficient
use of resources, decreased efficiency and non-productive
management efforts. [PMBOK® Guide 6th edition, Pages
160, 161] [Planning]
38. C - Scope Validation involves obtaining the
stakeholders’ formal acceptance of project deliverables.
https://t.me/PrMaB
[PMBOK® Guide 6th edition, Page 163] [Traceability &
Monitoring]
39. B - The COO has shared the product scope which is
the set of features and functions that characterize the
required solution/product. The project scope defines the
work that needs to be done to deliver a product, service,
or result.
[The PMI Guide to Business Analysis, page 17] [Needs
Assessment]
40. C - “Buy a feature” is a type of collaborative game
used to enable a group of stakeholders to agree on
prioritization by giving each stakeholder an amount of
pretend money to buy their choice of features, splitting the
money received across features however desired. It puts
emphasis on the perceived value of the features and limits
the buying capacity of the stakeholders.
[The PMI Guide to Business Analysis, page 391]
[Planning]
41. C - Examples of control points are stage gates or
phase gates. The evaluation which occurs at the end of a
sprint, iteration, or release can also be considered a
control point.
[The PMI Guide to Business Analysis, page 392]
[Analysis]
42. D - The business architecture is the tool that describes
an organization by mapping its essential characteristics,
such as people, locations, processes, applications, data,
and technology.
[The PMI Guide to Business Analysis, page 388]
[Analysis]
43. D - The purpose alignment model is a technique that
provides a framework to support strategic or product
decision making. The framework is used to categorize
options by aligning them with the business purpose they
support.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 81] [Needs
Assessment]
44. D - The project’s NPV has fallen, which is an
unfavorable condition, however the project is still
profitable since the NPV is still a positive value.
[The PMI Guide to Business Analysis, pages 90, 283]
[Evaluation]
45. D - If the situation statement is not properly
understood, or if the stakeholders have a different idea of
the situation, there is a risk that a wrong solution will be
identified. Since the situation statement is an output of the
Identify Problem or Opportunity process, you need to
reperform this process to ensure that the situation
statement is properly developed.
[The PMI Guide to Business Analysis, page 57] [Needs
Assessment]
46. D - Culture and location are not the same thing. Even
when all the stakeholder groups reside in one location,
there are cultural differences among the groups. All the
other choices are valid project assumptions.
[Business Analysis for Practitioners: A Practice Guide,
page 42; The PMI Guide to Business Analysis, page 115-
116] [Planning]
47. A - The scenario makes it clear that you cannot accept
the risk. Since you need to try Agile approaches while
retaining some of the predictive methods, it is
recommended that you and the team sit together and agree
on a hybrid model for this project. [PMBOK® Guide 6th
edition, page 19] [Needs Assessment]
48. C - A report table typically accompanies a prototype
of a report to show the implementation team what the
report should look like. The rest of the choices are
irrelevant in this context.
[The PMI Guide to Business Analysis, page 201]
[Analysis]
https://t.me/PrMaB
49. B - According to PMI’s Pulse of the Profession® In-
Depth Report: Navigating Complexity, the presence of
multiple stakeholders contributes maximum to the project
complexity. The rest of the three choices are the least
impacting factors.
[Business Analysis for Practitioners: A Practice Guide,
page 42; The PMI Guide to Business Analysis, page 115-
116] [Planning]
50. B - Validate requirements is the process of checking
that the requirements meet business goals and objectives.
[The PMI Guide to Business Analysis, page 225]
[Analysis]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) - 14
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 14
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. Which of the following is an approach that suggests
that the team should begin with understanding how the
user will use a product, write test cases, and then develop
solutions against the tests?
A. DFD
B. ERD
C. BDD
D. BRD
https://t.me/PrMaB
understand the relationships between these reasons and
identify the real root cause of the situation?
A. Ishikawa diagram
B. Interrelationship diagram
C. Context diagram
D. Fishbone diagram
https://t.me/PrMaB
5. Projects with adaptive life cycles use product backlogs
to define a project’s scope. The product backlog is a set of:
A. Voice of the customer
B. Non-functional requirements
C. Client lullabies
D. User stories
https://t.me/PrMaB
D. Analyze the product’s legal and regulatory impacts.
C. Decision tree
D. Decision table
https://t.me/PrMaB
priorities by placing product features on a matrix
according to their criticality and market differentiation?
A. Decision table
B. Extrapolating
C. Back tracking
D. Discounting
B. Power/influence grid
C. Salience model
D. Sufficiency model
https://t.me/PrMaB
few senior stakeholders who can help you identify
business improvement opportunities; however, these
stakeholders have extremely busy schedules and you can
only plan your activities according to their schedules. You
decide to interview these stakeholders individually due to
their availability constraints. What is the risk involved in
this approach?
A. The stakeholders might not be able to collaborate
and work toward a stated objective.
https://t.me/PrMaB
administrative closure activities. One of the requirements
is the development of the project’s final report. Which
information would you NOT include in this report?
A. Cost objectives
B. Scope objectives
C. Risk summaries
B. Ground rules
D. Kanban board
https://t.me/PrMaB
are happy with the project so far. However, George has
some potential concerns that might become issues in the
near future. The next project status update meeting with
the key stakeholders is the next day. What should George
do?
A. Wait until the concerns become issues
https://t.me/PrMaB
A. Should have
B. Could have
C. Must have
D. Won’t have
C. Product backlog
D. Traceability matrix
https://t.me/PrMaB
23. A software vendor has recently hired you to manage
some of its key projects. During your orientation at the
organization you were told that the organization has
recently adopted Agile practices for project management.
A chart was then shown to you where Agile and Kanban
were shown as a subset of Lean. What is your view on
this?
A. The chart is wrong because Agile is a subset of
Lean while Kanban is not.
https://t.me/PrMaB
25. You are reviewing a legacy system and analyzing how
its users are currently using the system. You have
conducted multiple workshops with the users to
understand the manual workarounds being performed by
the users to compensate for the gaps in the product
functionality. However, so far you have not been
successful. You decide to observe how the users operate
the system in real-time to better understand these
workarounds methods and practices. What is the typical
disadvantage associated with this technique?
A. The workaround might not be required during the
time when the users are being observed.
https://t.me/PrMaB
your country. The project has a big number of
stakeholders, who have so far struggled with defining the
project requirements in a level of detail required for
system development. As a result, you have decided to try
Agile approaches for system development. With the
detailed system requirement not defined, which of the
following is one of the major risks on your project?
A. Scope verification
B. Scope creep
D. Scope control
https://t.me/PrMaB
C. Identifying a subset of sprint backlog for
development in the next sprint.
D. Invest in project B.
https://t.me/PrMaB
A. Monitor Stakeholder Engagement
D. Identify Stakeholders
B. Critical path
C. Normal flow
D. Alternative route
https://t.me/PrMaB
D. Informally documented confirmed elicitation
results
B. Integration Testing
C. Regression Testing
https://t.me/PrMaB
deliverables have been presented for customer inspection
to date. What new risk has been introduced by this?
A. The change control board might not approve further
change requests.
D. The contract
B. Context diagram
C. Report table
D. User story
https://t.me/PrMaB
Statement that contains an objective statement of the
problem and the associated opportunity. Which of the
business analysis processes do you need to perform next
to produce the required capabilities for the future-state
processes?
A. Determine Future-State
C. Project Assumption
D. Project Constraint
https://t.me/PrMaB
43. You are currently preparing for the Solution
Evaluation activities for a new accounting system your
organization is developing inhouse. All of the stated
benefits of the project are intangible, and therefore not
possible to measure. In this case, how would you conduct
Solution Evaluation?
A. Define measurements that provide indirect
evidence that the benefits have been achieved.
B. Project charter
C. Business case
https://t.me/PrMaB
D. Team owner adds an item to the product backlog.
B. Job analysis
C. Future-state definition
D. Gap analysis
48. State tables and state diagrams are useful for solutions
involving workflows and can help with the discovery of
business rules that relate to an object moving from one
state to another. In which situation would you prefer
developing a state diagram instead of a state table?
A. When you want the stakeholders to focus only on
the valid transition flow.
https://t.me/PrMaB
B. When you want to analyze complex business
workflows.
B. Steering Committee
B. Option C
C. Option D
D. Option A
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) - 14
Answer Key and Explanations
1. C - Behavior-driven development (BDD) is an
approach that suggests that the team should being with
understanding how the user will use a product (its
behavior), write test cases for that behavior, and then
develop solutions against the tests.
[The PMI Guide to Business Analysis, page 219]
[Analysis]
2. B - The fishbone diagrams, also known as Ishikawa
diagrams, are tools to identify potential root causes of the
situation but do not help us analyze the interrelationship
between these potential root causes or reasons. An
interrelationship diagram is a special type of cause-and-
effect diagram that depicts related causes and effects for a
given situation. These help uncover the most significant
causes and effects involved in a situation.
[The PMI Guide to Business Analysis, pages 71] [Needs
Assessment]
3. A - New stories and changes are added to the bottom
of the backlog, where they sit until the next time the
backlog is reprioritized.
[The PMI Guide to Business Analysis, page 273]
[Traceability & Monitoring]
4. A - The goal model and business objectives models
describe the business objectives that the solution is meant
to achieve, along with the high-level features for the
solution. Either model can be used as a tool to help
prioritize the requirements according to how much they
support or achieve the objectives.
[The PMI Guide to Business Analysis, page 233]
[Analysis]
5. D - In projects with adaptive life cycles, the overall
scope of the project will be decomposed into a set of
https://t.me/PrMaB
requirements and work to be performed, referred to as
product backlog. Backlogs include product requirements
and user stories. [PMBOK® Guide 6th edition, Page 131]
[Traceability & Monitoring]
6. B - A burndown chart shows a team’s progress by
showing the number of story points remaining in the
project. The vertical axis shows the number of story points
remaining and the iterations are shown across the
horizontal axis. The linear trend of a burndown chart is
downward sloping. However, if no story points are
delivered during a particular iteration, the burndown chart
will remain flat for that iteration.
[The PMI Guide to Business Analysis, page 131]
[Analysis]
7. C - You have assembled the business case and gotten it
approved. The next logical step is to collaborate with the
project manager to develop the project charter. The rest of
the options are all activities that should have been
completed as part of the feasibility study that should have
been completed prior to assembling the business case.
[The PMI Guide to Business Analysis, pages 99, 103]
[Needs Assessment]
8. B - Among the given choices, only context diagrams
and event response tables are scope models; decision table
and decision trees are rule models. An event response
table defines the in-scope events that a system must react
to and also articulates the system’s responses to these
events.
[The PMI Guide to Business Analysis, page 192]
[Analysis]
9. A - Context diagram is a scope model that shows all
the direct system and human interfaces to systems within a
solution.
[The PMI Guide to Business Analysis, page 186]
[Analysis]
https://t.me/PrMaB
10. C - The purpose alignment model is used to help
facilitate discussions about priorities by placing product
features on a matrix according to their criticality and
market differentiation.
[The PMI Guide to Business Analysis, page 408]
[Analysis]
11. D - The process of moving future amounts back into
their present value, taking the time value of money into
account, is generally known as discounting.
[The PMI Guide to Business Analysis, page 90]
[Planning]
12. D - The sufficiency model is not a valid model. The
other choices are valid models used to analyze
stakeholders. [PMBOK® Guide 6th edition, Pages 512,
513] [Planning]
13. A - Facilitated workshops are more effective than
individual interviews as these allow participants to
collaborate and work toward a stated objective. In this
scenario a facilitated workshop might not be possible
because of the stakeholders’ schedule conflicts. The risk
with interviewing is that your stakeholders might not be
able to learn from each other’s ideas and collaboratively
work toward identifying the improvement opportunities.
The rest of the choices are stakeholder issues that are
irrelevant to the chosen elicitation technique.
[The PMI Guide to Business Analysis, page 79] [Needs
Assessment]
14. A - Products are created as parts of solutions to
address business needs; therefore, they provide business
value. A product can be tangible or intangible. In this
scenario both the ERP system, and the customer service
center are valid example of products that would add value
to the business.
[The PMI Guide to Business Analysis, page 9] [Needs
Assessment]
https://t.me/PrMaB
15. D - The lessons learned from the previous similar
projects are used throughout the project. These are already
part of the organizational process assets and are not
recorded in the final project report. The rest of the choices
are valid sections of a final project report. [PMBOK®
Guide 6th edition, Page 127] [Evaluation]
16. D - The team should consider making work visible
using Kanban boards and experimenting with limits for
the various areas of the work process in order to improve
flow.
[The PMI Guide to Business Analysis, page 233]
[Analysis]
17. C - Any process that formalizes the acceptance of the
deliverables of a project should be included in the scope
management plan. [PMBOK® Guide 6th Edition, Page
137] [Traceability & Monitoring]
18. D - Effective stakeholder management requires
addressing potential concerns that have not yet become
issues and anticipating future problems that may be raised
by stakeholders. Such concerns need to be identified and
discussed as soon as possible to assess associated project
risks. [PMBOK® Guide 6th edition, Page 524] [Analysis]
19. B - Solution evaluation activities are performed to
assess whether a solution has achieved the desired
business results. Solution evaluation consists of the work
done to analyze measurements obtained for the solution
by comparing the actual results of acceptance testing to
the expected or desired results. This cannot be done prior
to the development of the solution. The rest of the choice
are all valid points in time to conduct solution evaluation.
[The PMI Guide to Business Analysis, page 279]
[Evaluation]
20. D - MoSCoW stands for must have, should have,
could have, and won’t have. Applying MoSCoW rules to
project requirements ensure that the highest valued
business requirements/features are developed first.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 234]
[Planning]
21. D - A traceability matrix is a table that connects or
traces links between items. Most commonly, business
analysts use traceability matrices to trace requirements
backward to features and business objectives. A business
analyst can repurpose the traceability matrix to analyze
models to ensure that they are complete.
[The PMI Guide to Business Analysis, page 195]
[Analysis]
22. B - Business analysis planning reduces a number of
requirement-related risks instead of increasing them. The
rest of the choices are all correct statements.
[Business Analysis for Practitioners: A Practice Guide,
page 38; The PMI Guide to Business Analysis, page 127-
129] [Planning]
23. C - Agile and Kanban are subsets of Lean because
they are named instances of Lean thinking that share Lean
concepts such as “focus on value”, “small batch sizes”,
and “elimination of waste”.
[PMI’s Agile Practice Guide, 1st edition, Page 11]
[Analysis]
24. C - A feature model is a scope model that visually
represents all the features of a solution arranged in a tree
or hierarchical structure. Feature models identify the list
of features for a product roadmap.
[The PMI Guide to Business Analysis, page 95] [Needs
Assessment]
25. C - You can use the observation technique to identify
the workarounds being used by the product users to
compensate for the gaps in the product performance. Such
workarounds could be missed when using interviews and
other verbal communication techniques, because it may
not occur to users who are familiar with using the product
for a long time to mention how they compensate for a lack
of functionality. However, a typical disadvantage with the
https://t.me/PrMaB
observation technique is that the users usually behave
differently when being observed.
[The PMI Guide to Business Analysis, page 283]
[Analysis]
26. A - Any requirements that do not trace back to and
support the business objectives can be cut from scope or
assigned a low priority. Since the requirements were put
forward by key stakeholders, cutting these from the scope
is not an option.
[The PMI Guide to Business Analysis, page 233]
[Analysis]
27. B - Uncontrolled project scope changes are often
referred to as scope creep. Scope creep is often viewed
negatively, but can be managed using a change control
process. [PMBOK® Guide 6th edition, Page 168]
[Traceability & Monitoring]
28. D - The product backlog can be stored in a
requirements management tool or spreadsheet, or may
simply reside in a list and be tacked to a wall. However,
WIP backlogs are not uploaded to the organizational
process assets library until the project has been
completed.
[The PMI Guide to Business Analysis, page 213]
[Analysis]
29. D - In adaptive projects, iteration planning, or sprint
planning, is the activity used to identify the subset of
project backlog items from the product backlog that the
development team will work on for the current/upcoming
iteration or sprint. The iteration/sprint planning plans one
iteration/sprint at a time, not all of the remaining
iterations/sprints.
[The PMI Guide to Business Analysis, page 267]
[Traceability & Monitoring]
30. B - IRR is a measure of return to cost; therefore, the
higher the IRR, the higher the return a solution option is
expected to deliver. However, the IRR of both projects are
https://t.me/PrMaB
way less than what would be the cost of these
investments, i.e., the lending rate of the bank. In this case,
it is advisable to disregard both of the projects.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
31. A - Validate Scope is primarily concerned with the
acceptance of all the deliverables while Control Quality is
primarily concerned with meeting the quality
requirements specified for the deliverables. Control
Quality is performed before Validate Scope. The other
responses are incorrect. [PMBOK® Guide 6th Edition,
Page 164] [Traceability & Monitoring]
32. D - The stakeholder register is developed during the
Identify Stakeholders process. [PMBOK® Guide 6th
edition, Page 507] [Needs Assessment]
33. C - Within the context of use case analysis, the normal
flow is the set of steps that are followed through the use
case scenario when everything goes as planned or
expected.
[The PMI Guide to Business Analysis, page 402]
[Analysis]
34. A - Unconfirmed elicitation results consist of the
information obtained from completed elicitation activities.
These results of elicitation activities may be documented
either formally or informally. When you gathered the
notes and other artifacts produced during the workshop,
these were considered as informally documented.
However, when you will refine this and update the
requirements management tool, these will become
formally documented. Further, when this information will
be reviewed and validated by the senior stakeholders, this
will become confirmed elicitation results.
[The PMI Guide to Business Analysis, pages 169, 172]
[Analysis]
35. D - The day in the life (DITL) testing is a semi-formal
activity conducted by someone with in-depth business
https://t.me/PrMaB
knowledge. The results obtained from DITL testing
enable validation or evaluation of whether a solution
provides the functionality for a typical day of usage by a
role that interacts with the solution. The rest of the
choices are the tests that are conducted by the product
team internally.
[The PMI Guide to Business Analysis, page 393]
[Analysis]
36. B - Requirements are typically written at three levels:
business, stakeholder, and solution requirements.
[The PMI Guide to Business Analysis, page 216]
[Analysis]
37. D - While anything bad can happen, the primary risk
you are facing here with vague change requests is that
these can be interpreted in multiple ways. Since you
haven’t presented any deliverables for customer
inspection, you face a serious risk of deliverables
rejection during the Validate Scope process as the
customer might have interpreted these change requests in
a different way than the project team. [PMBOK® Guide
6th edition, page 131] [Traceability & Monitoring]
38. B - The business case usually provides information
from a business standpoint so that any investment in the
project can be justified. Typically it would contain both
the business need as well as the cost-benefit analysis. The
business case is an input to the Develop Project Charter
process. [PMBOK® Guide 6th edition, Page 77] [Needs
Assessment]
39. C - A report table is an interface model. The rest of
the choices are not examples of interface models.
[The PMI Guide to Business Analysis, page 185]
[Analysis]
40. B - You have been provided with the Situation
Statement. This implies that the Identify Problem or
Opportunity process has been completed. You now need
to perform the Assess Current State process prior to
https://t.me/PrMaB
performing Determine Future-State and Prepare for
Transition to Future-State processes.
[The PMI Guide to Business Analysis, page 63] [Needs
Assessment]
41. D - An imposed deadline or milestone is an example
of a constraint. Such project constraints are documented
in the scope statement. [PMBOK® Guide 6th edition,
Page 154] [Planning]
42. B - Help the team learn that they self-manage their
work. Consider Kanban boards to see the flow of work.
Consider a daily stand-up to walk the board and see what
work is where.
[The PMI Guide to Business Analysis, page 233]
[Analysis]
43. A - You need to define measurements that provide
indirect evidence that the benefits have been achieved.
You cannot choose to ignore benefit measurements if
benefits are intangible. Further, if the benefits are
intangible, neither NPV or IRR can be used.
[The PMI Guide to Business Analysis, page 279]
[Evaluation]
44. A - The three inputs to the Conduct Elicitation process
are elicitation preparation materials, product scope, and
the situation statement. For the elicitation event, the
participants will provide better quality inputs if they are
more aware of all these inputs.
[The PMI Guide to Business Analysis, page 164]
[Analysis]
45. B - The team doesn’t add items to the backlogs, only
the product owner is authorized to do that. If the issue
requires immediate attention, then the item needs to be
added to the iteration/sprint backlog.
[The PMI Guide to Business Analysis, pages 216, 400]
[Planning]
https://t.me/PrMaB
46. B - Job analysis is a technique that can be used to
identify the job requirements and competencies required
to perform effectively in a specific job or role. On the
other hand, gap analysis is conducted to understand the
gaps between the current-state and the future-state
processes. The other two choices are irrelevant.
[The PMI Guide to Business Analysis, page 117]
[Planning]
47. D - The Kanban method is based on the principle of
pulling work and does not prescribe the use of timeboxed
iterations. The Kanban method is less prescriptive than
some Agile approaches and less disruptive to being
implemented. Organizations can begin applying the
Kanban method with relative ease.
[The PMI Guide to Business Analysis, page 233]
[Analysis]
48. A - State tables are mostly used for analysis to ensure
that all transition combinations have been considered.
State diagrams are used for the ease of stakeholders to
visualize the valid transition flow. Note that stakeholders
can validate the transition flow using both models given
that they understand the models, however, unlike state
tables, state diagrams only focus on the valid transition
flows. The last two choices are applicable to both models.
[The PMI Guide to Business Analysis, page 203]
[Analysis]
49. A - A Business Analysis Center of Excellence is in
organizational structure created whereby business analysts
are managed centrally or are provided mentorships
centrally for the purpose of improving the business
analysis discipline across the organization.
[The PMI Guide to Business Analysis, page 389]
[Analysis]
50. A - IRR is a measure of return to cost; therefore, the
higher the IRR, the higher the return a solution option is
https://t.me/PrMaB
expected to deliver. In this case, option B has the
maximum IRR of 12%, so needs to be selected.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) - 15
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 15
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. You are currently helping an organization improve and
mature its business analysis skills. You are currently
developing a business analysis guide that would help all
organizational business analysts to consistently apply
business analysis skills to all future projects. Which of the
following statements regarding product requirements is
correct?
A. All product requirements must have a direct impact
on the organizational revenue.
https://t.me/PrMaB
D. The product requirements are determined prior to
identifying business need.
B. Organizational Chart
C. Process Flows
D. Wireframe
B. Backlog management
D. Predictive analytics
B. Initial planning
C. Prototyping
https://t.me/PrMaB
D. Backlog grooming
B. Through brainstorming
B. Histogram
C. Process Flow
https://t.me/PrMaB
be presented at the conference and has asked you to
represent the organization. You are required to present
your product’s roadmap at the conference. The product
roadmap can be presented in which of the following
formats?
A. Neither visual nor textual
B. Textual
C. Visual or textual
D. Visual
B. PMO
C. Business analysis
D. Capability
B. Baseline
C. User story
D. Benchmark
https://t.me/PrMaB
11. You are currently facilitating an elicitation workshop.
During the first half of the workshop you have used the
speedboat technique to elicit information about product
features that customers/stakeholders find problematic. In
the second half, you want to focus on the positive
influences. You now want to use the sailboat technique to
focuses on positive influences of the product. Where do
you document those influences?
A. Hull of the boat
B. Phases
C. Kanbans
D. Sprints
https://t.me/PrMaB
C. You are performing “Document Analysis” during
the Assess Current State process.
B. RACI
C. WBS
D. SWOT
B. Agile Coach
C. Agile Team
D. Product Owner
https://t.me/PrMaB
A. The business analysis work plan is a sub-
component of the business analysis plan.
B. Quality control
C. Workbench
D. Benchmarking
https://t.me/PrMaB
the complexity of the project, you have decided to
properly plan your elicitation approach. During the
Determine Elicitation Approach process, you need to
answer a number of questions EXCEPT:
A. When to conduct the elicitation activities?
https://t.me/PrMaB
A. 2200000
B. 600000
C. 1600000
D. 62092
B. Anova analysis
D. Ishikawa analysis
B. User stories
https://t.me/PrMaB
24. You are evaluating a solution’s performance post its
release. According to the business case, which was
developed three years ago at the project initiation, the
NPV of the project at 5% discount rate was $75,000.
During the project, the discount rate changed to 7%. What
will be the impact of this change?
A. The project’s NPV will decrease, which is a
favorable condition.
B. Estimation poker
C. Pert analysis
D. Bottom-up estimation
https://t.me/PrMaB
B. Speedboat
C. PERT
D. Spider web
https://t.me/PrMaB
B. At the point when the product is being developed.
https://t.me/PrMaB
31. A product team has identified that some of the product
requirements are conflicting with each other. To resolve
this, the team needs to know which change to pursue by
analyzing the stakeholder support available for that
change. Which of the following techniques can help you
in this situation?
A. Force field analysis
B. Root-cause analysis
C. PESTLE analysis
D. Kano analysis
https://t.me/PrMaB
B. Interactive communication
C. Push communication
D. Pull communication
B. Simulation
C. Real options
D. SWOT analysis
https://t.me/PrMaB
as well as for Erica‘s career. Although the project scope
statement was well-defined and requirements were
gathered from stakeholders in the planning phase, many
design change requests have come in from customers
during project execution. Which of the following tasks
must Erica perform to avoid scope creep caused by
uncontrollable changes?
A. Perform scope control and process all changes
through the integrated change control process
https://t.me/PrMaB
38. A business analyst develops several models during a
product life cycle. Many models, once developed, are
often revisited, and updated. However, the development
order might be different as some models can only be
developed until more detailed and refined product
information becomes available. In a product lifecycle,
which one of the following models is typically developed
first?
A. Context diagrams
C. Decision Trees
D. Process Flows
B. Prototyping
C. Forward traceability
D. Focus groups
B. Product backlog
https://t.me/PrMaB
C. Root cause analysis
D. Fishbone diagram
B. Flowcharts
C. Gantt charts
https://t.me/PrMaB
performance levels. Which of the following elicitation
techniques would you use to enable multiple SMEs to
collaboratively work together to identify the root causes
and the variances?
A. Interviews
B. Observation
C. Surveys
D. Facilitated workshops
B. Meetings
C. Kanban board
D. Process analysis
B. Tail
C. Head
D. Body
https://t.me/PrMaB
46. Recently a new product was launched by your
company. Although the company was able to witness
great numbers with regards to the sale of the product,
several performance issues were reported by the product
customers. You have been asked to investigate this matter
and conduct a detailed post-implementation solution
evaluation. You started with defining your solution
evaluation approach. Which of the following will be a key
input to this exercise?
A. Product scope
C. Sales figures
https://t.me/PrMaB
C. Develop the business case.
B. Context diagram
C. Feature model
B. Product backlog
C. Assumptions backlog
D. Feature list
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) - 15
Answer Key and Explanations
1. B - A product requirement is a condition or capability
that is required to be present in a product, service, or result
to satisfy a business need; hence the business need must be
identified prior to identifying a solution, product or its
requirements. A product requirement should be
independent of the design of the solution that addresses it
and the design of the solution must not drive the product
requirements. Products and solutions do not always have a
direct impact on the organizational revenue and instead
have indirect impacts, e.g., employee training, improving
goodwill etc.
[The PMI Guide to Business Analysis, page 9] [Needs
Assessment]
2. C - Process flows are in the process model category
and are used to visually document the steps or tasks that
people perform in their jobs or when they interact with a
solution.
[The PMI Guide to Business Analysis, page 198]
[Analysis]
3. B - Backlog management is a technique used in
adaptive approaches to maintain the requirements list.
Configuration management is a technique that is used in
predictive projects. The rest of the choices are irrelevant to
maintaining the requirements list.
[The PMI Guide to Business Analysis, page 265]
[Traceability & Monitoring]
4. B - On adaptive projects, iteration zero is the iteration
where the initial planning for all iterations occur. In some
approaches this is also called sprint zero.
[The PMI Guide to Business Analysis, page 399]
[Analysis]
https://t.me/PrMaB
5. B - Prioritization schemes provide a way of ranking a
set of ideas that are usually generated through
brainstorming. The other choices are not valid idea
generation techniques.
[The PMI Guide to Business Analysis, page 234]
[Planning]
6. A - A decision tree and decision table are rule models
that show a series of decisions and the outcomes to which
the decision leads. Decision trees and tables are often used
to model business rules. The rest of the choices are not
rule models.
[The PMI Guide to Business Analysis, page 189]
[Analysis]
7. D - The correct format for the definition of acceptance
criteria is: Given , when , then
[The PMI Guide to Business Analysis, page 219]
[Analysis]
8. C - Product roadmaps may be assembled in the form
of a text-based document or they may take the form of a
visual model.
[The PMI Guide to Business Analysis, page 94] [Needs
Assessment]
9. D - A capability is a function, process, service, or other
proficiency of an organization. Capabilities enable an
organization to achieve its strategy. Without the capability,
the goals and objectives of the strategy cannot be
achieved. This is the most relevant option from the given
list of choices.
[The PMI Guide to Business Analysis, page 64] [Needs
Assessment]
10. B - Baseline is the approved version of a work product
that can be changed only through formal change control
procedures and is used as a basis for comparison to actual
results.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 389]
[Analysis]
11. D - Sailboat is a variation of the speedboat technique
that focuses on positive influences rather than identifying
negative ones. All identified positive influences are
documented on the sails of the boat.
[The PMI Guide to Business Analysis, page 166]
[Analysis]
12. D - Agile release planning determines the number of
iterations required for the product development known as
sprints. [PMBOK® Guide 6th edition, Page 216]
[Analysis]
13. C - You are performing “Document Analysis” during
the Assess Current State process. Document analysis is an
elicitation technique performed during the Assess Current
State process to analyze existing documentation and
identify relevant product information.
[The PMI Guide to Business Analysis, page 68] [Needs
Assessment]
14. B - RACI model is a common type of responsibility
assignment matrix that uses Responsible, Accountable,
Consult, and Inform designations to define the
involvement of stakeholder in activities. This would
provide you with a great framework to complete your
process model. All of the other choices are irrelevant to
this objective.
[The PMI Guide to Business Analysis, page 118]
[Planning]
15. D - Conditions of Satisfaction is the criteria that is
used to gauge the success of a deliverable. Since the
product owner has the ultimate responsibility of the
project, the product owner provides the Conditions of
Satisfaction.
[The PMI Guide to Business Analysis, pages 216, 217]
[Planning]
https://t.me/PrMaB
16. A - The business analysis work plan is a
subcomponent of the business analysis plan. The business
analysis work plan includes level of effort estimates for
business analysis activities which can be compared to the
actual work effort to help the team improve future
estimates.
[Business Analysis for Practitioners: A Practice Guide,
page 65; The PMI Guide to Business Analysis, page 146]
[Planning]
17. D - Benchmarking is the technique of comparing
actual or planned project practices to those of other
projects to generate ideas for improvement and to provide
a basis by which to measure performance. [PMBOK®
Guide 6th edition, Page 281] [Traceability & Monitoring]
18. D - Setting ground rules will serve no purpose in this
situation. Escalation should not be the first thing you
should do. You cannot use the Feature Injection method as
the values associated with the features is currently the
bone of contention between the SMEs. You should first
try to resolve this using group decision-making
techniques.
[The PMI Guide to Business Analysis, page 89] [Needs
Assessment]
19. D - Elicitation results are not confirmed during the
Determine Elicitation Approach process, instead these are
confirmed during the Confirm Elicitation Results process.
All the other options are valid questions you need to
address during the Determine Elicitation Approach
process.
[The PMI Guide to Business Analysis, page 154]
[Planning]
20. B - Reading the international standards will be a
useful thing for benchmarking or defining the future state.
You could meet the VP of Operations and request the
documentation, but most probably she would ask you to
schedule a workshop with the SMEs and map the current
process flow.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 81] [Needs
Assessment]
21. D - NPV = discounted inflows – discounted outflows
Since the full investment, i.e. $1 million, needs to be
made now, we don’t have to discount the outflows.
However, we need to discount all the inflows by 10% per
annum. The discount formula is: Present Value (PV) =
Future Value / (1 + discount rate)^period For year 1: PV1
= 100,000 / 1.1^1 = 90,909 For year 2: PV1 = 100,000 /
1.1^2 = 82,645 For year 3: PV1 = 100,000 / 1.1^3 =
75,131 For year 4: PV1 = 100,000 / 1.1^4 = 68,301 For
year 5: PV1 = 1,200,000 / 1.1^5 = 745,106 Hence the
total PV of the inflows = 1,062,092 NPV = 1,062,092 –
1,000,000 = $62,092 [PMBOK® Guide 6th edition, Pages
34, 473] [Needs Assessment]
22. A - Kano analysis is a technique used to model and
analyze product features by considering the features from
the viewpoint of the customer. None of the rest of the
choices could help you with this analysis.
[The PMI Guide to Business Analysis, page 79] [Needs
Assessment]
23. A - Agendas, meeting minutes, parking lot lists, and
some types of models, although necessary to organize
work and perform effectively, are not considered business
analysis deliverables. These items are often called work
products and are created in order to perform the work but
are not a promised deliverable that will be tracked and
managed. On the other hand, the rest of the choices are
business analysis deliverables.
[Business Analysis for Practitioners: A Practice Guide,
page 62; The PMI Guide to Business Analysis, page 127]
[Planning]
24. B - The NPV expresses the value of an investment in
today’s value of money. A higher discount rate reduces
the present value of future returns and hence reduces net
present value; which is not a favorable condition.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, pages 90, 283]
[Evaluation]
25. B - Estimation poker is a collaborative relative
estimation technique in which there is an agreed-upon
scale used for the relative estimates. This is a typical user
story estimation technique used in Agile projects.
[The PMI Guide to Business Analysis, page 396]
[Analysis]
26. A - Product box is an elicitation technique that uses
game play to focus on the features of a product that are
important to the customer. Speedboat method focuses on
problematic features of the product. Spider web method
focuses on relationships between the product being
analyzed and other products. PERT is not a collaboration
games technique.
[The PMI Guide to Business Analysis, page 166]
[Analysis]
27. B - You need to develop a sequence diagram to meet
the team’s requirement. Sequence diagrams describe how
users or system processes interact with one another across
any involved users or systems and the order in which the
processes or steps are performed.
[The PMI Guide to Business Analysis, page 199]
[Analysis]
28. D - Display-action-response models are generally
created at the point when functional requirements or
acceptance criteria are being specified.
[The PMI Guide to Business Analysis, page 200]
[Analysis]
29. A - Requirements management tools allow
requirements and other product information to be captured
and stored in a repository. These tools help maintain audit
trails and perform version control to assist with change
management. These tools also facilitate review and
approval processes thorough workflow functionality.
Requirements management tools catered to adaptive
https://t.me/PrMaB
projects may include additional functionality to create and
manage product and iteration backlogs, and produce
burndown charts. A requirements management tool does
not help define high-quality product information.
[The PMI Guide to Business Analysis, page 260]
[Traceability & Monitoring]
30. A - You can easily rule out scoping and estimating.
Verification and validation are often confused.
Verification is the evaluation of whether the product
complies with regulation, requirement, specification, or
imposed conditions. Validation is the assurance that the
product meets the needs of the customer.
[Business Analysis for Practitioners: A Practice Guide,
page 58; The PMI Guide to Business Analysis, page 127]
[Planning]
31. A - Force field analysis is a decision-making
technique that can be used to help the product team
analyze whether there is sufficient support to pursue a
change. The rest of the choices cannot help the product
team in the current situation.
[The PMI Guide to Business Analysis, page 398]
[Analysis]
32. B - Whichever mechanism is used to decide how to
slice the epics, the slices are prioritized by the value that
each slice delivers.
[The PMI Guide to Business Analysis, page 214]
[Analysis]
33. B - Interactive communication is the most efficient
form of communication as it requires multidirectional
exchange of information. [PMBOK® Guide 6th edition,
Page 374] [Analysis]
34. C - For complex projects, where progressive
elaboration is required, elicitation is performed iteratively
with analysis.
[The PMI Guide to Business Analysis, page 155]
[Analysis]
https://t.me/PrMaB
35. A - Weighted ranking is a technique used to support
objective decision making. It is typically performed with
the use of a weighted ranking matrix. A weighted ranking
matrix or table is used to weight, rate, and score each
criterion against a set of options.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
36. A - All scope changes must be controlled in a project
through the Control Scope process. However, scope
control must also ensure that all changes requested by
customers go through the Perform Integrated Change
Control process. This way, scope creep can be avoided,
and project changes can be managed. Hence, Erica must
perform scope control and process all changes through the
Integrated Change Control process. [PMBOK® Guide 6th
edition, Page 168] [Traceability & Monitoring]
37. B - As a seasoned business analyst, first you need to
try to resolve the problem yourself. Spending more time
with the head of procurements and finding opportunities
for collaboration might help. If all your efforts fail, you
then might consider escalation of the situation.
[Business Analysis for Practitioners: A Practice Guide,
page 43; The PMI Guide to Business Analysis, page 115-
116] [Planning]
38. A - Context diagrams are generally created early to
define scope and can be updated as new information is
identified. The rest of the choices are the models that are
developed later as more information becomes available.
[The PMI Guide to Business Analysis, page 186]
[Analysis]
39. C - Forward traceability is a technique that establishes
the relationship of a requirement to the design or code
which implements it. On the other hand, backward
traceability establishes the relationship of a requirement to
the scope, business goals, or business objectives from
which it originated.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, pages 388, 398]
[Analysis]
40. A - In business objectives models, busines problems
and business objectives decompose high-level business
strategies into lower-level business problems and
objectives to visually represent the value of the project
and how the solution will achieve the business objectives.
[The PMI Guide to Business Analysis, page 195]
[Analysis]
41. A - Burndown charts are the primary way of tracking
and communicating the team’s progress against the
release plan.
[The PMI Guide to Business Analysis, page 131]
[Analysis]
42. A - Since the product requirements are not known
upfront and can only be discovered through a series of
prototyping iterations, an Agile approach is suitable for
the design phase. Once the product is developed, the mass
rollout can be manage using a predictive life cycle.
[PMBOK® Guide 6th edition, page 19] [Needs
Assessment]
43. D - Facilitated workshops use a structured meeting led
by a skilled, neutral facilitator and a carefully selected
group of stakeholders to collaborate and work together
toward a stated objective. This is the technique you should
use to have the SMEs collaboratively work together to
identify the root causes and the variances.
[The PMI Guide to Business Analysis, page 283]
[Evaluation]
44. A - A questionnaire is the right tool to be used if you
have a large population base and you need to quickly
identify which features are valued more than the others.
[The PMI Guide to Business Analysis, page 68]
[Planning]
45. C - The fishbone diagram starts with recording the
problem or issue at the fish’s head.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 70]
[Planning]
46. A - Product scope is defined as the features and
functions that characterize a solution. The product scope
and the business goals and objectives on which a solution
is based provide suggestions as to what types of
information should be collected and measured for
evaluation purposes.
[The PMI Guide to Business Analysis, page 288]
[Evaluation]
47. C - The most effective method would be to use a
Kanban board as that would provide a continuous means
to visually communicate project status to the team.
[The PMI Guide to Business Analysis, page 233]
[Analysis]
48. A - Common techniques that can be used in the
discovery of stakeholders are brainstorming, interviews,
surveys, and organizational charts, to name a few.
[Business Analysis for Practitioners: A Practice Guide,
page 39; The PMI Guide to Business Analysis, page 111]
[Planning]
49. A - Use case is a process model, while the rest of the
choices are all scope models.
[The PMI Guide to Business Analysis, page 185]
[Analysis]
50. B - In projects with adaptive life cycles, the overall
scope of the project will be decomposed into a set of
requirements and work to be performed, sometime
referred to as a product backlog. [PMBOK® Guide 6th
edition, Page 131] [Planning]
https://t.me/PrMaB
PMI-PBA DOMAIN AREA
TEST: NEEDS
ASSESSMENT
Practice Questions
Test Name: Domain Area Test: Needs Assessment
Total Questions: 20
Correct Answers Needed to Pass:
14 (70.00%)
Time Allowed: 30 Minutes
Test Description
This practice quiz specifically targets your knowledge of the
Needs Assessment PMI-PBA Domain area.
Test Questions
1. Which of the following processes belong to the
planning process group?
A. Identify Stakeholders
https://t.me/PrMaB
B. Value chain maps
C. SIPOC
B. Situation statement
D. Business case
https://t.me/PrMaB
stakeholders. The stakeholders are subject matter experts
in their own domains but do not have experience in
developing product roadmaps. Which of the following
techniques should you use?
A. 80/20 rule
B. Affinity diagram
C. Brainstorming
D. Facilitated workshop
https://t.me/PrMaB
B. Real options
C. Dictatorship
D. Affinity diagram
B. Terminating
C. Transitioning
D. Releasing
https://t.me/PrMaB
10. Visual communication is the transmission of
information and ideas using graphics. This is generally
considered to be more powerful than verbal
communication. Which of the following techniques
should you use to elicit new product high-level
requirements from the stakeholders in situations where
visual communication is more effective than verbal
communication?
A. Brainstorming
B. Prototyping
D. Multi-voting
https://t.me/PrMaB
projects. In your opinion, what’s wrong with this
situation?
A. The consultant went straight into “determining the
future-state” prior to assessing the current state.
https://t.me/PrMaB
B. The business must initiate a process improvement
initiative to optimize the supply chain processes
prior to their digitization.
https://t.me/PrMaB
17. Your organization has recently released a product into
the market and has collected customer feedback through
surveys. You are now reviewing these results and using a
Kano model to analyze the product’s features. Which
product features will you classify as “performance
features”?
A. The features that either satisfy or dissatisfy the
customers depending upon how well they perform.
B. Capability framework
C. Capability table
https://t.me/PrMaB
should you use during the workshop to present this
information to the stakeholders?
A. Ishikawa diagram
B. Pareto diagram
C. Tornado diagram
B. Invest in option A
D. Invest in option B
https://t.me/PrMaB
PMI-PBA Domain Area Test: Needs
Assessment
Answer Key and Explanations
1. B - All of the given choices are the processes from the
project stakeholder management knowledge area.
However, only the Plan Stakeholder Engagement process
belongs to the planning process group. [PMBOK® Guide
6th edition, Page 25] [Needs Assessment]
2. D - Value stream maps focus on specific areas (process
level) of an organization, e.g., the situation given in the
scenario. On the other hand, value chain maps analyze all
of the activities (organizational level) within an
organization. The other two models do not focus on value-
added activities.
[The PMI Guide to Business Analysis, pages 70] [Needs
Assessment]
3. B - From the given options, only the situation
statement is an output of the Identify Problem or
Opportunity process. A situation statement is an objective
statement of a problem or opportunity.
[The PMI Guide to Business Analysis, page 62] [Needs
Assessment]
4. D - An interrelationship diagram is a special type of
cause-and-effect diagram that depicts related causes and
effects for a given situation. Factors (or nodes) that have a
large number of “outgoing” arrows are the sources of the
problem.
[The PMI Guide to Business Analysis, pages 71; Business
Analysis for Practitioners: A Practice Guide, page 23]
[Needs Assessment]
5. D - Brainstorming and facilitated workshop are good
choices. However, given the limited experience of the
stakeholders in developing roadmaps, a facilitated
https://t.me/PrMaB
workshop is a better option. Facilitated workshops use a
structured meeting led by a skilled, neutral facilitator.
[The PMI Guide to Business Analysis, page 95] [Needs
Assessment]
6. C - The “inject features” step in the Feature Injection
technique involves selecting the features with maximum
business value and presenting these in the form of
scenarios.
[The PMI Guide to Business Analysis, page 89] [Needs
Assessment]
7. B - Real options is a decision-making thought process
that can be used on projects that follow an adaptive
delivery model. Two fundamental principles are applied to
decision making with real options. The first is to reduce
the number of decisions that need to be made in the short
term, and the second is to delay all decision making until
as late as possible.
[The PMI Guide to Business Analysis, page 89] [Needs
Assessment]
8. D - The six Business Analysis Process Groups are:
Defining and Aligning, Initiating, Planning, Executing,
Monitoring & Controlling and Releasing.
[The PMI Guide to Business Analysis, page 21] [Needs
Assessment]
9. B - Several key elements are typically elicited and
documented in a product roadmap, including strategy
information, portfolio, program, initiatives, product vision,
success criteria, market forces, product releases, features
and timelines.
[The PMI Guide to Business Analysis, pages 93, 94]
[Needs Assessment]
10. B - Group decision-making techniques, brainstorming
and multi-voting techniques do not involve any visual
communication approach. Prototyping uses models that
provide a visual representation of what may eventually
evolve into a product’s design.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 61] [Needs
Assessment]
11. B - Adaptive projects often create a brief statement of
project intent which states the business objectives, value
propositions, benefits, goals, and milestones, etc. It may
also include very high-level user epics that are later
broken down into user stories. At this stage, you need to
identify the user epics that comprise the project scope.
[The PMI Guide to Business Analysis, page 62] [Needs
Assessment]
12. A - The CEO’s engagement of the consultant for a
process improvement job identified by the executive
leadership team indicates that the Identify Problem or
Opportunity process was completed in some shape or
form. The next step is to assess the current state which
seems to be ignored by the hired consultant.
[The PMI Guide to Business Analysis, page 63] [Needs
Assessment]
13. C - Configuration item verification and audit is related
to configuration management instead of change
management. [PMBOK® Guide 6th edition, Pages 118,
119] [Needs Assessment]
14. B - A product requirement is a condition or capability
that is required to be present in a product, service, or
result to satisfy a business need. All of the given choices
are valid business requirements but initiating a process
improvement initiative prior to the implementation of the
SCM system is outside the scope of the SCM system
implementation, hence not a SCM system product
requirement.
[The PMI Guide to Business Analysis, page 9] [Needs
Assessment]
15. A - The net present value (NPV) is a cost benefit
analysis technique. It is a monetary value expressed as the
difference of the present value of revenues and the present
value of expenditures over the lifecycle of the product or
https://t.me/PrMaB
service delivered by the project. [PMBOK® Guide, 6th
edition, Page 60] [Needs Assessment]
16. B - Benchmarking is a comparison of an
organization’s practices, processes, and measurements or
results against established standards or against what is
achieved by a “best in class” organization within its
industry or across industries. Selecting an organization
from a different industry will not provide the desired
outcomes.
[The PMI Guide to Business Analysis, page 60] [Needs
Assessment]
17. A - The performance features are the ones that either
satisfy or dissatisfy the customers depending upon how
well they perform. The customers use these features to
consciously evaluate the final solution.
[The PMI Guide to Business Analysis, page 80] [Needs
Assessment]
18. B - A capability framework is a description of the
range of capabilities an organization needs to achieve its
goals and objectives. Some organizations refer to these
types of frameworks as maturity models which can be
used to rank capability maturity levels.
[The PMI Guide to Business Analysis, page 66] [Needs
Assessment]
19. D - Process flows describe business processes and the
ways stakeholders interact with those processes. Process
flows can be used to document current as-is processes of
the business. The rest of the choices are not applicable to
the context of the scenario.
[The PMI Guide to Business Analysis, page 70] [Needs
Assessment]
20. A - IRR is a measure of return to cost; therefore, the
higher the IRR, the higher the return a solution option is
expected to deliver. In this case, investing in the fixed
term deposit makes more sense than investing in any of
the options since the IRR of both options are lower than th
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) - 16
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 16
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. You are currently helping a junior business analyst
plan her business analysis activities on a website
development project. You want to ensure that the business
analyst considers a number of factors while planning for
elicitation. Which of the following are key factors that
must be considered when planning for elicitation?
A. Number and location of stakeholders and types and
level of detail required in business analysis
deliverables.
https://t.me/PrMaB
D. Project lifecycle, type of project, time constraints,
budget, number and location of stakeholders, and
types and level of detail required in business
analysis deliverables.
C. Context diagram
D. Data model
https://t.me/PrMaB
C. Add the change request as a new user story in the
iteration backlog.
B. Competitive Analysis
D. Document Analysis
https://t.me/PrMaB
D. Review the detailed reports with the key
stakeholders.
B. Report Table
C. Decision Tree
D. Context Diagram
https://t.me/PrMaB
A. Activity matrix
B. Burndown chart
C. War room
D. Kanban board
B. DITL
C. CRUD
D. DEEP
B. Normal flow
C. Postconditions
D. Alternative flow
https://t.me/PrMaB
12. A project team is currently analyzing its current
iteration progress and reviewing the following chart. What
is this chart called?
A. Control Chart
B. Burndown Chart
D. Histogram
https://t.me/PrMaB
completed tasks took more than twice the amount of time
that was allotted for them. Where did Peter go wrong?
A. Peter should have stressed on early definition of
detailed requirements.
https://t.me/PrMaB
B. Features within the least development effort are
selected for development.
B. PERT analysis
C. Variance analysis
D. Sensitivity analysis
https://t.me/PrMaB
The team is now brainstorming over the requirements to
deliver this project. The team believes that they need to
carry out extensive system security and penetration testing
and additional resources will be required to perform this
task. This requirement is part of:
A. Scope creep
B. Project Scope
C. Product Scope
B. Needs Assessment
C. Collect Requirements
https://t.me/PrMaB
D. Remove Peter from the project and replace him
with a more senior business analyst.
B. Medium
C. Encoding
D. Decoding
https://t.me/PrMaB
A. Contributing in the development of the project
charter.
https://t.me/PrMaB
project stakeholders do not have any experience in using
the technology being proposed by the project, the project
stakeholders are struggling to define the product
requirements. Which of the following business analysis
techniques provides a visual representation of a product’s
design during its conceptual design stage?
A. Low-fidelity prototyping
B. High-fidelity prototyping
C. Fishbone diagram
D. Kano analysis
29. The WBS represents all product and project work. The
total work at the lowest levels should roll up to the higher
levels so that nothing is left out and no extra work is
performed. This principle is also the:
A. Ground rule
B. 80/20 rule
C. Pareto’s rule
https://t.me/PrMaB
30. Your organization has recently won a project to
construct a 5-star hotel in the city. As a contractual
obligation, you are now support to provide your client a
hierarchical structure of project resources organized by
category and resource type, used in planning, managing
and controlling project work. What do you need to
develop and share with your client?
A. Resource Breakdown Structure
B. Resource Pool
D. Team structure
B. Must-have
C. Performance
https://t.me/PrMaB
D. Delighters
https://t.me/PrMaB
B. Ask the business analyst to revalidate the business
requirements and the potential solutions.
https://t.me/PrMaB
A. Implementation dependency
B. Discretionary dependency
C. Value dependency
D. Subsets
D. Validate Requirements
https://t.me/PrMaB
Which of the following models would help you identify
likely use cases, user stories, and system flows?
A. Entity relationship diagram
C. Context diagram
D. Data dictionary
https://t.me/PrMaB
B. Plan Scope Management, Collect Requirements,
Define Scope, Validate Scope, Create WBS, and
Control Scope
https://t.me/PrMaB
A. Analyze the reasons why this technology was not
considered earlier.
https://t.me/PrMaB
C. The information provided in the persona is
behavioral in nature.
B. Hoshin Kanri
C. Planning Poker
D. Kanban Planning
C. Expert Judgment
D. Decomposition
https://t.me/PrMaB
and other product information. On adaptive projects, this
process falls under the scope of:
A. Daily standups
B. Backlog refinement
C. Retrospectives
D. Kanban
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) - 16
Answer Key and Explanations
1. D - There are a number of factors to consider when
planning for elicitation: stakeholder group characteristics
and dynamics, project lifecycle, characteristics of the
technique, type of project, time constraints, budget,
number of key stakeholders involved and their location,
types of requirement deliverables being produced, level of
detail required in business analysis deliverables,
techniques that are familiar to the business analyst.
[Business Analysis for Practitioners: A Practice Guide,
page 53; The PMI Guide to Business Analysis, page 127]
[Planning]
2. C - A context diagram is a scope model that shows all
the direct system and human interfaces to systems within a
solution. A context diagram clearly depicts the in-scope
systems and any inputs or output, including the system or
actors providing or receiving them.
[The PMI Guide to Business Analysis, page 186]
[Planning]
3. A - Since Shawn is in the execution phase and
stakeholders are requesting project information, he must
respond through the Manage Communications process.
The communications management plan, organizational
process assets and work performance reports are inputs to
this process. Shawn can use any of these documents to
respond to their requests. The project’s business case is not
of much help at this stage. [PMBOK® Guide 6th edition,
Page 379] [Analysis]
4. A - In adaptive projects, the product owner decides to
abnormally terminate the user story or add new ones in
collaboration with the product team. The product team
cannot decide this on their own.
[The PMI Guide to Business Analysis, page 264]
[Traceability & Monitoring]
https://t.me/PrMaB
5. D - Document analysis is an elicitation technique used
to analyze existing documentation to identify information
relevant to the requirements. While identifying problems
or opportunities, this technique involves reviewing
information relevant to the business need. For example,
strategic goals and objectives, performance goals and
results, customer survey results, documentation about
current processes, and business rules might be analyzed.
[The PMI Guide to Business Analysis, page 61] [Needs
Assessment]
6. B - A report table is an interface model that describes
detailed requirements for a single report. Report tables are
usually created any time after an initial list of reports for a
solution has been identified and prioritized. Report tables
typically contain technical information that generally is
not suitable for the consumption of the stakeholders. Since
the stakeholders have already approved the prototypes,
you can send the prototypes and the reports to the
development team for development.
[The PMI Guide to Business Analysis, page 201]
[Analysis]
7. A - A display-action-response model is used in
conjunction with a prototype or wireframe to connect the
user interface element requirements to a visual
representation.
[The PMI Guide to Business Analysis, page 199]
[Analysis]
8. C - The models are organized into five categories:
Scope models, process models, rule models, data models,
and interface models.
[The PMI Guide to Business Analysis, page 184]
[Analysis]
9. D - This is an example of Kanban board. A Kanban
board provides a means to visualize the flow of work,
make impediments easily visible, and allow flow to be
managed by adjusting the work in process limits.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 233]
[Analysis]
10. D - DEEP Describes the characteristics that a product
backlog needs to demonstrate to be considered well-
defined. DEEP Is an acronym that stands for detailed
appropriately, estimated, emergent, and prioritized.
[The PMI Guide to Business Analysis, page 394]
[Analysis]
11. D - Each use case contains a normal flow, which is the
most common scenario of interactions between the system
and user, as well as alternative and exception flows, where
the scenario diverges from the normal flow. In this
scenario, the secondary approval workflow needs to be
documented as the alternative flow of the use case.
[The PMI Guide to Business Analysis, page 214]
[Analysis]
12. B - This is an example of a Burndown Chart. A
burndown chart is a graphical representation of work left
to do versus time. The outstanding work is shown on the
vertical axis and time along the horizontal. It is useful for
predicting when all of the work will be completed.
[PMBOK® Guide, 6th edition, Page 226] [Traceability &
Monitoring]
13. B - In business analysis, product roadmaps provide
important information about a product, providing insights
about the product vision and how the product will support
organizational strategy, business goals and objectives over
time. To develop this you need to graphically display all
high-level product features along with the sequence in
which the features will be built and delivered.
[The PMI Guide to Business Analysis, page 95]
[Evaluation]
14. D - Adaptive and Agile methods are more suited to
projects with a huge amount of uncertainties. As the
project scope wasn’t defined at the start and the
requirements were expected to change throughout the
https://t.me/PrMaB
project lifecycle, this is the kind of project that benefits
the most from adaptive approaches. [PMBOK® Guide 6th
edition, page 665] [Planning]
15. B - Feasibility studies are typically conducted as a part
of the Determine Viable Options and Provide
Recommendation process. Feasibility study results are the
output of this process.
[The PMI Guide to Business Analysis, page 85] [Needs
Assessment]
16. D - The “inject features” step in the Feature Injection
technique involves selecting the features with maximum
business value and presenting these in the form of
scenarios.
[The PMI Guide to Business Analysis, page 89]
[Planning]
17. C - Confirm Elicitation Results will be preformed
after the event. Before each elicitation event, you need to
carry out the Prepare for Elicitation process. Note that
Identify Problem or Opportunity and Assemble Business
Case processes are performed early during the project and
are not repeated prior to each elicitation event.
[The PMI Guide to Business Analysis, page 160]
[Analysis]
18. C - Variance analysis is a technique for determining
the cause and degree of difference between the baseline
and actual performance. In the given scenario, variance
analysis must be applied to study the causes of the
differences between the baseline and actual performance.
[The PMI Guide to Business Analysis, page 293]
[Evaluation]
19. B - This requirement is part of the project scope. The
project scope defines the work that needs to be done to
deliver a product, service, or result. This is different than
product scope, which is the set of features and functions
that characterize the required solution/product.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 17] [Needs
Assessment]
20. B - For complex and high value projects, activities of
business analysis get started well before the project is
initiated. Typically in such cases, the requirements
management process starts with a business need analysis.
The rest of the choices are the processes that are
performed once the project has been initiated. [PMBOK®
Guide 6th edition, Page 132] [Needs Assessment]
21. C - The business analysis approach is simply the
method a business analyst uses when managing and
performing the business analysis activities on a project.
The business analysis approach is documented in the
business analysis plan. Therefore, the first step is to
identify if this plan exists.
[Business Analysis for Practitioners: A Practice Guide,
page 38; The PMI Guide to Business Analysis, page 127-
129] [Planning]
22. C - A report table is an interface model that describes
detailed requirements for a single report. Report tables are
usually created any time after an initial list of reports for a
solution has been identified and prioritized.
[The PMI Guide to Business Analysis, page 201]
[Analysis]
23. A - Anything that interferes with the meaning of a
message is considered noise. [PMBOK® Guide 6th
edition, Page 372] [Analysis]
24. B - Many projects are initiated with tight timelines
that place pressure to address the tactical activities before
the plan. The project team should avoid the urge to rush
into requirements elicitation without first understanding
the expectations for the business analysis process and the
road map for pursuing the work. The rest of the choices
are all good practices.
[Business Analysis for Practitioners: A Practice Guide,
page 38; The PMI Guide to Business Analysis, page 127-
https://t.me/PrMaB
129] [Planning]
25. D - You would conduct regression test and evaluate
the result prior to releasing a solution and conducting the
UAT. During the post-implementation review you would
rely on other performance data as inputs such as impact
on productivity, system adoption rate, and levels of
customer satisfaction etc.
[The PMI Guide to Business Analysis, page 282]
[Evaluation]
26. C - Several businesses exist without documented
business architectures, processes and strategies. The
absence of documentation doesn’t mean these businesses
do not have architectures, processes or strategies.
Although the absence of this documentation is not a
favorable thing for an analyst, this shouldn’t impede the
capability analysis. However, without historical data
conducting a business capability analysis will be
extremely hard because the historical data is used to
establish performance standards by which current and
future performance is evaluated.
[The PMI Guide to Business Analysis, page 66] [Needs
Assessment]
27. A - Kano analysis and fishbone diagram are irrelevant
to the question. Low-fidelity prototyping uses models that
provide a visual representation of what may eventually
evolve into a product’s design. High-fidelity prototyping
is used during the actual development of the product.
[The PMI Guide to Business Analysis, page 61] [Needs
Assessment]
28. D - Stakeholder lists can quickly become long and
difficult to manage; therefore, placing stakeholders into
groups based on their characteristics will allow for easier
management of the information. Establishing a
stakeholder register without grouping the stakeholder will
not yield any benefit. The other two choices are irrelevant.
https://t.me/PrMaB
[Business Analysis for Practitioners: A Practice Guide,
page 44; The PMI Guide to Business Analysis, page 115-
116] [Planning]
29. D - The WBS represents all product and project work.
The total work at the lowest levels should roll up to the
higher levels so that nothing is omitted and no extra work
is performed. This principle is also called the 100% rule.
[PMBOK® Guide 6th edition, Page 161] [Planning]
30. A - The Resource Breakdown Structure (RBS) is a
hierarchical structure of team and physical resources
related by category and resource type. [PMBOK® Guide
6th edition, Page 316] [Planning]
31. D - A questionnaire is the right tool to be used if you
have a large population base and you need to quickly
identify which features are valued more than the others.
The rest of the choices are incorrect.
[The PMI Guide to Business Analysis, page 68] [Analysis]
32. B - According to the Kano model, once some amount
of a must-have feature has been implemented, customer
satisfaction cannot be increased by adding more of that
feature. Also, no matter how much of a must-have feature
is added, customer satisfaction never rises above the mid-
point. We can observe the law of diminishing marginal
returns on such features.
[The PMI Guide to Business Analysis, page 79]
[Planning]
33. A - At this stage, the inadequacy of the time
allowance is an assumption. However, you need to test
this assumption once you have your business analysis plan
ready. Since the business analysis planning might take
some time, it is best to convey your concerns to the
project manager immediately.
[Business Analysis for Practitioners: A Practice Guide,
page 68; The PMI Guide to Business Analysis, page 127]
[Planning]
https://t.me/PrMaB
34. A - Rolling wave planning resembles agile approaches
since it allows the project management team to wait until
the deliverables or subcomponents are agreed on, so the
details of the WBS can be developed. [PMBOK® Guide
6th edition, Page 160] [Needs Assessment]
35. B - Prototyping both solutions will waste valuable
resources. The best strategy is to validate the requirements
and the proposed solution through the business analyst as
they are ultimately responsible for managing the business
requirements. [PMBOK® Guide 6th edition, page 132]
[Traceability & Monitoring]
36. B - Requirements are prioritized based on a number of
factors such as: value, cost, difficulty, regulatory, and risk,
etc. Chronological order of the requirements elicitation
should be irrelevant and requirements discovered later
could be of higher business value.
[Business Analysis for Practitioners: A Practice Guide,
page 55; The PMI Guide to Business Analysis, page 127]
[Planning]
37. C - This is the example of a value dependency. The
system provides value by estimating the amount of work
for each incoming request. If the amount of work cannot
be estimated to a reasonable degree, there is no value in
performing resource levelling as that will then also be
inaccurate and introduce delays because each work item
has its own processing requirements.
[The PMI Guide to Business Analysis, page 259]
[Traceability & Monitoring]
38. A - Maintaining the integrity of baselines is done in
the Perform Integrated Change Control process. This
process is conducted from project inception through
project completion. [PMBOK® Guide 6th edition, Page
113] [Traceability & Monitoring]
39. A - Verification is the process of reviewing the
requirements and other product information for errors,
conflicts, and adherence to quality standards. Verification
also involves evaluating whether requirements and other
https://t.me/PrMaB
product information complies with a regulation,
specification, or imposed condition. During the Verify
Requirements process you will evaluate the compliance of
product requirements with the federal regulation.
[The PMI Guide to Business Analysis, page 221]
[Analysis]
40. B - Event response tables are created to help identify
likely use cases, user stories, or system flows.
[The PMI Guide to Business Analysis, page 192]
[Analysis]
41. A - It is not uncommon for business stakeholders to
struggle in trying to articulate their requirements in detail
required for product development. Agile methods solve
this problem by allowing a business analyst to document
the stakeholders needs as user stories and work on
elaborating these stories later. Once the user stories have
been captured, the next logical step is to add these to the
product backlog.
[The PMI Guide to Business Analysis, page 215]
[Analysis]
42. D - The logical sequence of the six scope management
processes is: Plan Scope Management, Collect
Requirements, Define Scope, Create WBS, Validate
Scope and Control Scope. [PMBOK® Guide 6th edition,
Page 129] [Planning]
43. A - When deciding the order of business analysis
activities, the project manager and business analyst should
work together to determine how the resource availability
will impact sequencing decisions.
[Business Analysis for Practitioners: A Practice Guide,
page 54; The PMI Guide to Business Analysis, page 156]
[Planning]
44. B - Force field analysis is a decision-making
technique that can be used to help product teams analyze
whether there is sufficient support to pursue a change.
https://t.me/PrMaB
Using this model, a team identifies the forces for or
against a proposed change.
[The PMI Guide to Business Analysis, page 266]
[Planning]
45. B - The legacy system users cannot provide technical
information of the system. Acceptance testing is irrelevant
to the situation and penetration testing is not advisable for
this matter. Your best bet is to have your development
team review the design documents of the legacy system
and analyze the interaction requirements.
[The PMI Guide to Business Analysis, page 167]
[Analysis]
46. A - Persona analysis is a technique that is conducted
to analyze a class of users for understanding their needs
and behaviors. A persona has a relationship with a class of
users and is not created for every user; one persona
typically represents more than one stakeholder, similarly,
one stakeholder can be associated with more than one
persona.
[Business Analysis for Practitioners: A Practice Guide,
page 45; The PMI Guide to Business Analysis, page 115-
116] [Planning]
47. A - Rolling Wave Planning is an iterative planning
technique in which the work to be accomplished in the
near term is planned in detail, while the work in the future
is planned at a higher level.
[The PMI Guide to Business Analysis, page 134]
[Planning]
48. D - The decomposition technique allows the project
manager to create smaller and more manageable pieces of
work from the larger work packages. [PMBOK® Guide
6th edition, Page 185] [Planning]
49. B - On adaptive projects, conducting elicitation is a
part of backlog refinement or elaboration. Elicitation of
high-level product information occurs to develop the
https://t.me/PrMaB
backlog, and elicitation of more detailed product
information happens within subsequent iterations.
[The PMI Guide to Business Analysis, page 169]
[Analysis]
50. A - Unconfirmed elicitation results consist of the
information obtained from completed elicitation activities.
These results of elicitation activities may be documented
either formally or informally. When you gathered the
notes and other artifacts produced during the workshop,
these were considered as informally documented.
However, when you will refine this and update the
requirements management tool, these will become
formally documented.
[The PMI Guide to Business Analysis, page 169]
[Analysis]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) - 17
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 17
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. The system that includes the process for submitting
proposed changes, reviewing and approving proposed
changes, defining approval levels for authorizing changes,
and providing a method to validate approved changes is
the:
A. Configuration Management System
B. Approval Plan
https://t.me/PrMaB
reasons to develop models for the elicited information
EXCEPT:
A. Documenting the models in the lessons learned
library.
https://t.me/PrMaB
A. Conduct Elicitation
B. Scatter diagram
C. Pareto diagram
D. Affinity diagram
https://t.me/PrMaB
B. Release plan
C. Product backlog
D. Scope statement
C. Context diagram
D. Wireframes
B. PERT
C. RBS
D. WBS
https://t.me/PrMaB
D. The product backlog was not established.
B. Persona analysis
C. Job analysis
D. RAM analysis
https://t.me/PrMaB
A. Develop entity relationship diagrams
B. Box plots
C. Affinity diagram
https://t.me/PrMaB
project. How would you review this change and identify
the impact on already developed product components?
A. Call a team meeting and discuss lessons learned.
B. Facilitate workshops
C. Focus groups
D. Questionnaires
https://t.me/PrMaB
19. You are leading a complex organizational
transformation project. You have a wide range of
stakeholders from active supporters to non-supportive and
resistant stakeholders. You are now analyzing these
stakeholders based on their influence and impact. What
will be your strategy to manage the stakeholders classified
as “low influence” but “high impact” stakeholders?
A. Pay attention to this group and address their
concerns; stakeholders in this group may represent
those expected to adapt to the implemented solution
once it is built.
https://t.me/PrMaB
B. ROI
C. IRR
D. NPV
B. Elicited requirements
C. Verified requirements
D. Validated requirements
https://t.me/PrMaB
A. By assessing the project budget and schedule
performance.
https://t.me/PrMaB
A. Agile
B. Inconsequential
C. Progressively elaborated
D. Iterative
https://t.me/PrMaB
about their expectations.
C. Stakeholder maps
D. Product backlog
https://t.me/PrMaB
A. They are sufficient for understanding all root
causes.
B. Facilitated workshops
C. Observation
D. Surveys
https://t.me/PrMaB
C. Add this to the risk log
C. Waterfall approach
D. Adaptive planning
https://t.me/PrMaB
C. Ask the team to remove the item from the backlog.
C. Monitor Communications
D. Manage Communications
https://t.me/PrMaB
A. Reserve burn down charts
https://t.me/PrMaB
business analysis techniques will help you relate the
identified problems within the current state to their
associated root causes and the capability required to
address the problem in the future state?
A. Capability table
B. Process analysis
D. SWOT analysis
https://t.me/PrMaB
B. Traceability matrix
D. RACI matrix
C. Statement of work
B. Fishbone diagram
C. Kanban board
D. Spikes
https://t.me/PrMaB
B. Conduct requirements elicitation
B. User stories
C. Epics
D. Product roadmap
https://t.me/PrMaB
49. You are analyzing requirements for a new software
application. All product deliverables have been identified
and now you need to determine the conditions that are
required to be met before each deliverable could be
accepted. These conditions are known as:
A. Product feasibility
B. Product requirements
C. Acceptance criteria
B. Process flow
D. State diagram
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) - 17
Answer Key and Explanations
1. A - The configuration management system includes
the process for submitting proposed changes, reviewing
and approving proposed changes, defining approval levels
for authorizing changes, and providing a method to
validate approved changes. In most application areas, the
Configuration Management System includes the change
control system. [PMBOK® Guide 6th Edition, Page 115]
[Traceability & Monitoring]
2. A - Although you might want to store the models in
the lessons learned library or as organizational process
assets, this is not a prime objective of developing them.
The rest of the choices are all primary reasons for
developing models.
[The PMI Guide to Business Analysis, page 184]
[Analysis]
3. D - System interface tables are usually created after
the ecosystem map and context diagram have been created
to identify the interfaces.
[The PMI Guide to Business Analysis, page 205]
[Analysis]
4. C - Since you have completed the elicitation
workshops, this means that you have completed the
Conduct Elicitation process. Now you are planning to
confirm the obtained results form the stakeholders, this
will be the Confirm Elicitation Results process.
[The PMI Guide to Business Analysis, page 170]
[Analysis]
5. D - Affinity diagram is a technique that allows large
numbers of ideas to be classified into groups for review
and analysis. The rest of the choices are not grouping
techniques.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 387]
[Analysis]
6. A - On adaptive projects, the product owner has the
authority to approve requirements. Typically, on these
projects, the product owner’s prioritization of the backlog
is generally interpreted as approval.
[The PMI Guide to Business Analysis, page 268]
[Traceability & Monitoring]
7. C - The backlog is the ordered list of all the work,
presented in story form, for a team. At any given point in
time, the current product backlog defines the current
project scope.
[The PMI Guide to Business Analysis, pages 133]
[Planning]
8. A - High fidelity prototypes allow the users to interact
with the prototype. None of the rest of the models have
this ability.
[The PMI Guide to Business Analysis, page 199]
[Analysis]
9. D - This is an example of a Work Breakdown
Structure. A work breakdown structure is a deliverable-
oriented breakdown of a project scope into smaller
components. [PMBOK® Guide, 6th edition, Page 158]
[Planning]
10. B - Story mapping is used to sequence user stories,
based upon their value and the order their user typically
performs them. Improper story mapping usually results in
customer complaints similar to the one given in the
scenario.
[The PMI Guide to Business Analysis, page 134]
[Planning]
11. C - The output of job analysis may include details
such as a high-level description of the work; a depiction
of the work environment; a detailed list of the activities a
person is expected to perform; a list of the preferred
https://t.me/PrMaB
interpersonal skills; or a list of required training, degrees,
and certifications.
[The PMI Guide to Business Analysis, page 117]
[Planning]
12. B - Solution Evaluation includes the processes to
validate a full solution or a segment of a solution that is
about to be or has already been implemented. Conducting
evaluation activities early during project initiation doesn’t
make sense. All other choices give valid points in time to
conduct solution evaluation activities.
[The PMI Guide to Business Analysis, page 279]
[Evaluation]
13. C - A use case is a process model that uses textual
narrative to describe the system-user interactions to
achieve successful completion of a goal. This is what the
developers had asked for and this is what needs to be
developed.
[The PMI Guide to Business Analysis, page 214]
[Analysis]
14. C - A burndown chart shows a team’s progress by
showing the number of story points remaining in the
project. The vertical axis shows the number of story
points remaining and the iterations are shown across the
horizontal axis. A steadily declining burndown chart
indicates that the velocity is constant; the same number of
story points are being delivered in each project iteration.
[The PMI Guide to Business Analysis, page 131, 148]
[Traceability & Monitoring]
15. C - Affinity diagrams are used to process a large set of
information or ideas into a manageable set of data
organized by categories. The rest of the choices aren’t fit
for this purpose.
[The PMI Guide to Business Analysis, page 77] [Needs
Assessment]
16. C - In this case, some of the business objectives have
been changed and you want to trace the impact to the
https://t.me/PrMaB
developed product components. The requirements
traceability matrix will help you identify the components
that are linked to these business objectives.
[The PMI Guide to Business Analysis, page 258]
[Traceability & Monitoring]
17. A - Documents may have enough information to use
as a starting point, thereby saving significant stakeholder
time during in-person elicitation activities.
[The PMI Guide to Business Analysis, page 167]
[Analysis]
18. B - The Multi-criteria decision analysis uses a
decision matrix to provide a systematic analytical
approach to evaluate the requested change according to a
set of predefined criteria. The other choices are either
quality or risk management tools. [PMBOK® Guide 6th
edition, Page 119] [Planning]
19. A - Stakeholders who are expected to adapt to the
implemented solution once it is built are from the “low
influence/high impact” group. Stakeholders that are just
being monitored to ensure their behavior does not change
over time are from the “low influence/low impact” group.
Stakeholders who are decision-makers have “high
influence”, and the stakeholders who are a critical source
for requirements are “high impact”.
[The PMI Guide to Business Analysis, page 119-120]
[Planning]
20. B - The Internal Rate of Return (IRR) gives the
projected annual yield of an investment (rate of return)
considering the time value of money. On the other hand,
the Return on Investment (ROI) is the percentage return
on an initial investment disregarding the time value of
money.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
21. C - A burndown chart shows a team’s progress by
showing the number of story points remaining in the
https://t.me/PrMaB
project. The vertical axis shows the number of story
points remaining and the iterations are shown across the
horizontal axis. A steadily declining burndown chart
indicates that the velocity is constant; the same number of
story points are being delivered in each project iteration.
A horizontal line will indicate no story points were
delivered during the sprint which means the velocity was
zero.
[The PMI Guide to Business Analysis, page 131, 148]
[Traceability & Monitoring]
22. A - Requirements that are approved establish the
requirements baseline. Requirements approval should be
sought once the requirements have been verified and
validated.
[The PMI Guide to Business Analysis, page 264]
[Traceability & Monitoring]
23. D - You might assess the competitive advantage the
product has provided to the organization if the intent of
product development was to provide competitive
advantage. Since this information is not provided, the best
answer to this question needs to be more generic. The
correct response is assessing the solution’s ability to
deliver its intended benefits to the organization, which
could be gaining competitive advantage, cost benefits or
processing efficiency, etc. Also note that the question is
asking for an approach to measure the product’s success
and not the project’s success.
[The PMI Guide to Business Analysis, page 17] [Needs
Assessment]
24. D - Since these are transition requirements these
should be documented as transition user stories and not
change requests. Furthermore, these should be added to
the product backlog from where they will be prioritized
and allocated to a sprint backlog.
[The PMI Guide to Business Analysis, page 140]
[Traceability & Monitoring]
https://t.me/PrMaB
25. D - The Identify Risks process is an ongoing, iterative
process as risks are often identified throughout the
project’s life cycle. [PMBOK® Guide 6th edition, Page
409] [Planning]
26. B - Business architecture is a subset of the enterprise
architecture and CONTAINS components such as the
business functions, organizational structures, locations,
and processes of an organization, including documents
and depictions of those elements.
[The PMI Guide to Business Analysis, page 65] [Needs
Assessment]
27. C - Focus groups and facilitated workshops are two
different elicitation techniques. A focus group brings
together prequalified stakeholders and subject matter
experts to learn about their expectations. On the other
hand, participants for a workshop do not need to be
prequalified or SMEs. Workshops are used to generate
ideas, while the focus groups are used to refine these ideas
and lead the development efforts.
[The PMI Guide to Business Analysis, page 167]
[Analysis]
28. C - The process of developing a business analysis
work plan is: Identify the deliverables -> Determine the
business analysis tasks and activities -> Determine the
timing and sequencing of tasks ->Determine the roles and
responsibilities -> Identifying the resources -> Estimate
the work
[Business Analysis for Practitioners: A Practice Guide,
page 61-65; The PMI Guide to Business Analysis, page
111] [Planning]
29. D - The product backlog is the list of all product
backlog items, typically user stories, requirements, or
features, that need to be delivered for a solution. On Agile
projects, the product backlog makes up the overall project
scope.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 133]
[Planning]
30. D - An interrelationship diagram is a special type of
cause-and-effect diagram that depicts related causes and
effects for a given situation. Interrelationship diagrams
help to uncover the most significant causes and effects
involved in a situation. They are helpful for visualizing
complex problems that have seeming unwieldy
relationships among multiple variables.
[The PMI Guide to Business Analysis, page 71] [Analysis]
31. B - Workshops are considered a primary technique for
quickly defining product information across multiple
domains and reconciling stakeholder differences. Because
of their interactive group nature, well-facilitated sessions
can build trust, foster relationships, and improve
communication among the participants, which can lead to
increased stakeholder consensus.
[The PMI Guide to Business Analysis, page 167]
[Analysis]
32. D - Notify your project stakeholders immediately.
They can determine the best path forward. An incorrect
business case could have a serious impact on the usability
of the final output of your project, or it could even impact
the company’s strategic goals. Failure to point out this
error to the appropriate management is a violation of the
PMI Code of Ethics. [PMI Code of Ethics and
Professional Conduct] [Traceability & Monitoring]
33. D - Adaptive planning defines a plan but
acknowledges that once work starts, the priorities may
change and the plan might need to be updated.
[PMBOK® Guide 6th edition, Page 177] [Analysis]
34. B - NPV alone is not the ideal financial benefit
measurement method. NPV results are highly dependent
on the magnitude of the project. Usually NPV
measurements are presented along with the project IRR or
the initial investment estimates to demonstrate the
financial feasibility of a project.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 90]
[Planning]
35. B - Since the product owner is ultimately responsible
for the product, you need to work with them to have the
item removed from the backlog.
[The PMI Guide to Business Analysis, page 216]
[Planning]
36. A - Manage Stakeholder Engagement is the process of
communicating and working with stakeholders to meet
their needs and expectations, address issues as they occur,
and foster appropriate stakeholder involvement.
[PMBOK® Guide 6th edition, Page 523] [Analysis]
37. A - Stakeholders whose business processes are
impacted by the project can be supportive or non-
supportive. If they see the project delivering value to them
or if they are direct beneficiaries of the outcome, they will
be supportive of the project. On the other hand, if they are
not the direct beneficiary of the project benefits and if
their workload is expected to be increased as a result of
the project’s outcome, they will be non-supportive.
[Business Analysis for Practitioners: A Practice Guide,
page 41; The PMI Guide to Business Analysis, page 115-
116] [Planning]
38. B - Stakeholder engagement strategy is a component
of the stakeholder engagement plan and is usually
considered confidential. Due to this reason, this section is
least likely to be included in a work performance report.
Other choices are more likely to be components of a work
performance report. [PMBOK® Guide 6th edition, Page
112] [Analysis]
39. A - The business analysis deliverables are produced
for the project and the product team. The product team
consumes the deliverables produced by the business
analyst for product development; hence they are the
primary customers. The key stakeholders and the product
users are the customer of the product development team.
https://t.me/PrMaB
[Business Analysis for Practitioners: A Practice Guide,
page 62; The PMI Guide to Business Analysis, page 111]
[Planning]
40. A - Acceptance criteria are documented in the project
scope statement, developed during the Define Scope
process. Poorly defined acceptance criteria would then
propagate to the Plan Quality Management process used
for planning quality. [PMBOK® Guide 6th edition, Page
154] [Planning]
41. A - Capability tables relate the identified problems
within the current state to their associated root causes and
the capability required to address the problem in the
future state. The rest of the analysis techniques do not
have this focus.
[The PMI Guide to Business Analysis, page 78] [Needs
Assessment]
42. B - The causes and the sub-causes are placed on the
bones of the fish. The head of the fish lists the problem
(effect) of the situation and not the root cause of the
situation.
[The PMI Guide to Business Analysis, pages 70] [Needs
Assessment]
43. A - A Product portfolio matrix, also known as a
growth-share matrix, is a market analysis quadrant
diagram used by organizations to qualitatively analyze
their products and product lines.
[The PMI Guide to Business Analysis, page 283]
[Evaluation]
44. D - Business goals and objectives specify stated
targets that the busines is seeking to achieve. They
provide the context for evaluating solution performance
because they are a measurable description of the expected
business value.
[The PMI Guide to Business Analysis, page 281]
[Evaluation]
https://t.me/PrMaB
45. C - A Kanban board provides a means to visualize the
flow of work, make impediments easily visible, and allow
flow to be managed by adjusting the work in process
limits.
[The PMI Guide to Business Analysis, page 233]
[Analysis]
46. A - Conduct Stakeholder Analysis is the logical next
step after the Identify Stakeholders process which first
generates the project stakeholder register. The rest of the
choices are the activities that must be started once the
stakeholder analysis is complete.
[The PMI Guide to Business Analysis, page 111]
[Planning]
47. D - In business analysis, product roadmaps provide
important information about a product, providing insights
about the product vision and how the product will support
organizational strategy, business goals and objectives over
time. The other choices are part of the product scope, but
they do not show the delivery of the features over time.
[The PMI Guide to Business Analysis, page 93] [Needs
Assessment]
48. D - The control limits are determined using statistical
calculations. [PMBOK® Guide 6th edition, Page 304]
[Traceability & Monitoring]
49. C - Acceptance criteria are a set of conditions that are
required to be met before deliverables are accepted. In
business analysis, acceptance criteria are built to evaluate
the product requirements and solution.
[The PMI Guide to Business Analysis, page 387]
[Planning]
50. B - A process flow is a process model and not a data
model. The rest of the choices are all data models.
[The PMI Guide to Business Analysis, page 185]
[Analysis]
https://t.me/PrMaB
PMI-PBA MOCK EXAM
(LITE) - 18
Practice Questions
Test Name: PMI-PBA Lite Mock Exam 10
Total Questions: 50
Correct Answers Needed to Pass:
35 (70.00%)
Time Allowed: 60 Minutes
Test Description
This is a cumulative PMI-PBA Mock Exam which can be used
as a benchmark for your PMI-PBA aptitude. This practice test
includes questions from all Business Analysis Domain areas.
Test Questions
1. You are leading the business analysis efforts for an
organizational transformation program. You are currently
creating questions that will be asked from stakeholders
during an upcoming elicitation activity. Which business
analysis process are you performing?
A. Identify Problem or Opportunity
https://t.me/PrMaB
Which of the following is an incorrect classification of a
feasibility study?
A. A feasibility study may be considered a program.
B. Decomposition
C. Delphi
D. Bottom-up estimating
C. Questionnaires
D. Planning poker
https://t.me/PrMaB
during the planning activities. Which of the following
project planning information is typically considered
sensitive on most projects?
A. Project schedule
B. Burndown charts
D. Task assignments
B. Display-Action-Response Model
C. Document Analysis
D. Ecosystem Map
https://t.me/PrMaB
8. You have been assigned to conduct a post-
implementation solution evaluation of a recently released
IT system. For this exercise you need performance data
before and after the release to do your comparisons.
Unfortunately, nobody gathered the required performance
data prior to the release. What should you do?
A. Review the performance data generated by similar
IT systems in the market.
B. RACI matrix
C. Fishbone diagram
D. Process model
B. Work packages
https://t.me/PrMaB
C. User stories
D. WBS elements
B. Basic
C. Performance
D. Delighters
https://t.me/PrMaB
13. The director of human resources in your organization
has expressed her interest in implementing a new
employee attendance system. The new attendance system
should utilize facial recognition technologies to detect and
record the employee sign-in and sign-off times. This
would replace the current card tap-in and tap-off system
the organization has been using for some time. You are
also aware that the new organizational strategy
encourages, “working from home” and is targeting to have
at least 50% of the employees working from home at any
given point in time. In your opinion, what is the problem
with the HR director’s project idea?
A. Facial recognition technologies are not matured
enough to be deployed.
14. You are working for a consulting firm that has been
engaged by a fast-moving consumer goods company to
assess its manufacturing processes. Several defects have
been reported in the manufacturing process and you have
conducted a thorough root cause analysis of the situation.
You develop a Pareto diagram to communicate the results
of your root cause analysis. What will this diagram
highlight?
A. The cost of resolving the reported problems.
https://t.me/PrMaB
D. The most significant issues among the reported
issues.
B. Option B
C. Option A
https://t.me/PrMaB
A. Recommendation a realignment of the strategy
B. Poor Planning
D. Time-delayed Decomposition
C. Need to be discontinued.
https://t.me/PrMaB
a number of hidden process requirements during the
Collect Requirements process?
A. Observation
C. Questionnaires
D. Surveys
https://t.me/PrMaB
D. A feature that provided competitive advantage to
your firm in comparison to the competitors.
C. Co-location
https://t.me/PrMaB
being used by the product users to compensate for the
gaps in the product performance?
A. Observation
B. Feature model
C. Kano analysis
D. SWOT analysis
D. State Diagram
https://t.me/PrMaB
relationship because they can make or break an
initiative; this group of decision-makers are a
critical source for requirements.
29. State table and state diagrams are useful for solutions
involving workflows and can help with the discovery of
business rules that relate to an object moving from one
state to another. In which situation would you prefer
developing a state table instead of a state diagram?
https://t.me/PrMaB
A. When you want to document the results of a
workflow analysis.
B. Scope creep
C. Project scope
D. Scope verification
B. Focus groups
C. Interviews
D. Questionnaires
https://t.me/PrMaB
following tools can help in this situation?
A. Kanban Board
B. Planning poker
C. Burndown chart
D. Information radiator
https://t.me/PrMaB
35. You have recently joined a product team developing
an internal information management system for the
organization. The project is currently in the planning
phase and you are responsible for eliciting the product
requirements and creating the work breakdown structure
for the product team. A business analysis plan for the
product does not exist. You believe that insufficient funds
have been allocated for the requirements phase. Ideally,
more funds should have been allocated for conducting
requirements elicitation workshops. How should you
resolve this issue?
A. Work within your allocated budget and elicit as
many requirements as you can.
B. 16542
C. 0
D. 116542
https://t.me/PrMaB
diagram, and a data dictionary need to be developed.
Which of these you should develop first?
A. Entity relationship diagram
C. Data dictionary
B. Delta technique
D. Facilitation
https://t.me/PrMaB
D. An adaptive approach may need to be adopted.
B. Autocracy
C. Bureaucracy
D. Unanimity
https://t.me/PrMaB
in cost savings to the project and completion of the project
one month ahead of schedule. Which of the following
actions would you take?
A. Communicate the current status and inform the
customer you will incorporate some additional
features to use up the savings in cost and time since
it was budgeted.
https://t.me/PrMaB
D. The project cost might exceed the project budget.
https://t.me/PrMaB
D. A detailed requirement may contain many user
stories which need to be linked prior to the first
iteration.
B. Context diagram
C. Dataflow diagram
D. Process flow
B. Student syndrome
C. 100% rule
D. DuPont Equation
https://t.me/PrMaB
the risk associated with having this senior manager not
supporting your project?
A. The product requirements cannot be elicited.
B. Leadership skills
C. Reward power
D. Persuasive power
https://t.me/PrMaB
PMI-PBA Mock Exam (LITE) - 18
Answer Key and Explanations
1. B - During the Prepare for Elicitation process, you
identify the questions for the elicitation activity.
[The PMI Guide to Business Analysis, page 161]
[Analysis]
2. A - Organizations may classify projects differently
depending on their internal policies and structures. A
feasibility study can be considered pre-project work, the
first phase of a project, or a stand-alone project. However,
it cannot be considered a program. A program will have
much larger scope. [PMBOK® Guide 6th edition, Page
11] [Needs Assessment]
3. B - Decomposition is used to breakdown information
described at a high level into a hierarchy of smaller, more
discrete parts. The rest of the choices are estimation
techniques and do not help in decomposition.
[The PMI Guide to Business Analysis, page 132]
[Analysis]
4. A - A prototype is a draft version of a product that
allows you to explore your ideas and show the intention
behind a feature or the overall design concept to users
before investing time and money into development.
Prototyping is an efficient and effective way to understand
and validate system requirements at the early stage of
software development.
[The PMI Guide to Business Analysis, page 61]
[Planning]
5. C - Much of the information produced as a result of
stakeholder analysis is typically considered sensitive in
nature. The business analyst should be careful when
distributing the results of this analysis to a broad
distribution group.
https://t.me/PrMaB
[Business Analysis for Practitioners: A Practice Guide,
page 45; The PMI Guide to Business Analysis, page 115-
116] [Planning]
6. B - Although document analysis is a good
requirements elicitation tool and you can use that to
review existing paper-based forms and reports to collect
system requirements, the question is asking us to identify a
technique that would help us elicit detailed system
requirements from the process workers. Process models
and ecosystem maps are drawn at a high level and would
not help the process workers identify detailed system
requirements such as UI layout, business rules and
validation criteria, etc. Display-Action-Response model is
a business analysis model that dissects a user interface
mockup into its display and behavior requirements at the
page element level.
[The PMI Guide to Business Analysis, page 395]
[Analysis]
7. D - A transition plan is based on the readiness
assessment as well as the transition strategy. It covers
development of all the communication, rollout, training
and user documentation procedure updates, business
recovery updates, and other collateral and final production
tasks needed to successfully cut over and adapt to the
future state.
[The PMI Guide to Business Analysis, page 297]
[Evaluation]
8. D - If there is no baseline of performance data, then
either the performance data after a release can represent
the business value or estimates of the original baseline can
be made.
[The PMI Guide to Business Analysis, page 282]
[Evaluation]
9. A - The RACI matrix and the fishbone diagram are
tools for responsibility assignment and root cause analysis
respectively, hence these options are irrelevant. Process
models can be used to determine the degree of fit between
https://t.me/PrMaB
a vendor’s product and business requirements of the
organization, but these cannot be used to present different
future state feature options. The feature model provides a
visual representation of all the features of a solution
arranged in a tree or hierarchical structure.
[The PMI Guide to Business Analysis, page 79] [Needs
Assessment]
10. C - In an agile approach, epics are decomposed into
smaller components called user stories. [PMBOK® Guide
6th edition, Page 160] [Analysis]
11. D - Delighters are the features that differentiate the
product from competitor’s products and are sometimes
referred to as the “wow” factor.
[The PMI Guide to Business Analysis, pages 80, 81]
[Needs Assessment]
12. D - During the selection of a project, the project’s
goals and objectives must be aligned with the business’
goals and objectives. This is independent to the project
life cycle or having a PMO overseeing the project.
[The PMI Guide to Business Analysis, page 57] [Needs
Assessment]
13. B - You need to spot the problem based on the given
information. We know that the organization plans to
encourage employees to work from home and have less
workforce at work. The HR director’s project idea is
clearly not aligned with the organizational strategy. As
part of business analysis, we ensure that all initiatives are
aligned with the organizational strategy and objectives.
[The PMI Guide to Business Analysis, page 57] [Needs
Assessment]
14. D - A Pareto diagram is a histogram that can be used
to communicate the results of root cause analysis. Pareto
diagrams are a special form of vertical bar chart used to
emphasize the most significant factor among a set of data.
[The PMI Guide to Business Analysis, pages 69]
[Analysis]
https://t.me/PrMaB
15. B - Option B needs to be selected as it has a higher
IRR value. IRR is a measure of return to cost; therefore,
the higher the IRR, the higher the return a solution option
is expected to deliver.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
16. C - Although observation could be time-intensive, the
major drawback of this technique is that people act
differently when they are being observed. The other two
choices are not accurate.
[The PMI Guide to Business Analysis, page 168]
[Analysis]
17. C - Honoring the CEO’s desires and executing the
project is against the PMI’s Code of Ethics since the
project manager knows that some of the projects are not
fully aligned with the strategy. Terminating the project is
an extreme and should not be the first consideration. The
project manager must make a recommendation to realign
the project objectives with the organizational strategy
since value to the business can only be delivered when
projects remain aligned with the strategic direction of the
organization. [PMBOK® Guide 6th edition, Page 14]
[Needs Assessment]
18. C - The correct answer is rolling wave planning.
Rolling wave planning is a form of progressive
elaboration and is used when the project management
team does not have enough information for a phase or
deliverable that will occur far into the future. [PMBOK®
Guide 6th edition, Page 160] [Planning]
19. B - A Product portfolio matrix, also known as a
growth-share matrix, is a market analysis quadrant
diagram used by organizations to qualitatively analyze
their products and product lines. One axis reflects market
growth while the other reflects the market share of the
organization. The matrix provides a quick visual way to
evaluate which products are meeting or exceeding
performance expectations in the marketplace. The
https://t.me/PrMaB
products that provide the most significant benefits to the
organization would be found in the upper left quadrant,
because these are the products where the organization has
a high market share in a market with a high growth rate.
Those in the upper right quadrant are regarded as having
good potential because, although they have a low market
share, they are in a market that is continuing to grow.
Those in the lower left quadrant, with a high market share
in a low growth market, are considered a dependable
income stream.
[The PMI Guide to Business Analysis, page 284]
[Evaluation]
20. A - A hidden requirement is the one that the user or
the customer fails to communicate or takes for granted.
Hidden requirements can be identified by a “participant
observer” who actually performs a process or procedure to
experience how it is done. [PMBOK® Guide 6th edition,
Page 145] [Analysis]
21. C - The three sections of a typical story map are
backbone, walking skeleton, and related user stories.
[The PMI Guide to Business Analysis, page 205]
[Analysis]
22. C - The data security standards and the processing
speed are performance features; these are the features that
either satisfy or dissatisfy the customers depending upon
how well they perform. A feature that provides
competitive advantage to your firm in comparison to the
competitors is a delighter. A bad user interface is always
unwanted by the customer; this is an example of a reverse
feature.
[The PMI Guide to Business Analysis, page 80] [Needs
Assessment]
23. D - Rolling Wave planning is not a tool and technique
of the Develop Team process, while the other choices are.
[PMBOK® Guide 6th Edition, Page 336] [Analysis]
https://t.me/PrMaB
24. B - Business goals and objectives specify stated
targets that the busines is seeking to achieve. They
provide the context for evaluating solution performance
because they are a measurable description of the expected
business value. In this case, all three measurements must
be used to evaluate the post-implementation performance
of the solution.
[The PMI Guide to Business Analysis, page 281]
[Evaluation]
25. A - From the given choices, only observation is an
elicitation technique. You can use this technique to
identify the workarounds being used by the product users
to compensate for the gaps in the product performance.
[The PMI Guide to Business Analysis, page 283]
[Evaluation]
26. D - The state table and state diagram are data models
that show the valid stats of an object and any allowed
transitions between those states. State tables model all
states as both a column and a row in a table that allows a
business analyst to systematically consider each potential
state transition (from row to column) to determine if the
transition should be allowed or is not capable of being
transitioned to/from other states. State diagrams, on the
other hand, visually depict the states and transitions, but
only show valid transitions for the object.
[The PMI Guide to Business Analysis, page 203]
[Analysis]
27. C - Stakeholders who are expected to adapt to the
implemented solution once it is built are from the “low
influence/high impact” group. Stakeholders that are just
being monitored to ensure their behavior does not change
over time are from the “low influence/low impact” group.
Stakeholders who are decision-makers have “high
influence”, and the stakeholders who are a critical source
for requirements are “high impact”.
[The PMI Guide to Business Analysis, page 119-120]
[Planning]
https://t.me/PrMaB
28. A - The completion of project scope is measured
against the project management plan, whereas the
completion of product scope is measured against the
product requirements. The work of the project results in
delivery of the specified product scope. [PMBOK® Guide
6th edition, Page 131] [Planning]
29. D - State tables are mostly used for analysis to ensure
that all transition combinations have been considered.
State diagrams are used for the ease of stakeholders to
visualize the valid transition flow. Note that stakeholders
can validate the transition flow using both models given
that they understand the models. The last two choices are
applicable to both models.
[The PMI Guide to Business Analysis, page 203]
[Analysis]
30. C - Project scope describes the work that must be
performed to deliver a product, service, or result to the
stakeholders. Product scope describes the features and
functions that characterize a product, service, or result.
[PMBOK® Guide 6th edition, Page 131] [Planning]
31. D - Questionnaires and surveys are written sets of
questions designed to quickly accumulate information
from a large number of respondents. Given the number of
customers, the rest of the options are not ideal in the given
scenario.
[The PMI Guide to Business Analysis, page 68] [Needs
Assessment]
32. A - A Kanban board is a WIP management tool. It
helps the team boost performance by limiting the Work in
Process (WIP).
[The PMI Guide to Business Analysis, page 233]
[Planning]
33. A - Depending on organizational norms, obtaining a
release decision may include obtaining signoff. For a
predictive project life cycle, signoff usually occurs at the
end of the project life cycle.
https://t.me/PrMaB
[The PMI Guide to Business Analysis, page 296]
[Evaluation]
34. D - As the business analyst, it is your responsibility to
elicit the detailed product requirements. Elicitation is
highly cyclical. It is repeated multiple times for each level
of abstraction and product information. All elicitation
processes that were performed to define business
requirements need to be repeated once again to define
more detailed product requirements.
[The PMI Guide to Business Analysis, page 155]
[Analysis]
35. D - Since the business analysis plan does not exist,
you need to develop one. If the funding for business
analysis activities is not adequate, you can only justify
additional funding with your business analysis plan.
[Business Analysis for Practitioners: A Practice Guide,
page 68; The PMI Guide to Business Analysis, page 127]
[Planning]
36. B - Net present value (NPV) is the difference between
the present value of cash inflows and the present value of
cash outflows. NPV = $116,542 - $100,000 = $16,542.
[The PMI Guide to Business Analysis, page 90] [Needs
Assessment]
37. A - Entity relationship diagrams, process flows, and
ecosystem maps are usually created first to identify the
data objects, processes, and systems to show in a data
flow diagram. A data dictionary lists data fields and
additional details for data objects in an entity relationship
diagram. The best way to proceed is to start the
development of the entity relationship diagram.
[The PMI Guide to Business Analysis, pages 187, 188]
[Analysis]
38. D - Well-facilitated sessions can build trust, foster
relationships, and improve communications among the
participant, which can lead to increased stakeholder
https://t.me/PrMaB
consensus. [PMBOK® Guide 6th Edition, Page 145]
[Analysis]
39. A - In large organizations, there may be a mixture of
small projects and large initiatives requiring long-term
commitments to manage these programs using scaling
factors (e.g. team size, geographical distribution,
regulatory compliance, organizational complexity, and
technical complexity). To address the full delivery life
cycle, a range of techniques utilizing a predictive
approach, adaptive approach, or a hybrid of both, may
need to be adopted. [PMBOK® Guide 6th edition, Page
178] [Traceability & Monitoring]
40. B - This is autocracy; one individual makes the
decision for the whole group.
[The PMI Guide to Business Analysis, page 267]
[Analysis]
41. D - The problem with the initiative is that it is not
aligned with the organizational strategy. The rest of the
options are not correct: A positive IRR means the project
is expected to return some value to the business; a project
with the highest IRR doesn’t necessarily mean maximum
risk; no data is given to determine the project’s payback
period.
[The PMI Guide to Business Analysis, page 57] [Needs
Assessment]
42. C - A project manager should always communicate an
accurate statement of the project status. There could be
subsequent actions to determine how the savings could be
best put to use, whether there could be any cost sharing,
etc.—but these would need to be done following the
appropriate procedure. [PMI Code of Ethics and
Professional Responsibility] [Traceability & Monitoring]
43. B - Obtaining approval on the plan helps to reduce the
risk of stakeholders not supporting the business analysis
process once it starts and underestimating the level of
participation necessary for the requirement activities.
https://t.me/PrMaB
[Business Analysis for Practitioners: A Practice Guide,
page 68; The PMI Guide to Business Analysis, page 127]
[Planning]
44. B - The business analysis work plan and the project
management plan are developed by the business analyst
and the project manager, respectively. The business
analysis work plan is a subcomponent of the business
analysis plan. The business analysis work plan is
ultimately integrated with the project management plan.
[Business Analysis for Practitioners: A Practice Guide,
page 61; The PMI Guide to Business Analysis, page 146]
[Planning]
45. C - In adaptive approaches, user stories are commonly
the method to represent requirements. A user story may
contain many detailed requirements which need to be
elaborated near their development.
[The PMI Guide to Business Analysis, page 215]
[Analysis]
46. B - Context diagram is a scope model. The rest of the
choices are not examples of scope models.
[The PMI Guide to Business Analysis, page 185]
[Analysis]
47. A - A Pareto diagram is a histogram that can be used
to communicate the results of root cause analysis. Pareto
diagrams are a special form of vertical bar chart used to
emphasize the most significant factor among a set of data.
The format of a Pareto diagram helps demonstrate the
80/20 principle whereby 80% of problems can be related
back to 20% of the causes.
[The PMI Guide to Business Analysis, pages 69] [Needs
Assessment]
48. C - Although the senior manager is not a direct
stakeholder for your project, the manager can use his
influence, tied to his position, to hinder the project
success. Since the senior manager is not a direct
stakeholder, events given in other choices are irrelevant.
https://t.me/PrMaB
[Business Analysis for Practitioners: A Practice Guide,
page 43; The PMI Guide to Business Analysis, page 115-
116] [Planning]
49. A - The fear originates from the disciplinary actions
taken in the recent past. This is an example of coercive
power. [PMBOK® Guide, 6th edition, Page 63] [Needs
Assessment]
50. B - When using document analysis for requirements
elicitation, it is important to recognize the accuracy and
relevancy of the information being used. If the
information is not accurate or relevant, the whole exercise
will be useless.
[The PMI Guide to Business Analysis, page 167]
[Analysis]
https://t.me/PrMaB
PMI-PBA EXAM CHEAT
SHEET –
Tools & Techniques
https://t.me/PrMaB
PMI-PBA® Tools and Techniques grouped by
Knowledge Areas
https://t.me/PrMaB
Analysis;
Elicitation
Techniques;
Feature Injection;
Group Decision-
making Techniques;
Real Options;
Valuation
Techniques;
Weighted Ranking
https://t.me/PrMaB
Lessons Learned;
Stakeholder Maps
https://t.me/PrMaB
Workshops; Focus
Groups; Interviews;
Observation;
Prototyping;
Questionnaires and
Surveys
https://t.me/PrMaB
Catalog; Definition
of Ready; Glossary;
Product Backlog;
Requirements
Management Tool;
Story Elaboration;
Story Slicing; Use
Case; User Story
https://t.me/PrMaB
Opportunity
Analysis; SWOT
Analysis
https://t.me/PrMaB
Management Tool;
Traceability Matrix
https://t.me/PrMaB
Process Assess Current State Business Architecture Techniques; Business
Group Capability Analysis; Capability Framework;
Capability Table; Elicitation Techniques;
Glossary; Pareto Diagrams; Process Flows;
Root Cause and Opportunity Analysis;
SWOT Analysis
https://t.me/PrMaB
Analysis Planning Estimation Techniques; Planning Techniques
https://t.me/PrMaB
Elaboration; Story Slicing; Use Case; User
Story
https://t.me/PrMaB
Controlling Communication
Process
Group Assess Business Burndown Charts; Elicitation Techniques;
Analysis Performance Process Flows; Retrospectives and Lessons
Learned; Root Cause and Opportunity
Analysis; Variance Analysis
https://t.me/PrMaB
PMI-PBA® Most Common Tools and Techniques
Elicitation Techniques 10
Document Analysis 7
Interviews 7
Process Flows 7
Facilitated Workshops 6
Prioritization Schemes 6
Story Mapping 6
Brainstorming 5
Glossary 5
Traceability Matrix 5
Feature Model 4
Backlog Management 3
Benchmarking 3
Product Backlog 3
SWOT Analysis 3
https://t.me/PrMaB
Business Analysis Tools and Techniques – A Quick Review
https://t.me/PrMaB
level solution where existing documentation on
the organizational structure and processes is
limited.
https://t.me/PrMaB
Data Flow Diagram A business analysis model that shows the flow of
data through a business workflow or the solution
being designed.
https://t.me/PrMaB
a trained facilitator. This technique is often used in
collaboration with other elicitation techniques
such as brainstorming, Affinity diagram,
prioritization schemes and collaborative games.
Goal Model and Business A business analysis model that shows the high-
Objectives Model level goals and objectives of an organization. This
is usually developed early during a project
lifecycle.
https://t.me/PrMaB
valuable, estimable, small, and testable.
https://t.me/PrMaB
expected to deliver significant change to an
organization or when stakeholders are sensitive to
using actual roles to analyze negative forces.
https://t.me/PrMaB
layout, data and fields of each report that needs to
be produced by a solution.
State Table and State Diagram A business analysis mode that shows different
states of data objects and the allowed transitions
between these states.
https://t.me/PrMaB
strengths and weaknesses considering the
opportunities and the threats that surround the
organization.
https://t.me/PrMaB
Additional Resources
https://t.me/PrMaB
EXAM TAKING TIPS
PMI-PBA® Exam Facts
https://t.me/PrMaB
apart from you, nobody is allowed to enter the room
while the test is in progress, otherwise the test will be
immediately ended by the proctor. The exam is divided
into two parts with a 10-minute break in between.
Make sure you seek the proctor’s permission prior to
taking the break.
Be prepared to fully utilize your blank “scratch” paper
in the exam. This means that you have committed
important concepts and key facts to memory; and you
are able to apply them to a blank sheet of paper in less
than five minutes.
Alleviate exam stress and anxiety by taking practice
exams that attune you to the pace, subject matter, and
difficulty of the real exam.
On the night before the exam, reduce your study time
to one hour or less and get extra sleep. The reduced
study time and extra rest will allow your brain to better
process the information it has absorbed during earlier,
more intense, study sessions.
https://t.me/PrMaB
raise your hand and ask for the proctor’s permission
before doing so).
Smile as you take the exam. It has been proven that
smiling alleviates stress and boosts confidence during
exceptionally difficult tasks. Use deep breathing
techniques to further relax.
If you have exam time remaining, review the questions
you “marked for review”. Use all the exam time you
have until each question has been reviewed twice.
https://t.me/PrMaB
to those items you are not sure about afterwards. Always read
carefully through the entire test as well, and do your best to
not leave any question blank upon submission– even if you do
not readily know the answer.
Most of the PMI-PBA® exam questions are scenario-based
questions. The format of such a question is a short-scenario
followed by a question. There are occasions where the
scenario is not totally relevant to the actual question being
asked. Such questions are designed to confuse test takers. Use
the online highlighting tool to highlight the actual question so
that you don’t get confused. In case the scenario is relevant to
the question, you can also use the highlighting tool to highlight
important keywords from the scenario.
Many people do well with reading through each question and
not looking at the options before trying to answer. This way,
they can steer clear (usually) of being fooled by one of the
“distracter” options or get into a tug-of-war between two
choices that both have a good chance of being the actual
answer. You may also want to use the strikethrough feature to
strike out the choice(s) you think are not correct. Note that,
striking out is only a user-interface feature and striking out
three choices does not mean that the fourth choice is
automatically selected as the correct answer; you must select
the choice you want to submit as the correct answer.
Never assume that “all of the above” or “none of the above”
answers are the actual choice. Many times they are, but in
recent years they have been used much more frequently as
distracter options on standardized tests. Typically, this is done
in an effort to get people to stop believing the myth that they
are always the correct answer.
You should be careful of negative answers as well. These
answers contain words such as “none”, “not”, “neither”, and
the like. Despite often times being very confusing, if you read
these types of questions and answers carefully, then you
should be able to piece together which is the correct answer.
Just take your time!
Never try to overanalyze a question, or try and think about
how the test givers are trying to lead astray potential test
https://t.me/PrMaB
takers. Keep it simple and stay with what you know.
If you ever narrow down a question to two possible answers,
then try and slow down your thinking and think about how the
two different options/answers differ. Look at the question
again and try to apply how this difference between the two
potential answers relates to the question. If you are convinced
there is literally no difference between the two potential
answers (you’ll more than likely be wrong in assuming this),
then take another look at the answers that you’ve already
eliminated. Perhaps one of them is actually the correct one
and you’d made a previously unforeseen mistake.
On occasion, over-generalizations are used within response
options to mislead test takers. To help guard against this,
always be wary of responses/answers that use absolute words
like “always”, or “never”. These are less likely to actually be
the answer than phrases like “probably” or “usually” are.
Funny or witty responses are also, most of the time, incorrect –
so steer clear of those as much as possible.
Although you should always take each question individually,
“none of the above” answers are usually less likely to be the
correct selection than “all of the above” is. Keep this in mind
with the understanding that it is not an absolute rule and
should be analyzed on a case-by-case (or “question-by-
question”) basis.
Looking for grammatical errors can also be a huge clue. If the
stem ends with an indefinite article such as “an” then you’ll
probably do well to look for an answer that begins with a
vowel instead of a consonant. Also, the longest response is
also oftentimes the correct one, since whoever wrote the
question item may have tended to load the answer with
qualifying adjectives or phrases in an effort to make it correct.
Again though, always deal with these on a question-by-
question basis, because you could very easily be getting a
question where this does not apply.
Verbal associations are oftentimes critical because a response
may repeat a key word that was in the question. Always be on
the alert for this. Playing the old Sesame Street game “Which
of these things is not like the other” is also a very solid
https://t.me/PrMaB
strategy, if a bit preschool. Sometimes many of a question’s
distracters will be very similar to try to trick you into thinking
that one choice is related to the other. The answer very well
could be completely unrelated however, so stay alert.
Just because you have finished a practice test, be aware that
you are not done working. After you have graded your test
with all of the necessary corrections, review it and try to
recognize what happened in the answers that you got wrong.
Did you simply not know the qualifying correct information?
Perhaps you were led astray by a solid distracter answer?
Going back through your corrected test will give you a leg up
on your next one by revealing your tendencies as to what you
may be vulnerable with, in terms of multiple-choice tests.
It may be a lot of extra work, but in the long run, going
through your corrected multiple-choice tests will work
wonders for you in preparation for the real exam. See if you
perhaps misread the question or even missed it because you
were unprepared. Think of it like instant replays in
professional sports. You are going back and looking at what
you did on the big stage in the past so you can help fix and
remedy any errors that could pose problems for you on the real
exam.
https://t.me/PrMaB
LOOKING FOR MORE
PMI-PBA EXAM PREP,
COURSEWARE, AND
CLASSES?
Visit us at www.PMTraining.com
https://t.me/PrMaB