Why managed Kubernetes matters in AWS - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why choose managed Kubernetes over self-managed?

Which of the following is the main advantage of using a managed Kubernetes service like AWS EKS instead of setting up Kubernetes yourself?

A You get automatic updates and security patches managed by the provider.

B You must manually configure the control plane and worker nodes.

C You can avoid paying for cloud resources since it runs on your local machine.

D You have full control over every node and component without restrictions.

💡 Hint

Think about what tasks managed services handle for you automatically.

Managed Kubernetes services handle control plane management, updates, and security patches, reducing your operational burden.

💻 Command Output

intermediate

Output of AWS EKS cluster creation command

What is the expected output when you successfully create an AWS EKS cluster using the AWS CLI command aws eks create-cluster?

AWS

aws eks create-cluster --name my-cluster --role-arn arn:aws:iam::123456789012:role/EKSRole --resources-vpc-config subnetIds=subnet-abc123,subnet-def456

A { "cluster": { "name": "my-cluster", "status": "ACTIVE", "endpoint": "https://1234567890.gr7.us-east-1.eks.amazonaws.com" } }

B { "cluster": { "name": "my-cluster", "status": "CREATING", "endpoint": null } }

C Error: Missing required parameter 'region'

D SyntaxError: Unexpected token in JSON

💡 Hint

Right after creation, the cluster status is not yet ACTIVE.

When you create an EKS cluster, the initial status is 'CREATING'. It becomes 'ACTIVE' only after setup completes.

🔀 Workflow

advanced

Correct order to deploy an app on AWS EKS

Arrange the steps in the correct order to deploy a containerized app on AWS EKS.

A 3,1,2,4

B 1,3,2,4

C 1,2,3,4

D 2,1,3,4

💡 Hint

Think about what must exist before you configure tools or deploy apps.

You first create the cluster, then configure kubectl to access it, then push your image, and finally deploy your app manifests.

❓ Troubleshoot

advanced

Diagnosing EKS node group connection issues

You created an EKS cluster and a managed node group, but your pods stay in Pending state. What is the most likely cause?

A The node group IAM role lacks permissions to join the cluster.

B The EKS cluster control plane is not yet ACTIVE.

C The Docker image is missing from the container registry.

D kubectl is not installed on your local machine.

💡 Hint

Think about what allows nodes to register with the cluster.

If the node group's IAM role lacks the right permissions, nodes cannot join the cluster, so pods remain Pending.

✅ Best Practice

expert

Best practice for securing AWS EKS clusters

Which practice is considered best for securing access to your AWS EKS cluster?

A Disable encryption at rest for etcd to improve performance.

B Allow unrestricted access to the Kubernetes API server from any IP.

C Store all secrets as plain text in ConfigMaps for easy access.

D Use AWS IAM roles for service accounts (IRSA) to grant pod permissions.

💡 Hint

Consider how to limit permissions for pods securely.

Using IAM roles for service accounts (IRSA) allows fine-grained, secure permissions for pods without sharing node IAM roles.