You want to create an EKS cluster that supports worker nodes in multiple Availability Zones for high availability. Which networking setup is required?
Think about how worker nodes communicate and how availability zones affect fault tolerance.
For high availability, worker nodes must be spread across multiple Availability Zones. This requires subnets in each zone. Public IPs allow nodes to communicate with the internet if needed.
Which IAM role policy is necessary for EKS worker nodes to join the cluster and communicate with the control plane?
Focus on policies that allow nodes to register and pull container images.
Worker nodes need AmazonEKSWorkerNodePolicy to join the cluster, AmazonEC2ContainerRegistryReadOnly to pull images, and AmazonEKS_CNI_Policy for networking.
You want to restrict access to your EKS cluster API endpoint so only specific IP addresses can connect. Which configuration achieves this?
Consider how EKS allows IP-based filtering on the API endpoint.
Enabling public endpoint access with allowed CIDR blocks restricts API access to specified IP ranges, controlling who can connect.
When you enable the Cluster Autoscaler on your EKS cluster, what behavior should you expect when pod resource requests increase?
Think about how autoscaling helps with resource shortages.
The Cluster Autoscaler adds nodes when pods cannot be scheduled due to insufficient resources, ensuring workload demands are met.
You want to enable detailed logging for your EKS cluster to monitor API calls, authentications, and scheduler events. Which logging configuration is correct?
Consider which logs provide comprehensive cluster activity visibility.
Enabling all control plane logs gives full visibility into cluster operations, which is best for monitoring and troubleshooting.