Examkin

Question

Difficulty: HardCreating Conceptual, Logical, and Physical Architectures

An enterprise architecture team for a global digital publishing platform is translating high-level business goals into a structured architecture framework on Google Cloud. During this transition, they must map logical system components (such as decoupled messaging, perimeter boundaries, and data persistency) to concrete physical GCP service implementations.

Which TWO architectural mapping decisions correctly translate the logical requirements into physical Google Cloud component selections while avoiding architectural anti-patterns? (Select TWO.)

  1. Mapping the logical tier for real-time decoupled ingestion and stream analytics to Cloud Pub/Sub combined with Cloud Dataflow.Answer
  2. Mapping the logical security perimeter boundary for cross-service network isolation and data exfiltration defense to VPC Service Controls.Answer
  3. C
    Mapping the logical perimeter boundary for data exfiltration protection to project-level primitive IAM roles (Owner/Editor) without VPC Service Controls boundaries.
  4. D
    Mapping the logical requirement for a regional single-instance relational content management database to a multi-region Cloud Spanner instance to minimize operational cost.
  5. E
    Mapping the logical requirement for a basic, low-traffic stateless HTTP request redirector microservice to a multi-zone GKE cluster to simplify management overhead.

Answer

The correct architectural mappings are: 1) Mapping real-time decoupled ingestion and stream analytics to Cloud Pub/Sub and Cloud Dataflow, and 2) Mapping perimeter security boundaries for data exfiltration defense to VPC Service Controls.
Mapping real-time decoupled event ingestion to Cloud Pub/Sub with Cloud Dataflow directly aligns the logical requirement for asynchronous messaging and pipeline analytics to managed physical services. Additionally, defining data exfiltration boundaries using VPC Service Controls correctly translates logical perimeter isolation into a physical security boundary on Google Cloud.

Step-by-Step Solution

1
Analyze the logical requirements for event processing and perimeter security.
Real-time asynchronous messaging maps logically to Pub/Sub and stream processing to Dataflow. Security isolation across service boundaries maps to VPC Service Controls perimeters.
Conceptual architectures define overall capability goals, logical architectures map functional capabilities and boundaries, and physical architectures implement concrete GCP products.
2
Evaluate the invalid physical service choices for storage, compute, and security.
Cloud Spanner for regional relational workloads creates cost overruns; GKE for simple stateless microservices adds unwanted cluster management complexity; primitive IAM roles fail to prevent data exfiltration across perimeters.
Selecting physical GCP components requires balancing non-functional requirements like cost, operational complexity, and zero-trust perimeter defense.

Key Concept

Translating Logical Architecture into Physical GCP Service Selections
Rate this question

Topics

Creating Conceptual, Logical, and Physical Architectures