In PP1 (Establishing a BCMS), defining scope is a foundational activity because it sets clear boundaries for what the BCMS applies to and what it does not. Good practice requires a scope statement that makes coverage explicit (e.g., products/services, sites, functions, legal entities, interfaces, and exclusions) so stakeholders understand the BCMS’s intended reach and so analysis and solutions design are directed appropriately. The GPG 7.0 Lite highlights that BCMS development includes developing the scope and policy, and it emphasizes continual improvement and review—implying scope may need review when organizational context changes. (thebci.org)

Option C captures the definition accurately: scope clarifies what is covered and not covered. Option A is too absolute; you consider relevant suppliers/customers, but scope does not automatically include “all.” Option B is incorrect because scope is reviewed as the organization changes (mergers, delivery model changes, regulatory change). Option D describes the policy, not the scope. Therefore, C is the correct statement.