Why Cloud Run matters for containers in GCP - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why choose Cloud Run for container deployment?

Cloud Run is a service to run containers. Which of these is the main reason Cloud Run is useful?

A It automatically scales containers up and down based on traffic without manual setup.

B It requires you to manage virtual machines for container hosting.

C It only supports containers built with specific programming languages.

D It needs you to configure load balancers manually before deployment.

💡 Hint

Think about what makes Cloud Run easy compared to traditional container hosting.

Cloud Run automatically adjusts the number of container instances based on incoming requests, so you don't manage servers or scaling manually.

❓ Architecture

intermediate

How does Cloud Run handle container instances?

Imagine you deploy a container to Cloud Run. What happens when no requests come in for a while?

A Cloud Run requires manual intervention to stop or start containers.

B Cloud Run keeps the container running indefinitely to reduce startup time.

C Cloud Run converts the container into a virtual machine for better performance.

D Cloud Run automatically stops the container to save resources and restarts it on new requests.

💡 Hint

Think about how serverless services save resources when idle.

Cloud Run stops containers when idle to save costs and restarts them automatically when new requests arrive.

❓ service_behavior

advanced

What is the effect of setting concurrency to 1 in Cloud Run?

Cloud Run allows setting concurrency, the number of requests a container instance handles at once. What happens if concurrency is set to 1?

A Cloud Run merges all requests into a single batch to process at once.

B Each container instance handles only one request at a time, potentially increasing instances but reducing request wait time.

C Cloud Run disables autoscaling and uses a fixed number of container instances.

D Each container instance handles multiple requests simultaneously, improving resource use but increasing latency.

💡 Hint

Think about how concurrency affects parallel request handling.

Setting concurrency to 1 means each container processes one request at a time, which can increase the number of instances but can reduce request queuing delays.

❓ security

advanced

How does Cloud Run secure container access by default?

When you deploy a container on Cloud Run, who can access it by default?

A Only authenticated users with explicit permission can access the container service.

B Anyone on the internet can access the container without restrictions.

C Only users inside the same virtual private cloud (VPC) can access the container.

D Access is blocked by default and requires manual firewall rules to open.

💡 Hint

Think about default security best practices for cloud services.

By default, Cloud Run services require authentication and only allow access to authenticated users unless configured to allow unauthenticated access.

✅ Best Practice

expert

What is the best practice for deploying stateless containers on Cloud Run?

You want to deploy a containerized app on Cloud Run. Which practice ensures smooth scaling and reliability?

A Disable autoscaling to keep container instances always running.

B Store session data inside the container's local filesystem for faster access.

C Design the container to be stateless, so any instance can handle requests without relying on local data.

D Use a single container instance to avoid scaling issues with shared state.

💡 Hint

Think about how containers scale and share workload in Cloud Run.

Stateless containers allow Cloud Run to scale instances freely without worrying about lost data or session state, improving reliability and performance.