CCBA Practice Questions

Implementing the requirements with the highest amount of risks first is a good idea, as it allows the

project manager to address the uncertainties and challenges early in the project, and to avoid

potential delays or rework later on. This is a common practice in agile or adaptive approaches to

business analysis and project management, which embrace change and value feedback12. The

otheroptions are not good ideas, as they either postpone the risky requirements until the end of the

project ©, which increases the likelihood of scope creep, budget overrun, or stakeholder

dissatisfaction, or implement the lowest risk requirements first (A), which may not deliver the most

value or benefit to the organization, or assume that the project will fail due to the risky requirements

(B), which is a pessimistic and unrealistic view of the project outcome. Reference: Business Analysis

Expert Certification, CCBA® | IIBA®, Certification of Capability in Business Analysis™ (CCBA®)

A domain subject matter expert is a stakeholder who has extensive knowledge and experience in the

business area or problem domain that is relevant to the project. They provide valuable insights and

information to the business analyst and help to define and validate the requirements and the

solution. Adam, who is steeped in knowledge regarding the project’s purpose, is likely to be a

domain subject matter expert.

Reference: The information is aligned with the competencies and knowledge areas defined in the

Business Analysis Body of Knowledge® (BABOK® Guide) and the Certification of Capability in Business

Analysis™ (CCBA®) as provided by the International Institute of Business Analysis (IIBA®). For

detailed

, please consult the CCBA® guide1 and the BABOK® Guide2 available through the

IIBA® website and bookstore3. You can also find some useful resources and sample questions from

other sources4.

The matrix documentation approach is used to specify and model requirements that are complex but

uniform in structure. This means that the requirements can be broken down into simple elements

that can be inputted into a matrix. A matrix is a rectangular array of numbers, symbols, or

expressions, arranged in rows and columns. Matrices can be used to represent various types of

requirements, such as data dictionaries, gap analysis, requirements traceability, and business rules

analysis. Matrices can help to communicate information to a specific audience, confirm information,

identify information gaps, and prevent the duplication of information. Reference:

Specifying and modeling requirements – The Functional BA

Selecting Requirements Documentation Techniques for Software Projects: a Survey Study

The business analysis task that Shelly is facilitating in this scenario is validate requirements. This task

involves ensuring that the requirements align with the business objectives, goals, and vision of the

organization, and that they support the delivery of value. Shelly and Thomas are reviewing the

requirements to verify that they are consistent, feasible, and acceptable for the stakeholders. The

other options are not relevant to this scenario, as they involve defining the criteria for accepting the

solution (A), ensuring the quality of the requirements documentation (B), or managing the

relationships and expectations of the stakeholders (D). Reference: CERTIFICATION OF CAPABILITY IN

BUSINESS ANALYSIS, Certification of Capability in Business Analysis (CCBA®) - Simplilearn

A . Prioritization ranks the requirements according to the cost and schedule: This is

an incorrect answer, as it confuses prioritization with estimation. Estimation is the process of

determining the effort, time, and resources needed to implement the requirements. Prioritization is

the process of determining the relative importance and urgency of the requirements.

B . Prioritization ranks the requirements on a weighted scale of key performance indicators, such as

cost, schedule, risk, and experience: This is a correct answer, as it describes one possible method of

prioritizing requirements based on multiple criteria that reflect the value and feasibility of the

requirements. Key performance indicators (KPIs) are measurable factors that indicate the progress

and success of the project or the solution.

C . Prioritization ensures that the most important stakeholders are considered first: This is

an incorrect answer, as it implies that some stakeholders are more important than others.

Prioritization does not rank the stakeholders, but the requirements. All stakeholders should be

considered and involved in the business analysis process, as they have different needs, expectations,

and perspectives that affect the solution.

D . Prioritization of requirements focuses on the most critical requirements first: This is

a correct answer, as it states the main purpose and benefit of prioritization. Prioritization helps to

ensure that the most valuable and essential requirements are delivered first, and that the scope,

schedule, and budget of the project are aligned with the business objectives and stakeholder

expectations.

Visual learners are those who learn best through the presentation of models, diagrams, charts,

graphs, and other visual aids. They prefer to see the information rather than hear it or do it. Visual

