PC-BA-FBA-20 BCS Foundation Certificate in Business Analysis V4.1 Free Practice Exam Questions (2026 Updated)

The Use Case Diagram is a conceptual model that shows the interaction between users (actors) and the required features (use cases) of the system. In an Agile context, use cases provide a high-level view of the system ' s intended functionality, which can be directly mapped to Epics and subsequently decomposed into lower-level User Stories. The use case diagram helps the team understand the scope and the user ' s interaction paths, making it an excellent visual tool for managing and breaking down the product backlog (of user stories) into manageable chunks. The other options are too technical (A, D) or focus only on object state (B).

(Reference: BCS Requirements Engineering / BCS Agile – Use Case Modelling and Product Backlog Management)

Agile requirements validation ensures that requirements are clear, feasible, and actionable before they are implemented in an iteration. This aligns with Agile principles of delivering value incrementally and avoiding waste.

Key Considerations:

Accurate Estimation for Sprint Planning: While estimation is important, it is not the primary purpose of requirements validation.

Correctness of Backlog Items: Ensuring correctness is part of validation but applies to all backlog items, not just those allocated to an iteration.

Testing Requirements: Testing occurs during or after development, not as part of validation.

Readiness for Development: Validation ensures that requirements are well-defined, understood, and feasible before they are developed.

Evaluation of Each Option:

A. To ensure estimation for sprint planning is accurate: Estimation accuracy is important but not the primary purpose of validation. Conclusion: This is not correct .

B. To ensure any requirements added to the backlog are correct: Correctness applies to all backlog items, not just those allocated to an iteration. Conclusion: This is not correct .

C. To ensure that requirements allocated to an iteration have been tested: Testing occurs after development, not during validation. Conclusion: This is not correct .

D. To ensure any requirements allocated to an iteration are ready to be developed: This is the primary purpose of Agile requirements validation—to ensure requirements are clear, actionable, and feasible before development begins. Conclusion: This is correct .

Final Recommendation:

The purpose of Agile requirements validation is:

D. To ensure any requirements allocated to an iteration are ready to be developed.

To build an enterprise view of processes , we need a framework that provides a holistic understanding of how value is created and delivered across the organization.

Key Considerations:

Class Model: Represents objects and their relationships in software development, not enterprise processes.

Swimlane Diagram: Visualizes workflows and responsibilities within a process but does not provide an enterprise-wide view.

Value Chain Analysis: Analyzes the activities that create value for customers, providing a comprehensive view of enterprise processes.

Porter’s Five Forces Model: Analyzes industry competition and external factors, not internal processes.

Evaluation of Each Option:

A. Class model: A class model is used in object-oriented design and does not represent enterprise processes. Conclusion: This is not correct .

B. Swimlane diagram: While swimlane diagrams visualize workflows, they focus on specific processes rather than an enterprise-wide view. Conclusion: This is not correct .

C. Value chain analysis: Value chain analysis examines the activities that contribute to value creation, making it ideal for building an enterprise view of processes. Conclusion: This is correct .

D. Porter’s five forces model: This model analyzes external competitive forces and does not focus on internal processes. Conclusion: This is not correct .

Scenario analysis is an investigation technique used to explore and evaluate potential future scenarios or situations. It helps stakeholders understand how different factors might impact a business area or process.

Key Characteristics of Scenario Analysis:

Broad View: Scenario analysis provides a comprehensive understanding of the business area by considering multiple possible outcomes.

Prototyping Basis: The insights gained from scenario analysis can inform the development of prototypes.

Tacit Knowledge Identification: By exploring real-world scenarios, it helps uncover implicit knowledge embedded in business practices.

Testing Scripts: Scenario analysis is not directly involved in preparing test scripts, which are typically created during the testing phase.

Evaluation of Each Option:

A. Provides a broad view of the business area under investigation: Scenario analysis evaluates multiple possibilities, offering a broad perspective. Conclusion: This is true .

B. Provides a basis for developing subsequent prototypes: Insights from scenario analysis can guide prototype development. Conclusion: This is true .

C. Helps identify tacit knowledge used in business practice: Exploring scenarios uncovers hidden knowledge and practices. Conclusion: This is true .

D. Helps prepare the scripts that will be used to test the delivered solution: Preparing test scripts is part of testing activities, not scenario analysis. Conclusion: This is false .

