• Home
• BCS Exams
• FCBA - BCS Foundation Certificate in Business Analysis (BH0-013)

FCBA BCS Practice Test Questions and Exam Dumps

Question 1

Business analysts are expected to have specific competencies, which are divided into three main categories. Which of the following falls under one of those recognized categories?

A. Management Qualities
B. Business Knowledge
C. IT Skills
D. Project Skills

Correct Answer: B

Explanation:

The role of a business analyst (BA) is multifaceted and requires a diverse range of competencies. According to widely accepted frameworks, such as those provided by the British Computer Society (BCS) and the International Institute of Business Analysis (IIBA), the competencies of a business analyst are broadly grouped into three key categories: behavioral skills and personal qualities, business knowledge, and techniques.

Option B, Business Knowledge, is one of the recognized categories. It refers to the understanding a business analyst must have regarding the business environment in which they operate. This includes knowledge of the organization’s industry, structure, market dynamics, business processes, policies, and internal and external factors influencing business operations. This category also encompasses understanding business architecture and aligning project outcomes with strategic goals. A strong grasp of business knowledge helps the analyst bridge the gap between business needs and technology solutions.

Let’s explore why the other options are not correct:

Option A: Management Qualities
While business analysts may need leadership or facilitation skills, "management qualities" is not one of the standard categories under which BA competencies are classified. Leadership traits can be part of behavioral skills or personal qualities but do not stand as a separate official competency category.

Option C: IT Skills
Although a business analyst might benefit from understanding IT systems or working knowledge of technical environments, IT Skills are not one of the core competency categories. The business analyst’s role is not necessarily technical but rather focused on identifying business needs and defining solutions, which may or may not be IT-based. Any technical skills they possess are considered supplementary rather than a fundamental competency group.

Option D: Project Skills
Project management is a discipline of its own and, while project awareness can be beneficial for a business analyst working on initiatives, "project skills" are not listed as one of the three primary categories of competencies. Skills such as planning or scheduling are more relevant to project managers. Business analysts may work closely with project teams but their competencies are defined separately.

The formal competency classification ensures clarity in expectations, training, and career development for business analysts. Recognizing Business Knowledge as one of the core categories underscores the business-centric nature of the analyst’s role, which is to ensure that the organization’s needs are understood and appropriately addressed in any solution, whether it involves IT, organizational change, or process improvement.

Therefore, B is the correct answer.

Question 2

When is the appropriate time to carry out benefits realisation?

A. Immediately at the end of the project
B. At the beginning of the project
C. At the end of the finalised feasibility study
D. Months or years after the end of the project

Correct Answer: D

Explanation:
Benefits realisation refers to the process of identifying, planning, managing, and ultimately measuring the benefits a project or program was intended to deliver. This concept is central to effective project and program management, especially when aligning outcomes with strategic business goals.

Understanding the timing of benefits realisation is crucial because not all project benefits are immediately apparent upon project completion. Many benefits—especially in large-scale, transformative, or infrastructure projects—take months or even years to materialize and become measurable. This is because some benefits are dependent on behavioral change, adoption, or long-term usage trends, all of which occur over time.

Let’s evaluate each option:

A. Immediately at the end of the project
While some initial benefits may be apparent at the time of project closure, most are not fully realized immediately. This is especially true for intangible or strategic benefits such as increased customer satisfaction, improved efficiency, or reduced operating costs. Immediate assessment may only capture outputs and deliverables, not long-term impact. Hence, this timing is too early for full benefits realisation.

B. At the beginning of the project
At this stage, benefits are only planned or forecasted, not realised. While it’s essential to define expected benefits early in the project lifecycle (often documented in a business case), the actual realisation of those benefits occurs later, after the project’s outcomes are implemented and embedded in business operations. Thus, benefits realisation cannot be conducted at the beginning.

C. At the end of the finalised feasibility study
The feasibility study is conducted to assess whether a project is viable from technical, financial, and operational perspectives. Like the business case, it may include benefit projections, but it does not involve any delivery or implementation. Since no actual change has occurred yet, benefits cannot be measured or realised at this stage.

