Your existing application keeps user state information in a single MySQL database. This state information is very user-specific and depends heavily on how long a user has been using an application. The MySQL database is causing challenges to maintain and enhance the schema for various users.
Which storage option should you choose?
For user-specific state information that varies significantly and requires a schema that can evolve over time, a NoSQL database like Cloud Datastore or Firestore is typically more appropriate. These databases provide a flexible schema, which allows you to easily make changes as the application evolves and user requirements become more complex. Additionally, they offer strong consistency and automatic scaling, which helps in managing a high volume of users without needing significant manual effort to maintain and enhance the schema.
Question sais that there are challenges to maintain and enhance schema, so schemaless DB is more preferable, moreover google mention that Datastore/Firestore is good for users profiles (https://cloud.google.com/datastore/docs/concepts/overview#what_its_good_for) Answer: D)
"Datastore is ideal for applications that rely on highly available structured data at scale. You can use Datastore to store and query all of the following types of data: Product catalogs that provide real-time inventory and product details for a retailer. User profiles that deliver a customized experience based on the user’s past activities and preferences. Transactions based on ACID properties, for example, transferring funds from one bank account to another."
D is the answer
D is right one.
D is correct
The question is a bit misleading. If its asking to keep a MySQL storage option then Cloud SQL or Spanner are the only options. However, assuming that they want to move away from schema and also the need for stateful DB I would go for Datastore/Firestore.
D is correct answer
https://cloud.google.com/datastore/docs/concepts/overview#what_its_good_for -> "User profiles that deliver a customized experience based on the user’s past activities and preferences". Answer id D.
D for sure
Option D
Out of the options provided, Cloud Datastore or Cloud Firestore would be the best choice for storing user state information that is very user-specific and depends heavily on how long a user has been using an application. This is because both Cloud Datastore and Cloud Firestore are NoSQL document databases designed for storing, retrieving, and managing semi-structured data at scale. They are well-suited for storing complex, hierarchical data structures and can handle a high volume of read and write operations. Additionally, Cloud Datastore and Cloud Firestore offer strong consistency and automatic scaling, which can help your application handle a high volume of users without requiring significant manual effort to maintain and enhance the schema.
Cloud SQL (MySQL) is the current storage option that is causing challenges to maintain and enhance the schema, so it is not a suitable solution.
Cloud Spanner is a highly scalable, distributed database system, but it may not be the most efficient solution for storing user state information that depends heavily on how long a user has been using the application.
Cloud Storage is not suitable for storing user state information as it is an object storage service that is not designed for storing structured data.
Since we need a flexible schema we can use Datastore/Firestore
The last sentence subtly implies a schema-enforced database is not the right solution for this use case.
D. Cloud Datastore/Firestore For user-specific state information that varies significantly and requires a schema that can evolve over time, a NoSQL database like Cloud Datastore or Firestore is typically more appropriate. These databases provide a flexible schema, which allows you to easily make changes as the application evolves and user requirements become more complex.
Resposta D