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 migrating a high-traffic MySQL database workload to Compute Engine on Google Cloud. An analysis of the database workload reveals the following requirements:
Which Compute Engine VM and block storage architecture should you configure to meet these performance and cost requirements?
c2) machine type with standard Persistent Disk (pd-standard), and configure read replicas to distribute query throughput.This option deploys a Compute-Optimized (C2) virtual machine instance attached to magnetic standard Persistent Disk (pd-standard), relying on multiple read replicas to distribute read query volume.
pd-standard) delivers high latency and low IOPS, causing severe performance degradation for database write operations and redo log updates.pd-standard is backed by standard HDDs and is intended for large sequential batch workloads or cold storage.The workload were compute-bound with mathematically intensive queries across a small dataset that did not require significant RAM caching or high write IOPS.
highcpu) machine type with Tier_1 networking enabled, and use attached Local SSDs configured as database swap space.This approach pairs a high-CPU (highcpu) machine type (approximately 1 to 2 GB of RAM per vCPU) with Tier_1 networking bandwidth and utilizes ephemeral Local SSDs configured as Linux swap space to extend available system memory.
highcpu machine types minimize RAM, forcing the operating system to swap pages to disk, which severely degrades relational database performance.The application were a compute-intensive distributed caching or analytics layer that required maximum network egress bandwidth and temporary scratch space.
highmem) machine type that accommodates the working set within the database buffer pool, and attach a Google Cloud Hyperdisk Balanced volume provisioned for the write workload.This architecture combines a memory-optimized high-memory (highmem) instance shape with Google Cloud Hyperdisk Balanced storage. A highmem machine type provides approximately 8 GB of RAM per vCPU, allowing large memory allocations without over-provisioning unneeded vCPUs. Hyperdisk Balanced offers flexible, decoupled provisioning of IOPS and throughput independently from storage capacity.
InnoDB buffer pool ensures that steady-state read queries are served directly from RAM rather than disk, eliminating disk I/O bottlenecks.highmem instance shape, you achieve a high RAM-to-vCPU ratio. This avoids paying for excess vCPUs that would remain idle under low CPU utilization per query.Serving reads out of RAM is dramatically faster and more cost-effective than provisioning ultra-high IOPS disk tiers to serve read queries from persistent storage. Pairing a highmem VM with Hyperdisk Balanced achieves maximum read performance at the lowest total cost of ownership.
standard) machine type with Hyperdisk Extreme provisioned to maximum IOPS to serve read operations directly from persistent storage.This approach uses a general-purpose standard machine type (4 GB RAM per vCPU) paired with Hyperdisk Extreme, provisioning maximum IOPS so that the storage layer handles all read and write queries directly without relying on in-memory caching.
InnoDB buffer pool.The database working set exceeded several terabytes and could not realistically fit into instance memory, making direct ultra-high IOPS disk access necessary.
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