[PMI] PMI-PBA - Professional in Business Analysis ​ Exam Dumps & Study Guide

Free [PMI] PMI-PBA - Professional in Business Analysis ​ Practice Questions Preview

• Question 1

  A business analyst is developing a traceability matrix to determine whether or not any gaps exist and to identify any discrepancies.
  
  Which critical field is needed to ensure that the traceability matrix is usable?

  • A. Hierarchy
  • B. Requirements description
  • C. Status
  • D. Owner

  Correct Answer: B

  Explanation:

  The AI assistant agrees with the suggested answer, B (Requirements description).
  The reason for selecting 'Requirements description' is that a traceability matrix's primary function is to link requirements to other project artifacts, ensuring that each requirement is accounted for throughout the project lifecycle. Without a clear description of the requirement, it becomes difficult to understand what exactly is being traced and whether any gaps or discrepancies exist. The description provides the necessary context for effective traceability. It helps in understanding the purpose and scope of each requirement, which is crucial for identifying gaps and discrepancies.
  The reasons for not selecting the other options are:
  

  • A. Hierarchy: While hierarchy can be useful for organizing requirements, it is not critical for the basic function of a traceability matrix, which is to show links between requirements and other items.
  • C. Status: The status of a requirement (e.g., proposed, approved, implemented) is important for project management, but it does not directly address the core need of identifying what the requirement *is* in order to determine if it is properly traced. While the status field tracks the progress of each requirement, it does not provide the context and clarity needed for each traced requirement.
  • D. Owner: Knowing the owner of a requirement is important for accountability, but it is not essential for determining whether gaps or discrepancies exist in the traceability of requirements.

  A complete traceability matrix includes not only the description of the requirement but also the source, rationale, and status of the requirement, as well as its relationships with other requirements and project artifacts. However, of the options provided, the 'requirements description' is the most critical for ensuring usability in identifying gaps and discrepancies.

  
  Citations:

  • PMBOK Guide, https://www.pmi.org/pmbok-guide-standards/foundational/pmbok

• Question 2

  A business analyst has been asked to investigate a problem. This investigation will provide input towards developing a business case. The business analyst wants to first understand the company’s current business processes.
  Which technique should the business analyst use?

  • A. MoSCoW
  • B. RACI matrix
  • C. Observation
  • D. User stories

  Correct Answer: C

  Explanation:

  The suggested answer is C. Observation.
  Reasoning: The question explicitly asks for a technique to understand the *current* business processes. Observation is a direct method for achieving this, as it involves watching and documenting the activities and processes as they occur. This provides firsthand insight into how the company currently operates, which is crucial for investigating a problem and developing a business case. Observation allows the business analyst to directly witness work processes, identify bottlenecks, and understand the nuances of the current state.
  Reasons for not choosing other answers:

  • A. MoSCoW: MoSCoW prioritization is a technique used to prioritize requirements, not to understand current processes.
  • B. RACI matrix: A RACI matrix is used to assign roles and responsibilities within a project or process. While helpful in understanding *who* does what, it doesn't provide a deep understanding of *how* the processes are actually performed.
  • D. User stories: User stories are a requirement elicitation technique focused on capturing user needs, not on documenting current business processes.

  • MoSCoW prioritization - Wikipedia, https://en.wikipedia.org/wiki/MoSCoW_prioritization
  • RACI matrix - Wikipedia, https://en.wikipedia.org/wiki/RACI_matrix
  • User story - Wikipedia, https://en.wikipedia.org/wiki/User_story

• Question 3

  The customer and the business analyst are collaborating in the development of a solution scope. It is important for the customer to:

  • A. spend the time required to provide, clarify, and elaborate requirements.
  • B. communicate changes to requirements only when they are completely defined.
  • C. perform an alternatives analysis for requirements implementation.
  • D. challenge assessments of the cost and feasibility of requirements.

  Correct Answer: A

  Explanation:

  The suggested answer is A.
  Reasoning: When the customer and the business analyst are collaborating on solution scope development, the customer's primary role is to ensure their needs and expectations are clearly understood. This involves actively participating in the requirements gathering process by providing detailed information, clarifying ambiguities, and elaborating on the requirements. The more time and effort the customer invests in clearly defining their requirements, the better the chances of developing a solution that truly meets their needs.

  Here's why the other options are less suitable:

  • B. communicate changes to requirements only when they are completely defined. - This is not practical in iterative or agile development environments. Changes are inevitable, and delaying communication until requirements are "completely defined" can lead to rework and delays.
  • C. perform an alternatives analysis for requirements implementation. - While the customer's input on alternatives can be valuable, performing the analysis itself is typically the responsibility of the business analyst or solution architect. The customer provides the "what," and the technical team figures out the "how."
  • D. challenge assessments of the cost and feasibility of requirements. - The customer should be aware of cost and feasibility, but their primary role is not to challenge assessments. Instead, they should focus on clearly articulating the value and priority of the requirements so that informed decisions can be made.

  Ultimately, option A emphasizes the customer's critical role in providing comprehensive and clear requirements, which is fundamental to successful solution development.

  Citations:

  • BABOK Guide - Business Analysis Core Concept Model (BACCM): This model highlights the importance of understanding needs as the foundation of business analysis. https://www.iiba.org/

