UiPath-ADAv1 Studio Interface and Variables Practice Question
Exhibit
Error: Variable 'InvoiceNumber' is not defined in the current scope. Sequence 'Process_Invoices' (Scope: Root) Sequence 'Extract_Data' (Scope: Process_Invoices) Sequence 'Write_To_Excel' (Scope: Extract_Data)
Refer to the exhibit. You are trying to use the variable 'InvoiceNumber' in the 'Write_To_Excel' sequence, but it was defined in the 'Process_Invoices' sequence. Why is the error occurring?
⚠ Common exam trap
Candidates often forget that variable scope is strictly hierarchical; they assume that defining a variable anywhere in a workflow makes it globally accessible throughout the entire project file.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The scope of 'InvoiceNumber' is likely restricted to 'Extract_Data' and cannot be accessed from 'Write_To_Excel'.
In UiPath, variables follow nested scoping rules. A variable defined in a parent container (Process_Invoices) is generally available to child containers (Extract_Data, Write_To_Excel). However, if the variable was defined with a narrower scope inside an intermediate sequence that did not encompass the destination, or if there is a conflict, the variable becomes unreachable. This error highlights the importance of hierarchical scope management in complex workflows.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Variables defined in parent sequences are automatically deleted after the first child sequence completes.
Why it's wrong here
Variable lifecycles persist as long as the parent sequence is executing. They are not automatically deleted upon the completion of child sequences. The issue is strictly related to the visibility/scope definition and whether the variable was correctly initialized within the hierarchy to be visible to the specific target activity.
- ✗
The variable 'InvoiceNumber' must be passed explicitly as an argument to every child sequence.
Why it's wrong here
While passing data via arguments is a best practice for modularization and reusability, it is not strictly required for a variable to be accessible in a nested sequence. A variable defined in a parent scope is naturally accessible to all child activities, provided the scope was correctly set during creation.
- ✓
The scope of 'InvoiceNumber' is likely restricted to 'Extract_Data' and cannot be accessed from 'Write_To_Excel'.
Why this is correct
If the variable was defined within the 'Extract_Data' sequence, it is limited to the scope of that sequence and its own children. If 'Write_To_Excel' was moved or configured incorrectly, it might have lost access to the scope where 'InvoiceNumber' exists, causing the compiler to throw this undefined variable error.
- ✗
The variable name is case-sensitive and does not match the declaration.
Why it's wrong here
Variable names in UiPath are indeed case-sensitive; however, the error message indicates that the variable is 'not defined in the current scope,' which specifically points to a hierarchy or access issue rather than a simple naming convention mismatch, which would typically report a typo or identifier error instead.
About these practice questions
One of 285 original UiPath-ADAv1 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official UiPath exam blueprint
This UiPath-ADAv1 practice question is part of Courseiva's free UiPath certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the UiPath-ADAv1 exam.