learners can benefit from the use of models in business analysis, as they can help them to

understand the problem, the solution, and the requirements in a clear and concise way.

Reference: The information is verified as per the CCBA Learning documents and resources, which

outline the standards and practices for business analysis. You can find more information about the

types of learners and the use of models in business analysis in the CCBA guide1 and the BABOK

Guide2 available through the IIBA website and bookstore3. You can also find some useful resources

and sample questions from other sources45.

A . It defines the nature of a solution that meets that need: This is a correct activity of enterprise

analysis, as it involves defining the scope, objectives, and requirements of the solution that will

address the business problem or opportunity.

B . It identifies business needs, problems, or opportunities: This is a correct activity of enterprise

analysis, as it involves understanding the current state of the organization, its goals, and the external

and internal factors that affect its performance.

C . It justifies the investment necessary to deliver that solution: This is a correct activity of enterprise

analysis, as it involves assessing the costs, benefits, risks, and feasibility of the proposed solution and

presenting a business case that supports the decision to implement it.

D . It manages and expresses requirements to a broad and diverse audience: This is

an incorrect activity of enterprise analysis, as it belongs to another knowledge area, which is

requirements communication and management. This knowledge area involves ensuring that the

requirements are understood, agreed upon, and controlled by all the stakeholders throughout the

project lifecycle.

When you assess a solution, what you are actually looking for is to determine the value of the

proposed solution to the stakeholder requirements. This is the main purpose of the solution

assessment and validation knowledge area, which involves measuring and evaluating the

performance and benefits of the solution, and ensuring that it meets the stakeholder needs and

expectations12. Value is defined as the worth, importance, or usefulness of something to a

stakeholder within a context3. To determine the value of the proposed solution, you need to identify

and analyze the value proposition, the value drivers, the value measures, and the value

delivery4. The other options are not what you are actually looking for when you assess a solution,

but rather aspects that may contribute to the value of the solution, such as the quality (B), which is

the degree to which a solution meets the requirements and delivers the expected benefits5, the cost

©, which is the amount of resources expended or consumed to implement and operate the solution,

or the accuracy (D), which is the extent to which a solution represents the true or exact state of the

problem or the need. Reference: Business Analysis Expert Certification, CCBA® | IIBA®, Certification

of Capability in Business Analysis™ (CCBA®), Business Analysis Certification Competencies, CCBA® |

IIBA®, The Ultimate Guide to Business Capability Analysis, CBAP / CCBA Certified Business Analysis

Study Guide, 2nd Edition, [Certification of Capability in Business Analysis (CCBA®) - Simplilearn], [A

GUIDE TO THE BUSINESS ANALYSIS BODY OF KNOWLEDGE]

A request for quote (RFQ) is a document that invites vendors to provide a price quote for their

products or services based on a detailed statement of work (SOW). The SOW describes the scope,

specifications, deliverables, and acceptance criteria of the solution that the organization needs. The

RFQ allows the organization to compare different vendors based on their prices and capabilities, and

to select the best one for the project.

Reference: The information is verified as per the CCBA Learning documents and resources, which

outline the standards and practices for business analysis. You can find more information about the

RFQ and the SOW in the CCBA guide1 and the BABOK Guide2 available through the IIBA website and

bookstore3. You can also find some useful resources and sample questions from other sources.

Before managing the requirements, Tracy must identify the roles, responsibilities, and owners of the requirements, as this is one of the tasks under the business analysis planning and monitoring knowledge area1. This task involves defining who will be involved in the requirements developmentand management process, what their roles and responsibilities are, and who has the authority to approve or change the requirements. This helps to ensure clarity, accountability, and collaboration among the stakeholders and the business analyst. The other options are not prerequisites for managing the requirements, but rather activities that may be performed during or after the requirements analysis and design definition knowledge area2. Decomposing the requirements in WBS (A) is a technique for breaking down the requirements into smaller and more manageable components. Creating cost-benefits analysis of each requirement (B) is a technique for evaluating the value and feasibility of the requirements. Communicating the requirements to the stakeholders for their consent and approval (D) is a task for verifying and validating the requirements. Reference: CERTIFICATION OF CAPABILITY IN BUSINESS ANALYSIS, Business Analysis Expert Certification, CCBA® | IIBA®