Question 320

A Lambda handler succeeds, but users report events being processed minutes after publication. Which metric shows consumer delay?

  1. Kinesis iterator age metric
  2. Lambda batch failure reporting
  3. Lambda parallelization factor
  4. Kinesis event source mapping

Explanation

Correct Answer

A:

IteratorAge measures how far behind a stream-reading Lambda consumer is in processing records; in this scenario, monitor the function's iterator age alongside errors and duration to distinguish falling behind from producer-side arrival gaps.

Incorrect Answers

B:

Lambda can report individual failed record IDs for supported stream batch processing; its benefit is retrying only failed records in a stream batch; that is different from diagnosing lag in a Lambda stream consumer.

C:

The parallelization factor raises concurrent Lambda batches processed per Kinesis shard while preserving partition-key ordering; the current need is for diagnosing lag in a Lambda stream consumer, not increasing consumer throughput on busy shards.

D:

A Lambda event source mapping reads Kinesis records, checkpoints progress and invokes the function in batches; this can support connecting a Lambda processor to a Kinesis shard, but would not address the need for diagnosing lag in a Lambda stream consumer.

Question 321

A shared KMS key protects several datasets but one ETL role must decrypt only values carrying an approved context. What control can help?

  1. Secrets Manager secret
  2. SSM Parameter Store SecureString
  3. IAM role credentials instead of access keys
  4. KMS encryption context policy

Explanation

Correct Answer

D:

KMS key policies can evaluate encryption-context conditions to narrow permitted cryptographic use; in this scenario, use supported encryption-context conditions and test that the service supplies the expected context on cryptographic operations.

Incorrect Answers

A:

Secrets Manager stores and retrieves sensitive credentials and supports managed rotation patterns; this helps with protecting a rotating production database password, not scoping decrypt permission to the intended encrypted dataset.

B:

Systems Manager Parameter Store can hold encrypted configuration values as SecureString parameters; although useful for storing a rarely changed encrypted ETL token, it leaves the need for scoping decrypt permission to the intended encrypted dataset unmet.

C:

IAM role sessions provide automatically rotated temporary credentials to supported AWS workloads; it would target authenticating an AWS SDK call without storing an AWS secret, while the question is about scoping decrypt permission to the intended encrypted dataset.

Question 322

A Java parser's container image includes full compilers and large build artifacts not needed at runtime. Which build approach reduces image bloat?

  1. ECS task CPU and memory sizing
  2. ECS Service Auto Scaling
  3. Container image multi-stage build
  4. EKS Horizontal Pod Autoscaler

Explanation

Correct Answer

C:

Multi-stage Docker builds separate build tools from the runtime image to reduce final image contents; in this scenario, copy only the compiled application and needed runtime into the final stage; validate libraries remain available to the task.

Incorrect Answers

A:

An ECS task definition reserves CPU and memory for its container workloads; its benefit is giving each transformation container enough compute and RAM; that is different from keeping transformation images lean and faster to distribute.

B:

ECS Service Auto Scaling changes the desired count of running service tasks based on configured metrics; the current need is for keeping transformation images lean and faster to distribute, not adding parallel workers when a queue backlog rises.

D:

Kubernetes HPA adjusts replica counts of a target workload using metrics and configured policies; this helps with scaling Kubernetes transformation pods based on utilization, not keeping transformation images lean and faster to distribute.

Question 323

A model extracts invoice terms but lacks confidence on handwritten totals and compliance requires verification. Which processing design is appropriate?

  1. Human review for low-confidence extraction
  2. Bedrock text classification request
  3. Schema validation of LLM output
  4. PII redaction before LLM call

Explanation

Correct Answer

A:

A review queue can route uncertain automated extractions to humans instead of blindly publishing them; in this scenario, introduce confidence thresholds and review outcomes into the pipeline rather than treating every generated value as authoritative.

Incorrect Answers

B:

Amazon Bedrock can invoke foundation models to classify or summarize unstructured text in a pipeline; it would target deriving categories from free-form support notes, while the question is about avoiding unchecked facts in ambiguous document extraction.

C:

Model responses require parsing and validation against an expected structured contract before ingestion; its benefit is preventing unstructured model responses from breaking ETL; that is different from avoiding unchecked facts in ambiguous document extraction.

