Limited-Time Offer: Enjoy 50% Savings! Ends in 00h 00m 00s Coupon code: 50OFF
Skip to content
Login Sign up

Free PMI Professional in Business Analysis PMI-PBA Exam Questions

Page: 1 / 14 Total 200 questions

Want more questions? Get Premium Access.

Question 1

A business analyst has captured all of the requirements from the various stakeholders within the organization and has compiled them into a complete list. After reviewing the list of requirements with the stakeholders, it is determined that the list of requirements is too large and will exceed the allotted budget.

Which tool or technique should the business analyst use with the stakeholders to prioritize the requirements to determine which requirements are approved, deferred, or rejected?

Correct Answer: B. Moscow Analysis
Explanation:

Moscow analysis is a tool or technique that the business analyst can use with the stakeholders to prioritize the requirements to determine which requirements are approved, deferred, or rejected. Moscow analysis is a method of categorizing requirements into four groups: must-have, should-have, could-have, and won't-have. Must-have requirements are essential and non-negotiable for the project success. Should-have requirements are important but not critical for the project success. Could-have requirements are desirable but not necessary for the project success. Won't-have requirements are out of scope or low priority for the current project. Moscow analysis can help to identify the most valuable and feasible requirements that can be delivered within the available time and budget. It can also help to manage stakeholder expectations and resolve conflicts or disagreements on the priority of the requirements. SMART goals is a tool or technique that can be used to define clear and measurable objectives for a project or a process, but it does not help to prioritize the requirements. SMART goals are specific, measurable, achievable, relevant, and time-bound. SWOT analysis is a tool or technique that can be used to assess the strengths, weaknesses, opportunities, and threats of a project or a process, but it does not help to prioritize the requirements. SWOT analysis can help to identify the internal and external factors that affect the project or process performance and quality. Timeboxing analysis is not a standard tool or technique in business analysis, but it may refer to a method of allocating a fixed amount of time for each task or activity in a project or a process, but it does not help to prioritize the requirements.Timeboxing analysis can help to manage time and resources efficiently and effectively.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 15; Business Analysis for Practitioners: A Practice Guide2, page 95.


Question 2

A project was in the design phase when the team received news of a new regulatory mandate that affects the project. The requirements have already been approved and baselined. If the new requirements are not included, the company will be out of compliance and may

face monetary penalties.

What should the business analyst do next?

Correct Answer: C. Follow the change control process.
Explanation:

The business analyst should follow the change control process to handle the new regulatory mandate that affects the project. The change control process is a set of procedures that defines how changes to the requirements or the project scope are identified, analyzed, approved, and implemented. The change control process helps to ensure that changes are aligned with the business need, the project objectives, and the stakeholder expectations.Reference: PMI Guide to Business Analysis, Chapter 9, Section 9.4.1; PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline, Domain IV: Traceability and Monitoring, Task 2.


Question 3

An organization is evaluating the possibility of conducting business internationally. Which factors should be investigated at the onset of the initiative?

Correct Answer: C. External dependencies
Explanation:

External dependencies are the factors or conditions that are outside the control of the project, but may affect its scope, schedule, cost, quality, or risks. External dependencies may include legal, regulatory, cultural, environmental, political, economic, or technological factors. An organization that is evaluating the possibility of conducting business internationally should investigate these factors at the onset of the initiative, as they may have significant impacts on the feasibility, viability, and desirability of the project. The other options are not factors that should be investigated at the onset of the initiative. Deliverables to be produced are the outputs or results of the project that meet the stakeholder requirements. Impacts on requirements baseline are the changes or deviations from the approved set of requirements that define the solution scope. Change control processes are the procedures and tools that manage how changes to the project scope, schedule, cost, quality, or risks are identified, evaluated, approved, implemented, and communicated. These factors are determined or addressed during the planning or execution phases of the project, not at the onset of the initiative.Reference: PMI-PBA Examination Content Outline, page 13; PMI-PBA Reference List, page 1, BABOK Guide v3, page 39;4.


