Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
In a UML activity diagram, which symbol represents a task?
In a UML (Unified Modeling Language) Activity Diagram, the symbol used to represent a task (or action/activity) is a round-cornered rectangular box. This shape denotes an individual piece of work or step carried out within the process.
The other symbols represent:
A filled in circle (B): The Initial Node (start of the process).
A diamond shaped box (C): A Decision or Merge Node (a point where a choice is made or paths recombine).
A bullseye (D) (a filled circle inside an outer circle): The Activity Final Node (end of the process flow).
(Reference: BCS Modelling Business Processes / BCS Business Analysis Practice -- UML Activity Diagrams)
Which of the following lists only includes stakeholders shown on the stakeholder wheel?
The stakeholder wheel is a framework used to categorize stakeholders based on their relationship to the organization or project. It typically includes categories such as customers, partners, suppliers, regulators, and competitors , among others.
Key Considerations:
Regulators, Compliance, Owners: While regulators and owners are valid stakeholders, 'compliance' is not a stakeholder category but rather a function or responsibility.
Competitors, Customers, Partners: These are all valid stakeholder categories commonly found on the stakeholder wheel.
Competitors, Consumers, Providers: While competitors and consumers (a synonym for customers) are valid, 'providers' is not a standard term used in the stakeholder wheel.
Contractors, Partners, Suppliers: Contractors are not typically included as a primary stakeholder category on the stakeholder wheel, though partners and suppliers are.
Evaluation of Each Option:
A . Regulators, Compliance, Owners: 'Compliance' is not a stakeholder category; it refers to adherence to rules or regulations. Conclusion: This is not correct .
B . Competitors, Customers, Partners: These are all valid stakeholder categories found on the stakeholder wheel. Conclusion: This is correct .
C . Competitors, Consumers, Providers: While competitors and consumers (customers) are valid, 'providers' is not a standard stakeholder category. Conclusion: This is not correct .
D . Contractors, Partners, Suppliers: Contractors are not typically included as a primary stakeholder category on the stakeholder wheel. Conclusion: This is not correct .
Final Recommendation:
The list that only includes stakeholders shown on the stakeholder wheel is: B . Competitors, Customers, Partners
John has been working on a business case for opening up the overseas market to new products He has been asked to document the risks What SHOULD he do to ensure they are appropriately recorded? Select the TWO that apply
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.
Which elements are included in a CARDI log?
Which of the following statements CORRECTLY describes a benefits dependency network?
A benefits dependency network shows how business objectives, expected benefits, enabling business changes, and supporting outputs are connected. It helps analysts and stakeholders understand how a proposed change is expected to create value. The technique is useful because benefits are rarely achieved simply by delivering a system or product; they depend on business changes such as process redesign, behaviour change, training, new roles, or organisational adoption. Option B is too narrow because a benefits dependency network is not merely a stakeholder-benefit list. Option C describes cost breakdown, not benefit dependency. Option D describes requirements traceability, which is a different requirements management technique. The correct description is an overall representation linking objectives, benefits, and the business changes needed to realise those benefits.
The management of a chain of hotels has decided that one of its critical success factors (CSF) is to 'provide excellent customer service' The below measures have been suggested.
Which THREE of these are appropriate key performance indicators (KPIs) for the CSF 'provide excellent customer service"?
To determine which measures are appropriate Key Performance Indicators (KPIs) for the Critical Success Factor (CSF) 'provide excellent customer service,' we must first understand the relationship between CSFs and KPIs:
Critical Success Factors (CSFs): These are the essential areas or activities that an organization must excel at to achieve its goals. In this case, 'provide excellent customer service' is a CSF.
Key Performance Indicators (KPIs): These are measurable metrics used to evaluate progress toward achieving a CSF. KPIs should directly align with the CSF and provide actionable insights.
Now, let's evaluate each option to determine whether it is an appropriate KPI for the CSF 'provide excellent customer service':
A . The number of customers who make use of their in-room mini bar
This measure tracks customer behavior related to a specific hotel amenity (the mini bar). While it may indicate customer satisfaction with the room's offerings, it does not directly measure the quality of customer service.
Conclusion: This is not an appropriate KPI for the CSF 'provide excellent customer service.'
B . The percentage of customers who use the leisure facilities
This measure tracks how many customers utilize the hotel's leisure facilities (e.g., gym, pool, spa). While it may reflect customer engagement with the hotel's amenities, it does not directly assess the quality of customer service.
Conclusion: This is not an appropriate KPI for the CSF 'provide excellent customer service.'
C . The number of customers who complain
Customer complaints are a direct indicator of dissatisfaction and can highlight areas where customer service needs improvement. A high number of complaints suggests poor customer service, while a low number indicates better service quality.
This measure is closely aligned with the CSF 'provide excellent customer service' because it provides actionable feedback on service performance.
Conclusion: This is an appropriate KPI for the CSF.
D . The percentage of customers who join the hotel loyalty scheme
Customers are more likely to join a loyalty scheme if they have had a positive experience with the hotel, including excellent customer service. This measure reflects customer satisfaction and loyalty, which are outcomes of good service.
Conclusion: This is an appropriate KPI for the CSF.
E . The percentage of customers who return
Repeat customers are a strong indicator of customer satisfaction and loyalty, which are directly influenced by the quality of customer service. If customers return to the hotel, it suggests they were satisfied with their previous experience, including the service they received.
Conclusion: This is an appropriate KPI for the CSF.
Which of the following statements is FALSE in relation to the hierarchy of requirements?
The hierarchy of requirements organizes requirements into levels (e.g., business needs, stakeholder requirements, solution requirements) to ensure alignment and traceability. Let's evaluate each statement to determine which is false .
Key Characteristics of the Requirements Hierarchy:
Linking Requirements: The hierarchy ensures that detailed requirements are connected to higher-level business needs and objectives.
Order of Development: The hierarchy does not dictate the sequence in which requirements should be developed; it focuses on relationships and dependencies.
Driven by Strategy: Requirements are derived from the organization's values, strategy, and objectives.
Traceability: The hierarchy links different types of requirements to ensure consistency and alignment.
Evaluation of Each Statement:
A . The requirements hierarchy enables detailed requirements to be linked to the business need: This is true; the hierarchy ensures traceability between high-level and detailed requirements. Conclusion: This is true .
B . The requirements hierarchy shows the order in which requirements should be developed: The hierarchy does not specify the development order; it focuses on relationships and dependencies. Conclusion: This is false .
C . Requirements are driven by the organisation's values, strategy and objectives: This is true; requirements must align with organizational goals. Conclusion: This is true .
D . The requirements hierarchy links different requirements to each other: This is true; the hierarchy ensures traceability and alignment across levels. Conclusion: This is true .
Final Recommendation:
The false statement is: B . The requirements hierarchy shows the order in which requirements should be developed.
Exam domains verified against: Official BCS PC-BA-FBA-20 exam guide, last checked October 2026.
Covers the key principles of business analysis and the different variants of the business analyst role. Understanding these fundamentals provides the foundation for all other competencies in the field.
Sample question from this domain above: Q4
Focuses on the T-shaped Professional concept and the three areas of business analysis competency. This demonstrates what skills and knowledge a well-rounded BA needs to develop.
Examines how business analysis fits within strategic planning using PESTLE for external analysis and VMOST for internal analysis. These frameworks help BAs understand the organisational landscape.
Sample question from this domain above: Q1
Identifies the five main activities: situation investigation and problem analysis, feasibility assessment and business case development, business process improvement, requirements definition, and business acceptance testing.
Covers core investigation techniques including workshops, observation, and interviews. These are the primary tools BAs use to gather information and understand stakeholder needs.
Sample question from this domain above: Q3
Uses the stakeholder wheel, Power/Interest grid, and RACI chart to identify and manage stakeholders. Effective stakeholder management is critical to project success and requirement validation.
Sample question from this domain above: Q2
Covers the business process hierarchy, enterprise-level modelling techniques, event-response and actor-task levels, as-is process models, and customer journey maps. This domain accounts for identifying and implementing process improvements.
Addresses gap analysis using the POPIT model, developing options, and applying design thinking. BAs use these techniques to bridge the gap between current and desired states.
Sample question from this domain above: Q5
Covers the business case lifecycle, feasibility assessment areas, business case structure and contents, and Agile considerations. The CARDI log is used to track risks, assumptions, and interdependencies throughout the project.
Examines documentation styles, requirements catalogues, user stories, use case diagrams for functional requirements, and class models for data. Clear requirement documentation ensures shared understanding across the team.
Sample question from this domain above: Q6
Covers requirements validation types and requirements management aspects. Validation ensures requirements meet stakeholder needs while management ensures they remain controlled throughout delivery.
Examines different delivery lifecycle types and their respective advantages and disadvantages. BAs need to understand how waterfall, iterative, and agile approaches differ in their implementation.
Sample question from this domain above: Q7
Common questions about the exam itself
