ExamFinch.com My Study

Study guide

13.3 Serverless and Cloud VM Robots: Cloud-Hosted Execution Options

Practice this exam

UiPath Automation Developer Professional UiPath-ADPv1

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Blueprint Map

1.1 About the UiPath-ADPv1 Exam: Format, Fees & Policies 1.2 The Exam Topics Mapped to This Guide & a Study Plan

2 Chapter 2: REFramework Architecture & State Dynamics

2.1 State Machine Architecture & The Four Core States 2.2 Configuration Management: Settings, Constants, and Assets 2.3 Transaction Types & The Dispatcher vs. Performer Architecture 2.4 Adapting REFramework: Tabular Data, Collections & Linear Processes

3 Chapter 3: REFramework Exception Handling & Recovery

3.1 BusinessRuleException vs. System.Exception Handling Patterns 3.2 Retry Mechanisms: Queue Retries vs. REFramework MaxRetryNumber 3.3 Consecutive System Exceptions & Graceful Process Termination

4 Chapter 4: State Machines, Custom Log Fields & REFramework Testing

4.1 Building State Machine Projects in Studio 4.2 Logging Levels, Robot Logs & Custom Log Fields in REFramework 4.3 Testing a REFramework Project With and Without Orchestrator Queues

5 Chapter 5: LINQ Queries & DataTable Operations

5.1 LINQ Essentials for Collections & Filtering 5.2 Advanced DataTable Querying with LINQ 5.3 In-Memory DataTable Transformations & Column Operations

6 Chapter 6: Regex, DateTime, JSON & Invoke Activities

6.1 Regular Expressions & Text Parsing for Automation 6.2 DateTime Formatting, Timezone Conversions & TimeSpan Calculations 6.3 JSON Parsing, JSONPath & Serialization with Newtonsoft.Json 6.4 Invoke Method & Invoke Code Activities 6.5 Data Referencing in Invokes: DataTable, List & Dictionary Arguments

7 Chapter 7: Modern UI Automation & Unified Targeting

7.1 Modern Design Experience & The Unified Target Concept 7.2 Anchors, Relative Elements & UI Automation Activities 7.3 Dynamic Selectors, Variables & Wildcards in Selectors

8 Chapter 8: Object Repository, Computer Vision & Remote Runtime

8.1 Object Repository & UI Descriptor Libraries 8.2 AI Computer Vision for Unattended & Remote Interfaces 8.3 Automation in Virtual Environments & UiPath Remote Runtime

9 Chapter 9: Advanced UI Automation: Browser Modes, Agentic UI & macOS

9.1 Browser Automation with the WebDriver Protocol 9.2 Agentic UI Automation: ScreenPlay, Semantic Activities & Healing Agent 9.3 macOS Automation: Native Apps, Office Apps & AppleScript

10 Chapter 10: Advanced Control Flow & Exception Architecture

10.1 Flowcharts, Sequences & Parallel Control Flow Patterns 10.2 Global Exception Handler Architecture & ErrorAction Directives 10.3 TryCatch, Retry Scope & Custom Exception Architectures

11 Chapter 11: Orchestrator Queues & Transaction Management

11.1 Queue Architecture, SpecificContent & Transaction Lifecycles 11.2 Queue Items SLA, Postpone, Deadlines & Priority Scheduling 11.3 Bulk Operations, Transaction Status Updates & Queue Triggers

12 Chapter 12: Orchestrator Tenant & Folder Entities

12.1 Asset Types, Per-Robot Assets & External Credential Stores 12.2 Modern Folder Hierarchy, User/Robot Assignment & Permissions 12.3 Storage Buckets, Webhooks & Environment Promotion 12.4 Orchestrator Tags: Labels, Properties & Governance

13 Chapter 13: Unattended Execution, API Triggers & Cloud Robots

13.1 Unattended Job Execution: Folders, Priorities, Background vs. Foreground & Runtimes 13.2 API Triggers: Starting Jobs from External Systems over HTTP 13.3 Serverless and Cloud VM Robots: Cloud-Hosted Execution Options

14 Chapter 14: Monitoring, Recording & Solutions Management

