Courseiva

Google Cloud Digital Leader (GCDL) — Questions 826–848

848 questions total · 12 pages · All types, answers revealed

Page 11

Page 12 of 12

826
MCQmedium

A startup is building a mobile app and needs to store user profiles and preferences. The data is hierarchical and the app requires real-time synchronization across devices. Which Google Cloud database should they use?

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

Cloud Firestore is a flexible, serverless NoSQL document database designed specifically for mobile and web clients, with real-time synchronization via listen callbacks and automatic offline data persistence. Its hierarchical data model organizes user profiles naturally as documents within collections, and security rules integrate directly with client SDKs. Unlike global SQL options, Firestore provides built-in multi-device sync and conflict handling, making it the ideal fit for a mobile app storing user profiles.

Why this answer

Firestore is a NoSQL document database designed for mobile apps, with real-time sync and offline support. Cloud SQL and Spanner are relational, not ideal for hierarchical data. Bigtable is for time-series/analytics, not mobile app data.

827
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.

828
MCQhard

A company wants to ensure that its Google Cloud resources can only be accessed from within a specific VPC network, preventing data exfiltration to the internet. They need to enforce this for Cloud Storage and BigQuery APIs. Which service should they use?

A.Cloud NAT
B.VPC Service Controls
C.VPC Firewall Rules
D.Private Google Access
AnswerB

VPC Service Controls define security perimeters around Google Cloud resources such as Cloud Storage and BigQuery, using context-aware access conditions (identity, IP, device) to block data exfiltration. It works at the API layer, independent of VPC network boundaries, and is the only option here that actively restricts data movement outside a defined perimeter.

Why this answer

VPC Service Controls create perimeters around managed services to restrict access to only allowed VPC networks.

829
MCQeasy

A company wants to run containerized applications on Google Cloud without managing the underlying VMs or orchestrator. Which compute service should they choose?

A.Cloud Run
B.Google Kubernetes Engine (GKE)
C.Compute Engine
D.App Engine
AnswerA

Cloud Run is the correct choice because it is a fully managed serverless platform that executes stateless containers in a scale-to-zero model, abstracting away all infrastructure such as clusters, nodes, and VMs. You simply deploy a container image and Cloud Run automatically provisions, scales, and load-balances the instances based on incoming HTTP requests or events, billing only for the resources used during request processing. This makes it ideal for containerized workloads where you want zero cluster management and event-driven autoscaling, without the operational overhead of Kubernetes or virtual machines.

Why this answer

Cloud Run is a fully managed serverless container platform that abstracts infrastructure. GKE requires cluster management. Compute Engine is VMs.

App Engine supports containers but with more restrictions.

830
MCQeasy

A startup's engineering team wants to monitor the CPU utilization of its Compute Engine instances and receive an alert when utilization exceeds 80% for 5 minutes. They want a fully managed Google Cloud solution that requires minimal setup and integrates with their existing dashboards. Which Google Cloud service should they use?

A.Cloud Monitoring
B.Cloud Logging
C.Cloud Profiler
D.Cloud Trace
AnswerA

Cloud Monitoring is a fully managed service that collects metrics such as CPU utilization from Compute Engine instances, lets you create dashboards, and supports alerting policies based on thresholds and durations. It integrates natively with Google Cloud and requires minimal setup, making it the ideal solution for this scenario.

Why this answer

Cloud Monitoring is the Google Cloud service for collecting metrics, creating dashboards, and setting up alerts. It automatically collects CPU utilization from Compute Engine instances and allows you to define an alerting policy that triggers when the metric exceeds a threshold for a specified duration. This matches the team's need for a managed, low-effort monitoring solution.

Exam trap

The trap here is confusing Cloud Monitoring with Cloud Logging, but only Cloud Monitoring is designed for numeric metrics and threshold-based alerts.

831
MCQeasy

A regional hospital chain wants to improve patient outcomes by analyzing electronic health records (EHRs) from multiple departments, including radiology, pathology, and pharmacy. Currently, each department stores data in separate on-premises databases, making it difficult to correlate information. The hospital must comply with HIPAA and other data privacy regulations. They have a small IT team and limited budget for new hardware. They want to enable clinicians to run ad-hoc queries across all data and generate insights using machine learning, without managing infrastructure. Which solution best achieves these goals?

