Question

Difficulty: MediumCreating Conceptual, Logical, and Physical Architectures

An enterprise intermodal freight operator is designing a modernized fleet telemetry system on Google Cloud. As the Principal Cloud Architect, you must translate high-level business requirements into a production-ready solution following Google Cloud architecture framework best practices. Place the architectural design phases in the correct sequential order, starting from initial business abstraction down to physical infrastructure deployment.

  1. 1Define the Conceptual Architecture by mapping business goals and service level objectives (SLOs) to functional capabilities (e.g., event ingestion, real-time analytics, archival storage) without referencing specific cloud services or vendor implementations.
  2. 2Formulate the Logical Architecture by identifying data flow pathways, decoupling interfaces, trust perimeters, and component abstractions (e.g., publish-subscribe messaging pattern, NoSQL key-value store, API gateway).
  3. 3Specify the Physical Architecture component mapping by selecting concrete Google Cloud services (e.g., Cloud Pub/Sub, Cloud Bigtable, BigQuery, VPC Service Controls) that satisfy the capacity, latency, and compliance requirements.
  4. 4Execute Physical Resource Deployment by writing Infrastructure-as-Code (Terraform) scripts to provision specific VPC subnets, IAM service accounts, GKE node pools, KMS keys, and network security perimeters.

Answer

The correct sequence starts with defining the Conceptual Architecture (functional business capabilities), followed by formulating the Logical Architecture (component boundaries and data flows), specifying the Physical Architecture component mapping (selecting Google Cloud services), and finally executing Physical Resource Deployment (provisioning via Infrastructure-as-Code).
The standard architectural design progression begins with the Conceptual Architecture (establishing high-level functional capabilities from business needs), progresses to the Logical Architecture (defining technology-agnostic data flows, security boundaries, and component interfaces), transitions to Physical Architecture selection (mapping logical blocks to specific Google Cloud services such as Cloud Pub/Sub and Bigtable), and culminates in Physical Deployment (instantiating actual GCP infrastructure via IaC).

Step-by-Step Solution

1
Identify the conceptual design phase
Map business requirements and SLA/SLO expectations into vendor-neutral functional capabilities.
Designing starts at the highest abstraction layer to ensure alignment with business goals before choosing technical components.
2
Determine the logical component structure
Define data movement patterns, security boundaries, and architectural patterns (e.g., event-driven ingestion, stream processing).
Logical modeling organizes interaction patterns and data contracts without locking into specific Cloud vendor SKUs.
3
Select physical Google Cloud products
Map logical tiers to physical GCP services like Pub/Sub, Cloud Bigtable, BigQuery, and VPC Service Controls.
Physical selection requires matching technical constraints (throughput, latency, compliance) to actual cloud service specs.
4
Provision physical infrastructure
Write and apply declarative IaC templates (Terraform) to deploy VPC networks, IAM roles, KMS keys, and compute clusters.
Deployment is the final execution stage where concrete infrastructure resources are instantiated in the target GCP projects.

Key Concept

Architectural Abstraction Layers (Conceptual -> Logical -> Physical)
Rate this question