UiPath-ADAv1 UiPath Automation Developer Associate Exam (2023.10) Free Practice Exam Questions (2025 Updated)

To filter rows in a DataTable based on a condition (e.g., Quantity > 500), the best activity to use is Filter Data Table.

Why is Option D Correct?

Filter Data Table allows filtering rows based on specific conditions (e.g., Quantity > 500).

It can be configured via UI settings or using expressions in the advanced filter options.

The result is stored in a new or existing DataTable.

Example Usage in UiPath Studio:

Drag the Filter Data Table activity into the workflow.

Set Input DataTable = dtInput

Set Output DataTable = dtFiltered

Configure the filter condition:

vbnet

CopyEdit

Column: "Quantity"

Operator: "Greater than"

Value: 500

Now, dtFiltered contains only rows where "Quantity" > 500.

Why Other Options Are Incorrect?

A (Sort Data Table) ❌

Sort Data Table only sorts data; it does not filter rows.

B (Output Data Table) ❌

Converts the DataTable into a string representation, used for display purposes, not filtering.

C (Lookup Data Table) ❌

Searches for specific values in a column but does not filter multiple rows.

The area selection feature in the UiPath Computer Vision wizard is used to refine the scope of the UI elements that are detected by the Computer Vision activities1. By using this feature, you can select a specific region of the application UI that you want to automate, and the wizard will only show the UI elements within that region. This is helpful when dealing with multiple fields bearing the same label, such as “Name” or “Address”, as you can select only the field that you want to interact with2. The selected area is not automatically resized, treated as a single UI element, or duplicated by the wizard.

A static selector should be used when all the attributes or tags remain the same for each execution. A static selector is a selector that has fixed values for the attributes or tags of the target element. A static selector can reliably identify the target element as long as the element does not change its properties or position on the screen. A static selector is suitable for simple and stable UI elements that have consistent and unique selectors1. For example, a static selector can be used to click on a button that has the same name and ID every time the automation runs.

Starting with UiPath Studio version 2022.10, the default project type is Windows, which uses .NET 6 or .NET 5 with Windows support1. If a project contains dependencies that lack Windows compatibility, such as custom activities or libraries, they are marked as unresolved when the project is converted to Windows2. The developer needs to manually resolve them by finding compatible alternatives or updating the code3.

To make a selector specifically target the "First Name" text field during runtime in the UI Explorer, the property that uniquely identifies the "First Name" field should be used. Based on the information provided, the most suitable property to use is the "id" as it is likely to be unique for each field in a form, which helps in precisely identifying the UI element.

The "For Each File in Folder" activity is the appropriate choice for iterating through all the files in a local folder in UiPath. This activity allows you to specify the folder path and then iterates through each file within that folder, performing actions on each file as needed. Options B, C, and D are not standard UiPath activities for this purpose.

According to the UiPath Automation Implementation Methodology, the automation lifecycle consists of six stages: Discovery and Kickoff, Process Analysis, Solution Design, Development and Unit Testing, Integration and UAT, and Deployment and Hypercare. The automation developer has the least contribution and responsibility in the first three stages, as they are mainly focused on identifying, analyzing, and designing the automation solution. The automation developer’s role is more prominent in the last three stages, as they are responsible for developing, testing, deploying, and monitoring the automation projects and components. References: Automation Lifecycle - Standalone, Automation Developer

Breakpoints are used in debugging to pause the execution of the project at specific activities, which may potentially cause execution issues, making option A correct. This allows developers to inspect the state of the application at that point, aiding in the identification and resolution of issues. Options B, C, and D do not accurately describe the purpose of breakpoints in the debugging process.

The Flow Switch activity is best suited for handling multiple distinct cases, such as processing documents from different vendors, where each vendor requires a unique set of actions.

Flow Switch is similar to a "Switch Case" in programming and allows for better readability and efficient branching logic.

It is more scalable than using multiple If or Flow Decision activities.

✅ Why other options are incorrect:

A (For Each): Iterates through a collection but does not handle conditional branching effectively.

B (Do While): Executes a loop until a condition is met, but not ideal for decision-based branching.

C (Flow Decision): Good for binary decisions (True/False) but inefficient for multiple conditions.

✅ Reference: UiPath Studio - Flow Switch

The Activate property of the Type Into activity allows the developer to bring the specified UI element to the foreground and activate it before the text is written1. This property is useful when the web form fields are not visible or focused by default.

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.

The default REFramework uses Orchestrator queues to store and retrieve transaction items, which are the units of work to be processed by the automation. To use the REFramework without Orchestrator queues, one needs to remove or modify the activities and variables that depend on them. The Get Transaction Item activity is used to fetch a transaction item from a queue, and the SetTransactionStatus activities are used to update the status of a transaction item in a queue. Therefore, these activities need to be excluded from the project. Additionally, the variable type of io_TransactionItem needs to be changed from QueueItem to a suitable data type that represents the transaction data, such as DataRow, String, etc. (UiPath Automation Developer study guide)

The Asset Type that should be used for storing email addresses of the process owners is Text. Text assets are used to store only string values, such as names, addresses, URLs, etc. Text assets can be easily retrieved and updated using the Get Asset and Set Asset activities in UiPath Studio. Text assets are suitable for storing email addresses, as they can contain alphanumeric characters, symbols, and special characters. Text assets can also be used in various activities that require string input or output, such as Send Email, Write Line, Assign, etc.

 The Include Subfolders filter is a toggle button that appears in the Monitoring pages when a modern folder is selected from the Folders drop-down list1. The modern folders are folders that can have subfolders and support role-based access control2. The Include Subfolders filter allows you to choose whether to display the data for the selected folder only, or for the selected folder and all its subfolders3. This filter applies to the Jobs, Queues, Triggers, and Robots pages4. The Include Subfolders filter helps you to monitor and manage the processes and resources across different levels of folders.

https://forum.uipath.com/t/read-all-file-from-sub-folder-and-sub-folder-of-sub-folder/460493

The Substring method is used to extract a part of a string based on a specified starting index and length. The syntax of the Substring method is:

string.Substring(startIndex, length)

where startIndex is the zero-based position of the first character in the substring, and length is the number of characters in the substring. For example, if the string is “Hello”, then string.Substring(1, 2) will return “el”, as it starts from the second character (index 1) and takes two characters.

To return four characters starting with the second character, the startIndex should be 1 and the length should be 4. Therefore, the expression should be:

StrVar.Substring(1, 4)

Process Owner Email should be stored as an Orchestrator Asset because it changes infrequently (once per year). Assets are best suited for static or rarely changing values.

Employee ID should be stored in the Queue Item because each transaction is unique and needs to process different employee data.

Orchestrator Assets store global variables, while Queues manage dynamic data that changes per transaction.

✅ Reference: UiPath Documentation – Assets and Queues

One of the key advantages of using UiPath Orchestrator queues is the ability to track the status of Queue Items. This feature allows for monitoring the progress of items as they are processed by robots, including whether they are new, in progress, successful, failed, or retried, among other statuses.

The UiPath Remote Runtime component is a component that enables the communication between a remote application or desktop, such as Citrix Virtual Apps, and the dedicated UiPath extension, such as the UiPath Extension for Citrix or the UiPath Extension for Windows Remote Desktop. It gathers information about the targeted UI elements of the remote applications and sends them to the corresponding extension, so that selectors can be natively generated in UIExplorer1. This way, you can create and manage tasks and exchanges between users and external applications using the authentication process of the API provider2. The UiPath Remote Runtime component is required to establish the connection between an application or desktop server and a corresponding UiPath extension installed on a client machine, without having to rely on OCR and image recognition activities3.