You are undertaking the migration of an application responsible for tracking library books and their details, such as the author or the year of publication, from an on-premises data warehouse to Google BigQuery. In the current relational database setup, the author information is stored in a separate table and is joined with the book information using a common key. According to Google's best practices for schema design, how should you structure the data to ensure the most efficient queries about the author of each borrowed book?

Exam-Like

Keep the schema the same, maintain the different tables for the book and each of the attributes, and query as you are doing today.

8.3%

Create a table that is wide and includes a column for each attribute, including the author's first name, last name, date of birth, etc.

19.4%

Create a table that includes information about the books and authors, but nest the author fields inside the author column.

61.1%

Keep the schema the same, create a view that joins all of the tables, and always query the view.

11.1%

Google Professional Data Engineer