What's changed: Created Professional Cloud Developer Chapter 4 (Domain 3 "Configuring for deployment": deploy to Cloud Run = source deploy/revisions/traffic splitting/Eventarc-Pub/Sub triggers/Apigee; deploy to GKE = Deployment/Service, liveness/readiness probes, Horizontal Pod Autoscaler, Cloud Run vs GKE).
4.1Deploying to Cloud Run
Understand deploying to Cloud Run from source, rollouts via revisions and traffic splitting, configuring triggers (Eventarc, Pub/Sub) and event receivers, and versioning/exposing/securing APIs with Apigee.
Cloud Run, which runs containers serverless, is a central deployment target for developers. Deploy easily from source and roll out safely.
4.1.1Deploying and rolling out
Cloud Run can deploy directly from source (auto-containerized internally). Each deploy creates a revision; traffic splitting enables canary (gradually shifting percentage to a new revision) and instant rollback on issues. Configure concurrency, CPU/memory, and min/max instances to tune performance and cost. Map "gradual rollout/rollback = revisions + traffic splitting."
4.1.2Triggers and exposing APIs
Cloud Run services can be invoked by Eventarc or Pub/Sub triggers to build event-driven processing (configure Eventarc/Pub/Sub as event receivers). Expose APIs with versioning, publishing, auth, rate limiting, and protection via Apigee. Map "invoke by events = Eventarc/Pub/Sub triggers" and "API versioning/protection = Apigee."
Common: requirement → means. E.g., "deploy easily from source" = Cloud Run source deploy; "gradual rollout/instant revert" = revisions + traffic splitting; "invoke Cloud Run by events" = Eventarc/Pub/Sub triggers; "version and protect APIs" = Apigee.
Watch the mix-ups: (1) Revisions (versions) and traffic splitting (percentage control) work together. (2) Concurrency and min instances affect performance/cost/cold starts. (3) Apigee is API management, not the deployment platform itself.
4.1.3Section summary
- Cloud Run deploys from source; revisions + traffic splitting for canary/rollback
- Eventarc/Pub/Sub triggers invoke services event-driven
- API versioning/exposure/protection via Apigee
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. In Cloud Run, to gradually shift traffic to a new revision and revert on issues, what do you use?
Q2. To invoke a Cloud Run service by events, what do you use?
Q3. To centralize versioning, auth, rate limiting, and protection of public APIs, what do you use?
Q4. Which correctly describes deploying containers to Cloud Run from source?
Q5. What do Cloud Run concurrency and min instances mainly affect?
Q6. Which correctly describes revisions and traffic splitting?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.