×

Quiz Session - Attempts With Random Questions

PMI-PBA Exam Questions

Page 10 of 25

181.

Which of the following is an example of a business metric?

  • User satisfaction rating of new ticketing system 

  • Number of defects found during testing 

  • Completion date of a specific deliverable

  • Budget variance for the project

Correct answer: User satisfaction rating of new ticketing system  

User satisfaction ratings serve as a significant business metric to assess the overall success of any solution implementation in meeting the user's requirements.

The number of defects found during testing is a quality metric, not a business metric.

The completion date of a specific deliverable is a project schedule metric, not a business metric.

The budget variance is a financial metric, not a business metric.

182.

During a monthly meeting, a project sponsor expresses a strong desire for the new software system of a business solution project to be able to integrate with the company's existing Customer Relationship Management (CRM) system. How should you classify this information?

  • Stakeholder requirement 

  • Functional requirement

  • Nonfunctional requirement

  • Technical requirements

Correct answer: Stakeholder requirement

Stakeholder requirements are the needs or expectations of stakeholders regarding the product or project. The project sponsor's desire for integration with the existing Customer Relationship Management (CRM) system is a specific need they have expressed, thus making it a stakeholder requirement.

Functional requirements define what a system should do (e.g., calculate sales tax).

Nonfunctional requirements define how a system should perform (e.g., be secure).

Technical requirements specify the technical aspects of a solution (e.g., use a specific programming language).

183.

You are conducting interviews with stakeholders to gather requirements. Which of the following is not a recommended interviewing tactic?

  • Focusing solely on technical details and solutions

  • Asking open-ended questions

  • Actively listening to the stakeholder's responses

  • Summarizing stakeholder preferences

Correct answer: Focusing solely on technical details and solutions

The focus during needs assessment interviews should primarily be on understanding business problems and needs, not to solely hone in on technical solutions.

Open-ended questions are vital for encouraging stakeholders to share their thoughts and perspectives.

Active listening showcases respect and helps to ensure an accurate understanding of the stakeholder's preferences.

Summarizing and confirming ensures that the business analyst has correctly captured the stakeholder's thoughts, ideas, and recommendations.

184.

During a requirements elicitation session, stakeholders express conflicting views on the priority of different features for a new software application. What is the best approach to resolve this conflict and reach a consensus?

  • Facilitate a discussion among stakeholders to understand their reasoning and explore compromises

  • Make the decision yourself based on your expertise and understanding of the requirements

  • Ask the project manager to decide which feature should be prioritized

  • Postpone decision until later in the project or when more information is available 

Correct answer: Facilitate a discussion among stakeholders to understand their reasoning and explore compromises

The best approach to resolving conflicting stakeholder views is to facilitate a discussion where everyone can express their perspectives and concerns. By understanding the reasoning behind their priorities, you can explore potential compromises and solutions to reach a consensus that satisfies the needs of the project and the stakeholders.

Making the decision yourself might alienate stakeholders and lead to resentment.

The project manager has authority, but the decision should ideally be made collaboratively.

Delaying the decision might cause project delays and increase the risk of scope creep.

185.

Which process can be used to evaluate whether a business solution is viable?

  • Feasibility analysis

  • Focus groups

  • Retrospective ceremonies

  • Business analysis stewardship

Correct answer: Feasibility analysis 

Feasibility analysis is the practice of weighing the legal, technical, economic, and operational viability of projects or business solutions. Results, findings, and insights help work teams make informed decisions about whether to approve workable solutions or delay or reject initiatives that pose too much risk without enough Return Of Investment (ROI).

Focus groups are used to collect qualitative information and data that can help project planning teams. 

Retrospective ceremonies are held at the end of project sprints to review lessons learned that can be used in future project roll-outs.

Business analysis stewardship is the practice of ensuring all activities conducted during business analysis are done ethically and effectively.

186.

During a requirements validation session, a stakeholder suggests that a particular requirement might be unnecessary and could be removed without impacting the overall project goals. What is the best way to proceed?

  • Facilitate a discussion to understand the stakeholder's reasoning and assess the impact 

  • Remove the requirement immediately, as stakeholder input is always valuable

  • Insist on keeping the requirement, as it was included in the initial analysis phase

  • Escalate the issue to the project manager for a final decision

