Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!
Prepare and test your skills
Prepare and test your skills
A Cloud Load Balancer distributes traffic to a Managed Instance Group containing identical Compute Engine VMs. The VMs send CPU and load metrics to Cloud Monitoring, which feeds the data to an Autoscaling Policy that directs the MIG to scale instances up or down.
Managed Instance Groups (MIGs) manage a collection of identical virtual machines as a single unit to provide elastic scaling. They rely on an autoscaling policy to monitor performance metrics such as average CPU usage or load balancing capacity, automatically adding or removing instances to match demand. This automation delivers high availability by replacing failed instances, maintains cost efficiency, and ensures reliable performance.
Cloud Run offers request-driven scaling that automatically scales to zero when there is no traffic and quickly scales up when new requests arrive. This makes it ideal for containerized workloads that do not need permanent server management, as it handles sudden traffic spikes without requiring manual intervention.
Spot VMs offer unused Google Cloud capacity at a steep discount but can be reclaimed by Google at any time. They are best suited for flexible, interruption-tolerant tasks that can handle potential preemption, allowing organizations to significantly reduce compute costs for batch jobs or fault-tolerant workloads.
Committed Use Discounts (CUDs) require a long-term contract commitment in exchange for lower prices, while Sustained Use Discounts (SUDs) provide automatic credits on continuous virtual machine usage without requiring a contract. Both help organizations predict and control long-term IT budgets, with CUDs offering more predictable savings and SUDs providing automatic discounts for ongoing usage.
Elastic scaling allows a cloud system to automatically adjust its resources to match changing demand. In Google Cloud, Managed Instance Groups (MIGs) manage a collection of identical virtual machines as a single unit to provide this flexibility. To handle sudden traffic spikes, horizontal scaling adds more virtual machine instances to a group rather than making a single machine larger. A MIG relies on an autoscaling policy to monitor performance metrics, such as average CPU usage or load balancing capacity, and decide when to scale. This automation delivers high availability by replacing failed instances, maintains cost efficiency, and ensures reliable performance.
For applications that do not need permanent server management, serverless platforms like Cloud Run offer request-driven scaling. This service automatically scales to zero when there is no traffic and quickly scales up when new requests arrive, making it perfect for containerized workloads. For more complex container setups, Google Kubernetes Engine (GKE) automates scaling at two different levels. The Horizontal Pod Autoscaler (HPA) adjusts the number of active Pods based on memory or custom metrics, while the cluster autoscaler adds or removes the underlying physical nodes. To make these systems work effectively, administrators use Cloud Monitoring to track telemetry data, like GPU utilization or request latency, and set alerts to proactively manage resource needs.
Workload portability means you can move applications between on-premises data centers and the cloud without rewriting the code. Containerization makes this possible by packaging an application with its dependencies, while Kubernetes provides a common runtime layer across different cloud providers to prevent vendor lock-in. To manage these distributed environments, GKE Enterprise uses a concept called fleets to group clusters together for unified management. This platform simplifies multi-cluster management, enforces zero-trust security using identity-based access, and maintains consistent governance across hybrid networks.
Designing a flexible hybrid solution often involves specific deployment patterns to handle varying business demands. An Edge Hybrid architecture runs critical tasks locally to ensure low latency and continuous operation even when internet connectivity is unstable. Alternatively, Cloud Bursting allows a private data center to temporarily route excess traffic to public cloud resources during sudden usage spikes. As data moves across these cloud boundaries, teams must protect it using encryption, apply strict data classification rules, and clearly map out the shared responsibility model between the user and the provider.
Maintaining consistency across a hybrid cloud requires automating the creation of resources. Tools like Terraform and the Kubernetes Resource Model allow teams to define their infrastructure using version-controlled configuration files. This process creates an immutable infrastructure model where resources are completely re-created from scratch rather than modified in place. Using these automated tools reduces configuration errors, improves operational efficiency, and ensures that deployments remain highly predictable.
Optimizing your cloud spend requires matching your compute choices to the exact needs of your workloads. For flexible, interruption-tolerant tasks, Spot VMs offer unused Google Cloud capacity at a steep discount but can be reclaimed by Google at any time. If standard virtual machine configurations do not fit your workload, Custom Machine Types let you customize the exact amount of CPU and memory you need to avoid paying for excess capacity. When choosing a platform, architects must balance the deep configuration flexibility of virtual machines against the low operational overhead of serverless options like Cloud Run.
Google Cloud offers several discount strategies to help organizations predict and control their long-term IT budgets. Teams can use Committed Use Discounts (CUDs) to secure lower prices in exchange for a long-term contract, or rely on Sustained Use Discounts (SUDs) for automatic credits on continuous virtual machine usage. To ensure these resources are used efficiently, administrators practice right-sizing by analyzing performance telemetry. Tools like Recommender and Cloud Monitoring analyze actual resource usage to provide intelligent recommendations, helping teams safely shrink underutilized systems without hurting performance.
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?