D:

Sensitive fields should be removed or minimized before they are sent to a model where policy requires it; the current need is for avoiding unchecked facts in ambiguous document extraction, not keeping customer identifiers out of model prompts.

Question 324

A customer CRM occasionally reassigns business IDs, but historic facts must continue pointing to the proper customer dimension rows. Which key strategy fits?

  1. Redshift star schema
  2. Lake Formation governed tables
  3. Surrogate warehouse dimension key
  4. DynamoDB access-pattern modeling

Explanation

Correct Answer

C:

Surrogate keys can stabilize warehouse joins when operational business identifiers change; in this scenario, use stable warehouse surrogate identifiers and maintain an explicit mapping to current and historical source business keys.

Incorrect Answers

A:

A star schema links facts to dimensions for analytic joins and common reporting aggregations; it would target modeling sales facts for BI measures by customer and product, while the question is about preserving historical dimension references through source ID changes.

B:

Lake Formation grants operate on registered data-lake catalog resources and can enforce fine-grained policies; its benefit is controlling which analysts can read governed S3 tables; that is different from preserving historical dimension references through source ID changes.

D:

DynamoDB tables are designed around known partition/sort key access patterns rather than normalized joins; this can support optimizing predictable NoSQL key queries, but would not address the need for preserving historical dimension references through source ID changes.

Question 325

A lakehouse team wants new Iceberg tables stored in a dedicated S3-managed table bucket with automatic compaction, snapshot cleanup and support for compatible query engines. What should they create?

  1. Iceberg partition evolution
  2. Apache Iceberg snapshots
  3. Amazon S3 Tables table bucket
  4. Iceberg schema evolution

Explanation

Correct Answer

C:

Amazon S3 Tables provides purpose-built table buckets for Apache Iceberg with automatic file compaction and snapshot maintenance; in this scenario, use an S3 table bucket and create the managed Iceberg tables; configure maintenance policies as needed instead of scheduling all file rewrites manually.

Incorrect Answers

A:

Iceberg can evolve partition specifications without rewriting historical data immediately into one fixed layout; its benefit is changing partition strategy as data volumes grow; that is different from hosting Iceberg tables with managed storage-level maintenance in Amazon S3.

B:

Iceberg tracks table snapshots and metadata so readers can use consistent committed table states; the current need is for hosting Iceberg tables with managed storage-level maintenance in Amazon S3, not keeping readers consistent during an object-based table update.

D:

Iceberg supports schema evolution using field identities rather than relying only on physical column order; this helps with adding columns without rewriting every historical file, not hosting Iceberg tables with managed storage-level maintenance in Amazon S3.

Question 326

A public report must show average wait times per district but cannot expose individual visit records. What release design is appropriate?

  1. Data anonymization aggregation
  2. One-way hashing of identifiers
  3. Amazon Macie sensitive data discovery
  4. Deterministic PII tokenization
  5. Redshift dynamic data masking

Explanation

Correct Answer

A:

Aggregation can report measurements across groups while excluding direct person-level rows from published outputs; in this scenario, publish sufficiently grouped statistics with suppression safeguards for small groups, evaluating residual re-identification risk.

Incorrect Answers

B:

A cryptographic hash maps inputs to fixed outputs without keeping an ordinary reversible mapping; the current need is for publishing population statistics without individual record detail, not comparing known identifiers without storing plaintext values.

C:

Macie can examine supported S3 data for sensitive information and report discovery findings; this can support detecting unexpected sensitive content in S3 objects, but would not address the need for publishing population statistics without individual record detail.

D:

Tokenization replaces sensitive identifiers with controlled surrogate values and protects the mapping separately; this helps with linking customer events without exposing raw identifiers, not publishing population statistics without individual record detail.

E:

Masking policies can return altered column representations to database users based on defined privileges; although useful for obscuring sensitive fields at query time for nonprivileged roles, it leaves the need for publishing population statistics without individual record detail unmet.

Question 327

Developers have hard-coded a database password in reusable Glue scripts, and rotation requires code edits. What configuration pattern improves this?

  1. ODBC connector configuration
  2. Glue VPC routing and DNS
  3. Secrets-based JDBC authentication
  4. JDBC driver compatibility

