UiPath-ADAv1 Exam Dumps - UiPath Certified Professional - Developer Track Questions and Answers

The code in the Invoke Code activity is looping through an array of integers and checking if the current value is greater than the previous value. If it is, the current value is stored in the output variable. Since the last value in the array is 9, this will be the final value of the output variable. (UiPath Studio - Invoke Code - UiPath Academy)

The Activities Guide is a comprehensive documentation of all the official UiPath activity packages that are available on the Official feed. The Activities Guide provides detailed information about each activity, such as the description, properties, examples, and compatibility. The compatibility section indicates which target frameworks are supported by the activity, such as Windows, Windows-Legacy, or Cross-platform. By browsing the Activities Guide, you can find a list of all the activities that support the Windows compatibility, as well as the minimum version required for each activity package.

The "Is Match Activity" is best suited to validate the format of a date stored in a string variable. This activity uses regular expressions (RegEx) to check if the string matches a specific pattern, which in this case would be the date format required by the custom form.

To create an array of folder names from the String variable FilePath, the method that will return an array of only the folder names is:

Split(FilePath,"").StringSplitOptions.RemoveEmptyEntries

This method uses the String.Split method, which returns an array of strings that are separated by a specified delimiter. The delimiter in this case is the backslash character ("") which is used to separate the folder names in the file path. The StringSplitOptions.RemoveEmptyEntries option is used to remove any empty entries from the resulting array, such as the one before the first backslash or after the last backslash1. For example, if the FilePath variable has the value:

FilePath = “C:\Users\UiPathRobot\Documents\Technologies”

Then the method Split(FilePath,"").StringSplitOptions.RemoveEmptyEntries will return an array of four strings:

{“C”, “Users”, “UiPathRobot”, “Documents”, “Technologies”}

These are the folder names in the file path, without any empty entries.

Understanding Variable Scope in UiPath

Variable scope defines where a variable is accessible within a workflow.

Using the narrowest possible scope is a best practice to avoid conflicts and unnecessary memory usage.

The For Each Row activity processes one row at a time, meaning variables like TimeOnThePlanet should be inside the loop's body, not at a higher scope.

Step-by-Step Breakdown of the Workflow:

Read Range Workbook Activity:

Reads the "NamesBirthdays.xlsx" file into dt_NamesBirthdays (DataTable).

Add Data Column Activity:

Adds a new column "Eligible" to dt_NamesBirthdays.

For Each Row in Data Table (dt_NamesBirthdays)

Processes each row of the DataTable.

Inside the Loop (Body of For Each Row):

TimeOnThePlanet and Age are assigned.

Formula:

TimeOnThePlanet = Date.Now.Date - Convert.ToDateTime(CurrentRow("DOB"))

Age = TimeOnThePlanet.Days / 365

If Condition (Age >= 18)

Assigns "Yes" to CurrentRow("Eligible").

Filter Data Table Activity:

Filters eligible voters and stores them in dt_NamesBirthdays.

Write Range Workbook Activity:

Writes dt_NamesBirthdays to "VotersNeedToBeRegistered.xlsx".

Why Option C (Correct Answer) Is the Best Choice

✅ "TimeOnThePlanet in scope: Body of For Each Row" is the correct choice because:

It is only needed inside the For Each Row loop.

The calculation TimeOnThePlanet = Date.Now.Date - Convert.ToDateTime(CurrentRow("DOB")) is done for each row individually.

Keeping it inside the loop reduces unnecessary memory allocation and ensures no unintended overwrites.

Why Other Options Are Incorrect

❌ A. "Age in scope: Sequence - Yes, Can Vote"

Incorrect because Age is used within the loop, not in the higher-level sequence.

Storing Age in a broader scope increases the risk of incorrect values being carried over between iterations.

❌ B. "Age in scope: Voter Registration"

Incorrect because Age is only needed in For Each Row, not the entire workflow.

Declaring it at the workflow level makes it accessible outside the loop unnecessarily.

❌ D. "dt_NamesBirthdays in scope: Body of For Each Row"

Incorrect because dt_NamesBirthdays is the main DataTable used across the workflow.

It should be declared at the workflow level (Voter Registration scope), not inside the loop.

Final Answer and Best Practice

✅ Correct Answer: C. TimeOnThePlanet in scope: Body of For Each Row

Best Practices for Variable Scope in UiPath:

Use the smallest possible scope needed for the variable.

Loop-specific variables (like TimeOnThePlanet) should be inside the loop.

DataTables and workflow-wide variables should be in the main sequence or workflow scope.

✅ Reference:

???? UiPath Documentation – Variables and Scope

???? UiPath Best Practices – Efficient Variable Management

The correct workflow name, based on best practices, is ScrapeFilteredStocks. This is because it follows the Pascal Case convention, which means that the first letter of each word is capitalized and there are no spaces or underscores between the words. This convention makes the workflow name easy to read and understand, as well as consistent with the UiPath standards. The other workflow names are incorrect because they either use lower case, snake case, or have no meaningful description. For example, Transactionstatus should be TransactionStatus, Workflow1 should be more descriptive, and creation_of_file should be CreationOfFile.

Understanding the Expression:

The expression DT.Rows(0)(1).ToString + DT.Rows(1)(0).ToString retrieves values from the DataTable using row and column indexes:

DT.Rows(0)(1).ToString → This refers to Row 0, Column 1:

Row 0: "Michael" (Column 0), 42 (Column 1)

Column 1 (Index 1) in Row 0 = 42

Result: "42"

DT.Rows(1)(0).ToString → This refers to Row 1, Column 0:

Row 1: "Clara" (Column 0), 25 (Column 1)

Column 0 (Index 0) in Row 1 = "Clara"

Result: "Clara"

Concatenating the Results:

"42" + "Clara" = "42Clara"

✅ Final Output: "42Clara"

Why Other Options Are Incorrect:

❌ A. MichaelClara → Incorrect because "Michael" is at DT.Rows(0)(0), not DT.Rows(0)(1).

❌ C. 42Michael → Incorrect because "Michael" is at DT.Rows(0)(0), but we are accessing DT.Rows(1)(0), which is "Clara".

❌ D. 25Clara → Incorrect because 25 is at DT.Rows(1)(1), but we are accessing DT.Rows(0)(1), which is 42.

Final Answer and Output:

✅ Answer: B. 42Clara

✅ Reference:

???? UiPath Documentation – DataTable Manipulation

???? UiPath - Working with Rows and Columns

In UiPath Studio, when creating a variable, the "Default" field is optional. The "Default" field is where you can assign an initial value to the variable, which it will hold until changed during the execution of the workflow. The "Variable type" must be specified to determine what kind of data the variable will hold. The "Name" is required to reference the variable within the workflow, and the "Scope" determines where the variable can be accessed from within the project.

UiPath arguments allow data to be passed between workflows.

In Arguments (In):

Accepts variables or hard-coded values.

Used to pass input values to the invoked workflow.

Out Arguments (Out):

Can only be variables (not hard-coded values).

Used to retrieve values from the invoked workflow.

In/Out Arguments (In/Out):

Can only be variables.

Used to pass and modify data within the workflow.

Why is B Correct?

✅ Follows UiPath's argument behavior:

In: Accepts variables or hard-coded values.

Out: Only variables (because values are returned dynamically).

In/Out: Only variables (since it modifies and returns the same variable).