Exam AWS Certified Data Analytics - Specialty topic 1 question 137 discussion

Not sure if C fulfills the "long term solution" part of the question. In the worst case, he needs to adjust it every time the data grows and the query takes again longer. What about A?

Right answer is A but exam answer is C, they want you to know about service quotas.

Default Athena’s max query time out minute is 30min. so we needs to up Service Quoata.

I believe the best choice is A. From the given information, we aren't clear on how much we can extend the timeout—would 60 minutes suffice? It's uncertain. Increasing timeouts without a clear rationale isn't a recommended approach, as there are costs associated with prolonged query times, both in terms of resources and expenses. Operational Best Practices: Increasing timeouts without understanding the actual need can be considered a "band-aid" solution. It might temporarily solve the symptom (i.e., timeout) but not the underlying problem causing the delay.:)

C is not a sustainable solution. So A is correct

A: I passed the test

A seems to be the long term fix here. I go with A

why not D?

Answer is C: By default, the maximum timeout limit for a single query execution in Athena is 30 minutes. If the query requires more than 30 minutes to complete, it can be terminated with a "Query timeout" error. Splitting the query into smaller queries, as mentioned in option A, can work but may be time-consuming and not a scalable solution for large datasets. Requesting an increase in the DML query timeout via the Service Quotas console, as mentioned in option C, can provide a more scalable and long-term solution to the problem. Option D, saving tables as compressed .csv files, is not a solution to the problem described in the scenario. It will not address the query timeout issue and does not provide a long-term solution for the problem.

I will go with A as that appears to be the long term fix. C talks about increasing the timeout but there is no mention of increase by what extent

The 30-minute DDL query limit is a soft limit, and an increase can be requested in the Service Quotas console.

C https://docs.aws.amazon.com/athena/latest/ug/service-limits.html

For A, as there’re a large number of queries that need to be split, the effort is huge. Some queries may still need a longer time to complete, and it’s OK for the data analyst to wait for them. So increasing the timeout limit is the long-term solution. I go with C.

Selected Answer: C

A looks correct option. timeout could occur if the spool size of a query is too much an spice is not able to generate output in specified time. Increasing timeout is not a long term solution as other queries may continue to timeout with such large data sets. So better to limit the scope by splitting the queries for specific limited dataset even if that means running query multiple times.

Answer - C

C - Per amazon doc - https://docs.aws.amazon.com/athena/latest/ug/service-limits.html