A.Purchase additional on-premises servers and implement a data warehouse with ETL processes.
B.Deploy a third-party analytics SaaS tool and export data from each department manually.
C.Migrate all data to Cloud Storage and grant clinicians access to files for manual analysis.
D.Use Cloud Healthcare API to ingest and standardize data from each department, store in BigQuery, and use BigQuery ML to build predictive models.
AnswerD

Using the Cloud Healthcare API to ingest and standardize data from each department addresses silos by converting disparate formats (e.g., FHIR, HL7v2, DICOM) into consistent, interoperable schemas. The standardized data is loaded into BigQuery, a fully managed, HIPAA-eligible serverless data warehouse, allowing analysts to query across the entire hospital chain without managing infrastructure. BigQuery ML enables building and deploying predictive models directly on the warehouse using SQL, avoiding the need for separate ML training environments. This combined solution is scalable, secure, and operationally efficient, making it the optimal choice for advanced analytics.

Why this answer

It leverages the Cloud Healthcare API to ingest and standardize data from disparate on-premises databases into a unified format, stores it in BigQuery for serverless ad-hoc querying, and uses BigQuery ML to build predictive models without managing infrastructure. This fully meets HIPAA compliance through built-in data residency and access controls, while the small IT team avoids hardware procurement and maintenance overhead.

Exam trap

Google Cloud often tests the misconception that on-premises data warehouses (Option A) are the only HIPAA-compliant option, but the trap here is that cloud-native services like Cloud Healthcare API and BigQuery are fully HIPAA-eligible and actually reduce compliance burden through automated controls and managed infrastructure.

How to eliminate wrong answers

Option A is wrong because purchasing additional on-premises servers and implementing a data warehouse with ETL processes requires significant upfront hardware investment and ongoing IT management, contradicting the limited budget and small IT team constraints. Option B is wrong because manually exporting data from each department to a third-party analytics SaaS tool is error-prone, non-scalable, and introduces security risks for PHI under HIPAA, as manual processes lack automated auditing and encryption controls. Option C is wrong because migrating all data to Cloud Storage and granting clinicians access to files for manual analysis does not enable ad-hoc querying or machine learning, and raw file access violates HIPAA's minimum necessary and access control requirements.

832
MCQeasy

What is the primary benefit of using preemptible VMs on Compute Engine?

A.Support for live migration
B.Higher performance than standard VMs
C.Guaranteed availability of resources
D.Cost savings for fault-tolerant workloads
AnswerD

Preemptible VMs cost up to 80% less than standard VMs, making them ideal for fault-tolerant workloads that can survive instance termination, such as batch data processing, rendering, or stateless web serving. This cost benefit is the primary purpose of using them, not performance or availability, and it enables large-scale compute tasks under a constrained budget.

Why this answer

Preemptible VMs on Compute Engine are deeply discounted (up to 60-91% off on-demand) but can be terminated by Google at any time with a 30-second warning, making them ideal for fault-tolerant, stateless, or batch workloads that can tolerate interruption. The primary benefit is therefore cost savings for workloads designed to handle preemption. They are not for guaranteed-availability or high-performance use cases.

Exam trap

The trap is associating 'preemptible' with performance or availability benefits — candidates who don't know the term may pick 'higher performance' or 'guaranteed availability' instead of recognizing it as a cost-optimization feature for interruptible workloads.

How to eliminate wrong answers

Option A is wrong because live migration is a feature of standard (non-preemptible) VMs that allows Google to migrate a running instance during host maintenance without downtime — preemptible VMs are explicitly terminated rather than migrated. Option B is wrong because preemptible VMs use the same underlying hardware as standard VMs and offer no performance advantage; they are simply cheaper and interruptible. Option C is wrong because preemptible VMs offer the opposite of guaranteed availability — Google can reclaim them at any time, and they are automatically terminated after 24 hours.

833
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.

834
MCQmedium

A company wants to run a stateful application that requires persistent, high-performance block storage attached to a single Compute Engine instance. The application needs consistent low latency. Which storage solution should they use?