Critical Success Factors (CSFs) are the few areas in which an organisation must achieve consistently high performance to meet its mission and strategic goals. To monitor whether a CSF is being achieved, a BA defines quantitative measures of performance, which are known as Key Performance Indicators (KPIs). KPIs are the specific, measurable metrics used to track and assess the success of an activity or the progress towards an objective. For example, if a CSF is " Excellent Customer Service, " a corresponding KPI might be " Average Call Waiting Time (less than 60 seconds) " —a clear, quantitative measure. While the Balanced Business Scorecard (D) is a framework that uses CSFs and KPIs, the specific quantitative measures themselves are the KPIs. Objectives (B) are the desired outcomes, not the measure of the outcome.

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice – Strategic Context, CSFs and KPIs)

Here are the next five questions:

The concern of consumers about unnecessary packaging is an external factor that influences the organisation. The appropriate technique for systematically analysing these external macro-environmental factors is PESTLE analysis. PESTLE stands for Political, Economic, Sociological, Technological, Legal, and Environmental factors. The increasing consumer concern about packaging falls clearly under the Sociological or Environmental categories of the PESTLE framework. This technique helps the business analyst identify trends and issues arising from outside the organisation that may create a business need or risk, which then drives strategic change. The other options are incorrect: a Power/Interest grid is for stakeholder management; Boston Box (BCG Matrix) is for product portfolio management; and a Resource Audit is for internal analysis of resources.

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice – Strategic Analysis, External Environment Analysis)

In an iterative or Agile lifecycle, requirements are not defined entirely upfront but are explored and refined just-in-time, immediately prior to implementation. The stage where the detailed solution requirements (functional and non-functional) are elaborated, modeled, and defined—ready for construction—is the Develop solution stage (often referred to as the Implementation or Construction phase of an iteration/sprint). The detailed work of defining, modelling, and validating the specific requirements happens as a preparatory step for the actual build, distinguishing it from the preceding planning phase (C) or the upstream strategic work (A, B).

(Reference: BCS Requirements Engineering – Lifecycle Models, Iterative Development)

The technique focused on analyzing the fit between an organisation ' s offerings and customer needs, specifically examining the combination of product and service attributes, the company ' s image, and the customer relationship, is the Value Proposition. The Value Proposition describes the unique benefits, value, and experience that a company promises to deliver to its customers to satisfy their needs and wants better than the competition. It ' s a critical tool for ensuring that the business improvement efforts are truly valuable from a customer ' s perspective. Porter ' s Five Forces and SWOT analysis are macro-strategic tools, and SIPOC is a process analysis technique.

(Reference: BCS Business Analysis Practice – Improving Business Services and Processes, Value Proposition)

A class model is used to represent business objects or data entities and the relationships between them. Its core elements include classes, attributes, and associations. A class represents a type of business object, such as Customer, Order, or Product. Attributes describe the information held about each class, such as customer name or order date. Associations show how classes relate to each other, for example, a Customer places an Order. Dataflow is not an element of a class model. Dataflow belongs more naturally to process modelling or data flow diagrams, where the analyst shows how information moves between processes, actors, or systems. Since the question asks for the item that is NOT part of a class model, the correct answer is Dataflow.

The Project Sponsor is the senior executive or manager who owns the project, champions it, secures funding, and holds ultimate accountability for the benefits. While they are the most important stakeholder and sign off on the requirements, they are typically NOT an active, day-to-day working member of the project team responsible for executing the Requirements Engineering activities. The Project Manager (A), Business Analyst (C), and Software Tester (D) are all core, active members of the project team with specific roles in managing, defining, and validating the requirements, respectively.

(Reference: BCS Requirements Engineering – Roles in Requirements Engineering)

The investigation technique best suited to achieve these outcomes is the Interview. A one-on-one interview provides a private and focused setting, which is essential for discussing confidential or politically sensitive issues that a stakeholder would not be comfortable raising in a group or on a written questionnaire. The personal interaction during an interview is the most effective way to build rapport with the stakeholder, leading to more open and honest communication. This deeper level of trust and detailed conversation is what allows the analyst to gain a richer appreciation of the political and cultural landscape of the business. Special purpose records, document analysis, and questionnaires are more impersonal and cannot provide the same level of qualitative insight or trust.

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice – Investigative Techniques, Interviews)

When documenting risks in a business case, it is essential to follow structured processes to ensure risks are appropriately identified, analyzed, and managed. Let’s evaluate each option again based on best practices outlined in the BCS Business Analysis Framework and other methodologies:

Key Considerations:

Risk Documentation: Risks must be recorded systematically to ensure they are visible, actionable, and traceable.

