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.

Extracting hidden text from a PDF requires Optical Character Recognition (OCR). Unlike FullText or Native methods, which work with selectable text, OCR is capable of recognizing text in images, scanned documents, and hidden text layers.

FullText and Native work for text-based PDFs, but fail if text is embedded in images.

OCR technologies (such as Tesseract, Microsoft OCR, or OmniPage OCR) analyze and extract text from images, ensuring all content is retrieved.

UiPath provides Get OCR Text and Read PDF with OCR activities for this purpose.

✅ Reference: UiPath Official Documentation – PDF and OCR

The Tenant context in UiPath Orchestrator allows management of tenant-wide settings, licenses, and entities.

Tenant-level actions include:

Managing licenses for attended/unattended robots.

Configuring tenant-wide settings such as security policies.

Managing users, roles, and permissions across folders.

✅ Why other options are incorrect:

A (Assets & Storage Buckets): Managed at the folder level, not tenant level.

C (Test Cases & Executions): Specific to folders, not tenant-wide.

D (Folder Roles & Mixed Roles): Roles are assigned at the folder level, not tenant level.

✅ Reference: UiPath Orchestrator - Tenant vs Folder Context

The Invoke Method activity is used to add items to a list of strings. In this case, the list is declared as “Colors”. The outcome of the Invoke Method activity will be that the list “Colors” will contain an item with the value “Yellow”. This is because the TargetObject property is set to “Colors”, which is the list variable, the MethodName property is set to “Add”, which is the method of the list class, and the Parameters property is set to “Yellow”, which is the value to be added to the list. (UiPath Studio documentation1)

By default, the Timeout property in UiPath is set to 30 seconds (30000 milliseconds).

If the UI element is not found within 30 seconds, the activity throws an exception.

The Timeout can be manually adjusted in the activity’s properties.

✅ Why other options are incorrect:

A (10 seconds): UiPath does not use a 10-second default timeout.

C (60 seconds): Default is 30 seconds, but it can be extended.

D (Indefinitely): Without modification, UiPath will timeout after 30 seconds, not indefinitely.

✅ Reference: UiPath Studio - Activity Timeout Property

The listOfMonthsByQuarter variable is a String array, which means it can store multiple values of type String. Each value in the array has an index, which is a number that indicates its position in the array. The index starts from 0, so the first value has index 0, the second value has index 1, and so on. To access a specific value in the array, we can use the syntax arrayName(index). For example, listOfMonthsByQuarter(0) will return the first value in the array, which is “1”. Similarly, listOfMonthsByQuarter(2) will return the third value in the array, which is “3”. Therefore, the data type of listOfMonthsByQuarter(2) is String, and the value is “3”. References: Arrays and Variables from UiPath documentation.

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.