Correct answer: Facilitate a discussion to understand the stakeholder's reasoning and assess the impact

It's important to explore the stakeholder's concerns and understand why they believe the requirement is unnecessary. By assessing the potential impact of removing the requirement on the project scope, you can make an informed decision that considers all perspectives.

Removing a requirement without analysis can lead to missing critical functionality.

Insisting on keeping the requirement without discussion can hinder collaboration and potentially lead to a suboptimal solution.

Escalation may be necessary if no agreement is reached, but collaborative problem-solving should be attempted first.

187.

During a sprint retrospective, the development team raised concerns about the lack of clarity in a specific requirement. What should you do next?

  • Collaborate with the product owner to clarify the requirement

  • Update the requirement in the traceability matrix

  • Conduct a root cause analysis to determine the origin of the ambiguity

  • Create a change request to modify the requirement

Correct answer: Collaborate with the product owner to clarify the requirement

Since product owners are responsible for defining and clarifying requirements, it’s important for business analysts to provide support and collaborative efforts to ensure requirements are defined accurately prior to implementation.  

Updates to the traceability matrix are done after requirements are clarified.

Conducting a root cause analysis might be helpful later to understand why the ambiguity occurred, but the immediate priority is clarification.

Creating a change request is unnecessary if the clarification can be provided without a formal change.

188.

Which of the following is not a market force factor?

  • Customer preferences

  • Competitive landscape

  • Supply and demand dynamics

  • Economic conditions 

Correct answer: Customer preferences

Consumer preferences are not usually considered market force factors. While they do influence demand within a market, consumer preferences do not equate to the broader factors that can affect the market in a more impactful way.

Market forces encompass all the dynamics that affect, influence, and spark supply and demand, including pricing, competitive factors, regulatory practices, and other behavioral activities within the marketplace.

189.

You're allocating requirements to project phases. Which of the following factors is least important when deciding which requirements to implement early in the project?

  • Number of requirement changes

  • Stakeholder value

  • Technical dependency

  • Risk mitigation

Correct answer: Number of requirement changes

While change is expected, the frequency of changes to a requirement isn't a primary factor in determining its implementation priority.

High-value requirements identified by stakeholders should be prioritized.

Requirements that other features depend on must be done early.

Addressing risky requirements early reduces overall project risk.

190.

Your team has just completed a series of facilitated workshops and interviews to gather stakeholder needs for a new software platform. You've documented these needs in a comprehensive requirements document. 

What is the most crucial next step before proceeding with design and development?

  • Obtain formal approval of the requirements document from key stakeholders

  • Conduct a peer review of the requirements document to check for technical accuracy

  • Develop a project schedule to estimate the timeline for implementing the requirements

  • Create wireframes and mockups to visualize the user interface of the new platform

Correct answer: Obtain formal approval of the requirements document from key stakeholders

Obtaining formal approval (sign-off) on the requirements baseline is essential before proceeding with development. This ensures that all stakeholders have reviewed and agreed upon the documented requirements, reducing the risk of misunderstandings or changes later in the project.

Peer review is important for quality assurance, but it happens before seeking stakeholder approval.

Project scheduling is important, but it should be based on the approved requirements.

Wireframes and mockups are part of the design phase, which should start after requirements are approved.

191.

​​Midway through a project, a key stakeholder requests a change that fundamentally alters the product's core functionality. The change is beneficial but would require significant rework. What is your first course of action?

  • Evaluate the impact of the change on the project; then communicate your findings to the stakeholder and project manager

  • Immediately inform the stakeholder that the change is too invasive and cannot be accommodated at this stage of the project

  • Propose alternative solutions that address the stakeholders without requiring a major overhaul of the product

  • Gather the project team to brainstorm potential solutions, and assess the feasibility of a requested change

Correct answer: Evaluate the impact of the change on the project; then communicate your findings to the stakeholder and project manager