Question 4

The project team is working on test scripts to test a solution. Which source can be used for building tests of end-to-end business processes across business functions and systems?

Correct Answer: C. Context diagram
Explanation:

A use case is a technique that describes how an actor interacts with a system to achieve a goal or perform a task. A use case consists of a main scenario and possible alternative scenarios that capture the normal, exceptional, and error flows of events. A use case can be used as a source for building tests of end-to-end business processes across business functions and systems, as it provides a comprehensive and realistic view of the expected behavior and outcomes of the solution.A use case can also help to verify and validate the functional requirements and acceptance criteria of the solution.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 20; Business Analysis for Practitioners: A Practice Guide2, page 99.


Question 5

The test team is reviewing requirements that were written for Project

Correct Answer: A, A
Explanation:

A use case is a technique that describes how an actor interacts with a system to achieve a goal or perform a task. A use case consists of a main scenario and possible alternative scenarios that capture the normal, exceptional, and error flows of events. A use case can also include the acceptance criteria that specify the conditions that must be met for the use case to be successfully completed and accepted by the stakeholders. The test team can review the use cases to help identify the acceptance criteria for the solution, as they provide a comprehensive and realistic view of the expected behavior and outcomes of the system.The test team can also use the use cases to design and execute test cases that verify and validate the functional requirements and acceptance criteria of the solution.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 20; Business Analysis for Practitioners: A Practice Guide2, page 99.


Question 6

A company has completed a major project within time, cost, and scope and satisfied high-level quality standards and marketing requests. However, the product was considered a complete failure by shareholders and the market due to low return on investment.

From the business analysis perspective, the main reason for this business failure was a failure to:

Correct Answer: D. establish measurable success criteria in the business case.
Explanation:

The main reason for the business failure was a failure to establish measurable success criteria in the business case. The success criteria are the standards or indicators that are used to measure the achievement of the business objectives and the expected benefits of the project. The success criteria should be defined and agreed upon by the stakeholders in the business case, and they should be specific, measurable, achievable, realistic, and time-bound (SMART). The success criteria can help the business analyst and the project team to evaluate the feasibility, viability, and desirability of the project, and to monitor and control the project performance and outcomes. The success criteria can also help to ensure the alignment of the project deliverables with the stakeholder expectations and the market needs.If the success criteria are not established or are poorly defined in the business case, the project may fail to deliver the desired value and return on investment, even if it meets the time, cost, scope, and quality constraints.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 16; Business Analysis for Practitioners: A Practice Guide2, page 86.


Question 7

For a large, highly complex project with significant risk, which elicitation technique should be used to analyze input to and output from the product?

Correct Answer: D. Interface analysis
Explanation:

Interface analysis is a technique that should be used to analyze input to and output from the product for a large, highly complex project with significant risk. Interface analysis is a technique that involves identifying and specifying how different components of a product interact with each other or with external systems or users. Interface analysis can help to define and document the data flows, formats, protocols, rules, and behaviors of each interface. Interface analysis can also help to identify and mitigate any risks or issues related to compatibility, integration, interoperability, or usability of the product. System analysis is not a technique that should be used to analyze input to and output from the product for a large, highly complex project with significant risk. System analysis is a broad term that refers to various activities and techniques for studying, designing, developing, testing, or maintaining a system. System analysis can include interface analysis as one of its aspects, but it is not a specific technique for analyzing input to and output from the product. Dependency analysis is not a technique that should be used to analyze input to and output from the product for a large, highly complex project with significant risk. Dependency analysis is a technique that involves identifying and evaluating how different elements of a project or a product depend on each other or on external factors. Dependency analysis can help to determine the impact of changes, prioritize tasks, allocate resources, or manage risks. Dependency analysis can include interface analysis as one of its aspects, but it is not a specific technique for analyzing input to and output from the product. Risk analysis is not a technique that should be used to analyze input to and output from the product for a large, highly complex project with significant risk. Risk analysis is a technique that involves identifying and assessing potential threats or uncertainties that may affect a project or a product. Risk analysis can help to quantify or qualify risks, prioritize risks, plan responses, or monitor risks.Risk analysis can include interface analysis as one of its aspects, but it is not a specific technique for analyzing input to and output from the product.Reference: Business Analysis for Practitioners: A Practice Guide1, page 78-79; PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline2, page 16-17.


Question 8

The business analyst is seriously concerned about the possibility of differing interpretations of data items mentioned in the requirements documents. Which course of action should the business analyst take to minimize the risk of misunderstanding?

Correct Answer: D. Hold a workshop with the development teams to explain the details of the requirements specification.
Explanation:

According to the PMI Guide to Business Analysis, a data dictionary is a tool that defines and describes the data elements and their attributes in a consistent and standardized way. A data dictionary can help to minimize the risk of misunderstanding or misinterpreting data items mentioned in the requirements documents, as it provides a common language and reference for all stakeholders involved in the project. A data dictionary can also help to ensure the quality, accuracy, and completeness of the data requirements. Planning a peer review, asking for a formal acceptance, or holding a workshop are other ways to improve the clarity and understanding of the requirements specification, but they do not address the specific issue of defining and describing the data items.Reference: PMI Guide to Business Analysis, page 169-170.


Question 9

Through user acceptance testing, a software flaw was identified. What should the business analyst do next as part of the root cause analysis in order to analyze and resolve the discrepancy?

Correct Answer: A. Create a fishbone diagram.
Explanation:

A fishbone diagram, also known as a cause-and-effect diagram or an Ishikawa diagram, is a tool that helps to identify and analyze the possible causes of a problem or an effect. It can help the business analyst to perform a root cause analysis in order to analyze and resolve the discrepancy identified through user acceptance testing. A fishbone diagram has a structure that resembles a fish skeleton, with a head, a spine, and several branches. The head represents the problem or the effect, the spine represents the main cause categories, and the branches represent the sub-causes or factors that contribute to the problem or the effect. By creating a fishbone diagram, the business analyst can brainstorm and organize the potential causes of the software flaw, and then investigate and verify the most likely root cause. A fishbone diagram can also help to communicate the findings and recommendations to the stakeholders and the development team. An interface analysis is a tool that helps to identify and describe the interactions and dependencies between different components or systems. It does not help to perform a root cause analysis in order to analyze and resolve the discrepancy identified through user acceptance testing, as it does not focus on the causes and effects of the problem. A Delphi estimation is a tool that helps to obtain a consensus among a group of experts on a complex or uncertain issue. It does not help to perform a root cause analysis in order to analyze and resolve the discrepancy identified through user acceptance testing, as it does not provide a systematic and structured way to identify and analyze the causes of the problem. A functional decomposition is a tool that helps to break down a complex system or process into smaller and simpler components or functions.It does not help to perform a root cause analysis in order to analyze and resolve the discrepancy identified through user acceptance testing, as it does not show the relationships and influences between the components or functions.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, PMI Guide to Business Analysis2, Business Analysis for Practitioners: A Practice Guide3, Root Cause Analysis: Definition, Examples & Methods | Tableau1


Question 10

A business analyst is reviewing a discrepancy report after a test session. The discrepancy report has revealed a defect that the business analyst must address.

Which of the following criteria should the business analyst use to identify the appropriate response to the defective test result?

Correct Answer: B. Determine if the defect is in the solution developed, in the original requirement, or in the test case.
Explanation:

The business analyst should determine if the defect is in the solution developed, in the original requirement, or in the test case. This criterion will help the business analyst to identify the root cause of the defect, and to decide the appropriate response to the defective test result. Depending on the source of the defect, the business analyst may need to revise the requirement, update the test case, or request a change to the solution.The business analyst should also communicate the defect and the response to the relevant stakeholders, and document the discrepancy report accordingly.References: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 25; Business Analysis for Practitioners: A Practice Guide2, page 140.


Question 11

Which tool is the most appropriate to aid in development of measurable and actionable requirements for a new project?

