Question 350

A Step Functions pipeline ends in FAILED, and operators need the sequence of completed and retried states. Where should they inspect?

  1. Glue conditional trigger
  2. Step Functions execution history
  3. Airflow dependency trigger rule
  4. EventBridge Scheduler flexible time window
  5. Airflow task retry policy

Explanation

Correct Answer

B:

Step Functions maintains execution event history for supported workflows and helps locate failed states; in this scenario, examine execution history and per-state inputs and errors while considering appropriate sensitive-data logging controls.

Incorrect Answers

A:

Glue conditional triggers can start downstream jobs when designated upstream jobs or crawlers reach configured states; the current need is for tracing the precise failure transition in a workflow, not running a publish job only after upstream Glue success.

C:

Airflow trigger rules determine when a downstream task may run relative to upstream task states; this helps with ensuring a cleanup task runs after upstream failures, not tracing the precise failure transition in a workflow.

D:

Flexible time windows let a scheduled invocation occur within a configured interval instead of at an exact instant; although useful for spreading noncritical batch launches to avoid thundering herds, it leaves the need for tracing the precise failure transition in a workflow unmet.

E:

Airflow tasks support retry counts and delays within a DAG's execution schedule; it would target retrying a transiently failing DAG task, while the question is about tracing the precise failure transition in a workflow.

Question 351

Every Glue job success and failure emits events, but a team wants only one named job's FAILED events. What routes these selectively?

  1. CloudWatch alarm action
  2. Step Functions workflow status alert
  3. SNS topic fan-out
  4. EventBridge event-to-target routing
  5. SQS durable queue

Explanation

Correct Answer

D:

EventBridge rules route matching state-change events to designated consumers; in this scenario, match both job identity and failure state in an EventBridge rule, then send the event to the selected alert target.

Incorrect Answers

A:

CloudWatch alarms evaluate metrics against thresholds and can invoke configured notification actions; the current need is for notifying only after a specific job state transition, not alerting after repeated error metric breaches.

B:

An EventBridge rule can match Step Functions execution status changes for monitoring and notifications; this can support notifying when a whole workflow fails rather than one retrying task, but would not address the need for notifying only after a specific job state transition.

C:

SNS publishes notifications to multiple subscribed endpoints or queues using topic subscriptions; this helps with delivering one alert to several independent recipients, not notifying only after a specific job state transition.

E:

SQS retains messages for asynchronous processing by consumers that may be temporarily unavailable; it would target buffering remediation work until a worker can run, while the question is about notifying only after a specific job state transition.

Question 352

An audit wants a representative subset of uniform sensor records for estimating the overall malformed-row rate. Which technique fits?

  1. Stratified random sampling
  2. Random sampling
  3. Systematic sampling caveat
  4. Spark key salting
  5. Reservoir sampling

Explanation

Correct Answer

B:

Simple random sampling selects records with equal inclusion probability when an unbiased population estimate is needed; in this scenario, draw a reproducible random sample at sufficient size and report uncertainty rather than selecting only convenient first rows.

Incorrect Answers

A:

Stratified sampling draws observations from defined subgroups to preserve rare but important categories; it would target assessing a dataset with very uneven country distributions, while the question is about building a general quality sample without subgroup constraints.

C:

Systematic sampling takes observations at regular intervals and may bias results when the stream is periodic; the current need is for building a general quality sample without subgroup constraints, not avoiding periodic bias when checking machine readings.

D:

Key salting distributes records for a heavily skewed join key across multiple synthetic partitions; this can support reducing one-key hotspots in a distributed join, but would not address the need for building a general quality sample without subgroup constraints.

E:

Reservoir sampling can maintain a bounded random sample from a stream of unknown total length; this helps with sampling a large unknown-length event stream with fixed memory, not building a general quality sample without subgroup constraints.

Question 353

A long-running EMR cluster is oversized overnight despite varying job demand. Which control helps reduce wasted compute?

  1. Glue worker sizing and job profiling
  2. EMR managed scaling
  3. Partition pruning
  4. Column projection before scan

Explanation

Correct Answer

B:

EMR managed scaling can adjust cluster capacity within configured limits based on workload demand; in this scenario, configure managed scaling and suitable instance groups or fleets, watching workload constraints and task completion targets.

Incorrect Answers

A:

Glue worker types and counts affect job parallelism, memory and billed compute consumption; although useful for right-sizing an oversized Glue ETL run, it leaves the need for reducing idle cluster capacity between Spark stages unmet.

