Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A retail organization is modernizing its application infrastructure on Google Cloud to reduce its environmental footprint. The engineering team needs to optimize two primary workloads:
Which cloud-native strategy should the organization implement to minimize energy waste and reduce carbon emissions?
Cloud Run is a fully managed, serverless compute platform that automatically scales containerized applications up and down based on incoming traffic, including scaling all the way down to zero active instances when there is no demand. Carbon-aware scheduling is an intelligent workload management practice that uses real-time and historical grid energy data—such as regional carbon-free energy metrics available in BigQuery public datasets—to shift compute tasks to times and locations with the cleanest electricity mix.
Combining serverless scale-to-zero capabilities with data-driven temporal and geographical shifting directly addresses both idle resource waste and grid carbon intensity. Unlike static virtual machine deployments that draw power continuously regardless of utilization, this cloud-native approach ensures that every watt of electricity is used productively and sourced as cleanly as possible.
An active-passive disaster recovery (DR) architecture is a traditional high-availability approach where a primary environment actively serves user traffic while a secondary, duplicate set of pre-provisioned infrastructure (such as Compute Engine virtual machines) runs on standby in another region, waiting to take over only if a failover event occurs.
The scenario required a traditional, near-zero Recovery Time Objective (RTO) for a legacy stateful application that cannot support active-active load distribution, serverless failover, or automated Infrastructure as Code (IaC) provisioning, and where minimizing environmental impact was not a primary constraint.
To architect energy-efficient disaster recovery in the cloud, organizations should prefer active-active architectures where all provisioned resources across regions actively serve traffic, or cold DR strategies using serverless services like Cloud Run or Terraform to provision recovery environments only when an actual outage occurs.
Vertical scaling (scaling up) is the process of increasing the compute capacity—such as adding more vCPUs or memory—of an existing, single virtual machine instance so it can handle larger workloads, rather than adding or removing multiple smaller instances dynamically (horizontal scaling).
The organization needed to increase capacity for a monolithic, stateful legacy database or single-threaded application that cannot be decoupled or distributed across multiple horizontal instances.
For cloud-native sustainability, horizontal scaling combined with stateless application design (such as storing session state in Memorystore for Redis) is the recommended approach. Features like Horizontal Pod Autoscaling (HPA) in GKE or automatic instance scaling in Cloud Run ensure that infrastructure expands only during demand spikes and contracts immediately afterward.
Standard CPU-only virtual machines use general-purpose processors designed to handle a wide variety of sequential computing tasks. In contrast, specialized hardware accelerators—such as Google Cloud TPUs (Tensor Processing Units) and GPUs (Graphics Processing Units)—are purpose-built to execute massive parallel computations for data processing, machine learning, and high-performance batch workloads.
The organization was running lightweight, simple sequential workloads that cannot be parallelized and would leave specialized TPU or GPU cores sitting idle and underutilized.
A core principle of sustainable cloud architecture is performance optimization. Upgrading to modern machine families (such as C4A Axion-based instances) or using purpose-built accelerators like TPUs increases performance per watt, allowing workloads to complete faster and release compute resources sooner.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated