PMI Updated PMI-PBA Exam Questions and Answers by archibald

Power/interest grid is a technique that involves plotting the stakeholders on a matrix based on their level of power and interest in the project. Power/interest grid can help the business analyst to identify and categorize the stakeholders during the initial phase of a project by showing how influential and engaged each stakeholder is. Power/interest grid can also help to determine the appropriate communication and engagement strategy for each stakeholder group. References: = PMI Professional in Business Analysis (PMI-PBA) ® Examination Content Outline (2019), page 9; Business Analysis for Practitioners: A Practice Guide (2015), page 61.

 A force-field analysis is a tool that helps to identify and analyze the factors or forces that support or oppose a change or an initiative. It can help to facilitate the decision-making process when stakeholders do not agree on the value of an initiative by showing the pros and cons of the initiative, as well as the relative strength and importance of each factor. A force-field analysis can also help to develop strategies to increase the supporting forces or decrease the opposing forces, or both, to achieve the desired outcome. A PEST analysis is a tool that helps to examine the external factors that affect an organization or an initiative, such as political, economic, social, and technological factors. It does not help to facilitate the decision-making process when stakeholders do not agree on the value of an initiative, as it does not show the internal factors or the balance of forces. A feasibility analysis is a tool that helps to evaluate the viability and suitability of a project or an initiative, as well as the risks and benefits associated with it. It does not help to facilitate the decision-making process when stakeholders do not agree on the value of an initiative, as it does not show the supporting and opposing forces. A gap analysis is a tool that helps to compare the current state and the desired state of a process, a product, or a service, and identify the gaps or differences between them. It does not help to facilitate the decision-making process when stakeholders do not agree on the value of an initiative, as it does not show the factors or forces that influence the initiative. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, PMI Guide to Business Analysis2, Business Analysis for Practitioners: A Practice Guide3, What is Force Field Analysis: Definition and Example

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. References: 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

 According to the PMI Professional in Business Analysis objectives and content, the business analyst should recommend the option with the highest functionality score and the lowest cost score. In this case, option A, 1, Custom solution, has the highest functionality score of 10 and the lowest cost score of 1. Therefore, it should be recommended. References:

PMI Professional in Business Analysis objectives and content: PMI-PBA Certification

PMI Professional in Business Analysis reference list: PBA Reference List

PMI Professional in Business Analysis study guide: PMI.com