UiPath-ADPv1 UiPath (ADPv1) Automation Developer Professional Exam(2023.10) Free Practice Exam Questions (2025 Updated)

To use UI Automation activities in a scenario where the destination remote computer is reached by jumping through multiple RDP connections, the following prerequisites are required:

Machine A - install the RDP extension. This extension enables the robot to generate native selectors over RDP connections and interact with the UI elements on the remote machines.

Machine B - install the RDP extension and the RemoteRuntime.msi. The RDP extension allows the robot to connect to Machine C from Machine B, while the RemoteRuntime component enables the communication between the robot and the UI elements on Machine B.

Machine C - install the RemoteRuntime.msi. This component enables the communication between the robot and the UI elements on Machine C, where the automation must be performed. References: [Remote Runtime Architecture], [Multiple RDP Connections], [UiPath Extension for Microsoft Remote Desktop and Apps]

The percentages from the Test Explorer panel represent the passing percent of the test cases that are executed. The Test Explorer panel shows the status of each test case, the total number of test cases, the number of passed test cases, the number of failed test cases, and the passing percent. The passing percent is calculated by dividing the number of passed test cases by the total number of test cases and multiplying by 100. For example, if there are 10 test cases and 8 of them pass, the passing percent is 80%. References: Test Explorer

The service mode is recommended for running unattended automations in UiPath. This mode allows robots to run without needing a user to be logged in, making it ideal for unattended scenarios.

Custom virtual channels, by default, are blocked in Citrix Virtual Apps and Desktops, which would prevent the UiPath Remote Runtime from functioning correctly. Therefore, adding the UiPath virtual channel to the allow list policy is necessary for proper automation interaction.

In the REFramework (Robotic Enterprise Framework), the initialization of all required applications should ideally be done in the 'InitAllApplications.xaml' file. This helps in keeping the project organized and maintains a standard structure.

 The project structure that is best-suited for complex processes in UiPath Studio, following UiPath best practices, is State Machine. A State Machine is a type of workflow that consists of a set of states, transitions, and triggers. A state represents a stage of the process, a transition represents a change from one state to another, and a trigger represents a condition or an event that activates a transition. A State Machine is suitable for complex processes because it can handle multiple paths and branches, depending on the logic and the triggers of the workflow. A State Machine can also handle loops and retries, as well as parallel execution of states. A State Machine can be created by using the StateMachine activity in UiPath Studio, or by using the REFramework template, which is based on a State Machine structure. References: [State Machines], [REFramework]

In UiPath Testing Activities, the "Verify Expression" activity is designed to evaluate expressions and can include other activities within its body. This feature is particularly useful in test cases where you need to assert the outcome of a specific expression or condition. By embedding other activities within the "Verify Expression" activity, users can execute additional actions or checks as part of the verification process, enhancing the flexibility and depth of testing scenarios within UiPath projects.References:

UiPath Documentation: Testing Activities Guide

In a Try Catch activity within UiPath, when an exception is thrown that does not match any of the exception types specified in the Catches section, the exception is unhandled by the Catches section. If the thrown exception is an ApplicationException and the Catches section is only configured to handle an InvalidOperationException, then the ApplicationException is not caught because it is a different type of exception.

However, regardless of whether the exception is caught, the Finally block always executes. The Finally block is designed to run after the Try block and after any Catch blocks are checked for matches (regardless of whether a match is found or not).

Therefore, the correct answer is:

A. The Finally block is executed and the Catches section catches the exception.

In this context, "the Catches section catches the exception" means that the Catches section is evaluated for a match. Since ApplicationException is not handled by the InvalidOperationException catch block, the exception is not actually caught, but the Finally block will still execute.

The type of error that should be thrown according to best practices for queue items that contain partial numbers is Business Exception. A Business Exception is an exception that occurs due to an incorrect or incomplete input data or an expected business rule violation. A Business Exception indicates that the transaction item cannot be processed successfully and should be marked as failed in the queue. A Business Exception can be thrown by using the Throw activity in UiPath Studio, with the exception type set to UiPath.Core.BusinessRuleException. Alternatively, a Business Exception can be thrown by using the Set Transaction Status activity in the REFramework, with the status set to Failed and the exception type set to Business Exception. References: [Business Exception vs Application Exception], [Throw], [Set Transaction Status]

