TOGAF® 9.2 Level 1 Wonder Guide Volume 1 – 2023 Enhanced Edition: TOGAF® 9.2 Wonder Guide Series, #1

By Ramki

Best way to prepare for TOGAF 9.2 Level 1 (Foundation) Exam

This Exam continues even when TOGAF 10 is released.  All are advised to take TOGAF 9.2 Certification and then, if needed, upgrade to TOGAF 10 through a simple one hour Bridge Exam.

This series of Volumes are prepared with you in mind and above pointers in the background

Volume 1 and Volume 2 covers modules as found in its contents. Volume 3 completes rest of the modules and also provides a consolidated view of important points of all the modules in the first two Volumes.

You may not find so much of explanation of how the answer is arrived at in any other Book or any other internet source. Our Book Series is quite unique. And are now updated as of 2023 to be in tune with the latest trends in the Exam questions pattern.

• Language: English
• Publisher: Ramki
• Release date: May 12, 2023
• ISBN: 9798223223924

Ramki

Author :   Ramakrishnan N  (Ramki)   Near 50 years of experience in Software Architecture, Enterprise Architecture Design (UML, others) and Patterns (GOF, Microservices and many more), SOA to Microservices to Cloud Native and few State-of-Art technologies.    Consultant and High-end Trainer to many prestigious International Enterprises   Certified in TOGAF 9 and TOGAF 10   Based at Bangalore, India.       Reachable through : [e-mail]

Book preview

Module 1 : Introduction and Core concepts of TOGAF®

Note that questions do come up with answer choices picked up from other modules beyond these. However correct answer may appear within the Module.

Revisit all questions after revising the whole of TOGAF®.

Q 101 Which one of the following best describes TOGAF® ?

A. A framework and method for architecture development

B. An architecture pattern

C. A business model

D. A method for developing Technology Architectures

E. A method for IT Governance

Explanation : Why read this ? To be prepared with other similar questions that could come up. Also, as a preparatory work in understanding TOGAF® and even be somewhat prepared for Level 2 Certification, which is based on the same syllabus.

TOGAF® - The Open Group Architecture Framework is a framework - a detailed method and a set of supporting tools - for developing an Enterprise Architecture.

A Framework, because it is an EAF : Enterprise Architecture Framework and in turn contains a method : ADM – Architecture Development Method which is meant for providing the process for developing ( Enterprise and Solution) Architectures.

 See : 1.3 Executive Overview

An Architecture Framework is a foundational structure, or set of structures, which can be used for developing a broad range of different architectures. : Note phrases like : ‘structure’, ‘range of different architectures’. This means EAF and TOGAF® will focus only on Architecture (including Design and means of implementation through coding and so on). Architecture design is a technically complex process, and the design of heterogeneous, multi-vendor architectures is particularly complex. TOGAF® therefore plays an important role in helping to de-mystify and de-risk the architecture development process and gets into Enterprise Architecture in depth, Solution Architecture to a reasonable depth and into Project Management and Solution Development issues to a reasonable extent.

TOGAF® provides a platform for adding value and enables users to build genuinely open systems-based solutions to address their business issues and needs.  TOGAF® in turn may involve Architectural approaches and Patterns, Business models, Technology and other Architectures as also IT Governance. But by itself TOGAF® is large superset of all these things and best be referred to as EA Framework.

Answer : A

Q 102 Which of the following statements do not describe an Enterprise ?

A. Collection of organization that has a common set of goals

B. HR departments of two competing companies

C. Division of a Corporation

D. HR department of a Corporation

Explanation :

Two competing enterprises cannot have a common department.

See under : 1.3 Executive Overview

What is an enterprise ?

TOGAF® defines enterprise as any ….. that has a …. For example, …. linked together by …. : So almost any organization, including non-IT related ones can ideally come under TOGAF®. It is about one department or a group of departments (organizations) or about a single Enterprise or a group of related Enterprises : must have ‘common goals’. Read the examples given and see if they could have ‘common ownership’.

For example, an enterprise could be : Get to know the variety of examples.

■ A whole …. a corporation

■ A … department

■ A …. by common ownership

■ Groups of … working together to ….

■ … and … of businesses working together, such as a …

Be prepared for Level 1 question involving any of the above points.

The idea of providing Explanation for each answer is not just to tell you how we arrive at the answer, but also to prepare you for any other question on the topic that is not explicitly listed here.

Answer : B

Q 103 Which part of the TOGAF® document provides a number of architecture development phases, together with narratives for each Phase ?

A. Part I : Introduction

B. Part II : Architecture Development Method (ADM)

C. Part III : ADM Guidelines and Techniques

D. Part IV : Architecture Content Framework

