Pass the BCI CBCI 7.0 Certification Course CBCI Questions and answers with CertsForce

A gap analysis is a critical evaluation tool used in the Solutions Design phase to identify differences between existing Business Continuity capabilities and what is required to achieve organizational resilience. The CBCI 7.0 course specifies that this analysis determines if new or revised strategies and solutions are needed to meet Business Continuity requirements effectively. By comparing current states with desired outcomes, the gap analysis highlights areas lacking adequate controls, resources, or processes. It drives decision-making for prioritizing improvements and investments in continuity measures. This systematic assessment ensures that Business Continuity strategies are fit for purpose and aligned with evolving risks and business objectives. It is not focused on financial performance or audit justifications but on actionable capability enhancements.

The CBCI 7.0 course stipulates that appointing deputies or alternates for each BCMS role is a governance best practice ensuring continuity of responsibility and decision-making. Deputies are subject matter experts equipped to act on behalf of the primary role holder during absences, maintaining operational integrity and responsiveness. Relying on the Business Continuity professional or Incident Response Team to cover absent roles without formal deputization risks delays and gaps. Putting responsibilities on hold is unacceptable as it compromises continuity efforts.

CBCI 7.0 treats maintenance and review as part of ensuring the BCMS remains effective and fit for purpose over time. In BCI guidance, maintenance activities are commonly triggered by meaningful change—especially changes that alter risk, dependencies, or the organization’s operating context. A core trigger explicitly referenced in BCI Good Practice material is “changes to the environment in which the organization operates.” This includes shifts such as new geopolitical conditions, supply-chain volatility, technology changes, emerging threats, regulatory changes in the wider environment, or market/infrastructure changes that can invalidate assumptions in the BIA, strategies, plans, and response structures.

Option A therefore represents a direct and widely recognized trigger for BCMS maintenance. By contrast, option B (performance appraisal process) is usually an internal HR mechanism and only indirectly relevant unless it changes competence/accountability expectations for BC roles. Option C (external auditor changes) does not inherently change continuity capability. Option D (competitor organizational structure) is not a BCMS maintenance trigger in itself; benchmarking can inform improvement, but it doesn’t automatically require maintenance updates.

In GPG-aligned CBCI 7.0 practice, the BIA estimates impacts over time and identifies what must be recovered, in what order, and with what minimum capability. A key BIA output is a clear view of the resources and dependencies needed to deliver the organization’s prioritised activities—including people/skills, information and data, technology, premises, finance, suppliers, and key internal/external interdependencies. This is foundational because strategies and solutions (PP4) and the enabling plans (PP5) must be based on what the BIA proves is required to restore delivery.

Therefore, option A is correct: those requirement categories are analysed specifically to identify the dependencies that enable prioritised activities to continue or resume.

Option B (general business plan) is broader strategic planning, not the specific continuity dependency mapping output from a BIA. Option C relates to culture development (PP2), not BIA dependency capture. Option D (response structure) uses BIA outputs, but the direct purpose of gathering people/data/finance/supplier requirements during BIA is to map the resources and dependencies for prioritised activities.

The CBCI 7.0 course explains that risk assessments fundamentally rely on evaluating the likelihood of risk occurrence and the consequences if they materialize. This probabilistic approach enables prioritization and treatment planning. Although risk assessments inform BIAs and regulatory compliance, their primary purpose is to analyze potential risks in terms of impact and probability to guide effective continuity strategies. Currency (timeliness) is important but secondary to the quality of likelihood and consequence evaluations, which form the basis of all risk decisions.

In the GPG 7.0 structure used by CBCI 7.0, Analysis (PP3) covers the Business Impact Analysis (BIA) and Risk Assessment, producing requirements such as priorities, resource needs, and recovery targets. Once those requirements are understood, the next step is Solutions Design (PP4)—selecting and designing strategies and solutions that can meet the recovery requirements (e.g., meeting RTOs, securing resources, reducing single points of failure).

That sequencing is why option B is correct: after analysis, you identify strategies and solutions for resuming/continuing operations. Option A (governance) is established earlier as part of setting up the BCMS framework. Option C is part of the analysis stage itself, not the next stage. Option D (operational plans) aligns more with Enabling Solutions (PP5), where solutions are implemented and supported by response structures and plans.

According to CBCI 7.0, strategies represent the high-level approaches that define how the organization will maintain or recover critical operations, aligned with Business Continuity requirements identified through BIAs and risk assessments. Solutions, on the other hand, are the specific, detailed methods and resources deployed to implement these strategies effectively. Strategies set the direction, while solutions translate these into practical capabilities such as alternate site arrangements, backup systems, or communication plans. Distinguishing strategies from solutions clarifies planning and execution responsibilities within the BCMS.

An effective BC policy is a high-level statement of intent and direction, formally expressed and endorsed by top management. Its effectiveness depends on visible leadership commitment—because leadership is responsible for ensuring the policy aligns with the organization’s strategic direction, is communicated, resourced, and kept under review for suitability. In BCI guidance, establishing the business continuity policy specifically requires top management action, support, and commitment, with governance to maintain and improve the policy over time.

Option A best reflects this core characteristic: top management commitment and continual improvement. The other options describe items that are typically handled in plans or supporting documents (e.g., incident management plan details, budget specifics, supplier constraints, or exercise lessons learned). Those elements may inform the BCMS, but they do not define what a BC policy is. The policy sets the framework and expectations; detailed procedures, constraints, and exercise learnings are managed elsewhere within the BCMS lifecycle.

When BC plans are updated, the organization must be able to prove which version is current, when it was reviewed, what changed, and who approved it. A formal version control process prevents confusion, reduces the risk of using outdated instructions during an incident, and supports assurance/audit needs. BCI guidance on content management for resilience explicitly highlights that clear version control prevents confusion and ensures teams work with the most current information—especially critical during crises when outdated guidance can compound problems.

Option B directly meets that requirement: it identifies review dates and highlights changes so plan owners and responders can trust the document. Option A (just saving to a shared drive) does not ensure people use the correct version or understand changes. Option C is insufficient for operational control. Option D is passive and does not implement document control; it also risks inconsistent distribution. In CBCI practice, controlled documents + versioning are essential to reliable response and recovery execution.

Risk treatment is a fundamental phase within the risk management process, focusing on how identified risks will be managed to reduce their potential impact or likelihood. The CBCI 7.0 course clarifies that risk treatment involves selecting and implementing measures to either prevent risks from occurring or to minimize their adverse effects on the organization. This step is critical to building resilience, as it directly influences the mitigation of unacceptable risks that could disrupt key business activities. While assigning responsibility, scoring risks, and reporting are important supporting actions, the core purpose of risk treatment is to apply controls and strategies that reduce risk exposure effectively, thereby enhancing continuity readiness.