UiPath Updated UiPath-ADAv1 Exam Questions and Answers by ivy-rae

The output panel will display “Hello World” because the workflow is designed to first display “Hello” and then “World” in the output panel. The workflow starts with an Assign activity that initializes the Boolean flag to True. Then, the While activity checks if the flag is True. If it is, the workflow enters the Body section of the While activity. Inside the Body section, the workflow checks if the flag is True. If it is, the workflow enters the Then section of the If activity and displays “Hello” in the output panel. Then, the Assign activity sets the flag to False. Since the flag is now False, the workflow enters the Else section of the If activity and displays “World” in the output panel. Finally, the workflow exits the While activity since the flag is now False.

Understanding the Default Delay in Modern UI Automation

In UiPath Studio, when using Modern UI Automation activities, the default values for delays, timeouts, and wait settings can be configured at the Project Settings level. If these properties are not explicitly set within an activity, UiPath will inherit the values from the Project Settings.

Analysis of the Provided Images:

Project Settings (UI Automation Modern Tab)

Delay before (seconds)

Run value: 0.2

Debug value: 0.2

This means that any Modern UI Automation activity (like Check App State) will use 0.2 seconds as the default delay before execution unless manually changed in the activity.

Check App State Activity Properties Panel

The "Delay before" field is empty, meaning it will inherit the default value from Project Settings, which is 0.2 seconds.

Explaining the Answer Choices:

A (0 seconds) ❌ Incorrect

If the Project Settings had no predefined value, the default UiPath behavior might have been 0 seconds. However, the provided settings explicitly define it as 0.2 seconds.

B (0.2 seconds) ✅ Correct

The Project Settings define 0.2 seconds as the default "Delay before" value for all Modern UI Automation activities.

Since no value is manually set in the Check App State activity, it inherits 0.2 seconds from Project Settings.

C (0.3 seconds) ❌ Incorrect

0.3 seconds is set as the "Delay after" value, not "Delay before".

D (30 seconds) ❌ Incorrect

30 seconds is the default timeout value, not the "Delay before" value.

Final Answer: B (0.2 seconds)

???? Official UiPath References:

UiPath Project Settings - Modern UI Automation

Check App State Activity

Delays and Timeouts in UI Automation

To convert ExtractedDate to a DateTime type, the expression that should be used is:

DateTime.Parse(ExtractedDate)

This expression uses the DateTime.Parse method, which converts a string representation of a date and time to its DateTime equivalent. The DateTime.Parse method can accept different formats of date and time strings, as long as they are supported by the current culture or a specified culture. The DateTime.Parse method returns a DateTime object that represents the date and time value of the string1. For example, if the ExtractedDate variable has the value:

ExtractedDate = “08-22-2022”

Then the expression DateTime.Parse(ExtractedDate) will return a DateTime object with the value:

[08/22/2022 12:00:00 AM]

This DateTime object can then be used to perform a comparison with a different date, such as using the DateTime.Compare method or the comparison operators2.

By default, the Timeout property in UiPath is set to 30 seconds (30000 milliseconds).

If the UI element is not found within 30 seconds, the activity throws an exception.

The Timeout can be manually adjusted in the activity’s properties.

✅ Why other options are incorrect:

A (10 seconds): UiPath does not use a 10-second default timeout.

C (60 seconds): Default is 30 seconds, but it can be extended.

D (Indefinitely): Without modification, UiPath will timeout after 30 seconds, not indefinitely.

✅ Reference: UiPath Studio - Activity Timeout Property