57 practice questions for Domain 2 of the AWS Certified Data Engineer - Associate (DEA-C01) exam, which makes up 26% of its scored content. Your answers count towards one score and one timer for the whole exam.
Domain 2: Data Store Management
89. An Amazon Redshift fact table is joined to a large dimension table on customer_id, and query plans show most time spent redistributing rows between nodes. Which solution meets these requirements?
Answer and explanation
Answer: B. KEY distribution on the join column co-locates matching rows on the same node, which removes the redistribution step the plan identifies. ALL distribution replicates a large fact table to every node and is appropriate only for small dimensions. EVEN distribution is what forces the redistribution. A sort key improves range-restricted scans without changing how rows are distributed for a join.
90. A pipeline must store JSON documents with varying structure and support queries from an application that already uses MongoDB drivers. Which solution meets these requirements?
Answer and explanation
Answer: B. DocumentDB supports MongoDB-compatible drivers and a flexible document model, so the existing application works without a rewrite. DynamoDB has a different API, which is the rewrite being avoided. Objects queried with Athena suit analytical access rather than operational reads. Flattening into Redshift discards the variable structure.
91. A Redshift workload runs heavily for a few hours each weekday and is idle otherwise. Which solution meets these requirements at the lowest cost?
Answer and explanation
Answer: C. Redshift Serverless provisions capacity on demand and bills for what is used, which suits intermittent workloads. A provisioned cluster sized for the peak bills continuously. Concurrency scaling adds burst capacity on top of a cluster that still runs. Manual pause and resume requires operational effort and still bills storage and forgotten uptime.
92. Historical data in Amazon S3 must be queried from Amazon Redshift without loading it into cluster storage. Which solution meets these requirements?
Answer and explanation
Answer: C. Spectrum queries data in place in S3 through an external schema, so historical data never occupies cluster storage. A COPY command loads the data into the cluster, which the requirement excludes. A materialized view caches results of local tables. A datashare exposes data between Redshift clusters rather than reading S3.
93. An operational store must serve key-value lookups at single-digit millisecond latency with unpredictable traffic and no capacity planning. Which solution meets these requirements?
Answer and explanation
Answer: B. DynamoDB serves key-value lookups at single-digit millisecond latency, and on-demand mode absorbs unpredictable traffic without capacity planning. Provisioning for the peak requires exactly the planning being avoided and pays for idle capacity. RDS involves query planning and disk access. Redshift is an analytical warehouse.
94. Operational data in Amazon Aurora must be analysed in Amazon Redshift without the team building and maintaining an ETL pipeline. Which solution meets these requirements?
Answer and explanation
Answer: D. Zero-ETL integration replicates Aurora data into Redshift continuously as a managed capability with no pipeline to build. DMS and Glue are both pipelines the team must maintain. Federated query reaches live Aurora but pushes analytical load onto the operational database.
95. A search workload requires full-text search with aggregations and near-real-time indexing of incoming documents. Which solution meets these requirements?
Answer and explanation
Answer: B. OpenSearch provides inverted-index full-text search with aggregations and near-real-time indexing. Redshift with LIKE predicates performs full scans and is not a search engine. Athena over S3 is batch-oriented with no near-real-time indexing. A DynamoDB index supports key lookups rather than full-text search.
96. A caching layer must serve sub-millisecond reads and must survive the loss of a node without losing the cached data. Which solution meets these requirements?
Answer and explanation
Answer: C. MemoryDB combines in-memory read latency with a durable multi-AZ transaction log, so data survives node loss. Memcached holds data only in memory and loses it on node failure. DynamoDB with DAX is durable in the table but the cache itself is not the system of record. S3 through CloudFront serves objects rather than sub-millisecond key lookups.
97. Schemas across thousands of Amazon S3 prefixes must be discovered and made queryable without manual table definition. Which solution meets these requirements?
Answer and explanation
Answer: B. Glue crawlers infer schema and partitions from S3 data and register them in the Data Catalog, which Athena, EMR, and Redshift Spectrum all consult. A self-managed metadata store integrates with nothing automatically. Object tags carry key-value metadata but do not describe table schemas. Manual external schemas is the work being avoided.
98. New hourly partitions written to Amazon S3 are not returned by Amazon Athena until a crawler runs. Which solution meets these requirements with the LEAST operational overhead?
Answer and explanation
Answer: D. Partition projection calculates partition values from a configured pattern at query time, removing the need for a crawler or manual registration. An hourly crawler works but adds cost and a delay window. Manual statements require a step after every write. Recreating the table is the same work with more disruption.
99. An AWS Glue crawler must catalog tables in an Amazon RDS database reachable only from a private subnet. Which solution meets these requirements?
Answer and explanation
Answer: B. A Glue connection defines the JDBC target and network placement so the crawler runs elastic network interfaces in the specified subnet. Making the database public contradicts the requirement. Exporting to S3 catalogs a copy rather than the source. Crawlers are a managed service and are not run from customer instances.
100. One table definition must serve Amazon Athena, Amazon Redshift Spectrum, and Amazon EMR without being maintained separately in each. Which solution meets these requirements?
Answer and explanation
Answer: B. The Glue Data Catalog is the shared metastore that Athena, Redshift Spectrum, and EMR all consult, so one definition serves every engine. Separate definitions guarantee drift. A hand-parsed schema file requires each engine to implement the parsing. Exporting a definition creates copies that diverge.
101. An existing Apache Hive metastore on premises must be made available to AWS analytics services during a migration. Which solution meets these requirements?
Answer and explanation
Answer: B. AWS services can either consume a migrated Glue Data Catalog or reference an external Hive metastore directly, both of which preserve the existing definitions. Recreating definitions by hand is error-prone at scale. A metastore in RDS as CSV is not a metastore the engines can query. A local metastore per cluster loses definitions when the cluster ends.
102. A new AWS Glue connection must be created so that a crawler can catalog data held in an Amazon DocumentDB cluster. Which configuration is required?
Answer and explanation
Answer: C. A crawler reaches a database source through a Glue connection that carries the endpoint, credentials, and subnet placement. A crawler cannot reach a private database endpoint without one. Exporting to S3 catalogs a copy rather than the source. Manual table creation defeats the purpose of crawling.
103. Objects in a data lake are queried heavily for 30 days, occasionally for 90 more, and rarely afterwards, and all must be retained for seven years. Which solution meets these requirements at the lowest cost?
Answer and explanation
Answer: C. A predictable, time-based access pattern is cheapest to handle with explicit lifecycle transitions to progressively colder classes while retaining the data. Expiring at 120 days violates the seven-year requirement. S3 Standard pays frequent-access rates for cold data. Intelligent-Tiering adds a monitoring charge for a pattern that is already understood.
104. IoT readings in an Amazon DynamoDB table lose business value after 90 days and must be removed at the lowest cost. Which solution meets these requirements?
Answer and explanation
Answer: D. DynamoDB TTL deletes expired items in the background at no additional cost and without consuming write capacity. A nightly scan and delete job consumes substantial capacity and grows more expensive as the table grows. Quarterly table rotation is manual and complicates queries spanning the boundary. Reducing capacity never removes the data.
105. Curated results must be moved from Amazon Redshift into Amazon S3 for downstream consumers each night. Which solution meets these requirements?
Answer and explanation
Answer: B. UNLOAD writes query results directly from the cluster to S3 in parallel and supports partitioned columnar output. Returning rows through a client is far slower and bounded by the client. A materialized view keeps consumers on the cluster rather than moving data to S3. A federated query reads from Redshift rather than exporting to S3.
106. Objects in an Amazon S3 bucket must be recoverable after an accidental overwrite for 30 days, after which the previous versions should be removed. Which combination of steps meets these requirements? (Select TWO.)
Answer and explanation
Answer: A, B. Versioning retains the previous version when an object is overwritten, and a noncurrent-version expiry rule removes it at 30 days. Expiring current versions deletes live data. Object Lock prevents overwriting entirely, which conflicts with normal updates. Replication copies objects and does not by itself provide version recovery.
107. A dataset must be deleted permanently at a specific age to satisfy a legal retention limit. Which solution meets these requirements?
Answer and explanation
Answer: B. An expiry rule covering current and noncurrent versions deletes the data at the required age without manual intervention. A transition moves the data to a colder class while retaining it. Object Lock prevents deletion for the retention period, which is the opposite requirement. Manual bucket deletion depends on someone remembering.
108. An Amazon Redshift dimension table of 200 rows is joined to every large fact table query, and queries are slowed by data redistribution. Which solution meets these requirements?
Answer and explanation
Answer: C. Replicating a very small dimension to every node removes redistribution for the join at negligible storage cost. KEY distribution on a 200-row table leaves most nodes idle for that table. EVEN distribution forces redistribution during the join. A sort key aids scan pruning without addressing distribution.
109. Analysts must query both the current state of a dimension and its history of changes. Which solution meets these requirements?
Answer and explanation
Answer: D. Type 2 preserves each version of a row with validity dates and a flag identifying the current record, so both current and historical queries are possible. Overwriting destroys history. Nightly snapshots of the latest state cannot reconstruct intermediate changes. Recreating the table discards everything before today.
110. A source system adds new optional columns to its output every few weeks, and the pipeline must absorb them without failing. Which combination of steps meets these requirements? (Select TWO.)
Answer and explanation
Answer: C, D. A format carrying its own schema plus a crawler that refreshes the catalog lets new columns appear without a code change. A hardcoded column list breaks on the first addition. Collapsing everything to one string destroys the typing that makes the data queryable. Rejecting unknown fields discards valid data.
111. An Oracle schema using stored procedures and unsupported data types must be converted before migration to Amazon Redshift. Which solution meets these requirements?
Answer and explanation
Answer: C. SCT converts schema objects and reports what must be rewritten by hand, which is the supported path for incompatible constructs. DMS moves data but does not convert unsupported schema objects. Recreating by hand loses the conversion assistance and the report of what cannot convert. A crawler infers a flat schema from exported data and loses procedural logic.
112. An audit must establish which source data produced a given curated table, across several transformation steps. Which solution meets these requirements?
Answer and explanation
Answer: D. Lineage records the relationships between inputs, jobs, and outputs, which is what tracing a curated table back to its sources requires. Row counts describe volume without establishing derivation. Versioning preserves object history within one location. CloudTrail records who accessed objects rather than how data was derived.
113. A large Amazon S3 table is queried with filters on region and event date, and query cost must be reduced. Which solution meets these requirements?
Answer and explanation
Answer: B. Partitioning on the filtered columns lets the engine skip whole prefixes before reading anything, which is the dominant cost lever for data scanned. More files increase per-file overhead. A single uncompressed file forces a full scan. Object storage tables have no secondary index construct of that kind.
114. A DynamoDB table stores events keyed by device identifier, and a small number of devices generate most of the traffic. Which solution meets these requirements?
Answer and explanation
Answer: A. Throttling concentrated on a few keys is a hot partition problem, and appending a shard suffix distributes those writes across more partitions. Raising capacity does not address skew because per-partition limits still apply. A local secondary index shares the base partition key and inherits the skew. Point-in-time recovery is a backup feature.
115. A data lake table accumulates thousands of small files per partition from a streaming writer, and query times have degraded. Which solution meets these requirements?
Answer and explanation
Answer: D. Many small files force a large number of expensive file-open operations, and compacting them into larger objects restores throughput. Versioning increases the number of stored objects. A colder storage class changes cost rather than query performance. More partitions spread the files further and can worsen the problem.
116. A pipeline must store event data queried by time range with automatic tiering of older data. Which data store is appropriate?
Answer and explanation
Answer: B. Timestream is built for time series with automatic tiering by age and time-range query optimisation. DynamoDB indexes support key lookups rather than range scans over time efficiently at scale. RDS partitioning requires manual tier management. S3 prefixes require a query engine on top.
117. A pipeline must serve an operational dashboard with sub-second aggregate queries over recent data. Which approach is appropriate?
Answer and explanation
Answer: C. Pre-aggregation serves dashboard queries at interactive latency. Athena over raw data has seconds-scale latency. Querying the transactional database loads production. A nightly spreadsheet is stale.
118. An Amazon Redshift cluster's storage is nearly full, and most data is rarely queried. Which approach is appropriate?
Answer and explanation
Answer: A. Spectrum queries cold data in S3 without it occupying cluster storage. Adding nodes pays compute rates for storage. Deleting loses data still occasionally needed. Compression helps marginally.
119. A data store must support a schema that changes frequently as the application evolves. Which store is appropriate?
Answer and explanation
Answer: A. Document stores accept records with varying structure. A wide warehouse table and a relational table both require migrations. A fixed Parquet schema must be rewritten on change.
120. A Glue crawler is creating a separate table for each partition directory instead of one partitioned table. Which cause should be investigated first?
Answer and explanation
Answer: B. A crawler splits into separate tables when directory schemas are incompatible. Missing permission would fail the crawl. Schedule and compression do not affect table structure.
121. A Data Catalog table's schema must be updated when a new column appears, without dropping existing columns. Which crawler configuration is appropriate?
Answer and explanation
Answer: A. Adding new columns while ignoring deletions evolves the schema forward safely. Full replacement may drop columns. Log-only never updates. A new table per change fragments the catalog.
122. An Amazon Athena query returns no results for a partition that exists in Amazon S3. Which cause should be investigated first?
Answer and explanation
Answer: C. A partition present in S3 but not in the catalog is invisible to Athena. A restrictive filter is possible but the question specifies the partition itself. Versioning and workgroup limits do not hide partitions.
123. Business terms and data ownership must be discoverable alongside technical schema information. Which approach is appropriate?
Answer and explanation
Answer: C. Attaching business metadata to the catalog entries keeps it discoverable where the schema is. A separate wiki drifts. Column names cannot carry ownership. Email does not scale.
124. A pipeline writes daily partitions, and partitions older than two years must be removed from both storage and the catalog. Which approach is appropriate?
Answer and explanation
Answer: C. Both storage and catalog must be cleaned or queries fail on missing data or storage accumulates. Expiring storage alone leaves dangling catalog entries. Dropping catalog entries alone leaves storage. Manual deletion is unreliable.
125. A dataset must be retained for compliance but must never be modified or deleted during the retention period. Which approach is appropriate?
Answer and explanation
Answer: D. Compliance mode prevents modification and deletion by any principal until retention expires. Deep Archive is a storage class rather than immutability. Versioning preserves history but allows deletion. A bucket policy can be changed by an administrator.
126. A DynamoDB table's items must expire after 30 days without consuming write capacity for deletion. Which approach is appropriate?
Answer and explanation
Answer: C. TTL deletes expired items in the background at no write capacity cost. A scan and delete job consumes capacity. Monthly table rotation complicates queries. Reducing capacity does not delete.
127. An Amazon Redshift table must be periodically cleaned of deleted rows to reclaim space and maintain query performance. Which operation is appropriate?
Answer and explanation
Answer: B. VACUUM reclaims space and re-sorts. ANALYZE updates statistics without reclaiming space. UNLOAD and COPY move data rather than maintaining the table.
128. A Redshift table is queried mostly by date range and joined on customer_id. Which key configuration is appropriate?
Answer and explanation
Answer: C. A date sort key enables zone-map pruning for range queries, and a customer_id distribution key co-locates join rows. Sorting on the join column does not help range filters. Distributing on date creates skew. ALL distribution replicates a large table.
129. A DynamoDB table must support queries by customer and by order date within customer. Which key design is appropriate?
Answer and explanation
Answer: B. Customer as partition key and date as sort key supports both queries directly with a range condition on the sort key. Date as partition key spreads one customer across partitions. A combined key prevents range queries. An index on customer_id alone does not support date ordering within customer.
130. A schema change adds a required column to a source, and downstream jobs written for the old schema begin failing. Which practice would have prevented this?
Answer and explanation
Answer: A. A schema registry with compatibility rules prevents an incompatible change being published. Retention and crawler refresh do not evaluate compatibility. Wider types do not address a new required column.
131. A data lake table must be partitioned to support queries filtering by region and by date. Which partition structure is appropriate?
Answer and explanation
Answer: B. Nested partitioning on both filter columns lets queries on either prune. Single-column partitioning prunes only that column. Hash partitioning supports no filter.
132. An analytics workload must query semi-structured data with a schema that varies between records. Which approach is appropriate?
Answer and explanation
Answer: B. A columnar format with nested and optional field support handles varying records while remaining queryable. A fixed schema discards data. A string column pushes parsing to every query. Rejecting records loses them.
133. A workload requires both transactional writes and analytical queries over the same data. Which approach is appropriate?
Answer and explanation
Answer: D. Separating the workloads with replication or zero-ETL suits each access pattern. Analytical queries on the transactional store degrade production. Transactions against a warehouse perform poorly. Two independently updated copies diverge.
134. A data store must support a workload reading entire columns across billions of rows. Which storage format is appropriate?
Answer and explanation
Answer: D. Columnar formats read only the requested columns, which dominates cost at this scale. CSV, Avro, and plain text are all row-oriented and read whole rows.
135. A Data Catalog table's partitions must be registered automatically as new prefixes appear, without running a crawler. Which approach is appropriate?
Answer and explanation
Answer: D. Partition projection derives partitions from a configured pattern with no registration step. A crawler is the mechanism being avoided. Manual registration requires a step per partition. Recreating the table is the same work with more disruption.
136. A crawler must not overwrite a table's manually refined column types on each run. Which configuration is appropriate?
Answer and explanation
Answer: D. Configuring the crawler to leave existing columns unchanged preserves manual refinements. Less frequent runs delay the overwrite. Deleting the crawler stops partition discovery. Recreating the table discards the refinements.
137. A team must discover which datasets contain a particular column name across a large catalog. Which approach is appropriate?
Answer and explanation
Answer: C. The catalog is searchable by column metadata. Opening each definition does not scale. Querying files is expensive. A spreadsheet drifts from reality.
138. An Iceberg table accumulates metadata and orphan files over time. Which maintenance operation is appropriate?
Answer and explanation
Answer: A. Snapshot expiry and orphan file removal are the table format's maintenance operations. A full rewrite is disproportionate. Deleting metadata corrupts the table. Partition count does not govern metadata growth.
139. A dataset must be moved to lower-cost storage after 90 days but remain queryable without a restore. Which storage class is appropriate?
Answer and explanation
Answer: B. Glacier Instant Retrieval provides millisecond access at archive pricing. Flexible Retrieval and Deep Archive both require a restore. Standard is the class being moved away from.
140. A pipeline must delete records for a specific customer across a partitioned data lake table to satisfy a deletion request. Which approach is appropriate?
Answer and explanation
Answer: D. Row-level delete in an open table format removes the specific rows. Deleting whole partitions removes other customers' data. A separate marker table leaves the data present. A full rewrite is expensive and error-prone.
141. A schema registry must reject a producer change that would break existing consumers. Which compatibility setting is appropriate?
Answer and explanation
Answer: B. Backward compatibility protects existing consumers from a producer change. No checking permits the break. Forward compatibility protects the opposite direction. Full transitive compatibility is stricter but the question asks specifically about protecting existing consumers.
142. A fact table's grain must be defined before the table is built. What does the grain specify?
Answer and explanation
Answer: D. The grain defines what one row represents, which determines every subsequent modelling decision. Row count, format, and partitioning are separate concerns.
143. A dimension table must record the current value of an attribute and nothing more. Which slowly changing dimension type applies?
Answer and explanation
Answer: D. Type 1 overwrites in place, retaining only the current value. Type 2 preserves full history. Type 3 retains one prior value. Type 0 retains the original value permanently.
144. A Glue crawler must catalog data in a bucket owned by another account. Which configuration is required?
Answer and explanation
Answer: B. Cross-account crawling requires bucket policy access and key permission where objects are encrypted. Copying duplicates storage, public access exposes the data, and running from the owning account may not suit the catalog's location.
145. A Data Catalog must support tables whose underlying data is in several formats. Which consideration applies?
Answer and explanation
Answer: C. Format is a table-level property, so tables may differ while one table's files should be consistent. Databases do not enforce a single format, separate catalogs are unnecessary, and the catalog does not convert data.