BAPv5 Exam Dumps : BCS Practitioner Certificate in Business Analysis Practice v5.2

The business analysis guidance makes it clear that a business case is not a “one-and-done” document that stops being useful at implementation. Instead, it is revisited at multiple decision gates through the lifecycle, including points after development estimates are known, before deployment, and later during operation when benefits realisation is checked. This directly contradicts statement A, because the business case remains relevant beyond implementation to confirm assumptions and verify whether expected benefits were actually achieved.

Statement B is also incorrect. The guidance explicitly states that the “do nothing / maintain the status quo” option should always be considered and will usually appear in the business case. It may sometimes be rejected due to unacceptable consequences, but it should still be included so decision-makers understand the risks of inaction.

Statement C is correct because the business case should consider both tangible and intangible benefits. The documentation explains that many benefits (for example improved customer satisfaction or staff morale) can be intangible, meaning they cannot be credibly valued in advance. While organisations vary in how they treat intangibles, the framework recognises them as legitimate benefits (with the caution not to overstate them or assign “spurious” values).

The business analysis guidance notes that reviewing a company website can reveal useful inferences about the organisation’s branding, values, priorities, and strategic positioning, including how it balances cost versus perceived quality. In particular, the guidance contrasts “populist” signals (primary colours, flashing icons, exclamation marks, “Bargain!” language) with a quieter, more restrained design, which tends to imply a more premium / quality-focused positioning.

The described site is muted (greys/whites), uses “lots of white space,” and includes only a few carefully chosen images. Those choices align strongly with conclusion D: the company is positioning its offering as high quality rather than “cheap and cheerful.” The seamless movement through information and concise, well-structured sections also indicate attention to usability and information architecture—signals consistent with high technical and design standards (conclusion C).

However, nothing in the description proves the firm is “well established” (A), “market leading” (B), or “very profitable” (E). Those claims require external evidence (market share, history, financial performance), whereas the website evidence supports positioning and quality/technical execution, not market status or profitability.

The Business Change Lifecycle in the documentation comprises five stages (shown in the lifecycle figure and described as the “key areas of activity” needed for successful business change). Business case work is not confined to a single moment; instead, it is revisited through the change effort at multiple decision points. The guidance illustrates this with “decision gates” where the business case is: produced initially, then confirmed after detailed requirements, confirmed once development costs are estimated, revisited before deployment, and later used to check benefits realisation once the new processes/systems are operating.

That pattern means business-case-related activity normally touches every stage of the lifecycle. Early on (Alignment and Definition), the business case is shaped and refined as understanding of problems, scope, and requirements improves. During Design and Implementation, the business case is validated and updated as costs, feasibility, and delivery plans become clearer and as the organisation prepares for change. In Realisation, the business case is used as the baseline for benefits review and to identify follow-up actions where benefits are not yet achieved. Therefore, “5” is the best answer.