Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A retail enterprise stores petabytes of historical transaction data in Amazon S3 and Azure Blob Storage while running its primary analytics workloads in Google Cloud. The company wants to analyze the data stored in these external clouds using standard GoogleSQL queries, subject to the following requirements:
How does BigQuery Omni help the enterprise meet these requirements?
The BigQuery Data Transfer Service is a fully managed data movement tool designed to automate the ingestion and replication of data into standard BigQuery tables on a scheduled basis. It connects to a wide variety of external data sources—including software-as-a-service (SaaS) applications and external cloud storage—to streamline data migration and centralize storage within Google Cloud.
Using a transfer service to replicate raw tables into Google Cloud physically moves the data out of its original environment, which violates the enterprise's strict data governance policies. Additionally, copying petabytes of raw data out of Amazon S3 or Azure Blob Storage into Google Cloud triggers substantial outbound data transfer (egress) fees from those external cloud providers. While inbound traffic into Google Cloud might be free, the source cloud provider still bills for the egress bandwidth required to export the raw files.
The organization wanted to permanently migrate raw datasets out of external clouds into native BigQuery storage on a recurring schedule without writing custom ingestion code, and was willing to pay cross-cloud egress fees.
While BigQuery Omni also offers optional cross-cloud transfer tools (such as LOAD DATA or CREATE TABLE AS SELECT statements) when data movement is desired, its core strategic advantage is enabling in-place analytics without requiring raw data migration.
Cross-Cloud Interconnect is a dedicated, high-bandwidth physical networking service that establishes direct connectivity between Google Cloud and other public cloud service providers. Its primary purpose is to provide reliable, high-throughput network transport for organizations that need to exchange large volumes of traffic between multicloud environments over the long term.
Relying on network transport to stream raw datasets into Google Cloud directly violates the requirement to keep raw data in its original cloud storage location for data governance. Furthermore, BigQuery Omni does not operate by streaming raw tables across a physical interconnect into Google Cloud compute regions; instead, it brings the BigQuery compute engine to the external cloud where the data already sits. Finally, moving data out of an external cloud provider over a network connection still constitutes outbound data transfer from the source cloud, rather than avoiding raw data movement altogether.
The scenario asked for a dedicated network connectivity solution to support long-term, high-volume data transfers or workload migrations between Google Cloud and another cloud provider.
A common misconception in multicloud analytics is that analyzing external data always requires high-speed network pipes to pull raw files into a central data warehouse. BigQuery Omni avoids this bottleneck entirely by executing computation locally within the AWS or Azure region.
In traditional cloud architectures, organizations sometimes deploy customer-managed virtual machine clusters (such as self-managed Apache Spark or Hadoop clusters) within their own AWS or Azure subscriptions to preprocess, compress, and export data to external destinations like Cloud Storage. This approach requires engineering teams to manually configure compute instances, manage scaling policies, and maintain software patches.
This option contradicts the core architecture of BigQuery Omni and fails every constraint in the scenario. First, BigQuery Omni is a completely serverless offering; customers never have to provision, configure, or manage compute clusters. Second, the compute clusters that execute BigQuery Omni queries do not run inside the customer's own AWS or Azure accounts—they run in a Google-managed multi-tenant service colocated in the same external cloud region. Finally, exporting raw data to Cloud Storage would violate the requirement to keep data in-place and avoid egress fees.
The organization was building a custom, self-managed ETL pipeline using infrastructure-as-a-service (IaaS) virtual machines in their own external cloud accounts rather than using a serverless, managed analytics engine.
With BigQuery Omni, the customer simply delegates read access to their storage buckets using standard AWS IAM roles or Azure Active Directory principals. Google handles all underlying cluster orchestration invisibly in the background.
BigQuery Omni is a flexible, multicloud analytics solution that extends the serverless architecture of BigQuery to other public cloud providers, specifically Amazon Web Services (AWS) and Microsoft Azure. Because BigQuery fundamentally separates compute from storage, it can decouple its query processing engine from native Google Cloud storage and run that engine directly inside external cloud regions to query data stored in Amazon S3 or Azure Blob Storage via BigLake tables.
SELECT query through the Google Cloud console, the BigQuery control plane sends the job to the BigQuery data plane located in the specified AWS or Azure region. Because the raw table data is read and processed locally within that external region, the organization avoids costly cross-cloud egress fees for moving massive raw datasets.EXPORT DATA statement.
Compared to traditional extract, transform, and load (ETL) pipelines that physically duplicate petabytes of data across clouds, in-place query execution breaks down data silos immediately while minimizing both networking costs and administrative overhead.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated