The city runs a general managed pool for web APIs and a separate GPU self-managed pool for model inference on one OKE cluster. What unit holds shape, image, subnet, and Kubernetes version for each capacity group?
Select an answer to reveal the explanation.
Short Explanation
A node pool is the capacity bucket: shape, image, subnet, and Kubernetes version live there. You can run more than one pool—general managed beside GPU self-managed—and aim workloads with labels and taints. That is cluster capacity design for developers, not a tenancy landing-zone exam.
Full Explanation
Worker capacity on OKE lives in node pools (managed or virtual, and self-managed joins as specialized capacity). Shape, image, subnet, and Kubernetes version are pool-level settings. Multiple pools on one cluster let teams isolate GPU inference from general web APIs using labels and taints. Replica counts and ConfigMaps do not replace node pools; landing-zone docs are out of scope as the unit of worker configuration.