E. Part V : Enterprise Continuum and Tools

Explanation :

PART II : Architecture Development Method describes the TOGAF® Architecture Development Method : (ADM) - a step-by-step approach to developing an Enterprise Architecture in a number of phases.

See : Chapter 4. Introduction to Part II

This chapter describes the …… (…) cycle, adapting the …, … scope, and .. integration : Note every word here.   

Part number of TOGAF® documentation is likely to be a frequent question. This is because you are expected to be very familiar with the Parts, Sections and contents of TOGAF® documentation. Do not refer to TOGAF® 9.1 or earlier documentation where Part numbers are different. It is unfortunate that most mock exams online refer to those part numbers of earlier versions of TOGAF® when giving the answer.

It is not only different but is also comes as different way of packaging in TOGAF® 10 and is supplemented with too many Series Guides in TOGAF® 10 Exam syllabus as compared to TOGAF® 9.2 Exam. Our books on TOGAF® 10 provide clarification and our Book on Bridge Exam (TOGAF® 10 Bridge Exam Certification Preparation : Friendly Wonder Guide) lays down the easy path to get TOGAF® 10 Certificate with just an one hour Exam to those who have TOGAF® 9.2 (or even TOGAF® 9.1) Certificate. Books similar to this 9.2 Series ae also available to those who are taking TOGAF® 10 Exam in full directly.

Answer : B

Q 104 In TOGAF®, what is the difference between an artifact and a deliverable ?

A. An artifact contains one or more deliverables

B. Artifacts and deliverables are synonymous; there is no difference between them

C. Deliverables are prepared by the Project Manager, whereas artifacts are defined by the Architect

D. Deliverables are reusable, whereas artifacts are unique to a given architecture project

E. Deliverables are specified as contractual outputs from a project, whereas artifacts are not

Explanation :

Be doubly clear on this distinction. Read portion here a few times till you get the point.

Deliverable : Contractually mandated. Architect delivers, usually not individual Artifact, but duly grouped Components

Artifact : Any piece (single element) of Architectural Value. A table in Data Architecture is an artifact. When a group of related tables are taken up in the architecture, along with all the relationship (Primary -Foreign Keys, joins etc.,) it is a Building Block. It is a Component which can find re-use in any other similar architecture work, may be with minimal changes therein.

Non-Deliverable Artifacts / Components may be optionally prepared and submitted as part of Architectural work. TOGAF® may mandate Statement of Architecture Work in Architecture Vision Phase, but nothing stops the architect from adding up another supplementary document to clarify the details. This additional document is a non-deliverable (not mandated, but felt necessary to supplement the work) from the architect.

Both categories are Architectural Work Pieces (Work Products). One of them (Deliverable) is compulsory and mandatory. Note that mandatory in the sense it is made compulsory by virtue of Tailored TOGAF® that is accepted to be followed by the Enterprise.

See under : 2.5 Deliverables, Artifacts, and Building Blocks

■ A deliverable is a …. that is …. specified and in turn …, …, and … by the stakeholders : Why is it a work product ? What is the role of stakeholder and what is role of Architect during their preparation ? : Architects prepare them as per contractual (meaning, as mandated by TOGAF®) and then review them with the stakeholders, get their sign-off approval thereafter.

Deliverables represent the output of projects and those deliverables that are in documentation form will typically be archived at completion of a project or transitioned into an Architecture Repository as a reference model, standard, or snapshot of the Architecture Landscape at a point in time.

■ An artifact is an ….. that describes … architecture. Artifacts are …. as …(…. things), matrices (… between things), and diagrams (… things). Examples include … and a … diagram. An architectural … may contain … and artifacts …. : Artifact is just one element (describing one aspect at a time) while Building Blocks may cover a group of them and so are more often know to us as Components or even Sub Systems. Get to know the here type of classifications of catalog – like a bullet pointed list, matrix like an Excel sheet and of course varieties of diagrams that are together bracketed here. Study the examples and relate to your own architectural experiences. What is the one-to-many relationship mentioned here ? What is the connection with the Repository ?

Answer : E

Q 105 Which of the TOGAF® architecture development phases includes the development of Data and Application Architectures ?

A. Phase A

B. Phase B

C. Phase C

D. Phase D

E. Phase E

Explanation :

This is how TOGAF® specified ADM has in its Phase C : Information Systems Architecture

See in TOGAF® Documentation :

Chapter 8  : Phase C: Information Systems Architectures

Chapter 9 : Phase C: Information Systems Architectures — Data Architecture

Chapter 10 : Phase C: Information Systems Architectures — Application Architecture

