Examkin

Question

Difficulty: MediumCreating Conceptual, Logical, and Physical Architectures

An enterprise cloud architecture team at a global aviation safety oversight agency is developing a regulatory compliance analytics platform. Place the architectural design phases in the correct sequential order, starting from the highest conceptual abstraction down to concrete Google Cloud infrastructure deployment.

  1. 1Define core business domain entities, regulatory data retention policies, and high-level availability/privacy requirements for flight safety records.
  2. 2Establish technology-agnostic service boundaries, data processing pipelines, and logical security trust zones isolating telemetry ingestion from compliance reporting.
  3. 3Map functional logical components to specific Google Cloud services, selecting Cloud Pub/Sub for ingestion, Dataflow for processing, and BigQuery for analytical storage.
  4. 4Draft declarative Infrastructure as Code (IaC) templates specifying precise subnet CIDRs, IAM role bindings, and Customer-Managed Encryption Keys (CMEK) configurations.

Answer

The correct sequence starts with defining conceptual business domain entities and compliance rules, followed by designing logical service boundaries and technology-agnostic data flows, then mapping logical components to specific Google Cloud products, and finally specifying detailed physical IaC parameters like subnets, IAM bindings, and CMEK settings.
The standard enterprise architecture lifecycle progresses hierarchically from Conceptual (defining business entities, governance goals, and regulatory boundaries) to Logical (defining functional data flows, service boundaries, and security domains independent of technology choices), followed by Physical Product Mapping (matching logical blocks to GCP offerings like Pub/Sub, Dataflow, and BigQuery), and concluding with Physical Configuration Specification (specifying exact IaC code, subnets, IAM, and encryption keys).

Step-by-Step Solution

1
Identify the Conceptual Architecture phase
Established business rules, domain data definitions, and compliance requirements without technical or vendor commitments.
Architecture planning must begin by capturing business intent and governance boundaries before determining technical design.
2
Identify the Logical Architecture phase
Created component boundaries, data processing flows, and security zones independently of cloud providers.
Logical modeling structures functional capabilities and relationships without tying the design to specific physical services.
3
Identify the Physical Resource Selection phase
Selected concrete GCP services (Pub/Sub, Dataflow, BigQuery) matching logical requirements.
Physical design translates vendor-agnostic functional blocks into actual target cloud service implementations.
4
Identify the Physical Infrastructure Provisioning phase
Formulated IaC manifests containing specific VPC subnets, IAM permissions, and CMEK encryption keys.
Detailed physical configuration parameters are required for deployment automation, operational management, and security enforcement.

Key Concept

Sequential Translation from Conceptual to Logical and Physical Architectures
Estimated Time:1m 30s
Rate this question

Topics

Creating Conceptual, Logical, and Physical Architectures