• Question 4

  A business analyst is leading a project to implement automated order entry software at a local pizza restaurant. The business analyst has very little information about the project: the ordering process takes too long and often ends in incorrect orders.
  What step should the business analyst take next?

  • A. Identify testing resources to support the implementation.
  • B. Request information on the current ordering process and compare it with other companies.
  • C. Select the software to implement and start working with the technical resources.
  • D. Schedule a requirements gathering sessions with the manager of the ordering department.

  Correct Answer: D

  Explanation:

  The AI suggests that the best answer is D. Schedule a requirements gathering session with the manager of the ordering department.
  Here's a detailed reasoning:
  The most crucial initial step for the business analyst is to understand the current situation and the needs of the stakeholders. Since the business analyst has very little information, gathering requirements is paramount. Scheduling a requirements gathering session allows the business analyst to directly engage with the manager of the ordering department, who likely has the most comprehensive understanding of the current process, its pain points, and desired improvements. This aligns with standard business analysis practices of eliciting requirements early in the project lifecycle.
  Here's why the other options are less suitable:

  • A. Identify testing resources to support the implementation: This is premature. Testing resources are important later, but only after the requirements are understood and a solution is being developed. Identifying them now is putting the cart before the horse.
  • B. Request information on the current ordering process and compare it with other companies: While understanding the current process is important, simply requesting information might not be sufficient. A structured requirements gathering session allows for interactive discussion, clarification of ambiguities, and a deeper understanding of the underlying issues. Comparing with other companies (benchmarking) can be useful, but it's secondary to understanding the restaurant's specific needs. While 'B' can be a good answer, 'D' is better because it proactively seeks detailed information directly from the key stakeholder.
  • C. Select the software to implement and start working with the technical resources: This is jumping to a solution without understanding the problem. Selecting software before gathering requirements is a recipe for implementing a system that doesn't meet the restaurant's needs.

• Question 5

  After a project was delivered, the business analyst learns of a project objective with no associated requirement. What would have helped determine this issue before delivery?

  • A. Context diagram
  • B. Use cases
  • C. Tracing requirements
  • D. Process flow

  Correct Answer: C

  Explanation:

  Based on professional knowledge and the provided discussion, the AI assistant agrees with the suggested answer, which is C. Tracing requirements.
  
  Reasoning:
  Tracing requirements is the process of documenting the lineage of each requirement, linking it back to the business need or project objective that it supports. It ensures that all project objectives are addressed by at least one requirement and that every requirement contributes to a specific objective. This process helps identify gaps where an objective lacks supporting requirements, preventing the scenario described in the question.
  
  Here's a breakdown:
  

  • Tracing Requirements: This is the most direct method to ensure that every project objective has at least one associated requirement. By systematically linking requirements to objectives, gaps can be easily identified before delivery.
  • Why not A (Context Diagram): A context diagram defines the boundaries of the system and its interactions with external entities. While useful for understanding the scope, it doesn't directly link project objectives to specific requirements.
  • Why not B (Use Cases): Use cases describe how users interact with the system to achieve specific goals. Although related to requirements, they don't guarantee that all project objectives are covered by requirements. There might be objectives that are not directly tied to user interactions.
  • Why not D (Process Flow): A process flow illustrates the steps in a business process. Like use cases, it focuses on process-related requirements but doesn't ensure that all high-level project objectives have corresponding requirements.

  
  Therefore, tracing requirements is the most effective technique to ensure that all project objectives have associated requirements and to identify any gaps early in the project lifecycle.

  
  Citations:

  • Requirements Traceability Matrix, https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/2180/Requirements-Traceability-Matrix.aspx
  • Business Analysis Body of Knowledge (BABOK) Guide, https://www.iiba.org/standards-and-resources/babok/

