Exam AWS Certified Solutions Architect - Associate SAA-C02 All Questions

View all questions & answers for the AWS Certified Solutions Architect - Associate SAA-C02 exam

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

Exam question from Amazon's AWS Certified Solutions Architect - Associate SAA-C02

Question #: 372
Topic #: 1

[All AWS Certified Solutions Architect - Associate SAA-C02 Questions]

A recently created startup built a three-tier web application. The front end has static content. The application layer is based on microservices. User data is stored as JSON documents that need to be accessed with low latency. The company expects regular traffic to be low during the first year, with peaks in traffic when it publicizes new features every month. The startup team needs to minimize operational overhead costs.
What should a solutions architect recommend to accomplish this?

A. Use Amazon S3 static website hosting to store and serve the front end. Use AWS Elastic Beanstalk for the application layer. Use Amazon DynamoDB to store user data.
B. Use Amazon S3 static website hosting to store and serve the front end. Use Amazon Elastic KubernetesService (Amazon EKS) for the application layer. Use Amazon DynamoDB to store user data.
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.
D. 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 RDS with read replicas to store user data.

Show Suggested Answer

Suggested Answer: C 🗳️

by dmscountera at March 11, 2021, 6:03 p.m.

Disclaimers:

- ExamTopics website is not related to, affiliated with, endorsed or authorized by Amazon.
- Trademarks, certification & product names are used for reference only and belong to Amazon.

Comments

Submit Cancel

dmscountera

Highly Voted 3 years, 9 months ago

upvoted 43 times

haaris786

3 years, 9 months ago

C makes more sense to me.

upvoted 5 times

...

noahsark

3 years, 8 months ago

https://docs.aws.amazon.com/lambda/latest/dg/services-apigateway-blueprint.html

upvoted 2 times

...

swadeey

3 years, 8 months ago

But question says "The application layer is based on microservices."

upvoted 5 times

youthanasia

3 years, 7 months ago

Check this link; https://docs.aws.amazon.com/lambda/latest/dg/services-apigateway-blueprint.html

upvoted 3 times

...

eBooKz

3 years, 2 months ago

Because user data is stored as document in JSON format a simple key-value datastore meets the need. That's where DynamoDB comes is your guy!

upvoted 2 times

...

Load full discussion...

...

Jade_Moon

Highly Voted 3 years, 9 months ago

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.

upvoted 28 times

theCreatorSD

3 years, 8 months ago

What if application layer job takes more than 15 mins?

upvoted 6 times

derekurizar

3 years, 1 month ago

If a website takes more than 15 minutes to respond, something is wrong with your backend lol

upvoted 4 times

...

reliquary

3 years, 9 months ago

AWS has integrated building blocks that support the development of microservices. Two popular approaches are using AWS Lambda and Docker containers with AWS Fargate. https://docs.aws.amazon.com/whitepapers/latest/microservices-on-aws/microservices.html

upvoted 1 times

...

Samantha23

3 years, 8 months ago

EKS can use Fargate https://aws.amazon.com/about-aws/whats-new/2019/12/run-serverless-kubernetes-pods-using-amazon-eks-and-aws-fargate/

upvoted 2 times

...

gargaditya

3 years, 7 months ago

I disagree,EKS ,like ECS offers 2 launch modes- EC2 and Fargate. So it can be server based or serverless.

upvoted 1 times

...

BECAUSE

Most Recent 2 years, 1 month ago

Selected Answer: C

C is the answer

upvoted 1 times

...

queen101

2 years, 11 months ago

S3+API GATEWAY+LAMBDA

upvoted 1 times

...

marklovesaws143

2 years, 11 months ago

Selected Answer: C

CCCCCCCCCCCCC

upvoted 1 times

...

future77

2 years, 12 months ago

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

upvoted 2 times

...

future77

2 years, 12 months ago

upvoted 1 times

...

slcheng

2 years, 12 months ago

Selected Answer: C

JSON and Lambda is a pair...

upvoted 1 times

...

slcheng

3 years ago

Selected Answer: C

Agreed with C.

upvoted 2 times

...

Arshadul

3 years, 1 month ago

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

upvoted 5 times

...

saifeddine92

3 years, 4 months ago

Selected Answer: C

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

upvoted 5 times

...

weilun_tann

3 years, 6 months ago

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/

upvoted 2 times

...

Vijay1986

3 years, 7 months ago

Selected Answer: C

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.

upvoted 2 times

...

gargaditya

3 years, 7 months ago

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?

upvoted 2 times

...

Nkd

3 years, 8 months ago

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

upvoted 4 times

...

Afsal_K_R

3 years, 8 months ago

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

upvoted 1 times

...

Manumj

3 years, 8 months ago

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

upvoted 2 times

...

Load full discussion...