Answer: tumbling window

## Detailed Analysis of Trigger Selection Based on the requirements for Pipeline1, the **tumbling window trigger** is the optimal choice for several key reasons: ### ✅ Why Tumbling Window Trigger (Option D) is Correct 1. **Fixed Window Processing**: Tumbling window triggers are specifically designed for processing data in fixed, non-overlapping time intervals (30 minutes in this case), which aligns perfectly with the requirement to execute every 30 minutes. 2. **Backfill Capability**: Tumbling window triggers natively support backfill scenarios. When you create the trigger, you can specify a start date in the past, and Azure Data Factory will automatically create and execute windows from that start date up to the current time, satisfying the requirement to backfill data from the beginning of the day. 3. **Re-execution Within Same Window**: If Pipeline1 fails, the tumbling window trigger allows for re-execution within the same 30-minute window period. Failed window executions can be manually retriggered or configured for automatic retry. 4. **Built-in Concurrency Control**: Tumbling window triggers have built-in concurrency controls that ensure only one instance of the pipeline runs for a given window period, preventing overlapping executions. 5. **Offset Support**: The 15-minute offset requirement is directly supported through the trigger's offset property, which delays the start of each window by the specified duration. ### ❌ Why Other Options Are Less Suitable - **Schedule Trigger (A)**: While schedule triggers can run every 30 minutes, they lack native backfill capabilities and require manual configuration for historical data processing. They also don't provide the same level of window-based execution guarantees. - **Event-based Trigger (B)**: This trigger responds to external events rather than fixed time intervals, making it unsuitable for the regular 30-minute execution requirement. - **Manual Trigger (C)**: Manual triggers require human intervention for each execution, which contradicts the automated, scheduled nature of the requirement and would significantly increase operational overhead. ### Configuration Efficiency The tumbling window trigger minimizes development effort because it provides all required functionality out-of-the-box: fixed interval execution, offset support, backfill capabilities, and concurrency control without requiring additional custom logic or complex configurations.

Author: LeetQuiz Editorial Team