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 healthcare research organization needs to store petabytes of unstructured medical imaging files, research documents, and system logs in Google Cloud. The organization has the following requirements:
How should the organization structure and manage this data in Google Cloud?
File storage organizes and represents data in a hierarchical tree of files within folders, functioning like an on-premises network-attached storage (NAS) array. Filestore is Google Cloud's fully managed file storage service that allows multiple Compute Engine VMs and GKE clusters to mount shared file systems using the Network File System (NFS) protocol and access data via standard directory paths.
100 TiB per instance depending on the service tier, which cannot accommodate multi-petabyte unstructured data lakes as cost-effectively as object storage.The organization needed a shared, low-latency NFS file system where multiple Compute Engine VMs or GKE containers simultaneously read and write shared application files within a traditional folder hierarchy.
If an application requires standard file system semantics while still storing data in Cloud Storage, organizations can use Cloud Storage FUSE to mount buckets as local file systems rather than provisioning Filestore.
Block storage divides data into fixed-size chunks called blocks, where each block is stored separately with its own unique hardware address. In Google Cloud, Persistent Disk provides durable, network-attached block storage (available in HDD and SSD options such as pd-standard, pd-balanced, and pd-ssd) that attaches directly to Compute Engine virtual machines (VMs) or Google Kubernetes Engine (GKE) clusters like a physical disk.
64 TiB per disk and 257 TiB per VM) and manage raw byte addresses rather than self-contained objects with custom metadata and immutable retention locks.The organization needed durable, high-IOPS primary disk storage attached to Compute Engine VMs to host a transactional database or serve as a virtual machine boot disk.
While block storage is foundational for virtual machine disks and databases, storing petabytes of unstructured files for analytics and archival is the core role of object storage in Cloud Storage.
Object storage is a data storage architecture specifically engineered to handle massive volumes of unstructured data. In Google Cloud, Cloud Storage is the fully managed service that provides object storage. Instead of organizing files within a rigid operating system directory tree or splitting data into raw hardware blocks, object storage manages data as distinct, self-contained units called objects placed within a flat hierarchy of containers called buckets. Each object bundles the raw file data together with system-assigned and user-defined metadata and a globally unique ID.
99.99% availability and high durability. Authorized users and applications can access objects from anywhere—both inside and outside Google Cloud—using REST APIs, client libraries, or the Google Cloud CLI.#NUMBER) rather than overwriting bytes in place. Features like Bucket Lock, Object Retention, and Object Versioning enforce regulatory compliance and prevent accidental deletion, while Object Lifecycle Management and Autoclass automatically transition aging objects into low-cost Nearline, Coldline, or Archive storage classes.Unlike block or file storage systems that are bound to specific virtual machines, network protocols, or capacity limits, Cloud Storage decouples storage from compute to provide global web accessibility, native immutability, and automated archival tiering at cloud scale.
Local SSD is a specialized block storage option that physically attaches solid-state drives directly to the host server running a Compute Engine virtual machine. Because the storage media resides on the same physical host as the compute instance rather than across a network, Local SSD delivers extreme input/output operations per second (IOPS) and ultra-low latency.
375 GiB per disk up to 12,000 GiB, or 84,000 GiB with Titanium SSD) and cannot scale to store petabytes of unstructured research data.The organization needed ultra-fast, low-latency scratch disk space or a temporary local cache for high-performance computing workloads where data is replicated elsewhere or can be easily reconstructed.
When workloads in Cloud Storage require accelerated read performance for AI/ML training and analytics without sacrificing durability, organizations can use Rapid Cache or Cloud Storage Rapid rather than relying on ephemeral Local SSDs for primary storage.
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