Practice Test 1 | Google Cloud Certified Professional Data Engineer | Dumps | Mock Test
You want to import data into BigQuery. You select a comma-delimiter CSV file to upload and enable “automatically detect” for BigQuery to predict the schema of the table. When you checked the data, you found a skew in data and it’s not properly distributed. You re-checked the file uploaded locally and found no skew in data. What is the reason for this?
A. File’s encoding is not supported by BigQuery. You need to convert the file’s encoding and load it again.
B. File’s encoding is not supported by BigQuery. You need to explicitly specify the encoding when loading data so it can be recognized.
C. Convert the file from CSV to JSON and import data as JSON to ensure there is no skew.
D. You need to explicitly specify the delimiter of the file when loading the data.
Answer: B.
BigQuery supports UTF-8 encoding for both nested or repeated and flat data. BigQuery supports ISO- 8859-1 encoding for flat data only for CSV files.
By default, the BigQuery service expects all source data to be UTF-8 encoded. Optionally, if you have CSV files with data encoded in ISO-8859-1 format, you should explicitly specify the encoding when you import your data so that BigQuery can properly convert your data to UTF-8 during the import process.
Answer A is incorrect: There is no need to manually convert the file to UTF-8. BigQuery can convert it for you.
Answer C is incorrect: There is no limits in data size when loading data to BigQuery.
Answer D is incorrect: While you may explicitly define the delimiter, BigQuery can detect the delimiter.
Source(s):
BigQuery – Loading data: https://cloud.google.com/bigquery/docs/loading-data-cloud-storage-csv
Comments are closed, but trackbacks and pingbacks are open.