Examkin

Question

Difficulty: HardCreating Conceptual, Logical, and Physical Architectures

An enterprise cloud architecture team at a global pharmaceutical corporation is establishing a design framework for a new GCP-based clinical trial telemetry platform. The framework requires systematic translation of business goals into provisioned infrastructure. In which sequential order should the cloud architect arrange the architectural design phases, starting from initial business requirements through to final GCP infrastructure deployment?

  1. 1Conceptual Architecture: Define high-level business capabilities, regulatory compliance scope (such as HIPAA and FDA 21 CFR Part 11), and vendor-neutral domain information flows.
  2. 2Logical Architecture: Establish functional software tiers, abstract data processing contracts, event-messaging patterns, and trust boundaries independent of specific cloud products.
  3. 3Physical Architecture: Map abstract logical tiers to concrete GCP services (e.g., Cloud Pub/Sub, Cloud Spanner with CMEK), defining specific VPC subnets, regions, and IAM roles.
  4. 4Implementation Specification: Author Terraform Infrastructure as Code (IaC) manifests, VPC Service Controls perimeter configurations, and CI/CD deployment pipelines.

Answer

The correct sequence begins with establishing the Conceptual Architecture (business domain and compliance requirements), followed by the Logical Architecture (vendor-neutral functional tiers and data processing contracts), then the Physical Architecture (mapping logical components to specific GCP managed services, VPC topologies, and IAM), and concludes with the Implementation Specification (writing IaC manifests, VPC SC perimeters, and deployment pipelines).
The architectural translation lifecycle begins with Conceptual Architecture (defining business capabilities, compliance, and domain boundaries), progresses to Logical Architecture (defining vendor-neutral functional modules, data contracts, and trust perimeters), translates into Physical Architecture (mapping logical components to concrete GCP services like Pub/Sub and Spanner, along with VPC/IAM topologies), and finishes with Implementation Specification (authoring Terraform IaC code, VPC SC perimeters, and CI/CD deployment pipelines).

Step-by-Step Solution

1
Identify high-level business capabilities, governance policies, and compliance boundaries.
Establishes the Conceptual Architecture phase to ground the architecture in enterprise business objectives.
Architectural design must originate from business requirements, regulatory constraints, and domain boundaries without premature technical bias.
2
Define functional software tiers, messaging contracts, and logical security perimeters.
Establishes the Logical Architecture phase.
Logical design structures software capabilities and data flows into technology-agnostic patterns prior to vendor service selection.
3
Select concrete Google Cloud managed services, regional deployments, and explicit IAM controls matching the logical design.
Establishes the Physical Architecture phase.
Physical design binds logical components to real GCP resources (e.g., Cloud Spanner, Cloud Pub/Sub, CMEK) and physical network boundaries.
4
Translate the physical design blueprint into executable provisioning scripts and pipelines.
Establishes the Implementation Specification phase.
Deployment automation (IaC templates like Terraform and CI/CD pipelines) requires a finalized physical architecture specification to build the environment.

Key Concept

Sequential Translation across Conceptual, Logical, Physical, and Implementation Layers in Cloud Architecture
Rate this question

Topics

Creating Conceptual, Logical, and Physical Architectures