Examkin

Question

Difficulty: MediumCreating Conceptual, Logical, and Physical Architectures

An enterprise cloud architecture team for a global satellite imagery provider is designing a new cloud solution architecture on Google Cloud to ingest, process, store, and distribute petabyte-scale earth observation data. To ensure alignment with enterprise architecture standards, the team must translate business requirements progressively through conceptual, logical, and physical architecture design phases. Arrange the architectural design activities in the correct sequential order from initial conceptual abstraction down to physical infrastructure enforcement.

  1. 1Define high-level business domains, functional capabilities, and broad technology-agnostic system boundaries for raw telemetry ingestion, automated raster processing, long-term archival, and external API distribution.
  2. 2Map business capabilities into logical service tiers, data flow paths, decoupling mechanisms, and security trust zones without binding to specific cloud vendor products.
  3. 3Select specific Google Cloud services such as Cloud Storage dual-region buckets, Cloud Pub/Sub, Google Kubernetes Engine (GKE) Autopilot, BigQuery, and VPC Service Controls to fulfill logical components.
  4. 4Develop Infrastructure as Code (IaC) templates to configure network subnets, private Service Connect endpoints, customer-managed encryption keys (CMEK), IAM roles, and VPC Service Control perimeters.

Answer

The correct sequence starts with defining high-level business capabilities and domains (conceptual architecture), followed by mapping capabilities into vendor-agnostic logical tiers and data flows (logical architecture), then selecting specific concrete Google Cloud services (physical architecture selection), and finally authoring Infrastructure as Code templates to configure detailed networks, IAM, CMEK, and security perimeters (physical implementation).
Enterprise cloud architecture design strictly flows top-down: Conceptual Architecture (defining business capabilities and domains without technology dependencies) -> Logical Architecture (structuring data flows, component boundaries, and security trust zones) -> Physical Architecture Selection (mapping logical tiers to specific Google Cloud services like GKE, BigQuery, Cloud Storage) -> Physical Implementation (authoring IaC code for exact subnets, CMEK, IAM, and VPC Service Control perimeters).

Step-by-Step Solution

1
Identify the Conceptual Architecture step
Defining high-level business capabilities, functional domains, and technology-agnostic boundaries forms the initial conceptual blueprint.
Conceptual architectures establish 'what' the business system does independent of implementation details or vendor choices.
2
Identify the Logical Architecture step
Mapping conceptual capabilities into logical service tiers, decoupled data flows, and trust zones establishes the logical design.
Logical architectures define structural relationships, data flow models, and component boundaries prior to selecting specific technologies.
3
Identify the Physical Component Selection step
Selecting specific Google Cloud managed services (e.g., Cloud Storage, Pub/Sub, GKE Autopilot, BigQuery) translates logical tiers into physical technology choices.
Physical architecture translates logical constructs into specific cloud products, resource configurations, and vendor technologies.
4
Identify the Physical Implementation & Guardrails step
Authoring IaC scripts to provision subnets, private Service Connect endpoints, CMEK keys, and VPC Service Control perimeters completes the physical instantiation.
Detailed deployment artifacts and security perimeters represent the final executable state of physical architecture.

Key Concept

Progressive Architectural Abstraction: Conceptual to Logical to Physical Architecture
Rate this question

Topics

Creating Conceptual, Logical, and Physical Architectures