All of the following describe a purpose of an Architecture Compliance review, except: A. determining the technical readiness of a project. An Architecture Compliance review is a process that assesses whether an architecture project or solution complies with established architectural standards, guidelines, and best practices. The primary purpose of an Architecture Compliance review is to ensure the application of best practices, identify errors or deviations from architectural standards, and identify where architecture standards require modification or improvement. It helps to maintain architectural integrity, improve quality, and mitigate risks associated with non-compliance. While a technical readiness assessment may be part of project management or technical review processes, it is not the primary purpose of an Architecture Compliance review.

Ensure the application of best practices to architecture work Provide an overview of the compliance of an architecture to mandated enterprise standards Identify where the standards themselves may require modification Identify services that are currently application-specific but might be provided as part of the enterprise infrastructure Document strategies for collaboration, resource sharing, and other synergies across multiple architecture teams Take advantage of advances in technology Communicate to management the status of technical readiness of the project Identify key criteria for procurement activities (e.g., for inclusion in Commercial Off-The-Shelf (COTS) product RFI/RFP documents) Identify and communicate significant architectural gaps to product and service providers

Answer should be A

While a technical readiness assessment may be part of project management or technical review processes, it is not the primary purpose of an Architecture Compliance review.

Yes C. 1. To *catch errors* in the project architecture early. 2. To ensure the application of *best practices to architecture work*. 3. To provide an *overview of the compliance of an architecture* to mandated enterprise standards. 4. To identify where the *standards themselves may require modification*. 5. To identify services that are currently application-specific but might be provided as part of the enterprise infrastructure. 6. To take advantage of advances in technology. 7. To identify key criteria for procurement activities. 8. To identify and communicate significant architectural gaps to product and service providers.

C is part of phase A - Architecture Vision - 6.3.10

It's C. All the others are listed in https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap42.html First and foremost, catch errors in the project architecture early, and thereby reduce the cost and risk of changes required later in the lifecycle This in turn means that the overall project time is shortened, and that the business gets the bottom-line benefit of the architecture development faster. Ensure the application of best practices to architecture work Provide an overview of the compliance of an architecture to mandated enterprise standards Identify where the standards themselves may require modification Identify services that are currently application-specific but might be provided as part of the enterprise infrastructure Document strategies for collaboration, resource sharing, and other synergies across multiple architecture teams Take advantage of advances in technology Communicate to management the status of technical readiness of the project Identify key criteria for procurement activities (e.g., for inclusion in Commercial Off-The-Shelf (COTS) product RFI/RFP documents) Identify and communicate significant architectural gaps to product and service providers

Option A