×

Quiz Session - Attempts With Random Questions

PMI-PBA Exam Questions

Page 5 of 25

81.

Which of the following is not a common technique for validating requirements?

  • Risk analysis

  • Walkthroughs and inspections

  • Prototyping

  • User acceptance testing

Correct answer: Risk analysis

Risk analysis is vital project planning work for business analysts, but it’s not a technique for directly validating requirements.

The following techniques are crucial in the requirement validation phase of business analysis planning:

  • Walkthroughs and inspections allow stakeholders to review requirements for accuracy and completeness.
  • Prototyping provides a tangible way to test and validate requirements.
  • User acceptance testing confirms that the solution meets the needs and expectations of the end users.

82.

You need to gather data on customer satisfaction levels tracked during the first quarter to quantify a business need. Which of the following techniques would be most effective?

  • Conduct a customer survey

  • Interview Subject-Matter ExpertS (SMES)

  • Analyze competitor data

  • Review historical records 

Correct answer: Conduct a customer survey

Gathering information directly from the targeted source (customers) will offer more valuable qualitative and quantitative feedback, which will result in impactful data that can better affect decision-making about proposed business solutions.

Interviewing Subject-Matter ExpertS (SMES), analyzing competitor data, and reviewing historical records will not provide the best data about customers that customer surveys will.  

83.

What should you avoid doing during a requirements elicitation interview?

  • Interrupting the stakeholder

  • Preparing a list of open-ended questions

  • Actively taking notes

  • Summarizing key points

Correct answer: Interrupting the stakeholder

Interrupting can disrupt the flow of conversation and make the stakeholder feel unheard. Business analysts should always focus on listening and understanding, reserving their opinions for later analysis and discussion.

Preparing a list of open-ended questions to guide the discussion is a good practice that helps ensure a structured and productive conversation.

Actively taking notes to capture important details and insights is crucial for documenting the requirements and ensuring accuracy.

Summarizing key points at the end of the interview to confirm understanding helps validate the business analyst’s understanding and identify any areas that need further clarification.

84.

You are eliciting requirements for a new customer relationship management system. Stakeholders have provided a list of high-level needs, but you need to break them down into more detailed and actionable requirements. 

Which technique would be most suitable for this?

  • Requirements decomposition

  • Dependency analysis

  • Interface analysis

  • Data modeling 

Correct answer: Requirements decomposition

Requirements decomposition involves breaking down high-level requirements into smaller, more manageable components. This helps ensure clarity and completeness and that each requirement is actionable for development.

Dependency analysis identifies relationships between requirements, not breaking them down into details.

Interface analysis defines how components interact, not the details of individual requirements.

Data modeling focuses on data structure, not decomposing requirements.

85.

You want to visually depict the interactions between different actors and the system being analyzed for a business solution. Which modeling technique is most appropriate?

  • Use case diagram

  • Data model

  • Decision table 

  • Goal model 

Correct answer: Use case diagram

Use case diagrams visually depict the interactions between users (actors) and the system's functionalities. They are a type of interaction matrix that provides a high-level overview of the system's behavior from the user's perspective.

Data models serve as visual representations of the structure and organization of information within a system.

Decision tables present conditions and associated actions, but they do not capture interactions between actors and the system.

Goal models describe the objectives a system is intended to achieve.

86.

Which of the following is not included in a business case document? 

  • Stakeholder register 

  • Situation statement

  • Product roadmap

  • Business goals and objectives 

Correct answer: Stakeholder register

A stakeholder register is not included in a business case document. Its purpose is to capture a list of stakeholders who are impacted and affected by the project or business initiative and to document their level of power and influence as it relates to the project work and outcomes.

Business case documents all include a situation statement to highlight the business problem or opportunity, a product roadmap that details the direction and plan for the production of the business solution, and a comprehensive list of business goals and objectives to frame the project work. 

87.

A team is using collaborative games to gather feedback on a proposed business solution. Which of the following is not a benefit of using this approach?

  • Faster decision-making due to reduced need for discussion

  • Increased stakeholder engagement and buy-in

  • Identification of hidden assumptions and potential issues

  • Generation of creative ideas and solutions

Correct answer: Faster decision-making due to reduced need for discussion

Collaborative games can make the feedback process more engaging; they often lead to more in-depth discussions and exploration of ideas, which might not necessarily result in faster decision-making.

Collaborative games often make stakeholders feel more involved and invested in the process, and this is beneficial for the project. 

The interactive nature of games can help uncover underlying assumptions that might not be apparent in traditional discussions.

