Examkin

Question

Difficulty: MediumSelecting and Designing Storage and Database Resources

Match each application data access pattern on the left with the most appropriate Google Cloud database or storage service on the right based on GCP architectural best practices.

  • Storing large binary media files with configurable lifecycle rules for automatic archival to cost-effective storage tiers.Cloud Storage
  • Ingesting high-throughput time-series IoT metrics requiring consistent single-digit millisecond latency at scale.Cloud Bigtable
  • Managing financial ledger transactions requiring multi-region, strong ACID consistency with relational SQL querying.Cloud Spanner
  • Serving hierarchical mobile app user preferences requiring live client synchronization and offline database support.Firestore

Answer

Large binary media files with lifecycle rules match Cloud Storage. High-throughput time-series IoT metrics match Cloud Bigtable. Financial ledger transactions needing multi-region ACID consistency match Cloud Spanner. Mobile app user preferences with offline sync match Firestore.
Each requirement directly aligns with key capabilities of GCP database offerings: Cloud Storage for object lifecycle management; Cloud Bigtable for high-scale time-series ingestion; Cloud Spanner for global ACID relational workloads; and Firestore for mobile document syncing with offline support.

Step-by-Step Solution

1
Analyze storage object structure and access lifecycle for un-structured data requirement.
Unstructured binary objects with lifecycle management requirements uniquely fit Cloud Storage.
Cloud Storage handles unstructured file objects and lifecycle transitions across storage tiers.
2
Evaluate throughput and latency metrics for time-series IoT workload.
High-velocity streaming data requiring single-digit millisecond latency matches wide-column NoSQL.
Cloud Bigtable provides sub-10ms performance specifically designed for high-throughput time-series analytics.
3
Assess consistency and scale demands for relational financial transactions.
Multi-region horizontal scalability with ACID compliance requires Cloud Spanner.
Cloud Spanner is the only GCP service offering globally synchronous transactions with SQL capabilities.
4
Determine mobile app offline synchronization and document storage needs.
Real-time client updates and offline local caching match Firestore.
Firestore client libraries natively handle offline state persistence and dynamic real-time data sync.

Key Concept

GCP Storage and Database Resource Selection Criteria
Rate this question

Topics

Selecting and Designing Storage and Database Resources