PMI Professional in Business Analysis certification questions and exam summary helps you to get focused on the exam. This guide also helps you to be on PMI-PBA exam track to get certified with good score in the final exam.
Business analysis has enhanced the ability of critical importance to project management. Becoming certified as a business analysis (BA) expert can improve your career in a new direction while events for BAs are on the rise. It is time to grow the certified professional for your organization requirements. If you work with stakeholders in setting requirements, shaping project outputs and driving required business outcomes, the PMI Professional in Business Analysis (PMI-PBA) will spotlight your necessary skills.
PMI Professional in Business Analysis (PMI-PBA) Certification Summary
Exam Name: Business Analysis Professional
Exam Code: PMI-PBA
Exam Fee Member: USD $405
Exam Fee Non-member: USD $555
Exam Duration: 240 Minutes
Number of Questions: 200
Passing Score: Above Target / Target / Below Target / Needs Improvement
Format: Multiple Choice Questions
Books / Trainings: Handbook
Schedule Exam: Apply Now
Sample Questions: PMI-PBA Exam Sample Questions and Answers
Practice Exam: PMI Professional in Business Analysis (PMI-PBA) Practice Test
PMI Professional in Business Analysis (PMI-PBA) Certification Exam Syllabus
Domain 1: Needs Assessment (18%)
Task 1
- Define or review a business problem or opportunity using problem and opportunity analysis techniques in order to develop a solution scope statement and/or to provide input to create a business case.
Task 2
- Collect and analyze information from a variety of sources using valuation tools and techniques to contribute to determining the value proposition of the initiative
Task 3
- Collaborate in the development of project goals and objectives by providing clarification of business needs and solution scope in order to align the product with the organization’s goals and objectives.
Task 4
- Identify stakeholders by reviewing goals, objectives, and requirements in order that the appropriate parties are represented, informed and involved.
Task 5
- Determine stakeholder values regarding the product, using elicitation techniques in order to provide a baseline for prioritizing requirements.
Domain 2: Planning (22%)
Task 1
- Review the business case, and the project goals and objectives, in order to provide context for business analysis activities.
Task 2
- Define strategy for requirements traceability using traceability tools and techniques in order to establish the level of traceability necessary to monitor and validate the requirements.
Task 3
- Develop requirements management plan by identifying stakeholders, roles and responsibilities, communication protocols, and methods for eliciting, analyzing, documenting, managing, and approving requirements in order to establish a roadmap for delivering the expected solution.
Task 4
- Select methods for requirements change control by identifying channels for communicating requests and processes for managing changes in order to establish standard protocols for incorporation into the change management plan.
Task 5
- Select methods for document control by using documentation management tools and techniques in order to establish a standard for requirements traceability and versioning.
Task 6
- Define business metrics and acceptance criteria by collaborating with stakeholders for use in evaluating when the solution meets the requirements.
Domain 3: Analysis (35%)
Task 1
- Elicit or identify requirements, using individual and group elicitation techniques in order to discover and capture requirements with supporting details (e.g., origin and rationale).
Task 2
- Analyze, decompose, and elaborate requirements using techniques such as dependency analysis, interface analysis, and data and process modeling in order to collaboratively uncover and clarify product options and capabilities.
Task 3
- Evaluate product options and capabilities by using decision-making and valuation techniques in order to determine which requirements are accepted, deferred, or rejected.
Task 4
- Allocate accepted or deferred requirements by balancing scope schedule, budget, and resource constraints with the value proposition using prioritization, dependency analysis, and decision-making tools and techniques in order to create a requirements baseline.
Task 5
- Obtain sign-off on requirements baseline using decision-making techniques in order to facilitate stakeholder consensus and achieve stakeholder approval.
Task 6
- Write requirements specifications using process (such as use cases, user stories), data, and interface details in order to communicate requirements that are measurable and actionable (that is, suitable for development).
Task 7
- Validate requirements using tools and techniques such as documentation review, prototypes, demos, and other validation methods in order to ensure requirements are complete, accurate and aligned with goals, objectives, and value proposition.
Task 8
- Elaborate and specify detailed metrics and acceptance criteria using measurement tools and techniques for use in evaluating whether the solution meets requirements.
Domain 4: Traceability and Monitoring (15%)
Task 1
- Track requirements using a traceability artifact or tools, capturing the requirements' status, sources and relationships (including dependencies), in order to provide evidence that the requirements are delivered as stated.
Task 2
- Monitor requirements throughout their lifecycles using a traceability artifact or tool in order to ensure the appropriate supporting requirements artifacts (such as models, documentation, and test cases) are produced, reviewed and approved at each point in the lifecycle.
Task 3
- Update a requirement’s status as it moves through its lifecycle states by communicating with appropriate stakeholders and recording changes in the traceability artifact or tool in order to track requirements towards closure.
Task 4
- Communicate requirements status to project manager and other stakeholders using communication methods in order to keep them informed of requirements issues, conflicts, changes, risks, and overall status.
Task 5
- Manage changes to requirements by assessing impacts, dependencies, and risks in accordance with the change control plan, and comparing to the requirements baseline in order to maintain the integrity of the requirements and associated artifacts.
Domain 5: Evaluation (10%)
Task 1
- Validate the solution's test results, reports, and other test evidence against the requirements acceptance criteria in order to determine whether the solution satisfies the requirements.
Task 2
- Analyze and communicate the solution's identified gaps and deltas using quality assurance tools and methods in order to enable stakeholders to resolve discrepancies between solution scope, requirements, and developed solution.
Task 3
- Obtain stakeholder sign-off on the developed solution using decision-making techniques in order to proceed with deployment.
Task 4
- Evaluate the deployed solution using valuation techniques in order to determine how well the solution meets the business case and value proposition.
PMI Professional in Business Analysis (PMI-PBA) Certification Questions
01. In a Scrum team, who enforces the rules and processes?
Options:
a) The Scrum Master
b) The development team
c) The stakeholders
d) The product owner
02. Which of the following are not among the most commonly used traceability tools?
Options:
a) Trace matrices
b) Traceability chain
c) Decision trees
d) Specification trees
03. At what time during the project is it most common for the retrospective to occur?
Options:
a) At any given time
b) At the beginning of every iteration or sprint
c) At the end of every iteration or sprint
d) At the end of a release
04. You have developed a RASCI chart. Who is most likely responsible for identifying stakeholders?
Options:
a) The business analyst
b) The development team
c) The sponsor
d) The Scrum Master
05. How would the business analyst monitor requirements throughout their life cycle?
Options:
a) Traceability artifacts or tools
b) Use models, documentation, and test cases
c) All of the above
d) None of the above
06. Business needs may arise from:
Options:
a) Market demands
b) Social need
c) Legal requirements
d) All of the above
07. Using the Brown Cow Model, the current situation will be found in which section?
Options:
a) Upper left corner
b) Lower left corner
c) Lower right corner
d) Upper right corner
08. What is one of the key challenges with requirements elicitation?
Options:
a) Recording the voice of the customer
b) Too many techniques to choose from
c) Too little time
d) Managing scope
09. Stakeholder analysis is performed to identify which of the following?
Options:
a) Each stakeholder's interest in the project
b) Potential conflicts in stakeholder viewpoint/interests that must be balanced
c) Communication needs of each stakeholder throughout the phases of the project
d) All of the above
10. Which one of the following factors most affects the choice of communication and collaboration technology?
Options:
a) Costs
b) Availability of technology
c) Project environment
d) Documentation
Answers:
Question: 01 Answer: a
Question: 02 Answer: c
Question: 03 Answer: c
Question: 04 Answer: a
Question: 05 Answer: c
Question: 06 Answer: d
Question: 07 Answer: b
Question: 08 Answer: a
Question: 09 Answer: d
Question: 10 Answer: c
How to Register for PMI Professional in Business Analysis Certification Exam?
Exam Registration:
Visit site for Register PMI Professional in Business Analysis Certification Exam.
Comments