Explanation
The String.Join method takes two parameters: a separator and an array of strings. It returns a new string that concatenates the elements of the array using the separator. The correct syntax is String.Join(separator, array).
Therefore, option B is the correct answer.
References:
Automation Developer Associate Training course, Section 1: Data Manipulation, Lecture: Data Manipulation with Strings in Studio How to use Array of string forum post, Answer by @balupad14

Explanation
The UI Object Repository is a feature that allows you to store and reuse UI elements across different automation projects1. A UI Library is a type of project that contains UI elements and workflows that can be used as dependencies in other projects2. When you import a UI Library as a dependency in your current project, the UI Object Repository defined in the UI Library will automatically be available in your current project3. You can access the UI elements from the Object Repository panel in Studio and use them in your activities4. Therefore, the correct answer is C. The other options are incorrect because they do not reflect the actual behavior of the UI Object Repository and the UI Library.
References: Object Repository documentation, Reusing Objects and UI Libraries documentation, Object Repository course, [Object Repository in Studio course].

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
The Visible property of the Excel Application Scope activity determines whether the Excel file is opened in the foreground or in the background. If the Visible property is set to True (default value), the Excel file is opened and displayed on the screen. If the Visible property is set to False, the Excel file is opened and processed in the background, without showing the user interface. This can improve the performance and speed of the automation, as well as avoid any interference with the user's work. Therefore, to create a process that runs in the background and uses Excel activities, the Visible property of the Excel Application Scope activity must be configured to False. References: Excel Application Scope from UiPath documentation.

Explanation
To ensure the selector targets only the First Name text field at runtime, you need to click the additional Property checkbox for ID in the UI Explorer Unselected Items column. This will add the ID attribute to the selector, which is a unique identifier for the text field element. The ID attribute has the value "firstname" for the First Name text field, as shown in the image. This will make the selector more reliable and specific, and avoid targeting the text label or other elements with the same class or tag.
https://docs.uipath.com/de/studio/standalone/2021.10/user-guide/uipath-explorer