First 50 of 190 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Integrated subject knowledge, evidence and application
According to the BABOK Guide, what is the primary purpose of business analysis?
- To write software requirements for development teams
- To enable change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders Correct answer.
- To perform quality assurance testing on delivered solutions
- To manage project timelines and deliverables
Explanation
The BABOK Guide defines business analysis as the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders. This is broader than just writing requirements or managing projects. Exam tip: Remember that business analysis is about enabling change and delivering value, not just documentation.
Question 2Integrated subject knowledge, evidence and application
Which of the following is NOT one of the six knowledge areas defined in the BABOK Guide?
- Solution Evaluation
- Project Management Correct answer.
- Elicitation and Collaboration
- Strategy Analysis
Explanation
The six BABOK Guide v3 knowledge areas are: Business Analysis Planning and Monitoring, Elicitation and Collaboration, Requirements Life Cycle Management, Strategy Analysis, Requirements Analysis and Design Definition, and Solution Evaluation. Project Management is a separate discipline and not a BABOK knowledge area. Exam tip: The current ECBA exam (effective July 21, 2025) is organized into nine domains -- three foundational domains plus the six BACCM core concepts (Change, Need, Solution, Stakeholder, Value, Context) -- rather than the BABOK knowledge areas, but the underlying knowledge-area content from BABOK v3 is still tested. Memorize all six knowledge areas and the tasks within them.
Question 3Integrated subject knowledge, evidence and application
In the BABOK Guide, what is a 'stakeholder'?
- A group or individual with a relationship to the change, the need, or the solution Correct answer.
- The business analyst assigned to the project
- The end user of the software application
- Only the project sponsor who funds the initiative
Explanation
A stakeholder is defined as a group or individual with a relationship to the change, the need, or the solution. This is a broad definition that includes sponsors, end users, developers, regulators, and many others. Exam tip: The BABOK definition of stakeholder is intentionally broad -- anyone affected by or who can affect the change is a stakeholder.
Question 4Integrated subject knowledge, evidence and application
What is the difference between a 'need' and a 'requirement' in the BABOK Guide?
- A need is a problem or opportunity, while a requirement is a usable representation of a need Correct answer.
- A need is documented formally, while a requirement is informal
- There is no difference; the terms are interchangeable
- A requirement comes before a need in the analysis process
Explanation
In BABOK terminology, a need is a problem or opportunity to be addressed, while a requirement is a usable representation of a need. Requirements provide the detail necessary to evaluate, build, or acquire a solution. Exam tip: Needs are high-level (problems/opportunities), while requirements are the detailed, actionable representations of those needs.
Question 5Integrated subject knowledge, evidence and application
Which term describes the internal and external factors that influence an enterprise's ability to change?
- Context Correct answer.
- Dependencies
- Assumptions
- Constraints
Explanation
Context refers to the circumstances that influence, are influenced by, and provide understanding of the change. It includes internal factors (organizational culture, capabilities) and external factors (market conditions, regulations). Exam tip: Context is broader than constraints -- it encompasses everything that provides understanding of the change environment.
Question 6Integrated subject knowledge, evidence and application
The BABOK Guide identifies several underlying competencies for business analysts. Which of the following is one of them?
- Analytical thinking and problem solving Correct answer.
- Network engineering
- Database administration
- Software development
Explanation
Analytical thinking and problem solving is one of the underlying competencies identified in the BABOK Guide. Others include behavioral characteristics, business knowledge, communication skills, interaction skills, and tools and technology. Exam tip: Underlying competencies are soft skills and thinking abilities, not technical specializations like coding or database administration.
Question 7Integrated subject knowledge, evidence and application
What does the BABOK Guide refer to as 'Business Analysis Information'?
- Data stored in the enterprise's database systems
- Any kind of information at any level of detail that is used as an input to or output from business analysis work Correct answer.
- Only formal documents created by the business analyst
- Financial reports used for budget planning
Explanation
Business Analysis Information is broadly defined as any kind of information at any level of detail that is used as an input to or output from business analysis work. It can be formal or informal, detailed or high-level, and in any format. Exam tip: Business analysis information is not limited to formal documents -- it includes models, notes, conversations, and any other relevant data.
Question 8Integrated subject knowledge, evidence and application
In the BABOK Guide, what is a 'change' in the context of business analysis?
- The act of transformation in response to a need Correct answer.
- An update to the business analyst's documentation
- A modification to a project schedule
- A defect report submitted by end users
Explanation
In the BABOK Guide, change is defined as the act of transformation in response to a need. Business analysis exists to enable change in an enterprise. The change could be strategic, tactical, or operational in nature. Exam tip: Change is central to business analysis -- the entire discipline exists to facilitate the transformation from a current state to a desired future state.
Question 9Integrated subject knowledge, evidence and application
What is the relationship between a 'solution' and 'value' in the BABOK Guide?
- Solutions always generate financial value immediately
- Value must be calculated before any solution can be proposed
- A solution is a specific way of satisfying a need, and value is the worth of the solution to stakeholders Correct answer.
- Solutions and value are unrelated concepts in business analysis
Explanation
A solution is a specific way of satisfying one or more needs in a context, and value is the worth, importance, or usefulness of something to a stakeholder. Solutions should be evaluated based on the value they deliver to stakeholders. Exam tip: Value is subjective -- different stakeholders may perceive different value from the same solution.
Question 10Integrated subject knowledge, evidence and application
Which of the following BEST describes the BABOK Guide's concept of a 'domain'?
- The technical infrastructure supporting the solution
- The geographic region where the enterprise operates
- A website address used by the enterprise
- The area of knowledge or activity being analyzed Correct answer.
Explanation
A domain is the area of knowledge or activity that defines a set of requirements. Understanding the domain is essential for effective business analysis. It includes the business processes, rules, and terminology specific to that area. Exam tip: Domain knowledge is critical for a business analyst -- you need to understand the subject area you are analyzing.
Question 11Integrated subject knowledge, evidence and application
What are the three levels of requirements classification in the BABOK Guide?
- Mandatory, optional, and desirable requirements
- Business, stakeholder, and solution requirements Correct answer.
- Current, transitional, and future requirements
- High, medium, and low priority
Explanation
The BABOK Guide classifies requirements into business requirements, stakeholder requirements, and solution requirements (which are further divided into functional and non-functional). Additionally, transition requirements form a fourth category. Exam tip: Know the requirement classification hierarchy -- business requirements are the highest level, followed by stakeholder, then solution requirements.
Question 12Integrated subject knowledge, evidence and application
What is a 'transition requirement' in the BABOK Guide?
- A requirement that applies only during the testing phase
- A requirement that is still in draft and not yet approved
- A requirement that describes capabilities the solution must have to facilitate the transition from the current state to the future state Correct answer.
- A requirement that defines how the solution will perform under load
Explanation
Transition requirements describe capabilities the solution must have to facilitate the transition from the current state to the future state, but that are not needed once the transition is complete. Examples include data migration, training, and parallel operations. Exam tip: Transition requirements are temporary -- they are only needed during the changeover period, not in the final solution.
Question 13Integrated subject knowledge, evidence and application
According to the BABOK Guide, which perspective views business analysis work through iterative, continuous delivery cycles?
- Operational perspective
- Agile perspective Correct answer.
- Predictive perspective
- Business intelligence perspective
Explanation
The Agile perspective views business analysis through iterative and incremental delivery cycles, emphasizing collaboration, working solutions, and continuous improvement. The predictive (or plan-driven) perspective follows a more sequential approach. Exam tip: The BABOK Guide recognizes multiple perspectives (Agile, Business Intelligence, Information Technology, Business Architecture, Business Process Management) for applying BA practices.
Question 14Integrated subject knowledge, evidence and application
What is a 'functional requirement' as defined by the BABOK Guide?
- A requirement that defines how many users the system must support
- A requirement that specifies the technology platform to be used
- A requirement that describes a capability that a solution must have in terms of behavior or information it will manage Correct answer.
- A requirement that describes a quality attribute of the solution
Explanation
A functional requirement describes a capability that a solution must have in terms of the behavior and information that the solution will manage. It defines what the system should do. Non-functional requirements, by contrast, describe quality attributes. Exam tip: Functional = what the system does. Non-functional = how well the system does it (performance, security, usability, etc.).
Question 15Integrated subject knowledge, evidence and application
Which of the following BEST describes a 'non-functional requirement'?
- A requirement that is not important to the project
- A requirement that captures a condition or quality the solution must meet, such as performance or security Correct answer.
- A requirement that describes a business process
- A requirement that has been rejected by stakeholders
Explanation
Non-functional requirements capture conditions or qualities the solution must meet, such as performance, reliability, security, usability, and scalability. They describe how well the system performs its functions rather than what functions it performs. Exam tip: Non-functional requirements are also called quality of service requirements or supplementary requirements.
Question 16Integrated subject knowledge, evidence and application
In the BABOK Guide, what does 'enterprise' refer to?
- The IT department within an organization
- Only large corporations with more than 500 employees
- A software application used for enterprise resource planning
- A system of one or more organizations and the solutions they use to pursue a shared set of common goals Correct answer.
Explanation
In BABOK terminology, an enterprise is a system of one or more organizations and the solutions they use to pursue a shared set of common goals. It can refer to a whole company, a department, or even a cross-organizational system. Exam tip: Enterprise in the BABOK context is flexible in scope -- it could be as small as a department or as large as multiple organizations working together.
Question 17Integrated subject knowledge, evidence and application
What is the primary purpose of the Business Analysis Planning and Monitoring knowledge area?
- To organize and coordinate business analysis activities and stakeholder engagement Correct answer.
- To define the strategic goals of the organization
- To gather information from stakeholders through interviews
- To evaluate whether a solution meets business needs
Explanation
Business Analysis Planning and Monitoring focuses on organizing and coordinating the business analysis effort, including planning the approach, engaging stakeholders, governing BA work, and managing BA information. Exam tip: This knowledge area is about how you plan and manage your BA work, not the actual analysis itself.
Question 18Integrated subject knowledge, evidence and application
Which task in Business Analysis Planning and Monitoring involves identifying stakeholders and understanding their characteristics?
- Plan Stakeholder Engagement Correct answer.
- Identify Business Analysis Performance Improvements
- Plan Business Analysis Approach
- Plan Business Analysis Governance
Explanation
Plan Stakeholder Engagement involves identifying stakeholders, understanding their needs and characteristics, determining their level of involvement, and planning how to collaborate with them throughout the initiative. Exam tip: Stakeholder engagement planning goes beyond just listing stakeholders -- it includes analyzing their influence, authority, and communication preferences.
Question 19Integrated subject knowledge, evidence and application
What does 'Plan Business Analysis Approach' involve?
- Developing the test plan for solution validation
- Creating the project charter for the initiative
- Defining how business analysis work will be performed, including the approach, activities, timing, and deliverables Correct answer.
- Selecting the tools and techniques for requirements elicitation only
Explanation
Plan Business Analysis Approach involves defining how business analysis work will be performed, including determining the overall approach (predictive, adaptive, or hybrid), timing, activities, and deliverables. It sets the foundation for all other BA activities. Exam tip: The BA approach can be plan-driven (predictive), change-driven (adaptive/agile), or a hybrid of both.
Question 20Integrated subject knowledge, evidence and application
In the context of BA Planning, what is a RACI matrix used for?
- Prioritizing requirements by business value
- Defining stakeholder roles as Responsible, Accountable, Consulted, or Informed Correct answer.
- Tracking defects found during testing
- Mapping business processes to system functions
Explanation
A RACI matrix is a tool used to define stakeholder roles and responsibilities. RACI stands for Responsible (does the work), Accountable (ultimately answerable), Consulted (provides input), and Informed (kept up to date). Exam tip: In a RACI matrix, only one person should be Accountable for each task, but multiple people can be Responsible, Consulted, or Informed.
Question 21Integrated subject knowledge, evidence and application
Which task within Business Analysis Planning and Monitoring focuses on managing how changes to requirements are handled?
- Plan Stakeholder Engagement
- Identify Business Analysis Performance Improvements
- Plan Business Analysis Information Management
- Plan Business Analysis Governance Correct answer.
Explanation
Plan Business Analysis Governance defines how decisions are made about requirements and designs, including the change control process, prioritization approach, and approval processes. It establishes the rules for managing changes. Exam tip: Governance is about decision-making authority and processes -- who approves requirements, how changes are managed, and how conflicts are resolved.
Question 22Integrated subject knowledge, evidence and application
What is the purpose of 'Plan Business Analysis Information Management'?
- To manage the project budget and timeline
- To train stakeholders on using the new solution
- To create the enterprise data architecture
- To define how business analysis information will be stored, accessed, and used Correct answer.
Explanation
Plan Business Analysis Information Management defines how BA information (requirements, models, designs) will be organized, stored, accessed, and integrated. This includes determining the level of formality, traceability needs, and repository approach. Exam tip: Information management covers storage, access, version control, and reuse of BA artifacts throughout the initiative.
Question 23Integrated subject knowledge, evidence and application
When a business analyst reviews the effectiveness of their BA processes and identifies areas for improvement, which task are they performing?
- Plan Business Analysis Governance
- Plan Stakeholder Engagement
- Identify Business Analysis Performance Improvements Correct answer.
- Plan Business Analysis Approach
Explanation
Identify Business Analysis Performance Improvements involves monitoring and assessing the effectiveness of BA processes and deliverables, then recommending improvements. This is a continuous improvement activity. Exam tip: This task is about improving the BA process itself, not improving the business solution -- it is a meta-activity focused on BA effectiveness.
Question 24Integrated subject knowledge, evidence and application
A business analyst is deciding whether to use a plan-driven or change-driven approach for a new initiative. Which factor would MOST favor a change-driven approach?
- Requirements are expected to evolve and stakeholder feedback is needed frequently Correct answer.
- Regulatory compliance requires a formal sign-off process
- Requirements are well-understood and stable
- The organization requires extensive upfront documentation
Explanation
A change-driven (adaptive/agile) approach is most appropriate when requirements are expected to change, stakeholders need to provide frequent feedback, and the solution will be delivered incrementally. Plan-driven approaches are better when requirements are stable and formal documentation is required. Exam tip: Change-driven approaches embrace uncertainty and welcome changing requirements, while plan-driven approaches try to minimize change.
Question 25Integrated subject knowledge, evidence and application
What is the primary output of the 'Plan Stakeholder Engagement' task?
- Business case document
- A project charter
- Stakeholder engagement approach Correct answer.
- Requirements management plan
Explanation
The primary output of Plan Stakeholder Engagement is the stakeholder engagement approach, which documents how stakeholders will be involved in business analysis activities, including their roles, communication needs, and collaboration strategies. Exam tip: The stakeholder engagement approach is different from a stakeholder list -- it describes how you will work with stakeholders, not just who they are.
Question 26Integrated subject knowledge, evidence and application
A business analyst wants to assess stakeholder influence and interest to determine engagement strategies. Which tool is MOST appropriate?
- Stakeholder map or power/interest grid Correct answer.
- Entity relationship diagram
- Fishbone diagram
- Gantt chart
Explanation
A stakeholder map or power/interest grid is used to plot stakeholders based on their level of influence/power and interest in the initiative. This helps determine the appropriate engagement strategy for each stakeholder group. Exam tip: High power + high interest stakeholders need active management, while low power + low interest stakeholders just need monitoring.
Question 27Integrated subject knowledge, evidence and application
What is 'traceability' in the context of business analysis information management?
- The method of tracking employee performance
- The process of debugging software code
- The ability to track relationships between requirements and other BA artifacts across the requirements life cycle Correct answer.
- The ability to track project costs against budget
Explanation
Traceability is the ability to track the relationships between requirements and other BA artifacts (such as business objectives, designs, and test cases) across the life cycle. It helps ensure all requirements are addressed and supports impact analysis. Exam tip: Traceability works in multiple directions -- forward (to design and tests), backward (to business objectives), and laterally (to related requirements).
Question 28Integrated subject knowledge, evidence and application
In BA Planning, what is the purpose of defining the 'level of formality' for BA deliverables?
- To decide how rigorously BA activities and outputs will be documented and controlled based on context Correct answer.
- To select the software tools for development
- To determine the budget for the project
- To establish the dress code for stakeholder meetings
Explanation
The level of formality determines how rigorously business analysis activities and outputs will be documented and controlled. Factors include project complexity, risk, organizational culture, and regulatory requirements. High-risk initiatives typically require more formal documentation. Exam tip: There is no one-size-fits-all formality level -- the appropriate level depends on the specific initiative's context and risk.
Question 29Integrated subject knowledge, evidence and application
Which metric could a business analyst use to measure the effectiveness of their business analysis work?
- Amount of overtime worked by the development team
- Frequency and severity of requirements defects found during later stages Correct answer.
- Number of lines of code written
- Number of emails sent to stakeholders
Explanation
The frequency and severity of requirements defects found during later stages (like development or testing) is a meaningful metric for BA effectiveness. Fewer defects suggest higher-quality requirements work. Exam tip: Good BA performance metrics focus on the quality and completeness of requirements, not on activity volume like number of documents produced.
Question 30Integrated subject knowledge, evidence and application
A business analyst needs to determine which stakeholders have decision-making authority over requirements. Which planning task addresses this?
- Plan Business Analysis Information Management
- Identify Business Analysis Performance Improvements
- Plan Business Analysis Governance Correct answer.
- Plan Business Analysis Approach
Explanation
Plan Business Analysis Governance addresses how decisions about requirements and designs are made, including who has approval authority. It establishes the decision-making framework for the initiative. Exam tip: Governance covers decision rights, prioritization processes, change control, and approval authority -- all the 'who decides what' questions.
Question 31Integrated subject knowledge, evidence and application
What is 'elicitation' in business analysis?
- The process of testing the solution against requirements
- The process of writing requirements documents
- The process of deploying the solution to production
- The process of drawing out or receiving information from stakeholders and other sources Correct answer.
Explanation
Elicitation is the process of drawing out, exploring, and identifying information relevant to the change. It involves receiving information from stakeholders, researching existing documentation, and experimenting. Exam tip: Elicitation is about discovering information, not just documenting it. It goes beyond interviews to include research, observation, and experimentation.
Question 32Integrated subject knowledge, evidence and application
Which of the following is an elicitation technique that involves watching stakeholders perform their work in their natural environment?
- Brainstorming
- Prototyping
- Document analysis
- Observation Correct answer.
Explanation
Observation involves watching stakeholders perform their work in their natural environment to understand current processes, identify inefficiencies, and discover unstated requirements. It can be passive (just watching) or active (asking questions while observing). Exam tip: Observation is especially useful when stakeholders have difficulty articulating their work processes or when documented procedures differ from actual practice.
Question 33Integrated subject knowledge, evidence and application
Which three tasks make up the elicitation portion of the Elicitation and Collaboration knowledge area?
- Plan Elicitation, Conduct Elicitation, Document Elicitation Results
- Prepare for Elicitation, Conduct Elicitation, Confirm Elicitation Results Correct answer.
- Schedule Elicitation, Perform Elicitation, Review Elicitation Outcomes
- Initiate Elicitation, Execute Elicitation, Close Elicitation
Explanation
The three elicitation tasks are Prepare for Elicitation (planning the activity), Conduct Elicitation (performing the elicitation), and Confirm Elicitation Results (validating that elicited information is correct and understood). The full Elicitation and Collaboration knowledge area actually has five tasks -- these three plus Communicate Business Analysis Information and Manage Stakeholder Collaboration. Exam tip: Remember the three elicitation tasks as Prepare, Conduct, Confirm, but do not forget that the broader knowledge area also covers communication and ongoing stakeholder collaboration.
Question 34Integrated subject knowledge, evidence and application
Which elicitation technique involves a structured group creativity method where participants generate ideas without criticism?
- Brainstorming Correct answer.
- Surveys
- Focus groups
- Interviews
Explanation
Brainstorming is a group creativity technique where participants generate as many ideas as possible without criticism or evaluation during the idea generation phase. The goal is quantity of ideas first, with evaluation happening afterward. Exam tip: The key rule of brainstorming is to defer judgment -- no idea should be criticized during the generation phase.
Question 35Integrated subject knowledge, evidence and application
What is the purpose of 'Confirm Elicitation Results'?
- To check that the elicited information is correctly and consistently understood by the stakeholders Correct answer.
- To present the solution design to the development team
- To get stakeholder signatures on the final requirements document
- To close out the project after go-live
Explanation
Confirm Elicitation Results ensures that the information gathered during elicitation is correctly understood and accurately recorded. It involves comparing elicited results with other information sources and getting stakeholder confirmation. Exam tip: Confirming results is not the same as formal approval -- it is about ensuring understanding and accuracy before further analysis.
Question 36Integrated subject knowledge, evidence and application
A business analyst is reviewing existing system documentation and process manuals to understand the current state. Which elicitation technique is being used?
- Document analysis Correct answer.
- Interface analysis
- Workshops
- Prototyping
Explanation
Document analysis involves reviewing existing documentation such as process manuals, system documentation, business rules, contracts, and other artifacts to extract relevant information. It is useful for understanding the current state. Exam tip: Document analysis is often a starting point for elicitation -- it helps the BA prepare for other techniques like interviews and workshops.
Question 37Integrated subject knowledge, evidence and application
Which elicitation technique is MOST effective for collecting information from a large number of geographically dispersed stakeholders?
- Observation
- Workshops
- Surveys or questionnaires Correct answer.
- Focus groups
Explanation
Surveys and questionnaires are the most effective technique for collecting information from a large number of geographically dispersed stakeholders because they can be distributed widely, completed asynchronously, and analyzed quantitatively. Exam tip: Surveys are best for gathering quantitative data from many people, but they lack the depth of techniques like interviews or workshops.
Question 38Integrated subject knowledge, evidence and application
What is a key benefit of using prototyping as an elicitation technique?
- It eliminates the need for requirements documentation
- It produces the final production-ready solution
- It helps stakeholders visualize the solution and provide concrete feedback Correct answer.
- It replaces the need for user acceptance testing
Explanation
Prototyping helps stakeholders visualize the proposed solution and provide concrete, actionable feedback. It is especially useful when stakeholders have difficulty expressing requirements in abstract terms. Prototypes can be throwaway (for exploration) or evolutionary (refined into the final product). Exam tip: Prototypes are communication tools -- they bridge the gap between abstract requirements and tangible solutions.
Question 39Integrated subject knowledge, evidence and application
During an elicitation workshop, the business analyst notices that one dominant stakeholder is preventing others from sharing their views. What is the BEST course of action?
- Use facilitation techniques to encourage participation from all attendees Correct answer.
- End the workshop and schedule individual interviews
- Ask the dominant stakeholder to leave the meeting
- Ignore the issue and continue with the dominant stakeholder's input
Explanation
The business analyst should use facilitation techniques to manage group dynamics and encourage participation from all attendees. Techniques include round-robin input, silent brainstorming, or directly inviting quieter participants to share. Exam tip: Facilitation is a core BA skill -- managing group dynamics to ensure all voices are heard leads to better and more complete requirements.
Question 40Integrated subject knowledge, evidence and application
What is 'interface analysis' used for in elicitation?
- Assessing the communication style between team members
- Identifying the interactions between solutions, systems, or organizational units Correct answer.
- Evaluating the visual design of stakeholder presentations
- Analyzing the user interface design of a website
Explanation
Interface analysis is used to identify the interactions, data flows, and touch points between solutions, systems, hardware, or organizational units. It helps define how components connect and exchange information. Exam tip: Interface analysis looks at boundaries -- where one system, process, or organization ends and another begins, and what passes between them.
Question 41Integrated subject knowledge, evidence and application
Which elicitation technique involves a structured conversation between the business analyst and one or more stakeholders to gather detailed information?
- Benchmarking
- Interview Correct answer.
- Survey
- Observation
Explanation
An interview is a structured or semi-structured conversation between a business analyst and a stakeholder to gather detailed information about needs, problems, and requirements. Interviews allow for follow-up questions and deeper exploration of topics. Exam tip: Interviews can be structured (predetermined questions), semi-structured (guided but flexible), or unstructured (open-ended conversation).
Question 42Integrated subject knowledge, evidence and application
What distinguishes a 'workshop' from a regular meeting in the context of business analysis?
- Workshops have no agenda and allow free discussion
- Workshops are facilitated, structured sessions with defined objectives to achieve a specific outcome in a focused timeframe Correct answer.
- Workshops are always virtual while meetings are in-person
- Workshops only involve senior management
Explanation
A workshop is a facilitated, structured session with clearly defined objectives designed to achieve a specific outcome within a focused timeframe. Unlike regular meetings, workshops have a facilitator, defined activities, and targeted deliverables. Exam tip: The key differentiators of a workshop are: a dedicated facilitator, structured activities, defined objectives, and a focused timeframe to produce specific outputs.
Question 43Integrated subject knowledge, evidence and application
What is the primary purpose of the Requirements Life Cycle Management knowledge area?
- To evaluate whether the solution meets the original business needs
- To manage and maintain requirements and design information from inception to retirement Correct answer.
- To develop the solution based on requirements
- To gather requirements from stakeholders
Explanation
Requirements Life Cycle Management focuses on managing and maintaining requirements and design information throughout their entire life cycle, from initial creation through retirement. This includes tracing, maintaining, prioritizing, assessing changes, and approving requirements. Exam tip: Requirements have a life cycle independent of the project -- they can be reused, modified, or retired over time.
Question 44Integrated subject knowledge, evidence and application
Which task in Requirements Life Cycle Management involves tracking relationships among requirements and other artifacts?
- Assess Requirements Changes
- Maintain Requirements
- Trace Requirements Correct answer.
- Prioritize Requirements
Explanation
Trace Requirements involves tracking the relationships between requirements, designs, solution components, and other artifacts. Traceability ensures that each requirement can be linked back to its origin and forward to the solution components that implement it. Exam tip: Traceability supports impact analysis -- when a requirement changes, you can trace which designs, tests, and components are affected.
Question 45Integrated subject knowledge, evidence and application
What does 'Maintain Requirements' involve?
- Ensuring requirements remain accurate, current, and valid throughout the life cycle Correct answer.
- Writing requirements for the first time
- Assigning requirements to developers for implementation
- Deleting old requirements from the repository
Explanation
Maintain Requirements ensures that requirements and designs remain accurate, current, and valid over their entire life cycle. This includes keeping them in the correct state, resolving conflicts, and ensuring ongoing relevance. Exam tip: Requirements maintenance is ongoing -- requirements may need updates as the business context changes, even after initial approval.
Question 46Integrated subject knowledge, evidence and application
Which prioritization technique assigns requirements to one of four categories: Must have, Should have, Could have, or Won't have?
- Kano analysis
- Timeboxing
- Weighted ranking
- MoSCoW analysis Correct answer.
Explanation
MoSCoW analysis categorizes requirements into Must have (essential), Should have (important but not vital), Could have (desirable), and Won't have (explicitly excluded for now). It is widely used in agile and timeboxed environments. Exam tip: MoSCoW is especially useful in time-constrained projects because it clearly separates what must be delivered from what is negotiable.
Question 47Integrated subject knowledge, evidence and application
A stakeholder requests a change to an approved requirement. What should the business analyst do FIRST?
- Escalate the change to the project sponsor
- Assess the impact of the change on other requirements, the solution, and the project Correct answer.
- Reject the change because requirements are already approved
- Immediately implement the change
Explanation
The business analyst should first assess the impact of the proposed change on other requirements, the solution, timeline, and resources. This impact analysis informs the decision of whether to accept, modify, or reject the change. Exam tip: Never accept or reject a change without first performing an impact analysis -- understanding the ripple effects is essential for informed decision-making.
Question 48Integrated subject knowledge, evidence and application
What is a 'requirements state' in the context of Requirements Life Cycle Management?
- A condition or status that a requirement can be in at a point in its life cycle Correct answer.
- The US state where the requirement applies legally
- The physical location where requirements documents are stored
- The programming language used to implement the requirement
Explanation
A requirements state describes the condition or status of a requirement at any point during its life cycle. Common states include: proposed, active, reviewed, approved, implemented, verified, deferred, cancelled, and obsolete. Exam tip: Tracking requirements states helps ensure that no requirement falls through the cracks and that each requirement receives appropriate attention.
Question 49Integrated subject knowledge, evidence and application
Which of the following is a purpose of 'Approve Requirements'?
- To mark the project as complete
- To ensure the business analyst has completed all elicitation activities
- To reach agreement among stakeholders that requirements are ready for use as a basis for further work Correct answer.
- To sign the project contract with the vendor
Explanation
Approve Requirements ensures stakeholders reach agreement that the requirements and designs are ready to be used as a basis for further work, such as solution development or procurement. Approval indicates the requirements are sufficiently defined and agreed upon. Exam tip: Approval does not mean requirements are frozen forever -- changes can still occur but must go through the change control process.
Question 50Integrated subject knowledge, evidence and application
What type of traceability relationship shows which higher-level requirement a detailed requirement was derived from?
- Derive traceability Correct answer.
- Lateral traceability
- Implementation traceability
- Forward traceability
Explanation
Derive traceability shows the relationship between a requirement and another requirement that was derived from it. For example, a business requirement may be the source of multiple stakeholder requirements. This type of traceability helps understand the origin and context of detailed requirements. Exam tip: Derive relationships help answer 'where did this requirement come from?' and 'what detailed requirements support this high-level need?'