IT Cert Ready

AWS

AWS Certified Data Engineer – Associate

Exam code: DEA-C01

Start practicing

About this certification

AWS Certified Data Engineer – Associate is a AWS certification. Exam code DEA-C01. IT Cert Ready offers 1,209 practice questions with domain quizzes, full mock exams, and detailed explanations. Practice by official domain with 4 blueprint-aligned domains.

Official exam domain weights

Verified blueprint weights from the official exam outline.

  • Domain 1 · Data Ingestion and Transformation · 34%
  • Domain 2 · Data Store Management · 26%
  • Domain 3 · Data Operations and Support · 22%
  • Domain 4 · Data Security and Governance · 18%

Sample AWS Certified Data Engineer – Associate practice questions

Preview realistic multiple-choice items from the IT Cert Ready question bank. Expand each answer for the correct choice and explanation—the same format used in domain quizzes and mock exams.

  1. Sample question 1 · Data Security and Governance (18%)

    Veltrix Labs, a SaaS startup operating in the EU, ingests customer telemetry data into Amazon S3 and processes it using AWS Glue ETL jobs. A GDPR audit has been initiated, and the compliance officer needs to demonstrate that all datasets containing personal data have been cataloged with appropriate metadata tags, that data lineage is traceable from ingestion to transformation, and that access to PII fields is logged for evidence collection. The engineering team currently uses AWS Glue Data Catalog to register tables but has not enforced column-level classification or enabled CloudTrail logging for Glue API calls. Which combination of actions should the data engineer prioritize to satisfy the audit's evidence collection requirements for PII governance and data lineage at Veltrix Labs?

    • A. Enable AWS Glue Data Catalog resource policies to restrict cross-account access, configure S3 server-side encryption, and use AWS Config rules to detect untagged S3 buckets.
    • B. Activate Amazon Macie on the S3 buckets to automatically classify PII columns, enable CloudTrail data events for Glue and S3, and use Glue Data Catalog column-level metadata tags to document PII classifications alongside Glue job bookmarks to establish transformation lineage.
    • C. Deploy AWS Lake Formation row-level security filters on all Glue tables, enable VPC Flow Logs for Glue connections, and schedule weekly Glue crawlers to refresh table schemas.
    • D. Configure AWS Glue DataBrew to profile datasets for PII patterns, enable Amazon GuardDuty for threat detection on S3, and use AWS Trusted Advisor to audit IAM permissions on Glue roles.
    View answer & explanation

    Correct answer: B. Activate Amazon Macie on the S3 buckets to automatically classify PII columns, enable CloudTrail data events for Glue and S3, and use Glue Data Catalog column-level metadata tags to document PII classifications alongside Glue job bookmarks to establish transformation lineage.

    [Domain 4 - Data Security and Governance, Subtopic 4 - Security and Governance - Area 1 - Glue Data Catalog] Core Concept: Apply data governance and compliance. requires applying glue data catalog in the context of the scenario, consistent with the official (ISC)² exam outline. Correct Answer (B): Activate Amazon Macie on the S3 buckets to automatically classify PII columns, enable CloudTrail data events for Glue and S3, and use Glue Data Catalog column-level metadata tags to document PII classifications alongside Glue job bookmarks to establish transformation lineage. Why the other options are incorrect: Option A: Resource policies and S3 encryption address access control and data protection but do not produce PII classification evidence, data lineage records, or the API-level audit trail required by the GDPR audit. Option C: Lake Formation row-level security and VPC Flow Logs address access restriction and network monitoring respectively, but neither classifies PII columns, documents lineage, nor generates the Glue API audit trail needed for compliance evidence. Option D: DataBrew profiling can surface PII patterns interactively but does not produce the automated, cataloged classification or the continuous audit trail that Macie and CloudTrail provide for formal regulatory evidence collection.

  2. Sample question 2 · Data Security and Governance (18%)

    Meridian Defense Analytics, a large government contractor operating under a classified-adjacent contract with strict NIST 800-53 controls, processes sensitive law enforcement statistical data in an AWS data lake. A junior data engineer inadvertently configured an AWS Glue ETL job to write transformed output — including fields containing Social Security Numbers — to an S3 prefix that lacks any Glue Data Catalog table definition or column-level sensitivity tags. The incident was detected by an automated S3 event notification 72 hours after the first write. The contractor's incident response policy classifies any untagged PII exposure as a Severity 2 incident requiring escalation to the agency's Privacy Officer within four hours of detection and full remediation within 48 hours. The data engineering manager must now coordinate both the technical remediation and the escalation communication simultaneously. To satisfy both the four-hour escalation requirement and the 48-hour remediation deadline, which sequence of actions should the data engineering team execute?

    • A. Immediately restrict S3 bucket access using a bucket policy, notify the Privacy Officer with a preliminary incident report citing the untagged PII output location, then register the output prefix as a Glue Data Catalog table with PII column classifications and update the ETL job to enforce catalog-registered output paths going forward.
    • B. Suspend the Glue ETL job, run Amazon Macie to quantify the PII exposure, wait for the full Macie report before notifying the Privacy Officer, and then register the affected prefix in the Glue Data Catalog after remediation is confirmed.
    • C. Re-run the Glue ETL job with a corrected output path to an already-cataloged S3 prefix, delete the original untagged output, and notify the Privacy Officer only after the corrected data is validated in the catalog.
    • D. Enable AWS CloudTrail data events on the affected bucket, generate an access log report for the Privacy Officer, and schedule Glue Data Catalog registration for the next sprint cycle to avoid disrupting the production ETL pipeline.
    View answer & explanation

    Correct answer: A. Immediately restrict S3 bucket access using a bucket policy, notify the Privacy Officer with a preliminary incident report citing the untagged PII output location, then register the output prefix as a Glue Data Catalog table with PII column classifications and update the ETL job to enforce catalog-registered output paths going forward.

    [Domain 4 - Data Security and Governance, Subtopic 4 - Security and Governance - Area 1 - Glue Data Catalog] Core Concept: Apply data governance and compliance. requires applying glue data catalog in the context of the scenario, consistent with the official (ISC)² exam outline. Correct Answer (A): Immediately restrict S3 bucket access using a bucket policy, notify the Privacy Officer with a preliminary incident report citing the untagged PII output location, then register the output prefix as a Glue Data Catalog table with PII column classifications and update the ETL job to enforce catalog-registered output paths going forward. Why the other options are incorrect: Option B: Waiting for a full Macie report before notifying the Privacy Officer violates the four-hour escalation requirement; Macie discovery is a useful supplementary control but cannot be a prerequisite to mandatory incident notification under the contractor's policy. Option C: Redirecting the ETL job and deleting the original output without first notifying the Privacy Officer violates the escalation timeline and may constitute destruction of evidence relevant to the incident investigation, compounding the compliance failure. Option D: Scheduling Glue Data Catalog registration for a future sprint cycle does not meet the 48-hour remediation deadline, and providing only a CloudTrail access log does not satisfy the governance policy requirement for catalog-level PII classification of the affected data asset.

  3. Sample question 3 · Data Security and Governance (18%)

    Arcturus Federal Systems, a mid-sized government contractor supporting a civilian agency, maintains a data lake on AWS storing contract performance records and personally identifiable information (PII) of agency personnel. During a routine compliance audit, the auditor discovers that a new S3 bucket containing exported workforce reports was created three weeks ago but was never registered in the AWS Glue Data Catalog. As a result, no column-level metadata, data classifications, or ownership tags exist for the bucket's contents. The agency's data governance policy requires all data assets to be cataloged within 48 hours of creation, with PII fields explicitly tagged. The audit finding must be escalated to the agency's Contracting Officer Representative (COR) within 24 hours, and remediation must be completed before the next contract performance review in five business days. Which combination of actions should the data engineering team take FIRST to address the compliance gap and meet the escalation timeline?

    • A. Immediately delete the unregistered S3 bucket and recreate it under a compliant naming convention, then register the new bucket in the Glue Data Catalog with PII column tags before the performance review.
    • B. Run an AWS Glue crawler against the unregistered S3 bucket to populate the Data Catalog with schema and metadata, then apply resource-level tags and column-level PII classifications in the catalog, and document the remediation timeline for the COR escalation report.
    • C. Enable Amazon Macie on the unregistered bucket to generate a PII discovery report, submit that report directly to the COR as evidence of compliance, and defer Glue Data Catalog registration until after the performance review.
    • D. Move the unregistered bucket's contents to an existing cataloged S3 location, update the existing Glue Data Catalog table to reflect the additional data, and notify the COR that no new catalog entry is required.
    View answer & explanation

    Correct answer: B. Run an AWS Glue crawler against the unregistered S3 bucket to populate the Data Catalog with schema and metadata, then apply resource-level tags and column-level PII classifications in the catalog, and document the remediation timeline for the COR escalation report.

    [Domain 4 - Data Security and Governance, Subtopic 4 - Security and Governance - Area 1 - Glue Data Catalog] Core Concept: Apply data governance and compliance. requires applying glue data catalog in the context of the scenario, consistent with the official (ISC)² exam outline. Correct Answer (B): Run an AWS Glue crawler against the unregistered S3 bucket to populate the Data Catalog with schema and metadata, then apply resource-level tags and column-level PII classifications in the catalog, and document the remediation timeline for the COR escalation report. Why the other options are incorrect: Option A: Deleting and recreating the bucket introduces unnecessary data availability risk and does not address the root cause — the absence of a cataloging process — making it an operationally disruptive and disproportionate response to a metadata gap. Option C: A Macie PII discovery report is a detection output, not a catalog registration; submitting it as a substitute for Glue Data Catalog compliance does not satisfy the governance policy requirement and defers the actual remediation past the performance review deadline. Option D: Merging data into an existing cataloged location without a distinct catalog entry obscures data lineage and ownership, violates the policy requirement for each asset to be individually registered, and misrepresents the compliance status to the COR.

  4. Sample question 4 · Data Security and Governance (18%)

    Orindal Systems is a mid-sized SaaS startup headquartered in Canada that stores healthcare-adjacent wellness data for enterprise clients. Following a SOC 2 Type II audit cycle, the external auditors request a sample of evidence demonstrating that PII fields in the company's Amazon Redshift data warehouse are masked during ETL processing and that any schema changes to tables containing sensitive columns are tracked over time. The data engineering team uses AWS Glue jobs to load data from S3 into Redshift and registers all tables in the AWS Glue Data Catalog. The team has not implemented column-level lineage documentation or schema change tracking. To address the auditors' sampling request for PII masking evidence and schema change documentation, which approach should the data engineer implement?

    • A. Use AWS Glue job scripts with dynamic frame transformations to apply masking logic on PII columns before loading to Redshift, record column-level metadata and sensitivity classifications in the Glue Data Catalog, and enable AWS CloudTrail to log all Glue Data Catalog DDL operations so schema changes are captured in an auditable trail.
    • B. Enable Amazon Redshift audit logging to capture all SQL queries, configure Redshift column-level access control using GRANT statements, and use Amazon EventBridge to trigger SNS notifications when new Glue crawlers run.
    • C. Deploy AWS Macie on the Redshift cluster to scan for PII, configure S3 Object Lock on the raw data bucket, and use AWS Config to detect changes to Redshift cluster parameter groups.
    • D. Implement AWS Lake Formation column masking policies on the Glue Data Catalog tables, enable S3 Intelligent-Tiering for cost-optimized storage of audit logs, and use AWS Glue DataBrew recipes to document transformation steps.
    View answer & explanation

    Correct answer: A. Use AWS Glue job scripts with dynamic frame transformations to apply masking logic on PII columns before loading to Redshift, record column-level metadata and sensitivity classifications in the Glue Data Catalog, and enable AWS CloudTrail to log all Glue Data Catalog DDL operations so schema changes are captured in an auditable trail.

    [Domain 4 - Data Security and Governance, Subtopic 4 - Security and Governance - Area 1 - Glue Data Catalog] Core Concept: Apply data governance and compliance. requires applying glue data catalog in the context of the scenario, consistent with the official (ISC)² exam outline. Correct Answer (A): Use AWS Glue job scripts with dynamic frame transformations to apply masking logic on PII columns before loading to Redshift, record column-level metadata and sensitivity classifications in the Glue Data Catalog, and enable AWS CloudTrail to log all Glue Data Catalog DDL operations so schema changes are captured in an auditable trail. Why the other options are incorrect: Option B: Redshift audit logging captures query-level activity after data has already landed in the warehouse and does not demonstrate that PII masking occurred during ETL ingestion, nor does it document schema change history in the Glue Data Catalog. Option C: Amazon Macie is designed to scan S3 objects and does not operate directly on Redshift clusters; S3 Object Lock addresses immutability rather than PII masking evidence or schema change tracking. Option D: Lake Formation column masking enforces access-time masking for query consumers but does not demonstrate that PII was masked during the ETL load process itself, and DataBrew recipes document profiling steps rather than producing the schema change audit trail required by the auditors.

  5. Sample question 5 · Data Security and Governance (18%)

    Velorix Systems, a mid-sized cloud-native technology firm operating across North America and the EU, recently migrated its customer analytics platform to AWS. During a routine compliance audit, the auditor discovers that the AWS Glue Data Catalog contains hundreds of tables referencing customer records, but there is no documented lineage showing how raw ingestion data flows through transformation jobs into the final reporting tables. The firm is subject to GDPR and must demonstrate to regulators that PII is tracked, transformed lawfully, and auditable end-to-end. The data engineering team must implement a solution that captures transformation lineage within the existing Glue-based pipeline without rebuilding the entire architecture. Which approach BEST enables Velorix Systems to satisfy the GDPR lineage and auditability requirement within their existing AWS Glue pipeline?

    • A. Enable AWS Glue job bookmarks on all ETL jobs so that the service tracks which data partitions have been processed, providing a lineage record for regulators.
    • B. Activate AWS Glue Data Catalog's built-in table versioning and configure AWS Glue workflows to emit job run metadata to AWS CloudTrail, then use Amazon Athena to query CloudTrail logs for end-to-end lineage reconstruction.
    • C. Migrate all Glue ETL scripts to AWS Lambda functions and use Amazon EventBridge to log each transformation event, replacing the Glue Data Catalog with a custom metadata store.
    • D. Enable Amazon Macie on the S3 buckets backing the Glue Data Catalog tables so that Macie automatically generates a lineage graph of PII movement across transformation stages.
    View answer & explanation

    Correct answer: B. Activate AWS Glue Data Catalog's built-in table versioning and configure AWS Glue workflows to emit job run metadata to AWS CloudTrail, then use Amazon Athena to query CloudTrail logs for end-to-end lineage reconstruction.

    [Domain 4 - Data Security and Governance, Subtopic 4 - Security and Governance - Area 1 - Glue Data Catalog] Core Concept: Apply data governance and compliance. requires applying glue data catalog in the context of the scenario, consistent with the official (ISC)² exam outline. Correct Answer (B): Activate AWS Glue Data Catalog's built-in table versioning and configure AWS Glue workflows to emit job run metadata to AWS CloudTrail, then use Amazon Athena to query CloudTrail logs for end-to-end lineage reconstruction. Why the other options are incorrect: Option A: Glue job bookmarks track processing state for incremental loads to avoid reprocessing data — they do not record transformation lineage or the provenance chain between source and target tables required for regulatory auditability. Option C: Migrating ETL scripts to Lambda and replacing the Glue Data Catalog with a custom metadata store contradicts the requirement to avoid rebuilding the entire architecture and introduces significant operational risk without a clear governance benefit. Option D: Amazon Macie is a data discovery and PII classification service that scans S3 objects for sensitive data patterns; it does not generate lineage graphs or track how data moves between transformation stages in a Glue pipeline.

AWS Certified Data Engineer – Associate exam prep FAQ

What is the passing score for the AWS Certified Data Engineer – Associate exam?
Passing scores for AWS Certified Data Engineer – Associate are set by AWS and can change between exam versions. Check the latest official exam outline on the AWS website for the current passing standard.
How many questions are on the AWS Certified Data Engineer – Associate certification exam?
Official AWS Certified Data Engineer – Associate exam length and item types are defined by AWS. Review the current exam blueprint for the latest question counts and timing.
How do domain quizzes help with AWS Certified Data Engineer – Associate exam prep?
Domain quizzes on IT Cert Ready let you practice AWS Certified Data Engineer – Associate one blueprint domain at a time across 4 official exam domains. You get immediate feedback, detailed explanations, and can revisit weak areas before taking a full timed mock exam.
How many AWS Certified Data Engineer – Associate practice questions are on IT Cert Ready?
IT Cert Ready includes 1,209 published AWS Certified Data Engineer – Associate practice questions with domain quizzes, full-length mock exams, and answer explanations mapped to the official outline.