Question 10 of 506
Automating and orchestrating ML pipelineshardMultiple ChoiceObjective-mapped

Quick Answer

The answer is to optimize DAG files by avoiding heavy top-level imports and database queries, as this directly reduces DAG parsing time in Cloud Composer. This is correct because the Airflow scheduler parses every DAG file frequently—by default every 30 seconds—and any import or query at the top level of the file is executed during each parse cycle, creating a bottleneck. By moving imports inside Python callables or using lazy loading, you ensure that expensive operations run only when a task actually executes, not during parsing. On the Google Professional Machine Learning Engineer exam, this concept tests your understanding of Airflow’s scheduler architecture and its impact on ML pipeline orchestration performance. A common trap is to focus on optimizing task execution time rather than parsing time, or to mistakenly add more workers. Remember the mnemonic: “Lazy imports, speedy parsing”—keep heavy code out of the top-level scope to let the scheduler breathe.

PMLE Automating and orchestrating ML pipelines Practice Question

This PMLE practice question tests your understanding of automating and orchestrating ml pipelines. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A team uses Cloud Composer to orchestrate a complex ML pipeline with many tasks. They notice that the DAG parsing time is very high, causing delays in task scheduling. Which action would most effectively reduce DAG parsing time?

Question 1hardmultiple choice
Full question →

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

Optimize DAG files to avoid heavy top-level imports and database queries

Option C is correct because heavy top-level imports and database queries in DAG files are executed every time the scheduler parses the DAG, which happens frequently (default every 30 seconds). By moving imports inside Python callables or using lazy loading, the parsing time is drastically reduced, allowing the scheduler to process DAGs faster and trigger tasks without delay.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

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

  • Remove all DAG files that are not currently needed from the bucket

    Why it's wrong here

    This reduces the number of DAGs parsed, but optimizing each DAG's top-level code is more effective.

  • Increase the parallelism of the Airflow scheduler

    Why it's wrong here

    Scheduler parallelism affects execution, not DAG parsing.

  • Optimize DAG files to avoid heavy top-level imports and database queries

    Why this is correct

    Top-level imports/queries are executed on every parse, so reducing them speeds up parsing.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Combine all DAGs into a single file

    Why it's wrong here

    A single large file may still have heavy parsing; separating DAGs doesn't help much.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Google Cloud often tests the misconception that reducing the number of DAG files or increasing scheduler resources will fix parsing delays, when the real bottleneck is the top-level code execution inside each DAG file.

Detailed technical explanation

How to think about this question

Under the hood, the Airflow scheduler parses each DAG file in a subprocess (or using the `DagFileProcessorManager`) to build the DAG object graph. Top-level imports cause Python to execute the entire import chain, including database connections (e.g., SQLAlchemy engines) or heavy library loads (e.g., TensorFlow, PyTorch), every parse cycle. In real-world scenarios, a team with 50+ DAGs each importing `pandas` and `scikit-learn` at the top level can see parse times exceeding 60 seconds, causing the scheduler to miss its heartbeat and trigger false 'scheduler is not healthy' alerts.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related PMLE practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free PMLE practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this PMLE question test?

Automating and orchestrating ML pipelines — This question tests Automating and orchestrating ML pipelines — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Optimize DAG files to avoid heavy top-level imports and database queries — Option C is correct because heavy top-level imports and database queries in DAG files are executed every time the scheduler parses the DAG, which happens frequently (default every 30 seconds). By moving imports inside Python callables or using lazy loading, the parsing time is drastically reduced, allowing the scheduler to process DAGs faster and trigger tasks without delay.

What should I do if I get this PMLE question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 30, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This PMLE practice question is part of Courseiva's free Google Cloud 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 PMLE exam.