Courseiva
hardMultiple Select

Cloud Digital Leader Practice Question: Which THREE of the following are common benefits…

Which THREE of the following are common benefits of adopting a cloud infrastructure compared to on-premises? (Choose 3)

⚠ Common exam trap

Google Cloud often tests the shared responsibility model by presenting options that imply a complete transfer of security liability, leading candidates to mistakenly select Option D, when in fact the customer retains critical security duties.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Ability to scale globally in minutes

Option A is correct because cloud providers operate redundant infrastructure across multiple geographic regions and Availability Zones, so resources can be provisioned and distributed worldwide within minutes rather than waiting weeks for physical hardware delivery and datacenter build-out. Option C is correct because the pay-as-you-go model bills based on actual consumption of compute, storage, and network resources, converting fixed costs into variable operational expenses. Option E is correct because adopting cloud eliminates the large upfront capital expenditure (CapEx) required to purchase servers, storage arrays, and networking gear, replacing it with operating expenditure (OpEx). Option B is incorrect because no environment, cloud or on-premises, can eliminate all security vulnerabilities; the shared responsibility model still leaves customer-side risks such as misconfiguration and application flaws. Option D is incorrect because security responsibility is shared, not fully transferred — the provider secures the cloud (physical facilities, hypervisor, managed services), while the customer remains responsible for security in the cloud (data, identities, configurations, patching of IaaS workloads).

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    Ability to scale globally in minutes

    Why this is correct

    Hyperscale cloud providers operate dozens (or hundreds) of geographic regions and edge locations, with APIs and console workflows that provision compute, storage, and load-balancing resources in minutes. Auto-scaling policies and global anycast networking let workloads expand horizontally across regions as demand spikes, whereas building or buying on-premises capacity would require procurement cycles measured in weeks or months. This rapid, worldwide, elastic capacity is a foundational cloud benefit.

  • ✗

    Elimination of all security vulnerabilities

    Why it's wrong here

    No environment—cloud, on-premises, or hybrid—can claim to eliminate all security vulnerabilities. Zero-day exploits are discovered continuously, patches take time to apply, and customer-controlled configuration choices (IAM policies, network rules, encryption settings, application code) frequently introduce their own exploitable weaknesses. Hyperscalers invest heavily in platform security, but the evolving threat landscape and the reality of software complexity make absolute invulnerability a false expectation.

  • ✓

    Pay-as-you-go pricing model

    Why this is correct

    Pay-as-you-go pricing means customers are billed for metered metrics such as vCPU-hours, memory usage, storage per GB-month, or network egress, rather than for fixed pre-purchased capacity. This operationalizes cost telemetry: when demand falls, scaling down immediately lowers the invoice, reducing the expensive idle capacity that often plagues data centers. Granular, sometimes per-second metering lets organizations match spend directly to actual resource consumption, making FinOps a practical discipline.

  • ✗

    Complete transfer of security responsibility to the provider

    Why it's wrong here

    The cloud is architected around a shared responsibility model: the provider secures physical hosts, the hypervisor, the network spine, and availability zones, but the customer remains accountable for access management, encryption configuration, workload patching, application security, and compliance of their data. Even if a customer uses a managed service or outsourced security tooling, contractual accountability ultimately stays with the customer, usually due to data owner and regulatory obligations. Therefore a complete transfer of security responsibility is structurally impossible.

  • ✓

    Elimination of upfront capital expenses

    Why this is correct

    Switching to cloud shifts information-technology spending from capital expenditure (buying servers, storage arrays, and networking hardware) to operational expenditure (paying subscription or consumption-based fees). Organizations no longer need to fund large upfront purchases, reserve data-center space, or track asset depreciation, which improves near-term cash flow and reduces the financial risk of infrastructure becoming obsolete. This financial model change is one of the core reasons many enterprises migrate their workloads to the cloud.

About these practice questions

One of 848 original GCDL practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.