Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is planning the migration of three distinct enterprise workloads to Google Cloud:
ext4 journaling file system.Which combination of Google Cloud storage services should you recommend?
This design maps each application workload to its optimal storage abstraction in Google Cloud: Cloud Storage for object storage, Filestore for fully managed network-attached file storage (NAS), and Persistent Disk for high-performance virtual block storage.
ReadWriteMany), fully preserving standard POSIX file permissions and folder hierarchies without code refactoring.ext4 to ensure data integrity and maximize IOPS and low-latency performance for transactional database engines.This combination aligns access protocols, latency expectations, and sharing semantics precisely with each workload's architectural profile, avoiding performance degradation or application redevelopment.
This option uses Cloud Storage for both the unstructured archive and the shared content management system, while assigning Filestore as the transactional database back-end.
ext4 journaling file system is designed for block storage (Persistent Disk or Hyperdisk), not a network-attached NFS share (Filestore).Workload 2 was modern cloud-native software rewritten to use object storage SDKs, and Workload 3 was an application sharing unstructured reports across several servers rather than a raw block database.
This architecture deploys Filestore for petabyte-scale media archives, Persistent Disk for the multi-VM shared content management system, and Cloud Storage as the primary storage layer for the transactional database.
ext4, xfs). They cannot provide concurrent read-write access to multiple independent VMs simultaneously without clustered file systems.ext4.Workload 1 required low-latency POSIX file operations, Workload 2 ran on an isolated single host with local block volumes, and Workload 3 consisted entirely of static object backups.
This configuration suggests using Persistent Disk for unstructured archives, Cloud Storage with FUSE or API access for the shared legacy CMS, and Filestore as the database block volume.
ext4 block volume.Workload 1 was a high-performance local cache disk, Workload 2 was a static asset distribution site, and Workload 3 required shared database dump exports.
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 Validated