Your company is loading comma-separated values (CSV) files into Google BigQuery. The data is fully imported successfully; however, the imported data is not matching byte-to-byte to the source file. What is the most likely cause of this problem?
A. The CSV data loaded in BigQuery is not flagged as CSV.
B. The CSV data has invalid rows that were skipped on import.
C. The CSV data loaded in BigQuery is not using BigQuery’s default encoding.
D. The CSV data has not gone through an ETL phase before loading into BigQuery.
|
Download Printable PDF. VALID exam to help you PASS. |
 |
C
C is 100% correct answer
A has no sense, if we set other format it’ll not import.
D wrong, it doesn’t need any etl phase before ingesting
Is not B
Its C as it says in cloud.google.com/bigquery/docs/loading-data#targetText=By%20default%2C%20the%20BigQuery%20service,8%20during%20the%20import%20process.
If you don’t specify an encoding, or explicitly specify that your data is UTF-8 but then provide a CSV file that is not UTF-8 encoded, BigQuery attempts to convert your CSV file to UTF-8.
Generally, your data is imported successfully, but it may not match byte-for-byte what you expect. To avoid this, specify the correct encoding and try your import again.