Topic 1 Question 48
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?
The CSV data loaded in BigQuery is not flagged as CSV.
The CSV data has invalid rows that were skipped on import.
The CSV data loaded in BigQuery is not using BigQuery's default encoding.
The CSV data has not gone through an ETL phase before loading into BigQuery.
ユーザの投票
コメント(11)
Answer: C Description: Bigquery understands UTF-8 encoding anything other than that will result in data issues with schema
👍 25[Removed]2020/03/27Answer : C : " If you don't specify an encoding, or if you specify UTF-8 encoding when the CSV file is not UTF-8 encoded, BigQuery attempts to convert the data to UTF-8. Generally, your data will be loaded successfully, but it may not match byte-for-byte what you expect." https://cloud.google.com/bigquery/docs/loading-data-cloud-storage-csv#details_of_loading_csv_data
👍 14YAS0072021/08/20Answer: C
👍 10[Removed]2020/03/20
シャッフルモード