Free PMI Professional in Business Analysis Exam PMI-PBA Exam Practice Test

Two weeks prior to the delivery date, a customer changes the business requirements. What should the business analyst do?

• Ask the developers to implement the changes.
• Deliver the existing product and then begin work on the requested changes.
• Trace the requirements and measure the impact of the requested changes on the existing delivery date.
• Schedule a review by the change control board (CCB) to determine next steps.

A business analyst is planning the business analysis activities for a new payroll project. Due to a tight timeline, the analyst advises stakeholders that the requirements sessions should begin as soon aspossible.Which key factor drives the selection of business analyst activities to be included in the project?

• Return on investment (ROI)
• Project life cycle
• Communication plan
• Payback period

A document is being created that will detail the customer's needs for a product and will include a functional model, a data model, and a glossary of terms This document is called a:

• project charier.
• requirements specification.
• business case.
• standard operating manual.

The sales team of a company has won a time-and-malerial project. The business analyst discovers that the sales team has underestimated the required budget and scheduleWhich course of action should the business analyst take?

• Accept the contract, and deliver only the requirements that fit within the budget and schedule.
• Refrain from working on the project and request that the customer cancel the contract.
• Develop a requirements baseline document and use it to negotiate the scope in the contract.
• Accept the contract, and then notify the customer about the potential for a cost overrun.

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?

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

A company is developing a new product for a customer and is required to verify and validate the product against the customers acceptance test plan and requirements. The product was successfully verifiedagainst the acceptance test criteria, but the customer does not believe that the product meets the requirements.This occurred because the customer's acceptance test plan:

• was not included in the work breakdown structure.
• did not have measurable and testable requirements.
• was incomplete and missing requirements.
• was not formally accepted by the company.

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?

• Use cases
• Process flow
• Context diagram
• Tracing requirements

To reduce the amount of time and effort needed to create a product specification for a project, the business analyst plans to reuse:

• requirements
• qualitative analysis
• quantitative analysis
• risk assessments.

Which solution should be chosen according to the completed weighted-ranking matrix?

• Enhance the existing system.
• Purchase off-the-shelf software.
• Develop in-house software.
• Outsource the development.

A sponsor requests a new requirement The business analyst explains that most of the information needed for this requirement does not exist and that the requirement cannot be implemented. The business analyst recommends deferring the requirement until the needed information is available and then adding it to a subsequent project The sponsor agrees.What should the business analyst do next?

• Mark the requirement as complete so that it is not forgotten.
• Bring the subsequent project to the change control board (CCB).
• Communicate that the status of this requirement has changed.
• Ask the stakeholders to review the requirement before any other action is taken.