2024年最新の実際に出る無料IIBA CCBA試験問題集と解答
CCBA練習テストエンジンで今すぐ試そう522試験問題
IIBA CCBA 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
IIBA CCBA（ビジネス分析における能力の認定）認定試験は、ビジネスアナリストのスキルと専門知識を検証するグローバルに認められた認定です。 CCBA認定試験は、ビジネス分析で少なくとも2〜3年の経験があり、この分野でのキャリアを促進したい個人向けに設計されています。この認定は、国際ビジネス分析研究所（IIBA）によって提供されており、世界中で認められています。
CCBA認定試験の準備には、さまざまなトレーニングや学習リソースを活用することができます。IIBAは、オンラインコース、学習ガイド、実践試験など、さまざまなトレーニングコースと学習資料を提供しています。また、候補者は、地元の勉強グループに参加したり、同じ分野のプロフェッショナルとつながって知識を共有し、認定プロセスをサポートしあうこともできます。
質問 # 143
What does MoSCoW mean when it comes to requirements prioritization?
- A. Mustn't, Shouldn't, Couldn't, Won't
- B. Must, Should, Could, Won't
- C. Must, Should, Could, Would
- D. Money, Schedule, Control, Waiting
正解：B
解説：
Explanation
MoSCoW is a prioritization technique used in business analysis and project management to categorize requirements into four levels of priority: Must have, Should have, Could have, and Won't have. This method helps teams focus on the most critical requirements that need to be satisfied for a project to be successful, while also identifying which requirements can be deferred or excluded if necessary.
Must have: These are non-negotiable requirements that are essential for the project's success. If these are not met, the project is considered a failure.
Should have: These are important but not critical requirements. They are high-priority items that can be scheduled for a future release without impacting the current one.
Could have: These are desirable requirements that do not affect the overall success of the project. They can be included if time and resources permit.
Won't have: These are the lowest priority requirements or those that are not necessary for the current delivery cycle. They are recognized but not planned for the current project timeline.
References: The MoSCoW method is detailed in the Dynamic System Development Method (DSDM) handbook and is widely used across various industries for effective project management
質問 # 144
Nancy has asked you to trace a particular requirement for her. What does 'to trace a requirement' mean?
- A. Tracing a requirement means to track a requirement from its first identification all the way to its completion to see what issues, risks, costs, quality, and defects have surrounded the requirement.
- B. Tracing a requirement means to look at a requirement and the others to which it is related. It links risk, cost, quality, and scope elements to stakeholder and solution requirements to other artifacts created by the team and to solution components.
- C. Tracing a requirement means to look at a requirement and the others to which it is related. It links business requirements to stakeholder and solution requirements to other artifacts created by the team and to solution components.
- D. Tracing a requirement means to look at a requirement and the others to which it is related. It links business requirements to components in the project's work breakdown structure.
正解：C
解説：
Explanation
Requirements traceability is the ability to describe and follow the life of a requirement in both a forward and backward direction, from its origin, through its development and specification, to its subsequent deployment and use, and through periods of ongoing refinement and iteration in any of these phases1. Requirements traceability helps to ensure that the requirements are aligned with the business need, the solution scope, and the project objectives, and that they are verified and validated throughout the project lifecycle2. Requirements traceability also supports change management, impact analysis, risk management, and quality assurance3. To trace a requirement, one needs to look at the requirement and the others to which it is related, and document the relationships among them. These relationships can be horizontal (between requirements at the same level of detail) or vertical (between requirements at different levels of detail). The most common types of relationships are derivation, satisfaction, verification, and refinement4. A requirement can be traced to other artifacts created by the team, such as design documents, test cases, models, and code, as well as to solution components, such as features, functions, and interfaces5. Therefore, option D is the correct answer, as it captures the essence of requirements traceability.
References:
Requirements traceability - Wikipedia, first paragraph
Business Analysis Expert Certification, CCBA® | IIBA®, section "BABOK® Guide v3", chapter 6, section 6.1.4 A Guide to Understanding the Requirements Traceability Matrix, section "Why Is Requirements Traceability Important?" A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), version 3, chapter 6, section 6.1.4.1 What Is Traceability? | Perforce, first paragraph
質問 # 145
What tool is best described as a spreadsheet to use when there's a relatively low amount of requirements that need to be traced?
- A. Coverage matrix
- B. Roles and responsibilities chart
- C. RACI Chart
- D. Quantitative matrix
正解：A
解説：
Explanation
Coverage matrix is a spreadsheet that's ideal to use when there's a relatively low amount of requirements that need to be traced. This tool is typically used to trace high-level requirements.
Answer D is incorrect. RACI Chart is a responsibility assignment matrix for resources and activities. It is not a tracing tool for requirements.
Answer A is incorrect. The roles and responsibilities chart is ideal for tracking who does what in regard to assignments, but not for tracing requirements.
Answer B is incorrect. Quantitative matrix is used to quantify the probability and impact of risks, not to trace requirements.
質問 # 146
Karen is the business analyst for her organization and she's reviewing the tasks within her endeavor. Several of the tasks have the characteristic that the activity will be completed with the project stakeholders, consultants, and business analyst, though this hasn't yet been approved. What is this condition of believing some things to be true about an activity without proving the validity of the belief called?
- A. Constraint
- B. Boundary
- C. Risk
- D. Assumption
正解：D
解説：
Explanation
An assumption is something that you believe to be true, but it's not been proven to be true or false. The assumption in this scenario is that the stakeholders will be available to complete activities.
Answer C is incorrect. A constraint is something that limits your options.
Answer D is incorrect. A boundary defines what's in and out of the domain of business analysis, project
management, or any other endeavor.
Answer A is incorrect. A risk is an uncertain event or condition that may have a positive or negative effect on
the project.
質問 # 147
Robert is the business analyst for his organization and he gathered and documented the requirements for a new solution. The stakeholders agree through informal communications that Robert has successfully captured the needed requirements for the solution. The stakeholders signoff on the requirements. What does the signoff represent to Robert?
- A. That the stakeholders agree that the requirements are constrained by time, cost, and quality.
- B. That the stakeholders agree that the requirements are accurate and complete.
- C. That his work is done.
- D. That the project can now be launched.
正解：B
解説：
Explanation
Stakeholder signoff of the requirements can be formal or informal, though either instance is a confirmation by the stakeholders that the business analyst has identified the completed and accurate requirements.
Answer D is incorrect. Robert is not done with his business analysis duties just because the requirements have been approved.
Answer B is incorrect. The project may not launch even though the requirements are accurate and complete.
There could be other circumstances that prevent the project from launching - such as cost, feasibility, or tactics.
Answer A is incorrect. Requirements are simply the identified needs to solve a problem or present a solution.
Projects are constrained by time, cost, and scope. Quality is not one of the three constraints but it is achieved by the balance of time, cost, and fulfillment of scope.
質問 # 148
You are a business analyst for your organization and you're working with the stakeholders to identify the primary inputs to the business analysis approach. Which of the following will help determine whether a plan-driven or change-driven approach is appropriate?
Each correct answer represents a complete solution.
- A. Penalty of not seizing the opportunity
- B. Business need
- C. Expert Judgement
- D. Organizational process assets
正解：B、C、D
解説：
Explanation
These are the primary inputs of planning the business analysis approach. The primary input of planning the business analysis approach is to consider the problem or opportunity faced by the organization. Time allowed for business analysis planning does have an effect on the thoroughness of the business analysis activities. The risk associated with the plan is also considered.
質問 # 149
A business analyst (BA) needs to obtain agreement on and approval of requirements for a software solution. In order for this task to proceed, what does the BA need to understand?
- A. The verified requirements
- B. The business analysis approach
- C. The solution design
- D. The stakeholder roles
正解：B
解説：
Reference:
Babok v3.0 - IIBA guide
質問 # 150
Which solution scope creation technique can be best described as the depiction of the scope of work required to integrate the new solution into the business and technical environments?
- A. User stories
- B. Scope modeling
- C. Interface analysis
- D. Functional decomposition
正解：C
解説：
Explanation
The interface analysis technique depicts the scope of work required to integrate the solution into the business environment.
Answer D is incorrect. Functional decomposition is used to understand the scope of work and to break the
solution scope into smaller work products or deliverables.
Answer A is incorrect. Scope modeling is used to identify appropriate boundaries for the solution scope.
Answer C is incorrect. User stories describe stakeholders and the goals the system supports and as such can
also be used to define the solution scope.
質問 # 151
A stakeholder would like to add requirements to an IT project which is in flight. The project manager wants to revisit the traceability repository prior to committing to the addition of any new requests, because it is used for which of the following activities?
- A. Supporting change and scope management
- B. Creating test plans and test cases
- C. Approving requirement relationships
- D. Developing documentation for technical support
正解：C
質問 # 152
You are the business analyst for your organization and you're working with your team to define the business problem. As part of this analysis, you've identified the adverse impacts of the problem, the benefits from a potential solution, and how quickly the problem could be solved. What other element should you consider?
- A. Vendors input and paid solutions
- B. Dataflow of the problem
- C. Underlying source of the problem
- D. Competition and their approach
正解：C
解説：
Explanation
When examining a business problem, it's always important to define the underlying source of the problem.
This identification can help resolve the matter faster and for less cost. This resolution can also help to prevent the problem from continuing with a new solution that doesn't properly address the problem.
Answer B is incorrect. Competition and their approach may be useful in some instances, but it's not the best answer considering the QUESTION.
Answer A is incorrect. This isn't a valid answer for the QUESTION.
Answer C is incorrect. There's no evidence that a dataflow has been created, or even needs to be created.
質問 # 153
Which of the following approaches describes the project management approach of refining requirements and project scope?
- A. Plan-driven
- B. Change-driven
- C. Iterative
- D. Progressive elaboration
正解：D
解説：
Progressive elaboration describes the project management approach of refining requirements and project scope.
Answer C is incorrect. Iterative is not a valid business analysis approach.
Answer A is incorrect. The plan-driven approach defines business analysis activities. This approach is used to focus on minimizing up-front uncertainty and to ensure that the solution is fully defined before implementation begins in order to maximize control and minimize risk. It is preferred when requirements are effectively defined in advance of implementation.
Answer B is incorrect. Change-driven approaches to business analysis deal with rapid delivery of the business value. The business value is delivered in short iterations in return for acceptance of a higher degree of uncertainty regarding the overall delivery of the solution.
The change-driven approaches are preferred while taking an exploratory approach for incremental improvement of an existing solution.
質問 # 154
Which task in the requirements analysis knowledge area is best described as ensuring that the requirements specifications and models meet the necessary standard of quality to allow them to be used effectively to guide further work?
- A. Defining assumptions and constraints
- B. Specifying and modeling requirements
- C. Organizing requirements
- D. Requirements verification
正解：D
解説：
Explanation/Reference:
Requirements verification is the correct answer. This task verifies that requirements specifications and models are accurate so that the endeavor may continue to achieve the best solution for the organization.
A is incorrect. The task of defining assumptions and constraints identifies factors other than
requirements that may affect which solutions are viable.
C is incorrect. The task to specify and model requirements is used to analyze expressed
stakeholder desires and/or the current state of the organization using a combination of textual statements, matrices, diagrams, and formal models.
B is incorrect. The purpose of organizing requirements is to create a set of views of the
requirements for the new business solution that are comprehensive, complete, consistent, and understood from all stakeholder perspectives.
質問 # 155
Which one of the following is not an event-based elicitation technique?
- A. Focus group
- B. Interface analysis
- C. Workshop
- D. Interview
正解：B
解説：
Explanation
Interface analysis is not an event-based elicitation technique. It is an elicitation technique that identifies interfaces between solutions and how the interfaces will interact.
Answer D is incorrect. A workshop is an event-based elicitation technique. Answer A is incorrect. A focus group is an event-based elicitation technique. Answer C is incorrect. An interview is an event-based elicitation technique.
質問 # 156
You are the business analyst for your organization and you're notifying the key stakeholders of a need to gather requirements for an endeavor. One of the stakeholders that you'll need to attend your requirements workshop is the project manager. What role will the project manager have in this workshop?
- A. The project manager will facilitate the requirements workshop.
- B. The project manager will ensure that the needed resources are available.
- C. None, the project manager should not be involved until all of the requirements have been identified.
- D. The project manager will help elicit requirements from the stakeholders.
正解：B
解説：
The role of the project manager in elicitation tasks is to ensure that the needed resources are available.
Answer C is incorrect. The project manager will likely be involved in the requirements workshop.
Answer A is incorrect. The project manager won't facilitate the requirements workshop, the business analyst will.
Answer D is incorrect. The project manager may help elicit requirements from stakeholders, but this isn't the best choice for the QUESTION.
質問 # 157
As a business analyst, you'll often need to analyze business needs, requirements, and solutions for assumptions and constraints. Which one of the following is a constraint? Choose the best answer.
- A. The solution should be implemented during the summer months.
- B. The solution won't need external resources.
- C. The solution must cost less than $450,000.
- D. The solution must be done by December 31.
正解：D
質問 # 158
What do business goals and objectives of enterprise analysis actually describe?
- A. Business goals and objectives describe the solution scope that the organization is seeking to accomplish.
- B. Business goals and objectives describe the ends that the organization is seeking to achieve.
- C. Business goals and objectives describe the desired future state of problems.
- D. Business goals and objectives describe the increased revenue that the organization is seeking to gain.
正解：B
解説：
Explanation
Business goals and objectives are statements of the desired outcomes that the organization wants to achieve through its initiatives and projects. They are not the means to achieve those outcomes, but the ends themselves. Business goals and objectives provide the context and direction for enterprise analysis, as they help to identify and prioritize the business needs and opportunities that align with the strategic vision of the organization. References:
Capability in Business Analysis™ (CCBA®) Certification Handbook, page 10 A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), version 3, page 35 What is enterprise analysis and what results does it have? | IIBA®
質問 # 159
Requirements have been prioritized in the product backlog for inclusion in the upcoming release. One of the project team members fears that at least one requirement from the prioritization list is not finalized and still requires further analysis. Which of the following factors describe the affected requirement?
- A. Benefit
- B. Stability
- C. Risk
- D. Dependency
正解：B
解説：
Explanation
Stability is the factor that describes the affected requirement, as it indicates the likelihood of the requirement remaining constant and static. Requirements that are not stable or whose definition changes frequently are given a lower priority to minimize recurrence, rework, and time and resource waste. References: Please refer to the CCBA® guide and other official IIBA resources for specific references and detailed explanations. You can also check out the following web search results for more guidance:
Five Requirements Prioritization Methods - Business Analyst Articles ...
What Are Requirement Prioritization Techniques? - Techcanvass
5 Popular Requirements Prioritisation Techniques - The Business Analyst ...
How to prioritize requirements - The Functional BA
An Overview of Requirements Prioritization > Business Analyst Community ...
質問 # 160
A business analyst (BA) needs approval for the requirements which were elicited, collated, and verified by a peer. The BA needs to understand the approval process and appropriate stakeholders who have the authority to approve the requirements. Which of the following artifacts contains this information?
- A. Governance approach
- B. Stakeholder engagement approach
- C. Business analysis approach
- D. Information management approach
正解：A
解説：
Explanation
According to the BABOK® Guide, the governance approach is an artifact that defines the processes, roles, and responsibilities for approving, prioritizing, and managing requirements and designs. The governance approach also specifies the decision making authority, approval criteria, and change control procedures for the requirements and designs. By understanding the governance approach, the business analyst (BA) can identify the appropriate stakeholders who have the authority to approve the requirements and the approval process that needs to be followed. References: BABOK® Guide, Version 3, Chapter 2, Section 2.4.5; Business Analysis Expert Certification, CCBA® | IIBA®, Section "What Should I know to be CCBA Certified?"
質問 # 161
Which of the following is used as a means of validating a created, selected, or tailored business analysis approach?
- A. Process modeling
- B. Progressive elaboration
- C. Decision analysis
- D. Structured walkthrough
正解：D
質問 # 162
Which task in the requirements analysis knowledge area is best described as ensuring that the requirements specifications and models meet the necessary standard of quality to allow them to be used effectively to guide further work?
- A. Defining assumptions and constraints
- B. Specifying and modeling requirements
- C. Organizing requirements
- D. Requirements verification
正解：D
解説：
Explanation
Requirements verification is the correct answer. This task verifies that requirements specifications and models are accurate so that the endeavor may continue to achieve the best solution for the organization.
Answer A is incorrect. The task of defining assumptions and constraints identifies factors other than requirements that may affect which solutions are viable.
Answer C is incorrect. The task to specify and model requirements is used to analyze expressed stakeholder desires and/or the current state of the organization using a combination of textual statements, matrices, diagrams, and formal models.
Answer B is incorrect. The purpose of organizing requirements is to create a set of views of the requirements for the new business solution that are comprehensive, complete, consistent, and understood from all stakeholder perspectives.
質問 # 163
Which business analysis task in the requirements management and communication domain is best described as creating and maintaining relationships among business objectives, requirements, team deliverables, and solution components to support business analysis activities?
- A. Prepare the requirements package.
- B. Document requirements for review.
- C. Communicate requirements.
- D. Manage requirements traceability.
正解：D
解説：
The question describes the task of managing requirements traceability.
Answer B is incorrect. Preparing the requirements package is a task that selects and structures a set of requirements to ensure that the requirements are effectively communicated to, understood by, and usable by a stakeholder group or groups.
Answer A is incorrect. Communicating requirements is the process of discussing the requirements through communication channels to ensure that the stakeholders understand the requirements.
Answer D is incorrect. Documenting requirements for review is not a valid answer, as this is not a business analysis task in the requirements management and communication knowledge area.
質問 # 164
Which one of the following terms is not a business analysis planning and monitoring approach?
- A. Structured walkthroughs
- B. Requirements elicitation
- C. Process modeling
- D. Decision analysis
正解：B
解説：
Requirements elicitation is a business analysis task; it is not a business analysis planning and monitoring approach.
Answer B is incorrect. Decision analysis is a business analysis planning and monitoring approach so this choice is incorrect.
Answer D is incorrect. Process modeling is a business analysis planning and monitoring approach so this choice is incorrect.
Answer A is incorrect. Structured walkthroughs are a business analysis planning and monitoring approach so this choice is incorrect.
質問 # 165
A business analyst (BA) is planning to elicit requirements. The BA understands the scope of the elicitation and has selected interviewing as an appropriate technique. Which of the following is part of the logistics for these interviews?
- A. Relationships between elicited requirements
- B. Participants and their roles
- C. Definition of the future state
- D. Performance metrics
正解：B
解説：
A key step in preparing for elicitation is to ensure that the logistics of the session or series of sessions are well planned for by considering the following key aspects:
The goals of the session.
Who are the participants and what are their roles?
Scheduled resources including people, rooms, and tools such as flip charts. Locations and communication channels.
Techniques that will be used.
Languages used by the stakeholders specifically being prepared to understand subject matter terminology and key abbreviations.
質問 # 166
All of the following are documented approaches to business analysis work except for which one?
- A. Deming's Quality Circle
- B. Waterfall approach
- C. Six Sigma
- D. Lean
正解：A
解説：
Explanation
Deming's Quality Circle describes the quality management approach of plan, do, check, and act. This isn't a business analysis approach.
Answer C is incorrect. The waterfall approach is a valid answer for business analysis approaches. Answer: D is incorrect. Lean is a valid answer for business analysis approaches.
Answer B is incorrect. Six Sigma is a valid answer for business analysis approaches.
質問 # 167
......
試験合格保証付きのCertification of Capability in Business Analysis CCBA試験問題集：https://www.goshiken.com/IIBA/CCBA-mondaishu.html
IIBA CCBA日常練習試験は2024年最新のに更新された522問あります：https://drive.google.com/open?id=1GmLYojhSc6x_WkJIehAkckpWyxnwVIsS