QUESTION: 93

A developer is building an automation that must interact with a destination remote computer reached by jumping through multiple RDP connections, as described by the following scenario:
- The Robot is installed on Machine A, which connects through RDP to Machine B.
- From Machine B another RDP connection is opened to Machine C, where the automation must be performed.
Which of the following scenarios is appropriate for the developer who wants to use UI Automation activities?

Ul Automation can be used and the following are prerequisites:
Machine A - install RDP extension.
Machine B - no requirement.
Machine C - install RemoteRuntime.msi.
UI Automation can be used and the following are prerequisites:
Machine A - no requirement.
Machine B - no requirement.
Machine C - install RemoteRuntime.msi.
UI Automation can be used and the following are prerequisites:
Machine A - install RDP extension.
Machine B - install RDP extension and RemoteRuntime.msi.
Machine C - install RemoteRuntime.msi.
UI Automation can be used and the following are prerequisites:

Machine A - install RDP extension.
Machine B - install RemoteRuntime.msi.
Machine C - install RemoteRuntime.msi.

Answer(s): C

Explanation:

UI Automation is a feature that enables you to automate the interaction with UI elements on remote machines using native selectors. To use UI Automation in a scenario where multiple RDP connections are involved, you need to install the UiPath Windows Remote Desktop extension on the client machines and the UiPath Remote Runtime component on the destination machine. The extension allows you to identify UI elements on the remote desktop and send keyboard and mouse events to them. The Remote Runtime component enables the communication between the extension and the UiPath Robot service. In this case, Machine A and Machine B are client machines, while Machine C is the destination machine. Therefore, you need to install the RDP extension on Machine A and Machine B, and the Remote Runtime component on Machine C. (UiPath Studio documentation1)

Reference:

1: About Native RDP Automation - UiPath Studio.

Reveal Solution Next Question

QUESTION: 94

A developer implemented a process using the Robotic Enterprise Framework and an Orchestrator queue. The MaxRetryNumber from the "Config.xlsx" file is set to "1" and the Max # of retries from the Queue settings from Orchestrator is set to
"2". At runtime, the first transaction item throws a Business Exception.
How many times will the transaction be retried?

The transaction will be retried only one time.
The transaction will not be retried.
The transaction will be retried 2 times.
The transaction will be retried multiple times, until it will be processed successfully.

Answer(s): B

Explanation:

The Robotic Enterprise Framework (REF) is a template that provides a structured and consistent way to develop automation processes. The REF uses an Orchestrator queue to store and process the transaction items, which are the units of work for the process. The REF also handles different types of exceptions that may occur during the execution of the process, such as system exceptions and business exceptions. A system exception is an error that prevents the normal execution of the process, such as a network failure or an application crash. A business exception is an error that is related to the business logic or rules of the process, such as an invalid input or an incorrect output.

The REF has different mechanisms to deal with these exceptions, such as retrying, logging, and updating the status of the transaction items.
The MaxRetryNumber from the "Config.xlsx" file is a parameter that specifies how many times the REF will retry a transaction item when a system exception occurs. The Max # of retries from the Queue settings from Orchestrator is a parameter that specifies how many times Orchestrator will retry a transaction item when it changes to Failed status due to any exception. These two parameters are independent of each other and have different effects on the retry mechanism. In this case, the first transaction item throws a business exception, which means that there is something wrong with the data or the logic of the process. The REF will not retry a transaction item when a business exception occurs, because it assumes that retrying will not solve the problem. Instead, the REF will log the exception, update the status of the transaction item to Failed, and move on to the next transaction item. Orchestrator will also not retry a transaction item when it changes to Failed status due to a business exception, because it respects the decision of the REF. Therefore, the transaction will not be retried at all.

Reference:

1: Robotic Enterprise Framework Template - UiPath Studio.

Reveal Solution Next Question

QUESTION: 95

What is the recommended approach for handling tabular data when building a REFramework transactional project in UiPath?

Implement custom activities to handle the tabular data.
Convert the tabular data into a string format and store it in a single variable.
Use separate variables to store each column of the tabular data.
Utilize a DataTable variable to store and process the tabular data.

Answer(s): D

Explanation:

A DataTable variable is a data structure that can store and manipulate tabular data in UiPath. A DataTable variable has rows and columns that correspond to the rows and columns of the tabular data source, such as an Excel or CSV file. A DataTable variable can be used to store the input data for a REFramework transactional project, where each row represents a transaction item. The REFramework template can be modified to use a DataTable variable as the TransactionItem type and to process each row in the GetTransactionData and ProcessTransaction workflows. Using a DataTable variable is the recommended approach for handling tabular data when building a REFramework transactional project in UiPath, because it is efficient, flexible, and easy to use. (UiPath ReFramework documentation1)

Reference:

1: Robotic Enterprise Framework Template - UiPath Studio.

Reveal Solution Next Question

QUESTION: 96

When a developer runs a process using the REFramework, with the process utilizing Orchestrator queues and a queue already created with the Name provided and the Auto Retry function disabled, which states will be executed without errors?

Initialization -> Process Transaction -> End Process
Initialization -> Get Transaction Data -> Process Transaction -> End Process
Initialization -> Get Transaction Data -> End Process
Initialization -> End Process

Answer(s): B

Explanation:

The REFramework is a template that provides a structured and consistent way to develop automation processes using state machines. The REFramework has four main states: Initialization, Get Transaction Data, Process Transaction, and End Process. Each state performs a specific function and transitions to another state based on the outcome.
When a developer runs a process using the REFramework, with the process utilizing Orchestrator queues and a queue already created with the Name provided and the Auto Retry function disabled, the following states will be executed without errors:
Initialization: This state is used to initialize the application, read the configuration data, and log in to Orchestrator. If the initialization is successful, the state transitions to Get Transaction Data; otherwise, it transitions to End Process. (UiPath ReFramework documentation1) Get Transaction Data: This state is used to retrieve a transaction item from the Orchestrator queue and assign it to a variable. If there is a transaction item available, the state transitions to Process Transaction; otherwise, it transitions to End Process. (UiPath ReFramework documentation1) Process Transaction: This state is used to execute the business logic for the current transaction item and handle any exceptions that may occur. If the transaction is successful, the state updates the status of the transaction item to Successful and transitions to Get Transaction Data; if the transaction fails due to a business exception, the state updates the status of the transaction item to Failed and transitions to Get Transaction Data; if the transaction fails due to a system exception, the state updates the status of the transaction item to Failed and retries the transaction based on the MaxRetryNumber parameter from the Config file. If the retry limit is reached, the state transitions to End Process; otherwise, it transitions to Get Transaction Dat a. (UiPath ReFramework documentation1)
End Process: This state is used to close all applications, log out of Orchestrator, and terminate the process. This state does not have any transition. (UiPath ReFramework documentation1)

Reference:

1: Robotic Enterprise Framework Template - UiPath Studio.

Reveal Solution Next Question

Free UiPath-ADAv1 Exam Braindumps (page: 24)

QUESTION: 93

Explanation:

Reference:

QUESTION: 94

Explanation:

Reference:

QUESTION: 95

Explanation:

Reference:

QUESTION: 96

Explanation:

Reference: