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 runs a legacy monolithic web application on on-premises virtual machines. The monolithic application combines API routing, background order processing, and state management into a single large codebase, resulting in slow release cycles and operational bottlenecks. During seasonal promotions, the ingress API gateway experiences major traffic spikes, forcing the organization to over-provision the entire infrastructure to maintain availability.
The team wants to modernize this architecture on Google Cloud by refactoring the monolith into loosely coupled microservices to increase release agility and ensure that the ingress and stateless service layers can scale dynamically based on workload demand.
Which modernization approach should you recommend?
A Managed Instance Group (MIG) manages pools of identical Compute Engine virtual machines (VMs), providing automated healing and scaling. Schedule-based autoscaling adjusts the number of VM instances in advance according to predetermined times, dates, or recurring schedules.
The scenario required a minimal-effort migration without modifying application code or architecture, and the traffic spikes followed a strictly predictable daily calendar.
Vertical scaling involves moving a workload to a larger virtual machine with greater CPU, memory, or I/O capacity, while using operating system multi-threading to handle concurrent operations within a single host instance.
The application were a non-distributed legacy database or proprietary commercial software that cannot be containerized or distributed across multiple hosts.
A DaemonSet is a Kubernetes workload controller that ensures a copy of a specific pod runs on all (or selected) worker nodes across the cluster. DaemonSets are primarily designed for background node-level operational agents, such as logging collectors, monitoring daemons, and storage drivers.
You needed to deploy a mandatory system monitoring agent or logging daemon to collect telemetry from every physical node in the GKE cluster.
Google Kubernetes Engine (GKE) is a managed Kubernetes platform that simplifies deploying, managing, and scaling containerized applications. When decomposing a monolithic architecture into microservices, deploying workloads as Kubernetes Deployments coupled with Horizontal Pod Autoscaling (HPA) allows individual components—such as ingress routers, API gateways, and stateless business services—to scale their replica counts automatically based on metrics like CPU utilization or custom traffic volume.
Migrating from a monolithic VM deployment to containerized microservices on GKE provides the exact elasticity and agility required. It decouples the application lifecycle while allowing high-traffic components like the ingress layer to autoscale independently on demand.
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