14.1 Orchestrator Monitoring, Trigger Alerts & Job Health 14.2 Job and Transaction Recording: Troubleshooting Faulted Unattended Jobs 14.3 Solutions Management: Packaging and Deploying Automations with Their Resources

15 Chapter 15: Debugging, Remote Debugging & Profiling

15.1 Studio Debugging Tools: Breakpoints, Panels & Execution Control 15.2 Remote Debugging: Remote Machine and Unattended Robot Connections 15.3 Profile Execution: Finding Performance Bottlenecks in Studio

16 Chapter 16: RPA Testing & Test Suite

16.1 UiPath Test Suite Overview, Test Cases & Given-When-Then Structure 16.2 Data-Driven Testing, Test Verification Activities & Mock Activities 16.3 CI/CD Pipelines with uipcli & Test Manager Traceability

17 Chapter 17: Long-Running Workflows, Action Center & Apps

17.1 Long-Running Workflows: Persistence, Suspend and Resume 17.2 Action Center & Human-in-the-Loop Orchestration 17.3 UiPath Apps: Action Apps, Automations & Integration Service

18 Chapter 18: Trigger-Based Attended Automation & Callouts

18.1 Trigger-Based Attended Automation: Forms, Triggers & Global Variables 18.2 Running Local Triggers & the Event Inspection Tool 18.3 Callouts & Forms for Attended Guidance

19 Chapter 19: UiPath Assistant & Robot Sessions

19.1 UiPath Assistant: Automations, Reminders, Widgets & Configuration 19.2 Robot Session (Picture in Picture): Child Session vs. Virtual Desktop

20 Chapter 20: Autopilot for Developers & Autopilot for Everyone

20.1 Autopilot for Developers: AI Assistance in Studio and Studio Web 20.2 Autopilot for Everyone: Chat, Automations & Clipboard AI

21 Chapter 21: API Automation & Integration Service

21.1 Integration Service: Connectors, Connections & Connector Activities 21.2 API Workflows in Studio Web 21.3 HTTP Requests: Web APIs, the Orchestrator API & Connector Requests 21.4 Connector Builder: Custom Integration Service Connectors 21.5 Integration Service Event Triggers: Connected and Disconnected 21.6 GenAI Activities: Generative AI Inside Workflows

22 Chapter 22: Data Service, Context Grounding & Coded Workflows

22.1 Data Fabric (Data Service) Entities: Modeling Business Data 22.2 Data Fabric Activities and the Platform Connector 22.3 Context Grounding: Retrieval-Augmented Generation with Company Data 22.4 Coded Automations: Structure, Arguments & Invoking Workflows 22.5 Coded Automation Services: Orchestrator, UI Automation, Microsoft 365 & Custom Services

23 Chapter 23: Integrated Scenario Practice

23.1 Integrated Scenario Practice: Designing an End-to-End Solution

13.3 Serverless and Cloud VM Robots: Cloud-Hosted Execution Options

Key Takeaways Explain This Topic AI

Cloud robots - Serverless run background, cross-platform processes with no machine to manage.

Serverless machine sizes are Small 1 GB, Standard 2 GB, Medium 4 GB, and Large 10 GB; automatic selection uses Medium for remote debugging and Standard for UI Automation or Document Understanding.

Cloud robots - VM are UiPath-managed Windows machines in manual or automatic pools, suitable for foreground UI automation.

Automatic pool profiles are Balanced (30 minutes), Fast (60 minutes), and Always on; extra VM runtimes are for background processes only.

Choose serverless for API and data work, and a VM or your own machine for desktop applications.

Last updated: September 2026

13.3 Serverless and Cloud VM Robots: Cloud-Hosted Execution Options

Core Concept: Automation Cloud can run unattended jobs on infrastructure that UiPath hosts. Cloud robots - Serverless run background, cross-platform processes on demand with no machine to manage. Cloud robots - VM give you Windows virtual machines managed by UiPath, for automations that need a desktop. The exam description lists both under Orchestrator.

  • Cloud Robots - Serverless
  • What runs on serverless

Background, cross-platform processes only. Processes that need a Windows desktop, or Windows-only activities, cannot run there. (UiPath notes a known issue where foreground jobs with UI Automation are interpreted as background jobs.)

