nerdexam
Google

PROFESSIONAL-DATA-ENGINEER · Question #46

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

The correct answer is 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. Explanation/Reference: BigQuery's views are logical views, not materialized views. Because views are not materialized, the query that defines the view is run each time the view is queried. Queries are billed according to the total amount of data in all table fields referenced dir

Submitted by kim_seoul· Mar 30, 2026Building and operationalizing data processing systems

Question

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?

Options

  • ACreate a view in BigQuery that concatenates the FirstName and LastName field values to produce the FullName.
  • BAdd 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
  • CCreate a Google Cloud Dataflow job that queries BigQuery for the entire Users table, concatenates the FirstName value and LastName value for each user,
  • DUse 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

How the community answered

(24 responses)
  • A
    4% (1)
  • B
    79% (19)
  • C
    13% (3)
  • D
    4% (1)

Explanation

Explanation/Reference: BigQuery's views are logical views, not materialized views. Because views are not materialized, the query that defines the view is run each time the view is queried. Queries are billed according to the total amount of data in all table fields referenced directly or indirectly by the top-level query a view would be very expensive being billed for all the data in the table when you only need one record, for example.

Topics

#BigQuery views#schema modification#cost optimization#SQL

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-DATA-ENGINEER Practice