Correct Answer: B. Use case diagram

Question 12

A project team has 120 days to deliver a solution, but the stakeholders have too many requirements for the delivery window. What requirements prioritization technique should be used to determine which requirements will be delivered?

Correct Answer: B. MoSCoW
Explanation:

Time-boxing is a prioritization technique that involves assigning a fixed amount of time or resource to each requirement or deliverable, and delivering as much value as possible within that time or resource constraint. Time-boxing is useful when the project has a tight timeline or budget, and the stakeholders have too many requirements for the delivery window.Time-boxing helps to focus on the most important and valuable requirements, and to manage the expectations and scope of the stakeholders.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 18; Business Analysis for Practitioners: A Practice Guide2, page 97.


Question 13

Testing on a project has been completed. In order to proceed with deployment, a decision is needed.

Who should the business analyst contact to review the testing results and get approval to proceed with deployment?

Correct Answer: B. The person identified in the RACI matrix
Explanation:

The person identified in the RACI matrix as accountable for deployment approval is the one who should be contacted by the business analyst to review the testing results and get approval to proceed with deployment. The RACI matrix defines who is Responsible, Accountable, Consulted, and Informed for each task or deliverable in a project or a process. The accountable person has the authority and accountability to approve or reject the work. The tester identified in the testing strategy is not necessarily the one who can approve deployment, as they may only be responsible for conducting testing. The project manager identified in the project charter may not have the authority to approve deployment, as they may only be responsible for managing the project. The project sponsor identified in the scope document may not be involved in deployment approval, as they may only be informed of the project progress and outcomes.


Question 14

The stakeholders for a newly approved project are subject matter experts who are very knowledgeable in the client's business and will provide the project requirements. The project team scheduled separate sessions with each subject matter expert to identify and prioritize the requirements.

Which technique is being used?

Correct Answer: D. Workshop sessions
Explanation:

Workshop sessions are a technique to elicit, analyze, and prioritize requirements by bringing together a group of stakeholders, such as subject matter experts, to collaborate and reach a consensus. Workshop sessions can be used to identify and prioritize the requirements for a newly approved project. The other techniques are not suitable for this purpose. Delphi technique is a technique to obtain expert opinions anonymously and iteratively until a consensus is reached. Brainstorming is a technique to generate a large number of ideas or solutions in a short time. Idea and mind mapping is a technique to visually organize ideas or information using diagrams or graphs.Reference: PMI-PBA Examination Content Outline, page 10; PMI-PBA Reference List, page 1, BABOK Guide v3, page 50.


Question 15

A company has just finished the development work for a new software sales tracking application and is in the process of validating that the new application meets all of the acceptance criteria defined for the business requirements. During the validation

process, a stakeholder discovers that the application does not provide the selection criteria needed to produce the sales volume

reporting required by the company's financial department. The business analyst for the project determines that the selection criteria

needed was not specified in the system requirements or design specifications.

Which of the following tools and/or techniques might be used by the business analyst to determine how the selection criteria requirement

was missed?

Correct Answer: A. Root cause analysis, fishbone diagram, and/or the Five Whys
Explanation:

Root cause analysis is a technique that involves identifying and analyzing the underlying causes of a problem or an issue. Root cause analysis can help the business analyst to determine how the selection criteria requirement was missed, and to prevent similar errors from occurring in the future. Root cause analysis can be done using various tools, such as fishbone diagram and the Five Whys. A fishbone diagram is a graphical tool that organizes the possible causes of a problem into categories, such as people, process, technology, environment, etc. A fishbone diagram can help the business analyst to visualize the relationships between the causes and the effects, and to identify the most likely root causes. The Five Whys is a questioning technique that involves asking ''why'' repeatedly until the root cause of a problem is revealed.The Five Whys can help the business analyst to drill down into the details of the problem, and to uncover the underlying factors and assumptions that led to the missed requirement.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 21; Business Analysis for Practitioners: A Practice Guide2, page 101.


Page: 1 / 14 Total 200 questions