SAA-C03 Question 347
Select 2A retail company wants to analyze transactional data stored in Amazon S3 for insights. The company needs a solution that allows them to run ad-hoc SQL queries on the data without having to set up or manage infrastructure. They also want to ensure that the data is well-organized and secured for future analysis. Which combination of AWS services should they use?
- A
Amazon Athena
- B
AWS Lake Formation
- C
Amazon RDS
- D
Amazon QuickSight
- E
Amazon Redshift
Show answer and explanation
Correct answers: A, B
Explanation
The combination of Amazon Athena and AWS Lake Formation meets the company's requirements perfectly. Amazon Athena allows them to run ad-hoc SQL queries directly on the data stored in Amazon S3 without managing infrastructure, while AWS Lake Formation helps organize and secure the data for future analysis. Other options like Amazon RDS, Amazon QuickSight, and Amazon Redshift are either unsuitable for the use case or require additional setup and infrastructure management.
- A. Correct.
Amazon Athena is a serverless query service that allows you to run SQL queries directly on data stored in Amazon S3. It is ideal for ad-hoc querying without the need to manage infrastructure.
- B. Correct.
AWS Lake Formation helps in organizing, securing, and managing data lakes in Amazon S3. It simplifies the process of setting up a secure and well-organized data lake, making it a suitable choice for the company's need to organize and secure their data.
- C. Incorrect.
Amazon RDS is a managed relational database service, but it is not appropriate for querying data directly from Amazon S3 or for ad-hoc analytics in this scenario.
- D. Incorrect.
Amazon QuickSight is a business intelligence and visualization tool, suitable for creating dashboards and reports, but it is not used for running SQL queries or organizing data in S3.
- E. Incorrect.
Amazon Redshift is a data warehouse solution, which requires setting up infrastructure. It is more suitable for structured and high-volume data warehousing scenarios rather than the ad-hoc querying and lightweight setup described here.