Node groups (managed, self-managed, Fargate) in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify a managed node group in an EKS cluster.

AWS

eks_cluster.add_nodegroup('[1]')

Drag options to blanks, or click blank then click option'

Amanaged

Bself_managed

Cfargate

Dlambda

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'self_managed' which requires manual management.

Choosing 'fargate' which is serverless, not a node group.

Choosing 'lambda' which is unrelated to node groups.

The managed node group is created and managed by AWS for EKS clusters.

2fill in blank

medium

Complete the code to create a self-managed node group using EC2 instances.

AWS

ec2.create_instances({ 'InstanceType': '[1]', 'MinCount': 1, 'MaxCount': 3 })

Drag options to blanks, or click blank then click option'

Alambda

Bfargate

Ct2.micro

Dmanaged

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'fargate' which is serverless and not an instance type.

Using 'managed' which is a node group type, not an instance type.

EC2 instance types like t2.micro are used for self-managed node groups.

3fill in blank

hard

Fix the error in the Fargate profile creation code by completing the missing field.

AWS

eks.create_fargate_profile(clusterName='myCluster', fargateProfileName='[1]', podExecutionRoleArn=role_arn, selectors=[{'namespace': 'default'}])

Drag options to blanks, or click blank then click option'

AselfManaged

BdefaultProfile

CmanagedNodeGroup

DlambdaProfile

Attempts:

3 left

💡 Hint

Common Mistakes

Using node group types as profile names.

Using unrelated terms like 'lambdaProfile'.

The Fargate profile name should be a descriptive string like defaultProfile.

4fill in blank

hard

Fill both blanks to define a managed node group with a specific instance type and desired capacity.

AWS

eks_cluster.add_nodegroup(instance_types=['[1]'], desired_capacity=[2])

Drag options to blanks, or click blank then click option'

At3.medium

B5

C3

Dt2.large

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid instance types.

Setting desired capacity to a string instead of a number.

The instance type t3.medium is valid and the desired capacity 3 sets the number of nodes.

5fill in blank

hard

Fill all three blanks to create a Fargate profile with a namespace selector and a profile name.

AWS

eks.create_fargate_profile(clusterName='myCluster', fargateProfileName='[1]', podExecutionRoleArn=role_arn, selectors=[{'namespace': '[2]'}], subnets=['[3]'])

Drag options to blanks, or click blank then click option'

AfargateProfile1

Bdefault

Csubnet-123abc

DmanagedNodeGroup

Attempts:

3 left

💡 Hint

Common Mistakes

Using node group types as profile names.

Using invalid subnet IDs.

Leaving namespace blank or incorrect.

The profile name fargateProfile1, namespace default, and subnet ID subnet-123abc are valid values for creating a Fargate profile.

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