C:

Partition pruning excludes dataset partitions whose values cannot satisfy a query predicate; its benefit is avoiding reads of unrelated months in a data lake; that is different from reducing idle cluster capacity between Spark stages.

D:

Reading only required fields can reduce bytes processed by columnar storage and SQL queries; the current need is for reducing idle cluster capacity between Spark stages, not minimizing scanned data during analytic transformations.

Question 354

A user can list an Athena table but receives AccessDenied when reading its S3 objects. What distinction should be checked?

  1. Catalog API lookup
  2. AWS Glue Data Catalog
  3. Catalog permissions boundary
  4. Apache Hive metastore

Explanation

Correct Answer

C:

Access to technical metadata and access to stored objects may be separately controlled by IAM and Lake Formation; in this scenario, verify both catalog authorization and underlying data access, as table visibility alone does not confer object-read permissions.

Incorrect Answers

A:

A data-processing application can query catalog APIs to discover schemas and data locations at runtime; this can support avoiding hard-coded column lists in a dynamic ETL client, but would not address the need for diagnosing why a visible table cannot be read.

B:

Glue Data Catalog is a managed technical metadata repository for datasets and ETL integration; this helps with centralizing technical table and partition definitions, not diagnosing why a visible table cannot be read.

D:

Hive metastore maintains table and partition metadata for compatible Hadoop ecosystem tools; it would target retaining a legacy Hive-compatible metadata system, while the question is about diagnosing why a visible table cannot be read.

Question 355

A batch pipeline adds date folders and needs an automated catalog update before analysts query. Which managed operation fits?

  1. Athena partition projection
  2. ALTER TABLE ADD PARTITION
  3. Partition pruning predicate
  4. Glue crawler partition update
  5. MSCK REPAIR TABLE

Explanation

Correct Answer

D:

A Glue crawler can discover supported new partitions and maintain catalog metadata during a run; in this scenario, run a correctly scoped crawler after the data lands so partition metadata is refreshed before dependent queries.

Incorrect Answers

A:

Partition projection computes partition locations from table properties instead of storing every partition explicitly; it would target avoiding per-day catalog updates for predictable partitions, while the question is about keeping partition metadata synchronized after scheduled ingestion.

B:

Adding a partition explicitly registers specified partition values and their locations in the catalog; its benefit is registering a small known list of partitions precisely; that is different from keeping partition metadata synchronized after scheduled ingestion.

C:

Query filters on partition columns allow compatible engines to avoid scanning unrelated object prefixes; the current need is for keeping partition metadata synchronized after scheduled ingestion, not reducing reads after partition registration.

E:

Athena's MSCK REPAIR TABLE can discover compatible Hive-style S3 partitions and add missing catalog entries; this helps with registering newly created Hive-style partition folders, not keeping partition metadata synchronized after scheduled ingestion.

Question 356

An API enrichment sometimes hangs on a network call, consuming concurrency until the platform kills it. Which execution limit should be set?

  1. Step Functions execution input/output paths
  2. Step Functions Choice state
  3. Lambda timeout setting
  4. Step Functions Catch transition
  5. Step Functions Map state

Explanation

Correct Answer

C:

A Lambda timeout caps the maximum duration of a single function invocation; in this scenario, set an appropriate function timeout and shorter client timeouts so hung dependencies do not hold capacity unnecessarily.

Incorrect Answers

A:

InputPath, ResultPath and OutputPath can shape data passed between workflow states; it would target retaining only relevant fields between processing tasks, while the question is about preventing a stalled serverless task from running indefinitely.

B:

A Choice state routes execution based on a condition in the state input; its benefit is selecting a branch after checking data type; that is different from preventing a stalled serverless task from running indefinitely.

D:

Catch handlers move execution to a recovery state when a configured task error occurs; this can support sending failed processing to a quarantine path, but would not address the need for preventing a stalled serverless task from running indefinitely.

E:

A Map state processes collection items using controlled parallel iterations in a workflow; this helps with applying the same transform to many independent input files, not preventing a stalled serverless task from running indefinitely.

Question 357

Error records in many Lambda log groups must reach a central normalization stream soon after emission. What feature routes them?

  1. CloudWatch Logs Insights
  2. CloudWatch subscription filter
  3. OpenSearch indexed log search
  4. CloudWatch metric filter
  5. Athena over structured S3 logs

Explanation