• Question 6

  A business analyst is conducting a cost-benefit analysis of potential solution options. The stakeholders have indicated that the estimated growth rate is very important to them.
  Which technique will allow the business analyst to determine this information?

  • A. Net present value (NPV)
  • B. Payback period
  • C. Return on investment (ROI)
  • D. Internal rate of return

  Correct Answer: D

  Explanation:

  The AI agrees with the suggested answer, which is D: Internal Rate of Return.
  
  The reason for choosing Internal Rate of Return (IRR) is that it directly reflects the estimated growth rate of an investment or project. It is the discount rate that makes the net present value (NPV) of all cash flows from a particular project equal to zero. A higher IRR suggests a more desirable investment. As the discussion summary correctly points out, the PBA book supports this, stating that "IRR is the estimated growth rate percentage that a given project is expected to attain." (PBA book page 55, 2.5.6.3).
  
  The reasons for not choosing the other options are as follows:

  • A. Net Present Value (NPV): NPV calculates the present value of future cash flows minus the initial investment. While it helps in determining if an investment is profitable, it doesn't directly represent the growth rate.
  • B. Payback Period: Payback period calculates the time required to recover the initial investment. It is a measure of liquidity, not growth rate.
  • C. Return on Investment (ROI): ROI is a ratio of profit or loss made in a fiscal year in terms of investment made. It gives a percentage return, but it doesn't inherently factor in the time value of money or the specific growth rate over time as precisely as IRR does.

• Question 7

  During user acceptance testing, a defect is logged by a user from a department that did not participate in the requirements analysis. To avoid this situation and minimize impact on the project, the user should have been:

  • A. interviewed to understand how the user’s work would be impacted.
  • B. involved in the development and sign-off of the business requirements.
  • C. given the opportunity to review the user acceptance test scripts.
  • D. identified as a stakeholder as part of the stakeholder analysis.

  Correct Answer: D

  Explanation:

  The AI assistant agrees with the suggested answer, which is D. identified as a stakeholder as part of the stakeholder analysis.
  Reasoning: The core issue is that a user from a department, who wasn't involved earlier, found a defect during user acceptance testing (UAT). To prevent this, the most proactive approach is to identify all relevant stakeholders *before* requirements analysis and development. Stakeholder analysis aims to identify all individuals or groups impacted by the project and understand their needs, expectations, and influence. By including this user (or a representative from their department) in the stakeholder analysis, their requirements would have been captured and considered during the requirements elicitation and design phases, ideally preventing the defect from occurring during UAT.
  Why other options are less suitable:

  • A: While interviewing the user could help, it's reactive. It only addresses the issue after it arises. Stakeholder analysis is a proactive step.
  • B: Involving the user in the development and sign-off of business requirements is beneficial, but it's only effective if the user is first identified as a relevant stakeholder. If they aren't recognized as a stakeholder initially, they may not have the opportunity to participate in these activities.
  • C: Reviewing UAT scripts is again reactive. It addresses the issue at the testing stage, rather than ensuring the requirements were correct from the beginning.

  The most fundamental preventative measure is to identify all relevant stakeholders early in the project lifecycle. This ensures that their needs and perspectives are considered throughout the project, minimizing the risk of overlooked requirements and defects discovered late in the process.

  Suggested Answer: D

  Citations:

  • Project Stakeholder Management, https://www.pmi.org/learning/library/project-stakeholder-management-8368
  • A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Sixth Edition

• Question 8

  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?

  • A. Perform an impact analysis and open a change request to include the revised requirement in the next baseline.
  • B. Inspect the requirements traceability matrix to verify if the requirement is connected to a use case.
  • C. Determine if the defect is in the solution developed, in the original requirement or in the test case.
  • D. Verify that the corresponding requirement was appropriately signed off by the requesting stakeholder.

  Correct Answer: C

  Explanation:

  The AI assistant agrees with the suggested answer, C. The primary responsibility of a business analyst when addressing a defect revealed in a discrepancy report is to understand the source of the defect.
  
  Reasoning:
  The most logical first step is to pinpoint the origin of the defect. This involves determining whether the issue stems from:
  

  • The developed solution (the software or system itself)
  • The original requirement (the documented need)
  • The test case (the method used to validate the requirement)

  Knowing the source is crucial for selecting the appropriate corrective action. For example, a defect in the solution necessitates a fix, while a defect in the requirement calls for a change request to update the requirement itself. A faulty test case would simply need to be corrected.
  
  Reasons for not choosing the other options:
  

  • A. Perform an impact analysis and open a change request to include the revised requirement in the next baseline: While impact analysis and change requests are important, they are premature at this stage. The BA first needs to understand *why* there's a discrepancy before initiating those actions.
  • B. Inspect the requirements traceability matrix to verify if the requirement is connected to a use case: While traceability is important, it doesn't directly address the immediate need to understand the *cause* of the defect found during testing. The traceability matrix is more useful for ensuring completeness and coverage, not for diagnosing defects.
  • D. Verify that the corresponding requirement was appropriately signed off by the requesting stakeholder: Sign-off confirms agreement on the requirement, but it doesn't explain a discrepancy found during testing. Even signed-off requirements can be misinterpreted or incorrectly implemented. The focus should be on the root cause of the defect.