Evaluating the impact of the change on the project's timeline, budget, and scope involves a proactive and analytical approach that seeks to understand the potential consequences of proposed changes before implementing them. This is crucial because it provides valuable insights and information that helps guide decision-makers toward the best course of action.

Informing the stakeholder that the change is too invasive is dismissive and doesn't consider potential solutions or compromises.

Suggesting alternative solutions without first evaluating their potential impact is premature and could lead to project complications

Brainstorming is useful but should be done after the initial impact assessment.

192.

Your team is developing a new financial reporting system for a large organization. The stakeholders have provided a set of high-level requirements, but you need to have more granular, actionable tasks for the development team. 

Which technique would be most appropriate for achieving this?

  • Work Breakdown Structure (WBS)

  • Interface analysis

  • Data dictionary

  • Risk analysis

Correct answer: Work Breakdown Structure (WBS)

A Work Breakdown Structure (WBS) is a hierarchical decomposition of the project scope into smaller, more manageable components. In this scenario, it would be used to break down the high-level requirements into specific tasks or deliverables that can be assigned to the development team. This helps ensure that all requirements are addressed and provides a clear roadmap for the project.

Interface analysis focuses on how different system components interact, not on decomposing requirements into tasks.

Data dictionaries define data elements and their relationships but not the tasks required to implement the requirements.

Risk analysis identifies and assesses risks but doesn't directly decompose requirements into actionable tasks.

193.

Which of the following techniques is used to ensure that the solution aligns with the original business needs and objectives?

  • Solution evaluation

  • Requirements elicitation

  • Stakeholder analysis

  • Risk assessment

Correct answer: Solution evaluation

The process of assessing a proposed or implemented solution is known as solution evaluation. This systematic assessment is carried out to determine whether the solution meets the business objectives and needs that were defined at the start of the project.

Requirements elicitation entails collecting requirements from various stakeholders, which is a crucial step in business solution development.

Analyzing stakeholders involves pinpointing and examining their requirements and preferences.

Risk assessment identifies and evaluates potential risks to the project.

194.

You have created a survey consisting of 25 questions for a new project that has just been approved by the project sponsor. What is the purpose of your work? 

  • Gather stakeholder feedback

  • Competitor analysis

  • Assess team performance

  • Create project schedules

Correct answer: Gather stakeholder feedback

Business analysts use surveys to poll and gather stakeholder responses regarding project process preferences and product or business solution requirements.  

Competitor analysis is incorrect because competitors aren’t stakeholders.

Surveys aren’t used to assess team performance or create project schedules. 

195.

What is the purpose of a requirement management tool in the context of requirements specification?

  • To store, organize, and track changes to requirements throughout the project lifecycle

  • Generate code automatically based on requirements

  • Create visual models of the system architecture

  • Facilitate communication between the business and the development team

Correct answer: To store, organize, and track changes to requirements throughout the project lifecycle

Requirement management tools, such as the traceability matrix, are used to link and track requirements throughout the project lifecycle and provide a central repository for storing requirements, tracking changes, managing versions, and establishing traceability.

Some advanced tools might have limited code generation capabilities, but this is not the primary purpose of requirement management tools. Their main focus is on documenting, organizing, and managing requirements, not generating code directly.

Visual modeling is often a separate activity, typically done using specialized modeling tools (e.g. UML tools). Some requirement management tools may have basic modeling features, but their main purpose is not to create complex system architecture models.

Requirement management tools can help with communication by providing a shared repository of information, but their primary purpose is broader than just facilitating communication. They serve to manage the entire lifecycle of requirements, including traceability, version control, and impact analysis.

196.

You are working on a project to develop a new online learning platform. The stakeholders have provided a vast number of requirements, including user stories, feature requests, and technical specifications. 

What is the best way to organize these requirements to ensure that the most important features are delivered first?

  • Use a prioritization matrix to rank the requirements based on their business value, urgency, and feasibility

  • Create a comprehensive spreadsheet listing all requirements and sort them alphabetically

  • Start developing the features that seem easiest to implement

  • Randomly select a set of requirements and start working

