UiPath-ADPv1 Attended Automation Practice Question
Exhibit
{
"RobotSettings": {
"AllowRemoteControl": false,
"LogToOrchestrator": "Information",
"UserInteractionTimeout": "00:00:30"
}
}Refer to the exhibit. An attended robot stops execution precisely after 30 seconds while waiting for user input in a customized form. What is the most likely cause based on the provided configuration?
⚠ Common exam trap
Candidates often confuse application-level timeouts with specific UI interaction properties, mistakenly attributing the stop to network lag instead of the explicit UserInteractionTimeout setting.
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 UserInteractionTimeout setting is forcing the process to terminate
The 'UserInteractionTimeout' property is set to 30 seconds, which acts as a hard limit for how long the robot will wait for a response during an attended task. If the user does not provide input within this timeframe, the activity throws a timeout exception. This setting is important for ensuring that robots do not block user workstations indefinitely during long-running attended processes.
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 robot is in an offline state and cannot communicate with Orchestrator
Why it's wrong here
If the robot were offline, it would fail to start or report a connectivity error immediately. The timeout behavior specifically indicates that the robot is active and waiting for a signal, but the configured duration for the interaction has been exceeded, causing the process to fail.
- ✓
The UserInteractionTimeout setting is forcing the process to terminate
Why this is correct
The explicit 'UserInteractionTimeout' configuration of 30 seconds directly controls the maximum time the robot waits for human input. When this limit is reached, the activity stops execution to prevent the robot from hanging, confirming this is the root cause of the observed termination behavior in the workflow.
- ✗
The LogToOrchestrator level is set to Information, causing a data overflow
Why it's wrong here
Setting the log level to 'Information' controls the verbosity of logs sent to Orchestrator, but it does not affect the execution timing of activities or force a timeout. This setting impacts server load and log storage, not the runtime behavior of the robot's interaction with the user.
- ✗
The AllowRemoteControl property is set to false, preventing user input
Why it's wrong here
The 'AllowRemoteControl' setting determines if an administrator can take control of the robot session remotely. It does not govern the local input timeout duration of activities. Disabling this is a security measure and has no impact on the time allotted for local user interaction in workflows.
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.