Courseiva

CCNA Google Cloud products, services, and solutions Questions

24 of 99 questions · Page 2/2 · Google Cloud products, services, and solutions · Answers revealed

Practice these questionsDomain overviewAll questions
76
MCQmedium

A company wants to connect its on-premises data center to Google Cloud with a reliable, lower-latency connection that doesn't traverse the public internet, but doesn't need the bandwidth of a full Dedicated Interconnect. Which Google Cloud connectivity product is most appropriate?

A.Cloud VPN, which creates an encrypted IPsec tunnel over the public internet
B.Partner Interconnect, which provides private connectivity through a service provider partner's network — supporting lower bandwidth tiers without requiring a direct physical fiber connection
C.Dedicated Interconnect, which requires provisioning a 10 Gbps or 100 Gbps dedicated physical fiber connection
D.Cloud CDN, which caches content at edge locations close to the on-premises data center
AnswerB

Partner Interconnect is the right solution. It provides the private connectivity (no public internet) and lower latency characteristics of Dedicated Interconnect, but at lower bandwidth tiers (50 Mbps–50 Gbps) through a service provider partner — appropriate for organizations that don't need or justify a full Dedicated Interconnect circuit.

Why this answer

Partner Interconnect is the correct choice because it provides private connectivity between an on-premises data center and Google Cloud via a service provider partner's network, offering lower bandwidth tiers (e.g., 50 Mbps to 10 Gbps) without requiring a direct physical fiber connection. This meets the requirements for a reliable, lower-latency connection that avoids the public internet, while Dedicated Interconnect would be overkill for bandwidth needs below 10 Gbps.

Exam trap

The trap here is that candidates often confuse Partner Interconnect with Cloud VPN, assuming that any private connection must be encrypted or that VPN is sufficient for low-latency needs, but the key differentiator is that Partner Interconnect avoids the public internet entirely, providing consistent latency and SLA-backed reliability that IPsec VPNs cannot guarantee.

How to eliminate wrong answers

Option A is wrong because Cloud VPN creates an encrypted IPsec tunnel over the public internet, which does not provide a private connection that avoids the public internet and may introduce higher latency and variability. Option C is wrong because Dedicated Interconnect requires provisioning a minimum of 10 Gbps or 100 Gbps dedicated physical fiber connection, which exceeds the stated need for lower bandwidth and does not fit the 'doesn't need the bandwidth of a full Dedicated Interconnect' requirement. Option D is wrong because Cloud CDN is a content delivery network that caches content at edge locations for improved performance of web content, not a connectivity product for linking an on-premises data center to Google Cloud.

Practice this question →
77
MCQeasy

A company wants to store archival data that must be retained for 10 years. The data is accessed less than once a year. Which Cloud Storage class is the most cost-effective?

A.Standard Storage
B.Nearline Storage
C.Coldline Storage
D.Archive Storage
AnswerD

Archive Storage is the correct choice for archival data because it is the cheapest storage class in Google Cloud for data accessed less than once per year. It offers the same global durability and redundancy as other classes, while its very low storage cost makes it ideal for long-term retention, even though it incurs the highest retrieval latency and a 365-day minimum storage duration.

Why this answer

Archive Storage is the most cost-effective option for data that must be retained for 10 years and is accessed less than once a year. This class offers the lowest storage cost among Google Cloud Storage classes, specifically designed for long-term preservation of data that is rarely accessed, with a minimum storage duration of 365 days and higher retrieval costs that are acceptable given the infrequent access pattern.

Exam trap

Google Cloud often tests the misconception that 'Coldline' is the cheapest storage class, but Archive Storage is actually the lowest-cost option for long-term retention with very infrequent access, and candidates may overlook the minimum storage duration and retrieval cost trade-offs.

How to eliminate wrong answers

Option A is wrong because Standard Storage is optimized for frequently accessed data with no minimum storage duration and higher per-GB storage costs, making it cost-prohibitive for 10-year archival retention. Option B is wrong because Nearline Storage is designed for data accessed less than once a month, with a 30-day minimum storage duration and higher storage costs than Archive Storage, making it less cost-effective for data accessed less than once a year. Option C is wrong because Coldline Storage is intended for data accessed less than once a quarter, with a 90-day minimum storage duration and storage costs that are still higher than Archive Storage, so it is not the most cost-effective for 10-year archival with annual access.

Practice this question →
78
Drag & Dropmedium

Drag and drop the steps to deploy a containerized application to Google Kubernetes Engine (GKE) into the correct order.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

The correct sequence starts with containerizing the app, creating a cluster, defining the deployment, applying it, and exposing it as a service.

Practice this question →
79
MCQeasy

A startup's website becomes unexpectedly popular and traffic spikes 50x within minutes. The application is hosted on Google Cloud. Which Google Cloud product automatically increases the number of application instances in response to this traffic spike without manual intervention?

A.Cloud Monitoring, which detects the traffic spike and sends an alert to the operations team to manually scale up
B.Managed Instance Groups with autoscaling (for VMs) or Cloud Run (for containers), which automatically provision additional instances based on traffic load without manual intervention
C.Cloud Load Balancing, which distributes traffic evenly across existing instances to handle the spike
D.Cloud Billing, which automatically increases the spending limit when traffic spikes occur
AnswerB