D. Months or years after the end of the project
This is the correct answer. True benefits realisation is a post-implementation activity. It involves measuring actual business impact after the project has been completed and its deliverables have been adopted into regular operations. For instance, a project that implements a new CRM system may deliver functionality at project close, but the business benefits—such as improved customer retention or increased sales—will take time to emerge. In some cases, organizations set up benefits reviews or post-implementation assessments at intervals such as 6 months, 12 months, or even several years after project completion.

Organizations that are mature in benefits management often establish a benefits realisation plan during the project but understand that evaluation must happen long after delivery. They may also assign benefits owners responsible for tracking these benefits over time.

In conclusion, since the goal of benefits realisation is to verify the value delivered by a project, it must be performed months or years after the project ends, when measurable outcomes have had time to accumulate. Therefore, the correct answer is D.

Question 3:

Which of the following statements correctly describes the process view of an organization?

A. It focuses on the customer of the organisation.
B. It focuses solely on the internal view of the organisation.
C. It focuses on the functions of an organisation.
D. It focuses on the organisational structure.

Correct Answer: A

Explanation:

The process view of an organization is a modern and strategic perspective that emphasizes how work flows through an organization to deliver value to the customer. Unlike traditional views that concentrate on structure or function, the process view centers on cross-functional activities, seeking to understand how various parts of the organization collaborate to meet customer needs efficiently and effectively.

Let’s review each of the answer options to determine which is accurate.

Option A: It focuses on the customer of the organisation.
This is the correct answer. The process view emphasizes end-to-end workflows that begin and end with the customer. It encourages organizations to break down internal silos and align processes with customer expectations, service quality, and satisfaction. This view is essential in business process reengineering, total quality management, and lean management methodologies, all of which prioritize customer outcomes. By focusing on how processes interact and contribute to customer value, organizations can become more agile, responsive, and efficient.

Option B: It focuses solely on the internal view of the organisation.
This is incorrect. While the process view does involve internal operations, it does not focus solely on them. Instead, it extends the view to consider external customer interactions, feedback loops, and how internal activities align with delivering value to those customers. A purely internal focus would fall under more traditional functional or structural views, which are not concerned with the customer journey in the same way.

Option C: It focuses on the functions of an organisation.
This describes the functional view, not the process view. The functional perspective breaks down the organization into departments like finance, HR, sales, and production, and views performance in terms of departmental efficiency. However, it often overlooks how these departments interact or how their activities collectively contribute to customer satisfaction. The process view, on the other hand, emphasizes interdepartmental collaboration and workflow integration.

Option D: It focuses on the organisational structure.
This relates to the structural view of an organization, which maps out hierarchies, reporting lines, and departmental boundaries. While useful for governance and resource management, the structural view often fails to capture the dynamic nature of how work actually gets done across the organization. It doesn't emphasize customer-centricity or the optimization of workflow processes, which are the hallmarks of the process view.

The process view of an organization is concerned with how different tasks and functions work together to deliver value to the customer. It enables organizations to analyze workflows from start to finish, crossing traditional departmental boundaries and aligning operational performance with strategic customer goals.

The correct answer is: A

Question 4

A Business Analyst creates a form for users to record the tasks they perform throughout the workday. What is the name of the investigation technique being used?

A. Special purpose records
B. Scenario analysis
C. Questionnaires
D. Activity sampling

Correct Answer: A

Explanation:

When conducting an investigation into how a system is used or how work is carried out in an organization, a Business Analyst may use a variety of investigation techniques. These methods are chosen based on the nature of the problem, the availability of users, and the type of data required. One such method involves giving users a form or template to fill out over a set period of time, where they document what tasks they perform and when. This approach is known as special purpose records.

Special purpose records are structured tools, often in the form of templates or logs, that are given to users to complete during their normal working routines. These records are specifically designed to capture particular types of information that may not be easily observed or captured through other means. The purpose is to gain insight into actual workflows, time spent on tasks, frequency of activities, or pain points users encounter throughout their day. It’s especially useful when the analyst cannot constantly observe the users due to time, resource, or access constraints.

By having users document their activities directly, special purpose records provide first-hand, detailed, and often quantitative data. They help bridge the gap between user experience and analyst observation, offering a reliable view into how systems are really used and how work is truly performed—beyond what users may say in interviews or questionnaires.

Let’s evaluate why the other options are not suitable:

Option B: Scenario analysis
This technique involves constructing detailed and often hypothetical scenarios to explore how a system or process would function under specific conditions. It’s generally used for future-oriented analysis and solution design rather than capturing real, day-to-day activities. Since the Business Analyst in this question is focusing on understanding current tasks, scenario analysis is not the right fit.

Option C: Questionnaires
While questionnaires are useful for gathering opinions or specific information from a larger audience, they consist of predefined questions that users answer once or over a short period. They do not involve ongoing recording of daily activities. Therefore, a questionnaire would not capture the same depth or accuracy about task performance as special purpose records would.

Option D: Activity sampling
This technique involves collecting data at random intervals to observe or ask users what they are doing at that moment. It is more statistical in nature and focuses on developing a picture of typical task distribution across time, often without requiring continuous logging by the user. It’s a good tool for high-level task frequency analysis, but it is different from asking users to systematically log all their tasks over a day.

In conclusion, the act of creating and distributing a structured form for users to log their activities throughout the day is best described by the technique of special purpose records, making A the correct answer.

Question 5

On a class diagram, what is represented by multiplicities?

A. The number of attributes held within each class
B. The minimum and maximum number of operations in each class
C. The minimum and maximum number of objects in each class
D. The business rules for an association between two classes

Correct Answer: C

Explanation:
In Unified Modeling Language (UML), a class diagram is a type of static structure diagram that describes the structure of a system by showing its classes, attributes, operations, and the relationships among objects. One important feature of class diagrams is the use of multiplicities, which are specified at each end of an association (i.e., a link between two classes).

The multiplicity indicates how many instances of one class can be associated with instances of another class. It essentially defines the minimum and maximum number of objects that can participate in a relationship. These are written as numerical values (e.g., 1, 0..1, 1.., 0.., etc.) near the ends of the association lines in a class diagram.

Let’s evaluate each option in detail:

A. The number of attributes held within each class
This is incorrect. Attributes in a class diagram are listed inside the class box and represent the data or properties of the class. The count of attributes is not related to multiplicities. Multiplicity is associated with relationships, not internal structure.

B. The minimum and maximum number of operations in each class
This is also incorrect. Operations (or methods) define the behavior of the class and are listed in the class diagram under the operations section. The number of operations is not governed by multiplicities. Operations are structural elements, not associations.

C. The minimum and maximum number of objects in each class
This is the correct answer. Multiplicities define the number of instances (objects) of a class that can be associated with another class in a specific relationship. For example, if Class A is associated with Class B with a multiplicity of 1..*, it means that at least one or potentially many instances of Class B can be linked to one instance of Class A. Conversely, a 0..1 multiplicity means zero or one instance is allowed. These ranges help designers understand and enforce cardinality constraints in object relationships.

D. The business rules for an association between two classes
While multiplicities can reflect certain business rules, such as “a customer can place multiple orders,” this is only partially true and does not fully explain what multiplicities are. The better answer is C, because multiplicities are a technical representation of object counts in relationships—not the rules themselves. Business rules might influence multiplicities, but they are not defined by them.

To sum up, multiplicities in class diagrams are crucial in understanding how many instances of one class can be linked to another. This information is vital during the design phase of object-oriented systems to prevent incorrect assumptions about object associations, such as enforcing a one-to-many or many-to-many relationship structure.

Therefore, the correct answer is C.

Question 6:

A well-formed requirement is expected to adhere to which of the following acronyms that define its essential characteristics?

A. MOSCOW
B. SMART
C. OSCAR
D. MOST

Correct Answer: B

Explanation:

When working with requirements in business analysis, project management, or systems engineering, it’s crucial that each requirement is clear, actionable, and verifiable. One widely recognized framework for evaluating the quality of a requirement is the SMART acronym. The concept of SMART requirements helps ensure that every requirement is specific enough to be understood, measurable so that its success can be evaluated, and achievable within the project's scope.

Let’s explore each option to determine which correctly applies to well-formed requirements.

Option A: MOSCOW
The MoSCoW method is an acronym used in prioritization, not in defining well-formed requirements. It stands for Must have, Should have, Could have, and Won’t have. This technique is often used to rank requirements or deliverables based on their criticality. Although it plays a role in requirement management, it doesn’t describe the quality or structure of a single requirement. Hence, this is not the correct answer.

