Best Google Database for User Profiles Migration

PCA Last updated

Designing network, storage, and compute resources.

Short answer

D Google Cloud Datastore is the recommended NoSQL database for storing semi-structured user profile data at scale.

Question

JencoMart wants to move their User Profiles database to Google Cloud Platform. Which Google Database should they use?

  1. Cloud Spanner
  2. Google BigQuery
  3. Google Cloud SQL
  4. Google Cloud Datastore Correct Answer

Key Takeaways

The question tests the ability to match a 'user profile' use case to Google's managed NoSQL solution, often confusing it with relational options like Cloud SQL or Spanner.

Determining the optimal database for migrating user profiles requires evaluating data structure and scale, with Cloud Datastore being the ideal NoSQL choice for this specific workload.

Common mistake: Candidates often select Cloud Spanner (A) due to its global scalability, failing to recognize that user profiles are typically semi-structured key-value data best served by Datastore.

Expert Analysis

Why the Answer Is Correct

Google Cloud Datastore is a fully managed NoSQL document database designed for scalable application development. It excels at storing semi-structured data like user profiles, game states, and product catalogs, which aligns perfectly with JencoMart's requirement. The official documentation explicitly lists 'User profiles' as a primary use case for Datastore.

Why the Other Options Are Wrong

Cloud Spanner (A) is a globally distributed relational database, which is overkill and less efficient for simple profile storage unless complex joins or ACID transactions across regions are required. Cloud SQL (C) is a managed relational database (MySQL/PostgreSQL), requiring rigid schema definitions that may not fit flexible profile structures as well as NoSQL. BigQuery (B) is an analytical warehouse, not an operational transactional database for serving user profiles.

Community Comment Notes

Many learners debated between Spanner and Datastore based on the complexity of the existing Oracle DB. As noted by user dabrat, Spanner is for 'Relational + Global', while others like tartar correctly pointed out that Datastore is ideal for 'User profiles'. The consensus among those referencing official docs favored Datastore for this specific entity type.

Official Reference

https://cloud.google.com/datastore/docs/concepts/overview

Exam Strategy

Always map the data type to the database service: Relational/Complex Transactions -> Spanner/SQL; Analytical -> BigQuery; Semi-structured/NoSQL Key-Value -> Datastore/Firestore.

Frequently Asked Questions

Why not Cloud Spanner for user profiles?

Spanner is for relational data needing strong consistency and complex joins. Datastore is more cost-effective and flexible for simple key-value profile storage.

Is Datastore still available in 2024?

Yes, but it is often referred to as Firestore in Datastore mode. For exam purposes, 'Datastore' remains the standard term for this NoSQL capability.

More PCA FAQ →

Community Votes

D
89%
A
11%

89% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 66 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded.

From public community threads 30 of 66

  1. JJu 👍 28
    answer is D. Google Cloud Datastorage Google Cloud Datastorage use: User profile game state * product catalogs
  2. dabrat 👍 23
    oracle= Relational +Gloabal = spanner =>A)
  3. tartar 👍 12
    D is ok https://cloud.google.com/datastore/docs/concepts/overview 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.
  4. Ishu_awsguy 👍 8
    They have a relational oracle DB with complex table structure. I dont think Data storw will work for them. Answer should be A ( Cloud Spanner)
  5. asheesh0574 👍 7
    I believe Jencomart is not in scope for exam