This is correct. MIG autoscaling monitors CPU/request metrics and automatically adds instances when load increases, then removes them when load drops. Cloud Run scales automatically to any number of container instances in seconds. Both handle the 50x spike scenario automatically.

Why this answer

Managed Instance Groups (MIGs) with autoscaling and Cloud Run both automatically adjust the number of running instances or container replicas based on real-time metrics like CPU utilization, request rate, or latency. When traffic spikes 50x, the autoscaler detects the increased load and provisions new VMs or container instances without any manual intervention, ensuring the application remains responsive. This is the only option that provides automatic, infrastructure-level scaling in response to load.

Exam trap

The GCDL exam often tests the misconception that load balancing alone handles spikes, but candidates must remember that load balancers distribute traffic only to existing instances — autoscaling is required to add capacity.

How to eliminate wrong answers

Option A is wrong because Cloud Monitoring only collects metrics and sends alerts; it does not automatically scale instances — scaling requires a separate service like MIG autoscaler or Cloud Run. Option C is wrong because Cloud Load Balancing distributes traffic across existing instances but does not create new instances; it relies on an autoscaler to add capacity. Option D is wrong because Cloud Billing manages budgets and spending limits, not instance provisioning; it has no mechanism to scale application instances.

Practice this question →
80
MCQeasy

A startup wants to run a containerized web application that scales to zero when not in use, and only pay for the time the container is processing requests. Which Google Cloud compute service should they choose?

A.Google Kubernetes Engine (GKE)
B.App Engine Standard Environment
C.Cloud Run
D.Compute Engine with autoscaling
AnswerC

Cloud Run is a fully managed, serverless compute platform that executes stateless HTTP-driven containers on top of the Knative serving layer. It dynamically scales containers from zero up to a maximum based on incoming requests, so you only pay for CPU, memory, and requests consumed during active processing, making it ideal for intermittent startup workloads. Because it abstracts the underlying machines and cluster, there is no idle infrastructure cost and no node management overhead.

Why this answer

Cloud Run is the correct choice because it is a fully managed serverless compute platform that automatically scales your containerized application to zero when there are no incoming requests. You are billed only for the resources consumed during request processing, measured in 100-millisecond increments, which aligns perfectly with the requirement to pay only for active processing time.

Exam trap

The trap here is that candidates often confuse 'scaling to zero' with 'autoscaling' and choose Compute Engine or GKE, not realizing that those services require at least one running instance or node, whereas Cloud Run is the only option that can truly scale down to zero instances when idle.

How to eliminate wrong answers

Option A is wrong because Google Kubernetes Engine (GKE) requires at least one node to run your containers, even if the application is idle, and does not scale to zero; you pay for the underlying node VMs regardless of usage. Option B is wrong because App Engine Standard Environment does not support arbitrary containerized applications; it runs only in a sandboxed runtime environment with specific language runtimes and does not allow you to bring your own Docker container. Option D is wrong because Compute Engine with autoscaling still requires a minimum number of running VM instances (even if set to 1) and does not scale to zero; you are billed for the provisioned VM instances even when no requests are being processed.

Practice this question →
81
MCQmedium

A data analytics team uses BigQuery for large-scale queries. They notice that queries are scanning more data than necessary, leading to high costs. Which feature should they implement to reduce the amount of data scanned per query?

A.Materialized views
B.Streaming inserts
C.Partitioning
D.Clustering
AnswerC

Partitioning divides a table into separate storage segments based on a specified column, commonly a date or timestamp, and BigQuery performs partition pruning during query execution. When a query's WHERE clause filters on the partition column, the engine avoids scanning partitions that fall outside the filter, directly reducing the bytes processed and thereby lowering query cost. This is a native, deterministic way to limit scan size and is especially effective for large, time-series tables.

Why this answer

Partitioning divides a table into segments based on a column (e.g., date), allowing BigQuery to prune partitions during query execution. When a query includes a filter on the partitioning column, BigQuery scans only the relevant partitions, significantly reducing the bytes processed and lowering costs.

Exam trap

Google Cloud often tests the distinction between partitioning (which reduces data scanned by pruning entire segments) and clustering (which only reorganizes data within partitions for better compression and filtering, but does not reduce the total data scanned unless combined with partitioning).

How to eliminate wrong answers

Option A is wrong because materialized views precompute and cache query results for faster performance, but they do not reduce the amount of raw data scanned per query; they may even increase storage costs. Option B is wrong because streaming inserts are used for real-time data ingestion into BigQuery, not for controlling data scan volume during queries. Option D is wrong because clustering sorts data within partitions based on column values, improving query performance and reducing costs only after partitioning is applied; without partitioning, clustering alone does not limit the total data scanned.

Practice this question →
82
MCQhard

A financial services company needs a managed data warehouse that can ingest streaming transaction data in real time AND support complex SQL analytics across years of historical data — all without managing any infrastructure. Which Google Cloud product meets both streaming ingest and analytical query requirements in a single serverless service?

A.Cloud Bigtable for streaming ingest and BigQuery for historical analytics — two separate services
B.BigQuery, which supports real-time streaming ingest via its Storage Write API and large-scale analytical SQL queries across petabytes of data in a single fully managed, serverless service
C.Cloud SQL with read replicas — one instance for streaming writes, read replicas for analytical queries
D.Cloud Dataflow running continuously to process the stream and load to Persistent Disk for SQL queries
AnswerB

