Study guide

7.4 Technology Architecture Domain: Hardware, Software, Cloud & Network Platforms

TOGAF Enterprise Architecture Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction to TOGAF & Enterprise Architecture Concepts

1.1 Overview of TOGAF Standard 10th Edition & Enterprise Architecture Concepts 1.2 The Structure of the TOGAF Standard (Easily Navigated Body of Knowledge) 1.3 Core Concepts: Enterprise, Architecture, Deliverables, Artifacts, and Building Blocks 1.4 TOGAF Certification Paths & the OGEA-101 Exam Plan

2 Chapter 2: ADM Foundation & Preliminary Phase

2.1 The Architecture Development Method (ADM) Cycle & Requirements Management 2.2 Preliminary Phase: Scope, Principles, and Architecture Capability Setup 2.3 Tailoring the ADM & Applying Iteration / Architecture Levels 2.4 Applying the ADM: The TOGAF Library, Purpose-Based Architecture Projects & the Digital Enterprise

3 Chapter 3: ADM Architecture Vision & Business Architecture

3.1 Phase A: Architecture Vision, Stakeholder Management & Value Proposition 3.2 Business Architecture Scope, Strategy & Capability Mapping 3.3 Phase B: Business Architecture Inputs, Steps, Outputs & Artifacts 3.4 Business Scenarios & Value Stream Modeling

4 Chapter 4: ADM Information Systems Architectures (Phase C)

4.1 Information Systems Architectures Overview & Phase C Strategy 4.2 Phase C Data Architecture: Principles, Data Models & Governance 4.3 Phase C Application Architecture: Logical Components, Services & Interfaces 4.4 Data and Application Integration, Migration & Interoperability

5 Chapter 5: ADM Technology Architecture & Solution Realization (Phases D, E, F)

5.1 Phase D: Technology Architecture, Platform Services & Infrastructure 5.2 Phase E: Opportunities and Solutions & Initial Implementation Strategy 5.3 Phase F: Migration Planning, Roadmap Development & Portfolio Prioritization 5.4 Transition Architectures & Implementation Dependencies

6 Chapter 6: ADM Governance, Change & Requirements Management (Phases G, H)

6.1 Phase G: Implementation Governance & Architecture Compliance 6.2 Phase H: Architecture Change Management & Driver Monitoring 6.3 Requirements Management: Central Flow, Impact Analysis & Traceability 6.4 Architecture Contracts, Dispensations & Compliance Reviews

7 Chapter 7: BDAT Architecture Domains Deep-Dive

7.1 Business Architecture Domain: Functions, Processes & Value Streams 7.2 Data Architecture Domain: Data Entities, Storage & Data Management 7.3 Application Architecture Domain: Application Services, Systems & Integration Patterns 7.4 Technology Architecture Domain: Hardware, Software, Cloud & Network Platforms

8 Chapter 8: Architecture Content — Content Framework, Enterprise Metamodel & Artifacts

8.1 Architecture Content Framework Overview & Deliverables vs Artifacts vs Building Blocks 8.2 Architecture Building Blocks (ABBs) vs Solution Building Blocks (SBBs) 8.3 The Enterprise Metamodel: Core Concepts, Entities & Attributes 8.4 Architecture Catalogs, Matrices & Diagrams (Visual Representation) 8.5 Stakeholders, Concerns, Architecture Views & Viewpoints

9 Chapter 9: Architecture Governance, Capability & Maturity

9.1 Architecture Governance Framework & The Role of the Architecture Board 9.2 Establishing an Architecture Capability & Organizational Structure 9.3 Architecture Skills Framework, Roles & Competency Levels 9.4 Architecture Maturity Models & Capability Assessments

10 Chapter 10: Enterprise Continuum, Reference Models & Key Techniques

10.1 Enterprise Continuum, Architecture Repository & Landscape Partitioning 10.2 Technical Reference Model (TRM) & Integrated Information Infrastructure Reference Model (III-RM) 10.3 Core EA Techniques: Gap Analysis, Interoperability, Risk, Capability-Based Planning & Architecture Patterns