When a breakpoint is placed at a particular activity within the workflow and the Step Over function is used, the Executor will move to the next activity in the sequence. Given the context of the REFramework, after stepping over the "Invoke InitAllSettings" workflow, the next activity that would execute is the "If in_OrchestratorQueueName ..." activity, assuming there are no activities in between within the "InitAllSettings" workflow itself. Step Over will not go into the invoked workflow but will move to the next activity at the same level of the workflow where the breakpoint was placed.References:

UiPath Studio Guide: Debugging

TheAdd Attachmentoption is available in theUiPath.WebAPI.Activities.HttpClientactivityonly when using POST or PUT methods, as these methods are designed for sending data (such as files or form data) to the server. GET, DELETE, HEAD, and OPTIONS methods do not support body content in the same way and are typically used for retrieval or metadata operations.

In aState Machine, every state—including theFinal State—can contain anEntryand anExitsection. However, theFinal Statedoesnot include Transitions, as it's meant to mark theend of execution. Once entered, no further transitions occur from this state.

The Descriptor Coverage sub-panel in the Test Explorer provides Selector coverage information. This coverage data is crucial for understanding how well the selectors in a project are being tested.

The Monitoring pages in UiPath Orchestrator are pages that provide information and statistics about the performance and health of your robots, processes, queues, and jobs. You can access the Monitoring pages from the left menu in Orchestrator, under the Monitoring section.

The Include Subfolders filter in the Monitoring pages is a filter that allows you to select whether the contents of the selected folder’s subfolders are displayed in the Monitoring pages. This filter is available when a modern folder is selected from the Folder drop-down list. A modern folder is a type of folder in Orchestrator that supports dynamic and fine-grained permission management, as well as folder-level isolation of data, processes, and execution.

When the Include Subfolders filter is checked, the Monitoring pages display the data for the selected folder and all its subfolders. For example, if you select a modern folder called Sales and check the Include Subfolders filter, the Monitoring pages will show the data for the Sales folder and all its subfolders, such as Sales-East, Sales-West, Sales-North, and Sales-South. This way, you can get a comprehensive view of the performance and health of your robots, processes, queues, and jobs across multiple subfolders.

When the Include Subfolders filter is unchecked, the Monitoring pages display the data only for the selected folder. For example, if you select a modern folder called Sales and uncheck the Include Subfolders filter, the Monitoring pages will show the data only for the Sales folder, excluding its subfolders. This way, you can get a focused view of the performance and health of your robots, processes, queues, and jobs within a specific folder.

The correct answer is B. It allows you to select whether the contents of the selected folder’s subfolders are displayed. This statement accurately describes the functionality of the Include Subfolders filter in the Monitoring pages when a modern folder is selected.

The other options are not correct statements. Option A is incorrect, because the Include Subfolders filter does not allow you to choose between background and foreground processes for the displayed data. Background and foreground processes are types of processes that run in the background or foreground of the robot machine, respectively. You can filter the displayed data by process type using the Process Type filter in the Monitoring pages. Option C is incorrect, because the Include Subfolders filter does not enable you to sort the displayed data based on job priorities. Job priorities are levels of importance that are assigned to jobs when they are created or triggered, such as High, Normal, or Low. You can sort the displayed data by job priority using the Sort By drop-down list in the Monitoring pages. Option D is incorrect, because the Include Subfolders filter does not allow you to allocate licenses per machine for the displayed data. Licenses are resources that are consumed by robots, processes, or users when they perform certain actions in Orchestrator. You can allocate licenses per machine using the License Allocation page in Orchestrator.

Starting with UiPath Studio version 2022.10, dependencies that lack Windows compatibility are marked as unresolved when they are converted in a project. This means that the project cannot be executed until the unresolved dependencies are manually resolved by the developer. This is done to ensure that the project can run on both Windows and Linux platforms without compatibility issues. References: [UiPath Studio Guide - Converting Projects to Linux Compatibility]

Server-side event triggers in UiPath Integration Service are used to automatically start UiPath processes in response to certain events, like data updates, insertions, or deletions in other systems. This allows for a high level of automation integration.

The Type Into activity has three input methods: Default, Simulate, and Window Messages. The Default method uses hardware drivers to send keystrokes to the target application, which means it requires the window to be active and visible. The Simulate and Window Messages methods use software drivers to send keystrokes to the target application, which means they can work in the background, even if the window is hidden or minimized. However, the Simulate method cannot send hotkeys, while the Window Messages method can. Therefore, the only input methods that can be used individually for the Type Into activity to enter text and hotkeys in a hidden or minimized window are Simulate and Window Messages. References:

•Type Into

•Input Methods