Examkin

Question

Difficulty: MediumPlanning Database Options and Persistent Disk Types

An enterprise media streaming platform is architecting its storage and database tier on Google Cloud. Match each technical workload requirement to the most appropriate Google Cloud database service or block storage option.

  • Ephemeral, sub-millisecond latency block storage for high-performance video transcoding scratch files on Compute EngineLocal SSD attached to Compute Engine
  • Fully managed relational database supporting standard SQL and ACID compliance with regional failover for subscription billingCloud SQL (Regional High Availability configuration)
  • Serverless, globally available NoSQL document database for managing dynamic user profile attributes and active session statesFirestore in Native mode
  • Petabyte-scale, high-throughput NoSQL database optimized for real-time video playback telemetry and time-series analytical ingestionCloud Bigtable

Answer

The requirement for ephemeral video transcoding scratch space pairs with Local SSD; the relational subscription billing workload pairs with Cloud SQL (Regional High Availability configuration); the serverless user profile document store pairs with Firestore in Native mode; and the petabyte-scale real-time telemetry workload pairs with Cloud Bigtable.
Each requirement is mapped directly to its optimal GCP engine based on architectural strengths: Local SSD for maximum throughput ephemeral block storage, Cloud SQL for relational transactional consistency, Firestore for flexible document management, and Cloud Bigtable for heavy time-series telemetry ingestion.

Step-by-Step Solution

1
Evaluate the requirement for high-performance temporary storage.
Video transcoding requires maximum throughput and minimal latency for scratch files, but does not require data persistence across instance restarts.
Local SSD is physically bound to the host server, providing ultra-high performance suitable for temporary scratch disk needs.
2
Evaluate the requirement for transactional relational data.
Subscription billing relies on standard SQL transactions and strict ACID guarantees paired with regional redundancy.
Cloud SQL provides managed relational engine capabilities complete with regional automated failover setups.
3
Evaluate the requirement for mobile/web user session and profile data.
Document-oriented session states benefit from a serverless, auto-scaling database with multi-region availability.
Firestore in Native mode simplifies serverless application architecture while scaling seamlessly for user state.
4
Evaluate the requirement for real-time analytics and time-series telemetry.
High-velocity streaming playback events require continuous high-throughput writes at scale.
Cloud Bigtable is designed specifically for time-series ingestion and massive analytical write workloads.

Key Concept

Selecting appropriate GCP storage types based on relational schema requirements, IOPS/latency needs, data longevity, and access patterns.
Estimated Time:1m 30s
Rate this question

Topics

Planning Database Options and Persistent Disk Types

More questions from this topic