Answer: Lookup, ForEach

## Detailed Explanation ### Requirements Analysis To solve this scenario effectively, we need to: 1. **Read the table names** from File1.txt to parameterize the Copy activity 2. **Execute multiple Copy activities in parallel** for optimal performance ### Selected Activities Analysis **B. Lookup Activity** - The Lookup activity is specifically designed to retrieve dataset contents from various sources including files in Azure Storage - It can read the content of File1.txt and return the table names as an array output - This output can then be passed as parameters to subsequent activities - Lookup is ideal for reading configuration files like File1.txt that contain metadata (table names in this case) **C. ForEach Activity** - ForEach enables iteration over the array of table names retrieved by the Lookup activity - When configured with parallel execution (sequential turned off), it can run multiple Copy activities simultaneously - Each iteration can pass a different table name as a parameter to the Copy activity - This satisfies the parallel execution requirement by allowing multiple table copies to occur concurrently ### Why These Options Are Optimal **Lookup + ForEach Combination:** - **Lookup** retrieves the dynamic list of tables from the configuration file - **ForEach** iterates through this list and executes Copy activities in parallel - This creates a parameterized, scalable solution where adding/removing tables only requires updating File1.txt ### Why Other Options Are Less Suitable **A. Get Metadata Activity:** - Get Metadata is designed to retrieve metadata about datasets (file properties, schema, etc.) - It cannot read the actual content of files like File1.txt - It's useful for checking file existence, size, or last modified date, but not for reading file contents **D. If Condition Activity:** - If Condition is for conditional branching in pipelines based on expressions - It doesn't help with reading file contents or enabling parallel execution - While it could be used for conditional logic within the pipeline, it doesn't address the core requirements of this scenario ### Implementation Workflow 1. **Lookup Activity**: Reads File1.txt and outputs an array of table names 2. **ForEach Activity**: Iterates through the table names array with parallel execution enabled 3. **Copy Activity (inside ForEach)**: Parameterized to use the current table name for both source (DB1 table) and destination (storage1 file) This architecture ensures maximum parallelization while maintaining parameterization based on the configuration file.

Author: LeetQuiz Editorial Team