Free Microsoft Data Engineering DP-700 Actual Exam Questions - Question 14 Discussion
HOTSPOT You are building a data orchestration pattern by using a Fabric data pipeline named Dynamic Data Copy as shown in the exhibit. (Click the Exhibit tab.) 
Dynamic Data Copy does NOT use parametrization. You need to configure the ForEach activity to receive the list of tables to be copied. How should you complete the pipeline expression? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. 
I agree using @variables('tables') fits best here since no parameters are allowed. Just make sure the variable is initialized beforehand, or ForEach won’t have any tables to iterate over.
Using @variables('tables') fits since no params allowed; just ensure variable’s set first.
I think using @variables('tables') makes the most sense here since the pipeline can’t use parameters. Just need to make sure some activity sets that variable with the table list before the ForEach starts.
If there’s no parameter, it makes sense to use a variable for the table list, so @variables('tables') is probably right. Just need to confirm the variable is set before the ForEach runs.
I’d go with @variables('tables') since there’s no parameter, and the variable should hold the table list. The tricky part is making sure ‘tables’ is actually set beforehand, though.
Makes sense to pick @variables('tables') since no parameters are involved. It fits the scenario where the list is stored in a variable for the ForEach to iterate over. Alternative like @pipeline().parameters won't work here.
Since the pipeline doesn’t use parameters, the list must come from a variable. So @variables('tables') in ForEach makes sense because variables can hold the list without needing parameters.
Since the question states no parametrization is used, that rules out pipeline parameters, so the ForEach activity should get its list from a pipeline variable. The expression looks like it needs @variables('tables') to fetch the array of tables. That fits with how variables store dynamic data inside a pipeline without external parameters. Using @variables('tables') makes sense here because it matches the "no parametrization" condition and provides the needed list for iteration in ForEach.
I think the key is that Dynamic Data Copy doesn't use parametrization, so we can rule out pipeline parameters here. Instead, the ForEach activity should get the list from a variable that’s already set in the pipeline. That means using something like variables('tables') for the expression. Since variables hold runtime data and tables list is dynamic, this fits better than parameters or dataset properties. So I'd go with using @variables('tables') in the expression to feed ForEach its list of tables to copy.
I’d pick the pipeline parameter option since variables usually require an explicit set or init, and they mentioned no parametrization is used. So probably using @pipeline().parameters.tables makes more sense here.
Looks like the expression should pull the table list directly from a pipeline variable or parameter array.
Seen a similar setup before, pretty sure it's about passing arrays in ForEach.