Examkin

Question

Difficulty: HardManaging Technology Debt and Legacy Cloud Migrations

An energy utility enterprise is modernizing a legacy asset monitoring platform by migrating it from an on-premises data center to Google Cloud. The environment contains a 2.5 PB historical sensor dataset residing on aging SAN storage, along with a batch analytics process comprised of lightweight, stateless microservices. The company's existing 1 Gbps Dedicated Interconnect is heavily saturated, running at 90% capacity to support real-time operational telemetry. Organizational policies require moving the 2.5 PB dataset into Cloud Storage within 45 days, containerizing the batch analytics with minimal operational management overhead, and enforcing strict perimeter controls to prevent data exfiltration by compromised or authorized identities.

Which architectural strategy best fulfills these technical and business requirements?

  1. Order a Google Cloud Transfer Appliance to perform an offline bulk data import to Cloud Storage, execute the stateless batch analytics microservices using Cloud Run, and enclose the cloud resources within a VPC Service Controls perimeter.Answer
  2. B
    Stream the 2.5 PB historical dataset over the existing 1 Gbps Dedicated Interconnect using Storage Transfer Service, execute the stateless batch analytics microservices using Cloud Run, and enclose the cloud resources within a VPC Service Controls perimeter.
  3. C
    Order a Google Cloud Transfer Appliance to perform an offline bulk data import to Cloud Storage, provision a high-availability Google Kubernetes Engine (GKE) cluster to execute the stateless batch analytics microservices, and enclose the cloud resources within a VPC Service Controls perimeter.
  4. D
    Order a Google Cloud Transfer Appliance to perform an offline bulk data import to Cloud Storage, execute the stateless batch analytics microservices using Cloud Run, and enforce fine-grained IAM roles without configuring a VPC Service Controls perimeter.

Answer

Order a Google Cloud Transfer Appliance to perform an offline bulk data import to Cloud Storage, execute the stateless batch analytics microservices using Cloud Run, and enclose the cloud resources within a VPC Service Controls perimeter.
The correct strategy combines Transfer Appliance for offline petabyte data movement within the 45-day deadline, Cloud Run to run stateless microservice containers with zero cluster management overhead, and VPC Service Controls to establish a perimeter preventing data exfiltration.

Step-by-Step Solution

1
Evaluate bulk data transfer constraints
Transferring 2.5 PB over a heavily utilized 1 Gbps link (with only ~100 Mbps available) would take over two years. Using an offline Transfer Appliance is required to complete the transfer within 45 days without saturating network bandwidth.
Large multi-petabyte datasets combined with constrained or shared network pipes necessitate offline physical appliance transfer.
2
Select the optimal compute abstraction for stateless batch microservices
Cloud Run allows containerized stateless services to run on a fully managed serverless infrastructure, minimizing operational management overhead compared to managing GKE clusters.
Choosing serverless container platforms avoids the infrastructure setup, upgrading, and cluster maintenance required by GKE.
3
Enforce security controls against data exfiltration
Define a VPC Service Controls perimeter around Cloud Storage and Cloud Run services to block unauthorized data egress, even from authenticated IAM identities.
IAM controls authorization but does not prevent authorized users from exfiltrating data to external Google Cloud resources outside the perimeter.

Key Concept

Managing legacy cloud migrations by combining offline appliance data transfer, serverless container modernization, and VPC Service Controls perimeters.
Rate this question

Topics

Managing Technology Debt and Legacy Cloud Migrations

More questions from this topic