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.
Your company hosts a public REST API on Google Cloud Run. You have developed an update with performance improvements, but you want to test it safely in production before doing a full rollout.
You need to implement a canary deployment where:
What should you do?
This option attempts to overwrite an existing revision and use Cloud Run instance limits (--max-instances) to throttle the number of requests processed by the new code.
max-instances setting restricts concurrency ceiling; it does not distribute a percentage of total incoming live requests between different code versions.429 Too Many Requests or 503 Service Unavailable errors to clients rather than routing them to older code.The goal was to protect downstream databases or external services from being overwhelmed by setting an upper bound on compute concurrency, rather than performing a canary rollout.
This approach provisions two distinct Cloud Run services (e.g., api-prod and api-canary) behind an external Application Load Balancer with serverless Network Endpoint Groups (NEGs), using backend service weighting to split traffic.
You needed to split traffic across services deployed in different Google Cloud regions, across hybrid on-premises endpoints, or if you required specialized advanced security policies (like Cloud Armor) across multi-region serverless NEGs.
This option introduces Cloud Pub/Sub as a message broker between clients and the Cloud Run service, attempting to sample 10% of incoming messages and push them to the new revision.
The application was an asynchronous background worker processing event payloads from a queue, and you wanted to test worker logic by consuming messages from a canary subscription.
Cloud Run traffic splitting is a built-in feature that enables users to divide incoming request traffic between two or more active revisions of the same service using precise percentages that sum to 100%.
--no-traffic (or without routing 100% immediately) and explicitly allocate 10% of traffic to the new revision while keeping 90% on the current production revision.gcloud run services update-traffic command or via the Google Cloud Console.
This approach leverages Cloud Run's native, serverless traffic allocation mechanism. It achieves the exact percentage distribution required for canary releases with minimal operational overhead and zero extra architectural complexity.
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