Amazon Web Services Data-Engineer-Associate Exam With Confidence Using Practice Dumps

The FLEX execution class allows you to run AWS Glue jobs on spare compute capacity instead of dedicated hardware. This can reduce the cost of running non-urgent or non-time sensitive data integration workloads, such as testing and one-time data loads. The FLEX execution class is available for AWS Glue 3.0 Spark jobs. The other options are not as cost-effective as FLEX, because they either use dedicated resources (STANDARD) or do not affect the cost at all (Spot Instance type and GlueVersion). References:

Introducing AWS Glue Flex jobs: Cost savings on ETL workloads

Serverless Data Integration – AWS Glue Pricing

AWS Certified Data Engineer - Associate DEA-C01 Complete Study Guide (Chapter 5, page 125)

Option C best matches the requirement of no new code with least operational effort because it keeps the analyst’s work inside the AWS-native, visual ETL experience and produces standardized outputs that data engineers can extend. The study material emphasizes that AWS provides visual data preparation capabilities that let users “clean and normalize data without writing any code,” which is exactly what the analyst needs before advanced engineering transformations begin.

Option A requires Python and Pandas, which directly violates the “does not require writing new code” requirement and introduces dependency management and debugging overhead. Option B uses multiple services (Canvas + Data Wrangler + Glue), which increases the number of moving parts, permissions, handoffs, and operational surface area compared to a single-service preparation approach. Option D offloads the entire preparation step to engineers, which increases operational effort and delays because the analyst cannot directly implement and iterate on standardization.

Using recipe-style transformations in the Glue visual interface aligns with the documented goal of simplifying data preparation workflows while enabling the engineering team to add more complex steps later in the pipeline.

Option A is the best answer because AWS DMS documentation recommends that, when practical, you create the replication instance in the same Region as your target endpoint, and in the same VPC or subnet as your target endpoint. In this scenario, the target is the Amazon Redshift cluster in eu-west-1 in Account_B, so placing the replication instance there is the most appropriate design. AWS DMS uses the replication instance to connect to the source, read the source data, transform it as needed, and load it into the target.

This also makes architectural sense because the replication instance must have network connectivity to both endpoints, and colocating it with the Redshift target usually simplifies connectivity to the target warehouse and aligns with AWS guidance. A replication instance in Account_B, eu-west-1 can still connect to the PostgreSQL source in Account_A, eu-east-1, provided the required networking and permissions are configured. AWS DMS supports replication tasks by defining a replication instance plus source and target endpoints.

The study guide also identifies AWS DMS as the correct managed service for database migration and continuous replication scenarios, including full load and change data capture. That matches this cross-account, cross-Region migration use case.