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.
An enterprise is planning to migrate workloads from its aging on-premises facilities to Google Cloud to reduce operational costs and meet corporate sustainability goals. The executive team wants to understand how Google's physical infrastructure inherently optimizes energy consumption, cooling, and resource utilization compared to traditional data centers.
How do Google's purpose-built data centers and custom servers achieve these operational and environmental benefits?
Cross-region and multi-region replication is an architectural strategy that copies data and deploys redundant application instances across geographically separate data centers. Its primary purpose is to provide high availability (HA) and disaster recovery (DR) so that critical business services remain operational if an entire regional facility experiences an outage.
Automatically replicating all workloads and data across multiple global regions does not optimize energy consumption; instead, it significantly increases energy usage, operational costs, and carbon emissions. Every gigabyte of stored data requires physical storage media that must be continuously powered, cooled, and managed. Furthermore, transferring massive volumes of data across wide-area networks between regions consumes substantial network bandwidth and electrical power at both the source and destination facilities.
The scenario asked how an organization could architect a mission-critical application to survive a complete regional outage and meet strict high-availability (HA) or disaster recovery (DR) compliance mandates, regardless of the extra cost and energy overhead.
To align with sustainability best practices, organizations should minimize replication and only duplicate resources across regions when strictly required for availability. Instead of indiscriminate global replication, teams can use geographical shifting to place workloads in a single region with a high percentage of Carbon-Free Energy (CFE).
In Google Cloud, environmental efficiency and operational management are governed by the shared responsibility and shared fate model. This framework clearly divides operational duties between the cloud provider (sustainability of the cloud) and the customer (sustainability in the cloud), ensuring each party manages the layers of the technology stack they directly control.
Google does not transfer the management of physical data center cooling, power distribution, or server hardware engineering to customers. Instead, Google retains full responsibility for the sustainability of Google Cloud. Customers do not have physical access to data centers or direct operational control over facility cooling systems, electrical grids, or custom chip manufacturing. Cloud billing and FinOps tools allow customers to monitor financial spend and carbon footprints, but they do not shift physical facility engineering duties to the user.
The scenario described a traditional on-premises data center where the enterprise itself is responsible for procuring server hardware, managing physical rack power distribution, and operating facility cooling systems.
By offloading the physical infrastructure layer to Google Cloud, organizations immediately benefit from Google's continuous investments in high-PUE facilities and custom silicon, allowing internal engineering teams to focus entirely on application-level efficiency and cost optimization.
An active-passive architecture is a traditional failover configuration where primary compute servers (active nodes) handle all live production traffic while a duplicate set of secondary servers (passive nodes) sit on standby. In a warm standby setup, these passive servers remain powered on and running idle so they can take over if the primary system fails.
Keeping duplicate physical servers powered on in a warm, idle state is a primary driver of energy waste and directly contradicts how Google Cloud optimizes resource utilization and cost-effectiveness. Idle or underutilized infrastructure continuously draws electrical power and generates heat—requiring additional data center cooling—without performing any productive work. Rather than relying on idle standby hardware, efficient cloud infrastructure maximizes utilization through dynamic scaling, bin packing, and active-active designs.
The question asked to identify an inefficient legacy disaster recovery pattern that organizations should replace with active-active architectures, cold DR, or serverless scale-to-zero failover to eliminate energy waste.
To balance reliability with high resource utilization, modern cloud architectures prefer active-active deployments where all provisioned nodes actively serve traffic, or serverless services like Cloud Run that scale down to zero instances and consume no energy until failover traffic actually arrives.
Google designs, builds, and operates its own vertically integrated data centers and custom server hardware, including specialized processors like Tensor Processing Units (TPUs) and modern virtual machine families. Rather than relying on generic commercial facilities and off-the-shelf components, every layer of the physical infrastructure is engineered specifically for cloud-scale efficiency, security, and performance.
Traditional on-premises data centers lack the operational scale required to justify bespoke cooling systems and custom silicon design. Leveraging Google's purpose-built facilities and custom hardware immediately provides organizations with a foundation that is sustainable by design, optimizing both environmental footprint and price-performance without requiring manual hardware engineering by the customer.
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