Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An organization is deploying a public-facing, stateless web service on Google Cloud Compute Engine. You have created an instance template that defines the base VM configuration. The application sits behind an HTTP(S) Load Balancer and experiences unpredictable spikes and drops in user requests throughout the day.
You need to automatically adjust the number of VM instances to meet changing demand while preventing over-provisioning and controlling infrastructure costs.
Which configuration should you implement?
Vertical scaling involves increasing or decreasing the compute capacity (vCPU and RAM) of an individual machine or managed database rather than adding more instances. Cloud SQL is a managed relational database service (MySQL, PostgreSQL, SQL Server) and is not used to host application compute servers.
You were scaling the hardware specifications (CPU and memory) of a managed relational backend database to accommodate increased transactional read/write workloads.
A Managed Instance Group (MIG) is a collection of identical Compute Engine virtual machines (VMs) deployed from a single instance template. An autoscaling policy automatically adjusts the number of VM instances in the group (scaling out by adding VMs during high load and scaling in by deleting VMs during low load) based on target utilization metrics.
A Managed Instance Group with an autoscaling policy is the native, Google-recommended compute solution for managing stateless, horizontally scalable workloads behind a load balancer.
Standalone Compute Engine VMs are independent virtual machine instances that are not attached to an instance group. Cloud Monitoring provides visibility into performance metrics, logs, and operational health across Google Cloud resources.
The goal was to configure notification alerts (such as email or PagerDuty incidents) when aggregate VM resource utilization exceeded defined thresholds.
An unmanaged instance group is a collection of heterogeneous Compute Engine VM instances that do not share a common configuration template and must be created and configured individually.
You needed to apply load balancing across a legacy set of pre-existing, differently configured VMs that do not support automated scaling or uniform templating.
Change the inputs and watch how the outcome changes.

Switch the backend architecture and traffic conditions to see how each configuration handles unpredictable 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