Exam Professional Machine Learning Engineer topic 1 question 80 discussion

C (same question 49) keywords the inventory is thousands of web banners -> Bigtable You want to Implement the simplest solution -> AI Platform Prediction

Here are some of the reasons why C is not as simple as B: Cloud Bigtable is a more complex database to set up and manage than Firestore. Cloud Bigtable is not as secure as Firestore. Cloud Bigtable is not as well-integrated with other Google Cloud services as Firestore. Therefore, B is the simpler solution that meets all of the requirements.

go for B

see e707

as Hiromi said

I would opt for B as we have requirement of retrieval latency

Embed the client on the website, deploy the gateway on App Engine, and then deploy the model on AI Platform Prediction.

I would go with Firestore as throughput or latency requirement provided in the question are possible with Firestore and bigTable may be an overkill. Had the scenario involved super large volumes of data, CBT would have taken precedence

I think B, based on "the simplest solution" consideration.

the primary requirement mentioned in the original question is to implement the simplest solution. Firestore is a fully managed, serverless NoSQL database that can also handle thousands of web banners and dynamically changing user browsing history. It is designed for real-time data synchronization and can quickly update the most relevant web banner as the user browses different pages of the website. While Cloud Bigtable offers high performance and scalability, it is more complex to manage and is better suited for large-scale, high-throughput workloads. Firestore, on the other hand, is easier to implement and maintain, making it a more suitable choice for the simplest solution in this scenario.

The answer is C for the following reason: If you need: - Submillisecond retrieval latency on a limited amount of quickly changing data, retrieved by a few thousand clients, use Memorystore. - Millisecond retrieval latency on slowly changing data where storage scales automatically, use Datastore. - Millisecond retrieval latency on dynamically changing data, using a store that can scale linearly with heavy reads and writes, use Bigtable. Source: https://cloud.google.com/architecture/minimizing-predictive-serving-latency-in-machine-learning#choosing_a_nosql_database C is better than B because 1) the inventory is thousands of web banners and 2) we expect the user to compare many travel destinations, dates, hotels, and tariffs during their search process. It means the user's browsing history is dynamically changing, and we need to identify "the most relevant web banner that a user should see next" => we will be dynamically changing the ad as the user browses different pages of the website.

Went with C

B for me

B, for me.

I think C because of latency requirements. Cloud BigTable has high latency feature from https://cloud.google.com/bigtable

I need a DB to store the banners, so no A. We're talking of thousands of banners, so no C. Memorystore calls Redis, and other solutions, so no D. The answer is B, for me.