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.

Practice

1. Which type of node group in AWS EKS automatically manages the worker nodes for you?

easy

A. On-premises node group

B. Managed node group

C. Fargate

D. Self-managed node group

Solution

1. Step 1: Understand node group types in EKS

   Managed node groups are designed to let AWS handle the worker nodes, including updates and scaling.

2. Step 2: Compare with other node groups

   Self-managed node groups require manual management of EC2 instances, and Fargate runs containers without servers.

3. Final Answer:

   Managed node group -> Option B

4. Quick Check:

   Managed node group = automatic worker node management [OK]

Hint: Managed node groups mean AWS manages nodes for you [OK]

Common Mistakes:

• Confusing self-managed with managed node groups
• Thinking Fargate manages EC2 instances
• Assuming on-premises node groups are managed by AWS

2. Which of the following is the correct way to specify a Fargate profile in AWS EKS configuration?

easy

A. Specify EC2 instance types under node group

B. Set up Auto Scaling group manually

C. Define selectors with namespaces and labels for Fargate profile

D. Create a launch configuration for EC2

Solution

1. Step 1: Recall Fargate profile setup

   Fargate profiles use selectors to match pods by namespace and labels to run on Fargate.

2. Step 2: Eliminate incorrect options

   EC2 instance types, Auto Scaling groups, and launch configurations relate to EC2, not Fargate.

3. Final Answer:

   Define selectors with namespaces and labels for Fargate profile -> Option C

4. Quick Check:

   Fargate profile uses selectors = Define selectors with namespaces and labels for Fargate profile [OK]

Hint: Fargate profiles use selectors, not EC2 settings [OK]

Common Mistakes:

• Trying to specify EC2 instance types for Fargate
• Confusing Auto Scaling with Fargate profiles
• Using launch configurations for Fargate

3. Given the following EKS setup, which node group type will run the pod?

apiVersion: v1
kind: Pod
metadata:
  name: myapp
  namespace: production
spec:
  containers:
  - name: app
    image: myapp:latest

Assuming a Fargate profile exists for namespace 'production' and a managed node group is also present.

medium

A. Managed node group

B. Self-managed node group

C. No node group will run the pod

D. Fargate

Solution

1. Step 1: Check pod namespace against Fargate profile

   The pod is in 'production' namespace, which matches the Fargate profile selector.

2. Step 2: Understand pod scheduling priority

   Pods matching Fargate profiles run on Fargate instead of node groups.

3. Final Answer:

   Fargate -> Option D

4. Quick Check:

   Pod in Fargate profile namespace runs on Fargate [OK]

Hint: Pod namespace matching Fargate profile means Fargate runs it [OK]

Common Mistakes:

• Assuming managed node group runs all pods
• Ignoring Fargate profile selectors
• Thinking self-managed node group runs pods by default

4. You created a self-managed node group but your pods are stuck in Pending state. What is a likely cause?

medium

A. EC2 instances in the node group are not registered with the cluster

B. Fargate profile is missing

C. Managed node group is not enabled

D. Pod namespace does not match Fargate profile

Solution

1. Step 1: Understand self-managed node group requirements

   Self-managed nodes must register with the cluster to run pods.

2. Step 2: Identify cause of Pending pods

   If EC2 instances are not registered, pods cannot schedule and remain Pending.

3. Final Answer:

   EC2 instances in the node group are not registered with the cluster -> Option A

4. Quick Check:

   Unregistered EC2 nodes cause Pending pods [OK]

Hint: Self-managed nodes must register to run pods [OK]

Common Mistakes:

• Assuming Fargate profile affects self-managed nodes
• Thinking managed node group must be enabled for self-managed nodes
• Ignoring node registration status

5. You want to run a highly scalable application without managing any servers. Which AWS EKS node group option should you choose and why?

hard

A. Fargate, because it runs containers without managing servers

B. Managed node group, because AWS handles node updates automatically

C. Self-managed node group, because you control EC2 instances directly

D. On-premises nodes, because they offer full control

Solution

1. Step 1: Identify requirement for no server management

   The question asks for running containers without managing servers.

2. Step 2: Compare node group options

   Self-managed and managed node groups require managing or at least maintaining EC2 instances. Fargate runs containers serverless.

3. Step 3: Confirm scalability and management

   Fargate automatically scales and removes server management burden.

4. Final Answer:

   Fargate, because it runs containers without managing servers -> Option A

5. Quick Check:

   No server management means Fargate [OK]

Hint: No servers to manage? Choose Fargate [OK]

Common Mistakes:

• Choosing self-managed for no server management
• Confusing managed node groups with serverless
• Selecting on-premises nodes for cloud scalability