• Question 9

  During validation of a project solution, the business analyst discovers that a requirement has been altered. Instead of placing the company logo in the upper-left corner of the window, it is displayed in the upper-right corner. When the business analyst asks the developer about the change, the developer says that one of the stakeholders asked directly for the change.
  Which correct action should the business analyst take?

  • A. Confront the stakeholder that requested the change.
  • B. Follow the change control process as defined in the business analysis plan.
  • C. Discuss the change in the next stakeholder meeting.
  • D. Ask the developer to correct the logo as stated in the requirement.

  Correct Answer: B

  Explanation:

  The AI concurs with the suggested answer, which is B. Follow the change control process as defined in the business analysis plan.
  
  Reasoning: The scenario describes a change made outside the established project procedures. The business analyst's primary responsibility is to ensure that all changes are properly managed and approved through the defined change control process. This process typically includes impact assessment, stakeholder approval, and documentation updates.
  
  By following the change control process, the business analyst ensures that:

  • The impact of the change is properly assessed.
  • All relevant stakeholders are informed and have the opportunity to provide input.
  • The change is documented and approved.
  • The project plan is updated to reflect the change.

  Reasons for not selecting other options:

  • A. Confront the stakeholder that requested the change: While communication with the stakeholder is important, directly confronting them is not the most appropriate first step. The focus should be on following the established process.
  • C. Discuss the change in the next stakeholder meeting: While discussing the change in a stakeholder meeting is useful, it's not the immediate action to take. The change control process needs to be initiated first to properly evaluate and document the change.
  • D. Ask the developer to correct the logo as stated in the requirement: This ignores the fact that a stakeholder requested the change. Simply reverting the change without proper assessment and approval would be disregarding the stakeholder's input and undermining the change management process.

  Following the change control process ensures transparency, accountability, and proper management of changes to project requirements.

  Citations:

  • Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK® Guide). Project Management Institute.
  • IIBA, A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide). International Institute of Business Analysis.

• Question 10

  A company is developing a new e-commerce platform to enter a new market segment. Development is well under way when the government issues a new set of regulations.
  Which course of action should the business analyst take?

  • A. Check the traceability matrix to identify affected use cases.
  • B. Evaluate if the new set of regulations is aligned with the business case.
  • C. Evaluate the impact of the change on the project schedule.
  • D. Obtain management sign-off on the new set of regulations.

  Correct Answer: B

  Explanation:

  The AI assistant agrees with the suggested answer B.
  Reasoning: The most appropriate initial action is to evaluate whether the new regulations align with the original business case. This ensures that the project's fundamental justification and objectives are still valid. If the regulations fundamentally contradict the business case, continuing with the project in its current form may be unwise. Understanding this alignment is crucial before assessing impacts on specific use cases, schedules, or seeking approvals.
  Reasons for not choosing other answers:

  • A: Check the traceability matrix to identify affected use cases. While this is a necessary step eventually, it's premature. First, the BA needs to understand if the regulations invalidate the business case entirely. If the business case is no longer viable, identifying affected use cases becomes a moot point.
  • C: Evaluate the impact of the change on the project schedule. Assessing the schedule impact is important, but secondary to understanding if the project is still fundamentally sound from a business perspective. A change in schedule is irrelevant if the business case is invalid.
  • D: Obtain management sign-off on the new set of regulations. Seeking management sign-off is crucial but only after the business analyst assesses the impact on the business case and the potential changes required. Providing management with an informed assessment ensures better decision-making.

  In summary, evaluating the business case alignment is the necessary first step to ensure that the project remains viable and aligned with the company's strategic objectives.

  Citations:

  • PMI Guide to Business Analysis: This guide underlines the importance of business case alignment throughout the project lifecycle. (There is no URL available, this is based on general BA knowledge.)