Why container services matter on AWS - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the AWS service used to run containers.

AWS

service = "[1]"

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

AEC2

BLambda

CS3

DECS

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing EC2 which is for virtual machines, not container orchestration.

Selecting S3 which is for storage, not containers.

The correct service to run containers on AWS is ECS (Elastic Container Service).

2fill in blank

medium

Complete the code to define the container orchestration tool AWS offers.

AWS

orchestration_tool = "[1]"

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

AKubernetes

BEKS

CDocker

DLambda

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Docker which is a container platform but not AWS's orchestration service.

Selecting Lambda which is for serverless functions.

AWS offers EKS (Elastic Kubernetes Service) as its managed Kubernetes orchestration tool.

3fill in blank

hard

Fix the error in the code to correctly launch a container task on AWS.

AWS

task_definition = client.register_task_definition(family='my-task', containerDefinitions=[[1]])

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

A{'name': 'app', 'image': 'myimage'}

B{'container_name': 'app', 'image': 'myimage'}

C{'name': 'app', 'image_url': 'myimage'}

D{'name': 'app', 'img': 'myimage'}

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect keys like 'image_url' or 'img' instead of 'image'.

Naming the container key as 'container_name' instead of 'name'.

The container definition requires 'name' and 'image' keys exactly. 'image_url', 'container_name', or 'img' are incorrect keys.

4fill in blank

hard

Fill both blanks to create a dictionary that maps container names to their CPU shares and memory limits.

AWS

container_resources = { '[1]': [2] }

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

Aapp

B{'cpu': 256, 'memory': 512}

Cweb

D{'cpu': 1024, 'memory': 2048}

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong container name like 'web'.

Swapping CPU and memory values.

The container name is 'app' and the resource limits are CPU 256 units and 512 MB memory.

5fill in blank

hard

Fill all three blanks to define a service that runs 3 tasks of a container named 'api' with a load balancer.

AWS

service_config = {
  'serviceName': '[1]',
  'desiredCount': [2],
  'loadBalancers': [[3]]
}

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

Aapi-service

B3

C{'targetGroupArn': 'arn:aws:elasticloadbalancing:...', 'containerName': 'api', 'containerPort': 80}

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong service names or counts.

Incorrect load balancer dictionary format.

The service name is 'api-service', desired count is 3 tasks, and the load balancer configuration includes the target group ARN, container name, and port.

Practice

1. Why do container services matter on AWS?

easy

A. They require manual server management.

B. They replace all AWS storage services.

C. They only work with virtual machines.

D. They make deploying and scaling apps easier and faster.

Solution

1. Step 1: Understand container service purpose

   Container services help package apps and run them easily on AWS.

2. Step 2: Identify benefits on AWS

   They simplify deployment and scaling without manual server work.

3. Final Answer:

   They make deploying and scaling apps easier and faster. -> Option D

4. Quick Check:

   Container services simplify app deployment [OK]

Hint: Containers simplify app deployment and scaling [OK]

Common Mistakes:

• Thinking containers replace storage
• Believing containers need manual servers
• Confusing containers with virtual machines

2. Which AWS service lets you run containers without managing servers?

easy

A. AWS Fargate

B. Amazon EC2

C. Amazon S3

D. AWS Lambda

Solution

1. Step 1: Identify serverless container service

   AWS Fargate runs containers without you managing servers.

2. Step 2: Compare other services

   EC2 requires server management, S3 is storage, Lambda is for functions.

3. Final Answer:

   AWS Fargate -> Option A

4. Quick Check:

   Serverless container service = Fargate [OK]

Hint: Fargate runs containers serverless on AWS [OK]

Common Mistakes:

• Choosing EC2 which needs server setup
• Confusing S3 storage with containers
• Mixing Lambda functions with containers

3. What happens when you update a containerized app on AWS using container services?

medium

A. The app stops completely during update.

B. The app scales down to zero automatically.

C. The app updates with little or no downtime.

D. The app requires manual server reboot.

Solution

1. Step 1: Understand container update behavior

   Container services allow rolling updates to keep apps running.

2. Step 2: Identify downtime impact

   Updates happen with minimal or no downtime, improving user experience.

3. Final Answer:

   The app updates with little or no downtime. -> Option C

4. Quick Check:

   Container updates minimize downtime [OK]

Hint: Container updates avoid downtime on AWS [OK]

Common Mistakes:

• Assuming app stops fully during update
• Thinking manual reboot is needed
• Confusing scaling with updating

4. You tried to deploy a container on AWS Fargate but got an error. What is a common cause?

medium

A. You used an unsupported programming language.

B. You forgot to specify a container image.

C. You did not create an EC2 instance first.

D. You uploaded a file larger than 1GB.

Solution

1. Step 1: Check deployment requirements

   Fargate needs a container image to run your app.

2. Step 2: Identify common errors

   Missing container image causes deployment failure; EC2 not needed for Fargate.

3. Final Answer:

   You forgot to specify a container image. -> Option B

4. Quick Check:

   Missing container image causes error [OK]

Hint: Always specify container image for Fargate deployment [OK]

Common Mistakes:

• Thinking EC2 is required for Fargate
• Blaming programming language support
• Confusing file size limits with deployment errors

5. You want to run a web app that scales automatically and updates without downtime on AWS. Which setup is best?

hard

A. Use AWS Fargate with ECS to run containers managed by AWS.

B. Use AWS Lambda with container images for serverless functions.

C. Use EC2 instances with manual scaling and updates.

D. Use Amazon S3 to host the app files directly.

Solution

1. Step 1: Identify requirements

   The app needs automatic scaling and zero downtime updates.

2. Step 2: Match AWS services

   Fargate with ECS runs containers serverless, handles scaling and rolling updates.

3. Step 3: Eliminate other options

   EC2 needs manual work, Lambda is for functions not full apps, S3 is static storage.

4. Final Answer:

   Use AWS Fargate with ECS to run containers managed by AWS. -> Option A

5. Quick Check:

   Automatic scaling and updates = Fargate + ECS [OK]

Hint: Fargate + ECS = auto scale and zero downtime updates [OK]

Common Mistakes:

• Choosing EC2 for manual scaling
• Confusing Lambda with full app hosting
• Using S3 for dynamic web apps