Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 7 discussion

B. Upload the container images to Amazon Elastic Container Registry (Amazon ECR). Configure two auto scaled Amazon Elastic Container Service (Amazon ECS) clusters with the Fargate launch type to handle the expected load. Deploy tasks from the ECR images. Configure two separate Application Load Balancers to direct traffic to the ECS clusters. This option meets the requirement of using a serverless architecture by utilizing the Fargate launch type for the ECS clusters, which allows for automatic scaling of the containers based on the expected load. It also allows for separate deployments for production and testing by configuring separate ECS clusters and Application Load Balancers for each environment. This option also minimizes operational complexity by utilizing ECS and Fargate for the container orchestration and scaling.

Answer is A. ABC all works but A is most COST EFFECTIVE

Option A is the most cost-effective and best meets the requirements because: It uses AWS Lambda with container images, providing a fully serverless architecture for microservices. API Gateway routes requests to separate production and testing Lambda functions, ensuring distinct environments.

"To create a Lambda function from a container image, build your image locally and upload it to an Amazon Elastic Container Registry (Amazon ECR) repository." https://docs.aws.amazon.com/lambda/latest/dg/images-create.html Thus A is not correct so must be B

The Point is in the question:The company needs to refactor the application as microservices that run on containers. sure A

🧠 Why A is correct for SAP-C02: Lambda does support container images up to 10 GB → This is official AWS functionality: https://docs.aws.amazon.com/lambda/latest/dg/images-create.html You don’t need ECS or ECR (explicitly) in the answer → AWS Lambda can pull container images from Amazon ECR, which is implied. The exam doesn't test whether the image is in ECR — only that you can deploy containers to Lambda, which is true. “Most cost-effective” and “serverless” are the key exam keywords → Lambda has zero idle cost, no infra to manage, and automatic scaling → ECS/EKS/Fargate introduce ALBs, networking, cluster logic = more cost and complexity You can run web apps in Lambda → Especially with API Gateway in front → Even frameworks like ASP.NET Core can run with slight adaptation

Appropriate answer is B

While both A and B are valid real-world solutions, A is more aligned with: Cost-effectiveness Simplicity AWS exam preference for serverless-first solutions Container support with Lambda

AWS Lambda now supports container images (up to 10 GB), so you can package your microservices as containers and run them serverlessly. As per the needs in the question, it tickets the boxes of low operational complexity and low cost. However there is one catch. Lambda can be used only for runtimes <=15 min. So if the containerised applications need to run > 15min per invocation, then option B. Since the questions doesn't specifically talk about any timing, i would stick with A

A is definitely no for hosting web applications, web applications typically make multiple HTTP requests where stick session are required which is not supported by API Gateway. So B looks perfect

I think it's A, you can upload docker images to lambda, and it's serverless. I don't think ECS can count as serverless in this case.

looks like now since 2020 lambda support container images https://aws.amazon.com/blogs/aws/new-for-aws-lambda-container-image-support/?utm_source=chatgpt.com

https://docs.aws.amazon.com/lambda/latest/dg/images-create.html

most cost-effective and lest operational overhead

I was initially torn between A and B, but answer A says to upload the container image to Lambda, which isn't possible - to use a container with Lambda, you still upload the image to ECR. Answer D (Beanstalk) isn't the most cost-effective for running containers. So between B and C (ECS vs EKS), ECS has less operational overhead, and also doesn't require the master node to be running, which means ECS will likely be very slightly cheaper, and have less operational work.

At the time I consider B & C without doubt. But finally consider to migration efforts, I choose B. I don't really consider the cost between B & C.

AWS Fargate launch type for Amazon ECS is indeed a pay-per-use model. With Fargate, you pay for the amount of vCPU and memory resources that your containerized application requests. The billing is based on the resources used from the time your container images are pulled until the Amazon ECS task terminates, rounded up to the nearest second, with a minimum charge of one minute12. This model allows you to focus on building and managing your applications without worrying about managing the underlying infrastructure, making it a convenient and scalable option for many use cases. See: https://aws.amazon.com/ecs/pricing/