Examkin

Question

Difficulty: MediumModernizing Workloads using Containers (ECS and EKS)

Aether Grid Solutions is modernizing its on-premises grid simulation engine by migrating the workload to Amazon ECS. The application consists of several high-performance containerized microservices that must bind directly to the host's network interface to bypass Docker network virtualization layers, minimize latency, and handle UDP broadcast traffic. The architecture must be highly available and deployed across multiple Availability Zones. To download external simulation datasets, the containers require outbound internet connectivity. The network security team mandates that this outbound path must not have any single points of failure. The infrastructure team wants to minimize the operational overhead associated with operating system patching and server provisioning where possible.

Which architectural design should the solutions architect recommend to satisfy these requirements?

  1. A
    Deploy the tasks using the AWS Fargate launch type with the host network mode, and provision a NAT Gateway in each Availability Zone.
  2. B
    Deploy the tasks using the Amazon ECS EC2 launch type with the host network mode, configure an Auto Scaling group using the Amazon ECS-optimized AMI, and provision a single NAT Gateway in one Availability Zone to handle outbound traffic for all subnets.
  3. Deploy the tasks using the Amazon ECS EC2 launch type with the host network mode, configure an Auto Scaling group using the Amazon ECS-optimized AMI, and provision a NAT Gateway in each Availability Zone.Answer
  4. D
    Deploy the tasks using the AWS Fargate launch type with the bridge network mode, and provision a NAT Gateway in each Availability Zone.

Answer

Deploy the tasks using the Amazon ECS EC2 launch type with the host network mode, configure an Auto Scaling group using the Amazon ECS-optimized AMI, and provision a NAT Gateway in each Availability Zone.
Deploying the containers on the Amazon ECS EC2 launch type using the host network mode allows the tasks to bind directly to the host's network interfaces, meeting the low-latency and UDP broadcast requirements. To minimize operational overhead, using an Auto Scaling group with the Amazon ECS-optimized AMI automates container instance management. Redundant NAT Gateways deployed across each Availability Zone ensure outbound connectivity is highly available without a single point of failure.

Step-by-Step Solution

1
Analyze the container networking requirements (direct host network interface binding and UDP broadcast support).
Identify that the host network mode is required, which is supported on Amazon ECS EC2 launch type but not on AWS Fargate.
AWS Fargate only supports the awsvpc network mode, which does not allow tasks to bind directly to the host network interface or support raw host-level networking behaviors like UDP broadcast.
2
Evaluate the high availability and outbound network connectivity requirements.
Determine that outbound internet access must be routed through redundant NAT Gateways in each Availability Zone.
A single NAT Gateway creates a single point of failure, violating the requirement for high availability and zero single points of failure in the outbound path.
3
Review the host management strategy to minimize operational overhead.
Implement an Auto Scaling group using the Amazon ECS-optimized AMI.
Using AWS-managed, container-optimized AMIs with Auto Scaling reduces the burden of manual OS patching and server provisioning.

Key Concept

Selecting the correct Amazon ECS launch type and network mode based on low-latency network performance and host-level binding constraints, combined with redundant network egress routing.
Estimated Time:2m 0s
Rate this question

Topics

Modernizing Workloads using Containers (ECS and EKS)

More questions from this topic