Free UiPath UiPath-ADPv1 Practice Exam with Questions & Answers | Set: 3

In UiPath Integration Service, a trigger will be automatically disabled upon failure under specific conditions to prevent continuous failure and unnecessary resource consumption. This typically happens when the job associated with the trigger fails to start after a predefined number of attempts for a single event, or when it consistently fails to start across a series of events. The condition of failing to start after 3 attempts for a single event or not starting for the last 25 events is designed to safeguard against persistent issues that could disrupt the automation flow or lead to resource wastage.References:

UiPath Integration Service Documentation: Triggers and Events

A State Machine is a type of automation that uses a finite number of states in its execution. It can go into a state when it is triggered by an activity, and it exits that state when another activity is triggered. A State Machine consists of four primary components:

•States: These are the nodes that represent the possible situations or conditions of the automation. Each state can have one or more activities inside it that define the behavior of the automation in that state. There are two types of states: State and Final State. A State Machine must have one initial state and one or more final states.

•Triggers: These are the events or conditions that cause the automation to enter a state. A trigger can be an activity, a variable, or an argument that is executed or evaluated before entering a state. For example, a Click activity can be a trigger for entering a state that performs some actions after clicking a button.

•Transitions: These are the arrows or branches that connect the states and define the flow of the automation. A transition can have a condition that determines whether the automation can move from one state to another. For example, a Boolean expression can be a condition for a transition that checks if a certain condition is true or false before moving to the next state.

•Actions: These are the activities or sequences that are executed when the automation moves from one state to another. An action can be performed before or after the transition, depending on the type of the transition. For example, a Log Message activity can be an action that logs a message when the automation exits a state.

You can find out more about state machines on the Studio - State Machines - UiPath Documentation Portal or in the official Workflow Foundation documentation.

The value of the qty variable will be 80 after executing the Assign activity. This is because the expression in the Assign activity is using the LINQ methods AsEnumerable, SkipWhile, and Item to access the data in the dt variable. The dt variable is a DataTable that contains the following data:

Item

Quantity

apple

5

banana

10

mango

20

orange

80

grape

40

The AsEnumerable method converts the DataTable into an Enumerable collection of DataRow objects. The SkipWhile method skips the elements of the collection until the condition is false. The condition is a lambda expression that checks if the value of the Item column is equal to “mango”. The (0) indexer returns the first element of the collection after skipping. The Item method accesses the value of the Quantity column of the DataRow. The ToString method converts the value into a string. Therefore, the expression will skip the first three rows of the DataTable and return the value of the Quantity column of the fourth row, which is 80. References: [DataTable.AsEnumerable Method], [Enumerable.SkipWhile Method], [DataRow.Item Property]

Intrigger-based attended automation, triggers can respond toapplication events, keyboard shortcuts, or UI interactions, and theycan execute workflows in parallel, eitheronce, sequentially, or simultaneously. This capability allows multiple automations to be triggered and run concurrently, which is ideal for departments like sales handling multiple requests in real-time.

The collection variable type that will cause an error when adding a new filename to the collection is System.Array. This is because System.Array is a fixed-size collection that cannot be resized or modified once it is initialized. Therefore, if the collection is initialized with a single filename, it cannot accommodate any more filenames. To add a new filename to the collection, the developer should use a dynamic collection type, such as System.Collections.Generic.List or System.Data.DataTable, that can grow or shrink as needed. Alternatively, the developer can use System.Collections.Generic.Dictionary if the filenames need to be associated with some keys or values. References: [Array Class], [Collection Classes]

Given the two data tables DT1 and DT2, to achieve the desired result where DT2 contains both the department and the names, the Merge Data Table activity should be configured to merge DT1 into DT2. This configuration requires specifying DT1 as the source table and DT2 as the destination table. The MissingSchemaAction should be set to AddWithKey which ensures that if the source table (DT1) contains columns that are not found in the destination table (DT2), they will be added to the destination table with the primary key information preserved.

Option A shows the correct configuration for the Merge Data Table activity to achieve this result:

Destination: DT1

Source: DT2

MissingSchemaAction: AddWithKey

This setup correctly adds the "Name" column from DT1 to DT2 based on the shared "ID" column, which acts as the key. Since both tables have an "ID" column with matching values, the names will be added to the corresponding IDs in DT2, resulting in a merged table with ID, Department, and Name columns.

In UiPath, the Flow Switch activity is commonly used within flowcharts. Its default TypeArgument property is set to Int32, which means it is primarily used to handle integer-based decision branching.

The screenshot shows an "Invoke Code" activity in UiPath with the following VB.NET code:

Users_List.Add("User1")

Users_List.Add("User2")

According to the given information, the "Users_List" variable is a List of Strings that has been initialized with an empty list before the Invoke Code activity is run. The code within the Invoke Code activity is adding two strings: "User1" and "User2" to the "Users_List".

The Log Message activity following the Invoke Code is attempting to log the count of items in "Users_List", which would be the number of elements contained in the list at that time.

Given the steps that have been described, after the Invoke Code activity has run, the "Users_List" will contain two elements ("User1" and "User2"). Therefore, the log message will print the count of items in the list, which is:

B. 2

So the correct answer is B, as the "Users_List" will have two elements and Users_List.Count will return the number 2.

The Invoke Code activity is used to execute VB.NET or C# code within a UiPath workflow1. The activity has the following properties:

Code: The code that is to be executed. This field supports only strings and String variables1.

Language: The language that the code is written in. The available options are VBNet and CSharp1.

Arguments: The parameters that can be passed to and from the code1.

In this question, the developer has created a variable of type List of Strings named “Users_List”, and initialized it with an empty list: “Users_List = new List(Of String)”. Then, the developer has used the Invoke Code activity to execute the following code:

Users_List.Add(“User1”) Users_List.Add(“User2”)

This code adds two items (“User1” and “User2”) to the “Users_List” variable. After the Invoke Code activity, the developer has used the Log Message activity to print the count of items in the “Users_List” variable, using the expression “Users_List.Count.ToString”. This expression returns the number of items in the list as a string2. Therefore, the log message will print “2”, as there are two items in the list

The transaction will be retried only one time because the MaxRetryNumber from the “Config.xlsx” file is set to “1”. This parameter determines how many times a transaction item is retried when it fails with an application or a business exception. The Max # of retries from the Queue settings from Orchestrator is set to “2”, but this parameter only applies to the queue items that are marked as “Retry” by the robot. In the Robotic Enterprise Framework, the SetTransactionStatus workflow marks the queue items as “Retry” only if the MaxRetryNumber is not reached. Therefore, the first transaction item will be retried once by the robot and then marked as “Failed” in the queue, regardless of the Orchestrator setting.