Free Preparation Discussions
MENU
IIBA CCBA Exam Questions
- Topic 1: Business Analysis Planning and Monitoring: This section of the exam measures the skills of a Business Analyst and covers the foundational tasks involved in planning the business analysis approach, identifying stakeholders, managing business analysis performance, and setting the structure for collaboration throughout the project.
- Topic 2: Elicitation and Collaboration: This section of the exam measures the skills of a Requirements Engineer and covers the activities needed to prepare for, conduct, and confirm elicitation results. It also focuses on how business analysts work with stakeholders to ensure effective communication and collaboration during the requirements process.
- Topic 3: Requirements Life Cycle Management: This section of the exam measures the skills of a Business Analyst and covers the tracking and managing of requirements from inception through retirement. It addresses how requirements are maintained, prioritized, traced, and reused across the life cycle of a solution.
- Topic 4: Strategy Analysis: This section of the exam measures the skills of a Requirements Engineer and covers the evaluation of the business environment to identify problems or opportunities and assess potential value. It also includes defining the future state and recommending strategies to achieve business goals.
- Topic 5: Requirements Analysis and Design Definition: This section of the exam measures the skills of a Business Analyst and covers the transformation of elicited requirements into detailed design options. It focuses on analyzing, modeling, verifying, and validating requirements to define solutions that meet business needs.
- Topic 6: Solution Evaluation: This section of the exam measures the skills of a Requirements Engineer and covers assessing the performance and value delivered by a solution in use. It includes determining if business needs are met and identifying areas where the solution or its implementation can be improved.
Free IIBA CCBA Exam Actual Questions
Note: Premium Questions for CCBA were last updated On Jun. 20, 2025 (see below)
A business analyst (BA) has set up a number of elicitation workshops with key subject matter experts (SMEs) on a new project. All SMEs have accepted the workshop invitations except for the legal SME who has not responded to any invitations. The first workshop is scheduled for next week and the BA has tried unsuccessfully to reach the legal SME by phone. How should the BA proceed?
Elicitation workshops are a technique that involves bringing together a group of stakeholders to elicit, analyze, and validate requirements for a project. Elicitation workshops require careful planning, preparation, and facilitation to ensure that the objectives are met and the outcomes are documented. Elicitation workshops also depend on the participation and collaboration of the relevant stakeholders, especially the subject matter experts who have the knowledge and expertise on the project domain.
If the business analyst has set up a number of elicitation workshops with key subject matter experts on a new project, and one of them has not responded to any invitations, the business analyst should proceed with the first workshop and capture the non-response as a project issue for the project manager to address. This is the best course of action because it allows the business analyst to continue with the planned elicitation activities and avoid delays or disruptions to the project schedule. It also ensures that the non-response is communicated and escalated to the appropriate authority, who can take the necessary actions to resolve the issue and ensure the involvement and input of the legal SME in the future workshops.
A business analyst (BA) is informing stakeholders about the importance of quality when eliciting requirements. What characteristic describes a quality requirement?
A quality requirement must be consistent, meaning it should not conflict with any other requirements, assumptions, or constraints. It should align with the overall objectives and constraints of the project, ensuring that all requirements work together harmoniously without contradictions or ambiguities.
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?
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.Reference: 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 ...
A business analyst (BA) is examining the relationships between elicited requirements on a project. What quality criteria must be satisfied when the BA is defining requirements relationships?
Comprehensive and Detailed Requirementsrelationships must be necessaryto ensure that each requirementlogically contributes to the overall solutionwithout unnecessary dependencies.
BABOK Guide (Chapter 5.1 - Trace Requirements)states thatdefining necessary relationships ensures that dependencies are valid and avoid redundant or irrelevant links.
Source (Option A)identifies requirement origins but does not determine relationship validity.
Complexity (Option B)describes difficulty but is not a requirement relationship criterion.
Priority (Option D)ranks requirements but does not define their relationships.
A business owner has marked certain requirements as high priority for the upcoming release. After performing some analysis, the project team concluded that some of these requirements are not actually high priority and can be implemented in later releases. How should the project team proceed with prioritizing requirements?
Comprehensive and Detailed Thebusiness owner must be consultedto discuss trade-offs andensure that prioritization aligns with business needs and constraints.
BABOK Guide (Chapter 5.1 - Prioritize Requirements)states thatprioritization should involve collaboration between business and project teams to balance feasibility and business value.
Implementing requirements based on team opinion (Option A)disregards business input.
Executing all requirements as identified by the business owner (Option B)ignores feasibility constraints.
Re-ranking without consultation (Option C)may result in misalignment with stakeholder expectations.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Lenny
2 months agoKenneth
3 months agoParis
3 months agoJerry
4 months agoJanessa
4 months agoEmiko
4 months agoGeraldine
5 months agoKrissy
5 months agoTamra
5 months agoMacy
5 months agoTheron
6 months agoPenney
6 months agoVeronika
6 months agoAlecia
6 months agoMelvin
7 months agoDiego
7 months agoTrina
7 months agoYaeko
7 months agoLetha
7 months agoJanine
7 months agoCarlee
8 months agoLorean
8 months agoMertie
8 months agoJame
9 months agoVilma
9 months agoFranchesca
9 months agoMary
9 months agoAja
9 months agoFernanda
10 months agoBrande
10 months agoBenton
11 months agoAudry
12 months agoKimberely
12 months agoRodrigo
12 months agoTawanna
1 years ago