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

Unattended Automations are intended for complex, highly repetitive tasks that are usually performed in batches. They can operate without human supervision and decisions can be made based on predefined rules. These tasks can run on virtual environments and do not require human input once started.

Credential stores are secure locations where you can store and retrieve sensitive data such as robot credentials and credential assets1. Orchestrator supports the use of multiple credential stores and has built-in integrations with the following ones2:

Azure Key Vault: A cloud-based service that provides secure storage and management of secrets, keys, and certificates3.

CyberArk CCP: A component of the CyberArk Privileged Access Security Solution that provides centralized management and distribution of credentials to applications and robots4.

HashiCorp Vault: A tool that enables secure access to secrets and encryption keys across dynamic environments5.

Thycotic Secret Server: A web-based solution that protects privileged accounts and credentials from cyberattacks and insider threats.

BeyondTrust: A platform that offers privileged access management, remote access, and vulnerability management solutions.

CyberArk: A leader in privileged access management that secures credentials, sessions, and endpoints across hybrid and cloud environments.

Therefore, option A is the correct answer, as it lists all the credential stores that have built-in support in Orchestrator. Option B is incorrect because it includes Cisco and Google Credentials, which are not credential stores supported by Orchestrator. Option C is incorrect because it includes Amazon Security Services, which is not a credential store supported by Orchestrator. Option D is incorrect because it includes Cisco, Amazon Security Services, Microsoft SCS, and IBM Vault, which are not credential stores supported by Orchestrator.

This is because the code is throwing a new IOException, but there is no catch block defined for IOException. The catch blocks present are for BusinessRuleException, ArgumentException, and InvalidOperationException. Therefore, the code will not be able to handle the thrown exception. References: https://docs.uipath.com/activities/docs/try-catch

Studio Web is UiPath’s cloud-based automation platform that enables cross-platform compatibility (Windows, Linux, Mac).

Why is B Correct?

✅ C# is the recommended language because:

Cloud projects in UiPath are built using .NET Core, which supports C# natively.

VB is not supported in cross-platform execution.

C# ensures compatibility with Linux-based cloud environments.

This expression filters the data table to obtain all rows representing employees from the Finance and IT departments with a Salary under 30,000. The expression uses the Select method of the data table, which returns an array of data rows that match a specified condition. The condition is written as a string that follows the syntax and rules of the DataColumn.Expression property. The condition uses parentheses to group the logical operators OR and AND, which have different precedence levels. The OR operator returns true if either operand is true, while the AND operator returns true only if both operands are true. The condition also uses single quotes to enclose the string values of the Department column, and the less than operator to compare the numeric values of the Salary column. (UiPath Studio documentation1)

The Connector Builder in UiPath Integration Service allows users to create custom connectors that integrate with third-party APIs.

Steps to Create a Custom Connector:

Open Automation Cloud.

Go to Integration Service.

Select the "Connectors" tab.

Click "Add a new Connector".

Choose to start from:

An API definition (predefined API)

A blank connector (custom integration).

Why is Option B Correct?

The Connector Builder is part of Integration Service, not Orchestrator or UiPath Studio.

The process begins in Automation Cloud under the Integration Service tab.

Why Other Options Are Incorrect?

A (Starts in UiPath Studio) ❌

Incorrect. Connectors are not built in UiPath Studio but in Automation Cloud > Integration Service.

C (Located in Orchestrator > Connections Tab) ❌

Incorrect. The Connections tab in Orchestrator is used to manage existing API connections, not to create custom connectors.

D (Requires OAuth 2.0 Selection) ❌

OAuth 2.0 is an authentication method, not a required step for creating all connectors.

In the Output property of all Get Mail activities, the supported variable type is List. The Output property is the property that stores the result of the activity in a variable. The Get Mail activities are the activities that retrieve email messages from various mail servers, such as POP3, IMAP, Outlook, or Exchange. The result of the Get Mail activities is a collection of email messages that match the specified criteria, such as the mail folder, the filter, or the top count. The collection of email messages is represented by the List type, which is a generic list that contains MailMessage objects. A MailMessage object is a class that represents an email message, with properties such as Subject, Body, Attachments, From, To, etc1. For example, if the Get Mail activity is used to retrieve the email messages from the Inbox folder of an Outlook account, the Output property can be configured with a variable of type List, such as mailList. The mailList variable will store the email messages as a list of MailMessage objects, which can then be accessed or manipulated using other activities, such as For Each, Save Attachments, or Send Mail2.

The main difference between an array and a list in UiPath (and .NET in general) is that an array is a fixed-size collection of elements of the same type, whereas a list is a dynamic-sized collection, meaning it can grow or shrink in size as needed. Both arrays and lists hold elements of the same type, but lists offer more flexibility in terms of adding or removing elements after the collection has been created.

When a developer starts a blank process in UiPath Studio, the following dependencies are automatically installed by default: UiPath.System.Activities, UiPath.Excel.Activities, UiPath.Mail.Activities, UiPath.UIAutomation.Activities and UiPath. Testing.Activities. These dependencies provide the basic activities and packages that are needed for most automation projects, such as working with data types, files, Excel, email, user interface, and testing. The developer can also add or remove other dependencies as needed, depending on the specific requirements of the automation project. References: Creating a Basic Process, Managing Dependencies.

According to the UiPath Automation Implementation Methodology, the automation lifecycle consists of six stages: Discovery and Kickoff, Process Analysis, Solution Design, Development and Unit Testing, Integration and UAT, and Deployment and Hypercare. The automation developer has the least contribution and responsibility in the first three stages, as they are mainly focused on identifying, analyzing, and designing the automation solution. The automation developer’s role is more prominent in the last three stages, as they are responsible for developing, testing, deploying, and monitoring the automation projects and components. References: Automation Lifecycle - Standalone, Automation Developer