7.4 Technology Architecture Domain: Hardware, Software, Cloud & Network Platforms

Key Takeaways Explain This Topic AI

Technology Architecture (Phase D) defines the physical and virtual compute, storage, networking, and platform software infrastructure required to host Application and Data components.

Platform Services provide runtime execution environments, container orchestrators, database engines, and middleware, abstracting physical hardware from application software.

Cloud Service Models (IaaS, PaaS, SaaS) reallocate operational responsibilities between enterprise architecture teams and cloud service providers across hybrid and multi-cloud environments.

The Technology Standards Catalog enforces standardized hardware and software stacks, classified against the enterprise's taxonomy of technology services, to manage technical debt and prevent vendor lock-in.

Technology Lifecycle Management utilizes N-1 support strategies and proactive obsolescence tracking to retire legacy infrastructure before security and operational risks materialize.

Last updated: November 2026

7.4 Technology Architecture Domain: Hardware, Software, Cloud & Network Platforms

Technology Architecture represents Phase D of the TOGAF Architecture Development Method (ADM). It defines the software, platform, network, and hardware infrastructure required to support the deployment and execution of application services, software components, and data repositories defined in Phase C.

Technology Architecture provides the physical and virtual foundation of the enterprise architecture. Without a resilient, scalable Technology Architecture, higher-level application components and business processes will experience performance bottlenecks, security vulnerabilities, and operational downtime.

Platform Services vs. Infrastructure Components

TOGAF Technology Architecture categorizes infrastructure elements into two distinct categories: Platform Services and Infrastructure Components . +---------------------------------------------------------------------------------+

  • | APPLICATION & DATA ARCHITECTURE (Phase C Deliverables) |
  • +---------------------------------------------------------------------------------+
  • |
  • v Hosted On
  • +---------------------------------------------------------------------------------+
  • | PLATFORM SERVICES (Technical Runtime Middleware) |
  • | OS (Linux/Windows) | Runtime (.NET/JVM) | Container Orchestration (Kubernetes) |
  • | DBMS Engine (PostgreSQL) | Message Broker (Kafka) | Identity Provider (Okta) |
  • +---------------------------------------------------------------------------------+
  • |
  • v Executed By
  • +---------------------------------------------------------------------------------+
  • | INFRASTRUCTURE COMPONENTS (Physical & Virtual Hardware Assets) |
  • | Compute (x86/ARM Servers, VMs) | Storage (SAN, NAS, NVMe) |
  • | Network (Switches, Routers, Firewalls) | Cloud Data Center Facilities (AWS, Azure) |
  • +---------------------------------------------------------------------------------+
  • 1. Platform Services (Technical Middleware & Runtimes)

Platform Services are technical software building blocks that provide execution runtimes, system utilities, and middleware infrastructure to support software applications. They abstract underlying physical hardware capabilities for application developers.

Operating Systems: Linux (RHEL, Ubuntu), Windows Server.

Container Orchestrators: Kubernetes, Docker Swarm, OpenShift.

Application Runtimes: Java Virtual Machine (JVM), Node.js, .NET Core runtime.

Database Management Engines: PostgreSQL, Oracle DB, Cassandra, Redis.

Integration & Messaging Middleware: Apache Kafka, RabbitMQ, IBM MQ.

2. Infrastructure Components (Hardware & Network Assets)

Infrastructure Components represent the physical hardware, virtualized hardware resources, network devices, and data center facilities that host platform services.

Compute Resources: Bare-metal x86/ARM servers, hypervisors (VMware ESXi, KVM), virtual machines.

Storage Infrastructure: Storage Area Networks (SAN), Network Attached Storage (NAS), NVMe arrays, cloud S3 storage buckets.

Network & Security Topology: Physical switches, routers, software-defined networking (SDN), firewalls, load balancers (F5, AWS ALB), VPN gateways, and CDN edge nodes.

Cloud Computing Service Models & Deployment Architectures

Modern Technology Architecture incorporates Cloud Computing Service Models that redefine boundary responsibilities between internal enterprise IT and external cloud service providers.

