UiPath-ADAv1 Exam Dumps - UiPath Automation Developer Associate Exam (2023.10)

The REFramework is a template that provides a structured and consistent way to develop automation processes using state machines. The REFramework has four main states: Initialization, Get Transaction Data, Process Transaction, and End Process. Each state performs a specific function and transitions to another state based on the outcome. When a developer runs a process using the REFramework, with the process utilizing Orchestrator queues and a queue already created with the Name provided and the Auto Retry function disabled, the following states will be executed without errors:

Initialization: This state is used to initialize the application, read the configuration data, and log in to Orchestrator. If the initialization is successful, the state transitions to Get Transaction Data; otherwise, it transitions to End Process. (UiPath ReFramework documentation1)

Get Transaction Data: This state is used to retrieve a transaction item from the Orchestrator queue and assign it to a variable. If there is a transaction item available, the state transitions to Process Transaction; otherwise, it transitions to End Process. (UiPath ReFramework documentation1)

Process Transaction: This state is used to execute the business logic for the current transaction item and handle any exceptions that may occur. If the transaction is successful, the state updates the status of the transaction item to Successful and transitions to Get Transaction Data; if the transaction fails due to a business exception, the state updates the status of the transaction item to Failed and transitions to Get Transaction Data; if the transaction fails due to a system exception, the state updates the status of the transaction item to Failed and retries the transaction based on the MaxRetryNumber parameter from the Config file. If the retry limit is reached, the state transitions to End Process; otherwise, it transitions to Get Transaction Data. (UiPath ReFramework documentation1)

End Process: This state is used to close all applications, log out of Orchestrator, and terminate the process. This state does not have any transition. (UiPath ReFramework documentation1)

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 "Share File/Folder" activity in the Microsoft 365 package is used to share a SharePoint file or folder URL with a specific user while defining access permissions.

This activity allows setting view/edit permissions and sending notifications to the recipient.

Example usage:

- Input: File URL, Email ID, Permission Type (View/Edit)

- Output: Shared link

Other options are incorrect:

A (Upload File) is used to store new files in SharePoint.

B (Move File/Folder) moves files or folders within SharePoint.

C (Get File/Folder) retrieves file details but does not handle sharing.

✅ Reference: UiPath Microsoft 365 Activities - Share File/Folder

Comprehensive and Detailed In-Depth Explanation:

When a UiPath bot tries to read an Excel file that is open in another application, it encounters an IOException (Input/Output Exception).

Step-by-Step Execution Guide: Handling IOException in UiPath

1️⃣ Try to Read an Open Excel File

vb

CopyEdit

Read Range Workbook: "Employees.xlsx"

2️⃣ If the file is already open, IOException occurs

3️⃣ The "IOException" Catch Block Handles the Error

Real-World Use Case: Ensuring File Availability Before Reading

📌 Scenario:

A bot is scheduled to read employee records every morning at 8 AM.

✔ If an employee accidentally leaves the Excel file open, the bot will fail.

✔ To prevent failure, the bot:

Tries to read the file.

If IOException occurs, sends an email alert instead of failing.

vb

CopyEdit

Try

Read Range Workbook: "Employees.xlsx"

Catch ex As IOException

Send Email: "Please close the Employees file!"

🚀 This makes the automation resilient!

Why the other options are incorrect?

❌ A. None – An exception will occur if the file is open.

❌ C. BusinessRuleException – This is for custom business logic errors, not file access issues.

❌ D. Exception – The IOException block specifically catches this error before reaching the generic Exception block.

✅ Reference:

UiPath Documentation: Handling Exceptions