BigQuery meets both requirements natively. The Storage Write API (and legacy streaming API) enables sub-minute data availability for analytics. BigQuery's distributed query engine handles analytical SQL across petabytes. No infrastructure to manage, no separate streaming and analytical systems to maintain.

Why this answer

BigQuery is a fully managed, serverless data warehouse that supports real-time streaming ingest via the Storage Write API and enables complex SQL analytics across petabytes of historical data. This single service meets both requirements without any infrastructure management, unlike the other options that require separate services or manual orchestration.

Exam trap

Google Cloud often tests the misconception that streaming ingest and analytical querying require separate services, leading candidates to overlook BigQuery's unified serverless capability in favor of multi-service architectures like Cloud Bigtable plus BigQuery.

How to eliminate wrong answers

Option A is wrong because it proposes two separate services (Cloud Bigtable for streaming and BigQuery for analytics), which violates the requirement for a single serverless service and introduces operational complexity. Option C is wrong because Cloud SQL is a relational database not designed for petabyte-scale analytics or real-time streaming ingest at high throughput, and read replicas do not provide serverless, managed data warehousing. Option D is wrong because Cloud Dataflow is a stream processing service, not a data warehouse, and Persistent Disk is block storage that cannot natively support SQL analytics without additional compute and query engines.

Practice this question →
83
Multi-Selecthard

A company uses Cloud Spanner for a global application. They need to ensure high availability and disaster recovery across regions. Which TWO actions should they take? (Choose 2)

Select 2 answers
A.Deploy the database in a single region with backups
B.Schedule regular backups using Cloud Spanner backup feature
C.Configure read replicas in a different region
D.Use Cloud Memorystore to cache database queries
E.Use a multi-region instance configuration
AnswersB, E

Scheduling regular backups with the Cloud Spanner backup feature is essential for disaster recovery because it protects against logical corruption, accidental deletion, or application errors that replication cannot mitigate. These backups are consistent and exportable to another instance, enabling point-in-time recovery within the backup's retention window (e.g., up to 35 days). Although backups do not provide immediate failover, they are a fundamental component of a data durability strategy and satisfy the specific ask in this scenario.

Why this answer

Cloud Spanner's built-in backup feature allows you to create consistent backups of your database without impacting performance, and these backups can be restored to a different region for disaster recovery. This provides a reliable way to recover from regional failures or data corruption, ensuring high availability and DR across regions.

Exam trap

Google Cloud often tests the misconception that read replicas or caching services like Memorystore can provide cross-region disaster recovery, but Cloud Spanner's architecture relies on synchronous multi-region replication and backups, not asynchronous replicas or external caches.

Practice this question →
84
MCQmedium

A power utility company collects electricity meter readings from 10 million smart meters every 15 minutes — generating billions of rows of time-series data per year. They need to query this data to detect anomalies and patterns. Which Google Cloud database is optimized for this massive-scale time-series IoT data?

A.Cloud SQL (PostgreSQL)
B.Cloud Bigtable
C.Firestore
D.Cloud Storage (CSV files)
AnswerB

Cloud Bigtable is a fully managed, wide-column NoSQL database purpose-built for massive time-series workloads just like this—10 million meters × 96 readings/day yields ~960 million rows per day, and Bigtable can ingest millions of writes per second. By designing the row key as `meter_id` + `timestamp`, all readings for a meter are stored contiguously, enabling sub-millisecond range scans for anomaly detection. It stores data as unstructured key-value pairs, scales to petabytes seamlessly, and integrates with BigQuery for analytics, making it the clear choice.

Why this answer

Cloud Bigtable is a fully managed, scalable NoSQL database designed for large analytical and operational workloads, making it ideal for ingesting and querying high-throughput time-series data from millions of IoT devices. It supports sub-10ms latency on queries, automatic sharding, and seamless integration with Google Cloud's data analytics ecosystem (e.g., BigQuery, Dataflow), which is critical for detecting anomalies and patterns across billions of rows of meter readings.

Exam trap

The trap here is that candidates confuse 'time-series data' with 'relational data' and choose Cloud SQL (PostgreSQL) for its SQL familiarity, overlooking the need for massive horizontal scalability and high write throughput that only Bigtable provides.

How to eliminate wrong answers

Option A is wrong because Cloud SQL (PostgreSQL) is a relational OLTP database not optimized for the extreme write throughput and horizontal scaling required for billions of time-series rows; it would hit performance bottlenecks and storage limits. Option C is wrong because Firestore is a document-oriented NoSQL database designed for real-time mobile/web apps with moderate write rates, not for massive-scale IoT time-series ingestion and analytical queries. Option D is wrong because Cloud Storage with CSV files lacks native querying capabilities, indexing, and low-latency access needed for real-time anomaly detection; it would require additional services like BigQuery for analysis, adding latency and complexity.

Practice this question →
85
MCQeasy

A data analytics team needs to analyze petabytes of structured data using SQL queries without managing any database infrastructure. Query results must return within seconds for most queries. Which Google Cloud service is designed for this use case?

A.Cloud SQL
B.BigQuery
C.Cloud Bigtable
D.Cloud Spanner
AnswerB

BigQuery is a serverless, petabyte-scale data warehouse that separates storage from compute, enabling independent scaling and on-demand pricing. Its columnar storage and massively parallel query engine, built on Dremel technology, allow fast SQL analytics on massive datasets with zero infrastructure management. This makes it the obvious choice for ad-hoc analysis and business intelligence, not transactional workloads.

Why this answer

BigQuery is a serverless, highly scalable data warehouse designed for analyzing petabytes of data using SQL without any infrastructure management. Its columnar storage and distributed query engine enable sub-second query performance on large datasets, making it ideal for this use case.

Exam trap

The GCDL exam often tests the distinction between OLTP (Cloud SQL, Cloud Spanner) and OLAP (BigQuery) services, and candidates may confuse Bigtable's NoSQL scalability with SQL analytics capabilities.

How to eliminate wrong answers

Option A is wrong because Cloud SQL is a managed relational database for OLTP workloads, not designed for petabyte-scale analytics or sub-second queries on massive datasets. Option C is wrong because Cloud Bigtable is a NoSQL wide-column database optimized for low-latency read/write operations on time-series or IoT data, not for complex SQL analytics on structured data. Option D is wrong because Cloud Spanner is a globally distributed relational database with strong consistency for transactional workloads, not a serverless analytics solution for petabyte-scale SQL queries.

Practice this question →
86
MCQmedium

A company's analytics team wants to enable business users to create their own reports and dashboards from a governed set of BigQuery data, without writing SQL. At the same time, the data engineering team must maintain centralized control over how key metrics (like 'revenue' or 'active users') are defined. Which Google Cloud product architecture best meets both requirements?

A.Looker Studio connected directly to BigQuery, allowing each business user to create their own metric definitions
B.Looker with LookML semantic layer: data engineers centrally govern metric definitions in LookML, business users create self-service reports through Looker's interface using those governed definitions — no SQL required
C.Sharing BigQuery query templates with business users and training them to modify them for their reports
D.Building a custom web application that wraps BigQuery APIs and presents data to business users
AnswerB

Looker's LookML semantic layer is precisely designed for this dual requirement. Engineers write LookML once; it becomes the source of truth for metric definitions. Business users explore and report using a visual interface that always queries through LookML — guaranteed consistency, no SQL needed.

Why this answer

Looker with LookML provides a semantic layer where data engineers centrally define governed metric definitions (e.g., 'revenue' as SUM(price * quantity) with specific filters). Business users can then create self-service reports and dashboards via Looker's drag-and-drop interface without writing SQL, ensuring consistency and control over key metrics.

Exam trap

The trap here is that candidates may think Looker Studio (formerly Data Studio) is sufficient for self-service reporting, but they overlook the critical requirement for a governed semantic layer (LookML) to enforce centralized metric definitions, which Looker Studio alone does not provide.

How to eliminate wrong answers

Option A is wrong because Looker Studio connected directly to BigQuery allows each business user to create their own metric definitions, which violates the requirement for centralized control over how key metrics are defined. Option C is wrong because sharing BigQuery query templates and training users to modify them still requires users to write or edit SQL, and it does not provide a governed semantic layer to enforce consistent metric definitions. Option D is wrong because building a custom web application that wraps BigQuery APIs is a heavy engineering effort that duplicates functionality already provided by Looker's semantic layer, and it does not inherently enforce centralized metric governance without additional custom logic.

Practice this question →
87
MCQhard

A healthcare organization needs to store and analyze large volumes of patient diagnostic imaging data (e.g., DICOM files) in Google Cloud. The data must be stored in a cost-effective manner for long-term retention, with the ability to query metadata and run analytics using SQL-like queries. Which combination of Google Cloud services best meets these requirements?

A.Cloud Storage (Standard) for images, Datastore for metadata
B.Cloud Storage (Archive) for images, Cloud Spanner for metadata
C.Cloud Storage (Nearline) for images, BigQuery for metadata analytics
D.Cloud Filestore for images, Cloud SQL for metadata
AnswerC

Cloud Storage Nearline offers a low storage price for data accessed less than once per quarter, with no minimum retention duration and reasonable retrieval costs, making it ideal for storing long-term medical images that are rarely retrieved but must be retained for compliance. BigQuery is a serverless, columnar data warehouse that supports standard SQL, enabling fast aggregation, JOINs, and full scans of metadata like accession numbers and timestamps without managing infrastructure. Its pay-per-query pricing and separation of storage from compute keep costs aligned with actual analytical usage, making this combination both cost-effective and analytically powerful.

Why this answer

Cloud Storage Nearline provides cost-effective long-term storage for large imaging files with retrieval flexibility, while BigQuery enables SQL-based analytics on metadata extracted from DICOM headers, meeting both retention and query requirements without the cost of standard storage or the complexity of transactional databases.

Exam trap

Google Cloud often tests the misconception that 'cost-effective long-term storage' must use Archive storage, ignoring that Nearline is sufficient for data accessed occasionally (e.g., quarterly analytics) and that BigQuery is the only service listed that provides native SQL analytics on metadata at scale.

How to eliminate wrong answers

Option A is wrong because Cloud Storage Standard is not cost-effective for long-term retention (higher per-GB cost than Nearline/Archive) and Datastore is a NoSQL document database optimized for transactional workloads, not for SQL-like analytics on large metadata sets. Option B is wrong because Cloud Storage Archive has the lowest storage cost but imposes retrieval delays (minutes to hours) unsuitable for frequent analytics, and Cloud Spanner is a globally distributed relational database designed for high-availability transactions, overkill and expensive for metadata querying. Option D is wrong because Cloud Filestore is a network-attached file system for high-performance computing workloads (e.g., NFSv3), not designed for object storage of DICOM files, and Cloud SQL is a relational database for OLTP, not for scalable analytics on large metadata volumes.

Practice this question →
88
MCQeasy

A company wants its internal applications to be accessible via a custom domain name (e.g., `app.company.com`) that routes to their Google Cloud load balancer. Which Google Cloud service manages DNS records for this?

A.Cloud CDN — it manages domain names for cached content.
B.Cloud DNS
C.Cloud Load Balancing — it automatically assigns domain names.
D.Cloud Armor — it routes traffic based on domain names.
AnswerB

Cloud DNS is GCP's authoritative, managed DNS service that lets you create public or private zones and manage records like A, AAAA, and CNAME. To route app.company.com to a GCP load balancer, you add an A record mapping that hostname to the load balancer's static IPv4 address. Because Cloud DNS uses anycast routing, it provides fast, reliable resolution and is the correct service for custom domain name mapping.

Why this answer

Cloud DNS is the correct service because it is Google Cloud's managed DNS service that translates human-readable domain names (like app.company.com) into IP addresses. It allows you to create and manage DNS records (such as A, CNAME, or ALIAS records) that point your custom domain to the IP address or hostname of your Google Cloud load balancer, enabling traffic routing to your internal applications.

Exam trap

The trap here is confusing services that handle traffic (like Cloud Load Balancing or Cloud Armor) with the service that manages DNS records, leading candidates to pick a service that operates at a different layer of the network stack.

How to eliminate wrong answers

Option A is wrong because Cloud CDN is a content delivery network that caches content at edge locations to improve latency; it does not manage DNS records or domain name resolution. Option C is wrong because Cloud Load Balancing distributes traffic across backends but does not automatically assign or manage domain names; you must configure DNS separately to point a custom domain to the load balancer's IP or hostname. Option D is wrong because Cloud Armor is a web application firewall that provides security policies (e.g., IP allowlisting/denylisting, OWASP rules) and can filter traffic based on domain names, but it does not manage DNS records or domain name resolution.

Practice this question →
89
MCQhard

A company runs a mission-critical PostgreSQL database on Google Cloud that must support automatic failover to a standby instance within 60 seconds if the primary instance fails, with minimal data loss. Which Cloud SQL configuration satisfies this high availability requirement?

A.Cloud SQL with automated daily backups, restoring from backup if the primary fails
B.Cloud SQL High Availability configuration with a synchronously replicated standby instance that automatically promotes to primary within approximately 60 seconds of primary failure
C.Cloud SQL read replicas in another region, manually promoted if the primary fails
D.Running a self-managed PostgreSQL cluster on Compute Engine VMs with a custom pacemaker/corosync HA setup
AnswerB

Cloud SQL HA is precisely the right answer. It maintains a standby instance in the same region with synchronous replication, automatically detects primary failure, and promotes the standby without manual intervention. Failover typically completes within 60 seconds, meeting the stated RTO with minimal data loss (synchronous replication means near-zero RPO).

Why this answer

Cloud SQL's High Availability (HA) configuration uses a synchronous replication mechanism between the primary and standby instances. This ensures that transactions are committed on both instances before being acknowledged, meeting the requirement for minimal data loss. In the event of a primary failure, the standby is automatically promoted to primary within approximately 60 seconds, satisfying the failover time requirement.

Exam trap

The trap here is that candidates may confuse read replicas (which are asynchronous and require manual promotion) with HA standby instances (which are synchronous and automatically promoted), or assume that automated backups can meet a strict 60-second RTO/RPO requirement.

How to eliminate wrong answers

Option A is wrong because restoring from automated daily backups cannot achieve a 60-second failover; recovery time would be much longer (minutes to hours) and data loss would include all changes since the last backup. Option C is wrong because Cloud SQL read replicas use asynchronous replication, which can result in significant data loss (seconds to minutes of transactions) and require manual promotion, failing both the automatic failover and minimal data loss requirements. Option D is wrong because while a self-managed Pacemaker/Corosync cluster could theoretically meet the requirements, it is not a Cloud SQL configuration and would require significant operational overhead, violating the premise of using a managed service; the question specifically asks for a Cloud SQL configuration.

Practice this question →
90
MCQmedium

A team needs to process and analyze streaming data in real-time as it arrives from IoT sensors. The pipeline must apply transformations, filter events, and write results to BigQuery. Which Google Cloud service is designed for this stream processing use case?

A.Cloud Dataproc
B.Cloud Dataflow
C.Cloud Composer
D.BigQuery Streaming Insert
AnswerB

Cloud Dataflow is Google Cloud's fully managed implementation of Apache Beam, designed for both real-time stream processing and batch processing with a unified programming model. It ingests events from Pub/Sub, applies user-defined transforms (PTransforms) for enrichment, filtering, and aggregation, and writes results to BigQuery using connectors. Dataflow handles autoscaling, exactly-once processing, and event-time windowing automatically, making it the standard GCP service for building streaming pipelines that transform data before analysis.

Why this answer

Cloud Dataflow is the correct choice because it is a fully managed, serverless service designed specifically for stream and batch data processing. It uses Apache Beam as its programming model, enabling you to apply transformations, filter events, and write results to BigQuery in real-time, exactly matching the described pipeline requirements.

Exam trap

The GCDL exam often tests the distinction between data ingestion (BigQuery Streaming Insert) and data processing (Dataflow), leading candidates to mistakenly choose the streaming insert option because it contains the word 'streaming' and seems directly related to real-time data.

How to eliminate wrong answers

Option A is wrong because Cloud Dataproc is a managed Hadoop/Spark service optimized for batch processing and large-scale data analytics, not for real-time stream processing with built-in support for event-time windows and exactly-once semantics. Option C is wrong because Cloud Composer is a managed workflow orchestration service based on Apache Airflow, designed for scheduling and coordinating batch jobs, not for continuous stream processing. Option D is wrong because BigQuery Streaming Insert is a method for ingesting data into BigQuery in near real-time, but it does not provide the transformation, filtering, or pipeline processing capabilities required; it is a data ingestion endpoint, not a stream processing engine.

Practice this question →
91
Multi-Selecteasy

A company wants to implement a CI/CD pipeline for their Cloud Run services. Which THREE Google Cloud services should they use? (Choose 3)

Select 3 answers
A.Cloud Operations Suite
B.Cloud Build
C.Cloud Deploy
D.Cloud Deployment Manager
E.Container Registry (or Artifact Registry)
AnswersB, C, E

Cloud Build is GCP's fully managed CI/CD platform that executes builds in steps defined in a cloudbuild.yaml file. It can run unit and integration tests, compile source code, and produce container images or other artifacts. As the core CI engine, it is the required service that transforms source commits into testable, deployable artifacts.

Why this answer

Cloud Build (B) is correct because it is Google Cloud's managed CI service that executes build steps defined in cloudbuild.yaml, compiles the container image, and can trigger builds from Cloud Source Repositories, GitHub, or Bitbucket on commit. Container Registry or Artifact Registry (E) is correct because the container image produced by Cloud Build must be stored in a registry; Artifact Registry is the recommended successor to Container Registry for storing and versioning Docker images that Cloud Run will pull. Cloud Deploy (C) is correct because it is the managed CD service that takes the built image and orchestrates progressive delivery to Cloud Run targets (dev/staging/prod) with approval gates and rollout strategies.

Cloud Operations Suite (A) is monitoring, logging, and tracing—useful for observability but not a CI/CD pipeline component. Cloud Deployment Manager (D) is an infrastructure-as-code tool for provisioning Google Cloud resources via YAML/Jinja templates, not for building or delivering application containers.

Exam trap

The trap is that candidates may assume Cloud Build alone is sufficient for CI/CD because it can also deploy directly to Cloud Run, but Cloud Deploy provides separate continuous delivery capabilities with advanced rollout strategies. Additionally, candidates may confuse Cloud Deploy with Cloud Deployment Manager, which is used for provisioning infrastructure, not CI/CD.

Practice this question →
92
MCQeasy

A company needs to store large volumes of unstructured data (images, videos, backups, documents) with high durability and global accessibility. Which Google Cloud service is designed for object storage at any scale?

A.Persistent Disk
B.Cloud Storage
C.Cloud Filestore
D.Cloud Spanner
AnswerB

Cloud Storage is Google's fully managed, globally distributed object storage service designed for unstructured data such as images, videos, backups, and datasets. It stores objects as immutable blobs in buckets, with a flat namespace and HTTP/S APIs, enabling access from anywhere via standard web protocols. It offers 11 nines of annual durability (99.999999999%) through redundant storage across multiple locations, and its scalability and lifecycle management make it ideal for data lakes, content distribution, and archival storage.

Why this answer

Cloud Storage is Google Cloud's fully managed, scalable object storage service designed for unstructured data such as images, videos, backups, and documents. It offers high durability (99.999999999% annual durability) and global accessibility via a unified namespace, making it the correct choice for storing large volumes of unstructured data at any scale.

Exam trap

The GCDL exam often tests the distinction between block, file, and object storage services, leading candidates to confuse Persistent Disk (block) or Cloud Filestore (file) with object storage for unstructured data.

How to eliminate wrong answers

Option A is wrong because Persistent Disk provides block storage for Compute Engine instances, not object storage, and is designed for low-latency access to structured data rather than unstructured data at global scale. Option C is wrong because Cloud Filestore is a managed file storage service (NFS) for shared file systems, optimized for structured workloads like high-performance computing, not for object storage of unstructured data. Option D is wrong because Cloud Spanner is a globally distributed relational database service for transactional and analytical workloads, not an object storage solution for unstructured data.

Practice this question →
93
MCQeasy

A company's DevOps team wants to orchestrate a complex workflow that involves calling multiple Google Cloud APIs in sequence — first running a Cloud Build job, then checking the results, then either deploying to Cloud Run or sending a notification. Which Google Cloud product is designed for orchestrating multi-step workflow logic?

A.Cloud Scheduler, which triggers a series of jobs at specified cron intervals
B.Google Cloud Workflows, which orchestrates multi-step processes by calling APIs in sequence with conditional logic, error handling, and state management
C.Cloud Pub/Sub, by publishing messages between pipeline stages to trigger each subsequent step
D.Cloud Run, by writing the orchestration logic as a container application that calls other services sequentially
AnswerB

