Cloud Digital Leader Why cloud technology is transforming business Practice Question
A hospital network wants to improve patient outcomes by sharing medical records across its 12 hospitals so that any physician can access a patient's complete history. Currently, each hospital has its own isolated system. Which cloud characteristic is most relevant to enabling this cross-hospital data sharing?
⚠ Common exam trap
Google Cloud often tests the distinction between 'resource pooling' (multi-tenancy of infrastructure) and 'ubiquitous network access' (broad network reachability), leading candidates to incorrectly choose resource pooling when the question focuses on cross-location data sharing rather than shared hardware.
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
✓
Cloud's ubiquitous network access, enabling a secure shared data platform accessible to authorized physicians across all 12 hospital locations through standard internet connectivity
Ubiquitous network access is the cloud characteristic that ensures a secure, shared data platform is accessible to authorized physicians across all 12 hospital locations via standard internet connectivity. This enables seamless cross-hospital data sharing without requiring each hospital to maintain its own isolated system, as the cloud provides consistent network-based access to the centralized medical records.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Cloud elasticity, which allows the hospital to scale up server capacity during peak admission periods
Why it's wrong here
Elasticity addresses dynamic capacity adaptation — rapidly adding or removing virtual machines, containers, or storage to match workload spikes, such as emergency room surges during flu season. It has no direct effect on cross-location data accessibility: a physician at site A still cannot query patient records at site B if the systems are disconnected, regardless of how much compute is available. Elasticity solves peak-performance bottlenecks, not the architectural problem of fragmented, non-network-interoperable medical record repositories.
- ✓
Cloud's ubiquitous network access, enabling a secure shared data platform accessible to authorized physicians across all 12 hospital locations through standard internet connectivity
Why this is correct
Ubiquitous network access (one of NIST's cloud characteristics) is directly applicable. A shared cloud-hosted medical records platform makes patient data accessible to authorized physicians from any hospital location — exactly solving the isolated system problem.
- ✗
Cloud's pay-per-use billing model, which reduces the cost of medical record storage
Why it's wrong here
The pay-per-use billing model is a financial and operational characteristic of cloud consumption (measured service), reducing upfront capital expense and aligning cost with usage for storage. However, the hospital's immediate clinical challenge is that authorized physicians cannot access patient data across 12 isolated systems — a cost reduction does not enable that access. Even free storage would not solve the problem without a shared, network-accessible data platform with identity-based authorization; the pay-per-use model is orthogonal to data interoperability and secure accessibility.
- ✗
Cloud resource pooling, which allows multiple hospitals to share physical compute resources
Why it's wrong here
Resource pooling is primarily a provider-side infrastructure mechanism: the hypervisor or orchestration layer dynamically assigns physical and virtual compute/storage across many tenants to maximize utilization. While this enables the cloud's multitenant economics, it does not create the logical data-sharing plane needed for physicians to retrieve records across 12 distinct hospital sites. The barrier is organizational data silos, not a shortage of physical servers; pooling alone leaves each site's EHR system isolated unless a network-accessible shared platform is overlaid.
Go deeper
Related to this question
About these practice questions
This GCDL question is part of Courseiva's 829-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
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.