nerdexam
Google

PROFESSIONAL-DATA-ENGINEER · Question #302

You are migrating your on-premises data warehouse to BigQuery. One of the upstream data sources resides on a MySQL. database that runs in your on-premises data center with no public IP addresses…

The correct answer is B. Use Datastream to replicate data from your on-premises MySQL database to BigQuery. Set up Cloud Interconnect between your on-premises data center and. Option B is correct because Datastream is Google Cloud's native change data capture (CDC) service purpose-built for replicating MySQL data to BigQuery, and Cloud Interconnect establishes a dedicated, private physical link between your on-premises data center and Google Cloud…

Submitted by renata2k· Mar 30, 2026Designing data processing systems

Question

You are migrating your on-premises data warehouse to BigQuery. One of the upstream data sources resides on a MySQL. database that runs in your on-premises data center with no public IP addresses. You want to ensure that the data ingestion into BigQuery is done securely and does not go through the public internet. What should you do?

Options

  • AUpdate your existing on-premises ETL tool to write to BigQuery by using the BigQuery Open Database Connectivity (ODBC) driver. Set up the proxy parameter
  • BUse Datastream to replicate data from your on-premises MySQL database to BigQuery. Set up Cloud Interconnect between your on-premises data center and
  • CUse Datastream to replicate data from your on-premises MySQL database to BigQuery. Use Forward-SSH tunnel as the connectivity method to establish a
  • DUse Datastream to replicate data from your on-premises MySQL database to BigQuery. Gather Datastream public IP addresses of the Google Cloud region

How the community answered

(37 responses)
  • A
    3% (1)
  • B
    76% (28)
  • C
    14% (5)
  • D
    8% (3)

Explanation

Option B is correct because Datastream is Google Cloud's native change data capture (CDC) service purpose-built for replicating MySQL data to BigQuery, and Cloud Interconnect establishes a dedicated, private physical link between your on-premises data center and Google Cloud - meaning data never touches the public internet, satisfying both security requirements.

Option A is wrong because an ODBC driver with a proxy parameter is not a secure, private-network solution - it doesn't prevent traffic from traversing the public internet, and this approach relies on third-party ETL tooling rather than a managed private connection.

Option C is wrong because SSH tunnels, while encrypted, still route traffic over the public internet - encryption is not the same as avoiding the public internet entirely, which is the stated requirement.

Option D is wrong because gathering Datastream's public IP addresses implies the connection will flow over the public internet, which directly violates the constraint.

Memory tip: Match the keyword to the service - "no public internet" → Cloud Interconnect (dedicated private link). Whenever an exam question demands traffic stay off the public internet, Cloud Interconnect (or VPN as a secondary option) is the answer; SSH tunnels and public IPs are automatic disqualifiers.

Topics

#Data migration#BigQuery#Datastream#Cloud Interconnect

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-DATA-ENGINEER Practice