Exam Professional Cloud Database Engineer topic 1 question 69 discussion

I think B is the correct one.https://cloud.google.com/solutions/implementing-multi-tenancy-cloud-spanner#multi-tenancy-data-management-patterns

B. From the question, it appears the multi-tenancy solution needs to be multi-regional. That suggests Spanner as the database platform. Within a multi-region instance, you cannot place a database into a specific region (D). The same is also true for a table (C) and a schema (A). That leaves B. Makes sense that you would have an instance specific to a given region to comply with the data residency requirements. Even if you did this with Cloud SQL - using the same database/schema/table design everywhere, you would still need to deploy into a specific region to satisfy the data regulations. So B still makes sense.

By using separate databases, we can ensure that all data for customers in Country A is stored within the region, meeting local data residency requirements.

to complete that it should be B: https://cloud.google.com/solutions/implementing-multi-tenancy-cloud-spanner#data_management_patterns_and_tenant_lifecycle_management

https://cloud.google.com/solutions/implementing-multi-tenancy-cloud-spanner#multi-tenancy-data-management-patterns

B because when you deploy a Cloud SQL or Spanner instance you can't specifically target a region at the schema, table, or database levels. You select the region at the instance level.

D is correct answer!

What is the difference between database and instance? Instance is where the database processing is done (memory, shorting, calculating) and database is where the data is stored. The task here is to isolate the data and keep the logic as simple as possible. So D looks like the best option to me. using one system with 1 instance with 1 set of logic ( views, procedures). But, separate , repeated set of base tables (for each PII) stored physically in different regions (data sets, databases, tablespaces).

I think it's B. Summary table at link shows only d. database and b. instance options as having high rating for reg & compliance. Option d. database does not have location flexibility - i.e. can't change location for different tenants, so then 'b.'

B https://cloud.google.com/solutions/implementing-multi-tenancy-cloud-spanner

I think it's schema: A schema is a collection of database objects like tables, triggers, stored procedures, etc.

A: Apply a schema data management pattern. • Schema: A tenant resides in exclusive tables within a database, and several tenants can be located in the same database.