Exam DVA-C02 All QuestionsBrowse all questions from this exam
Go to Exam
Question 401

A company uses AWS X-Ray to monitor a serverless application. The components of the application have different request rates. The user interactions and transactions are important to trace, but they are low in volume. The background processes such as application health checks, polling, and connection maintenance generate high volumes of read-only requests.

Currently, the default X-Ray sampling rules are universal for all requests. Only the first request per second and some additional requests are recorded. This setup is not helping the company review the requests based on service or request type.

A developer must configure rules to trace requests based on service or request properties. The developer must trace the user interactions and transactions without wasting effort recording minor background tasks.

Which solution will meet these requirements?

    Correct Answer: D

    To meet the requirements, disable sampling for high-volume read-only requests to avoid unnecessary recording of these minor tasks. Sample at a higher rate for all requests that handle user interactions or transactions to ensure these crucial actions are traced effectively.

Discussion
catoteja

It’s C

Mo_1981Option: D

D is correct Chatgpt explanation Focus on Important Traces: By disabling sampling for high-volume read-only requests such as health checks, polling, and connection maintenance, you can prevent these low-priority requests from overwhelming the tracing system. This ensures that the system resources are conserved for more critical user interactions and transactions. Higher Sampling Rate for User Interactions: By sampling at a higher rate for requests that handle user interactions or transactions, you can ensure that these important requests are traced more comprehensively. This allows for better monitoring and troubleshooting of the application where it matters most. Selective Tracing: This approach allows you to selectively trace and monitor requests based on their importance and volume. High-volume background tasks are sampled minimally or not at all, while low-volume but critical user interactions and transactions are sampled more frequently.