Practice Test 3 | Google Cloud Certified Professional Data Engineer | Dumps | Mock Test
You imported a CSV file to BigQuery using API. You checked the data and found that data is skewed and not properly aligned by the table’s columns. What could be the possible issue?
A. You need to explicitly specify the delimiter of the file before loading the data.
B. The file’s encoding is not UTF-8. You need to convert the file’s encoding and load it again.
C. The file’s encoding is not UTF-8. You need to explicitly specify the encoding while loading data.
D. File size may exceed 1GB. You need to break the file into smaller files.
Correct Answer: C
BigQuery supports UTF-8 encoding for both nested (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.
Option A is incorrect: While you may explicitly define the delimiter, BigQuery can detect the delimiter.
Option B is incorrect: There is no need to manually convert the file to UTF-8. BigQuery can convert it for you.
Option D is incorrect: There is no limit in data size while loading data to BigQuery.
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.