MLA-C01 · Question #237
An ML engineer is building an ML model in Amazon SageMaker AI. The ML engineer needs to load historical data directly from Amazon S3, Amazon Athena, and Snowflake into SageMaker AI. Which solution…
The correct answer is D. Use SageMaker Data Wrangler to query and import the data. Amazon SageMaker Data Wrangler is specifically designed for data ingestion, exploration, and preparation inside SageMaker AI. It includes built-in native connectors for Amazon S3, Amazon Athena, and Snowflake (among dozens of other sources), allowing an ML engineer to query…
Question
An ML engineer is building an ML model in Amazon SageMaker AI. The ML engineer needs to load historical data directly from Amazon S3, Amazon Athena, and Snowflake into SageMaker AI. Which solution will meet this requirement?
Options
- AUse AWS Glue DataBrew to import the data into SageMaker AI.
- BBuild a pipeline in SageMaker Pipelines to process the data. Use AWS DataSync to load the
- CCreate a feature store in SageMaker Feature Store. Use an Apache Spark connector to Feature
- DUse SageMaker Data Wrangler to query and import the data.
How the community answered
(46 responses)- A13% (6)
- B4% (2)
- C4% (2)
- D78% (36)
Explanation
Amazon SageMaker Data Wrangler is specifically designed for data ingestion, exploration, and preparation inside SageMaker AI. It includes built-in native connectors for Amazon S3, Amazon Athena, and Snowflake (among dozens of other sources), allowing an ML engineer to query, preview, and import data from all three sources directly into a SageMaker environment without writing custom ETL code. Option A (AWS Glue DataBrew) is a standalone data preparation service and does not natively integrate all three sources into SageMaker in one workflow. Option B (SageMaker Pipelines + AWS DataSync) is incorrect because DataSync is a file-transfer service for migrating data to AWS storage, not a query engine for Athena or Snowflake. Option C (SageMaker Feature Store + Apache Spark) is an engineering-heavy approach that requires a custom Spark connector setup and is far more complex than necessary for simply loading historical data.
Topics
Community Discussion
No community discussion yet for this question.