Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A financial analytics team is deploying a containerized simulation API that processes synchronous HTTP requests. The service often sits idle for several hours before receiving sporadic traffic.
The application has the following requirements:
Which Google Cloud hosting environment should the team select?
App Engine flexible environment is a Platform-as-a-Service (PaaS) hosting option that runs applications inside Docker containers deployed on managed Compute Engine VMs. It provides custom runtime flexibility while letting Google handle underlying VM provisioning, health checks, and regional instance groups.
Your requests finished in under 60 minutes, your workload could tolerate weekly managed VM restarts (or short retries), and you wanted a PaaS wrapper over Compute Engine VMs without managing OS patches.
Even though App Engine flexible environment runs on top of Compute Engine VMs, its managed execution layer enforces the same 60-minute timeout constraint as Cloud Run services while adding slower scale-out times.
Compute Engine is Google Cloud's Infrastructure-as-a-Service (IaaS) platform that runs customizable virtual machines (VMs) inside your Virtual Private Cloud. Using the Standard provisioning model provides dedicated compute instances designed for continuous operation, where you retain full control over the operating system, container runtime, and instance lifecycle.
Serverless environments prioritize rapid scale-to-zero elasticity by enforcing strict request timeouts and managed lifecycles. When a workload combines 90-minute synchronous processing with zero tolerance for cold starts or forced restarts, an instance-based environment like Compute Engine avoids the hard runtime constraints of serverless platforms.
App Engine standard environment is a sandboxed serverless platform optimized for rapid scaling and low-cost operation using Google-managed language runtimes. Under automatic scaling, the platform dynamically provisions or terminates instances based on request load and pending latency.
/tmp) and restricts custom system-level binaries or native OS modifications.The application were a lightweight, stateless web API built in a supported runtime whose requests completed in under 10 minutes and could tolerate occasional cold starts (or used min_instances for warm capacity).
While App Engine standard supports longer timeouts under manual or basic scaling, it lacks the custom container support and full VM control provided by Compute Engine.
Cloud Run is a fully managed serverless container platform that abstracts infrastructure management and automatically scales container instances based on incoming request traffic. Configuring min_instance_count to 1 keeps a baseline container instance warm, while startup CPU boost temporarily allocates extra CPU during container initialization to speed up cold starts.
1 prevents cold starts for the first concurrent requests, additional instances launched during traffic spikes still incur container startup latency, even with startup CPU boost enabled.Each synchronous simulation completed in under 60 minutes (or could be refactored into asynchronous tasks via Cloud Run jobs or Cloud Tasks), allowing you to benefit from serverless scaling while using min-instances to keep baseline containers warm.
Many developers assume that setting minimum instances and instance-based billing turns a Cloud Run service into an unrestricted VM, but the 60-minute HTTP request timeout still applies to every incoming service request.
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