Node groups (managed, self-managed, Fargate) in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Node Group Types in EKS

Which statement correctly describes the difference between managed node groups and self-managed node groups in Amazon EKS?

A Self-managed node groups are automatically updated by AWS, while managed node groups require manual updates by the user.

B Managed node groups are automatically updated and maintained by AWS, while self-managed node groups require manual updates and management by the user.

C Both managed and self-managed node groups are fully managed by AWS with no user intervention needed.

D Managed node groups cannot run on EC2 instances, while self-managed node groups run on EC2 instances.

💡 Hint

Think about who is responsible for updating and maintaining the nodes in each group.

Managed node groups are maintained by AWS, including updates and health monitoring. Self-managed node groups require the user to handle updates and maintenance.

❓ Architecture

intermediate

Choosing Node Group Types for Cost and Maintenance

You want to run a Kubernetes workload on EKS with minimal maintenance overhead and automatic scaling. Which node group type should you choose?

A Self-managed node groups, because they allow full control over the instances.

B Managed node groups, because AWS handles updates and scaling automatically.

C Fargate, because it runs containers without managing servers and scales automatically.

D On-premises nodes connected via AWS Outposts.

💡 Hint

Consider which option removes the need to manage servers entirely.

Fargate runs containers without requiring you to manage servers or nodes, providing automatic scaling and minimal maintenance.

❓ Configuration

advanced

EKS Node Group Configuration for Mixed Workloads

You want to configure an EKS cluster to run both long-running services and batch jobs. You decide to use managed node groups for services and Fargate for batch jobs. Which configuration is correct to achieve this?

AWS

eksctl create cluster --name my-cluster --region us-west-2

# Add Fargate profile for batch jobs
aws eks create-fargate-profile --cluster-name my-cluster --fargate-profile-name batch-jobs --pod-execution-role-arn arn:aws:iam::123456789012:role/AmazonEKSFargatePodExecutionRole --subnets subnet-abc123 subnet-def456 --selectors namespace=batch

A Use managed node groups for batch jobs and self-managed node groups for services.

B Use self-managed node groups for batch jobs and Fargate for services.

C Use only Fargate for all workloads to simplify management.

D Use managed node groups for the default namespace and create a Fargate profile targeting the batch namespace for batch jobs.

💡 Hint

Think about how Fargate profiles select pods by namespace or labels.

Managed node groups handle the default namespace workloads, while Fargate profiles can be configured to run pods in specific namespaces like 'batch' for batch jobs.

❓ security

advanced

IAM Roles for Node Groups and Fargate Profiles

Which IAM role is required for running pods on Fargate in an EKS cluster?

A An IAM role with AmazonEKSFargatePodExecutionRolePolicy attached, assigned to the Fargate profile for pod execution.

B An IAM role with AmazonEKSWorkerNodePolicy attached, assigned to the EC2 instances in managed node groups.

C An IAM role with AmazonEC2FullAccess attached, assigned to the EKS control plane.

D No IAM role is needed for Fargate pods as AWS manages all permissions automatically.

💡 Hint

Consider what role allows Fargate to pull container images and run pods securely.

Fargate requires a pod execution role with the AmazonEKSFargatePodExecutionRolePolicy to allow pulling images and running pods securely.

❓ service_behavior

expert

Behavior of Node Groups During Cluster Scaling

In an EKS cluster with both managed node groups and Fargate profiles, what happens when the cluster scales up to handle increased pod demand?

A Managed node groups automatically add EC2 instances based on the node group's autoscaling settings, while Fargate automatically launches more pods without managing servers.

B Both managed node groups and Fargate require manual addition of resources to scale pods.

C Fargate scales EC2 instances automatically, but managed node groups require manual scaling.

D Managed node groups scale pods automatically, but Fargate requires manual pod scaling.

💡 Hint

Think about how each node group type handles scaling differently.

Managed node groups use EC2 autoscaling groups to add or remove instances automatically. Fargate runs pods on demand without managing servers, scaling pods automatically.