You are migrating an application that tracks library books and information about each book, such...

Question

You are migrating an application that tracks library books and information about each book, such as author or year published, from an on-premises data warehouse to BigQuery In your current relational database, the author information is kept in a separate table and joined to the book information on a common key Based on Google's recommended practice for schema design, how would you structure the data to ensure optimal speed of queries about the author of each book that has been borrowed?

Accepted Answer

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

Answer

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

Answer

B. 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

Answer

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

Summer Sale Limited Time 65% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: pass65

Exam Professional-Data-Engineer All Questions

Google Cloud Certified Professional-Data-Engineer Question # 60 Topic 7 Discussion

Correct Answer:

Options Selected by Other Users:

Contribute your Thoughts: