UiPath-ASAPv1 Exam Study Guide: The Ultimate 2026 Practice Test

One of the responsibilities of a Solution Architect is to identify and document the accesses needed for themselves, the developers and the robots to perform the automation tasks. This includes the applications, systems, databases, APIs, credentials, permissions, roles, and security policies that are required for the automation solution. By identifying and documenting the accesses needed, the Solution Architect can avoid access delays that may impact the development, testing, and deployment of the automation solution. The Solution Architect should also communicate and coordinate with the Project Manager, the IT team, and the business stakeholders to ensure that the access requests are approved and granted in a timely manner.  References :  Roles of a Solution Architect in Automation, RPA Setting ,  Automation Suite - Deployment architecture , [UiPath Automation Solution Architect Learning Plan].

Learn more

According to the UiPath documentation and the UiPath Academy course, there are four types of feeds that can be used to deploy a package in Orchestrator:

Tenant feed : This is the default feed for all tenants in Orchestrator. It is hosted on the Orchestrator server and can store both processes and libraries.  It can be accessed by all users within the tenant 1 2 .

Folder feed : This is a feed that can be configured for a specific folder in Orchestrator. It can store only processes and can be accessed only by users within the folder.  It can be useful for isolating packages for different environments or projects 1 3 .

Personal workspace feed : This is a feed that can be configured for a personal workspace in Orchestrator. It can store only processes and can be accessed only by the user who owns the workspace.  It can be useful for testing and debugging packages before publishing them to other feeds 1 4 .

Custom feed : This is a feed that can be configured by adding an external source, such as Azure DevOps, Artifactory, MyGet, etc. It can store both processes and libraries and can be accessed by users who have the credentials for the external source.  It can be useful for integrating with third-party tools or services 1  .

References :

Automation Ops - Orchestrator Feeds - UiPath Documentation Portal 1

Queues and Transactions - UiPath Documentation Portal 2

Folders - UiPath Documentation Portal 3

Personal Workspaces - UiPath Documentation Portal 4

External Feed For Packages - UiPath Community Forum

A long-running workflow is a type of automation process that requires logical fragmentation or human intervention, such as invoice processing or performance reviews 1 .  Long-running workflows are designed as Orchestration Processes in Studio, using the Persistence and Intelligent.OCR package 2 .  This package contains activities that enable the workflow to suspend and resume execution based on certain conditions, such as waiting for a job, a queue item, a form task, or an external task to be completed 1 .  These activities are called persistence points, and they create checkpoints in the workflow where the process state is saved and restored 2 .  In order for the persistence points to work properly, all the variables used in the scope of a long-running activity must be serializable, meaning that they can be converted into a format that can be stored and retrieved 3 .  Non-serializable variables, such as browser or application objects, cannot be used in long-running workflows, as they would cause errors or inconsistencies 3 .

References :  1 :  Orchestrator - Working With Long-running Workflows   2 :  Action Center - Designing long-running workflows   3 :  Best practice long running processes - UiPath Community Forum