Jobs use the Cloud - Serverless runtime (and a Testing runtime type for test automation).

Machine sizes

When you create a serverless machine you choose the size used for its jobs:

  • Size Memory
  • Small 1 GB
  • Standard 2 GB
  • Medium 4 GB
  • Large 10 GB

With automatic size selection, Orchestrator chooses based on the job: remote debugging jobs use Medium , processes that use UI Automation or Document Understanding use Standard , and other processes use Small .

Why teams use it

No robot installation, patching, or machine connection.

Capacity scales with demand, so API-driven and queue-driven background work starts quickly.

Studio can remote debug on serverless robots.

Guard rails

On the Community plan, triggers that use a Cloud - Serverless runtime automatically get execution-based trigger disabling (disable after 10 consecutive failed executions, grace period 0 days), shown as read-only.

  • Cloud Robots - VM
  • What you get

Windows virtual machines hosted and maintained by UiPath, connected to Orchestrator automatically.

You create a Cloud robot VM pool and choose its image, such as Windows Server 2019 or a Windows desktop image, and its size.

Pool types

  • Pool setting Behavior
  • Manual You decide how many VMs exist and when they run
  • Automatic Orchestrator starts and stops VMs based on pending jobs, within the limits you set
  • Availability profiles (automatic pools)
  • Profile Behavior
  • Balanced VMs stay available for 30 minutes after the last job before shutting down
  • Fast VMs stay available for 60 minutes , trading cost for quicker starts
  • Always VMs stay on, for the fastest pickup
  • Runtimes

A cloud VM runs foreground jobs through its unattended runtime. Additional runtimes can be added only for background processes.

Setting Up Serverless Execution

In Tenant > Machines , add a machine of type Cloud robots - Serverless and choose its size or automatic selection.

Assign that machine to the folder that holds the process.

Make sure the process is a background, cross-platform project; check this in Studio before publishing.

Start a job or configure a trigger that uses the Cloud - Serverless runtime type.

Review the first runs in the Jobs page and adjust the machine size if jobs are slow or run out of memory.

Because nothing is installed on your side, serverless jobs cannot read files from a local drive or a network share. Keep inputs in storage buckets, queues, or cloud services instead.

Choosing Where a Process Runs

  • Requirement Serverless Cloud VM Your own machine
  • Needs a Windows desktop or Windows-only activities No Yes Yes

Must reach systems inside your network Only through services exposed to it Possible with VPN or peering set up by your team Yes

  • No infrastructure to manage Yes UiPath manages the VM No
  • Fast start for short background jobs Yes Depends on availability profile Depends on your setup
  • Legacy desktop apps installed locally No You can install them Yes
  • Exam-Style Scenarios

Scenario 1: A process calls three REST APIs, transforms JSON, and writes a result to a storage bucket. It is triggered by an API trigger dozens of times a day. Best fit: serverless; it is background and cross-platform.

Scenario 2: A process fills forms in a Windows desktop ERP client. Best fit: Cloud VM or your own unattended machine. Serverless cannot host desktop UI automation.

Scenario 3: Nightly batches should cost as little as possible, and a few minutes of start-up time is acceptable. Best fit: an automatic VM pool with the Balanced profile, or serverless if the process is background and cross-platform.

Scenario 4: Jobs sometimes fail with out-of-memory errors on serverless. Fix: choose a larger machine size, such as Medium (4 GB) or Large (10 GB), instead of relying on the automatic Small size.

Recording and Troubleshooting

Video recording of jobs is available for Cloud robots - Serverless, which helps investigate failures when you cannot sign in to the machine.

Remote debugging with a serverless robot uses a Medium machine automatically, so the debug session has enough memory.

Use Schedule ending of job execution and job alerts on triggers to catch stuck jobs.

Common Traps

Serverless is not a Windows desktop. Foreground or Windows-compatibility processes need a VM or your own machine.

Automatic machine size is picked per job type; it does not grow when a job runs out of memory.

Additional runtimes on a cloud VM are for background processes only.

Serverless and Cloud VM robots are Automation Cloud offerings, not part of a standalone on-premises Orchestrator.