UiPath-ADPv1 Attended Automation Practice Question
When a robot is configured for attended automation, what happens to the robot's session if the user logs off while the process is running?
⚠ Common exam trap
Candidates often assume the robot will continue running in the background or pause. They fail to realize that attended robots are strictly bound to the user session.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The process is terminated immediately
In an attended configuration, the robot runs within the active user session. If the user logs off, the session is terminated, and consequently, the robot process is immediately killed. Unlike unattended robots that run in persistent, session-independent environments, attended robots are tethered to the user's login. This behavior is intentional, ensuring that the robot does not perform actions without the active user present to supervise, complying with security requirements.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The process switches to the background and continues
Why it's wrong here
Attended processes are not designed to move to the background or detach from the user session. They rely on the active user session to interact with UI applications. If that session is terminated, there is no desktop for the robot to interact with, and the process will naturally fail immediately.
- ✓
The process is terminated immediately
Why this is correct
Because the attended robot operates within the user's active Windows session, logging off destroys the session environment. Without a valid session, the robot cannot maintain its UI connections or run its activities, leading to an immediate termination of the process by the operating system and the Robot Service.
- ✗
The process pauses and resumes when the user logs back in
Why it's wrong here
Windows sessions do not support 'pausing' and 'resuming' complex automation processes in this manner. When a user logs off, all running applications are closed. The robot process is treated as a standard application and is terminated along with everything else in the session, preventing any possibility of automatic resumption later.
- ✗
The process continues until it hits the next UI interaction
Why it's wrong here
Once the user logs off, the graphical shell disappears, meaning the robot's UI interactions will fail instantly even before it reaches the next activity. The process doesn't wait for a UI interaction to fail; it is killed by the OS as part of the session teardown process at the logout.
About these practice questions
This UiPath-ADPv1 question is part of Courseiva's 276-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official UiPath exam blueprint
This UiPath-ADPv1 practice question is part of Courseiva's free UiPath certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the UiPath-ADPv1 exam.