DEA-C01 Data Ingestion and Transformation Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Use a JDBC connection with the Redshift cluster endpoint, database name, and a database user credential stored in AWS Secrets Manager.

  Why it's wrong here

  A JDBC connection with a Secrets Manager credential provides authentication and connectivity but does not by itself enable Redshift's COPY-based parallel unload/load optimization. The Glue job would still need a Redshift connection type to leverage the Redshift Data API or COPY command with an IAM role. This approach also bypasses the IAM role integration that Glue uses for Redshift, so it does not meet the parallel loading and IAM authentication requirement.

• ✗

  Configure an AWS Glue connection of type JDBC with the Redshift JDBC URL and set the 'redshift_tmp_dir' parameter to an S3 path, using a database password stored in AWS Glue.

  Why it's wrong here

  A JDBC connection with a temporary S3 directory can support Redshift COPY operations, but it relies on a database password rather than an IAM role for authentication. Storing the password in AWS Glue is less secure and does not satisfy the IAM-based authentication requirement. Additionally, this method does not automatically enable the parallel loading behavior that Glue provides with a native Redshift connection type and IAM role integration.

• ✓

  Create an AWS Glue connection of type Amazon Redshift, specify the cluster, database, and an IAM role with permissions to access both S3 and Redshift, and enable the 'Use Redshift COPY' option.

  Why this is correct

  An AWS Glue connection of type Amazon Redshift with an attached IAM role allows Glue to use the Redshift COPY command with temporary S3 staging, which parallelizes data loading across Redshift slices. The IAM role provides authentication without embedding database credentials. Enabling the Redshift COPY option directs Glue to stage data in S3 and issue a COPY command, which is the documented way to achieve parallel, IAM-authenticated loads from Glue to Redshift.

• ✗

  Use an AWS Glue connection of type Amazon S3 and configure the Redshift cluster endpoint in the job's script using boto3.

  Why it's wrong here

  An S3 connection type only provides access to S3; it does not establish a Redshift connection or enable the COPY-based parallel load. Configuring the endpoint in the script with boto3 may allow programmatic access, but it does not leverage Glue's native Redshift integration, IAM role pass-through, or the parallel staging mechanism. This approach also requires managing credentials manually, which contradicts the IAM authentication requirement.

Go deeper

Related to this question