Option B: SMART
This is the correct answer. SMART stands for:

• Specific: The requirement should be clear and unambiguous. It must detail exactly what is expected, leaving no room for misinterpretation.

• Measurable: The requirement must include criteria by which success can be measured. This helps assess whether the implementation meets the original intent.

• Achievable (or Attainable): It should be realistic and feasible, given the time, resources, and constraints of the project.

• Relevant (or Realistic): The requirement must contribute to the overall goals of the project and be aligned with organizational needs.

• Time-bound (or Time-related): If applicable, the requirement should specify time constraints or delivery schedules.

By following these guidelines, requirements become more manageable, testable, and verifiable. This is why SMART is frequently cited in requirements engineering and project planning.

Option C: OSCAR
OSCAR is a less common acronym, sometimes used in coaching or performance evaluations (Objective, Situation, Choices, Actions, Review), but it is not recognized in the context of well-formed requirements. It does not relate to the key attributes needed to structure a clear and effective requirement.

Option D: MOST
MOST stands for Mission, Objectives, Strategies, and Tactics. It is a strategic planning framework used to align business actions with organizational goals. Like OSCAR, it is not applicable to the structure or quality of individual requirements, so this is also not the correct answer.

A well-formed requirement is evaluated based on whether it is Specific, Measurable, Achievable, Relevant, and Time-bound, which are the five elements of the SMART framework. This ensures that requirements are clear, feasible, testable, and contribute meaningfully to the project's objectives.

The correct answer is: B

Question 7

In the V-model, which stage from the waterfall model is divided into several distinct stages?

A. Development
B. Analysis
C. Testing
D. Design

Correct Answer: C

Explanation:

The V-model, also known as the Verification and Validation model, is a software development model that builds upon the traditional waterfall model by emphasizing the relationship between development stages and their corresponding testing phases. While the waterfall model presents a linear progression of stages, the V-model adds a mirrored set of testing stages aligned with each phase of development.

In the waterfall model, testing is treated as a single, late-stage activity that typically comes after development is complete. This creates a sequential approach where the product is designed and built before any form of testing begins. The limitation of this approach is that if issues are found during testing, they can be costly and time-consuming to fix because they may trace back to earlier stages like requirements or design.

The V-model, however, addresses this issue by aligning each development stage with a corresponding testing stage. This creates a V-shaped structure where the left arm represents development activities and the right arm represents testing and validation activities. Here’s how the stages typically align:

• Requirements analysis (left side) aligns with Acceptance testing (right side)

• System design aligns with System testing

• Architectural design aligns with Integration testing

• Module design aligns with Unit testing

This structure breaks the single “testing” phase in the waterfall model into multiple testing stages in the V-model, each one designed to validate the outputs of a specific development activity. The purpose is to ensure that verification (confirming each part is built correctly) and validation (confirming the whole system meets the requirements) are carried out more thoroughly and earlier in the process.

Let’s review the incorrect options:

Option A: Development
While development is handled in both models, it is not split into different stages in the V-model in the way that testing is. Development corresponds mostly to the implementation or coding phase in both models.

Option B: Analysis
Analysis in both models is typically treated as a singular early-stage activity focused on gathering and defining requirements. It is not the primary stage that gets subdivided in the V-model.

Option D: Design
Design is elaborated upon in both models but not to the same degree that testing is. While there may be distinctions like architectural and detailed design, the V-model primarily emphasizes the expansion and formalization of testing stages rather than design stages.

Therefore, the correct answer is C, because in transitioning from the waterfall model to the V-model, the broad, single-phase concept of "testing" is expanded into several distinct and aligned testing phases, each paired with a specific development activity. This subdivision allows for earlier defect detection, improved traceability, and overall higher-quality system delivery.

Question 8

Which of the following terms may be used to describe the attitude of a stakeholder who is NOT in favour of the project but is probably not actively opposed to it?

A. Opponent
B. Neutral
C. Critic
D. Blocker

Correct Answer: C

Explanation:
In stakeholder analysis and project management, it is essential to categorize stakeholders based on their attitude, interest, and influence toward the project. This classification helps project managers develop communication strategies, plan engagements, and manage potential risks effectively. Stakeholders can fall into various categories, such as supporters, blockers, neutrals, and critics.