Show 25 more comments
  1. cetanx 👍 5
    Alternative-1: Postgre GCP has quite some references to migration from Oracle to Postgre but it has 1000 concurrent connection limit which seems like not good enough for a company with 10K stores. It's also a regional service. Alternative-2: Datastore Datastore is a good option for storing user profile data but I am not sure if it's also good for migrating from an OLTP database with complex table structure. I couldn't find any reference to it but it any how seems like a complex migration. Alternative-3: Cloud Spanner GCP has KBs for migrating from Oracle to Cloud Spanner (https://cloud.google.com/solutions/migrating-oracle-to-cloud-spanner) so this makes Cloud Spanner a better option. Also Cloud Spanner is a global service which makes it more suitable for a company across 3-continents. I would go with "A".
  2. Ishu_awsguy 👍 5
    But yeah it is debatable on how much moderization we take. With Cloudspanner ( require less modernisation compared to Datastore) With Cloud SQL ( Require less modernisation compared to Datastore) With datastore - Best solution eventually - but the most tricky migration and modernisation. very subjective question
  3. elguando 👍 5
    I'd say A. It says their existing oracle database has a "Complex table structure". That would be easier and just as performant if migrated to cloud spanner versus trying to rewrite it for nosql.
  4. DrLu 👍 5
    Technical Requirements • Assess key application for cloud suitability. • Modify application for the cloud. **(Which means possible to change the code or database when it migrate to GCP )
  5. MahAli 👍 5 Answered D
    It was already mentioned in another question they are moving to data store :)
  6. Navi08 👍 5
    I would go with A as User Profiles Database is 20TB
  7. JohnWick2020 👍 4
    My pick is A - Cloud Spanner Reasons - the company are currently hosting apps on infra that is EOL or no longer supported. So immediate priority is to "move" database in first instance as painless as possible. The database in question is relational with a "complex setup" so my preference would be to "lift-and-shift" to Cloud Spanner (Relational) and much later to Datastore (NoSQL). Cloud Spanner is minimal effort vs DataStore which requires significant effort involving rearchitecting, data migration and optimization - among other things.
  8. AGG 👍 4
    Look at this link : https://cloud.google.com/solutions/migrate-oracle-workloads Datastore is not taken under consideration, only Cloud Spanner & Cloud SQL Expand services into Asia, Global company, outsource infra - all those words are related with Spanner - I would go with A
  9. N1_arch 👍 4
    Should be A for migrating from Oracle and complex table structure and global DB >> Spanner
  10. ESP_SAP 👍 3
    Correct Answer is (D): What it's good for 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. https://cloud.google.com/datastore/docs/concepts/overview#what_its_good_for
  11. cchiaramelli 👍 3 Answered C
    Since it is relational data, it should be A or C. Cloud SQL is the only that supports the Oracle SQL features, like Procedures and triggers, etc. I also think Cloud Spanner seems to be an overkill since it is a 20TB database, which Cloud SQL easily handles IMO, C is the cheapest and easiest, while A would require some refactorings and longer migration, which doesnt pay off for the current database's size
  12. jasim21 👍 3
    The only lift & shift option for Oracle DB is bare metal. To host on cloud spanner you need to rewrite the code. Since application modification is allowed as per technical requirement why not rewrite to most suitable product of GCP for user profile i.e. Datastore. The answer is D Reference: https://cloud.google.com/solutions/migrate-oracle-workloads
  13. JCGO 👍 3
    Question in previous page tlls that they have migrated user profiles Oracle DB to Datastore. s0 D is correct :)
  14. YashBindlish 👍 3
    Should be A, because the existing Env is using Oracle for User Profiles database…
  15. dman69 👍 3 Answered D
    Datastore is used for user profiles
  16. ankit89 👍 3
    A Option Seems more close.
  17. joe2211 👍 3 Answered D
    vote D
  18. BiddlyBdoyng 👍 2
    A: Spanner retains the RDBMS compatibility and helps to reduce latency for any Asia resources B: BigQuery no good for OLTP C: CloudSQL, the closest option we have to Oracle D: Significant architectural change but potentially a great alternative to RDBMS, document database typically a good fit for user data & as others have said it can eliminate the complex RDBMS structure and queries The problem I have with Spanner is the cost, it is extremely expensive compared to the other options, so is it really needed? But when I review the requierments I don't see cost as being up there whilst latency to Asia it is, so whilst I intuitively picked Datastore I'll revise to Spanner.
  19. jayaen 👍 2
    user profiles are semi - structured .. defintely cannot be fit into relational data . so option should be cloud data store which is no sql document store . the flowchart to choose correct data solution is as below link https://grumpygrace.dev/posts/gcp-flowcharts/#storage-and-data
  20. taer 👍 2 Answered A
    Cloud Spanner is a fully managed, scalable, and globally distributed relational database service. It provides strong consistency, high availability, and low-latency capabilities, which would be suitable for JencoMart's User Profiles database requirements.
  21. masterchief735 👍 2 Answered A
    The requirement is Global and also they nedd relational database which cloud datstore doesn't allow and bigquery is datawarehouse and for analysis and cloud sql support upto 30 TB relational database.So A should be correct.
  22. Kysmor 👍 2
    Answer is D, Datastore (as also mentioned in a previous question) and as Google documentations: "What it's good for... * User profiles that..." https://cloud.google.com/datastore/docs/concepts/overview#what_its_good_for
  23. guid1984 👍 2
    DataStore is the answer it can also eliminate their current complex table structure on premise ORACLE DB. I will choose D
  24. BeCalm 👍 2 Answered A
    This is pretty straightforward. Relational + Global = Spanner. DS not meant for TB size.
  25. lynx256 👍 2
    IMO - D is ok - for maNy reasons but also because of Question #: 3 from Topic #: 2 :)

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Optimizing Data Transfer for ETL with Cellular Connections

S-Grade

Streamlining Cloud IAM Audit Analysis with BigQuery

S-Grade

Auditing BigQuery User Query Counts

S-Grade

Practice All PCA Questions

Access 81 questions with complete answers and detailed explanations.

View Full PCA Practice Test →

← Back to PCA Study Guide