Exam AWS Certified Solutions Architect - Professional SAP-C02 All Questions

View all questions & answers for the AWS Certified Solutions Architect - Professional SAP-C02 exam

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

Exam question from Amazon's AWS Certified Solutions Architect - Professional SAP-C02

Question #: 127
Topic #: 1

[All AWS Certified Solutions Architect - Professional SAP-C02 Questions]

A delivery company needs to migrate its third-party route planning application to AWS. The third party supplies a supported Docker image from a public registry. The image can run in as many containers as required to generate the route map.

The company has divided the delivery area into sections with supply hubs so that delivery drivers travel the shortest distance possible from the hubs to the customers. To reduce the time necessary to generate route maps, each section uses its own set of Docker containers with a custom configuration that processes orders only in the section's area.

The company needs the ability to allocate resources cost-effectively based on the number of running containers.

Which solution will meet these requirements with the LEAST operational overhead?

A. Create an Amazon Elastic Kubernetes Service (Amazon EKS) cluster on Amazon EC2. Use the Amazon EKS CLI to launch the planning application in pods by using the --tags option to assign a custom tag to the pod.
B. Create an Amazon Elastic Kubernetes Service (Amazon EKS) cluster on AWS Fargate. Use the Amazon EKS CLI to launch the planning application. Use the AWS CLI tag-resource API call to assign a custom tag to the pod.
C. Create an Amazon Elastic Container Service (Amazon ECS) cluster on Amazon EC2. Use the AWS CLI with run-tasks set to true to launch the planning application by using the --tags option to assign a custom tag to the task.
D. Create an Amazon Elastic Container Service (Amazon ECS) cluster on AWS Fargate. Use the AWS CLI run-task command and set enableECSManagedTags to true to launch the planning application. Use the --tags option to assign a custom tag to the task.

Show Suggested Answer

Suggested Answer: D 🗳️

by zhangyu20000 at Jan. 16, 2023, 2:36 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

dev112233xx

Highly Voted 2 years, 4 months ago

Selected Answer: D

D is the correct answer, When you use the APIs to create a service or run a task, you must set enableECSManagedTags to true for run-task and create-service. (see link below) B doesn't make sense because EKS is more for complex orchestrated microservices apps, i don't think it needed in such scenario https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-using-tags.html

upvoted 16 times

Jay_2pt0_1

1 year, 9 months ago

Stepped through that same thought process

upvoted 1 times

...

God_Is_Love

Highly Voted 2 years, 5 months ago

Selected Answer: D

EKS with Fargate is a more complex platform than ECS with Fargate. Kubernetes has a steeper learning curve than ECS, and requires more expertise to manage. ECS with Fargate is designed to be simple and easy to use, making it a good choice for organizations that want to quickly deploy containerized applications without having to manage the complexity of Kubernetes.

upvoted 6 times

...

princajen

Most Recent 2 weeks ago

Selected Answer: D

ECS on Fargate is the best fit here because the company wants cost-effective scaling based on the number of containers and least operational overhead. Fargate removes the need to manage EC2 infrastructure, and ECS is easier to work with than EKS unless you're running a complex Kubernetes-based microservices platform. Also, tagging is natively supported in ECS Fargate tasks using the --tags option along with --enable-ecs-managed-tags, which is perfect for cost allocation per delivery section. In contrast, tagging pods directly in EKS via CLI is not straightforward, and managing Kubernetes adds unnecessary complexity for this use case.

upvoted 1 times

...

0dc6cac

2 months ago

Selected Answer: D

it's D, people who pick B have never worked with EKS in a prod environment :-/

upvoted 1 times

...

altonh

7 months ago

Selected Answer: D

For option B, how do you tag a POD using AWS CLI?

upvoted 1 times

...

amministrazione

11 months, 2 weeks ago

D. Create an Amazon Elastic Container Service (Amazon ECS) cluster on AWS Fargate. Use the AWS CLI run-task command and set enableECSManagedTags to true to launch the planning application. Use the --tags option to assign a custom tag to the task.

upvoted 1 times

...

ninomfr64

1 year, 7 months ago

Selected Answer: D

A and B = between EKS and ECS if K8s is not required I go for ECS C = between EC2 and Fargate if nothing points you clearly to Ec2 i would go for Fargate (less overhead, could cost less) D = correct

upvoted 3 times

...

ele

1 year, 7 months ago

Selected Answer: B

D is a trap, even if it's tempting, but '--tags ' is not a valid option for tagging ecs tasks/services. B is the right answer.

upvoted 1 times

helloworldabc

11 months, 3 weeks ago

just D

upvoted 1 times

...

cox1960

1 year, 7 months ago

--tags is valid https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/run-task.html

upvoted 1 times

cox1960

1 year, 7 months ago

but --enable-ecs-managed-tags is the right option instead of "`enableECSManagedTags` to `true`"

upvoted 1 times

...

career360guru

1 year, 7 months ago

Selected Answer: D

D is best option with least operational overhead.

upvoted 3 times

...

atirado

1 year, 8 months ago

Selected Answer: D

Options A and C are more operationally complex than B and D because you will need to manage the EC2 instances and underpin the EKS cluster and the ECS service definition. And as if to make the selection easier, B and D explicitly mention using AWS Fargate in a way that works. Selecting between Options B and D boils down the interpretation of “each section uses its own set of Docker containers with a custom configuration that processes orders only in the section's area”. The only indication in the question that kind of helps is "The third party supplies a supported Docker image from a public registry": The custom configuration is just for processing orders in the section's area rather something in the docker image itself.

upvoted 2 times

...

n_d1

1 year, 11 months ago

Selected Answer: D

As per the Amazon EKS documentation, the following EKS resources support tags: - clusters - managed node groups - Fargate profiles I think that rules out B in favour of D! https://docs.aws.amazon.com/eks/latest/userguide/eks-using-tags.html#tag-resources

upvoted 3 times

...

Ganshank

1 year, 12 months ago

Real-world answer - B. Certification answer - D.

upvoted 5 times

...

NikkyDicky

2 years, 1 month ago

Selected Answer: D

going with D

upvoted 2 times

...

rbm2023

2 years, 3 months ago

Selected Answer: D

Since the question where the requirement is the least operational overhead and we are between EKS and ECS, I would go for ECS, I believe EKS has more operational overhead for deploying and for operating. Also, you would probably have to apply less steps to build this structure using ECS when comparing with EKS.

upvoted 4 times

...

iamunstopable

2 years, 3 months ago

B is correct Anytime you need Docker containers with a custom configuration use EKS

upvoted 2 times

...

Jay_2pt0_1

2 years, 4 months ago

Selected Answer: B

Like many have already stated, the debate is between B and D. I think B is the answer as "each section uses its own set of DOcker Containers with a customer configuration, " which leads me to believe that EKS orchestration is worthwhile in terms of operational overhead.

upvoted 3 times

...

mfsec

2 years, 4 months ago

Selected Answer: D

D is easier

upvoted 2 times

...

Load full discussion...