Exam AWS Certified Developer Associate All Questions

View all questions & answers for the AWS Certified Developer Associate exam

Exam AWS Certified Developer Associate topic 1 question 72 discussion

Exam question from Amazon's AWS Certified Developer Associate

Question #: 72
Topic #: 1

[All AWS Certified Developer Associate Questions]

A microservices application is deployed across multiple containers in Amazon Elastic Container Service (Amazon ECS). To improve performance, a developer wants to capture trace information between the microservices and visualize the microservices architecture.
Which solution will meet these requirements?

A. Build the container from the amazon/aws-xray-daemon base image. Use the AWS X-Ray SDK to instrument the application.
B. Install the Amazon CloudWatch agent on the container image. Use the CloudWatch SDK to publish custom metrics from each of the microservices.
C. Install the AWS X-Ray daemon on each of the ECS instances.
D. Configure AWS CloudTrail data events to capture the traffic between the microservices.

Show Suggested Answer

Suggested Answer: A 🗳️

by reve666 at Dec. 29, 2021, 7:35 a.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

mcdirk

Highly Voted 3 years, 2 months ago

Selected Answer: A

A https://docs.aws.amazon.com/xray/latest/devguide/xray-daemon-ecs.html#xray-daemon-ecs-build you build the xray container along side the other ecs images deployed via the task definition. you then have to configure/ instrument the app to utilize the sdk for the rest

upvoted 8 times

suru003

2 years, 2 months ago

It's C. Question: A microservices application is **deployed** across multiple containers in Amazon Elastic Container Service (Amazon ECS). To improve performance, a developer wants to capture trace information.

upvoted 1 times

...

sumanshu

Most Recent 6 months, 2 weeks ago

Selected Answer: C

A) Eliminated - the X-Ray SDK does require changes to the application code to instrument it for tracing.

upvoted 1 times

sumanshu

5 months, 1 week ago

B) Eliminated - CloudWatch is good for metrics and logs but does not provide tracing or visualization of the interaction between microservices. D) Eliminated - It captures activity logs, not detailed traces or dependency diagrams of microservices.

upvoted 1 times

sumanshu

5 months, 1 week ago

C) - May be Correct (if EC2 Launch Type) - This method works for ECS on EC2 launch type, but for ECS Fargate, you cannot install the daemon on instances directly because Fargate does not provide access to the underlying infrastructure. This option is valid only in certain ECS configurations.

upvoted 1 times

sumanshu

5 months, 1 week ago

A) - May be Correct Then

upvoted 1 times

...

sumanshu

6 months, 2 weeks ago

Selected Answer: A

A) Correct C) Eliminated - While installing the X-Ray daemon directly on ECS instances works for EC2 launch types, this is not ideal for containerized workloads. The X-Ray daemon should run as a container in ECS tasks to properly trace individual services.

upvoted 1 times

sumanshu

6 months, 2 weeks ago

Sorry for wrong explanation... Correct C) - The X-Ray daemon collects trace data from the ECS tasks (containers) and sends it to the AWS X-Ray service. When you install the daemon on the ECS instances, you can still collect basic traces (e.g., HTTP calls and latency) without requiring application code changes. This approach works well for ECS tasks using the EC2 launch type. A ) Eliminated - the X-Ray SDK does require changes to the application code to instrument it for tracing.

upvoted 1 times

...

rcaliandro

2 years ago

Selected Answer: A

In order to integrate X-Ray to an ECS microservices application, we need to use the x-ray-demon image and use the X-Ray SDK. The A is the correct answer

upvoted 1 times

...

BATSIE

2 years, 2 months ago

ita option A , Option C is partially correct, but it only installs the AWS X-Ray daemon on each ECS instance. To capture trace information between microservices, you need to instrument your application using the AWS X-Ray SDK, as mentioned in option A.

upvoted 3 times

...

suru003

2 years, 2 months ago

Selected Answer: C

Since, the application is already deployed, A cannot be the case. I vote for C.

upvoted 1 times

...

MrTee

2 years, 2 months ago

Selected Answer: A

option A is the correct solution for capturing trace information and visualizing the microservices architecture in this scenario. Option C is incorrect because installing the AWS X-Ray daemon on each ECS instance will only collect trace information for services running on that specific instance. In a microservices architecture, services can be running on multiple instances and this approach would not capture the full picture of the architecture. Additionally, manually installing and configuring the X-Ray daemon on each instance can be time-consuming and error-prone

upvoted 2 times

...

MMaquis

2 years, 4 months ago

Selected Answer: A

Certainly A

upvoted 1 times

...

misgan

2 years, 5 months ago

I thought about A , but base image got me confused. On Documentation https://docs.aws.amazon.com/xray/latest/devguide/xray-daemon-ecs.html#xray-daemon-ecs-build , we can see x-ray is not base image, it is just installed inside image with curl and running as side car

upvoted 1 times

...