Courseiva
Planning and Configuring a Cloud SolutioneasyMultiple ChoiceObjective-mapped

Google ACE Planning and Configuring a Cloud Solution Practice Question

A data analyst needs to run complex analytical queries on a large dataset (10 TB) stored in Cloud Storage. They want to use a serverless query engine that charges based on the amount of data processed. Which Google Cloud service should they use?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

BigQuery

BigQuery is a serverless data warehouse that charges based on queries processed (on-demand) or flat-rate. It can query external data in Cloud Storage via federated queries.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Cloud SQL

    Why it's wrong here

    Cloud SQL is a managed relational database service designed for online transaction processing (OLTP), not for complex analytical queries over large datasets. It scales vertically with limited storage and compute, and running heavy analytical workloads on it would degrade transactional performance and incur high costs. For petabyte-scale analytics with columnar storage and distributed query execution, Cloud SQL lacks the necessary architecture.

  • BigQuery

    Why this is correct

    BigQuery is Google Cloud's serverless, highly scalable data warehouse optimized for analytical queries on massive datasets. It separates storage from compute, uses columnar storage and a distributed query engine, and offers pay-per-query pricing, so you only pay for the data scanned. With features like partitioning, clustering, and BI Engine, it is the ideal choice for complex analytical workloads without managing infrastructure.

  • Bigtable

    Why it's wrong here

    Bigtable is a fully managed, low-latency NoSQL database designed for real-time operational workloads, such as IoT, ad tech, and time-series data. It excels at high-throughput point reads and writes, but its key-value model and lack of full SQL support make it unsuitable for complex analytical queries that require joins, aggregations, and large scans. Analytical use cases are better served by BigQuery, which is built for interactive querying at scale.

  • Dataproc

    Why it's wrong here

    Dataproc is a managed Apache Hadoop and Spark service that allows you to run clusters for batch processing, streaming, and data engineering. However, it is not serverless: you must provision, scale, and manage clusters, and you pay for cluster uptime rather than per query. While Spark can do complex analytics, the operational overhead and lack of fully managed serverless pricing make it a less direct fit for an analyst needing simple, on-demand analytical queries.

Quick reference

Cloud Service Model Comparison

ModelYou ManageProvider ManagesExamples
IaaSOS, runtime, apps, dataHardware, hypervisor, networkingEC2, Azure VMs, GCP Compute Engine
PaaSApps and dataOS, runtime, middleware, hardwareElastic Beanstalk, Azure App Service
SaaSData and settings onlyEverything elseMicrosoft 365, Salesforce, Workday
FaaS / ServerlessFunction code onlyInfra, scaling, runtimeLambda, Azure Functions, Cloud Run
CaaSContainers and appsKubernetes, OS, hardwareEKS, AKS, GKE

About these practice questions

One of 769 original ACE practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This ACE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ACE exam.