A.Local SSD
B.Filestore
C.Cloud Storage
D.Persistent Disk
AnswerD

Persistent Disk is a network-attached block storage service that can be attached to a single VM as a raw device, providing durable and high-performance storage. It is independent of the VM lifecycle, so data persists even when the VM is stopped or terminated, and it supports snapshots and regional replication for added durability. This makes it the correct choice for a stateful application that needs reliable block storage while allowing the VM to be restarted or migrated.

Why this answer

Persistent Disk provides durable block storage with consistent performance attached to a single VM. Local SSDs are ephemeral and not suitable for stateful data.

835
Multi-Selecthard

Which TWO of the following are important considerations when designing a cloud solution for data residency compliance? (Choose exactly 2.)

Select 2 answers
A.Enabling Cloud Data Residency policies
B.Selecting a Cloud Storage region to store data within required jurisdiction
C.Choosing the lowest-cost storage class
D.Using a single availability zone for all data
E.Encrypting all data at rest
AnswersA, B

Cloud Data Residency policies in Microsoft Purview let you restrict data-at-rest storage for Microsoft 365 workloads to a chosen geography, directly satisfying the stem's data residency constraint. They govern where tenant data is stored, not merely where it is processed, making them a core design consideration for compliance.

Why this answer

Option A is correct because enabling Cloud Data Residency policies (such as Google Cloud's Assured Workloads or organization policies that enforce location restrictions) directly constrains where resources and data can be created and stored, which is the core mechanism for meeting data residency requirements. Option B is correct because selecting a Cloud Storage region (for example, europe-west1 or us-central1) determines the physical jurisdiction where the data resides, and data residency compliance specifically requires data to remain within an approved geographic boundary. Option C is not a residency consideration because storage class selection (Standard, Nearline, Coldline, Archive) affects cost and access frequency, not the geographic location of the data.

Option D is not a residency consideration because using a single availability zone affects durability and availability, not jurisdictional placement. Option E is not a residency consideration because encryption at rest protects confidentiality but does not control or guarantee where the data is physically stored.

836
MCQhard

A solutions architect is designing a system that must remain available even if an entire Google Cloud region becomes unavailable due to a major disaster. Which deployment approach achieves this goal?

A.Deploying the application across multiple zones within the same Google Cloud region
B.Using a single zone but enabling automatic VM restart policies
C.Deploying the application across multiple Google Cloud regions so that if one region fails, other regions continue serving traffic
D.Enabling Cloud Backup for all VMs in the deployment to allow rapid restoration after a regional failure
AnswerC

Multi-region deployment is required to survive a full regional outage. By running active or active-passive instances in multiple distinct geographic regions, the system continues operating when any single region fails. Each region is geographically and infrastructure-independently isolated.

Why this answer

Deploying across multiple Google Cloud regions ensures that if an entire region becomes unavailable, traffic can be rerouted to healthy regions, achieving disaster recovery across regional failures. This approach leverages Google Cloud's global load balancing (e.g., External HTTPS Load Balancer with backend services in multiple regions) and regional managed instance groups to maintain availability even when a complete region is lost.

Exam trap

Google Cloud often tests the distinction between zonal and regional fault tolerance, and the trap here is that candidates confuse multi-zone deployment (which handles zonal failures) with multi-region deployment (which is required for regional disaster recovery).

How to eliminate wrong answers

Option A is wrong because deploying across multiple zones within the same region protects against zonal failures but does not protect against a regional disaster, as all zones in a region share the same regional control plane and can fail together. Option B is wrong because using a single zone with automatic VM restart policies only recovers from transient failures within that zone, not from a complete regional outage where the zone itself is unavailable. Option D is wrong because enabling Cloud Backup for all VMs allows data restoration after a failure but does not provide automatic failover or continuous availability; the system would still experience downtime while backups are restored, and it does not address the need for immediate traffic redirection during a regional disaster.

837
MCQeasy

A company has set a budget alert at 80% and 100% of $10,000 for a specific project. The project has a billing account linked. What happens when the cost reaches $8,000?

A.The project is automatically suspended.
B.All resources in the project are deleted.
C.The billing account is disabled.
D.A notification is sent to the configured Pub/Sub topic.
AnswerD

A notification is sent to the configured Pub/Sub topic—this is the correct and primary behavior of a budget alert. When spending (or forecasted spending) exceeds a threshold, the Cloud Billing service publishes a message containing details like the budget name, current cost, and threshold value to the topic you selected. This message can then be consumed by Cloud Functions, Cloud Run, or other services to trigger automated responses, but the alert itself only delivers the notification.

Why this answer

Budget alerts in Google Cloud are informational only; when spend crosses a threshold (80% of $10,000 = $8,000), the configured notification channel — typically a Pub/Sub topic, and optionally email to billing admins — receives a message. No automatic enforcement action is taken on the project or billing account. This is by design: budgets are for visibility, not control.

Exam trap

GCDL often tests the misconception that budget alerts enforce spending limits — candidates assume a budget can suspend or delete resources, when in fact it only sends notifications.

How to eliminate wrong answers

Option A is wrong because Google Cloud budgets do not automatically suspend projects; suspension requires an explicit programmatic action (e.g., a Cloud Function triggered by the Pub/Sub message calling the Cloud Billing API). Option B is wrong because budgets never delete resources — deletion is a destructive action that must be explicitly invoked. Option C is wrong because the billing account is not disabled by a budget alert; disabling billing is a manual or programmatic action, and even then it stops billing rather than being triggered by the alert itself.

838
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.

839
MCQhard

A company uses folders to separate environments (dev, test, prod) and teams (eng, data, security). An engineer needs to apply a policy that disables the use of 'g1-small' machine types only in the 'dev' folder under the 'eng' folder. The organization node has no existing constraints. What is the most specific way to apply this policy?

A.Apply the policy at the organization node.
B.Apply the policy at each project individually.
C.Apply the policy at the 'dev' folder.
D.Apply the policy at the 'eng' folder.
AnswerC

The dev folder is the node in the resource hierarchy that contains only development projects and subfolders under eng; applying the policy there inherits to all of those descendants. Because the policy does not flow upward or to sibling folders like test or prod, this is the precise way to scope the restriction to just the dev environment. It leverages the hierarchy to define the policy exactly where the environment boundary is intended.

Why this answer

Organization policies are hierarchical and inherit downward, so applying the constraint at the 'dev' folder scopes it precisely to that folder and its projects without affecting sibling folders or the parent 'eng' folder. This is the most specific node that matches the requirement of restricting only the 'dev' environment.

Exam trap

GCDL often tests whether candidates understand policy inheritance and the 'most specific node' principle, so they over-apply at the org or under-apply at projects instead of using the folder.

How to eliminate wrong answers

Option A is wrong because applying at the organization node would enforce the constraint across all folders and projects, far broader than required. Option B is wrong because applying at each project is more granular than needed and harder to manage, and it doesn't leverage folder inheritance. Option D is wrong because applying at the 'eng' folder would affect all child folders (including test and prod under eng), not just dev.

840
MCQhard

An organization has a compliance requirement to run workloads in specific geographic regions only. They want to prevent any resources from being created outside those regions. Which Google Cloud control should they use?

A.Cloud Audit Logs
B.Organization policy with location restriction
C.VPC Service Controls
D.IAM conditions with resource location
AnswerB

The organization policy constraint `gcp.resourceLocations` is the correct mechanism because it actively enforces geographic compliance at resource creation time. By defining an allowlist of permitted locations at the organization, folder, or project level, Google Cloud blocks any attempt to create a resource outside those regions. This is a centralized, context-aware enforcement that works across supported services, making it the native, authoritative way to guarantee workloads run only in mandated locations.

Why this answer

Organization policies with location restrictions allow administrators to set constraints on where resources can be created. The constraint `gcp.resourceLocations` can be used to restrict allowed regions. IAM roles control who can create resources, but not where.

VPC Service Controls restrict data access, not resource creation location. Cloud Audit Logs only record actions.

841
MCQmedium

An organization's leadership sets a goal to make all future business decisions based on data rather than intuition. They migrate from siloed departmental spreadsheets to a centralized cloud data platform where all teams access the same real-time data. What organizational concept does this represent?

A.Data warehousing — storing historical data for reporting purposes.
B.Data-driven decision making — using objective data analysis rather than intuition to guide business decisions.
C.Business intelligence — creating reports and dashboards.
D.Data governance — policies for who owns and manages data.
AnswerB

Data-driven decision making (DDDM) is the organizational practice of making business choices based on objective data analysis, with executives defining key metrics and empowering teams to act on findings rather than relying on positional authority or gut feel. In a cloud context, DDDM is enabled by unified data platforms, self-service analytics, and real-time pipelines, but the technology alone is insufficient—leadership commitment to trust the data, tolerate failures from experiments, and change decision rights is the actual cultural change. This is the correct answer because the question describes a cultural shift, not a tool.

Why this answer

The scenario describes a shift from intuition-based decisions to decisions grounded in objective data analysis, which is the essence of data-driven decision making. The migration to a centralized cloud data platform ensures all teams access the same real-time data, eliminating silos and enabling consistent, evidence-based choices across the organization.

Exam trap

Google Cloud often tests the distinction between the technology (e.g., data warehousing, BI tools) and the organizational philosophy (data-driven decision making), trapping candidates who focus on the platform migration rather than the behavioral shift it enables.

How to eliminate wrong answers

Option A is wrong because data warehousing focuses on storing historical data for reporting, not on the real-time, decision-making transformation described. Option C is wrong because business intelligence involves creating reports and dashboards from data, but the core concept here is the cultural and operational shift to using data for decisions, not just visualization. Option D is wrong because data governance deals with policies for data ownership and management, which is a supporting framework, not the primary organizational concept of using data to guide decisions.

842
MCQmedium

A company wants to set up automated checks that continuously verify their website's homepage, login page, and API endpoints are accessible from multiple global locations. If any endpoint becomes unreachable for more than 2 minutes, the on-call engineer should be alerted. Which Cloud Monitoring feature provides this?

A.Cloud Logging log-based alerts that detect 5xx errors in application logs.
B.Cloud Monitoring uptime checks that probe endpoints from global locations with alerting on failure.
C.Cloud Trace that records response times for each user request.
D.Custom scripts on Compute Engine VMs that ping endpoints every minute.
AnswerB

Cloud Monitoring uptime checks are a managed, synthetic monitoring solution that sends HTTP, HTTPS, or TCP probe requests to your endpoints from multiple global points of presence (PoPs) at configurable intervals. Alerting policies can be triggered when a configurable number of locations report failure, which verifies external availability from the user's perspective, not just internal health. This is the correct choice because it is a deliberately designed, low-maintenance service for exactly this use case, requiring no custom infrastructure and providing global coverage by default.

Why this answer

Cloud Monitoring uptime checks are specifically designed to probe HTTP, HTTPS, or TCP endpoints from multiple global locations at configurable intervals (e.g., every 1 minute). They can trigger alerting policies when a check fails for a specified duration (e.g., 2 minutes), directly matching the requirement for continuous, multi-location endpoint accessibility verification with alerting on sustained failure.

Exam trap

The trap here is that candidates confuse log-based alerts (which detect errors in logs) with proactive uptime checks (which test connectivity), leading them to choose Option A because they think 5xx errors are the only way to detect unreachability, ignoring that a completely down endpoint may not generate logs at all.

How to eliminate wrong answers

Option A is wrong because Cloud Logging log-based alerts analyze log entries (e.g., 5xx errors) but do not actively probe endpoints from global locations; they react to logs already generated, not to connectivity failures that may not produce logs. Option C is wrong because Cloud Trace is a distributed tracing tool that captures latency and request paths for individual user requests, not a monitoring feature for endpoint availability from multiple locations. Option D is wrong because custom scripts on Compute Engine VMs would require manual setup, lack native multi-location probing, and do not integrate with Cloud Monitoring's alerting policies; they are an ad-hoc solution, not a managed service.

843
MCQeasy

Which Google Cloud service helps identify and classify sensitive data such as credit card numbers or personal health information in Cloud Storage and BigQuery?

A.Security Command Center
B.Data Loss Prevention (DLP) API
C.Cloud Data Catalog
D.Access Transparency
AnswerB

The Data Loss Prevention (DLP) API is specifically designed to inspect, classify, and protect sensitive data by scanning content for predefined infoTypes (e.g., names, credit card numbers, national ID numbers) and custom patterns. It can analyze text, structured data, and even images via OCR, then classify findings and optionally apply de-identification transformations like redaction or tokenization. This makes it the correct service for identifying and classifying sensitive data.

Why this answer

The Data Loss Prevention (DLP) API is specifically designed to discover, classify, and protect sensitive data such as credit card numbers, personal health information, and other PII. It can scan Cloud Storage buckets and BigQuery tables, using built-in infoType detectors to identify and classify sensitive content. This makes it the correct service for the described requirement.

Exam trap

The trap is confusing Data Catalog (metadata) with DLP (content classification); candidates often pick Data Catalog because it sounds like it catalogs data, but it does not inspect content for sensitivity.

How to eliminate wrong answers

Option A is wrong because Security Command Center is a security posture and threat management service; it does not classify sensitive data in storage or BigQuery. Option C is wrong because Cloud Data Catalog is a metadata management service that helps discover and tag data assets, but it does not perform sensitive data classification or DLP scanning. Option D is wrong because Access Transparency provides logs of Google personnel access to your data, not data classification.

844
Multi-Selectmedium

A media company needs to store and serve video files globally with high availability and low latency. They also need to process these videos using transcoding. Which THREE Google Cloud services should they use? (Choose 3)

Select 3 answers
A.Cloud Storage
B.Compute Engine
C.Transcoder API
D.Cloud CDN
E.BigQuery
AnswersA, C, D

Cloud Storage is the correct choice because it is a managed object storage service that provides highly durable and available storage for video files. With regional and multi-regional locations, it allows media to be stored globally and served directly via HTTP/HTTPS, with options like Google Cloud CDN for edge caching. It is purpose-built for holding large binary media assets like videos, unlike compute or analytics services.

Why this answer

Cloud Storage [CORRECT] is the right choice for storing the video files because it provides a highly durable, globally accessible object store with multi-regional and dual-region bucket options that support high availability for media assets. Cloud CDN [CORRECT] is correct because it caches content at Google's global edge points of presence, reducing latency when serving video files to users worldwide. Transcoder API [CORRECT] is correct because it is the managed service specifically designed to transcode video files into different formats and resolutions for playback on various devices.

Compute Engine is not the best fit here because managing your own VMs for storage and transcoding adds operational overhead compared to the managed Cloud Storage and Transcoder API services. BigQuery is an analytics data warehouse and does not store or serve video files or perform transcoding, so it does not belong in this solution.

Exam trap

The trap is picking Compute Engine for transcoding because it sounds flexible; the exam expects you to recognize the Transcoder API as the purpose-built managed service and to avoid analytics services like BigQuery for media storage or delivery.

845
MCQeasy

What is a key business benefit of moving from a capital expenditure (CapEx) model for IT infrastructure to an operational expenditure (OpEx) model like pay-as-you-go cloud computing?

A.Improved cash flow by avoiding large upfront hardware purchases
B.Elimination of all IT staff
C.Reduced need for software licenses
D.Guaranteed performance improvement
AnswerA

Moving to cloud converts large, one-time capital expenditures for on-premises hardware into predictable operational expenditures. By avoiding significant upfront purchases of servers and storage arrays, organizations preserve cash for strategic investments and benefit from a pay-as-you-go model that spreads costs over the subscription period. This directly improves short-term cash flow, as monthly fees are generally lower than the initial capital outlay and can be matched to actual usage.

Why this answer

The key business benefit of moving from CapEx to OpEx is improved cash flow because the organization avoids large upfront hardware purchases and instead pays only for what it consumes. This shifts spending from a capital budget to an operating budget, making costs variable and predictable. Eliminating IT staff, reducing software licenses, and guaranteeing performance are not inherent outcomes of the OpEx model.

Exam trap

GCDL often tests the misconception that OpEx eliminates IT staff or software licenses, when the actual benefit is cash flow and shifting from capital to operating budget.

How to eliminate wrong answers

Option B is wrong because moving to OpEx does not eliminate the need for IT staff; organizations still require engineers to manage cloud resources, security, and architecture. Option C is wrong because cloud computing does not inherently reduce software license requirements; many cloud services still require licenses (e.g., Windows Server, SQL Server), and some SaaS models shift but do not eliminate licensing. Option D is wrong because OpEx does not guarantee performance improvement; performance depends on architecture, sizing, and configuration, not on the billing model.

846
MCQmedium

An e-commerce company plans its infrastructure for peak shopping events (e.g., Black Friday) which drive 50× normal traffic. On-premises, they must maintain 50× capacity year-round. In the cloud, they provision 50× capacity only during peak periods. Which cloud characteristic enables this cost optimization?

A.Measured service — metering and reporting resource consumption.
B.Elasticity — the ability to rapidly scale resources up during peak demand and release them when no longer needed.
C.Broad network access — accessing resources from any internet-connected device.
D.Resource pooling — the provider's resources are shared among many customers.
AnswerB

Elasticity is the ability to rapidly and automatically provision or release cloud resources in response to changing workload demand. In this case, the company scales to 50x capacity for the Black Friday peak, runs for that period, then scales back to the normal 1x baseline, so it only pays for the extra capacity when it is actually used. This avoids the cost of permanently over-provisioning a data center for a short-lived surge, which is exactly the cost optimization described.

Why this answer

Elasticity is the cloud characteristic that allows resources to be automatically provisioned to handle 50× peak traffic and then de-provisioned when demand subsides, eliminating the need to maintain idle capacity year-round. This contrasts with on-premises infrastructure, where capacity must be statically over-provisioned to handle peak loads, leading to significant cost inefficiency. The ability to scale out and scale in dynamically based on real-time demand is the core enabler of the described cost optimization.

Exam trap

The GCDL exam often tests the distinction between elasticity (dynamic scaling of resources for a single customer) and resource pooling (sharing of resources among multiple customers), leading candidates to confuse the multi-tenant efficiency of pooling with the on-demand scaling characteristic of elasticity.

How to eliminate wrong answers

Option A is wrong because measured service refers to metering and reporting resource consumption for billing and usage tracking, not the ability to dynamically adjust capacity to match demand. Option C is wrong because broad network access describes the capability to access resources from any internet-connected device via standard protocols (e.g., HTTPS, SSH), which is unrelated to scaling infrastructure for peak events. Option D is wrong because resource pooling involves the provider sharing its physical and virtual resources among multiple customers via a multi-tenant model, which improves provider efficiency but does not directly enable a single customer to scale their own resource allocation up and down on demand.

847
MCQeasy

A startup is building a mobile app and needs a real-time database that synchronises data across user devices automatically. The data model is document-based, and the app needs offline support. Which database should they use?

A.Cloud Bigtable
B.Cloud SQL
C.Firestore
D.Memorystore
AnswerC

Firestore is a NoSQL document database with real-time synchronization built into its mobile SDKs, automatically pushing data changes to connected clients and persisting a local cache for offline operation. It resolves conflicts and syncs local writes when connectivity returns, enabling responsive, collaborative mobile experiences. Its flexible, schema-less document model maps naturally to app objects, making it the standard choice for real-time mobile apps.

Why this answer

Firestore is Google Cloud's serverless, document-oriented NoSQL database that provides real-time synchronization across devices via listeners, plus built-in offline persistence for mobile and web SDKs. Its document/collection data model and automatic multi-device sync directly match the startup's requirements.

Exam trap

GCDL often tests the difference between Firestore (document, real-time, offline) and Bigtable (wide-column, analytical) — candidates pick Bigtable for 'NoSQL' without checking the real-time sync and offline requirements.

How to eliminate wrong answers

Option A is wrong because Cloud Bigtable is a wide-column, HBase-compatible NoSQL store optimized for massive analytical and time-series workloads (millions of rows, low-latency reads at scale) — it has no real-time sync or offline mobile SDK. Option B is wrong because Cloud SQL is a managed relational database (MySQL, PostgreSQL, SQL Server) with a fixed schema, not a document model, and it lacks native real-time device synchronization. Option D is wrong because Memorystore is a managed Redis/Memcached in-memory cache, not a persistent document database with offline support.

848
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.

Page 11

Page 12 of 12