Sign in
Home/AWS/Associate (DEA-C01)/Free questions

AWS Certified Data Engineer - Associate (DEA-C01) — Free Practice Questions

10 free sample questions from a bank of 206, with the correct answers and explanations. No signup required — start practising right now.

1A data engineer is configuring an AWS Glue job to read data from an Amazon S3 bucket. The data engineer has set up the necessary AWS Glue connection details and an associated IAM role. However, when the data engineer attempts to run the AWS Glue job, the data engineer receives an error message that indicates that there are problems with the Amazon S3 VPC gateway endpoint. The data engineer must resolve the error and connect the AWS Glue job to the S3 bucket. Which solution will meet this requirement?
  • Update the AWS Glue security group to allow inbound traffic from the Amazon S3 VPC gateway endpoint.
  • Configure an S3 bucket policy to explicitly grant the AWS Glue job permissions to access the S3 bucket.
  • Review the AWS Glue job code to ensure that the AWS Glue connection details include a fully qualified domain name.
  • Verify that the VPC's route table includes inbound and outbound routes for the Amazon S3 VPC gateway endpoint.
Answer: D

The short version

D — Fix the route table for the S3 gateway endpoint to restore Glue access. Gateway endpoints rely on VPC route entries, not security groups, so missing routes strand the job even when IAM and bucket policies look correct.

Key concepts in this question

  • S3 gateway endpoint: VPC endpoint type that adds prefix-list routes to selected route tables for private S3 access without internet gateways.
  • VPC route tables: control subnet traffic; the associated table must cover Glue network interfaces.
  • Glue with VPC connections: jobs using a Glue connection launch in customer subnets and reach S3 through the endpoint routes rather than public paths.
  • Security group contrast: gateway endpoints have no security group, so inbound rules on the Glue group cannot repair endpoint routing failures.
  • Bucket policy and DNS contrast: permission grants and fully qualified names matter, but the stated symptom points to endpoint routing rather than auth or naming.

Why D is correct

Verifying that the VPC route table includes inbound and outbound routes for the S3 gateway endpoint ensures traffic from Glue subnets to S3 prefix lists traverses the endpoint. If the table lacks the endpoint entry or the wrong subnets are associated, packets never reach S3 and the job fails with endpoint errors. Correcting the route association restores private connectivity while preserving isolation, directly resolving the reported VPC endpoint problem.

Why the others are wrong

  • A. Gateway endpoints do not use security groups, so changing Glue inbound rules cannot fix endpoint routing.
  • B. Bucket policies grant data access but do not create the network path that a broken route table removes.
  • C. Fully qualified domain handling affects DNS resolution, not the missing gateway route entries described in the error.

DEA-C01 exam tip

Glue to S3 gateway endpoint failure means check route table association first, not security groups.

2A retail company has a customer data hub in an Amazon S3 bucket. Employees from many countries use the data hub to support company-wide analytics. A governance team must ensure that the company's data analysts can access data only for customers who are within the same country as the analysts. Which solution will meet these requirements with the LEAST operational effort?
  • Create a separate table for each country's customer data. Provide access to each analyst based on the country that the analyst serves.
  • Register the S3 bucket as a data lake location in AWS Lake Formation. Use the Lake Formation row-level security features to enforce the company's access policies.
  • Move the data to AWS Regions that are close to the countries where the customers are. Provide access to each analyst based on the country that the analyst serves.
  • Load the data into Amazon Redshift. Create a view for each country. Create separate IAM roles for each country to provide access to data from each country. Assign the appropriate roles to the analysts.
Answer: B

The short version

B — Lake Formation row-level security enforces same-country access with least effort. One S3 lake plus centrally managed filters limits each analyst to matching country rows without per-country tables or cross-Region copies.

Key concepts in this question

  • Row-level security: Lake Formation data filters restrict which rows a principal sees based on column values such as country code.
  • Central governance: register the bucket once as a lake location, then define permissions and LF-Tags in one catalog instead of many tables.
  • Multi-country analytics: analysts in many locales share one hub but must be isolated to their own national customer subset.
  • Least operational effort: managed filters scale to new countries and analysts by adding values, not by cloning storage or IAM architectures.
  • Heavier alternatives: separate tables, Region moves and Redshift views multiply storage, sync jobs and role sprawl while still needing filter logic.

Why B is correct

Registering the S3 bucket in Lake Formation and applying row-level filters on the country attribute gives each analyst a logical slice of the same physical data. Governance teams grant access through Lake Formation permissions tied to analyst identity, and Athena or Spark queries automatically enforce the filter. New countries need only new filter values and grants, so compliance is centralized and operational effort stays minimal.

