PMI Professional in Business Analysis PMI-PBA Exam Practice Test

Page: 1 / 14
Total 200 questions
Question 1

A business analyst is trying to complete the requirement documentation of a project and finds that the developers have started development. The business analyst should first facilitate the:



Answer : D

The requirements sign-off is a process that involves obtaining the formal approval and acceptance of the requirements from the customer and other stakeholders. The requirements sign-off confirms that the requirements are clear, complete, correct, and consistent, and that they meet the customer's needs and expectations. The requirements sign-off also establishes a baseline for the development and testing of the solution, and serves as a reference point for managing changes and resolving issues.The business analyst should first facilitate the requirements sign-off with the customer before the developers start development, to ensure that the requirements are agreed upon and validated by all parties, and to avoid rework, delays, and conflicts later in the project.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 18; Business Analysis for Practitioners: A Practice Guide2, page 92.


Question 2

A business analyst has elicited, documented, and verified the requirements, discovering that there are not enough resources to deliver all the requirements. Which technique should the business analyst employ to rectify the issue?



Answer : D

Asking stakeholders to vote on the requirements is a technique that the business analyst can employ to rectify the issue of not having enough resources to deliver all the requirements. Voting is a method of prioritizing requirements by asking stakeholders to rank or rate them according to their importance, urgency, value, or risk. Voting can help to identify the most critical or essential requirements that should be delivered first or within the available resources. Voting can also help to resolve conflicts or disagreements among stakeholders and reach a consensus on the priority of the requirements. Holding a brainstorming workshop to build the rationale for the requirements is not an effective technique to rectify the issue, as it does not address the resource constraint or the priority of the requirements. Brainstorming is a method of generating ideas or solutions by encouraging free and creative thinking from participants. Brainstorming can help to elicit or analyze requirements, but not prioritize them. Performing traceability to find out where the requirements originated is not a useful technique to rectify the issue, as it does not indicate the importance or value of the requirements. Traceability is a process of tracking the relationship between requirements and other project artifacts, such as design, test cases, or deliverables. Traceability can help to ensure completeness, consistency, and quality of the requirements, but not prioritize them. Surveying stakeholders on their likes and dislikes about the requirements is not a viable technique to rectify the issue, as it does not provide a clear or objective way of prioritizing the requirements. Surveying is a method of collecting feedback from stakeholders by asking them questions about their satisfaction, preferences, expectations, needs, problems, or suggestions.Surveying can help to validate or evaluate the requirements, but not prioritize them.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 15; Business Analysis for Practitioners: A Practice Guide2, page 95.


Question 3

A system enhancement project has been initiated to address the concerns of an external group of stakeholders not included in the first release. What should be done to ensure stakeholder satisfaction with the enhancement?



Answer : C

Engaging all stakeholders early in the requirements gathering phase is a good practice to ensure stakeholder satisfaction with the enhancement. By involving the stakeholders in the elicitation process, the business analyst can understand their needs, expectations, preferences, and constraints. By defining the acceptance criteria with the stakeholders, the business analyst can establish a clear and measurable definition of what constitutes a successful solution. Engaging all stakeholders early can also help to build trust, collaboration, and buy-in for the change. Requesting that the project manager identify all affected project stakeholders is not sufficient to ensure stakeholder satisfaction, as it does not involve direct communication with the stakeholders. Providing all signed-off project documentation to the stakeholders for information purposes only is not effective, as it does not allow for feedback or validation from the stakeholders.Soliciting feedback and adding requirements to the project backlog is not advisable, as it can lead to scope creep, rework, and delays.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 11; Business Analysis for Practitioners: A Practice Guide2, page 66.


Question 4

When faced with a tight timeline, the project sponsor suggests that the project team start development without creating traceability artifacts. What should the business analyst do?



Answer : B

The business analyst should explain the value of requirements traceability to the project sponsor. Requirements traceability is the process of tracking and documenting the relationships and dependencies among the requirements, the project deliverables, and the business objectives. Requirements traceability helps to ensure the quality, completeness, and alignment of the requirements, and to manage the changes, risks, and issues that may arise during the project.Requirements traceability also helps to measure the performance and the value of the solution, and to facilitate the verification and validation of the solution.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 20; Business Analysis for Practitioners: A Practice Guide2, page 100.


Question 5

Which of the following best describes the function of the requirements baseline?



Answer : C

The requirements baseline is a set of approved and prioritized requirements that are used as the basis for the development scope. The requirements baseline defines what the project or program will deliver and what the stakeholders expect to receive. The requirements baseline also serves as a reference point for managing changes and measuring progress.Reference: PMI Guide to Business Analysis, Chapter 9, Section 9.3.1; PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline, Domain IV: Traceability and Monitoring, Task 1.


Question 6

A company is working on the next big release of their best-selling product. The requirements will be validated through in-person validation sessions.

What would be the most viable technique to use in this scenario?



Answer : B

A review of the solution prototype would be the most viable technique to use in this scenario for validating requirements through in-person sessions. A solution prototype is a simplified version of part or all of a solution that can be used to elicit feedback from stakeholders. A review of a solution prototype involves presenting or demonstrating it to stakeholders and asking them questions to assess their satisfaction, understanding, agreement, or concerns. A review of a solution prototype can help to validate that the solution meets the stakeholder requirements and delivers value to them. A brainstorming session is a technique for generating ideas or solutions by encouraging free and creative thinking from participants. A brainstorming session can help to elicit or analyze requirements but not validate them. A use-case development session is a technique for creating use cases that describe how actors interact with a system to achieve their goals. A use-case development session can help to elicit or specify requirements but not validate them. A review of the previous version is a technique for examining an existing solution or product to identify its strengths, weaknesses, opportunities, or threats.A review of the previous version can help to elicit or analyze requirements but not validate them.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 13; Business Analysis for Practitioners: A Practice Guide2, page 76.


Question 7

A business analyst has incorporated all the relevant feedback from stakeholders in the business analysis plan.

Which next step should the business analyst take?



Answer : A

The next step that the business analyst should take after incorporating all the relevant feedback from stakeholders in the business analysis plan is to obtain approval on the plan. The business analysis plan is a document that describes how the business analysis activities will be performed, managed, and controlled throughout the project. It should be approved by the key stakeholders before the business analyst starts documenting or implementing the requirements. The approval process ensures that the stakeholders agree on the scope, approach, deliverables, roles, and responsibilities of the business analysis work. Starting documenting requirements without obtaining approval on the plan is not advisable, as it may lead to confusion, rework, or conflicts among the stakeholders. Storing the document for safe keeping is not a productive step, as it does not communicate or validate the plan with the stakeholders.Starting implementing the project without obtaining approval on the plan is not feasible, as it may result in wasted resources, missed expectations, or failed outcomes.Reference: Business Analysis for Practitioners: A Practice Guide1, page 29-30; PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline2, page 13.


Page:    1 / 14   
Total 200 questions