Fargate vs EC2 launch type in AWS - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding AWS Fargate vs EC2 Launch Type

Which statement correctly describes a key difference between AWS Fargate and EC2 launch types for running containers?

A Fargate requires you to manage the underlying EC2 instances, while EC2 launch type abstracts instance management.

B EC2 launch type requires you to manage the underlying EC2 instances, while Fargate abstracts instance management.

C Both Fargate and EC2 launch types require manual scaling of EC2 instances.

D Fargate launch type only supports Windows containers, while EC2 supports Linux containers.

💡 Hint

Think about who manages the servers in each launch type.

Fargate lets you run containers without managing servers. EC2 launch type requires you to manage the EC2 instances yourself.

❓ Architecture

intermediate

Choosing Launch Type for Cost Optimization

You want to run a containerized application with predictable steady traffic and want to optimize costs by using reserved capacity. Which launch type should you choose?

A Use EC2 launch type to leverage reserved EC2 instances for cost savings.

B Use Fargate launch type because it automatically uses reserved instances.

C Use Fargate launch type because it supports reserved EC2 capacity.

D Use EC2 launch type because Fargate does not support container orchestration.

💡 Hint

Reserved capacity applies to EC2 instances, not serverless services.

Reserved EC2 instances reduce cost when you manage your own EC2 instances. Fargate is serverless and does not use reserved instances.

❓ service_behavior

advanced

Behavior of Auto Scaling with Fargate vs EC2

Which statement best describes how auto scaling works differently between Fargate and EC2 launch types?

A Fargate auto scaling adjusts the number of running tasks without managing instances; EC2 auto scaling adjusts the number of EC2 instances.

B Both Fargate and EC2 auto scaling adjust the number of EC2 instances only.

C Fargate auto scaling requires manual scaling of EC2 instances; EC2 auto scaling automatically scales tasks.

D Auto scaling is not supported with Fargate launch type.

💡 Hint

Consider what resources each launch type manages.

Fargate scales tasks directly since it manages infrastructure. EC2 launch type requires scaling EC2 instances to support tasks.

❓ security

advanced

Security Responsibility Differences

Which security responsibility is unique to the EC2 launch type compared to Fargate?

A Encrypting data in transit between containers.

B Configuring security groups for tasks.

C Managing container image vulnerabilities.

D Patching and securing the underlying EC2 instances.

💡 Hint

Think about who controls the servers in each launch type.

With EC2 launch type, you must patch and secure the EC2 instances. Fargate abstracts this responsibility.

✅ Best Practice

expert

Best Practice for Hybrid Use of Fargate and EC2 Launch Types

You have a mixed workload: some tasks require custom AMIs and others benefit from serverless management. What is the best practice for using both Fargate and EC2 launch types in the same ECS cluster?

A Use only EC2 launch type and simulate serverless behavior with custom scripts.

B Create separate ECS clusters for Fargate and EC2 launch types to avoid conflicts.

C Use a single ECS cluster with both launch types and assign tasks to appropriate launch types as needed.

D Use only Fargate launch type and avoid EC2 launch type for simplicity.

💡 Hint

Consider ECS cluster flexibility and task placement.

ECS supports running both Fargate and EC2 launch types in the same cluster, allowing flexible task placement.

Practice

1. What is the main difference between AWS Fargate and EC2 launch types for running containers?

easy

A. Fargate runs containers without managing servers, EC2 requires managing servers.

B. Fargate requires managing servers, EC2 runs containers without servers.

C. Both require managing servers but use different operating systems.

D. Both run containers without any server management.

Solution

1. Step 1: Understand Fargate's server management

   Fargate abstracts server management, so you don't handle servers directly.

2. Step 2: Understand EC2 launch type server management

   EC2 launch type requires you to manage the servers where containers run.

3. Final Answer:

   Fargate runs containers without managing servers, EC2 requires managing servers. -> Option A

4. Quick Check:

   Server management difference = D [OK]