Why the others are wrong

  • A. Per-country tables duplicate storage and require ongoing partition sync plus per-table grants.
  • C. Moving data to nearby Regions adds replication, cost and latency without providing row-level isolation by itself.
  • D. Redshift views plus per-country IAM roles provision a warehouse and multiply view and role maintenance for a lake problem.

DEA-C01 exam tip

Same-country-only lake access with least effort means Lake Formation row filters on one S3 hub.

3A 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?
  • Use API calls to access and integrate third-party datasets from AWS Data Exchange.
  • Use API calls to access and integrate third-party datasets from AWS DataSync.
  • Use Amazon Kinesis Data Streams to access and integrate third-party datasets from AWS CodeCommit repositories.
  • Use Amazon Kinesis Data Streams to access and integrate third-party datasets from Amazon Elastic Container Registry (Amazon ECR).
Answer: A

The short version

A — Use AWS Data Exchange APIs to add third-party data with least overhead. It provides licensed catalog products with API and S3 delivery, so the media team subscribes and ingests without building transfer or capture pipelines.

Key concepts in this question

  • Third-party enrichment: recommendation models improve with external behavior and preference datasets that must be licensed and refreshed reliably.
  • AWS Data Exchange: marketplace for data products with subscriptions, automated S3 exports and API access plus entitlement management.
  • Least operational overhead: favors subscribing to curated products over operating sync agents, streams or code repositories for data movement.
  • DataSync contrast: managed file transfer between owned storage systems, not a catalog for discovering and licensing external datasets.
  • Kinesis and code service contrast: streaming ingestion and source or image registries do not curate commercial datasets or handle licensing.

Why A is correct

API calls to Data Exchange let the company find relevant third-party products, subscribe once and pull updates directly into the analytics platform through APIs or S3 exports. Entitlements, versioning and delivery are managed by the service, minimizing integration code and refresh operations. That catalog-to-pipeline path is purpose-built for incorporating external datasets quickly, unlike generic transfer or streaming tools.

Why the others are wrong

  • B. DataSync moves files between owned NFS, SMB, S3 and cloud stores but does not provide licensed third-party catalogs.
  • C. Kinesis plus CodeCommit mixes streaming ingestion with source-code hosting, neither of which distributes commercial datasets.
  • D. Kinesis plus ECR similarly pairs streaming with container images, irrelevant to dataset licensing and delivery.

DEA-C01 exam tip

Third-party datasets with least effort means Data Exchange; DataSync is for owned file transfers.

4A financial company wants to implement a data mesh. The data mesh must support centralized data governance, data analysis, and data access control. The company has decided to use AWS Glue for data catalogs and extract, transform, and load (ETL) operations. Which combination of AWS services will implement a data mesh? (Choose two.)
  • Use Amazon Aurora for data storage. Use an Amazon Redshift provisioned cluster for data analysis.
  • Use Amazon S3 for data storage. Use Amazon Athena for data analysis.
  • Use AWS Glue DataBrew for centralized data governance and access control.
  • Use Amazon RDS for data storage. Use Amazon EMR for data analysis.
  • Use AWS Lake Formation for centralized data governance and access control.
Answer: B, E

The short version

BE — S3 plus Athena plus Lake Formation implements the Glue-based mesh. S3 gives scalable domain storage queried serverlessly by Athena, while Lake Formation centralizes permissions and sharing across domains.

Key concepts in this question

  • Data mesh: decentralized domain ownership with centralized governance, cataloging and self-serve access controls.
  • Glue catalog and ETL: shared metadata plus domain pipelines that prepare S3 datasets for discovery and analysis.
  • S3 plus Athena: durable lake storage with serverless SQL that lets domains publish and consume data without managing clusters.
  • Lake Formation: provides LF-Tags, cross-account sharing and row and column filters for mesh-wide governance and access control.
  • Mismatched services: Aurora, RDS, Redshift provisioned and EMR add managed databases or clusters where the mesh calls for elastic lake plus serverless query.

Why BE is correct

Using S3 for domain data storage keeps each mesh domain independent and scalable, while Athena provides federated serverless analysis over those S3 assets cataloged in Glue. Layering Lake Formation on top supplies the centralized governance and access-control plane the requirement demands, including permissions, sharing and audit. Together they satisfy storage, analysis and governance with Glue-compatible services, matching the choose-two mesh design.

Why the others are wrong

  • A. Aurora plus Redshift provisioned couples storage to provisioned analytics clusters rather than elastic mesh storage.
  • C. DataBrew prepares individual datasets visually but does not provide mesh-wide governance and access control.
  • D. RDS plus EMR similarly centers on provisioned databases and cluster analytics instead of S3 lake plus central policy.

