Create ResourceQuota objects with hard CPU and memory limits per namespace and Apply LimitRange to set default requests and permissive limits for containers in each namespace are the correct choices.

Create ResourceQuota objects with hard CPU and memory limits per namespace enforces a namespace level cap on total CPU and memory consumption so each team has a hard budget and cannot exceed it over the long term. This is the right mechanism to guarantee per team limits across all pods in a namespace.

Apply LimitRange to set default requests and permissive limits for containers in each namespace provides sensible defaults for requests so pods schedule predictably while allowing permissive limits that let teams temporarily overcommit during spikes. Combined with a ResourceQuota this approach balances scheduling behavior with an overall cap.

Horizontal Pod Autoscaler using custom metrics is about scaling replica counts based on metrics and it does not provide namespace level caps or per team resource budgets. It helps with handling load but it is not a mechanism to enforce team quotas.

GKE Autopilot is a managed cluster mode that changes how resources and requests are handled at the node and control plane level and it is not a configuration method to implement per namespace hard quotas plus permissive defaults. Choosing Autopilot changes the operational model rather than directly providing the requested quota behavior.

Enable Vertical Pod Autoscaler adjusts container resource requests over time to match observed usage and it can conflict with horizontal scaling strategies. It is not a substitute for namespace level ResourceQuota and does not enforce hard per team limits.

Full AWS Practitioner Certification Question