You have an Azure Factory instance named DF1 that contains a pipeline named PL1.PL1 includes a tumbling window trigger. You create five clones of PL1. You configure each clone pipeline to use a…

Question

Options

• AAdd a new trigger to each cloned pipeline
• BAssociate each cloned pipeline to an existing trigger.
• CCreate a tumbling window trigger dependency for the trigger of PL1.
• DModify the Concurrency setting of each pipeline.

• A
  7% (3)
• B
  76% (32)
• C
  2% (1)
• D
  14% (6)

Explanation

Associating each cloned pipeline to the existing tumbling window trigger on PL1 (option B) is the correct approach because a single trigger can drive multiple pipelines simultaneously, ensuring all clones fire on exactly the same schedule without any configuration drift.

Why the distractors are wrong:

• A - Creating a new trigger for each clone would produce independent triggers that could easily diverge from PL1's schedule and introduces unnecessary management overhead.
• C - A tumbling window trigger dependency controls the order of execution between triggers (upstream/downstream chaining), not schedule synchronization - it solves a sequencing problem, not a schedule-matching problem.
• D - The Concurrency setting controls how many simultaneous runs of a single pipeline are allowed; it has no effect on when pipelines are scheduled to run.

Memory tip: Think of a trigger as a "broadcast signal" - one signal can wake up many pipelines at once. If you want clones to march in lockstep with the original, plug them all into the same trigger rather than giving each one its own clock.

No community discussion yet for this question.