Hint: Fargate = no servers to manage, EC2 = you manage servers [OK]

Common Mistakes:

• Confusing which launch type manages servers
• Thinking both require server management
• Assuming Fargate needs server setup

2. Which of the following is the correct way to specify the launch type as Fargate in an ECS service JSON?

easy

A. "launchType": "EC2"

B. "launchType": "FARGATE"

C. "launchType": "Serverless"

D. "launchType": "Container"

Solution

1. Step 1: Check valid launch type values in ECS

   ECS supports "EC2" and "FARGATE" as launch type values in uppercase.

2. Step 2: Identify correct Fargate syntax

   The correct string for Fargate is "FARGATE" in uppercase letters.

3. Final Answer:

   "launchType": "FARGATE" -> Option B

4. Quick Check:

   Fargate launch type syntax = A [OK]

Hint: Use uppercase "FARGATE" for launchType in ECS JSON [OK]

Common Mistakes:

• Using lowercase "fargate" instead of uppercase
• Using invalid launch type names like "Serverless"
• Confusing EC2 and Fargate strings

3. Given this ECS service configuration snippet, what launch type will it use?

{
  "launchType": "EC2",
  "taskDefinition": "my-task-def"
}

medium

A. It will run containers on EC2 instances you manage.

B. It will run containers on AWS Fargate without server management.

C. It will fail because "EC2" is not a valid launch type.

D. It will run containers on Lambda functions.

Solution

1. Step 1: Read the launchType value

   The launchType is set to "EC2" which means containers run on EC2 instances.

2. Step 2: Understand EC2 launch type behavior

   EC2 launch type requires you to manage the servers where containers run.

3. Final Answer:

   It will run containers on EC2 instances you manage. -> Option A

4. Quick Check:

   launchType "EC2" means managed servers = A [OK]

Hint: launchType "EC2" means you manage servers [OK]

Common Mistakes:

• Thinking "EC2" means serverless
• Assuming "EC2" is invalid syntax
• Confusing EC2 with Lambda

4. You tried to deploy an ECS task with this launch type: "launchType": "fargate" but got an error. What is the likely cause?

medium

A. Fargate launch type is not supported in ECS.

B. The launch type should be a boolean, not a string.

C. You must specify the launch type as "EC2" for tasks.

D. The launch type value is case-sensitive and must be uppercase "FARGATE".

Solution

1. Step 1: Check launch type case sensitivity

   ECS launch type values are case-sensitive and require uppercase strings like "FARGATE".

2. Step 2: Identify error cause

   Using lowercase "fargate" causes a validation error because it's invalid syntax.

3. Final Answer:

   The launch type value is case-sensitive and must be uppercase "FARGATE". -> Option D

4. Quick Check:

   Case-sensitive launchType = B [OK]

Hint: Use uppercase "FARGATE" to avoid launch type errors [OK]

Common Mistakes:

• Using lowercase launch type values
• Thinking Fargate is unsupported
• Confusing data types for launchType

5. You want to run a containerized app with minimal server management and automatic scaling. Which launch type should you choose and why?

hard

A. EC2 launch type, because it gives full control over servers and scaling.

B. EC2 launch type, because it is cheaper and requires no scaling setup.

C. Fargate launch type, because it removes server management and handles scaling automatically.

D. Fargate launch type, because it requires manual server setup but better performance.

Solution

1. Step 1: Identify launch type for minimal server management

   Fargate removes the need to manage servers, unlike EC2 which requires server control.

2. Step 2: Consider automatic scaling capabilities

   Fargate automatically scales containers based on demand without manual server scaling.

3. Final Answer:

   Fargate launch type, because it removes server management and handles scaling automatically. -> Option C

4. Quick Check:

   Minimal management + auto scaling = Fargate = C [OK]

Hint: Choose Fargate for no servers and auto scaling [OK]

Common Mistakes:

• Choosing EC2 for minimal management
• Assuming EC2 auto scales automatically
• Thinking Fargate needs manual server setup