DEA-C01 exam tip

Glue mesh means S3 plus Athena for data and Lake Formation for governance; memorize BE.

5A data engineer maintains custom Python scripts that perform a data formatting process that many AWS Lambda functions use. When the data engineer needs to modify the Python scripts, the data engineer must manually update all the Lambda functions. The data engineer requires a less manual way to update the Lambda functions. Which solution will meet this requirement?
  • Store a pointer to the custom Python scripts in the execution context object in a shared Amazon S3 bucket.
  • Package the custom Python scripts into Lambda layers. Apply the Lambda layers to the Lambda functions.
  • Store a pointer to the custom Python scripts in environment variables in a shared Amazon S3 bucket.
  • Assign the same alias to each Lambda function. Call reach Lambda function by specifying the function's alias.
Answer: B

The short version

B — Package shared formatting code as Lambda layers for single-point updates. Layers version common Python separately from function code, so fixing the script means publishing a new layer version and updating references instead of editing every function.

Key concepts in this question

  • Shared formatting logic: many functions import the same helpers, creating duplication when code is copied into each deployment package.
  • Lambda layers: distributable archives for libraries and custom modules that functions attach by ARN and version.
  • Manual update pain: copying scripts into each function forces repetitive edits, testing and redeploys with drift risk.
  • Versioned reuse: updating the layer once and pointing functions to the new version propagates fixes consistently.
  • Weak alternatives: S3 pointers and aliases add custom loading code and indirection without native dependency management.

Why B is correct

Packaging the custom Python scripts into Lambda layers separates shared formatting from business logic, letting each function import the layer path at runtime. When the engineer modifies the scripts, they publish a new layer version and update function configurations to reference it, which is far less manual than patching every deployment bundle. Layers also support semantic versioning and access control, making reuse auditable across many functions.

Why the others are wrong

  • A. S3 pointers in execution context need custom download and import code in every function with extra latency.
  • C. Environment-variable pointers to S3 still require loaders plus manual synchronization across functions.
  • D. Shared aliases ease invocation routing but do not share code; each function bundle still contains its own copy.

DEA-C01 exam tip

Shared Lambda code needing easy updates means Lambda layers, not S3 pointers or aliases.

6A company created an extract, transform, and load (ETL) data pipeline in AWS Glue. A data engineer must crawl a table that is in Microsoft SQL Server. The data engineer needs to extract, transform, and load the output of the crawl to an Amazon S3 bucket. The data engineer also must orchestrate the data pipeline. Which AWS service or feature will meet these requirements MOST cost-effectively?
  • AWS Step Functions
  • AWS Glue workflows
  • AWS Glue Studio
  • Amazon Managed Workflows for Apache Airflow (Amazon MWAA)
Answer: B

The short version

B — Glue workflows orchestrate Glue crawlers and jobs most cost-effectively. They schedule the SQL Server crawl plus S3 load natively inside Glue with triggers and no separate orchestrator billing.

Key concepts in this question

  • Glue-native pipeline: crawl a SQL Server table, run ETL and load S3 using only Glue crawlers and jobs.
  • Glue workflows: stateful graphs of crawlers, jobs and triggers with scheduling, dependencies and monitoring built into Glue pricing.
  • Cost-effectiveness: avoids paying for Airflow environments or per-transition state machines when all steps live in one service.
  • Step Functions contrast: ideal for cross-service chains with EMR or Lambda, but adds orchestration transitions for a Glue-only flow.
  • Studio and MWAA contrast: Studio aids visual job authoring and MWAA runs full Airflow, both heavier than native workflow triggers for this scope.

Why B is correct

A Glue workflow can start the SQL Server crawler, wait for catalog update, launch the ETL job that transforms output to S3 and handle retries from one console. Scheduling and dependencies stay within Glue, so there is no extra cluster or per-step orchestration charge beyond Glue runs. For requirements that are entirely crawl plus ETL plus orchestrate, that native fit is the most cost-effective choice.

Why the others are wrong

  • A. Step Functions adds cross-service power and transition cost unnecessary for a Glue-only pipeline.
  • C. Glue Studio builds and monitors jobs visually but is not the scheduler that chains crawlers to jobs.
  • D. MWAA runs managed Airflow with hourly environment cost, excessive for a single-service Glue sequence.

DEA-C01 exam tip

Crawl plus Glue job plus S3 with lowest cost means Glue workflows; Step Functions is for mixed services.

