New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon-DEA-C01 Exam - Topic 2 Question 22 Discussion

Actual exam question for Amazon's Amazon-DEA-C01 exam
Question #: 22
Topic #: 2
[All Amazon-DEA-C01 Questions]

A media company wants to improve a system that recommends media content to customer based on user behavior and preferences. To improve the recommendation system, the company needs to incorporate insights from third-party datasets into the company's existing analytics platform.

The company wants to minimize the effort and time required to incorporate third-party datasets.

Which solution will meet these requirements with the LEAST operational overhead?

Show Suggested Answer Hide Answer
Suggested Answer: A

AWS Data Exchange is a service that makes it easy to find, subscribe to, and use third-party data in the cloud. It provides a secure and reliable way to access and integrate data from various sources, such as data providers, public datasets, or AWS services. Using AWS Data Exchange, you can browse and subscribe to data products that suit your needs, and then use API calls or the AWS Management Console to export the data to Amazon S3, where you can use it with your existing analytics platform. This solution minimizes the effort and time required to incorporate third-party datasets, as you do not need to set up and manage data pipelines, storage, or access controls.You also benefit from the data quality and freshness provided by the data providers, who can update their data products as frequently as needed12.

The other options are not optimal for the following reasons:

B . Use API calls to access and integrate third-party datasets from AWS. This option is vague and does not specify which AWS service or feature is used to access and integrate third-party datasets. AWS offers a variety of services and features that can help with data ingestion, processing, and analysis, but not all of them are suitable for the given scenario.For example, AWS Glue is a serverless data integration service that can help you discover, prepare, and combine data from various sources, but it requires you to create and run data extraction, transformation, and loading (ETL) jobs, which can add operational overhead3.

C . Use Amazon Kinesis Data Streams to access and integrate third-party datasets from AWS CodeCommit repositories. This option is not feasible, as AWS CodeCommit is a source control service that hosts secure Git-based repositories, not a data source that can be accessed by Amazon Kinesis Data Streams. Amazon Kinesis Data Streams is a service that enables you to capture, process, and analyze data streams in real time, such as clickstream data, application logs, or IoT telemetry. It does not support accessing and integrating data from AWS CodeCommit repositories, which are meant for storing and managing code, not data .

D . Use Amazon Kinesis Data Streams to access and integrate third-party datasets from Amazon Elastic Container Registry (Amazon ECR). This option is also not feasible, as Amazon ECR is a fully managed container registry service that stores, manages, and deploys container images, not a data source that can be accessed by Amazon Kinesis Data Streams. Amazon Kinesis Data Streams does not support accessing and integrating data from Amazon ECR, which is meant for storing and managing container images, not data .


1: AWS Data Exchange User Guide

2: AWS Data Exchange FAQs

3: AWS Glue Developer Guide

: AWS CodeCommit User Guide

: Amazon Kinesis Data Streams Developer Guide

: Amazon Elastic Container Registry User Guide

: Build a Continuous Delivery Pipeline for Your Container Images with Amazon ECR as Source

Contribute your Thoughts:

0/2000 characters
Trinidad
14 days ago
Kinesis options look complicated. Stick with A for simplicity.
upvoted 0 times
...
Dan
19 days ago
Option B seems okay, but A is more efficient.
upvoted 0 times
...
Vannessa
24 days ago
Kinesis options sound complicated, not worth the hassle!
upvoted 0 times
...
Elli
30 days ago
B seems simpler, but not sure it’s the most efficient.
upvoted 0 times
...
Corazon
1 month ago
Wait, can we really trust third-party datasets?
upvoted 0 times
...
Fausto
1 month ago
Totally agree, API calls are straightforward.
upvoted 0 times
...
Lelia
2 months ago
A) is the best choice for easy integration!
upvoted 0 times
...
Argelia
2 months ago
Haha, using CodeCommit or ECR to access datasets? That's like using a sledgehammer to crack a nut!
upvoted 0 times
...
Altha
2 months ago
Option B is too vague, we need more specifics on how to access the datasets from AWS.
upvoted 0 times
...
Leila
2 months ago
I agree, using AWS Data Exchange to access and integrate the datasets sounds like the most straightforward solution.
upvoted 0 times
...
Lauran
2 months ago
I think minimizing operational overhead is key, so A sounds like the right approach based on what we studied.
upvoted 0 times
...
Junita
2 months ago
I feel like we had a practice question about Kinesis, but I can't recall if it's the best choice here.
upvoted 0 times
...
Maile
3 months ago
Agreed! API calls from AWS Data Exchange save time.
upvoted 0 times
...
Alica
3 months ago
Option A seems like the easiest way to integrate third-party datasets with minimal effort.
upvoted 0 times
...
Peggie
3 months ago
I think option A is the best. Easy integration with minimal effort.
upvoted 0 times
...
Aimee
3 months ago
I'm not entirely sure, but I think option B might involve more manual work compared to A.
upvoted 0 times
...
Tonette
3 months ago
I remember we discussed how using APIs can streamline data integration, so option A seems promising.
upvoted 0 times
...
Susy
4 months ago
Option A seems like the way to go. API calls are generally pretty straightforward, and AWS Data Exchange looks like it would provide the access to third-party data that the company needs.
upvoted 0 times
...
Domonique
4 months ago
Hmm, I'm not too familiar with AWS services, so I'm not sure which one would have the least operational overhead. I'd need to research the different options a bit more to make a confident decision.
upvoted 0 times
...
Rickie
4 months ago
Based on the requirement to minimize effort and time, I'd go with option A. Using API calls to access third-party data seems like the most efficient approach compared to the other options involving Kinesis and CodeCommit.
upvoted 0 times
...
Larae
4 months ago
I'm a bit confused by the options - are we supposed to use AWS services specifically, or can we use other tools? I'm not sure if option A is the best if we're limited to AWS.
upvoted 0 times
...
Nickolas
4 months ago
I think option A looks the most straightforward - using API calls to access and integrate third-party datasets from AWS Data Exchange seems like the least operational overhead.
upvoted 0 times
Luis
9 days ago
I agree, option A seems the easiest to implement.
upvoted 0 times
...
...

Save Cancel