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 team has deployed a new revision (orders-v2) of an internal microservice running on Cloud Run. Before directing any live user traffic to orders-v2, quality assurance engineers need to perform isolated smoke testing using a dedicated URL.
After testing is successful, you need to route 10% of incoming production requests to orders-v2 and keep 90% of traffic directed to the existing stable revision (orders-v1).
Which configuration approach should you use?
orders-v2 to 10 and orders-v1 to 90 so that instances automatically distribute requests proportionally.Concurrency defines the maximum number of concurrent requests that a single container instance can process simultaneously before Cloud Run spins up additional container instances to handle incoming load.
You wanted to optimize memory and CPU performance by tuning how many simultaneous requests an individual container handles.
orders-v2 for isolated URL testing, then adjust traffic splitting on the service to assign 10% to orders-v2 and 90% to orders-v1.Cloud Run uses an immutable revision model where every deployment creates a new revision. Revision tags provide a direct, dedicated URL scheme (for example, https://TAG---SERVICE-IDENTIFIER.run.app) to access a specific revision without exposing it to the main service endpoint. Traffic splitting allows administrators to distribute incoming requests across two or more revisions by defining specific percentage weights.
test or stage) directly to orders-v2 creates a unique URL that routes 100% of traffic hitting that URL specifically to orders-v2, while keeping main service traffic at 0% for that revision.orders-v2 and 90% to orders-v1 via the root service URL.orders-v1 takes effect immediately with no redeployment needed.gcloud run services update-traffic or through the Google Cloud console.This approach leverages native Cloud Run traffic management capabilities within the same service boundary. It eliminates the operational overhead of creating external load balancers, duplicate projects, or separate DNS records.
orders-v2 as an asynchronous Cloud Run Job, then replace the container image of orders-v1 once testing completes.Cloud Run jobs are designed for running containerized tasks to completion asynchronously (such as batch data processing, backups, or database migrations) rather than serving continuous HTTP web traffic.
orders-v1 immediately exposes all users to the new code without a canary phase (10/90 split).The workload was a scheduled data transformation script or nightly batch job that did not process interactive HTTP web requests.
orders-v2 into a separate Google Cloud project, and configure Cloud DNS round-robin weighted records between both service endpoints.Cloud DNS is an enterprise DNS hosting service that resolves domain names to IP addresses or endpoints and can use routing policies such as weighted round-robin to distribute traffic across distinct IP targets.
You needed to distribute global incoming traffic across entirely separate, multi-region backends or separate independent architectures during a complex multi-cloud or multi-project infrastructure migration.
Change the inputs and watch how the outcome changes.

Switch the approach and rollout stage to see how each configuration routes QA and production requests.
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