Free Practice Questions for BCS PC-BA-FBA-20 Exam

One of the key principles of business analysis is to present stakeholders with options rather than prescribing a single solution. This approach ensures that stakeholders can make informed decisions based on their priorities and constraints.

Key Principles of Business Analysis:

Present Options Not Solutions: Business analysts should provide multiple viable options, allowing stakeholders to choose the best course of action.

Understand Symptoms: While understanding symptoms is important, it is part of problem analysis, not a key principle.

Focus on Requirements Definition Only: Business analysis encompasses more than just defining requirements; it includes understanding problems, analyzing options, and ensuring value delivery.

Integrate IT Changes: While integrating IT changes is valuable, it is not a universal principle of business analysis.

Evaluation of Each Option:

A. Present options not solutions: This is a fundamental principle of business analysis, emphasizing stakeholder choice. Conclusion: This is correct .

B. Understand the symptoms of the problem being defined: Understanding symptoms is part of problem analysis but not a standalone principle. Conclusion: This is not correct .

C. Focus on requirements definition only: Business analysis involves more than just requirements definition. Conclusion: This is not correct .

D. Integrate IT changes together with project requirements to improve efficiency: While integration is valuable, it is not a universal principle of business analysis. Conclusion: This is not correct .

Activity sampling is a quantitative form of observation used to collect measurable evidence about how work is performed. Instead of continuously observing one person or process, the analyst samples activities at intervals and records what is happening. This helps identify how time is spent, how often particular tasks occur, and where inefficiencies may exist. Surveys are quantitative but they gather responses from participants rather than observing actual work. Interviews are primarily qualitative because they rely on discussion and stakeholder explanation. User role analysis is used to understand user types, responsibilities, and interactions, but it is not a form of observation. Since activity sampling directly observes work and produces measurable data, it is the correct answer.

A business analyst is responsible for understanding business needs, analysing problems, eliciting requirements, exploring options, and helping stakeholders define valuable change. Options A, B, and D are all normal business analysis responsibilities. The analyst investigates the business situation, identifies needs, supports option development, and uses elicitation techniques such as interviews, workshops, observation, and document analysis to understand requirements. Ensuring that projects are delivered within budget constraints is primarily a project management responsibility. A project manager controls project delivery, manages schedule, cost, resources, risks, and progress against the approved plan. The business analyst may contribute estimates or impact analysis, but they do not normally own budget delivery. Therefore, option C is least likely to be a business analyst responsibility.

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 T-shaped professional model is used in business analysis to describe the ideal mix of skills and knowledge. The ' T ' shape consists of a vertical bar and a horizontal bar. The vertical bar represents the deep and specific domain knowledge or core expertise (e.g., business analysis techniques, specific industry knowledge). The horizontal bar (the top of the ' T ' ) represents the multi-disciplinary breadth of skill and knowledge that an individual can apply to various situations. This breadth includes soft skills like communication, facilitation, leadership, and a broad understanding of different business areas (like finance, operations, IT, and strategy). It is this breadth that allows the business analyst to collaborate effectively across different teams and disciplines, understand the context of the change, and recommend truly holistic solutions.

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice – Competencies of a Business Analyst)

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.

Critical success factors define the areas where an organisation must perform well to achieve its objectives. They are broad success areas, such as improving customer service, reducing operating costs, increasing market share, or improving product quality. Key performance indicators are measurable values used to monitor whether those success factors are being achieved. Therefore, KPIs track progress against CSFs. CSFs are not sub-targets within KPIs; the relationship works the other way around. KPIs also are not measured by CSFs because CSFs are qualitative success areas, while KPIs are measurable indicators. For example, if a CSF is “provide excellent customer service,” relevant KPIs might include complaint numbers, customer satisfaction scores, repeat customer percentage, or response times. This makes option C the correct relationship.

To determine the best way to present the changes to the scheduling team, we need to consider the nature of the information being communicated and the audience (the scheduling team). The extract describes changes to processes, roles, and systems, which are best represented visually to ensure clarity and understanding.

Key Considerations:

Business Process Model (BPM): A BPM is a visual representation of the steps in a process. It is particularly useful for communicating changes to workflows, roles, and responsibilities. Since the extract discusses splitting the scheduling team into two groups and introducing new software and processes, a BPM would effectively illustrate how these changes impact the workflow.

Business Activity Model (BAM): A BAM focuses on high-level activities and their logical dependencies, often used in strategic planning. However, it is less detailed than a BPM and may not adequately capture the specific changes to scheduling processes.

POPIT (People, Organization, Process, Information, Technology): POPIT is a framework for analyzing business change across multiple dimensions. While it provides a holistic view, it is not a presentation tool and would not be the best choice for directly communicating the changes to the scheduling team.

Prototype: A prototype is typically used to demonstrate the functionality of a system or software. While the introduction of telephony software and an online booking system could involve prototyping, this option does not address the need to communicate process and role changes.

Evaluation of Each Option:

A. Business Process Model: A BPM is ideal for illustrating the changes to the scheduling process, including the split into inpatient and outpatient teams and the integration of new software. It provides a clear, step-by-step visual representation that the scheduling team can easily understand. Conclusion: This is the best option .

B. Business Activity Model: While a BAM could provide a high-level overview of the changes, it lacks the detail needed to explain specific process adjustments. Conclusion: This is not the best option .

C. POPIT: POPIT is a framework for analysis, not a communication tool. It would not effectively convey the changes to the scheduling team. Conclusion: This is not the best option .

D. Prototype: Prototyping is relevant for demonstrating software functionality but does not address the need to communicate process and role changes. Conclusion: This is not the best option .

Final Recommendation:

The changes should be presented using a Business Process Model , as it effectively communicates the revised workflows and roles to the scheduling team.

Requirements may be documented using several diagrammatic styles where visual representation helps stakeholders understand scope, data, behaviour, or process flow. A use case model is diagrammatic because it shows actors, system boundaries, and use cases. A data model is diagrammatic because it represents data entities, attributes, and relationships. A business process model is also diagrammatic because it shows tasks, decisions, flows, hand-offs, and responsibilities. An epic, however, is normally a high-level Agile requirement or large user story, not a diagrammatic document style. It may be broken down into features or user stories, but the epic itself is textual rather than a modelling notation. Therefore, “Epic model” is the item that is not suitable as a diagrammatic document style for requirements.