Google Associate Cloud EngineerDeploying and implementing a cloud solutionMedium
A company is migrating an on-premises web application to Google Cloud. The application uses a custom Apache HTTP Server configuration and requires direct control over the operating system. The application experiences variable traffic, with occasional spikes. Which Google Cloud compute service would provide the best balance of flexibility, control, and scalability for this scenario?
- ACompute Engine with Managed Instance Groups
- BGoogle Kubernetes Engine (GKE) Autopilot
- CApp Engine Standard environment
- DCloud Run
Show answer & explanationAnswer & explanation
Correct answer: A. Compute Engine with Managed Instance Groups
Compute Engine provides full control over the operating system and custom configurations like Apache HTTP Server. Managed Instance Groups (MIGs) allow for automatic scaling based on traffic, balancing flexibility and scalability. This meets the requirements for OS control and variable traffic.
Why the other options are wrong
- B. GKE Autopilot manages Kubernetes clusters for containerized applications, but the scenario emphasizes direct OS control and custom Apache, which is better suited for Compute Engine VMs.
- C. App Engine Standard is a PaaS with limited OS control and specific language runtimes, not suitable for custom Apache configurations.
- D. Cloud Run is serverless for stateless containers and offers less OS control, not ideal for a custom Apache setup requiring direct OS access.
Compute Engine with MIGs
Compute Engine offers Infrastructure as a Service (IaaS) with full control over virtual machines. Managed Instance Groups (MIGs) automate the deployment, management, and scaling of multiple VMs.
- Full OS and software control.
- MIGs provide auto-scaling and auto-healing.
- Ideal for custom configurations and lift-and-shift migrations.
- Requires more management overhead than PaaS/serverless.
Memory trick: Compute Engine with MIGs gives you the VM keys and a scaling crew.