Explanation

Correct Answer

C:

ETL connections can retrieve database credentials from a secret rather than embedding plaintext; in this scenario, put credentials in a secret and reference them through the permitted connection; grant only required access to retrieve the secret.

Incorrect Answers

A:

ODBC connection settings rely on a driver and data-source configuration compatible with the application runtime; its benefit is integrating a tool that expects an ODBC data source; that is different from separating sensitive credentials from ETL source code.

B:

Glue network connections need paths and DNS resolution to reach databases inside a VPC; the current need is for separating sensitive credentials from ETL source code, not resolving a JDBC timeout to an internal data source.

D:

JDBC requires a driver compatible with the source database and its supported protocol; this helps with making a Glue job connect to a vendor database, not separating sensitive credentials from ETL source code.

Question 328

Each sensor message needs only unit conversion, with no window joins or prior observations. Which processing model is simplest?

  1. Idempotent output writes
  2. Kinesis retention adjustment
  3. Stateless transformation
  4. Durable consumer checkpoints
  5. Managed Service for Apache Flink keyed windows

Explanation

Correct Answer

C:

Stateless processors derive each output solely from their current input and need no cross-event accumulated state; in this scenario, a stateless function can transform each record independently and scale horizontally without shared window state.

Incorrect Answers

A:

Idempotent writes make replaying the same logical input safe without duplicating downstream effects; it would target preventing duplicate target rows after event redelivery, while the question is about applying independent per-record normalization rules.

B:

Stream retention controls how long published records remain available for replay in Kinesis Data Streams; its benefit is extending the recovery window for an offline consumer; that is different from applying independent per-record normalization rules.

D:

Checkpoints track a stream application's committed read position separately from the stream itself; this can support resuming from the last successfully processed record, but would not address the need for applying independent per-record normalization rules.

E:

Managed Service for Apache Flink can maintain keyed window aggregates with checkpoint-based state recovery across streaming records; this helps with running recoverable per-customer rolling-window totals in managed Flink, not applying independent per-record normalization rules.

Question 329

Support analysts need order facts but should not view complete email addresses stored in the same Redshift table. Which feature is relevant?

  1. Redshift database role
  2. Redshift dynamic data masking
  3. Redshift GRANT on schema objects
  4. Redshift row-level security policy

Explanation

Correct Answer

B:

Redshift dynamic data masking can change the presentation of sensitive columns according to database policy; in this scenario, apply masking policies to sensitive columns for designated roles while granting unmasked access only to approved users.

Incorrect Answers

A:

A Redshift database role groups database privileges that can be granted to multiple database users; its benefit is administering common warehouse table permissions centrally; that is different from hiding customer email values from ordinary warehouse readers.

C:

Redshift SQL grants determine which database principals can access schemas, tables and other objects; this can support giving a reporting role SELECT on one curated table, but would not address the need for hiding customer email values from ordinary warehouse readers.

D:

Redshift row-level security can restrict table rows returned for principals under applied policies; this helps with limiting warehouse query results to a user's assigned tenant, not hiding customer email values from ordinary warehouse readers.

Question 330

A crawler accidentally includes prior-year invoices stored under unrelated prefixes in the same S3 bucket. Which source configuration reduces contamination?

  1. S3 prefix-based ingestion
  2. Glue JDBC partition predicates
  3. DMS table mapping rules
  4. Glue job bookmarks

Explanation

Correct Answer

A:

Explicit S3 prefixes narrow the object keys examined by a batch ETL input; in this scenario, restrict its include path to the intended dataset prefix and use exclusions when required to avoid unrelated objects.

Incorrect Answers

B:

JDBC partitioning lets Glue spread relational reads over partitions instead of one serial scan; its benefit is accelerating a large batch read of a numeric-keyed table; that is different from scoping a daily batch to the intended landing folder.

C:

DMS table mappings select source schemas and tables and can apply supported transformations; the current need is for scoping a daily batch to the intended landing folder, not selecting only permitted source tables for replication.

D:

Glue job bookmarks can track previously processed source data between supported job runs; this can support avoiding the routine reread of already processed batches, but would not address the need for scoping a daily batch to the intended landing folder.

AWS Certified Data Engineer - Associate DEA-C01 Practice Tests