Pass the UiPath UiPath Certified Professional - Developer Track UiPath-ADAv1 Questions and answers with CertsForce

Variables and arguments are both used to store and pass data in UiPath, but they have some differences in their scope and direction. Variables are used to pass data between activities within the same workflow file. They have a default direction of In/Out, which means they can be read and written by any activity in the workflow. Arguments are used to pass data between different workflow files. They have a specific direction of In, Out, or In/Out, which means they can only be read or written by the workflow that invokes them or the workflow that is invoked. Variables and arguments can have different data types, such as String, Int32, Boolean, etc. Variables can be assigned to an argument value, but arguments cannot be assigned to a variable value. References: Managing Arguments, Variables, Arguments, and Control Flow in Studio, Different between variables and arguments

The Strict selector relies only on the UI element’s full selector and does not use anchors.

Why is Option B Correct?

Strict selectors contain only reliable UI element attributes (title, id, class, etc.).

No anchors are needed, as the element is uniquely identified through direct targeting.

Anchors are used only in Fuzzy or Image-based selectors for dynamic UI elements.

Why Other Options Are Incorrect?

A (Strict selector always works better with multiple anchors.) ❌

Incorrect. The Strict selector does not use anchors at all.

C (Strict selector requires at least two anchors.) ❌

Incorrect. Anchors are irrelevant in Strict mode.

D (Strict selector only uses automatically identified anchors.) ❌

Incorrect. Strict selectors do not use anchors, manually or automatically.

Connections are the core component of the UiPath Integration Service. They enable you to create and manage tasks and exchanges between users and external applications using the authentication process of the API provider. Each connection is associated with a specific connector, which defines the actions and triggers that can be performed on the external application. You can create connections in the Integration Service page of the Automation Cloud portal, and use them in your automation projects in Studio, StudioX, Apps, or Assistant. You can also share connections with other users or groups in your organization using folders and permissions1.

The correct sequence for the computation of the signature for client apps that receive Orchestrator requests and need to check their authenticity is:

Retrieve the X-UiPath-Signature HTTP header. This header contains the signature of the request body, encoded in Base64. (UiPath Orchestrator documentation1)

To obtain the raw signature bytes, decode the value of the header from Base64. You can use any tool or library that supports Base64 decoding. (UiPath Orchestrator documentation1)

Compute the hash using SHA256 and the signing key (UTF-8 encoded). The signing key is a secret value that is shared between Orchestrator and the client app. You can use any tool or library that supports SHA256 hashing. (UiPath Orchestrator documentation1)

Compare the computed signature to the value from X-UiPath-Signature HTTP header. If they match, then the request is authentic and has not been tampered with. If they do not match, then the request is invalid and should be rejected. (UiPath Orchestrator documentation1)

The UI Object Repository is a feature that allows you to store and reuse UI elements across different automation projects1. A UI Library is a type of project that contains UI elements and workflows that can be used as dependencies in other projects2. When you import a UI Library as a dependency in your current project, the UI Object Repository defined in the UI Library will automatically be available in your current project3. You can access the UI elements from the Object Repository panel in Studio and use them in your activities4. Therefore, the correct answer is C. The other options are incorrect because they do not reflect the actual behavior of the UI Object Repository and the UI Library.

A state in a State Machine is a set of actions that execute while the workflow is in a certain condition1. Each state has three components: Entry, Exit, and Transition Actions2. Entry Actions are executed when the state is entered, Exit Actions are executed when the state is exited, and Transition Actions are executed when a transition is triggered by a condition3.

Frequent business logic changes require constant updates to the automation workflow, leading to high maintenance costs and effort.

Processes that are prone to human error can be mitigated with validation mechanisms.

A high process run time doesn’t necessarily mean high maintenance—it might just need optimization.

Exception handling is a necessary part of automation and doesn’t inherently cause maintenance issues.

To minimize maintenance, RPA teams should prioritize stable processes with well-defined, predictable business logic.

✅ Reference: UiPath RPA Process Selection Guide

Understanding the Error:

The runtime execution error shown in the image is:

pgsql

CopyEdit

Message: Object reference not set to an instance of an object.

Exception Type: System.NullReferenceException

This error occurs when trying to access or modify an object that has not been initialized.

Step-by-Step Breakdown of the Issue:

What is Happening in the Workflow?

The developer is trying to assign a value to the dictionary using:

PinMapping["John"] = "1195488487"

Then, they attempt to log the count of the dictionary items:

String.Concat(PinMapping.Count, " people")

The error occurs at the Assign activity.

What Causes a NullReferenceException in a Dictionary?

If a dictionary variable is declared but not initialized, it remains Nothing (null).

Trying to access or modify a null object causes a NullReferenceException.

The dictionary should be initialized before adding key-value pairs.

Why Option B is Correct?

✅ The Dictionary was not initialized.

The error occurs because the dictionary PinMapping is not initialized before assigning values.

To fix this, the dictionary must be initialized before use:

PinMapping = New Dictionary(Of String, String)

PinMapping("John") = "1195488487"

This ensures that the dictionary is properly instantiated in memory before accessing it.

Why Other Options Are Incorrect?

❌ A. "The 'John' key was not present in the dictionary."

Incorrect because a missing key does not cause a NullReferenceException.

Instead, attempting to retrieve a missing key causes a KeyNotFoundException.

The error in the screenshot is caused by the dictionary itself being null, not a missing key.

❌ C. "The assign's set value syntax should be PinMapping["John"]."

Incorrect because the syntax used in the Assign activity is correct.

The dictionary is of type Dictionary(Of String, String), and "John" is correctly specified as a string key.

❌ D. "The assign's set value syntax should be PinMapping<"John">."

Incorrect because PinMapping<"John"> is not valid syntax in VB.NET.

The correct syntax is PinMapping("John") or PinMapping["John"] (in C# syntax).

How to Fix the Error?

✅ Solution: Initialize the Dictionary Before Using It

Before using the dictionary, add the following initialization step:

PinMapping = New Dictionary(Of String, String)

Then assign values as needed:

PinMapping("John") = "1195488487"

Final Answer and Explanation:

✅ Answer: B. The Dictionary was not initialized.

Key Takeaways:

A NullReferenceException occurs when trying to use an uninitialized dictionary.

Always initialize a dictionary before adding key-value pairs.

A missing key does not cause this error—it would result in a KeyNotFoundException.

✅ Reference:

???? UiPath Documentation – Dictionaries

???? VB.NET – Dictionary Initialization

When a transaction item throws a Business Rule Exception, it means that the item does not meet the business requirements and cannot be processed further1. Therefore, the transaction item is marked as failed and not retried, regardless of the Max # of retries setting for the queue2. However, the process does not stop and continues with the remaining transaction items in the queue3.