Ownership of Risks: Assigning ownership ensures accountability and clarity about who is responsible for monitoring and mitigating each risk.

Risk Management Lifecycle: The process typically involves identification, documentation, assessment, ownership assignment, and response planning.

Evaluation of Each Option:

A. Create a RAID log

A RAID log (Risks, Assumptions, Issues, and Dependencies) is a widely used tool in business analysis and project management for capturing and managing risks systematically.

It provides a centralized repository for tracking risks, assumptions, issues, and dependencies, ensuring that risks are documented comprehensively and transparently.

This aligns with best practices for risk management and is a critical first step in ensuring risks are appropriately recorded.

Conclusion: This is a must-do action.

B. Document the source of each risk

While documenting the source of each risk can provide valuable context, it is not a mandatory or primary step in the initial documentation phase.

Sources of risks are often identified during risk analysis or root cause analysis, which occurs after risks have been recorded.

Although useful, this step is secondary to creating a RAID log and assigning ownership.

Conclusion: This is not the most critical action at this stage.

C. Identify an owner for each risk

Assigning ownership for each risk is a fundamental part of risk management. Without clear ownership, risks may remain unmonitored or unaddressed.

Ownership ensures accountability and helps streamline communication and decision-making regarding risk mitigation strategies.

According to the BCS Business Analysis Framework , identifying risk owners is a key responsibility during the risk documentation process.

Conclusion: This is a must-do action.

D. Provide justification for each countermeasure identified

Justifying countermeasures is part of the risk response planning phase, which occurs after risks have been documented, assessed, and prioritized.

At this stage, John’s focus should be on identifying and recording risks, not on evaluating or justifying solutions.

Conclusion: This is not relevant at the documentation stage.

E. Impact assessment of each countermeasure identified

Similar to option D, impact assessments for countermeasures are conducted during the risk response planning phase, not during the initial documentation phase.

This step is premature and does not align with the immediate need to document risks.

Conclusion: This is not relevant at the documentation stage.

Final Recommendation:

Based on the BCS Business Analysis Framework and industry best practices, the two most appropriate actions for John are:

Create a RAID log (to systematically document risks).

Identify an owner for each risk (to ensure accountability and clarity).

These steps ensure that risks are appropriately recorded and managed, laying the foundation for effective risk management.

  To determine the appropriate stakeholder management strategies for Harvey, we need to analyze his role and level of interest at two points in time:

When the project started: Harvey was the Director of Operations and had little interest in the HR project because his focus was on operational projects.

Now that his role has changed: As the Director of HR, Harvey has inherited sponsorship of the HR project, making him a key stakeholder with high interest and influence.

Stakeholder Management Strategies:

Watch: This strategy is used for stakeholders with low interest and low influence. It involves monitoring their behavior without actively engaging them.

Constant active management: This strategy is used for stakeholders with high interest and high influence. It involves frequent communication and collaboration to ensure their needs and expectations are met.

Evaluation of Each Option:

A. Keep informed; Constant active management: " Keep informed " is appropriate for stakeholders with moderate interest but does not align with Harvey ' s initial lack of interest. Conclusion: This is not correct .

B. Ignore, Constant active management: Ignoring a stakeholder is inappropriate, especially for someone in a senior leadership role like Harvey. Conclusion: This is not correct .

C. Watch, Constant active management:

Initially, Harvey had low interest and low influence on the HR project, making " watch " an appropriate strategy.

After becoming the Director of HR and inheriting sponsorship, Harvey now requires " constant active management " due to his high interest and influence. Conclusion: This is the correct answer .

D. Constant active management, keep informed: This reverses the order of strategies and does not align with Harvey ' s initial lack of interest. Conclusion: This is not correct .

A RACI chart defines responsibility and involvement for tasks. “Responsible” identifies the person or role that performs the work. “Consulted” identifies people who provide input, advice, or specialist knowledge before or during completion of the task. If Alice is responsible for Task A and no one else is shown as consulted, the matrix indicates that Alice performs the task without formal consultation from other team members. Option A is wrong because “a lot of help” would normally be reflected by consulted or responsible roles. Option B is wrong because RACI does not show task sequence or dependencies. Option D is wrong because RACI does not rank task importance. It only clarifies roles and responsibilities. Therefore, option C is the correct conclusion.

