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.
A financial analytics company is designing the compute architecture on Google Compute Engine for two distinct workloads:
Management wants to minimize infrastructure and software licensing costs while maintaining operational flexibility without locking the batch processing pipeline into rigid long-term commitments.
Which compute configuration and provisioning strategy should you recommend?
Memory-optimized machine types (such as the M-series) provide very large amounts of RAM per core for massive in-memory databases, and resource-based Committed Use Discounts (CUDs) lock an organization into specific hardware allocations in exchange for discounts over a 1-year or 3-year term. Future reservations in calendar mode reserve dedicated blocks of compute capacity for scheduled start dates and fixed durations.
The workload consisted of an enterprise in-memory relational database requiring continuous, multi-year uptime with guaranteed zonal hardware availability.
Custom machine types allow administrators to configure exact vCPU and memory allocations on supported Compute Engine machine series (such as N1, N2, N2D, and N4) rather than being constrained to rigid predefined ratios. Spot VMs are virtual machine instances provisioned from surplus Google Cloud compute capacity offered at significant discounts (60%–91%) with the caveat that Compute Engine can preempt them if capacity is reclaimed.
This architecture pairs precise resource sizing for core-licensed steady workloads with deeply discounted, pay-as-you-go preemptible resources for interruptible batch analytics, achieving maximum cost efficiency while keeping cloud infrastructure agile.
This option applies Spot VMs (which are preemptible at any moment) to the business-critical web backend service and runs the interruptible batch data processing pipeline on full-price on-demand standard VMs.
The web backend was an experimental test environment that could tolerate outages, and the batch processing pipeline had strict, uncompromisable Service Level Agreements requiring zero interruptions.
Predefined general-purpose machine types (such as standard n2-standard or e2-standard instances) come with standard power-of-two vCPU configurations (e.g., 2, 4, 8, 16). Spend-based Committed Use Discounts provide a percentage discount in exchange for committing to a minimum hourly dollar spend across Google Cloud services over a 1-year or 3-year term.
n2-standard-8 or n2-highmem-8), resulting in 2 unneeded cores that increase software licensing expenses.All workloads required predictable, non-preemptible capacity across multiple Google Cloud products and could naturally fit standard 4-vCPU or 8-vCPU shapes.
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