Your organization has been collecting and analyzing data in Google BigQuery for 6 months. The majority of the data analyzed is placed in a time-partitioned table named events_partitioned. To reduce the cost of queries, your organization created a view called events, which queries only the last 14 days of data. The view is described in legacy SQL. Next month, existing applications will be connecting to BigQuery to read the events data via an ODBC connection. You need to ensure the applications can connect. Which two actions should you take? (Choose two.)
A. Create a new view over events using standard SQL
B. Create a new partitioned table using a standard SQL query
C. Create a new view over events_partitioned using standard SQL
D. Create a service account for the ODBC connection to use for authentication
E. Create a Google Cloud Identity and Access Management (Cloud IAM) role for the ODBC connection and shared "events"
|
Download Printable PDF. VALID exam to help you PASS. |
 |
A standard SQL query cannot reference a view defined using legacy SQL syntax. In order to connect through ODBC connection, we need to use standard SQL. So, we need to create a new view over events_partitioned table using standard SQL which is C. Need service account to connect through ODBC which is option D. Check the links below.
I am not sure about A whether we can create a view over another view which was built using legacy SQL
https://cloud.google.com/bigquery/docs/views
https://cloud.google.com/community/tutorials/bigquery-from-excel
https://www.simba.com/products/BigQuery/doc/ODBC_InstallGuide/mac/content/odbc/bq/configuring/authenticating/serviceaccount.htm
is there a reference in Google documentation that ODBC connection won’t work with legacy SQL?
and….of course A has no sense, create a view of a view…
And D also doesnt look good, you create the role and apply which user? application access–> service account, every time.
It has to be standard because of this:
Google has collaborated with Magnitude Simba to provide ODBC and JDBC drivers that leverage the power of BigQuery’s –>standard SQL.
On what should we build the view, on the events_partitioned, just like the view you had before but in standard SQL.
no sense in creating a new partitioned table as B says.
To let it access the data you should access with a service account.
You can configure the driver to authenticate the connection with a Google service account. When you authenticate your connection this way, the driver handles authentication on behalf of the service account, so that an individual user account is not directly involved and no user input is required.
So I think is C and D.