The Open Group OGEA-103 Exam With Confidence Using Practice Dumps

The illustration shows the relationship between the Enterprise Continuum, the Architecture Continuum, and the Solutions Continuum, which are key concepts in the TOGAF framework. The Enterprise Continuum is a view of the Architecture Repository that shows how generic foundation architectures can be leveraged and specialized to support the requirements of an individual organization. The Architecture Continuum specifies a structured classification for architectural artifacts, such as models, patterns, and descriptions, that can be reused and adapted across different domains and levels of abstraction. The Solutions Continuum identifies implemented solutions that support various stages of business and IT capability evolution, such as common systems, industry solutions, and organization-specific solutions. The illustration also shows how the architecture context and requirements are influenced by external factors, such as business drivers, stakeholders, and standards, and how they shape the generic and specific architectures and solutions. The illustration also shows how the deployed solutions become part of the architecture context for future iterations of the architecture development cycle. References:

•TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 6: Architecture Repository, Section 6.2 Enterprise Continuum.

•TOGAF Standard, 10th Edition, Part IV: Architecture Content Framework, Chapter 35: Enterprise Continuum and Tools, Section 35.1 Introduction.

Within the TOGAF framework, assessments are used to ensure that architecture work is conformant with governance parameters. A compliance assessment (sometimes called architecture compliance or compliance review) is the evaluation of a project’s architectural artifacts—its design, architecture decisions, progress status—against the established architecture standards, principles, and constraints. The content of a compliance assessment typically includes reviewing the project status, the architectural design alignment, and identifying noncompliance issues or deviations. Because it focuses on how well the project matches the architecture, rather than on capabilities, organizational structure, or risk per se, the described contents correspond to a compliance assessment. The compliance assessment helps governance bodies enforce architectural consistency and correct deviations during implementation.

The Chief Engineer is concerned that implementation across multiple plants and mixed teams (internal + contractors) may be inconsistent and of poor quality.

The question asks: How should Architecture Contracts be used to address this concern according to the TOGAF standard?

TOGAF states that an Architecture Contract must:

Define obligations of both architecture and implementation organizations

Specify metrics, measures, acceptance criteria, and success factors

Identify risks and mitigation

Support Architecture Governance through compliance reviews

Apply to BOTH internal teams and external suppliers (external contracts must be legally enforceable)

Option C is the only one that correctly reflects these TOGAF requirements.

✔ Why Option C is correct

1. Architecture Contracts must specify goals, measures, acceptance terms, and risks

TOGAF explicitly states that Architecture Contracts should include:

Statement of Architecture Work

Performance metrics and measures

Acceptance criteria

Risks and issues

Compliance and conformance requirements

Option C includes all of these.

2. Third-party contracts must be legally enforceable

True — TOGAF states that when external suppliers are involved, Architecture Contracts often take the form of legally binding contracts.

Option C:

“Third-party contracts must be legally enforceable.”

Correct.

3. Compliance reviews must be scheduled

TOGAF’s Architecture Governance Framework prescribes scheduled Architecture Compliance Reviews to ensure that implementation conforms to the Architecture Contract.

Option C:

“establish a schedule of compliance reviews at key points”

Correct — this directly addresses the Chief Engineer’s concern about consistency and quality.

4. Deviations must be reviewed by the Architecture Board and any dispensations should be time-bound

TOGAF allows dispensations but requires:

Formal review

Approval by the Architecture Board

Time-bound accommodations rather than permanent exceptions

Option C includes exactly this guidance.