AWS Fargate is (strictly speaking) not a service

[fspiess]

Dear all,

I have one suggestion for a correction:

SAA-C02 Timed Mode Set 2, Question 13:

A new online banking platform has been re-designed to have a microservices architecture in which complex applications are decomposed into smaller, independent services. The new platform is using Docker considering that application containers are optimal for running small, decoupled services. The new solution should remove the need to provision and manage servers, let you specify and pay for resources per application, and improve security through application isolation by design.

Which of the following is the MOST suitable service to use to migrate this new platform to AWS?

Correct answer based on exam solution: Fargate.

My selection: EKS

My reasoning:

As an AWS technical trainer, I have observed it here and there that Fargate is considered a service, which strictly speaking is not true. It is a compute option (sometimes called “technology” or “compute engine”) for ECS and EKS. As the question asks for a _service_, in my opinion Fargate is not an option. In turn, Fargate does not have its own documentation page – it is placed underneath ECS:

https://docs.aws.amazon.com/AmazonECS/latest/userguide/what-is-fargate.html

Kind regards

Frank

[Tutorials-Dojo]

Hi Frank,

Thank you for sharing your opinion on this scenario. You are right; AWS Fargate is technically considered a technology rather than a full-pledge AWS service per se. It’s one of the compute options in ECS and EKS.

We have overhauled the scenario, and the change will be reflected in our practice exams soon. Thanks again and we wish you all the best in your upcoming AWS exam!

Cheers,

Jon Bonso