DEA-C01 Data Operations and Support Practice Question
A data engineer notices that an AWS Glue ETL job that processes streaming data from Amazon Kinesis Data Streams is failing intermittently with a 'ResourceNotFoundException' error for the Kinesis stream. The job has been running successfully for weeks. Which action should the engineer take to resolve the issue?
⚠ Common exam trap
The trap is assuming 'ResourceNotFoundException' always means the resource is missing or misnamed — in AWS, permission denials are frequently masked as not-found errors, so candidates who jump to renaming or recreating resources miss the IAM root cause.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Add the 'kinesis:DescribeStream' permission to the IAM role used by the Glue job.
A 'ResourceNotFoundException' from a Glue job reading Kinesis typically indicates the Glue execution role lacks permission to describe or access the stream, causing the service to report the stream as not found rather than as access-denied. Adding 'kinesis:DescribeStream' (and typically DescribeStreamSummary, GetShardIterator, GetRecords) to the IAM role resolves the issue. Since the job ran successfully for weeks, a recent IAM policy change or role modification is the likely trigger.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the number of shards in the Kinesis data stream to handle higher throughput.
Why it's wrong here
Adding shards addresses throughput capacity, not a ResourceNotFoundException, which indicates the stream name or ARN in the Glue connection no longer resolves. Shard count does not affect name resolution. Resharding is the right action when the job lags behind Kinesis throughput or hits per-shard read limits.
- ✗
Rename the Kinesis data stream to match the stream name used in the Glue job exactly, including case.
Why it's wrong here
Renaming a stream does not fix a ResourceNotFoundException that appeared after weeks of successful runs; the stream name already matched. The error stems from the stream being deleted or recreated with a new ARN, or the connection pointing at a stale endpoint. Renaming would matter only during initial misconfiguration.
- ✓
Add the 'kinesis:DescribeStream' permission to the IAM role used by the Glue job.
Why this is correct
Missing DescribeStream permission causes intermittent resource not found errors.
- ✗
Increase the timeout for the Glue job in the job configuration.
Why it's wrong here
Job timeout governs how long a run may execute before being stopped; it has no bearing on resolving a Kinesis stream name or ARN, so the ResourceNotFoundException persists. Raising the timeout is appropriate when jobs exceed the default duration, not when the referenced stream cannot be found.
Visual reference
Go deeper
Related to this question
About these practice questions
This DEA-C01 question is part of Courseiva's 1,321-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Amazon Web Services exam blueprint
This DEA-C01 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DEA-C01 exam.