BCS BCS Foundation Certificate in Business Analysis V4.1 PC-BA-FBA-20 Exam Dumps: Updated Questions & Answers (July 2026)

The power/interest grid helps determine the appropriate stakeholder engagement strategy. Stakeholders with high power and high interest need constant active management because they can strongly influence the change and care about the outcome. Stakeholders with high power but low interest should usually be kept satisfied or kept onside. Stakeholders with low power and low interest are normally watched or monitored with minimal effort. “Keep informed” applies to stakeholders with low power but high interest. These stakeholders care about the change and may be affected by it, but they do not have strong authority or influence over decisions. They should receive clear communication, updates, and opportunities to understand progress. Therefore, low power/influence and high interest is the correct combination.

A change strategy outlines how an organization will move from its current state to its desired future state. Its purpose is to ensure a structured and effective transition.

Key Considerations:

Ensuring the simplest way for transition: While simplicity is desirable, it is not the primary purpose of a change strategy.

Ensuring the quickest way for transition: Speed is not the main focus; effectiveness and alignment with goals are more important.

Achieving the transition between current state and future state: This accurately describes the purpose of a change strategy, which is to bridge the gap between where the organization is now and where it wants to be.

Mapping the alternative options: While mapping options may be part of the planning process, it is not the ultimate purpose of the change strategy.

Evaluation of Each Option:

A. Ensuring the simplest way for transition: Simplicity is a consideration but not the primary purpose of a change strategy. Conclusion: This is not correct .

B. Ensuring the quickest way for transition: Speed is secondary to achieving an effective and sustainable transition. Conclusion: This is not correct .

C. Achieving the transition between current state and future state: This is the core purpose of a change strategy, ensuring the organization moves effectively toward its goals. Conclusion: This is correct .

D. Mapping the alternative options: Mapping options is part of the analysis phase, not the overarching purpose of the strategy. Conclusion: This is not correct .

Final Recommendation:

The best description of the purpose of a change strategy is:

C. Achieving the transition between current state and future state.

Functional and non-functional requirements sit within the detailed requirements area and describe what the solution must do and how well it must perform. Functional requirements define required behaviour, services, processing, calculations, or interactions. Non-functional requirements define qualities and constraints such as performance, security, usability, availability, and reliability. In a requirements hierarchy, these requirements are developed from broader business, general, and technical requirement categories. Option B is too narrow because it describes mainly non-functional requirements, not functional requirements. Option D is wrong because the highest level is the business need or business requirement. Option A refers to project principles, not solution requirements. Therefore, functional and non-functional requirements are best described as an elaboration of General and Technical requirements.

Design thinking is a human-centered, iterative approach used to uncover innovative solutions by focusing on user needs and exploring multiple possibilities. It emphasizes creativity, collaboration, and experimentation.

Key Characteristics of Techniques:

Design Thinking: Uses an iterative process (empathize, define, ideate, prototype, test) to generate innovative options.

Fishbone Diagram: A root cause analysis tool, not focused on innovation.

Rich Pictures: A visual representation of a situation, useful for understanding context but not for generating innovative options.

Mind Maps: A brainstorming tool that organizes ideas hierarchically, but it does not inherently follow an iterative approach.

Evaluation of Each Option:

A. Design thinking: Design thinking explicitly uses an iterative approach to uncover innovative options. Conclusion: This is correct .

B. Fishbone diagram: Fishbone diagrams focus on identifying root causes, not innovation. Conclusion: This is not correct .

C. Rich pictures: Rich pictures visualize complex situations but do not inherently foster innovation. Conclusion: This is not correct .

D. Mind maps: Mind maps organize ideas but do not follow an iterative, innovative process like design thinking. Conclusion: This is not correct .

Final Recommendation:

The technique that uses an iterative approach to uncover innovative options is:

A. Design thinking.

When developing options for a business change, the business analyst must consider a range of solution types, which often fall into categories to ensure all possibilities are explored. While the exact naming conventions can vary, the following three core types are commonly considered and often named as:

Basic (or " Do Minimum " ) option: A low-cost, minimal-effort option to address the problem without major change (often including the " Do Nothing " or " Do Nothing Different " option for comparison).

Extended (or " Do Something " option): The preferred or main option, representing the full-scale, major change recommended to achieve the business objectives.

Executive (or " Commercial Off-The-Shelf (COTS) " ) option: An option based on purchasing an existing system or service, rather than custom-building a solution.Exhaustive option is NOT a standard or recognised category of business change option within the BCS syllabus.

