Introduction Knowledge-Based Practice

Questions

1. 1.

   When an enterprise architecture team establishes deliverables for stakeholder approval, how does the TOGAF Standard define the acceptable format and realization of these deliverables?

   • A) Deliverables must strictly be published as static, formal text documents to ensure legal non-repudiation in audit trails.
   • B) Deliverables can only exist as synchronized live views directly rendered from an enterprise architecture repository tool.
   • C) Deliverables must adhere to a standardized physical report template mandated uniformly across all phases of the ADM.
   • D) Deliverables are not restricted to traditional document formats and may be realized through presentations, intranet sites, or repository models.
2. 2.

   According to the TOGAF Standard, what is the typical lifecycle outcome for an architecture deliverable upon or near the completion of an architecture project?

   • A) It is dissolved into unversioned operational documentation and discarded to prevent repository sprawl.
   • B) It remains solely under project-level version control and is permanently restricted from enterprise-wide reuse.
   • C) It is archived or transitioned into the Architecture Repository as a reference model, standard, or snapshot of the Architecture Landscape.
   • D) It is automatically converted into an Architecture Contract without requiring additional governance review or sign-off.
3. 3.

   In the TOGAF Standard, what is the primary governance function of an architecture deliverable upon completion of an ADM phase?

   • A) It replaces the need for operational governance frameworks and project management charters across the enterprise.
   • B) It establishes a formal, agreed baseline that binds stakeholders and the architecture team to a validated set of architectural decisions and commitments.
   • C) It automatically approves all subsequent implementation procurements and contracts without further review by governance boards.
   • D) It transitions all operational and support accountability for target systems immediately to the architecture practice.
4. 4.

   During an ADM cycle, an enterprise architect must decide how to package and govern architectural artifacts for executive sponsors and governance boards. Which guideline from the TOGAF Standard should govern how architecture deliverables are tailored and produced?

   • A) Deliverables should be adapted, combined, or scoped to satisfy stakeholder concerns and organizational decision-making needs rather than produced as an exhaustive, rigid set of standalone documents.
   • B) Deliverables must be published as separate, unalterable formal documents for each individual catalog, matrix, and diagram defined in the ADM phases to maintain compliance.
   • C) Deliverables should be treated as informal, transient working papers that bypass milestone sign-offs until post-implementation operational handover.
   • D) Deliverables must follow the implementation partner's proprietary development methodology exclusively, eliminating the standard ADM deliverable structures.
5. 5.

   According to the TOGAF Standard, which statement accurately characterizes an architecture deliverable and distinguishes it from other architectural work products?

   • A) It is an individual architectural work product such as a catalog, matrix, or diagram used to describe a specific viewpoint.
   • B) It is an autonomous, reusable component of business, IT, or architectural capability packaged for operational deployment.
   • C) It is a contractually specified work product that is formally reviewed, agreed upon, and signed off by designated stakeholders.
   • D) It is an informal working document maintained dynamically across iterations without requiring governance sign-off or baselining.

Answers and step-by-step solutions appear after you finish the test.