7A financial services company stores financial data in Amazon Redshift. A data engineer wants to run real-time queries on the financial data to support a web-based trading application. The data engineer wants to run the queries from within the trading application. Which solution will meet these requirements with the LEAST operational overhead?
  • Establish WebSocket connections to Amazon Redshift.
  • Use the Amazon Redshift Data API.
  • Set up Java Database Connectivity (JDBC) connections to Amazon Redshift.
  • Store frequently accessed data in Amazon S3. Use Amazon S3 Select to run the queries.
Answer: B

The short version

B — Use the Redshift Data API for lightweight app-embedded queries. It exposes HTTPS endpoints for SQL without persistent JDBC connections, pooling or bastion management inside the trading application.

Key concepts in this question

  • Real-time trading queries: web app needs short parameterized reads from Redshift with minimal connection overhead.
  • Redshift Data API: managed REST interface that runs SQL asynchronously, returns results as paged payloads and integrates with IAM and Secrets Manager.
  • JDBC contrast: requires connection pools, driver management, network allowlists and careful handling of concurrent web sessions.
  • WebSocket contrast: persistent bidirectional channels add complexity for request-response SQL that HTTPS already serves.
  • S3 Select contrast: filters S3 objects in place but cannot query Redshift financial tables or joins.

Why B is correct

The Data API lets the trading application call ExecuteStatement and fetch results over HTTPS using IAM auth, with no JDBC drivers or always-open database sockets. It handles queuing, parameterization and credential lookup through Secrets Manager, scaling with app requests while Redshift executes queries normally. That serverless access pattern gives real-time query capability with the least operational overhead.

Why the others are wrong

  • A. WebSocket connections to Redshift are not a native query interface and need custom gateway plus session handling.
  • C. JDBC connections force pool sizing, timeout tuning and VPC plumbing for every app instance.
  • D. S3 plus S3 Select queries flat objects only and cannot serve live Redshift financial data and joins.

DEA-C01 exam tip

App-embedded Redshift queries with least ops means Data API over HTTPS, not JDBC pools.

8A company uses Amazon Athena for one-time queries against data that is in Amazon S3. The company has several use cases. The company must implement permission controls to separate query processes and access to query history among users, teams, and applications that are in the same AWS account. Which solution will meet these requirements?
  • Create an S3 bucket for each use case. Create an S3 bucket policy that grants permissions to appropriate individual IAM users. Apply the S3 bucket policy to the S3 bucket.
  • Create an Athena workgroup for each use case. Apply tags to the workgroup. Create an IAM policy that uses the tags to apply appropriate permissions to the workgroup.
  • Create an IAM role for each use case. Assign appropriate permissions to the role for each use case. Associate the role with Athena.
  • Create an AWS Glue Data Catalog resource policy that grants permissions to appropriate individual IAM users for each use case. Apply the resource policy to the specific tables that Athena uses.
Answer: B

The short version

B — Per-use-case Athena workgroups with tags plus IAM isolate queries and history. Workgroups separate execution, result locations and history while tag-based policies scope who can use each one in a shared account.

Key concepts in this question

  • Athena workgroups: named execution contexts with own query limits, result buckets, encryption and history.
  • Tag-based access: workgroup tags combined with IAM condition keys restrict teams and apps to their designated workgroup.
  • Same-account isolation: needs logical separation of runs and audit trails without creating new accounts or buckets per team.
  • S3 bucket contrast: per-use-case buckets alone do not partition Athena history, settings or compute controls.
  • Catalog and role contrast: Glue resource policies and generic IAM roles lack workgroup-level query separation and history scoping.

Why B is correct

Creating a workgroup per use case lets the company set result locations, concurrency and monitoring separately, so query processes and history are naturally partitioned. Tagging each workgroup and writing IAM policies that allow only matching tags enforces that users, teams and applications run in their assigned context. This is the documented Athena isolation pattern for shared accounts and meets the requirement directly.

Why the others are wrong

  • A. Per-use-case S3 buckets plus bucket policies manage storage access but leave Athena runs and history commingled.
  • C. Per-use-case IAM roles without workgroups cannot partition query history and execution settings cleanly.
  • D. Glue catalog resource policies control table access, not Athena workgroup execution and history separation.

DEA-C01 exam tip

Shared-account Athena isolation means workgroups plus tags plus IAM, not extra buckets alone.

9A data engineer needs to schedule a workflow that runs a set of AWS Glue jobs every day. The data engineer does not require the Glue jobs to run or finish at a specific time. Which solution will run the Glue jobs in the MOST cost-effective way?
  • Choose the FLEX execution class in the Glue job properties.
  • Use the Spot Instance type in Glue job properties.
  • Choose the STANDARD execution class in the Glue job properties.
  • Choose the latest version in the GlueVersion field in the Glue job properties.