Let’s analyze what the term “Critic” refers to, especially in contrast with the other options:

A. Opponent
An opponent is someone who is generally opposed to the project and may work against it. Opponents are often clearly against the project’s goals and can act to hinder progress. They may speak out against the project or influence others to resist it. The question specifies someone who is not actively opposed, so "opponent" is too strong a term for this context.

B. Neutral
A neutral stakeholder has no particular strong opinion or emotional investment in the project's success or failure. They may not be significantly affected by the project or may have a wait-and-see approach. While a neutral person is not necessarily supportive, the term suggests a lack of stance rather than a negative bias. The question suggests the stakeholder is not in favour, indicating a slight negative inclination rather than indifference. Therefore, "neutral" does not accurately describe the situation.

C. Critic
A critic is someone who has reservations, concerns, or negative views about the project but is not necessarily hostile or actively trying to prevent the project’s success. Critics may voice concerns, raise issues, or question the project's direction, but they are usually constructive and not destructive. This term perfectly aligns with the question’s description of a stakeholder who is not in favour but also not actively opposed. Critics can be valuable as their feedback, if addressed properly, may lead to improvements in the project.

D. Blocker
A blocker is a stakeholder who actively obstructs or tries to halt progress on the project. Blockers are more committed to stopping the project than opponents and may use their influence or position to create barriers. This goes beyond mere disapproval or reluctance—it implies intentional resistance. This is not consistent with the stakeholder described in the question, who is not actively opposed.

Therefore, the best description of a stakeholder who is not supportive but not actively resisting the project is a Critic. Such stakeholders can often be brought to a more neutral or even supportive stance through proper engagement, transparency, and responsiveness to their concerns. They represent an important group to manage carefully in stakeholder engagement strategies, as ignoring them could risk them shifting toward active opposition if their concerns are left unaddressed.

Thus, the correct answer is C.

Question 9:

If a new computer system allows the organization to eliminate five clerical positions, under which category of costs or benefits should this be classified?

A. Tangible costs
B. Tangible benefits
C. Intangible costs
D. Intangible benefits

Correct Answer: B

Explanation:

In project management, cost-benefit analysis plays a critical role in evaluating whether a proposed change or investment—like implementing a new computer system—is justified. A central concept in this analysis is the classification of costs and benefits into tangible and intangible categories.

Tangible items are those that can be quantified in monetary terms, while intangible items are those that are qualitative or subjective and difficult to measure financially.

Let’s evaluate each of the options to determine the appropriate category for the suggestion that five clerical posts can be abolished due to system automation.

Option A: Tangible costs
Tangible costs are the actual financial expenditures associated with implementing the system. These might include the cost of purchasing hardware, software licenses, training staff, and maintenance. While relevant to the overall analysis, the abolition of posts results in a financial saving, not an expense. Therefore, this is not the correct classification.

Option B: Tangible benefits
This is the correct answer. A tangible benefit is one that can be clearly measured and expressed in monetary terms. If the implementation of a new system leads to the elimination of five clerical positions, the organization will save on salaries, benefits, office space, and potentially administrative overhead. These are direct, calculable savings that can be factored into a return on investment (ROI) calculation. For example, if each clerical position costs $40,000 annually, the total savings would be $200,000 per year. This makes it a classic example of a tangible benefit.

Option C: Intangible costs
Intangible costs refer to costs that are not easily measurable in financial terms. These might include reduced staff morale, fear of job loss, resistance to change, or potential declines in customer satisfaction during the transition phase. While the abolition of posts may lead to some intangible costs (such as employee dissatisfaction), the act of reducing headcount itself is a benefit in financial terms, not a cost.

Option D: Intangible benefits
Intangible benefits are positive outcomes that are not easily quantified, such as improved decision-making, better customer satisfaction, enhanced company image, or increased flexibility. While the new computer system may produce such benefits, the specific benefit of reducing payroll by eliminating positions is tangible and measurable—hence, this option is incorrect in this context.

The proposed abolition of five clerical jobs due to a new computer system represents a direct cost saving that can be measured in financial terms. This makes it a tangible benefit, as it results in a quantifiable improvement to the organization’s bottom line.

The correct answer is: B