Professional Cloud Developer Practice Test

What this test covers

One concept per question, across the topics Professional Cloud Developer draws on.

• Kubernetes provides a consistent deployment target across environments
• Pending pods indicate a scheduling problem, almost always insufficient capacity
• Workload identity federation eliminates long-lived service account keys
• Safe rollouts require readiness signalling and graceful connection draining
• Signed URLs grant time-limited access to a specific object without an identity
• Workload Identity removes long-lived credentials from the cluster
• Scale to zero suits spiky traffic with a small operations team
• Canary releases validate against real traffic before full rollout
• Namespaces alone provide no network isolation; network policies do
• Secrets belong in a dedicated service with access control, versioning and audit
• Build once, promote the same artefact through every environment
• Traces show where time is spent across service boundaries
• Firestore's client libraries provide offline persistence and automatic synchronisation
• At-least-once delivery makes idempotent consumers a requirement, not an optimisation
• Connection pooling decouples application concurrency from database connection count
• Cloud Run concurrency directly determines how many instances a given request rate needs
• Attach a purpose-specific service account and grant only the role it needs