(Reference: BCS Business Analysis Practice – Business Case, Identifying Options)

===========

The technique described is a Mind map. A Mind Map is a non-linear, visual tool used for structuring information and generating ideas around a central concept. It is characterized by having a central image or topic from which topic-related branches and sub-branches radiate. The structure helps the business analyst (or a group in a workshop) to organize complex, unstructured thoughts, visualize associations, and explore an area holistically. This technique is often used in the initial stages of investigation, such as problem analysis or requirements elicitation, to help gain a broad understanding of the scope and related issues. This is distinct from a Process map (which shows the flow of activities), an Entity relationship diagram (which models data structures), or the Business analysis process model (which models the BA ' s work steps).

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

The project sponsor owns the business justification for the change and is accountable for ensuring that the initiative delivers the intended business value. The sponsor champions the change, secures funding, provides strategic direction, resolves high-level issues, and remains focused on benefits realisation. Scheduling tasks, monitoring task progress, managing slippage, and controlling delivery against time and budget are mainly project management responsibilities. A project manager manages the delivery plan; the sponsor is concerned with whether the change produces the expected business benefits. The business case normally defines those benefits, and the sponsor is responsible for ensuring they are achieved or appropriately managed. Therefore, the sponsor’s responsibility is best represented by delivering the specific and agreed business benefits predicted in the business case.

Change control is a critical aspect of requirements management in business analysis. It ensures that changes to requirements are systematically evaluated, approved, and implemented without negatively impacting the project.

Key Considerations:

Change Control Definition: Change control is a formal process used to manage modifications to requirements, ensuring that changes are necessary, feasible, and aligned with project goals.

Version Numbering: While version numbering is part of documentation management, it is not the primary purpose of change control.

Preventing Changes: Change control does not prevent changes but ensures they are managed appropriately.

Tracing Requirements: Tracing requirements involves tracking their origin and impact, which is separate from managing changes.

Evaluation of Each Option:

A. A process to control version numbering: Version numbering is a documentation practice, not the purpose of change control. Conclusion: This is not correct .

B. A process to manage changes to requirements: This accurately describes change control as a structured approach to handling modifications to requirements. Conclusion: This is correct .

C. A process to ensure that changes cannot be made: Change control does not block changes but ensures they are managed effectively. Conclusion: This is not correct .

D. A process to trace requirements: Tracing requirements is a related but distinct activity focused on linking requirements to their source and impact. Conclusion: This is not correct .

Actor-task level analysis looks at detailed work performed by specific actors, roles, or users. At this level, a task can be broken into smaller steps, inputs and outputs can be identified, and performance measures can be applied to assess efficiency, quality, or timeliness. Therefore, options B, C, and D are valid statements about actor-task analysis. Value chain analysis, however, is not used at this detailed actor-task level. It is an enterprise-level technique used to understand how organisational activities create value for customers. It examines primary and support activities across the business, not the detailed steps performed by a particular actor. Because value chain analysis belongs at a higher level of business process analysis, option A is the false statement.

A business process model uses swimlanes to represent different roles, departments, or systems involved in a process. Hand-offs occur when responsibility for a task is transferred from one role or department to another.

Key Considerations:

Process Flow Lines Crossing Each Other: Crossing lines do not indicate hand-offs; they simply show the sequence of tasks.

Decision Point: A decision point represents a choice or branching in the process, not a transfer of responsibility.

Task Spanning Multiple Swimlanes: A single task spanning multiple swimlanes is uncommon and does not represent a hand-off.

Process Flow Crossing Swimlanes: When a process flow crosses from one swimlane to another, it indicates that responsibility for the task has been handed off to a different role or department.

Evaluation of Each Option:

A. By process flow lines crossing each other: Crossing lines are unrelated to hand-offs and may simply indicate parallel tasks. Conclusion: This is not correct .

B. By a decision point: Decision points represent choices or conditions, not transfers of responsibility. Conclusion: This is not correct .

C. By a task spanning multiple swimlanes: Tasks typically belong to a single swimlane, so this is not a valid representation of hand-offs. Conclusion: This is not correct .

D. By the process flow crossing from one swimlane to another: This accurately represents a hand-off, as it shows the transfer of responsibility between roles or departments. Conclusion: This is correct .

Final Recommendation:

Hand-offs are represented:

D. By the process flow crossing from one swimlane to another.