正解:B
The correct answer is B .
In TOGAF 9.2, gap analysis is used to identify shortfalls between the Baseline Architecture and the Target Architecture. TOGAF explains that gaps may include items that have been deliberately omitted, accidentally left out, or not yet defined. In the official TOGAF 9.2 list of potential sources of gaps, business domain gaps include people gaps, process gaps, tools gaps, information gaps, measurement gaps, financial gaps , and facilities gaps. Therefore, Financial gap is the option that directly matches the official TOGAF 9.2 example of a business domain gap.
Option A , "Skills gap," is close in meaning to a people-related gap, but TOGAF 9.2 specifically gives the example as people gaps , such as cross-training requirements. Since the answer choices include Financial gap
, which is explicitly listed by TOGAF 9.2, A is not the best answer.
Option C , "Data gap," is not a business domain gap. TOGAF 9.2 lists data-related gaps separately under data domain gaps , such as data not being current enough, not located where it is needed, not available when needed, not created, not consumed, and data relationship gaps.
Option D , "Capability gap," is not listed in the TOGAF 9.2 gap analysis technique as one of the explicit examples of a business domain gap. Although capability gaps may be discussed in broader architecture planning, the official gap analysis examples in TOGAF 9.2 identify Financial gap as a business domain gap.
References: TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 23:
Gap Analysis, Section 23.1 Introduction.