Orchestrate Python and Bash Scripts with Least Overhead

Answer Correct answer: B — Amazon Managed Workflows for Apache Airflow (MWAA) enables migration of existing orchestration workflows without refactoring code or managing servers.

An ecommerce company wants to use AWS to migrate data pipelines from an on-premises environment into the AWS Cloud. The company currently uses a third-party tool in the on-premises environment to orchestrate data ingestion processes. The company wants a migration solution that does not require the company to manage servers. The solution must be able to orchestrate Python and Bash scripts. The solution must not require the company to refactor any code. Which solution will meet these requirements with the LEAST operational overhead?

  1. AWS Lambda
  2. Amazon Managed Workflows for Apache Airflow (Amazon MVVAA) Correct Answer
  3. AWS Step Functions
  4. AWS Glue

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

This question tests the ability to select a managed orchestration service that maintains compatibility with legacy on-premises workflows while eliminating server management overhead.

Amazon Managed Workflows for Apache Airflow (MWAA) is the correct choice for migrating existing orchestration tools to AWS without refactoring code or managing servers. It natively supports Python and Bash scripts, ensuring a seamless migration.

Many candidates choose AWS Step Functions because it is a fully managed, serverless workflow service. However, Step Functions requires rewriting logic into its specific JSON state machine format, which violates the requirement to not refactor any code.

Community Discussion (5 comments)

HunkyBunky 👍 2 Selected: B
B - because company want to use same tool on premises and least operational overhead
didorins 👍 1 Selected: C
"The company wants a migration solution that does not require the company to manage servers.". How is it Amazon Managed Workflows for Apache Airflow and not Step Functions when Step Functions is the serverless of the two ?
Ja13 👍 3 Selected: B
An ecommerce company wants to use AWS to migrate data pipelines from an on-premises environment into the AWS Cloud. The company currently uses a third-party tool in the on-premises environment to orchestrate data ingestion processes. The company wants a migration solution that does not require the company to manage servers. The solution must be able to orchestrate Python and Bash scripts. The solution must not require the company to refactor any code. Which solution will meet these requirements with the LEAST operational overhead? A. AWS Lambda B. Amazon Managed Workflows for Apache Airflow (Amazon MVVAA) C. AWS Step Functions D. AWS Glue
HunkyBunky 👍 1 Selected: B
B - best fits in task requirements
Bmaster 👍 2
My Choice is B

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Amazon Managed Workflows for Apache Airflow (MWAA) allows organizations to run Apache Airflow on AWS without managing the underlying infrastructure. Since the company currently uses a third-party tool to orchestrate ingestion (likely an Airflow-based or similar DAG-driven system), MWAA provides a direct path for migration. It natively executes Python and Bash scripts as tasks within these DAGs, satisfying the requirement to avoid code refactoring. The 'managed' aspect ensures there is no operational overhead for patching or scaling the orchestrator.

Why the Other Options Are Wrong

AWS Lambda (A) is compute, not orchestration; it cannot easily manage complex dependencies between multiple scripts without external tooling. Amazon Step Functions (C) is a serverless orchestration service, but it requires defining workflows using AWS-specific JSON state definitions. This necessitates refactoring existing Python/Bash execution logic into Step Functions' structure, violating the 'no refactor' constraint. AWS Glue (D) is primarily for ETL data transformation and job scheduling, not general-purpose orchestration of arbitrary Python and Bash scripts in the same flexible manner as Airflow.

Community Comment Notes

The community heavily favored option B, aligning with the exam's focus on 'orchestration' over generic 'serverless'. One comment highlighted the key constraint: "because company want to use same tool on premises and least operational overhead", emphasizing the migration aspect. Another user questioned why Step Functions wasn't chosen due to its serverless nature, noting that while it manages servers, it fails the architectural compatibility test for existing scripts. As HunkyBunky noted, MWAA is the best fit for task requirements involving script orchestration without code changes.

Official Reference

Exam Strategy

When a question mentions 'migration' from an on-premises environment and explicitly forbids 'refactoring', look for the AWS managed service that replicates the functionality of the legacy tool. If the legacy tool involves DAGs or Python/Bash scripting, MWAA is often the answer. If the requirement was purely 'serverless compute', Lambda would be considered, but 'orchestration' points to Step Functions or MWAA.

Frequently Asked Questions

Why not AWS Step Functions for orchestration?

Step Functions requires rewriting workflows into JSON state machines, forcing code refactoring. MWAA supports existing Python/Bash DAGs directly.

Does MWAA require managing servers?

No, MWAA is a managed service where AWS handles the infrastructure, allowing you to focus only on your workflow code.

More DEA-C01 FAQ →

Related Analysis

Practice All DEA-C01 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DEA-C01 Practice Test →

← Back to DEA-C01 Study Guide