Choose, then check the mechanism.

Which production topology is mandatory for an Autopilot cluster?

Why: Autopilot clusters are always regional. Multi-region availability still requires more than one cluster or another recovery design.

A 60-node plan uses the usual /24 Pod block per node. Approximately how many Pod addresses must the range hold?

Why: Each node reserves 256 addresses: 60 × 256 = 15,360, even though the Pod maximum is lower.

Private nodes need ordinary internet egress. What is the usual managed building block?

Why: Cloud NAT provides outbound translation without assigning public IPs or accepting unsolicited inbound sessions.

Quiz 1–3: architecture and networking

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.