Examkin

Soru

Zorluk: OrtaPlanning Database Options and Persistent Disk Types

Match each Google Cloud database or persistent disk option on the left with its target technical workload requirement on the right.

  • Cloud SpannerFully managed relational database providing multi-region horizontal scaling with strong global ACID consistency.
  • Cloud BigtableHigh-throughput NoSQL key-value store optimized for sub-10 millisecond latency on large-scale analytical and time-series workloads.
  • Extreme Persistent Disk (pd-extreme)Block storage providing configurable performance up to 120,000 IOPS for high-performance self-managed database workloads on Compute Engine.
  • FirestoreScalable serverless NoSQL document storage with real-time data synchronization for web and mobile client applications.

Cevap

Cloud Spanner matches fully managed relational database with strong global ACID consistency; Cloud Bigtable matches high-throughput NoSQL key-value store for time-series; Extreme Persistent Disk matches block storage providing up to 120,000 IOPS; Firestore matches serverless NoSQL document storage with real-time synchronization.
Each Google Cloud storage service is matched to its core architectural use case: Cloud Spanner delivers globally scalable relational transactions; Cloud Bigtable provides sub-10ms latency for massive NoSQL time-series data; Extreme Persistent Disk (pd-extreme) provides maximum block-level IOPS for VM-hosted databases; and Firestore provides serverless NoSQL document synchronization for web/mobile apps.

Adım Adım Çözüm

1
Analyze the data structure, transaction model, and scalability requirements for each workload scenario.
Differentiate between relational global transactions, NoSQL key-value throughput, NoSQL document sync, and high-performance block storage.
Selecting the proper GCP database or block storage option depends on consistency guarantees, query capabilities, and IOPS requirements.
2
Map managed database options based on database paradigm.
Pair Cloud Spanner with global relational workloads needing ACID compliance, and pair Firestore with serverless document sync for mobile/web clients.
Cloud Spanner offers horizontally scalable SQL, while Firestore focuses on document hierarchies with client SDK sync.
3
Map high-throughput NoSQL storage and specialized Compute Engine block storage.
Pair Cloud Bigtable with high-throughput low-latency NoSQL data streams, and pair pd-extreme with high-IOPS block storage for self-managed VM databases.
Cloud Bigtable handles massive analytical streams, while pd-extreme provides the highest IOPS for block devices attached to Compute Engine VMs.

Anahtar Kavram

Selecting GCP Database and Storage Solutions Based on Workload Requirements
Bu soruyu puanla

Konular

Planning Database Options and Persistent Disk Types

Bu konudan daha fazla soru