Last Updated on March 19, 2022 by Admin 2

PMI-PBA : PMI Professional in Business Analysis : Part 08

  1. A stakeholder requests to add new critical requirements the day before the scheduled baseline requirements approval meeting. The stakeholder insists that these requirements must be taken into account despite time and budget constraints.

    What is the most effective way to manage this situation?

    • Postpone the baseline approval meeting, analyze the impact, and schedule a new meeting to discuss dependencies and priorities with stakeholders.
    • Share the new requirements with all stakeholders and ask them to submit their comments before the meeting.
    • Ask for more resources to manage this change and justify these additional resources with the value the change will give to the company.
    • Discuss the change with stakeholders during the baseline approval meeting and ask them to approve the new baseline.
  2. The following requirement was included in a business requirements document: “An API shall be built to send data back and forth from the accounting system to the customer relationship system so that name and address data can be synchronized.” What should be done with this business requirement?

    • It should remain because it specifies the reason why the business requirement is needed.
    • It should be revised because it states a solution to the problem rather than the business need.
    • It should be removed because it does not state how often the data should be synchronized.
    • It should remain because it specifies the type of data and the source system.
  3. What is one benefit of documenting the change control process?

    • Stakeholders understand the difficulty of managing requirements.
    • Stakeholders know how to request changes.
    • Stakeholders have a schedule of changes to be deployed.
    • Stakeholders are shielded from how changes are assessed.
  4. A business analyst is working on a system enhancement project and has completed the requirements according to the requirements management plan. The business analyst is now ready to request approval from the stakeholders.

    How should the business analyst obtain approval?

    • Provide a defect tracking log for review.
    • Conduct a formal or informal review of the requirements.
    • Send an email requesting approval of requirements.
    • Create and maintain an audit history log of changes to requirements.
  5. A project affects the marketing unit and procurement unit. The project manager gives the business analyst an overview of the project for the first time.

    What should the business analyst do immediately after the discussion?

    • Schedule time with the process owners.
    • Develop an issues log.
    • Put the information into a project plan.
    • Assess the risks for the project.
  6. The business analyst generated a design specification for a new product. What is the best type of formal review to conduct with the customer to establish an approved requirements baseline?

    • Critical design review
    • Production readiness review
    • System requirements review
    • Test readiness review
  7. A business analyst is working on a highly complex project and has elicited a large number of requirements from stakeholders in several departments. Due to the large number of requirements, the stakeholders have determined that they would like to prioritize them to minimize a potentially large scope.

    Which technique could the business analyst use to manage requirements?

    • Storyboarding
    • RACI models
    • SMART goals
    • MoSCoW
  8. One of the main purposes for creating a requirements traceability matrix is to:

    • track how requirements can be connected to the solution.
    • provide test cases to validate solution deliverables.
    • document stakeholder approval of project requirements.
    • track the project solution scope.



  9. A business analyst and stakeholders have completed documentation of the acceptance criteria for the requirements of a new vehicle leasing database. A concern is raised that some of the key performance indicators may not validate the desired benefits of the implementation.

    What should the business analyst do to ensure that the business need can be validated?

    • Document a constraint
    • Document a defect
    • Document an assumption
    • Document a business rule
  10. A business analyst is ready to begin requirements elicitation; however, stakeholders are not available to participate for another two weeks. Which elicitation technique should the business analyst use during this time?

    • Brainstorming
    • Benchmarking
    • Document analysis
    • Cost-benefit analysis
  11. To reduce the amount of time and effort needed to create a product specification for a project; the business analyst plans to reuse:

    • risk assessments.
    • qualitative analysis.
    • quantitative analysis.
    • requirements.
  12. Which document best provides the boundaries for product development?

    • Scope document
    • Project plan
    • Scope definition
    • Requirements baseline
  13. A business analyst in organization Y is assigned to elicit requirements in a project within a defined timeline. The business analyst has identified and invited key stakeholders to a requirements workshop. However, the stakeholders are not giving clear and concise requirements; their opinions about requirements are changing and conflicting with each other in the meeting. In the end, the business analyst could not elicit and define the requirements and therefore adjourned the meeting.

    Which tool or technique could have been used by business analyst to avoid this situation?

    • Prototyping
    • Document analysis
    • Decision tree
    • Surveys
  14. A business analyst from Company A has been assigned a project to document and identify requirements for a new commercial software implementation. The first step is to break down the business analysis deliverables into activities and tasks. Then, the business analyst will add an estimate of the time needed to complete the work.

    Which type of estimation technique is the business analyst using?

    • Analogous
    • Bottom-up
    • Delphi
    • Parametric
  15. 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?

    • Feature model
    • Use case
    • Prototype model
    • Context diagram
  16. A business analyst has elicited, documented, and verified the requirements, discovering that there are not enough resources to deliver all the requirements. Which technique should the business analyst employ to rectify the issue?

    • Hold a brainstorming workshop to build the rationale for the requirements.
    • Perform traceability to find out where the requirements originated.
    • Survey stakeholders on their likes and dislikes about the requirements.
    • Ask stakeholders to vote on the requirements.
  17. A project’s requirements baseline is established and approved. A stakeholder then submits a new requirement through the change control process.

    How can the business analyst determine the impact on existing requirements?

    • Use time-boxing to defer the new requirement.
    • Review the requirements traceability matrix.
    • Update the use case documentation.
    • Perform a stakeholder analysis
  18. Which tool should be used to improve the communication of product needs with the stakeholders and to improve their understanding?

    • Requirements management tool that documents requirements and their properties and relationships.
    • Workflow management tool that documents the flow of information
    • Document management system and a relationship matrix that groups all related documents
    • Modeling tool integrated into a version control feature that ensures that team knowledge is captured
  19. The sales team of a company has won a time-and-material project. The business analyst discovers that the sales team has underestimated the required budget and schedule.

    Which course of action should the business analyst take?

    • Accept the contract, and deliver only the requirements that fit within the budget and schedule
    • Develop a requirements baseline document and use it to negotiate the scope in the contract.
    • Refrain from working on the project and request that the customer cancel the contract.
    • Accept the contract, and then notify the customer about the potential for a cost overrun.
  20. A business analyst is trying to complete the requirement documentation of a project and finds that the developers have started development. The business analyst should first facilitate the:

    • requirements acceptance with the customer.
    • requirements gathering workshops with the stakeholders.
    • requirements validation with the testers.
    • requirements sign-off with the customer.