The playful environment of games can encourage out-of-the-box thinking and innovative solutions.

88.

You are working on a project to improve the UX on a company's website. Which of the following metrics would be most relevant for measuring the success of this project?

  • Customer satisfaction rating

  • Average page load time 

  • Number of website visitors

  • Number of products sold

Correct answer: Customer satisfaction rating

Since the project focuses on improving UX, which is the user experience, the most relevant metric would be a measure of customer satisfaction, as it directly measures how customers perceive their experience with the website.

Average page load time is important, but it's not the most relevant metric for measuring customer experience.

Number of website visitors measures website traffic, but not necessarily satisfaction.

Number of products sold measures sales performance, but not necessarily customer experience.

89.

You are documenting the requirements for an automotive navigation business solution system. You need to capture the system’s essential functionalities. Which modeling technique would be most appropriate for representing these requirements?

  • Use case diagram

  • State diagram

  • Story mapping

  • System interface table

Correct answer: Use case diagram

Use case diagram is the best fit here because it is a modeling tool used in systems analysis and design to represent the functionality of a system from the perspective of its users. It provides a graphical overview of the interactions between users and the system and is particularly useful for capturing functional requirements.

A state diagram focuses on the different states the system can be in, which is not relevant to capturing functional requirements.

Story mapping is used to organize user stories, which is a more informal way of describing requirements.

A system interface table documents the interactions between different systems, not the core functionalities within the system.

90.

You're preparing to conduct a stakeholder analysis for a new business solution project. Which of the following is not an output of this work?

  • Work breakdown structure

  • Stakeholder engagement plan

  • Stakeholder list

  • Stakeholder map

Correct answer: Work breakdown structure

Work Breakdown Structure (WBS) is a project management tool used for decomposing the project scope into smaller, manageable tasks. It is a method for organizing and managing project work, not a result of stakeholder analysis.

A stakeholder engagement plan serves as a strategy guide that outlines the approach for effective communication and interaction with project stakeholders.

The stakeholder list serves as a complete record of all individuals who will potentially be impacted by or have a vested interest in the development and execution of a project.

A stakeholder map is a visual representation of the relationships among stakeholders and their respective levels of influence, power, or interest in a project.

91.

During requirements elicitation, which of the following should you do to ensure effective communication with stakeholders?

  • Actively listen to stakeholders

  • Use technical jargon and acronyms 

  • Speak primarily about the project's constraints and limitations

  • Focus on presenting solutions

Correct answer: Actively listen to stakeholders

Active listening and paraphrasing are essential for building rapport, clarifying expectations, and ensuring that business analysts accurately capture the stakeholders' needs.

Using technical jargon and acronyms can alienate and confuse stakeholders who may not be familiar with technical terms.

When eliciting requirement needs from stakeholders, the emphasis should primarily be on grasping their requirements and goals from the onset. It is crucial to address project restrictions and limitations, but the initial focus should be on understanding their perspectives.

DIscussions about solutions should come after a thorough understanding of the problem and requirements.

92.

Which of the following is an input to the process of establishing relationships and dependencies between requirements?

  • Requirements documentation

  • Approved change request

  • Project scope statement

  • Stakeholder feedback

Correct answer: Requirements documentation

Understanding individual requirements and their potential interrelationships or dependencies is contingent on the availability of comprehensive requirements documentation.

Approved change requests are outcomes of the change management process, not inputs to establishing dependencies.

The project scope statement defines the boundaries of the project, but doesn't detail the specifics of requirement relationships.

Stakeholder input can reveal possible interconnections, but business analysts require concrete requirements to formalize these dependencies.

93.

You are using the analytical hierarchy process to prioritize project requirements. Which step in this process involves equating requirements to determine their relative importance?

  • Developing pairwise comparison matrices

  • Establishing priorities

  • Synthesizing results

  • Performing sensitivity analysis 

Correct answer: Developing pairwise comparison matrices

In the analytical hierarchy process, pairwise comparison matrices are created to compare each requirement against every other requirement, assigning a numerical value to their relative importance.

Establishing priorities is the overall goal of the analytical hierarchy process.

Synthesizing results is done after creating the matrices.

Sensitivity analysis is done to check the robustness of the results.

94.

Which of the following tools is primarily used to capture and prioritize stakeholder needs and expectations in a structured format?

  • Kano model 

  • Requirements traceability matrix

  • Use case diagram

  • Context diagram

Correct answer: Kano model 