Phase C: Information Systems Architectures together describes the development of Information Systems Architectures for an architecture project, meaning all that information related (generating, storing and the like) in the form of Architecture is covered in such portions of the project. This naturally incudes the development of Data Architecture and Application Architecture.

Phase C is both about Data Architecture and Application Architecture. It describes these in the development method of Enterprise Architecture. No other Phase is directly about these two.

TOGAF® has made both Data and Application Architecture to be part of same Phase C. This is done deliberately since both these domains of architecture are close to each other and need frequent referencing between them doing the design stages.

Answer : C

Q 106 Which one of the following is the reason why the first execution of an ADM cycle will be more difficult than later cycles ?

A. Because management is not familiar with the ADM process

B. Because there are few architecture assets available

C. Because of lack of governance

D. Because of insufficient trained architecture practitioners

E. Because the Baseline Architecture must be fully defined across the enterprise

Explanation :

If TOGAF® is practiced for the first time and ADM cycle starts, there will be zero to very little architectural assets available in the Architecture Repository. When the projects move through ADM Phases, gradually assets will get added up.

See : 4.1.1 The ADM, Enterprise Continuum, and Architecture Repository, appearing under 4.1 ADM Overview

The …execution of the ADM will often be the …, since the … will be relatively scarce. Even at this …., however, there will be .. available from … such as TOGAF®, as well as the …. at large, that could be .. effort.

TOGAF® refers to a number of Reference materials and others as external references, including ones such as ARTS, Energistics. SIB – Standard Information Base etc., Still during the start of a fresh TOGAF®, there will hardly be any pre-existing architectural works, known as Baseline Architecture. 

Of course, only start-up organization will have TOGAF® based Enterprise Architecture from its inception. Most of our organizations will have different kind of architectural practices before moving to TOGAF®. Still the first execution under TOGAF® will be tougher because of the learning curve involved in arranging the available architectures in the right place.

Answer : B

Q 107 Which of the following is a reason to adapt ADM ?

A.  All of the answers below

B.  The use of TOGAF® is being integrated with another Framework

C.  The ADM is being used for a purpose other than Enterprise Architecture

D.  The Enterprise is a large Federated Organization

E.  The IT governance model needs to be tailored

Explanation :

TOGAF® clearly specifies the reasons why every Enterprise should take TOGAF® Documentation a first cut one and duly tailor ( customize / adapt) it as an Enterprise-Specific one. Important to get to know them. See : 4.3 Adapting the ADM. Look at each answer choice from B to E from that angle.

For answer choice B) The Architecture Development Method (ADM) is a flexible process that can be used to support the development of architecture as a stand-alone process, or as an extension to other solution development or project management methods. TOGAF® never claims to be a stand-alone framework.

For example, an enterprise may wish to use TOGAF® and its generic ADM in conjunction with the well-known Zachman Framework, or another Enterprise Architecture framework that has a defined set of deliverables specific to a particular vertical sector : Government, Defence, e-Business, Telecommunications, etc., The ADM has been specifically designed with this potential integration in mind.

For answer choice C) The ADM is a generic method for architecture development, which is designed to deal with most system and organizational requirements. However, it will often be necessary to modify or extend the ADM to suit specific needs. So is it that ADM is tied with EA ? Note that TOGAF® can be used outside of IT.

For answer choice D) The term enterprise in the context of enterprise architecture can be used to denote both an entire enterprise - encompassing all of its information and technology services, processes, and infrastructure - and a specific domain within the enterprise. In both cases, the architecture crosses multiple systems, and multiple functional groups within the enterprise. ADM is useful here but will need Tailoring.

For answer choice E) TOGAF® provides an industry standard framework for architecture that may be used in a wide variety of organizations. However, before TOGAF® can be effectively used within an architecture project, it needs adaptation, including in its Governance stipulations.

Answer : A

Q 108 According to TOGAF®, which one of the following best describes an enterprise architecture ?

A.  An Architecture of a Commercial Organization

B.  An Architecture that consists of more than one subsidiary company

C.  An Architecture that crosses multiple systems and multiple functional groups within the enterprise

D. The highest level of Architecture that can be achieved in a given organization

Explanation :

Why not answer choice A) : An architecture of a commercial organization. Because TOGAF® can be applied to ANY enterprise. It can be Government, military, private corporate : Just any Enterprise

Why not answer choice B) : An architecture that consists of more than one subsidiary company. Because TOGAF® can apply to a standalone enterprise with or without subsidiaries.

Why not answer choice D) : The highest level of architecture that can be achieved

Reviews for TOGAF® 9.2 Level 1 Wonder Guide Volume 1 – 2023 Enhanced Edition

[Duc Do · Rating: 5 out of 5 stars]

Verygood. I'll share my friends. good and good for me and everyone