Exam AWS DevOps Engineer Professional topic 1 question 20 discussion

I'll go with A and C References: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/install-CloudWatch-Agent-on-premise.html https://docs.aws.amazon.com/xray/latest/devguide/xray-api-sendingdata.html

To identify the cause of the high response latencies, the DevOps team should: Install the CloudWatch agent server side and configure the agent to upload relevant logs to CloudWatch. This will allow the team to collect log data without introducing additional latency. Enable AWS X-Ray tracing in API Gateway, modify the application to capture request segments, and use the X-Ray daemon to upload segments to X-Ray. This will allow the team to collect tracing data without introducing additional latency. Therefore, the correct actions to take are A and C. Option B is incorrect because uploading request segments to X-Ray during each request would introduce additional latency. Option D is incorrect because sending log information back to API Gateway with each request would introduce additional latency. Option E is incorrect because calculating and uploading statistical data relevant to the API service requests to CloudWatch metrics would introduce additional latency.

B C is correct B. Enable AWS X-Ray tracing in API Gateway, modify the application to capture request segments, and upload those segments to X-Ray during each request. Why? AWS X-Ray tracing helps trace end-to-end requests, enabling latency analysis. By capturing request segments in your application and uploading them to X-Ray, you gain visibility into where delays occur without impacting performance significantly. C. Enable AWS X-Ray tracing in API Gateway, modify the application to capture request segments, and use the X-Ray daemon to upload segments to X-Ray. Why? Using the X-Ray daemon optimizes the process of sending trace data, offloading this task from your application and reducing performance impact. The daemon works seamlessly with API Gateway and on-premises systems.

AC es la bonne réponse

A. Install the CloudWatch agent server-side and configure the agent to upload relevant logs to CloudWatch is a valid action to collect relevant data. This action will collect logs and other relevant system data from the on-premises API, which can then be analyzed in CloudWatch Logs Insights to identify the cause of the high response latencies. B. Enable AWS X-Ray tracing in API Gateway, modify the application to capture request segments, and upload those segments to X-Ray during each request is another valid action. This will allow the DevOps team to trace the request as it passes through the system and identify which segments are causing the high response latencies. Therefore, the correct options are A and B.

A and C for me E introduces more latency

I'll go with A and C

Enabling X-Ray tracing in the API Gateway console You can use the Amazon API Gateway console to enable active tracing on an API stage. These steps assume that you have already deployed the API to a stage. Sign in to the API Gateway console at https://console.aws.amazon.com/apigateway. In the APIs pane, choose the API, and then choose Stages. In the Stages pane, choose the name of the stage. In the Stage Editor pane, choose the Logs/Tracing tab. To enable active X-Ray tracing, choose Enable X-Ray Tracing under X-Ray Tracing. If desired, choose Set X-Ray Sampling Rules and go to the X-Ray console to configure sampling rules. Once you've enabled X-Ray for your API stage, you can use the X-Ray management console to view the traces and service maps. Nothing shows here that you should use an x-ray daemon everything is collected automatically with proper service role attached on API gateway, not sure C is one of the correct answer.

B, D and E will increase the latency.

The question is about latency and not logging/monitoring. As a result, X-ray is the right answer and not Cloudwatch logs for transaction tracing across API Gateway and on-prem application hosting the API. So the correct answer is C,D. I will go with C and D.

A and C is the correct answer!

A. After you install the cloudwatch agent, then it will provide the metrics but cannot use them to get the latency information

A and C for sure

A & C. high response latencies could happen when your resource is full

the only 2 options that dont cause the application to incur more processing.

Ans is : CE

A for metrics and C for performance data