Finish with production diagnosis.

0 / 15

Your score updates as you check answers.

A Pod is Pending. What is the first high-value action?

Why: The scheduler reason selects the correct branch: requests, placement, volume, policy or infrastructure capacity.

Gateway shows Programmed True. What remains to prove?

Why: Programmed confirms controller progress, not the full user path through cloud infrastructure and application health.

What does Backup for GKE not recreate?

Why: The target cluster must already exist; networking, node pools, features and external dependencies need separate infrastructure recovery.

Quiz 13–15: troubleshooting and synthesis

This quiz is easiest to understand by separating the Kubernetes contract from the Google Cloud implementation. Choose one answer for each question, then use Check answer to reveal the explanation. Questions mix recall, design and troubleshooting from the full deck. The Kubernetes objects stay familiar, but GKE supplies controllers, infrastructure and safe defaults around them. This is why a team can move from an on-premises cluster without rewriting every workload, while still needing to redesign networking, identity and operational ownership for the cloud environment.

A useful inspection step is `kubectl explain gateway.spec`. Read the output as evidence, not as a ritual: first confirm the desired object exists, then look at status conditions, events and the Google Cloud resource it represents. In production, capture the expected result in a runbook or automated check so an operator can distinguish slow reconciliation from a configuration error.

Production gotcha: A correct answer should be supported by a mechanism from the slides, not by brand preference. The safe habit is to verify quotas, regional availability and feature support against current Google Cloud documentation before rollout. Reset the quiz after review to test retention without prompts.