Answer: event

## Explanation For this scenario where an Azure Data Factory pipeline needs to execute when a new file arrives in an Azure Data Lake Storage Gen2 container, the **Event trigger** is the appropriate choice. ### Why Event Trigger is Correct: - **Event-driven architecture**: The Event trigger is specifically designed to respond to events in Azure services, including blob storage events from Azure Data Lake Storage Gen2 - **File arrival detection**: When configured with Azure Event Grid, the Event trigger can monitor for specific blob storage events such as 'Blob Created' or 'Blob Deleted' - **Real-time processing**: This trigger enables immediate pipeline execution when new files are detected, supporting real-time data processing scenarios - **Storage event integration**: Azure Data Lake Storage Gen2 integrates seamlessly with Event Grid, allowing automatic triggering when files are added, modified, or deleted ### Why Other Options Are Less Suitable: - **On-demand trigger**: This requires manual execution and doesn't automatically respond to file arrivals - **Tumbling window trigger**: This is designed for periodic, fixed-interval processing (e.g., every 15 minutes) rather than event-driven file detection - **Schedule trigger**: This operates on a fixed time-based schedule (hourly, daily, etc.) and cannot detect or respond to individual file arrival events The Event trigger provides the most efficient and responsive solution for file-based processing workflows in Azure Data Factory, ensuring pipelines execute precisely when new data becomes available.

Author: LeetQuiz Editorial Team