The UiPath Remote Runtime component is a component that facilitates the communication between a remote application or desktop, such as Citrix Virtual Apps, and the dedicated UiPath extension – the UiPath Extension for Citrix, the UiPath Extension for Windows Remote Desktop and Apps, or the UiPath Extension for VMware Horizon1. It gathers information about the targeted UI elements of the remote applications and sends them to the corresponding extension, so that selectors are natively generated in UiExplorer1. The UiPath Remote Runtime component is required to establish the connection between an application or desktop server and a corresponding UiPath extension installed on a client machine, where Studio is installed1. This way, selectors are natively generated on the client machine, without having to rely on OCR and image recognition activities1. .

The graphics show a UiPath workflow that contains a Try Catch activity with a Type Into activity inside the Try block and a Log Message activity inside the Catch block. The Type Into activity isconfigured to type “Typing into Notepad” into a Notepad window with the selector “ < wnd app=‘notepad.exe’ cls=‘Notepad’ title=‘Untitled - Notepad’ / > ”. The Log Message activity is configured to log the exception message in the Output panel.

If the automation is executed and Notepad.exe is not running, the Type Into activity will fail to find the target UI element and throw an exception. The exception will be caught by the Catch block and the Log Message activity will log the exception message in the Output panel. The exception message will contain the name of the exception type, which is ApplicationNotFoundException. This exception is thrown when the application that is specified in the selector is not found or not running. Therefore, the Log Message text value that is contained in the Output panel is ApplicationNotFoundException.

The other options are not correct, as they are not the exception type that is thrown by the Type Into activity when the application is not running. Option A is incorrect, because Exception is a generic term for any error or problem that occurs during the execution of a program, not a specific exception type. Option C is incorrect, because Try is not an exception type, but a keyword that marks the beginning of a block of code that may throw an exception. Option D is incorrect, because SelectorNotFoundException is not an exception type, but a possible error message that is displayed when the selector is invalid or does not match any UI element.

The Get File/Folder activity from the Microsoft 365 package should be used to retrieve the Driveitem ID for a Sharepoint URL. This activity allows you to get information about a specific file or folder from OneDrive or SharePoint, such as the name, size, ID, URL, etc. You can specify the file or folder to be retrieved by browsing, entering the ID, or entering the URL1.

To get the Driveitem ID for a Sharepoint URL, you need to do the following steps:

Use the Get File/Folder activity and select the Enter Url option in the File or folder to get property.

Enter the Sharepoint URL of the file or folder in the File or folder Url property. For example, 5.

Create a variable of type Microsoft.Graph.DriveItem in the Output property. For example, driveItem.

Use an Assign activity to get the Driveitem ID from the output variable. For example, driveItemId = driveItem.Id.

The other options are not activities that can be used to retrieve the Driveitem ID for a Sharepoint URL, because they either do not have an output property that returns the Driveitem ID, or they do not have an input property that accepts the Sharepoint URL. For example:

The Get Group activity gets information about a specific group from Microsoft 365, such as the name, ID, description, etc. It does not have an output property that returns the Driveitem ID, nor an input property that accepts the Sharepoint URL2.

The Share File/Folder activity shares a file or folder with the specified recipients. It does not have an output property that returns the Driveitem ID, but only the sharing link and the expiration date3.

The Download File activity downloads a file from OneDrive or SharePoint to a local folder. It does not have an output property that returns the Driveitem ID, but only the local path of the downloaded file4.

The default URL of the OCR server that runs the Computer Vision service is https://cv.uipath.com/. The Computer Vision service is a cloud-based service that provides OCR and AI capabilities for UiPath automation projects. The service can be accessed by using the Computer Vision activities in UiPath Studio, such as CV Screen Scope, CV Click, CV Type Into, and more. The service requires an API key and a URL to connect to the OCR server. The default URL is https://cv.uipath.com/, but it can be changed to a custom URL if the developer has a self-hosted OCR server. The API key can be obtained from the UiPath Automation Cloud portal or from the UiPath Marketplace. References: [About Computer Vision], [Computer Vision Activities]

To ensure that all UI Automation activities within project workflows reference elements from the Object Repository, the ' Object Repository Enforced ' option should be set to Yes in the ' UI Automation Modern ' tab within the Project Settings window. This setting enforces the use of the Object Repository for UI activities.

The UiPath Integration Service supports two types of events: Generic and Predefined. Generic events are customizable, while Predefined events are specific to certain integrations and come with predefined configurations.

AI Computer Vision is a feature of UiPath that enables the automation of remote applications or desktops, such as Citrix Virtual Apps, Windows Remote Desktop, or VMware Horizon, by using native selectors. Native selectors are expressions that identify UI elements reliably and accurately, without relying on OCR or image recognition activities1. AI Computer Vision uses a mix of AI, OCR, text fuzzy-matching, and an anchoring system to visually locate elements on the screen and interact with them via UiPath Robots, simulating human interaction2. AI Computer Vision is especially useful for scenarios where the UI elements have low quality or scaling issues, which make them difficult to recognize with traditional methods3.

Option A is an accurate example of using AI Computer Vision features in a UiPath project, because it involves identifying and interacting with UI elements in a remote desktop application, which is one of the main use cases of AI Computer Vision. By using the Computer Vision activities, such as CV Screen Scope, CV Click, CV Get Text, etc., you can automate tasks in a remote desktop application without using selectors, OCR, or image recognition activities4.

The other options are not accurate examples of using AI Computer Vision features in a UiPath project, because they involve tasks that are not related to the automation of remote applications or desktops, or that do not use the Computer Vision activities. For example:

Option B involves training a custom machine learning model, which is not a feature of AI Computer Vision, but of the UiPath AI Fabric, a platform that enables you to deploy, consume, and improve machine learning models in UiPath.

Option C involves extracting plain text from a scanned PDF document, which is not a feature of AI Computer Vision, but of the UiPath Document Understanding, a framework that enables you to classify, extract, and validate data from various types of documents.

Option D involves performing sentiment analysis on a text string, which is not a feature of AI Computer Vision, but of the UiPath Text Analysis, a set of activities that enable you to analyze the sentiment, key phrases, and language of a text using pre-trained machine learning models.

The statement that is true about the existing UiPath Studio installation packages is that the Attended Robot installation package installs only the UiPath Robot. The UiPath Robot is the component that executes the automation workflows designed in UiPath Studio. The Attended Robot installation package is intended for scenarios where the Robot works on the same machine as a human user and requires human input or supervision. The Attended Robot installation package does not include UiPath Studio or UiPath Assistant. UiPath Studio is the component that allows the developer to design and debug the automation workflows. UiPath Assistant is the component that allows the user to manage and run the automation workflows on their machine. The Unattended Robot installation package and the Automation Developer installation package both include UiPath Studio, UiPath Assistant, and UiPath Robot, but they are intended for different scenarios. The Unattended Robot installation package is for scenarios where the Robot works on a dedicated machine and does not require human input or supervision. The Automation Developer installation package is for scenarios where the developer needs to create and test the automation workflows on their machine. References: [UiPath Installation Guide], [UiPath Robot] , [UiPath Studio], [UiPath Assistant]

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.