Correct Answer

B:

Log subscription filters send matching events from CloudWatch Logs to supported downstream consumers; in this scenario, configure subscription filters with the right delivery permissions and matching patterns rather than periodic full log exports.

Incorrect Answers

A:

Logs Insights searches and aggregates records in CloudWatch log groups with query syntax; the current need is for streaming selected application errors into a central processor, not interactively grouping recent Lambda exception events from CloudWatch log groups.

C:

OpenSearch can index log documents for search, filtering and operational dashboards; this helps with searching high-cardinality text patterns across indexed application logs, not streaming selected application errors into a central processor.

D:

A metric filter creates CloudWatch metric datapoints from matching CloudWatch Logs events; although useful for alerting on a distinctive application error pattern, it leaves the need for streaming selected application errors into a central processor unmet.

E:

Athena can query centrally stored S3 audit logs after their schema is represented in a catalog; it would target running SQL over accumulated S3 log archives, while the question is about streaming selected application errors into a central processor.

Question 358

A Glue log group retains high-volume debug events indefinitely and logging costs keep rising. What setting controls the lifecycle?

  1. CloudWatch dashboard
  2. CloudWatch custom metric
  3. CloudWatch Logs retention policy
  4. CloudWatch metric anomaly detection

Explanation

Correct Answer

C:

Log-group retention settings automatically remove old log events after an assigned retention period; in this scenario, set a retention period consistent with incident-response and audit requirements instead of storing all verbose logs forever.

Incorrect Answers

A:

A dashboard displays chosen service and custom metrics in a shared operational view; this helps with correlating stream lag with transformation failures, not controlling long-term storage of verbose ETL debug logs.

B:

Custom CloudWatch metrics record application-specific measurements not emitted by a service automatically; although useful for monitoring per-batch invalid record counts, it leaves the need for controlling long-term storage of verbose ETL debug logs unmet.

D:

Anomaly detection models a metric's historical range and alarms on unusual deviations; its benefit is catching unexpected deviations from a periodic pipeline pattern; that is different from controlling long-term storage of verbose ETL debug logs.

Question 359

A partner returns a nextPageToken with each response and new data appears while extraction runs. Which client design is important?

  1. ECS task role credential provider
  2. Boto3 paginator
  3. API response pagination contract
  4. SDK client retry configuration

Explanation

Correct Answer

C:

API consumers must follow service pagination and page-size contracts to avoid missing records; in this scenario, follow continuation tokens until completion and use a stable extraction watermark or snapshot where the API supports it.

Incorrect Answers

A:

The AWS SDK credential provider chain can obtain short-lived task-role credentials from an Amazon ECS task identity without static keys; the current need is for implementing a complete read of a partner's paginated REST feed, not authenticating a scheduled ECS data-container AWS SDK client without static keys.

B:

Boto3 paginators iterate AWS API responses that return continuation tokens and limited pages; this can support retrieving every object across paginated AWS API responses, but would not address the need for implementing a complete read of a partner's paginated REST feed.

D:

AWS SDK retry settings manage retry attempts and backoff for supported retryable API failures; although useful for handling transient AWS service throttling from ETL code, it leaves the need for implementing a complete read of a partner's paginated REST feed unmet.

Question 360

A custom uploader frequently fails before CompleteMultipartUpload and leaves billed incomplete parts. What cleanup rule addresses this?

  1. S3 Lifecycle noncurrent expiration
  2. S3 Object Lock retention
  3. S3 Lifecycle expiration
  4. S3 Lifecycle abort multipart upload

Explanation

Correct Answer

D:

A lifecycle rule can remove incomplete multipart-upload parts after a configured age; in this scenario, abort incomplete multipart uploads after a safe interval; this does not remove fully completed objects.

Incorrect Answers

A:

Noncurrent version expiration removes older object versions in versioned buckets according to policy; this can support cleaning up superseded object versions, but would not address the need for preventing orphaned upload parts from accumulating charges.

B:

S3 Object Lock enforces supported retention controls that can prevent object deletion during required periods; this helps with retaining evidence against premature deletion, not preventing orphaned upload parts from accumulating charges.

C:

Lifecycle expiration removes eligible objects automatically after conditions such as object age are met; although useful for deleting obsolete unversioned objects after a retention interval, it leaves the need for preventing orphaned upload parts from accumulating charges unmet.

AWS Certified Data Engineer - Associate DEA-C01 Practice Tests