Workflows is the purpose-built orchestration service. It defines steps that call Cloud Build API, evaluate results, and conditionally proceed to Cloud Run deployment or notification — exactly the described use case. It handles retries, parallelism, and state automatically.

Why this answer

Google Cloud Workflows is the correct choice because it is a fully managed orchestration platform specifically designed to define multi-step workflows that call Google Cloud APIs and external services in sequence. It supports conditional logic (e.g., if-then-else), error handling (e.g., retries with exponential backoff), and state management, making it ideal for the described scenario of running a Cloud Build job, checking results, and conditionally deploying to Cloud Run or sending a notification.

Exam trap

The trap here is that candidates confuse a simple trigger or messaging service (like Cloud Scheduler or Pub/Sub) with a full orchestration engine, overlooking the need for conditional logic and state management that only Google Cloud Workflows provides.

How to eliminate wrong answers

Option A is wrong because Cloud Scheduler is a cron-based job scheduler that triggers tasks at fixed intervals, not an orchestrator that can handle conditional branching, error handling, or stateful sequencing of API calls. Option C is wrong because Cloud Pub/Sub is a messaging service for asynchronous event-driven communication; while it can trigger subsequent steps, it lacks built-in orchestration features like conditional logic, error handling, and workflow state management, requiring custom code to implement the full workflow. Option D is wrong because Cloud Run is a serverless container runtime; writing orchestration logic as a container application would require manual implementation of sequencing, state management, and error handling, and it does not provide native workflow orchestration capabilities like Google Cloud Workflows does.

Practice this question →
94
MCQhard

A data analytics team needs to run a one-time transformation on 10 TB of data stored in Cloud Storage, then load the results into BigQuery. The transformation is a custom Java application that reads files, processes them, and writes to a new location. Which service should they use to minimize operational overhead?

A.Cloud Dataflow with Apache Beam Java SDK
B.Google Kubernetes Engine (GKE) with a custom container
C.Dataproc Serverless with Spark job
D.Cloud Functions triggered by Cloud Storage events
AnswerA

Cloud Dataflow with Apache Beam is designed for building robust, scalable, and often continuous data processing pipelines, not primarily for executing a standalone, one-time custom Java application directly. While it supports Java and handles large datasets, adapting a custom Java application to the Apache Beam model for a single execution introduces unnecessary development and conceptual overhead. It would be the correct choice if the transformation was a complex, recurring, or streaming job requiring a unified programming model and managed orchestration for high scalability and fault tolerance.

Why this answer

Cloud Dataflow with Apache Beam Java SDK is the appropriate service for running custom Java transformations on large datasets in a fully managed, serverless manner. It reads from Cloud Storage, processes data, and can load results to BigQuery without provisioning clusters. Other options like Cloud Functions have execution limits, GKE requires cluster management, and Dataproc Serverless is intended for Spark jobs, not arbitrary custom Java applications.

Exam trap

The trap is to choose Cloud Functions due to its serverless nature, but it cannot handle 10 TB in a single invocation. Another trap is confusing Dataproc Serverless (which is for Spark jobs) with Dataflow (which is for Beam pipelines in Java).

How to eliminate wrong answers

Option A is wrong because Cloud Dataflow with Apache Beam Java SDK is optimized for stream and batch processing with a unified programming model, but it introduces additional complexity in defining pipelines and managing state, which is unnecessary for a simple one-time transformation; Dataflow also requires more setup for custom Java code compared to Spark on Dataproc Serverless. Option B is wrong because Google Kubernetes Engine (GKE) with a custom container requires manual cluster management, scaling, and orchestration, which increases operational overhead for a one-time job; it is not serverless and demands ongoing maintenance of infrastructure. Option D is wrong because Cloud Functions triggered by Cloud Storage events are designed for lightweight, event-driven processing with limited execution time (9 minutes max) and memory (8 GB max), making them unsuitable for processing 10 TB of data in a single transformation.

Practice this question →
95
Multi-Selecteasy

A company wants to monitor its Google Cloud spending and receive alerts when costs exceed a threshold. Which two services should they use together?

Select 2 answers
A.Cloud Scheduler
B.Cloud Asset Inventory
C.Cloud Logging
D.Cloud Billing Budgets and Alerts
E.Cloud Monitoring
AnswersD, E

Cloud Billing Budgets and Alerts is the native GCP service for defining budget amounts at the billing account or project level and setting threshold rules (e.g., 50%, 90%, 100% of budget). It automatically sends notifications via email and Pub/Sub when thresholds are crossed, enabling proactive cost governance and integration with automation workflows. This is the primary, purpose-built tool for monitoring spending and receiving budget alerts.

Why this answer

Cloud Billing Budgets and Alerts (D) allows you to define a spending threshold and receive notifications when costs approach or exceed that limit. Cloud Monitoring (E) can ingest those budget alert events and trigger additional actions, such as sending notifications via email, SMS, or Pub/Sub, or integrating with incident management tools. Together, they provide a complete cost monitoring and alerting solution.

Exam trap

The trap here is that candidates often confuse Cloud Logging (which stores logs) or Cloud Scheduler (which runs jobs) with the actual billing alerting service, not realizing that Cloud Billing Budgets and Alerts is the dedicated service for cost thresholds and Cloud Monitoring is needed for centralized alert management.