The Stakeholder Wheel (or Stakeholder Interest Groupings) is a model used to categorize stakeholders in the strategic analysis phase, particularly for external environment analysis. This technique groups stakeholders based on their primary relationship to the organisation. The key groups included in the stakeholder wheel are Suppliers, Customers, Competitors, Partners, Owners (Shareholders), Regulators/Government, Media, and Employees/Trade Unions. Based on the options provided, the group that contains three valid, distinct categories from this standard model is Regulators, Auditors, Owners. While ' Auditors ' can be considered part of the ' Regulators ' or ' Owners ' (depending on their role), and ' Owners ' are often Shareholders, this option best reflects the high-level external interest groups used for broad strategic categorization compared to the internal focus of B or the mixed categories of A and C. The inclusion of Regulators and Owners is essential for any strategic stakeholder analysis.

(Reference: BCS Business Analysis Practice – Stakeholder Analysis, Stakeholder Wheel)

Kaplan and Norton ' s Balanced Business Scorecard is a strategic framework that evaluates organizational performance across four key perspectives: Financial, Customer, Internal Business Processes, and Learning and Growth . To determine which area has not been considered, we need to map the provided KPIs to these perspectives.

Mapping the KPIs:

The time to deliver orders for products: This relates to operational efficiency and falls under the Internal Business Process perspective.

Consumer satisfaction with products: This directly measures customer experience and falls under the Customer perspective.

Wastage in product production: This also relates to operational efficiency and falls under the Internal Business Process perspective.

The qualifications of production employees: This measures employee capabilities and development, falling under the Learning and Growth perspective.

Evaluating Each Perspective:

Financial: None of the provided KPIs address financial performance, such as revenue, profitability, or cost management. Conclusion: This perspective has not been considered .

Customer: Consumer satisfaction with products is a clear indicator of the Customer perspective. Conclusion: This perspective has been considered.

Internal Business Process: Both " time to deliver orders " and " wastage in production " relate to internal processes. Conclusion: This perspective has been considered.

Learning and Growth: The qualifications of production employees indicate employee development, which aligns with this perspective. Conclusion: This perspective has been considered.

Final Recommendation:

The Financial perspective has not been considered in the company’s KPIs.

Business analyst competencies are commonly grouped into personal qualities, business knowledge, and professional techniques. Personal qualities include communication, analytical thinking, facilitation, influencing, and relationship-building. Business knowledge covers understanding the organisation, industry, strategy, finance, processes, and business context. Professional techniques include modelling, requirements engineering, stakeholder analysis, investigation techniques, and business case development. IT skills may be useful for some business analysts, especially those working on digital or software-enabled change, but IT skills are not one of the three main competency groups. Treating IT skills as a core group would narrow the business analyst role too much, because business analysis is concerned with business change, not only technology delivery. Therefore, option D is not one of the three competency groups.

Workshops are structured meetings designed to achieve specific objectives through group participation. Regardless of the workshop ' s focus, collaboration is a fundamental goal.

Key Considerations:

Collaboration: Workshops bring stakeholders together to share ideas, solve problems, and make decisions collaboratively.

Reviewing the Business Case: While reviewing the business case may be a specific objective of some workshops, it is not a universal goal.

Creating Mind Maps and Process Models: These are tools or outputs of workshops, not overarching goals.

Brainstorming Ideas: Brainstorming is a technique used in workshops but is not the ultimate goal of all workshops.

Evaluation of Each Option:

A. Collaboration: Collaboration is the core purpose of workshops, enabling participants to work together effectively. Conclusion: This is correct .

B. Reviewing the business case: This is a specific objective, not a universal goal of all workshops. Conclusion: This is not correct .

C. Creating mind maps and process models: These are tools or outputs, not goals. Conclusion: This is not correct .

D. Brainstorming ideas: Brainstorming is a technique, not the overarching goal of all workshops. Conclusion: This is not correct .

Final Recommendation:

The goal of all workshops is:

A. Collaboration.

One of the core principles of business analysis is the continuous need for negotiation and consensus building, particularly when dealing with conflicting stakeholder perspectives and requirements. Business analysis actively seeks to negotiate and resolve these conflicts rather than avoiding them, which is a key part of establishing a shared understanding of the problem and the proposed solution. The other options contradict established BA principles: the principle is to find root causes, not symptoms (leading to superficial and ineffective solutions); to investigate and evaluate multiple options, not just solutions (ensuring the optimal change is selected); and to focus on business improvement as the driver for any necessary IT system change, not the other way around. The BA role necessitates working across competing interests to reach a successful outcome, making negotiation a fundamental principle.

(Reference: BCS Business Analysis Practice – Principles of Business Analysis / Analysing and Managing Stakeholders)