Practice Test 2 | Google Cloud Certified Professional Cloud Architect | Dumps | Mock Test
A financial company has recently moved from on-premise to Google Cloud Platform, they have started to use Bigquery for data analysis, while the performance of Bigquery has been good, but they are concerned about controlling the cost for Bigquery usage. Select the relevant Bigquery best practices for controlling costs from the options given below. (Select 3)
A. Avoid SELECT * Query only the columns that you need.
B. Use the –dry_run flag in the CLI Before running queries, preview them to estimate costs
C. Use a LIMIT clause as a method of cost control
D. If possible, partition your BigQuery tables by date
E. Always keep large result sets in BigQuery storage
Options A, B, D are the right choices.
Using SELECT * is the most expensive way to query data. When you use SELECT *, BigQuery does a full scan of every column in the table. Queries are billed according to the number of bytes read. To estimate costs before running a query you could use The –dry_run flag in the CLI. If possible, partition your BigQuery tables by date. Partitioning your tables allows you to query relevant subsets of data which improves performance and reduces costs.
Option C is an incorrect choice because applying a LIMIT clause to a query does not affect the amount of data that is read. It merely limits the results set to output. You are billed for reading all bytes in the entire table as indicated by the query.
Option E is an incorrect choice because, Keeping large result sets in BigQuery storage has a cost. If you don’t need permanent access to the results, use the default table expiration to automatically delete the data for you.
Reference(s) :
Comments are closed, but trackbacks and pingbacks are open.