Your company has a data warehouse that keeps your application information in BigQuery.
The BigQuery data warehouse keeps 2 PBs of user data.
Recently, your company expanded your user base to include EU users and needs to comply with these requirements: -> Your company must be able to delete all user account information upon user request.
-> All EU user data must be stored in a single region specifically for EU users.
Which two actions should you take? (Choose two.)
Click on the arrows to vote for the correct answer
A. B. C. D. E.CE.
https://cloud.google.com/solutions/bigquery-data-warehouseTo comply with the requirements of deleting all user account information upon user request and storing all EU user data in a single region specifically for EU users, you should take the following two actions:
B. Create a dataset in the EU region that will keep information about EU users only.
To store all EU user data in a single region, you should create a BigQuery dataset in the EU region. A dataset is a container for tables, views, and routines, and it allows you to organize and control access to your data. By creating a dataset in the EU region, you can ensure that all data related to EU users is stored in a single location.
To create a dataset in the EU region, you can use the following steps:
C. Create a Cloud Storage bucket in the EU region to store information for EU users only.
To store user data that needs to be deleted upon user request, you should create a Cloud Storage bucket in the EU region. A bucket is a container for storing objects, and it allows you to store and access data from anywhere in the world. By creating a bucket in the EU region, you can ensure that all data related to EU users is stored in a single location.
To create a Cloud Storage bucket in the EU region, you can use the following steps:
Note that option A is not a suitable solution because federated queries involve querying external data sources such as Cloud Storage, which could lead to performance issues and increased complexity. Option D is also not a suitable solution because it involves re-uploading all data, which is time-consuming and inefficient. Option E is a potential solution, but it would require a mechanism to identify and delete user records upon request.