→ It can be used to pass output of one activity to input for another activity.
→ every variable has defined scope, we can check the option in the variables panel.
2&4 are incorrect.
→ variable doesn’t have the directions, the directions is for arguments.
→ For creating a variable we cannot drag and drop an activity to designer panel and create a variable. We can create variables in the variable panel itself.
Option1 and Option3 are correct
→ The variables are used to pass the data between activities.
→ The scope plays the crucial role because the variable can be used to pass the data within the defined scope of the variable.
In the case as shown as below then Option4 is also correct.
→ Without a single activity in the designer panel the variable can’t get created.
1, 3 and 4 are correct. The question is trying to confuse you between variables and arguments. 2 applies to arguments, not variables.
The reason 4 is correct is because of 3. You have to define a scope for a variable, and a scope means a Sequence activity within which the variable is created.
That’s not what 4 says. It’s not asking about how/where you create variables. 4 says there must be an activity in your automation before you can create variables, and this is correct. Because without at least one Sequence activity, there is nothing to scope the variable to.
Actually I disagree with option A.
Yes they ‘can’ be used to pass data in between activities, but they might as well not do that. (Would make them completely redundant, but I can create a variable b_IsItRaining with a default to false and then not use the variable. Useless I know, but that does make answer 1 tricky, and possibly false )