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 runs its e-commerce application in an on-premises data center. To handle massive traffic surges during seasonal sales, the company purchased enough physical servers to meet peak demand. This traditional setup has resulted in several challenges:
How does migrating to a cloud environment resolve these resource provisioning challenges?
Google Cloud service quotas are per-project, regional, or global limits that define the maximum amount of a specific cloud resource that an organization can provision or consume. They include resource quotas (such as the maximum number of Compute Engine VMs, Cloud Storage buckets, or GKE nodes) and rate quotas (which limit the number of API requests sent to a service within a given timeframe).
The scenario asked how an organization could implement financial governance guardrails in a development or testing environment to restrict developers from accidentally provisioning excessive Compute Engine VMs and exceeding their department budget.
In Google Cloud, a capacity reservation is a feature used with Compute Engine to guarantee that a specific number of virtual machines (VMs) of a chosen machine type are always available in a designated zone. Reservations can be scoped to a single project or shared across multiple projects to ensure that critical workloads can always acquire compute resources when needed.
The scenario asked how an organization could guarantee that a fixed number of Compute Engine VMs are always available in a specific zone to satisfy strict disaster recovery (DR) or continuous high-availability compliance mandates.
While reservations are valuable for assuring baseline capacity or preparing just ahead of a known, massive event, relying on permanent maximum reservations year-round ignores the core cloud benefits of elasticity and autoscaling.
Vertical scaling (scaling up or down) involves replacing or resizing an existing compute component with one that has more or less capacity, such as increasing the CPU cores, memory, or storage of a single virtual machine. Horizontal scaling (scaling out or in) involves adding or removing replica nodes—such as adding more VM instances in a Compute Engine managed instance group (MIG) or more Pods in Google Kubernetes Engine (GKE)—to distribute the workload across multiple machines.
The organization was migrating a legacy, single-node monolithic database that cannot be distributed across multiple servers, and administrators needed to manually resize the VM's machine type during a scheduled maintenance window prior to a seasonal sale.
Elasticity is the fundamental cloud capability that allows a system to dynamically adjust its computing resources based on changing workload requirements. Autoscaling is the automated mechanism that executes this principle by monitoring performance metrics—such as CPU utilization, memory usage, or incoming network traffic—and automatically provisioning or deprovisioning resources like Compute Engine virtual machines (VMs) or Cloud Run container instances.
Compared to traditional on-premises infrastructure—which forces organizations to choose between costly over-provisioning or risky under-provisioning—cloud elasticity combined with autoscaling provides an automated, pay-as-you-go model that seamlessly matches capacity to current demand.

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