A financial technology enterprise, PayGlide, is migrating its legacy payment processing workload from on-premises virtualization hosts to AWS. The workload consists of multiple critical microservices that must be modernized using containers. The enterprise requires a fully managed serverless container platform to eliminate the operational overhead of managing underlying container hosts. The new architecture must span multiple Availability Zones to ensure high availability, and it must have resilient outbound internet access to communicate with external payment gateways. Furthermore, these microservices must resolve the internal DNS names of shared services hosted in a separate shared services VPC within their organization. Which of the following networking and container configurations meets these requirements with the least operational overhead?
- ADeploy the microservices on Amazon ECS using the AWS Fargate launch type with the `awsvpc` network mode. Deploy a single NAT Gateway in a single public subnet to route outbound traffic for all workload private subnets. Associate the Route 53 Private Hosted Zone of the shared services VPC with the workload VPC.
- BDeploy the microservices on Amazon ECS using the AWS Fargate launch type with the `bridge` network mode to share the host's network namespace. Deploy redundant NAT Gateways across multiple Availability Zones in the public subnets of the workload VPC. Associate the Route 53 Private Hosted Zone of the shared services VPC with the workload VPC.
- Deploy the microservices on Amazon ECS using the AWS Fargate launch type with the `awsvpc` network mode. Deploy redundant NAT Gateways across multiple Availability Zones in the public subnets of the workload VPC. Associate the Route 53 Private Hosted Zone of the shared services VPC with the workload VPC.Cevap
- DDeploy the microservices on Amazon ECS using the AWS Fargate launch type with the `awsvpc` network mode. Deploy redundant NAT Gateways across multiple Availability Zones in the public subnets of the workload VPC. Route all DNS traffic from the workload VPC to the shared services VPC via an AWS Transit Gateway without associating the Route 53 Private Hosted Zone to the workload VPC.