Answer: A

The short version

A — Choose FLEX execution class for schedule-insensitive daily Glue jobs. FLEX runs on spare capacity at reduced cost for workloads that tolerate variable start times, ideal when no fixed deadline exists.

Key concepts in this question

  • Glue execution classes: STANDARD for time-sensitive production versus FLEX for flexible non-urgent jobs at lower price.
  • Cost driver: flexible jobs can wait for spare resources, trading start-time variability for significant savings.
  • No fixed time: daily jobs without SLA allow Glue to optimize placement instead of reserving immediate capacity.
  • Spot misconception: Glue does not expose a generic Spot Instance toggle; FLEX is the supported flexible-capacity option.
  • Version contrast: newer Glue versions add features but do not change execution economics the way FLEX does.

Why A is correct

Selecting FLEX in the job properties tells Glue the workflow can start when spare capacity is available, which lowers run cost for the daily set. Because the engineer states the jobs need neither a specific start nor finish time, the variability of FLEX is acceptable. It requires only a property change with no code rewrite, making it the most cost-effective scheduling choice.

Why the others are wrong

  • B. Glue job properties do not offer a direct Spot Instance type selection; FLEX is the correct flexible capacity mechanism.
  • C. STANDARD reserves immediate capacity for urgent jobs and costs more than needed for time-flexible batches.
  • D. Latest GlueVersion modernizes runtime features but does not discount execution for flexible schedules.

DEA-C01 exam tip

Glue jobs with no time SLA and lowest cost means FLEX execution class.

10A data engineer needs to create an AWS Lambda function that converts the format of data from .csv to Apache Parquet. The Lambda function must run only if a user uploads a .csv file to an Amazon S3 bucket. Which solution will meet these requirements with the LEAST operational overhead?
  • Create an S3 event notification that has an event type of s3:ObjectCreated:*. Use a filter rule to generate notifications only when the suffix includes .csv. Set the Amazon Resource Name (ARN) of the Lambda function as the destination for the event notification.
  • Create an S3 event notification that has an event type of s3:ObjectTagging:* for objects that have a tag set to .csv. Set the Amazon Resource Name (ARN) of the Lambda function as the destination for the event notification.
  • Create an S3 event notification that has an event type of s3:*. Use a filter rule to generate notifications only when the suffix includes .csv. Set the Amazon Resource Name (ARN) of the Lambda function as the destination for the event notification.
  • Create an S3 event notification that has an event type of s3:ObjectCreated:*. Use a filter rule to generate notifications only when the suffix includes .csv. Set an Amazon Simple Notification Service (Amazon SNS) topic as the destination for the event notification. Subscribe the Lambda function to the SNS topic.
Answer: A

The short version

A — S3 ObjectCreated with CSV suffix filter directly to Lambda is leanest. One event notification fires only on CSV uploads and invokes the converter, with no polling, tagging rules or extra SNS hops.

Key concepts in this question

  • S3 event notifications: bucket triggers that invoke Lambda on object actions with prefix and suffix filters.
  • s3 ObjectCreated star: covers puts, posts, copies and multipart completions for newly uploaded objects.
  • Suffix filtering: limits invocations to keys ending in dot-csv so Parquet outputs and other files do not retrigger conversion.
  • Direct destination: setting the Lambda ARN as destination avoids SNS topics, subscriptions and added latency.
  • Least overhead: fewer resources and event types means fewer permissions, fewer duplicate invokes and simpler debugging.

Why A is correct

Creating an s3 ObjectCreated star notification with a dot-csv suffix filter and the Lambda ARN as destination ensures every user CSV upload triggers exactly one conversion run. The function reads the new object, writes Parquet and exits, scaling to zero between uploads. Broader event types, tagging conditions or SNS fan-out would add cost and failure modes without benefit for this single-trigger requirement.

Why the others are wrong

  • B. ObjectTagging events fire only when tags change, missing plain CSV uploads that carry no special tags.
  • C. Wildcard s3 star includes deletes and restores, causing unnecessary invokes beyond CSV creation.
  • D. Routing through SNS adds topic, permissions and subscription management for a direct Lambda trigger that suffices.

DEA-C01 exam tip

CSV-only Lambda conversion with least ops means ObjectCreated star plus suffix filter to Lambda.

Want the full bank of 206 questions for AWS Certified Data Engineer - Associate (DEA-C01)? See all practice exams.