PMI-PBAのPDF問題集で2025年02月11日試験問題 有効なPMI-PBA問題集
究極のPMI-PBA準備ガイドで無料最新のPMI練習テスト問題集
PMI PMI-PBA認定は、グローバルに認知され、ビジネス分析コミュニティで高い評価を受けています。この認定は、候補者がビジネス分析の実践に深い理解を持ち、様々な状況で効果的に適用できる能力を持っていることを示しています。また、候補者が継続的なプロフェッショナルな成長と、分野の最新のプラクティスやトレンドについて最新情報を得ることにコミットしていることを示しています。
PMI-PBA試験は、ビジネス分析における教育と経験の両方を持つ候補者を求める厳格な認定プログラムです。候補者は、ビジネス分析における最低3年の経験と35時間のビジネス分析の教育を持つ必要があります。さらに、候補者は、ビジネス分析のさまざまな側面をカバーする200問の多肢選択問題の試験に合格する必要があります。PMI-PBA試験はコンピュータベースであり、世界中のさまざまなテストセンターで提供されています。
PMI-PBA認定試験は、プロジェクトチームやステークホルダーと協力して要件を定義、分析、文書化するビジネスアナリストのスキルと知識をテストするために設計されています。この認定は、プロジェクト管理基準とプラクティスを推進するグローバルな組織であるProject Management Institute（PMI）によって提供されています。PMI-PBA認定は世界的に認められており、ビジネスアナリストの高度な熟練度を示す価値ある資格です。
質問 # 81
Midway through the 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 identify the requestor.
What should the business analyst have documented?
- A. Sponsor approval in the requirements traceability matrix
- B. The source in the RACI matrix
- C. The source in the requirements traceability matrix
- D. Roles and responsibilities in the RACI matrix
正解：D
解説：
Documenting the source of each requirement in the requirements traceability matrix allows for easy identification of the requestor and facilitates communication with stakeholders. References: PMI-PBA Examination Content Outline, Business Analysis for Practitioners: A Practice Guide.
質問 # 82
A business analyst is documenting the acceptance criteria to suppon 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?
- A. The analyst utilized user stories as a requirements document tool.
- B. The analyst failed to gather any baseline information.
- C. The analyst did not include the scope document in the acceptance criteria paperwork.
- D. The analyst performed forward and backwards traceability.
正解：B
質問 # 83
A stakeholder wants to modify an existing feature. Which of the following would be used to determine the scope of the change on the product?
- A. Sequence diagram
- B. Requirements attributes table
- C. Requirements traceability matrix
- D. Project schedule and cost baseline
正解：C
解説：
A requirements traceability matrix (RTM) is a tool that helps to track the relationship between the requirements and the product features. It can be used to determine the scope of a change request by identifying which requirements and test cases are affected by the modification of an existing feature. A project schedule and cost baseline are not directly related to the product features, but rather to the project management aspects. A requirements attributes table is a tool that helps to classify and prioritize the requirements, but it does not show the link between the requirements and the product features. A sequence diagram is a tool that helps to illustrate the interactions between the components of the product, but it does not show the traceability of the requirements. References: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, PMI Guide to Business Analysis2, Business Analysis for Practitioners: A Practice Guide
質問 # 84
During validation of a project solution, the business analyst discovers that a requirement has been altered.
Instead of placing the company logo in the upper-left corner of the window, it is displayed in the upper-right corner. When the business analyst asks the developer about the change, the developer says that one of the stakeholders asked directly for the change.
Which correct action should the business analyst take?
- A. Follow the change control process as defined in the business analysis plan.
- B. Confront the stakeholder that requested the change.
- C. Ask the developer to correct the logo as stated in the requirement.
- D. Discuss the change in the next stakeholder meeting.
正解：D
解説：
Explanation
質問 # 85
A financial company deployed a new online product to their customers to invest in the stock market. The company notices a problem regarding financial calculations and starts the problem analysis. The company discovers that the new rules for taxes and fees were not implemented.
This problem could have been avoided by:
- A. rolling back the operations using a contingency process in order to avoid loss and client dissatisfaction.
- B. involving a business analyst during all phases of system development.
- C. using a table that shows each applicable business rule with the implemented functional requirement.
- D. implementing an automated issue tracking system to facilitate the tracing of defects to the requirements.
正解：C
解説：
Explanation
Using a table to map business rules to functional requirements ensures that all tax and fee calculations are implemented correctly. It helps in verifying that the system reflects current regulations and avoids calculation errors. References: PMI-PBA
Examination Content Outline, Business Analysis for Practitioners: A Practice Guide.
質問 # 86
The human resources, engineering, and marketing departments have provided feedback on the business needs for a new product. After analyzing the feedback from the three departments, it would be best to:
- A. collaborate on a product scope that aligns with the company's objectives.
- B. delegate the decision to be made by the product sponsor.
- C. negotiate to best meet each department's objectives.
- D. vote on the product's highest-value business needs.
正解：A
解説：
Explanation
A product scope is a description of the features, functions, and characteristics of a product that meets the needs and expectations of the stakeholders. It defines what the product is and what it is not, and provides the basis for planning, developing, testing, and delivering the product. A product scope should align with the company's objectives, which are the desired outcomes or results that the company wants to achieve through its products, services, and projects. Aligning the product scope with the company's objectives helps to ensure that the product delivers value to the customers and the business, supports the company's vision and mission, and contributes to the company's strategic goals12.
To collaborate on a product scope that aligns with the company's objectives, the business analyst should follow these steps12:
Identify and engage the relevant stakeholders, such as the human resources, engineering, and marketing departments, as well as the product sponsor, the customers, and the end users. Stakeholders are the individuals or groups who have an interest or influence in the product, and who can provide input, feedback, and approval for the product scope.
Elicit and analyze the business needs, requirements, and expectations of the stakeholders, using various techniques, such as interviews, surveys, workshops, observation, prototyping, and brainstorming.
Business needs are the problems or opportunities that the product aims to address or exploit, and that justify the investment in the product. Requirements are the specifications or conditions that the product must meet or satisfy to fulfill the business needs. Expectations are the desires or wishes that the stakeholders have for the product, which may or may not be realistic or feasible.
Validate and prioritize the business needs, requirements, and expectations, based on their value, urgency, risk, dependency, and alignment with the company's objectives. Validation is the process of ensuring that the business needs, requirements, and expectations are clear, complete, correct, consistent, and feasible. Prioritization is the process of ranking the business needs, requirements, and expectations according to their relative importance and impact on the product scope and the company's objectives.
Define and document the product scope, using various tools, such as a product vision statement, a product scope statement, a product backlog, a product roadmap, and a product breakdown structure. A product vision statement is a brief and compelling description of the purpose, value proposition, and target market of the product. A product scope statement is a detailed and formal description of the product scope, including the product objectives, deliverables, features, functions, boundaries, assumptions, constraints, and acceptance criteria. A product backlog is a list of the product requirements, features, and enhancements that are prioritized and refined for development. A product roadmap is a high-level and strategic plan that shows the direction, timeline, and milestones of the product development. A product breakdown structure is a hierarchical and graphical representation of the product components and their relationships.
Communicate and manage the product scope, using various techniques, such as reviews, walkthroughs, inspections, audits, and change control. Communication is the process of sharing and exchanging the product scope information with the stakeholders, and ensuring that they understand and agree on the product scope. Management is the process of monitoring and controlling the product scope, and ensuring that it is delivered according to the plan and the company's objectives. Change control is the process of evaluating, approving, and implementing any changes to the product scope, and ensuring that they are aligned with the company's objectives.
Voting on the product's highest-value business needs is not the best option, because it may not consider the perspectives and preferences of all the stakeholders, and it may not reflect the company's objectives.
Negotiating to best meet each department's objectives is not the best option, because it may result in compromises or trade-offs that may not benefit the product or the company as a whole, and it may not align with the company's objectives. Delegating the decision to be made by the product sponsor is not the best option, because it may not involve the participation and collaboration of the other stakeholders, and it may not align with the company's objectives. : 1 PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline, page 10-11; 2 Business Analysis for Practitioners: A Practice Guide, page
133-134
質問 # 87
After a project was delivered, the business analyst learns of a project objective with no associated requirement.
What would have helped determine this issue before delivery?
- A. Use cases
- B. Process flow
- C. Context diagram
- D. Tracing requirements
正解：D
解説：
Explanation/Reference: https://www.pmi.org/learning/library/top-five-causes-scope-creep-6675
質問 # 88
A business analyst has been asked to investigate a problem. This investigation will provide input towards developing a business case. The business analyst wants to first understand the company's current business processes.
Which technique should the business analyst use?
- A. RACI matrix
- B. User stories
- C. Observation
- D. MoSCoW
正解：B
質問 # 89
A new project is in the planning phase. What should the business analyst consider with regard to planning the requirements change process?
- A. How requirement changes will be implemented
- B. How requirement changes will impact the validation plan
- C. How requirement changes will be communicated
- D. How requirement changes will impact the requirements baseline
正解：D
質問 # 90
A type of requirements document that would be the most valuable to a database administrator would be:
- A. an entity relationship diagram.
- B. a business process diagram.
- C. an object diagram.
- D. a data flow diagram.
正解：A
解説：
Explanation/Reference: https://www.smartdraw.com/entity-relationship-diagram/
質問 # 91
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?
- A. Prototyping
- B. Questionnaires
- C. Group decision making
- D. Stakeholder analysis
正解：A
解説：
Explanation
Prototyping is a technique that involves creating a simplified or partial version of the solution to elicit feedback from the stakeholders. Prototyping can help the business analyst to deal with a complex project with stakeholders who find it difficult to articulate their needs by providing a visual and interactive representation of the solution. Prototyping can also help to reduce requirements risk by validating or verifying the requirements, identifying gaps or errors, and resolving ambiguities or conflicts. References: = PMI Professional in Business Analysis (PMI-PBA)
Examination Content Outline (2019), page 12; Business
Analysis for Practitioners: A Practice Guide (2015), page 69.
質問 # 92
The document that defines the process for managing requirements revisions is the:
- A. scope management plan.
- B. change management plan.
- C. project management plan.
- D. communications management plan.
正解：D
質問 # 93
Which tool can be used to analyze how the system responds to various combinations of input conditions with the probability of each outcome?
- A. Weighted criteria
- B. Expected monetary value
- C. Functional decomposition
- D. Decision tree
正解：D
解説：
A decision tree is a tool that can be used to analyze how the system responds to various combinations of input conditions with the probability of each outcome. A decision tree is a graphical representation of a decision problem that shows the possible choices and their consequences. A decision tree can help to evaluate the expected value of each alternative and choose the optimal one. Functional decomposition is a tool that can be used to break down a complex system or process into smaller and simpler components. Expected monetary value is a tool that can be used to calculate the average outcome of a decision under uncertainty by multiplying the value of each outcome by its probability and summing them up. Weighted criteria is a tool that can be used to prioritize requirements or alternatives based on their importance and performance scores. References: PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline1, page
15; Business Analysis for Practitioners: A Practice Guide2, page 95.
質問 # 94
The project team is working on the requirements specifications for a new product. The team reached a decision on which requirements will be included in the next release. A third of the stakeholders endorse one approach while no other approach achieved more than a quarter of the vote.
Which decision role was used?
- A. Plurality
- B. Consensus
- C. Majority
- D. Unanimity
正解：A
解説：
Explanation
Plurality is the decision role that was used by the project team to decide which requirements will be included in the next release. Plurality means that the option with the most votes is selected, even if it does not have a majority (more than 50%) of the votes. Plurality is a decision role that can be used when there are more than two options and a quick decision is needed. References: PMI Guide to Business Analysis, Chapter 4, Section
4.3.2.4; PMI Professional in Business Analysis (PMI-PBA)
Examination Content Outline, Domain II:
Planning, Task 3.
質問 # 95
A business analyst is working on a project to update the user interface for a legacy procurement system.
An end user raises concerns that the new solution will not support their core business processes.
How could the business analyst address the end user's concerns about the new interface?
- A. Consult the stakeholder register to evaluate if the user has authority to influence the project.
- B. Develop a prototype to gather functional requirements.
- C. Document the business data objects using an entity relationship diagram.
- D. Develop a use case package to support the user interface.
正解：D
質問 # 96
A business analyst has captured all of the requirements from the various stakeholders within the organization and has compiled them into a complete list. After reviewing the list of requirements with the stakeholders, it is determined that the list of requirements is too large and will exceed the allotted budget.
Which tool or technique should the business analyst use with the stakeholders to prioritize the requirements to determine which requirements are approved, deferred, or rejected?
- A. MoSCoW Analysis
- B. SMART Goals
- C. SWOT Analysis
- D. Timeboxing Analysis
正解：A
質問 # 97
A business analyst is conducting a cost-benefit analysis of potential solution options. The stakeholders have indicated that the estimated growth rate is very important to them.
Which technique will allow the business analyst to determine this information?
- A. Internal rate of return
- B. Net present value (NPV)
- C. Payback period
- D. Return on investment (ROI)
正解：A
解説：
Explanation
Internal rate of return (IRR) is a technique that calculates the annualized rate of return of an investment or a project. IRR can help the business analyst to determine the estimated growth rate of potential solution options by comparing the present value of the expected cash inflows and outflows of each option. IRR can also help to select the option that has the highest rate of return and exceeds the minimum required rate of return or the cost of capital. References: = PMI Professional in Business Analysis (PMI-PBA)
Examination Content Outline
(2019), page 11; Business Analysis for Practitioners: A Practice Guide (2015), page 66.
質問 # 98
What should the business analyst do during the first steps of a project?
- A. Evaluate the sources for requirements and prioritize them.
- B. Align the sponsor expectations along the project goals.
- C. Identify the classes of users and their requirements.
- D. Identify stakeholders and their interests.
正解：B
解説：
One of the first steps of a project is to identify the stakeholders and their interests. Stakeholders are the individuals or groups who have an interest or influence in the project or its outcome. Identifying the stakeholders and their interests helps to understand their needs, expectations, roles, responsibilities, and communication preferences. It also helps to manage their involvement and engagement throughout the project life cycle, and to address any potential conflicts or issues that may arise. The other options are not the first steps of a project. Identifying the classes of users and their requirements is part of the requirements elicitation process, which occurs after the project initiation phase. Aligning the sponsor expectations along the project goals is part of the project charter development, which is also done after the project initiation phase.
Evaluating the sources for requirements and prioritizing them is part of the requirements analysis process, which occurs after the requirements elicitation process. References: PMI-PBA Examination Content Outline, page 10; PMI-PBA Reference List, page 1, BABOK Guide v3, page 50; 3.
質問 # 99
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. Problem or opportunity statement
- B. Statement of work
- C. Project plan
- 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
質問 # 100
......
合格率 取得する秘訣はPMI-PBA認定試験エンジンPDF：https://www.jpntest.com/shiken/PMI-PBA-mondaishu
今すぐ試そう！高評価PMI PMI-PBA試験問題集：https://drive.google.com/open?id=13HMEkcN1jJFm0VI6jq5NTtzzBhNe5YaS