Exam AWS Certified Solutions Architect - Associate SAA-C02 topic 1 question 372 discussion

C. Use Amazon S3 static website hosting to store and serve the front end. Use Amazon API Gateway and AWS Lambda functions for the application layer. Use Amazon DynamoDB to store user data. Not 100% sure

Answer is C. Microservice does not always means "container". It can be realized by several methods one of which is API gateway + Lambda. https://docs.aws.amazon.com/whitepapers/latest/microservices-on-aws/microservices-on-aws.html B could be the answer, if Fargate is there not EKS. EKS is not serverless, so can't minimize operational costs.

C is the answer

S3+API GATEWAY+LAMBDA

CCCCCCCCCCCCC

API Gateway will win against EKS for sure. " Amazon API Gateway addresses those challenges and reduces the operational complexity of creating and maintaining RESTful APIs. API Gateway allows you to create your APIs programmatically by importing Swagger definitions, using either the AWS API or the AWS Management Console. API Gateway serves as a front door to any web application running on Amazon EC2, Amazon ECS, AWS Lambda, or in any on-premises environment. Basically, API Gateway allows you to run APIs without having to manage servers." https://docs.aws.amazon.com/whitepapers/latest/microservices-on-aws/api-implementation.html End of story: https://docs.aws.amazon.com/whitepapers/latest/microservices-on-aws/serverless-microservices.html

API Gateway will win against EKS for sure. " Amazon API Gateway addresses those challenges and reduces the operational complexity of creating and maintaining RESTful APIs. API Gateway allows you to create your APIs programmatically by importing Swagger definitions, using either the AWS API or the AWS Management Console. API Gateway serves as a front door to any web application running on Amazon EC2, Amazon ECS, AWS Lambda, or in any on-premises environment. Basically, API Gateway allows you to run APIs without having to manage servers." https://docs.aws.amazon.com/whitepapers/latest/microservices-on-aws/api-implementation.html

JSON and Lambda is a pair...

Agreed with C.

Keys: --> 3 tier application --> Front end is static --> MicroServices being used to store data in DB in json format. Expectation: Min operational overhead + auto scale Distractors: A/B/D A is a distractor as it talks about Elastic Beanstalk, though it is an amazing PaaS service it would use EC2 instances which might lead to some downtime in scaling out also need to keep an eye over instance size to handle the traffic. B is distractor because again an operational overhead in managing the task definition/tasks D because it uses RDS which does not auto scale and we are talking about JSON documents to be stored B satisfies all as S3 is great for hosting static content, API gateway comes with fully managed auto scaling capability, lambda is a serverless compute service with massive scaling capacity to serve the requests, same for DynamoDB

json => dynamoDB minimal operational overhead expenditures => lambda & API gateway instead of Beanstalk or EKS so C is the correct answer

C. Use Amazon S3 static website hosting to store and serve the front end. Use Amazon API Gateway and AWS Lambda functions for the application layer. Use Amazon DynamoDB to store user data. - "JSON documents..." --> key-value store --> DynamoDB --> RDS (D) is wrong - "Microservices" + "operational overhead expenditures must be kept to a minimum" --> favour serverless frameworks --> Beanstalk (A) is wrong - EKS (B), if on Fargate, might be correct --> https://aws.amazon.com/about-aws/whats-new/2019/12/run-serverless-kubernetes-pods-using-amazon-eks-and-aws-fargate/

C . --> S3 is best for "Static Data", API Gateway + Lambda is best for "Microservices", DynamoDB is best for "JSON format".... All the three are less operational/maintenance since serverless.

Microservice: https://aws.amazon.com/microservices/ Essentially, Microservice implies dividing an application into smaller scalable components.These communicate via APIs. AWS offers Containers and Lambda as 2 ways to achieve this goal. ============= Note that between RDS and Dynamo DB, Dynamo DB suits as it is serverless(minimal cost) and JSOn is more like semi structured data(RDS would be fit for structured data). So,D eliminated. A is not a good fit because Elastic Beanstalk is for Developers to do deployments without thinking too much about infrastrucutre. It may include EC2s or serverless both. Between B and C,both support autoscaling and EKS has 2 launch modes,EC2 and Fargate (serverless). Perhaps C over B just because Lambda is AWS native?

answer should be CCCCC https://docs.aws.amazon.com/whitepapers/latest/microservices-on-aws/serverless-microservices.html

this link will describe how to build serverless microservices. https://docs.aws.amazon.com/whitepapers/latest/microservices-on-aws/serverless-microservices.html This means you can build microservice without ecs for minimizing operational overhead. So the answer is C

we can rule out option D straight away as it needs some operational overhead A , B , C are the services which do not have any operational overhead and the trick here is choosing the cheapest so C is the cheapest one compared to the Bean stalk and Kubernetes