Examkin

Question

Difficulty: HardProvisioning Storage and Database Systems

A telemetry infrastructure team is designing the provisioning of a high-throughput time-series database on Google Cloud to ingest real-time IoT metrics. Additionally, they must migrate 3 petabytes of historical baseline metrics from their on-premises data center within a strict 14-day window. The company's on-premises internet link is limited to an unreserved 1 Gbps connection. Regulatory compliance mandates that all stored data at rest must be encrypted using keys managed in Cloud KMS with automated monthly rotation, while preventing team overhead associated with storing raw key material. Which combination of services and provisioning strategies meets all throughput, migration timeline, and compliance requirements?

  1. Provision Cloud Bigtable configured with Customer-Managed Encryption Keys (CMEK) referencing Cloud KMS for real-time ingestion, and request Google Cloud Transfer Appliance to perform the offline migration of the 3 PB dataset into Cloud Storage.Answer
  2. B
    Provision Cloud Spanner across a multi-region configuration using Customer-Supplied Encryption Keys (CSEK) for real-time ingestion, and deploy Storage Transfer Service over the existing 1 Gbps link to stream the 3 PB historical dataset.
  3. C
    Provision Cloud Bigtable with default Google-managed encryption keys, and set up Storage Transfer Service agents on local servers to upload the 3 PB historical dataset over the internet while maintaining Terraform state files locally without object locking.
  4. D
    Provision Cloud Bigtable configured with Customer-Supplied Encryption Keys (CSEK), and order Google Cloud Transfer Appliance to import the 3 PB offline dataset while maintaining infrastructure provisioning scripts in local unversioned files.

Answer

Provision Cloud Bigtable configured with Customer-Managed Encryption Keys (CMEK) referencing Cloud KMS for real-time ingestion, and request Google Cloud Transfer Appliance to perform the offline migration of the 3 PB dataset into Cloud Storage.
The correct strategy combines Cloud Bigtable for high-throughput time-series telemetry ingestion, Google Cloud Transfer Appliance for migrating 3 PB of data offline within 14 days, and CMEK via Cloud KMS to comply with encryption and automated rotation policies without raw key management overhead.

Step-by-Step Solution

1
Analyze data transfer timeline constraints
Calculating network throughput for 3 PB over 1 Gbps yields roughly 277 days under ideal conditions (3×1015 bytes×8 bits/byte/109 bps≈2.4×107 seconds3 \times 10^{15} \text{ bytes} \times 8 \text{ bits/byte} / 10^9 \text{ bps} \approx 2.4 \times 10^7 \text{ seconds}). An offline physical transfer appliance is mathematically required to meet the 14-day migration window.
Online streaming via Storage Transfer Service is unviable due to physical bandwidth bottlenecks.
2
Select appropriate database system for time-series IoT workload
Cloud Bigtable is the optimal high-throughput, low-latency target for time-series IoT data.
Cloud Bigtable scales linearly for continuous high-rate writes and reads.
3
Evaluate key management security and compliance requirements
Customer-Managed Encryption Keys (CMEK) via Cloud KMS allow automated key rotation without requiring raw key management overhead (unlike CSEK).
CMEK integrates natively with Cloud Bigtable and Cloud Storage while satisfying regulatory requirements.

Key Concept

Provisioning scalable storage and database resources using physical transfer mechanisms for petabyte-scale data and CMEK via Cloud KMS for security compliance.
Estimated Time:2m 0s
Rate this question

Topics

Provisioning Storage and Database Systems

More questions from this topic