Examkin

Soru

Zorluk: Çok zorCreating Conceptual, Logical, and Physical Architectures

A global healthcare provider is translating its enterprise conceptual architecture into logical and physical cloud designs on Google Cloud. The architecture requires streaming ingestion of high-frequency IoT patient telemetry data, a globally consistent database supporting multi-region ACID transactions for clinical trial records, private service consumption between isolated line-of-business Virtual Private Clouds (VPCs) without exposing underlying network subnets or relying on transitive routing, and strict controls to prevent authorized internal users from exfiltrating data to external locations. Which physical architecture design correctly satisfies all conceptual and logical requirements while adhering to Google Cloud best practices?

  1. Deploy Pub/Sub and Cloud Dataflow for streaming ingestion, Cloud Spanner for multi-region transactional data storage, Private Service Connect for cross-VPC service communication, and a VPC Service Controls perimeter encompassing the GCP projects.Cevap
  2. B
    Deploy Pub/Sub and Cloud Run for streaming ingestion, Cloud SQL with cross-region read replicas for multi-region transactional data storage, VPC Network Peering to transitively route traffic across all line-of-business VPCs, and IAM bucket policies to prevent external data exfiltration.
  3. C
    Deploy Cloud Pub/Sub and Cloud Bigtable for streaming ingestion, Cloud Spanner for transactional data storage, HA VPN tunnels to link line-of-business VPCs across projects, and primitive Owner IAM roles to grant service accounts cross-project access.
  4. D
    Deploy Cloud Logging and Compute Engine Managed Instance Groups for streaming ingestion, Cloud SQL for multi-region transactional data storage, Dedicated Interconnect for intra-cloud VPC communication, and Storage Transfer Service for real-time exfiltration monitoring.

Cevap

Deploy Pub/Sub and Cloud Dataflow for streaming ingestion, Cloud Spanner for multi-region transactional data storage, Private Service Connect for cross-VPC service communication, and a VPC Service Controls perimeter encompassing the GCP projects.
The architecture combining Pub/Sub, Dataflow, Cloud Spanner, Private Service Connect, and VPC Service Controls correctly maps all conceptual requirements to physical GCP services while enforcing enterprise security boundaries and scalability.

Adım Adım Çözüm

1
Analyze the conceptual transactional database requirement for multi-region ACID writes.
Cloud Spanner is identified as the required physical relational storage service, as Cloud SQL does not support multi-region synchronous writes.
Global clinical trial data requires multi-region consistency and strong ACID semantics across regions.
2
Analyze the cross-VPC networking requirement for private service consumption without transitive routing or subnet exposure.
Private Service Connect (PSC) is selected to expose services privately using internal IP endpoints across VPC boundaries.
VPC Network Peering does not support transitive routing and exposes entire subnet spaces, whereas PSC abstracts underlying networks.
3
Analyze the data security and exfiltration prevention requirement.
VPC Service Controls is selected to establish a security perimeter around GCP project resources.
IAM roles alone cannot prevent authenticated users from copying data to non-approved storage locations outside the project perimeter.
4
Map the streaming ingestion logical requirement to managed physical services.
Pub/Sub combined with Cloud Dataflow provides serverless, auto-scaling stream processing.
High-frequency IoT device telemetry requires decoupled message queuing and unified pipeline processing.

Anahtar Kavram

Mapping conceptual business and operational requirements to physical GCP architectural components across data, networking, and security tiers.
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

Creating Conceptual, Logical, and Physical Architectures