Practice this question →
96
Drag & Dropmedium

Drag and drop the steps to set up a Cloud CDN for a backend bucket in the correct order.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

First create and prepare the bucket, then set up a load balancer, enable CDN, and test.

Practice this question →
97
MCQeasy

A data analyst at a media company needs to run complex SQL queries on petabytes of user engagement data to produce weekly reports. The dataset is stored in Google Cloud. Which Google Cloud product is purpose-built for this type of large-scale analytical SQL workload?

A.Cloud SQL, Google Cloud's managed relational database service
B.BigQuery, Google Cloud's serverless data warehouse for petabyte-scale analytical SQL
C.Cloud Bigtable, Google's NoSQL wide-column database
D.Firestore, Google Cloud's serverless NoSQL document database
AnswerB

BigQuery is precisely designed for this use case. Its serverless architecture, columnar storage format, and distributed query engine make it ideal for analysts running complex SQL against massive datasets. The weekly report workload is a canonical BigQuery use case.

Why this answer

BigQuery is Google Cloud's serverless, highly scalable data warehouse specifically designed for petabyte-scale analytical SQL queries. It separates compute from storage and uses a columnar storage format and a distributed query engine to execute complex SQL on massive datasets without provisioning infrastructure, making it the ideal choice for the described workload.

Exam trap

The GCDL exam often tests the distinction between OLTP databases (Cloud SQL) and OLAP data warehouses (BigQuery), trapping candidates who see 'SQL' and assume any SQL-supporting service works for petabyte-scale analytics, ignoring the fundamental architectural differences in storage, scaling, and query execution.

How to eliminate wrong answers

Option A is wrong because Cloud SQL is a managed relational database service for OLTP workloads (e.g., MySQL, PostgreSQL, SQL Server) and is not designed for petabyte-scale analytical SQL; it has storage and concurrency limits that make it unsuitable for large-scale data warehousing. Option C is wrong because Cloud Bigtable is a NoSQL wide-column database optimized for high-throughput, low-latency read/write operations (e.g., time-series, IoT) and does not support SQL queries or complex analytical joins. Option D is wrong because Firestore is a serverless NoSQL document database for real-time mobile/web applications, not for analytical SQL workloads; it lacks SQL support and is not built for petabyte-scale aggregation or reporting.

Practice this question →
98
MCQmedium

A company is running a latency-sensitive application on Compute Engine instances in a single zone. They want to improve availability without sacrificing low latency. Which strategy should they use?

A.Deploy instances in multiple zones within the same region
B.Use Cloud CDN to cache content
C.Use larger machine types with more vCPUs
D.Deploy instances in multiple regions
AnswerA

Deploying instances across multiple zones within the same region keeps compute close to users and each other, with one-way network latency typically under 1-2 ms, while protecting against entire data center failures. A regional managed instance group can distribute instances across zones and use health checks to automatically replace failed VMs, ensuring the application remains available during a zone outage without forcing cross-geography traffic.

Why this answer

Deploying instances in multiple zones within the same region provides high availability by distributing workloads across physically separate data centers (zones) while keeping network latency low, as intra-region latency is typically under 1-2 ms. This approach protects against zonal failures without the added latency of cross-region communication, which can be 10-100 ms or more.

Exam trap

The trap here is that candidates confuse high availability with geographic distribution, assuming multiple regions are always better, but the question explicitly requires low latency, which multi-region deployments cannot guarantee due to increased network distance.

How to eliminate wrong answers

Option B is wrong because Cloud CDN caches static content at edge locations to reduce latency for content delivery, but it does not improve the availability of a latency-sensitive application's compute instances or handle dynamic request processing. Option C is wrong because using larger machine types with more vCPUs improves performance for compute-bound tasks but does not provide redundancy or fault tolerance; a single zone failure would still take down all instances. Option D is wrong because deploying instances in multiple regions introduces significant cross-region network latency (often 10-100+ ms), which violates the requirement to maintain low latency for the application.

Practice this question →
99
MCQeasy

A company wants to migrate a legacy monolithic application to Google Cloud with minimal code changes. The application runs on a specific OS version and uses a relational database. Which migration approach is most suitable?

A.Rebuild the application using serverless functions
B.Lift and shift to Compute Engine and Cloud SQL
C.Refactor the application into microservices
D.Replatform to use Cloud Run
AnswerB

Rehosting the monolith onto Compute Engine preserves the existing OS version and application code, while Cloud SQL supplies the managed relational database. This satisfies the minimal-code-change constraint, unlike refactoring to containers or serverless, which would demand rewriting.

Why this answer

The correct option is B: Lift and shift to Compute Engine and Cloud SQL. This approach is most suitable because it preserves the existing application with minimal code changes, allowing the same OS version to run on Compute Engine VMs while migrating the relational database to Cloud SQL, a managed relational database service. Options A and C require significant code changes (rebuilding as serverless functions or refactoring into microservices), which contradicts the minimal-change requirement.

Option D, replatforming to Cloud Run, also typically requires containerization and code adjustments and may not support the specific OS version or relational database dependencies as directly.

Practice this question →
← PreviousPage 2 of 2 · 99 questions total

Ready to test yourself?

Try a timed practice session using only Google Cloud products, services, and solutions questions.

Start 20-question session