Google Exam Professional Cloud Database Engineer Topic 10 Question 14 Discussion

Actual exam question for Google's Professional Cloud Database Engineer exam

Question #: 14
Topic #: 10

[All Professional Cloud Database Engineer Questions]

You are choosing a database backend for a new application. The application will ingest data points from IoT sensors. You need to ensure that the application can scale up to millions of requests per second with sub-10ms latency and store up to 100 TB of history. What should you do?

AUse Cloud SQL with read replicas for throughput.

BUse Firestore, and rely on automatic serverless scaling.

CUse Memorystore for Memcached, and add nodes as necessary to achieve the required throughput.

DUse Bigtable, and add nodes as necessary to achieve the required throughput.

Show Suggested Answer

Suggested Answer: C

by Willard at Feb 07, 2023, 03:45 AM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Database Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Gracia

18 days ago

I'm just picturing the poor database admin trying to keep up with adding Bigtable nodes like a hamster on a wheel. 'Wheee, another node! Wheee, another node!'

upvoted 0 times

...

Melodie

21 days ago

Cloud SQL with read replicas? Really? That's like trying to use a bicycle to haul a freight train. This application needs serious big-data firepower, not your grandpa's SQL database.

upvoted 0 times

...

Cassie

27 days ago

Ooh, Memorystore for Memcached? That's an interesting idea! But I'm not sure if it can keep up with the insane throughput and data volume this application needs. Definitely not a good fit in my opinion.

upvoted 0 times

...

Aileen

29 days ago

I'm not so sure about Bigtable. What about Firestore? It's serverless, so you don't have to worry about scaling it up yourself. And it can probably handle the data volume and throughput requirements.

upvoted 0 times

Taryn

2 days ago

A) Use Cloud SQL with read replicas for throughput.

upvoted 0 times

...

2 months ago

I think we should go with option D, Bigtable, because it can handle massive amounts of data and scale easily.

upvoted 0 times

...