PMI Professional in Business Analysis PMI-PBA Exam Questions

Answer : B

A functional requirement is a requirement that specifies what the system should do or how it should behave under certain conditions. A functional requirement describes the functionality, behavior, or performance of the system.An example of a functional requirement is the system is able to require passwords, which defines a security feature of the system that prevents unauthorized access.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 17; Business Analysis for Practitioners: A Practice Guide2, page 92.

Answer : C

Clear and unambiguous requirements are crucial for verification. Ambiguity can lead to misunderstandings and difficulty in assessing whether the product meets the specified needs during testing.Reference: PMI-PBA Examination Content Outline, Business Analysis for Practitioners: A Practice Guide.

Answer : B

A requirements baseline document is the most valuable document for a business analyst to provide to the project sponsor to know which requirements will be implemented. A requirements baseline document is a version of the requirements specification that has been reviewed, approved, and formally established as the basis for further development and delivery of the solution. A requirements baseline document defines the scope of the project and the expected value of the solution. It also serves as a reference point for managing changes and measuring progress. A requirements traceability matrix is a document that shows the relationship between requirements and other project artifacts, such as design, test cases, or deliverables. A requirements traceability matrix can help to ensure completeness, consistency, and quality of the requirements, but it does not indicate which requirements will be implemented. A requirements management plan is a document that describes how requirements will be elicited, analyzed, documented, validated, and managed throughout the project. A requirements management plan can help to define the roles, responsibilities, processes, and tools for managing requirements, but it does not specify which requirements will be implemented. A reliability matrix is not a standard document in business analysis, but it may refer to a tool that measures the reliability or dependability of a system or a process.A reliability matrix can help to evaluate the performance or quality of a solution, but it does not determine which requirements will be implemented.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 13; Business Analysis for Practitioners: A Practice Guide2, page 76.

Answer : A

Operational feasibility is the kind of feasibility assessment that the business analyst is undertaking to understand how well a potential solution fits into the organization. Operational feasibility evaluates how the solution will affect the current operations, processes, culture, and people of the organization. It also considers how the solution will be accepted, adopted, and used by the stakeholders. Technical feasibility is not the kind of feasibility assessment that the business analyst is undertaking, as it evaluates how the solution can be implemented using the available technology, infrastructure, and resources. Cost-effectiveness feasibility is not the kind of feasibility assessment that the business analyst is undertaking, as it evaluates how the solution will provide benefits that outweigh its costs.Time feasibility is not the kind of feasibility assessment that the business analyst is undertaking, as it evaluates how long it will take to implement the solution and whether it can meet the desired schedule.Reference: Business Analysis for Practitioners: A Practice Guide, page 41-421; PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline, page 14

Answer : D

The business analyst should use document analysis as an elicitation technique during this time. Document analysis is a technique that involves reviewing and analyzing existing documents, such as policies, procedures, standards, reports, or contracts, to elicit information about the business needs, requirements, or solution options. Document analysis is useful when the stakeholders are not available to participate, or when the business analyst needs to gain background knowledge or context before engaging with the stakeholders.Document analysis can also help to identify gaps, issues, or assumptions that need to be clarified or validated with the stakeholders later.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 12; Business Analysis for Practitioners: A Practice Guide2, page 51.

Answer : A

A capability table is a tool that lists the current capabilities of an application and compares them with the desired capabilities identified by the end users. A capability table can help the business analyst to analyze this information and determine project scope by showing the gaps between the current and future states of the application, and prioritizing the new features that will address those gaps. A capability table can also help to define the high-level requirements and objectives of the project.Reference: = PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline (2019), page 11; Business Analysis for Practitioners: A Practice Guide (2015), page 67.

Answer : C

A product scope is a description of the features, functions, and characteristics of a product that meets the needs and expectations of the stakeholders. It defines what the product is and what it is not, and provides the basis for planning, developing, testing, and delivering the product. A product scope should align with the company's objectives, which are the desired outcomes or results that the company wants to achieve through its products, services, and projects.Aligning the product scope with the company's objectives helps to ensure that the product delivers value to the customers and the business, supports the company's vision and mission, and contributes to the company's strategic goals12.

To collaborate on a product scope that aligns with the company's objectives, the business analyst should follow these steps12:

Identify and engage the relevant stakeholders, such as the human resources, engineering, and marketing departments, as well as the product sponsor, the customers, and the end users. Stakeholders are the individuals or groups who have an interest or influence in the product, and who can provide input, feedback, and approval for the product scope.

Elicit and analyze the business needs, requirements, and expectations of the stakeholders, using various techniques, such as interviews, surveys, workshops, observation, prototyping, and brainstorming. Business needs are the problems or opportunities that the product aims to address or exploit, and that justify the investment in the product. Requirements are the specifications or conditions that the product must meet or satisfy to fulfill the business needs. Expectations are the desires or wishes that the stakeholders have for the product, which may or may not be realistic or feasible.

Validate and prioritize the business needs, requirements, and expectations, based on their value, urgency, risk, dependency, and alignment with the company's objectives. Validation is the process of ensuring that the business needs, requirements, and expectations are clear, complete, correct, consistent, and feasible. Prioritization is the process of ranking the business needs, requirements, and expectations according to their relative importance and impact on the product scope and the company's objectives.

Define and document the product scope, using various tools, such as a product vision statement, a product scope statement, a product backlog, a product roadmap, and a product breakdown structure. A product vision statement is a brief and compelling description of the purpose, value proposition, and target market of the product. A product scope statement is a detailed and formal description of the product scope, including the product objectives, deliverables, features, functions, boundaries, assumptions, constraints, and acceptance criteria. A product backlog is a list of the product requirements, features, and enhancements that are prioritized and refined for development. A product roadmap is a high-level and strategic plan that shows the direction, timeline, and milestones of the product development. A product breakdown structure is a hierarchical and graphical representation of the product components and their relationships.

Communicate and manage the product scope, using various techniques, such as reviews, walkthroughs, inspections, audits, and change control. Communication is the process of sharing and exchanging the product scope information with the stakeholders, and ensuring that they understand and agree on the product scope. Management is the process of monitoring and controlling the product scope, and ensuring that it is delivered according to the plan and the company's objectives. Change control is the process of evaluating, approving, and implementing any changes to the product scope, and ensuring that they are aligned with the company's objectives.

Voting on the product's highest-value business needs is not the best option, because it may not consider the perspectives and preferences of all the stakeholders, and it may not reflect the company's objectives. Negotiating to best meet each department's objectives is not the best option, because it may result in compromises or trade-offs that may not benefit the product or the company as a whole, and it may not align with the company's objectives.Delegating the decision to be made by the product sponsor is not the best option, because it may not involve the participation and collaboration of the other stakeholders, and it may not align with the company's objectives.Reference:1PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline, page 10-11;2Business Analysis for Practitioners: A Practice Guide, page 133-134