PMI-PBA試験問題集合格させるのは2025年最新の認証済み試験問題
PMI-PBA試験問題でリアルに更新された問題PDF
質問 # 116
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?
- A. Obtain approval from the project sponsor.
- B. Develop a change control process.
- C. Hold firm on scope and reject changes.
- D. Document changes as they occur.
正解：B
解説：
A change control process is a set of procedures that defines how changes to the requirements are identified, assessed, approved, implemented, and communicated. A change control process helps to ensure that changes are aligned with the business objectives, do not introduce unnecessary risks, and do not adversely affect the quality of the solution. A change control process also helps to manage stakeholder expectations and avoid scope creep. References: PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline1, page 13; Business Analysis for Practitioners: A Practice Guide2, page 77.
質問 # 117
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?
- A. Define how the solution will be evaluated.
- B. Prepare the requirements traceability matrix.
- C. Draft a high-level data model.
- D. Document how the relevant systems interact.
正解：D
解説：
Explanation
Before beginning requirements elicitation, the business analyst should document how the relevant systems interact. This is an important activity that helps to understand the current state of the systems, their interfaces, dependencies, and data flows. It also helps to identify the gaps, issues, and opportunities for improvement in the systems. Documenting how the systems interact can be done using various techniques, such as system context diagrams, data flow diagrams, or interface analysis12.
Preparing the requirements traceability matrix, defining how the solution will be evaluated, and drafting a high-level data model are not activities that should be initiated before beginning requirements elicitation. These activities are part of the analysis, validation, and management of the requirements, and they should be done after the requirements have been elicited12.
References: 1 PMI Professional in Business Analysis (PMI-PBA)
Examination Content Outline, page
10-11; 2 Business Analysis for Practitioners: A Practice Guide, page 131-132
質問 # 118
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?
- A. Document analysis
- B. Use cases
- C. Diagrams
- D. Prototyping
正解：B
質問 # 119
A company is working on the next big release of their best-selling product. The requirements will be validated through in-person validation sessions.
What would be the most viable technique to use in this scenario?
- A. A brainstorming session
- B. A review of the solution prototype
- C. A review of the previous version
- D. A use-case development session
正解：B
解説：
A review of the solution prototype would be the most viable technique to use in this scenario for validating requirements through in-person sessions. A solution prototype is a simplified version of part or all of a solution that can be used to elicit feedback from stakeholders. A review of a solution prototype involves presenting or demonstrating it to stakeholders and asking them questions to assess their satisfaction, understanding, agreement, or concerns. A review of a solution prototype can help to validate that the solution meets the stakeholder requirements and delivers value to them. A brainstorming session is a technique for generating ideas or solutions by encouraging free and creative thinking from participants. A brainstorming session can help to elicit or analyze requirements but not validate them. A use-case development session is a technique for creating use cases that describe how actors interact with a system to achieve their goals. A use- case development session can help to elicit or specify requirements but not validate them. A review of the previous version is a technique for examining an existing solution or product to identify its strengths, weaknesses, opportunities, or threats. A review of the previous version can help to elicit or analyze requirements but not validate them. References: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 13; Business Analysis for Practitioners: A Practice Guide2, page 76.
質問 # 120
The project team has all the document control process and versioning in place to capture the requirements changes. The team ensures that the change is documented in the scope document, resulting in the changed work breakdown structure (WBS) and schedule. However, a key requirement was not implemented in the release.
Which is a possible reason why the requirement was not implemented?
- A. The requirements traceability matrix was not updated with the change.
- B. The requirements management plan was not updated with the change.
- C. The scope management plan was not updated with the change.
- D. The schedule management plan was not updated with the change.
正解：C
質問 # 121
The project manager is beginning to prepare for a test readiness review with the customer. The project manager knows that the customer will want a summary of requirements that have been rejected or deferred.
The project manager has requested that the business analyst provide a list of rejected and deferred requirements.
What should the business analyst have done to complete this request?
- A. Spend more time up-front reviewing the requirements to limit rejections.
- B. Track rejected requirements in the system requirements verification matrix.
- C. A Set up a change control board to track the number of rejections.
- D. Limit the number of rejected requirements on the project.
正解：B
解説：
The system requirements verification matrix is a tool that helps to track the status of each requirement throughout the project lifecycle. It shows whether a requirement has been accepted, rejected, deferred, or implemented. The business analyst should have used this tool to record the reasons for rejection or deferral of any requirement, as well as the impact and resolution of such changes. This way, the business analyst can easily provide a list of rejected and deferred requirements to the project manager upon request. Setting up a change control board is not enough to track the number of rejections, as it does not provide a detailed record of each requirement's status. Limiting the number of rejected requirements on the project is not a realistic or helpful approach, as some requirements may be invalid, incomplete, or conflicting and need to be rejected or deferred for the benefit of the project. Spending more time up-front reviewing the requirements may reduce the chances of rejections, but it does not guarantee that no requirement will be rejected or deferred later in the project. References: Business Analysis for Practitioners: A Practice Guide, page 161-162; PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline, page 19.
質問 # 122
Several interviews with stakeholders to develop an inventory management system in a new architectural environment have revealed a significant concern about system and architectural stability. In which tool should the business analyst include this attribute to ensure that the requirement meets the acceptance criteria?
- A. Stakeholder satisfaction survey
- B. Interface analysis
- C. Traceability matrix
- D. Process modeling
正解：C
質問 # 123
How can a business analyst show progressive iterations of product development to stakeholders after the requirements baseline has been approved?
- A. Review performance data with the project sponsor.
- B. Talk to distinct testing groups to check testing status.
- C. Conduct requirement walkthrough sessions.
- D. Create prototype proof-of-concept models.
正解：D
解説：
Explanation
According to the PMI Professional in Business Analysis objectives and content, a prototype is a tool that can be used to demonstrate the features and functionality of a product or solution in an iterative manner. A prototype can help to elicit, validate, and verify requirements, as well as to obtain feedback and approval from stakeholders. A prototype can also help to reduce risks, errors, and rework, and to increase customer satisfaction and quality. A proof-of-concept model is a type of prototype that is used to test the feasibility and viability of a product or solution. A proof-of-concept model can help to show the benefits and value of the product or solution, and to identify any technical or business challenges or constraints. References:
PMI Professional in Business Analysis objectives and content: PMI-PBA Certification PMI Professional in Business Analysis reference list: PBA Reference List PMI Professional in Business Analysis study guide: Study.com
質問 # 124
A business analyst is attempting to elicit requirements on a current project. The business subject matter experts (SMEs) from various departments in the company question how the solution will work with their various systems. Which modeling technique should the business analyst use to depict how the solution will work with all of the company's systems?
- A. Interface modeling
- B. Enterprise modeling
- C. Data modeling
- D. Rules modeling
正解：A
解説：
Explanation
Interface modeling is a technique to describe how different components or systems interact with each other and exchange information. Interface modeling can be used to depict how the solution will work with all of the company's systems by showing the inputs, outputs, and dependencies of each system. Interface modeling can help to identify potential integration issues, gaps, and conflicts among the systems. The other techniques are not suitable for this purpose. Data modeling is a technique to define the structure, format, and relationships of data. Rules modeling is a technique to define the logic, constraints, and policies that govern the behavior of the solution. Enterprise modeling is a technique to describe the structure, culture, and processes of an organization. References: PMI-PBA
Examination Content Outline, page 11; PMI-PBA
Reference List,
page 1, BABOK
Guide v3, page 54.
質問 # 125
An organization is in the process of replacing its current system. The business analyst is charged with ensuring that all current connections to other systems remain functional after the upgrade.
What analysis should the business analyst conduct to facilitate a successful migration?
- A. Systems
- B. Document
- C. Interface
- D. User interface
正解：A
解説：
Explanation/Reference:
質問 # 126
A new project's goal is to replace an existing system. What is an input into solution evaluation and decision making in this context?
- A. Technical readiness of the development team
- B. Customer metrics on the existing system
- C. Cost-benefit analysis of the existing system
- D. New solution design specification
正解：C
質問 # 127
To reduce the amount of time and effort needed to create a product specification for a project, the business analyst plans to reuse:
- A. requirements.
- B. risk assessments.
- C. quantitative analysis.
- D. qualitative analysis.
正解：A
解説：
To reduce the amount of time and effort needed to create a product specification for a project, the business analyst plans to reuse requirements. Requirements are statements that describe the needs, expectations, or capabilities of the stakeholders or the solution. Requirements can be reused from previous or similar projects, as long as they are relevant, consistent, and compatible with the current project context and objectives.
Reusing requirements can help to save time and effort, avoid duplication or redundancy, leverage best practices, and ensure quality and compliance. Quantitative analysis is not something that the business analyst plans to reuse to reduce the amount of time and effort needed to create a product specification for a project.
Quantitative analysis is a technique that involves using numerical data and methods to measure, compare, or evaluate the feasibility, value, or impact of a solution or an alternative. Quantitative analysis can be performed for different purposes and at different stages of the project, but it does not provide requirements for the product specification. Risk assessments are not something that the business analyst plans to reuse to reduce the amount of time and effort needed to create a product specification for a project. Risk assessments are techniques that involve identifying and analyzing potential threats or uncertainties that may affect the project or the solution. Risk assessments can help to prioritize, mitigate, or monitor risks, but they do not provide requirements for the product specification. Qualitative analysis is not something that the business analyst plans to reuse to reduce the amount of time and effort needed to create a product specification for a project.
Qualitative analysis is a technique that involves using descriptive data and methods to understand, interpret, or evaluate the characteristics, behaviors, or perceptions of the stakeholders or the solution. Qualitative analysis can be performed for different purposes and at different stages of the project, but it does not provide requirements for the product specification. References: Business Analysis for Practitioners: A Practice Guide 1, page 114-115; PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline 2, page 17-18.
質問 # 128
In order to reduce product and project risk for a large, complex project, a business analyst is asked to help develop a change process that includes formal authorization and tracking throughout the life cycle of the project. The business analyst needs a capability that will help ensure that the product conforms to approved requirements, changes can be documented, and the status of each change can be reported.
What should the business analyst use?
- A. Configuration management system
- B. Work breakdown structure
- C. Traceability matrix
- D. Context models
正解：A
解説：
Explanation/Reference: https://www.izenbridge.com/blog/what-is-configuration-management-a-software-management- study/
質問 # 129
A company has completed a major project within time, cost, and scope and satisfied high-level quality standards and marketing requests. However, the product was considered a complete failure by shareholders and the market due to low return on investment.
From the business analysis perspective, the main reason for this business failure was a failure to:
- A. review and evaluate market expectations.
- B. establish measurable success criteria in the business case.
- C. gather the appropriate usability requirements.
- D. set the product positioning.
正解：A
質問 # 130
A few months into a project, the business analyst determines that the costs are exceeding the perceived benefits. The business analyst wants to address the possible risks of having to cancel the product.
Which of the following documents should be used?
- A. Project charter
- B. Business analysis plan
- C. Stakeholder impact matrix
- D. Business case
正解：D
質問 # 131
Midway through Ihe requirements gathering phase, a stakeholder informs the business analyst that a requested requirement does not address the solution. The stakeholder wants to know who made the request. The business analyst spends hours searching emails to identity the requestor.
What should the business analyst have documented?
- A. Sponsor approval in the requirements traceability matrix
- B. The source in the requirements traceability matrix
- C. Roles and responsibilities in the RACI matrix
- D. The source in the RACI matrix
正解：C
質問 # 132
A company is working on implementing a software application. They are converting their complex, in-house processes into the new system. The business analyst has been asked to analyze the processes.
Which technique should be followed?
- A. Feasibility analysis
- B. MoSCoW
- C. Interface analysis
- D. Requirements traceability
正解：C
解説：
Interface analysis is a technique that involves identifying and describing how a system or product interacts with other systems, products, or users. Interface analysis can help the business analyst to analyze the complex, in-house processes that are being converted into the new system by defining the inputs, outputs, functions, features, behaviors, and performance of each interface. Interface analysis can also help to ensure compatibility, interoperability, usability, and security of each interface. References: = PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline (2019), page 12; Business Analysis for Practitioners: A Practice Guide (2015), page 69.
質問 # 133
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?
- A. Statement of work
- B. Project plan
- C. Problem or opportunity statement
- D. Traceability matrix
正解：D
解説：
A traceability matrix is a document that links requirements to their sources and traces them throughout the project life cycle. It helps to track changes in requirements, assess their impact, and ensure that they are met by the project deliverables. A traceability matrix is a useful tool for document control, as it records the version history of each requirement and the rationale for any changes. A statement of work, a project plan, and a problem or opportunity statement are not methods of document control, but rather documents that describe the project scope, objectives, activities, and justification. References: PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline, page 9 1; Business Analysis for Practitioners: A Practice Guide, page 121 2
質問 # 134
Which of the following is a properly written requirement statement?
- A. The pot shall be lightweight and heat up quickly.
- B. The pot shall be manufactured in the following colors: yellow, red, brown, blue.
- C. The pot shall be usable in the oven or on the stove.
- D. The pot shall prominently display the company brand.
正解：B
解説：
A properly written requirement statement should be clear, concise, consistent, complete, and testable. It should specify what the product or service should do, not how it should do it. It should also avoid using ambiguous or vague words that could be interpreted differently by different stakeholders. Among the four options, only option C meets these criteria. Option C is a properly written requirement statement because it clearly and precisely defines the attribute of the pot (the colors) and the possible values for that attribute (yellow, red, brown, blue). It is also consistent with the standard terminology and format for requirement statements, and it is complete and testable, as it can be verified by inspection or measurement. Option A is not a properly written requirement statement because it uses ambiguous and vague words such as "lightweight" and "heat up quickly". These words do not specify the exact or measurable criteria for the pot's weight and heating time, and they could mean different things to different stakeholders. Option B is not a properly written requirement statement because it does not specify the conditions or constraints for the pot's usability in the oven or on the stove. For example, it does not state the maximum temperature or duration that the pot can withstand, or the type of oven or stove that the pot can be used on. Option D is not a properly written requirement statement because it does not specify the requirement for the pot itself, but rather for the company brand. The company brand is not a feature or function of the pot, but rather a marketing or branding strategy. The requirement statement should focus on the pot's characteristics and capabilities, not on the company's image or reputation. References: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, PMI Guide to Business Analysis2, Business Analysis for Practitioners: A Practice Guide3, How To Write Good Requirements (With Example) - TestLodge Blog
質問 # 135
When modeling processes or analyzing tasks, business rules can be uncovered by asking about:
- A. task transitions that hinder organizational performance.
- B. tasks that overlap with each other.
- C. work that may be performed out of sequence.
- D. reasons for choosing a particular course of action.
正解：D
解説：
Explanation
Business rules are statements that define or constrain some aspect of the business, such as policies, standards, procedures, regulations, or constraints. Business rules can be uncovered by asking about the reasons for choosing a particular course of action when modeling processes or analyzing tasks. By asking why a certain decision is made, what criteria are used, what conditions are applied, or what consequences are expected, the business analyst can elicit the business rules that govern the behavior or outcome of the process or task. Asking about tasks that overlap with each other, work that may be performed out of sequence, or task transitions that hinder organizational performance may help to identify issues or opportunities for improvement in the process or task, but they may not reveal the business rules that underlie them. References:
PMI Professional in Business Analysis (PMI-PBA)
Examination Content Outline1, page 15; Business
Analysis for Practitioners: A Practice Guide2, page 95.
質問 # 136
A business analyst is discussing the acceptance criteria for a new measurement system with the operations manager. The operations manager is particularly concerned about the accuracy of the new system because mistakes in data measurements could be extremely costly to fix.
Which of the following is the best strategy to define the appropriate acceptance criteria?
- A. Plan a training session for the new system before it is handed over to the operations manager.
- B. Ask the operations manager to formally accept the requirements documents.
- C. Quantify the risks associated with the measurement errors and update the risk register.
- D. Clearly define the maximum acceptable error rate for the new system.
正解：D
解説：
Explanation
According to the PMI Guide to Business Analysis, one of the best strategies to define appropriate acceptance criteria is to clearly define the performance measures and targets for the solution, such as accuracy, reliability, availability, efficiency, etc. These measures and targets help to evaluate how well the solution meets the stakeholder needs and expectations, and how it contributes to the business value. In this case, since the operations manager is concerned about the accuracy of the new measurement system, a good strategy would be to clearly define the maximum acceptable error rate for the new system, which would indicate how accurate the system should be in order to be accepted by the stakeholder. Quantifying the risks associated with measurement errors, asking for a formal acceptance of requirements documents, or planning a training session for the new system are not effective strategies to define appropriate acceptance criteria, as they do not specify how the performance of the solution will be measured or evaluated. References: PMI Guide to Business Analysis, page 316-317.
質問 # 137
A major stakeholder of a project is surprised to learn that a particular requirement was not implemented during the latest launch. The business analyst tells the stakeholder that the requirement status was changed to
"deferred."
What could have prevented the stakeholder from being surpnsed about the status change?
- A. The status should have been communicated to all project stakeholders.
- B. The status should have been communicated to the requirement's source.
- C. The status should have been reviewed prior to project launch.
- D. The status should have been updated in the traceability matrix.
正解：A
質問 # 138
A business analyst has incorporated all the relevant feedback from stakeholders in the business analysis plan.
Which next step should the business analyst take?
- A. Start implementing the project.
- B. Store the document for safe keeping
- C. Obtain approval on the plan.
- D. Start documenting requirements
正解：D
質問 # 139
......
合格させる保証付き無料クイズ2025年最新の実際に出ると確認されたPMI：https://jp.fast2test.com/PMI-PBA-premium-file.html
無料PMI Professional in Business Analysis PMI-PBA究極の学習ガイド：https://drive.google.com/open?id=1RipA1jiU437UQ1NtSwepdN7STD7TQyZ5