Explanation
The Assign activity is used to assign a value to a variable. In this case, the variable is "qty". The value of the variable will be 80 after executing the Assign activity because the expression in the Assign activity is
"dt.AsEnumerable().Where(Function(x) x("Item").ToString.Equals("mango")).Select(Function(y) y("Quantity")).ToString". This expression is filtering the data table "dt" for rows where the "Item" column is equal to "mango" and then selecting the "Quantity" column from those rows. Since there is only one row in the data table where "Item" is equal to "mango", the value of the "Quantity" column in that row is 80. (UiPath Studio documentation)
References:
: [Assign - UiPath Activities].

Explanation
The workflow will pause the execution only once when it is executed in Debug mode with "Continue on Exception" enabled. Debug mode is a mode of execution that allows the developer to test and troubleshoot the workflow by using various debugging tools, such as breakpoints, step actions, and output messages4. "Continue on Exception" is a debugging option that enables the execution to continue even if an exception is encountered, without displaying the error message or stopping at the faulty activity5. In the workflow, there are two activities that can throw exceptions: the "Throw" activity, which throws a custom exception with the message "This is an exception", and the "Write Line" activity, which writes the value of the
"Var" variable to the Output panel. The "Var" variable is not initialized, so it has a null value by default.
When the "Write Line" activity tries to write the null value, it throws a NullReferenceException, as explained in the previous question. However, since the "Continue on Exception" option is enabled, the execution does not stop at the "Write Line" activity, but continues to the next activity, which is the "Throw" activity. The
"Throw" activity throws the custom exception, which is caught by the "Catch" section of the "Try Catch" activity. The "Catch" section contains a "Log Message" activity, which writes the exception message to the Output panel. The execution then moves to the "Finally" section, which contains a "Write Line" activity with the text "This is the end". The workflow then ends successfully. The only time the execution pauses is when it reaches the breakpoint that is set at the "Throw" activity. A breakpoint is a debugging tool that allows the developer to pause the execution at a specific activity and inspect the values of the variables and arguments, as well as the output messages6. The developer can then resume the execution by using the step actions or the continue button7. Therefore, the workflow will pause the execution only once at the breakpoint, and not at the exceptions, as they are ignored by the "Continue on Exception" option. References: Debugging a Workflow, Debugging Actions, Breakpoints, and Continue on Exception from UiPath documentation.

Explanation
When a transaction item throws a Business Rule Exception, it means that the item does not meet the business requirements and cannot be processed further1. Therefore, the transaction item is marked as failed and not retried, regardless of the Max # of retries setting for the queue2. However, the process does not stop and continues with the remaining transaction items in the queue3.
References:
Business Exception vs System Exception forum post, Answer by @loginerror RE Framework MaxRetryNumber and Orchestrator Queue Max # Rertry, again forum post, Answer by
@Arpit_Kesharwani

Explanation
Based on the image you sent, the automation process consists of four steps: opening Notepad.exe, typing some text, saving the file, and closing Notepad.exe. Each step has a Log Message activity that writes a text value to the Output panel. If Notepad.exe is not running, the first step will fail and throw an exception. The exception type is SelectorNotFoundException, because the Open Application activity cannot find the selector for Notepad.exe1. Therefore, the Log Message text value that is contained in the Output panel is
"SelectorNotFoundException", which is option D.
References: Open Application documentation.

Explanation
The Object Repository tree structure shows one application with two screens and five UI elements. The application is the top-level node, the screens are the second-level nodes, and the UI elements are the third-level nodes. The UI elements have properties, selectors, and images that define them.
https://docs.uipath.com/studio/docs/about-the-object-repository