You work for a large fast food restaurant chain with over 400,000 employees. You store employee information in Google BigQuery in a Users table consisting of a FirstName field and a LastName field. A member of IT is building an application and asks you to modify the schema and data in BigQuery so the application can query a FullName field consisting of the value of the FirstName field concatenated with a space, followed by the value of the LastName field for each employee. How can you make that data available while minimizing cost?
A. Create a view in BigQuery that concatenates the FirstName and LastName field values to produce the FullName.
B. Add a new column called FullName to the Users table. Run an UPDATE statement that updates the FullName column for each user with the concatenation of the FirstName and LastName values.
C. Create a Google Cloud Dataflow job that queries BigQuery for the entire Users table, concatenates the FirstName value and LastName value for each user, and loads the proper values for FirstName, LastName, and FullName into a new table in BigQuery.
D. Use BigQuery to export the data for the table to a CSV file. Create a Google Cloud Dataproc job to process the CSV file and output a new CSV file containing the proper values for FirstName, LastName and FullName. Run a BigQuery load job to load the new CSV file into BigQuery.
|
Download Printable PDF. VALID exam to help you PASS. |
 |
As per my understanding,
A: is not correct, as views will internally execute the query on the table itself , every query to view will process all roaws of table and provide fullname column.( this is not cost effective solution)
B: is not correct, as Update DML statement as limit or quota , an we have 400,000 rows
C: seems correct to me , as its a one time activity and wont take much cost .
D: is not at all and option, its way lengthy and. costly process.
It’s (B). Good point with the materialized view, but 400k rows is nothing 😉
Agree should be A
c and d make no sense, between A and B…well, with A you dont use any aditional space in the storage.
I dont know if the new column has any advantage….I guess not, since we’d have to update the column every time we added a new name.
A is my choince