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

The Strict selector relies only on the UI element’s full selector and does not use anchors.

Why is Option B Correct?

Strict selectors contain only reliable UI element attributes (title, id, class, etc.).

No anchors are needed, as the element is uniquely identified through direct targeting.

Anchors are used only in Fuzzy or Image-based selectors for dynamic UI elements.

Why Other Options Are Incorrect?

A (Strict selector always works better with multiple anchors.) ❌

Incorrect. The Strict selector does not use anchors at all.

C (Strict selector requires at least two anchors.) ❌

Incorrect. Anchors are irrelevant in Strict mode.

D (Strict selector only uses automatically identified anchors.) ❌

Incorrect. Strict selectors do not use anchors, manually or automatically.

To configure the Filter Data Table Wizard to keep all invoices with a Total value that is over 10 000 USD, you should choose the following options from the drop-down lists:

Column: Total Operation: > Value: 10000

The reason for choosing these options is to filter the data table based on the condition that the Total column value is greater than 10000. This will keep only the rows that satisfy this condition and remove the rest. You can learn more about the Filter Data Table activity and how to use it from the following sources:

Four Ways to Filter Data Tables in UiPath Studio | UiPath

How to Filter Data Table - Help - UiPath Community Forum

Filter Data table with specific column - UiPath Community Forum

The Try Catch activity is used to handle errors and exceptions that may occur during the execution of a workflow1. It has three sections: Try, Catches, and Finally1.

The Try section contains the activities that may throw an exception or an error. If an exception or an error occurs, the execution of the Try section is stopped and the control is passed to the Catches section1.

The Catches section contains one or more exception handlers that specify what type of exception or error to catch and what actions to perform when it is caught. The exception handlers are executed in order, from top to bottom, until a matching exception or error is found. If no matching exception or error is found, the execution of the workflow is stopped and a runtime error is thrown1.

The Finally section contains the activities that are always executed at the end of the Try Catch activity, regardless of whether an exception or error occurred or not. The Finally section is used to perform cleanup actions, such as closing applications, releasing resources, or logging messages1.

In your case, you have configured the properties for the Try Catch activity as follows:

The Try section contains a Throw activity with an ApplicationException.

The Catches section contains an InvalidOperationException with a Message Box activity and a Log Message activity.

The Finally section is empty.

This means that the Try Catch activity will throw an ApplicationException in the Try section and look for a matching exception handler in the Catches section. However, since you have chosen InvalidOperationException as the exception handler, which does not match the ApplicationException, the execution of the workflow will be stopped and a runtime error will occur. The Finally section will not be executed.

Therefore, option B is correct.