Cloud Model Customer Responsibility Scope Provider Responsibility Scope Architectural Use Case

IaaS (Infrastructure as a Service) OS, Runtimes, Middleware, Data, Applications Physical Hardware, Hypervisors, Storage, Data Center Facilities Lift-and-shift legacy migrations; custom network control.

PaaS (Platform as a Service) Data, Application Code, Configurations OS, Runtimes, Middleware, Database Engines, Hardware Cloud-native application development; rapid DevOps deployment.

SaaS (Software as a Service) User Access Management, Data Entry Entire Application, Runtimes, Infrastructure, Facilities Standard business support tools (Salesforce, Office 365, Workday).

Hybrid Cloud and Multi-Cloud Topologies

Enterprises increasingly deploy Hybrid Cloud (combining on-premises data centers with public cloud instances) and Multi-Cloud architectures (using AWS, Azure, and Google Cloud concurrently). Enterprise architects must design robust network topology blueprints, such as dedicated cloud interconnects (AWS Direct Connect, Azure ExpressRoute), unified zero-trust identity federation, and multi-cloud data synchronization.

Technology Standards Catalog & Lifecycle Governance

To prevent technical debt, shadow IT, and vendor lock-in, Phase D establishes a Technology Standards Catalog , classified against the enterprise's taxonomy of technology services. The 10th Edition gives the TOGAF Technical Reference Model (TRM) , now a Series Guide marked Historical, as one example of such a taxonomy. Standards that projects must follow are recorded in the Standards Library , where TOGAF tracks each one through a Proposed, Provisional, Standard, Phasing-Out, and Retired lifecycle.

Technology Standardization Framework

Approved / Standard: Officially supported technologies for all new deployments.

Emerging / Evaluation: Promising technologies undergoing controlled POC testing.

Twilight / Phasing Out: Legacy technologies approved for maintenance but barred from new projects.

Retired / Prohibited: Unauthorized technologies that must be removed immediately due to security or support end-of-life.

Technology Lifecycle Management (N-1 Strategy)

To maintain system stability, architects enforce an N-1 Versioning Strategy , where production environments run strictly on the current stable version ( N N N ) or immediately preceding minor version ( N − 1 N-1 N − 1 ). Proactive obsolescence tracking ensures that operating systems, database engines, and hardware components are upgraded prior to vendor End-of-Life (EOL) deadlines.

  • Network Topology, Security Boundaries & High Availability Patterns
  • 1. Network Topology & Perimeter Security

In Phase D, network architecture defines physical and logical connectivity across compute nodes:

Demilitarized Zones (DMZs): Multi-tier perimeter zones separating public-facing web tier proxies from internal application servers and database clusters.

Software-Defined Networking (SDN): Micro-segmentation of virtual network zones, enforcing granular traffic filtering rules between application microservices.

Zero-Trust Network Architecture (ZTNA): Continuous authentication, mutual TLS (mTLS) encryption, and explicit authorization for every internal inter-service call.

2. Integration with Security Architecture (SABSA Alignment)

TOGAF Phase D integrates closely with SABSA (Sherwood Applied Business Security Architecture) :

Security Services: Encryption in transit (TLS 1.3), encryption at rest (AES-256), Key Management Services (KMS), and Hardware Security Modules (HSMs).

Identity & Access Management (IAM): Federated single sign-on (SSO), SAML 2.0 / OIDC protocols, role-based access control (RBAC), and privileged access management (PAM).

3. High Availability (HA) & Disaster Recovery (DR) Patterns

Physical and virtual infrastructure must satisfy non-functional Availability (RTO and RPO) requirements:

Active-Active Multi-Region Clustering: Concurrent workload processing across geographically separated cloud regions, providing zero RTO for critical services.

Active-Passive / Warm Standby: Secondary passive environment updated continuously via database replication, failing over automatically if primary region suffers outage.

Recovery Point Objective (RPO) & Recovery Time Objective (RTO): Quantitative targets driving backup cadence, transaction log shipping, and automated failover orchestration.

Loading diagram... BDAT Architecture Domain Interdependencies & Layered Stack