Correct answer: Use a prioritization matrix to rank the requirements based on their business value, urgency, and feasibility

A prioritization matrix is a valuable tool for organizing and prioritizing requirements. It allows you to systematically evaluate each requirement based on multiple criteria, such as business value, urgency, and feasibility. This ensures that the most important and valuable features are developed first, maximizing the return on investment for the project.

Sorting requirements alphabetically doesn't help prioritize them based on their importance or value.

Starting with the easiest features might not align with the overall business goals and priorities.

Randomly selecting requirements can lead to a disorganized development process and potentially miss critical features.

197.

A project is using a distributed team with members working in different time zones and cultures. How do you ensure effective communication of requirements status across this diverse team?

  • Establish a comprehensive communication plan

  • Rely on email as the primary communication channel

  • Assume everyone understands the requirements and project goals

  • Communicate with the project manager, who is responsible for cascading information to the rest of the team

Correct answer: Establish a comprehensive communication plan

A well-defined communication plan tailored to the team's specific needs and diversity ensures that everyone is informed, engaged, and working toward the same goals.

Email communication is useful, but it's not the only or most effective way to communicate in a distributed team.

Assuming shared understanding can lead to misunderstandings and misaligned deliverables.

The project manager plays a crucial role, but the business analyst should also communicate directly with team members to ensure clarity and alignment.

198.

You're working on a project with a fixed budget and a tight deadline. Which prioritization model would be most suitable to maximize the value delivered within these constraints?

  • Cost of delay

  • Timeboxing

  • Value versus risk

  • Kano model 

Correct answer: Cost of delay

The cost of delay model focuses on prioritizing features based on the economic impact of delaying their implementation. This helps maximize value delivery within time and budget constraints.

Timeboxing sets a fixed timeframe for each task but doesn't inherently prioritize based on value.

Value versus risk prioritizes based on the combination of value and risk, not necessarily on budget constraints.

The Kano model categorizes features into different types but doesn't directly address budget and time constraints.

199.

You are the lead business analyst for a new gaming app project that is using an Agile methodology, and the requirements are advancing swiftly. You need to ensure that the documentation of the requirements is accurately controlled and traceable. 

Which following method would you use to manage the different versions of requirements documents to ensure that changes are tracked and approved appropriately throughout the project?

  • Document control

  • Rolling wave planning

  • Collaboration point

  • Story mapping

Correct answer: Document control

To ensure that the right people have access to the correct version of a document, document control serves as a means of supervising the creation, review, approval, and distribution of project documents. It also helps to track document approval and changes.

Rolling wave planning emphasizes ongoing, iterative planning rather than static document management.

The collaboration point is intended to provide a dedicated environment or time frame for stakeholders to interact and exchange ideas rather than serving as a tool for managing documents.

Story mapping focuses on visualizing and understanding user journeys and the features associated with them rather than on managing different versions of a document.

200.

You're nearing the completion of the planning phase, but stakeholders are still presenting new requirements for the business solution. How do you prevent scope creep and ensure the project stays on track?

  • Evaluate each new requirement against the project's objectives and constraints

  • Refuse to consider any new requirements at this stage without assessment

  • Quickly incorporate all new requirements without assessing their impact

  • Defer all new requirements to a future phase of the project

Correct answer: Evaluate each new requirement against the project's objectives and constraints

New requirements should be evaluated against the project's objectives and constraints and assessed for their value, feasibility, and impact on the project timeline and budget before being incorporated to prevent project delays and cost overages.

Refusing to consider any new requirements without assessing them can be counterproductive. It can alienate stakeholders and make them feel unheard. Some new requirements might be valid and essential for project success.

Uncontrolled scope creep is a common project management issue caused by introducing new requirements without considering their implications. Evaluating the impact of new requirements on the project's timeline, resources, and objectives before incorporating them ensures the project remains aligned with its goals and that changes are managed effectively.

Postponing new requirements to a later project phase poses risks. Certain requirements may be crucial for the current phase, and their delay could adversely affect the project's overall success. It is essential to assess each requirement individually and prioritize accordingly.

×