Examkin

Soru

Zorluk: ZorCreating Conceptual, Logical, and Physical Architectures

A national electrical utility company is designing a new cloud platform on Google Cloud to collect, analyze, and store smart meter data. The architectural plan defines three logical tiers: an Ingestion Tier for high-throughput time-series telemetry from 5 million meters, a Storage Tier split between high-volume time-series metrics and standard single-region relational customer billing metadata, and a Security Tier enforcing strict perimeter boundaries to prevent authorized internal users from exfiltrating sensitive telemetry to external storage locations. Which physical Google Cloud architecture best maps these logical tiers to meet all operational and security requirements?

  1. Ingest telemetry using Cloud Pub/Sub and Cloud Dataflow; store time-series metrics in Cloud Bigtable and billing metadata in Cloud SQL; enforce data exfiltration protection by configuring VPC Service Controls perimeters around the storage resources.Cevap
  2. B
    Ingest telemetry using Cloud Pub/Sub and Cloud Dataflow; store time-series metrics in Cloud Bigtable and billing metadata in Cloud Spanner; enforce data exfiltration protection by configuring VPC Service Controls perimeters around the storage resources.
  3. C
    Ingest telemetry using Cloud Pub/Sub and Cloud Dataflow; store time-series metrics in Cloud Bigtable and billing metadata in Cloud SQL; enforce data exfiltration protection strictly using fine-grained Cloud IAM roles without enabling VPC Service Controls.
  4. D
    Ingest telemetry using self-managed Apache Kafka deployed on a Google Kubernetes Engine (GKE) cluster; store time-series metrics in Cloud Bigtable and billing metadata in Cloud SQL; enforce data exfiltration protection by configuring VPC Service Controls perimeters.

Cevap

The optimal architecture uses Cloud Pub/Sub and Cloud Dataflow for ingestion, Cloud Bigtable for time-series metrics, Cloud SQL for single-region relational billing metadata, and VPC Service Controls to prevent data exfiltration.
The solution correctly maps each logical tier to optimal GCP physical resources: Cloud Pub/Sub and Dataflow provide fully managed stream ingestion and transformation; Cloud Bigtable handles high-throughput time-series writes; Cloud SQL satisfies single-region relational database demands cost-effectively; and VPC Service Controls establishes perimeter security to prevent data exfiltration.

Adım Adım Çözüm

1
Analyze logical ingestion requirements
High-throughput streaming telemetry from millions of meters requires scalable event ingestion and stream processing, accurately provided by Cloud Pub/Sub and Cloud Dataflow.
Managed streaming services scale automatically without infrastructure maintenance.
2
Evaluate logical storage requirements for telemetry and billing data
Time-series data requires high-write throughput (Cloud Bigtable), while single-region relational billing data requires standard SQL (Cloud SQL).
Cloud Spanner is unnecessary for single-region relational databases and adds unnecessary cost and complexity.
3
Map security and perimeter exfiltration requirements to physical GCP controls
VPC Service Controls establishes security perimeters around Google Cloud APIs and storage services to block data exfiltration.
IAM alone cannot prevent authorized users from copying data outside the security perimeter.

Anahtar Kavram

Translating Conceptual and Logical Tiers into Physical GCP Solution Architectures
Bu soruyu puanla

Konular

Creating Conceptual, Logical, and Physical Architectures