The Kano model categorizes customer needs into different types (basic, performance, excitement) to help prioritize features and determine their impact on customer satisfaction.

The requirements traceability matrix serves as a valuable tool for mapping and monitoring the connections between requirements and related artifacts throughout the development process.

Use case diagrams are used to visualize user interactions with a system.

Context diagrams define the boundaries of a system and its interactions with external entities.

95.

A project is following an Agile methodology with frequent iterations and rapidly changing requirements. How should you adapt the communication approach to keep stakeholders informed effectively?

  • Utilize a Kanban board

  • Send daily email updates 

  • Schedule weekly status meetings 

  • Create a comprehensive requirements document 

Correct answer: Utilize a Kanban board

A Kanban board provides transparency and allows stakeholders to easily track progress and identify potential bottlenecks.

Daily emails can be overwhelming and might not provide the necessary context.

Weekly meetings might not be frequent enough to address the dynamic nature of Agile projects.

A comprehensive document might not be the most efficient way to communicate real-time progress in an Agile environment.

96.

You are advising a project team working to implement a call center business solution. You need to understand the current operations of the client to identify areas for improvement. Which of the following tools would be most effective in garnering this information?

  • Process flows

  • Personas

  • User stories

  • Estimation techniques

Correct answer: Process flows

Process flows, which are diagrammatic representations of steps and decision points in a process, are invaluable for comprehending intricate processes, such as those encountered in a call center environment.

Personas represent user groups, not process steps.

User stories describe desired functionality from a user's perspective.

Estimation techniques are used for predicting project duration or cost.

97.

A requirement has been moved to be included in a later phase of the project. What should you do to ensure proper traceability?

  • Update the status of the requirement in the traceability matrix to Deferred

  • Remove the requirement from the traceability matrix

  • Notify stakeholder that the requirement is no longer relevant

  • Create a new requirement for the latter phase and link it to the original requirement 

Correct answer: Update the status of the requirement in the traceability matrix to Deferred

Maintaining a record of the decision to defer a requirement in the traceability matrix by updating its status to Deferred ensures clarity and facilitates future tracking when the requirement is reconsidered.

Eliminating the requirement would result in the loss of critical information, potentially leading to future misunderstandings and complications.

Updating the traceability matrix to Deferred should be prioritized first over notifying stakeholders. However, stakeholders should still be notified in addition to updating the matrix.

Creating a new requirement might be necessary if the requirement is significantly modified for the latter phase, but the original requirement should still be updated as Deferred.

98.

You are leading a project to develop a new mobile app. Due to budget constraints, you can only include a limited number of features in the initial release. How would you determine which features to prioritize?

  • Prioritize features based on their alignment with the project's business goals and objectives

  • Consult with the development team to see which features are easiest to implement

  • Conduct a survey of potential users to gauge their interest in different features

  • Randomly select features to avoid bias

Correct answer: Prioritize features based on their alignment with the project's business goals and objectives

Prioritizing based on business goals ensures that the features that deliver the most value to the business and stakeholders are developed first.

Ease of implementation should not be the primary driver for prioritization.

User surveys can be helpful, but the final decision should align with business objectives.

Random selection does not ensure the most valuable features are prioritized.

99.

You are monitoring requirements throughout their lifecycle. Which of the following activities is not part of this monitoring process?

  • Eliciting new requirements from stakeholders

  • Reviewing and approving requirements artifacts

  • Updating the status of requirements in the traceability matrix

  • Communicating requirement changes to stakeholders

Correct answer: Eliciting new requirements from stakeholders

Eliciting new requirements typically occurs during the initial requirements gathering phase rather than as an ongoing monitoring activity.

Reviewing and approving ensures that artifacts meet the requirements.

Updating the status of requirements in the traceability matrix keeps track of the progress and state of each requirement.

Communicating requirement changes informs stakeholders of any modifications or updates.

100.

Which of the following is not common practice for accepting a solution?

  • Achievement of the projected Return On Investment (ROI)

  • Successful completion of User Acceptance Testing (UAT)

  • Approval of the solution's technical design by the IT department

  • Verification that the solution meets the defined business requirements

Correct answer: Achievement of the projected Return On Investment (ROI)

Return On Investment (ROI) is a critical metric, but it usually can only be evaluated after a solution has been deployed and is operational rather than before its release.

User Acceptance Testing (UAT) is a crucial step in verifying that the solution meets user needs.

Technical approval is necessary to ensure the solution's technical feasibility.

Meeting business requirements is the core objective of any solution.

×