DEA-C01 Data Ingestion and Transformation Practice Question

Order the steps to troubleshoot a failed AWS Glue job that reads from JDBC and writes to S3.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

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

✓

Check AWS Glue job logs, then verify network connectivity, then verify IAM permissions, then test JDBC connection, then review the Glue script.

Start with logs to identify errors, then check connectivity, IAM permissions, test connection, and review script.

Answer analysis

For each option: why learners choose it and why it is or isn't the right answer here.

✓
Check AWS Glue job logs, then verify network connectivity, then verify IAM permissions, then test JDBC connection, then review the Glue script.
Why this is correct
This is the correct order because you start with logs to identify the error, then systematically check connectivity, permissions, connection, and script to isolate the issue.
✗
Verify IAM permissions, then check AWS Glue job logs, then verify network connectivity, then test JDBC connection, then review the Glue script.
Why it's wrong here
This is incorrect because checking IAM before logs may waste time if the error is not permission-related; logs should always be first to identify the specific error.
✗
Test JDBC connection, then check AWS Glue job logs, then verify network connectivity, then verify IAM permissions, then review the Glue script.
Why it's wrong here
This is incorrect because testing connection without first checking logs may miss the actual error; logs provide context for what failed.
✗
Review the Glue script, then check AWS Glue job logs, then verify network connectivity, then verify IAM permissions, then test JDBC connection.
Why it's wrong here
This is incorrect because script review should be last after confirming environment issues; starting with script may overlook connectivity or permission problems.

Quick reference

Storage Class	Min Duration	Retrieval	Use Case
S3 Standard	None	Immediate	Frequently accessed data
S3 Standard-IA	30 days	Immediate	Infrequent access, rapid retrieval
S3 One Zone-IA	30 days	Immediate	Non-critical infrequent data
S3 Intelligent-Tiering	None	Immediate–hours	Unknown or changing access patterns
S3 Glacier Instant	90 days	Milliseconds	Archive with instant retrieval
S3 Glacier Flexible	90 days	Minutes–hours	Archive, flexible retrieval
S3 Glacier Deep Archive	180 days	Hours	Long-term compliance archive

Go deeper