Last Updated on March 19, 2022 by Admin 2

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

  1. The business analyst has completed the requirements gathering and documentation processes in developing a baseline document. Several signoffs are needed. During the joint review process with the key stakeholders, the stakeholders announce that they are still not ready to sign off due to a communication gap.

    Which technique should the business analyst have followed to ensure consensus?

    • The business analyst should have invited the key stakeholders to the meeting.
    • The business analyst should have reviewed the requirements of the project sponsor first before reviewing other requirements.
    • The business analyst should have performed a complete review of each requirement with the key stakeholders prior to the meeting.
    • The business analyst should have performed a complete review of each requirement with one of the stakeholders’ peers before the meeting.
  2. For a large, highly complex project with significant risk, which elicitation technique should be used to analyze input to and output from the product?

    • Interface analysis
    • Risk analysis
    • System analysis
    • Dependency analysis
  3. A project team has been assembled to reduce production costs. The business analyst is working with the project team to review and approve requirements. A stakeholder from the assembly line area has an issue with one of the requirements since it is dependent on using existing equipment that is set to be retired within the next six months.

    Which of these techniques would the business analyst use to manage issues identified by stakeholders with requirements to ensure that those issues are resolved?

    • Interviews
    • Problem tracking
    • Process modeling
    • Estimation



  4. A business analyst is documenting the acceptance criteria to support a minor modification in a user portal. The analyst submits the criteria for review, but it is deemed incomplete and returned.

    What could have caused the documentation to be returned?

    • The analyst did not include the scope document in the acceptance criteria paperwork.
    • The analyst utilized user stories as a requirements document tool.
    • The analyst failed to gather any baseline information.
    • The analyst performed forward and backwards traceability.
  5. A business analyst is preparing a requirements management plan and needs to define a method to deal with a complex project with stakeholders who find it difficult to articulate their needs. Which method would best minimize requirements risk?

    • Prototyping
    • Stakeholder analysis
    • Group decision making
    • Questionnaires
  6. In the first few weeks after a large implementation of a new web-based application, a critical report failed. Further investigation determined that a worker had been using a field that was not supposed to be used. This issue was not identified in testing.

    Which technique could have prevented this problem from occurring?

    • Prototyping
    • Use cases
    • Document analysis
    • Diagrams
  7. Requirements for a project have already been approved and finalized when a stakeholder approaches the project team with a change to one of their requirements. Which method of document control should the business analyst use to document changes in requirement(s) versioning?

    • Project plan
    • Statement of work
    • Traceability matrix
    • Problem or opportunity statement
  8. A company has launched a new online sales application and engaged a focus group to test how quickly the customer could place an order. The focus group also provided feedback on their satisfaction.

    Which metrics tool should the business analyst use to record the results?

    • Focus group
    • Business completion
    • Customer
    • Sales and marketing
  9. A business analyst has been assigned to a project team that is redesigning the company’s website. The business analyst has been documenting the relationships between requirements and has found requirements that do not trace to a business need.

    Which type of requirements are these?

    • Tested
    • Out-of-scope
    • Implemented
    • In-scope
  10. A project team has completed the system use cases along with accompanying screen mockups. The business analyst schedules a review meeting with the client team to walk through the artifacts.

    What is the purpose of this meeting?

    • To validate that the system is aligned with the stakeholder requirements
    • To verify that the documents are aligned with the transition requirements
    • To validate that the documents are aligned with the solution requirements
    • To verify that the system is aligned with the quality requirements
  11. After reviewing a business case, project goals, and objectives, a business analyst determines that the organization prefers taking an exploratory approach to finding the solution that best meets the business need. Which approach best aligns with the business need for this organization?

    • Change-driven approach
    • Analytical approach
    • Waterfall approach
    • Plan-driven approach
  12. The business analyst is planning an approach to formally manage updates to requirements that may be requested by stakeholders. What should the business analyst do?

    • Document changes as they occur.
    • Obtain approval from the project sponsor.
    • Develop a change control process.
    • Hold firm on scope and reject changes.
  13. After completing the requirements, the project manager and business analyst realize that the project scope is not feasible in the projected schedule. The business analyst needs to review the amount of work the team is capable of delivering based on the approved project schedule.

    Which prioritization technique should the business analyst use?

    • Multivoting
    • Time-boxing
    • Weighted ranking
    • SWOT analysis
    Reference: (323)
  14. A new project is in the planning phase. The business owner believes that, since the timeline is aggressive, requirements elicitation should begin as soon as possible.

    Which activity should the business analyst initiate before beginning requirements elicitation?

    • Draft a high-level data model.
    • Prepare the requirements traceability matrix.
    • Document how the relevant systems interact.
    • Define how the solution will be evaluated.
  15. A business analyst needs to estimate the effort associated with project requirements. However, the lack of detail is concerning.

    What technique could the business analyst use to help alleviate this concern?

    • Decomposition model
    • Swimlane diagram
    • Business analysis work plan
    • Context diagram
  16. Change control systems include provisions to implement changes without formal review in the event of an emergency. When the provision is utilized:

    • changes must still be documented and captured.
    • the risk associated with the change is not evaluated.
    • a change control board should be established.
    • changes can be applied without further managerial involvement.
  17. A business analyst conducts an initial review to define scope. The analysis includes the review of the business case, project goals, and objectives to obtain the necessary and required context. Based on that information, the business analyst determines that this is a large project with multiple interfaces which could cost the company money that was not initially included in the budget.

    What characteristics of the project are needed to determine the approach so that the business analyst can validate whether they will need to have a discussion about the budget?

    • Selected project life cycle
    • Business analysis deliverables to be produced
    • Type of elicitation activities to be conducted
    • Decision on the type of models to be used
  18. The project team is early in the development phase of a new product. The project will need to be completed on a tight timeline and with a lean budget.

    What should the team do to reduce the risk of rework?

    • Organize a new elicitation workshop.
    • Perform a Pareto analysis on the requirements.
    • Validate the requirements before continuing with development.
    • Ask the project sponsor to prioritize the requirements.
  19. A company is developing a new product for a customer and is required to verify and validate the product against the customer’s acceptance test plan and requirements. The product was successfully verified against 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 formally accepted by the company.
    • was incomplete and missing requirements.
    • did not have measurable and testable requirements.
    • was not included in the work breakdown structure.
  20. A project team has 120 days to deliver a solution, but the stakeholders have too many requirements for the delivery window. What requirements prioritization technique should be used to determine which requirements will be delivered?

    • Multivoting
    • MoSCoW
    • Time-boxing
    • Budget analysis