Remote Debugging Flashcards
What are the types of connections to connect to the remote robot?
Choose two of the options that apply
Establish a TCP/IP connection to the robot on the remote machine.
Connect to an unattended robot in the same tenant using Orchestrator.
Connect to an attended robot in the same tenant using Orchestrator.
Connect to an unattended robot in the different tenant using Orchestrator.
Establish a TCP/IP connection to the robot on the remote machine.
Connect to an unattended robot in the same tenant using Orchestrator.
Review question: Where does changing a variable in the Immediate Panel reflect?
Choose the three options that apply
The Output panel.
The Locals panel.
Further execution in debug mode of the workflow.
The execution of the workflow at runtime.
The Watch panel.
The Locals panel.
Further execution in debug mode of the workflow.
The Watch panel.
What are some of the main prerequisites to establish an unattended robot connection?
Choose the three options that apply
The unattended robot is configured and the machine has one of the following runtime licenses available: Unattended or NonProduction.
The unattended robot is configured and the machine has one of the following runtime licenses available: Unattended, NonProduction, Testing.
Studio and the target robot are connected to the same Orchestrator tenant.
For debugging foreground processes, the option Run foreground automations is enabled for the robot in Orchestrator.
Studio and the target robot are connected to any of the Orchestrator tenants.
The unattended robot is configured and the machine has one of the following runtime licenses available: Unattended, NonProduction, Testing.
Studio and the target robot are connected to the same Orchestrator tenant.
For debugging foreground processes, the option Run foreground automations is enabled for the robot in Orchestrator.
Remote debugging enables you to ________?
Choose one of the options below
Run and debug attended processes on robots deployed to remote machines, except Linux robots.
Run and debug attended and unattended processes on robots deployed to remote machines, including Linux robots that can run cross-platform projects.
Run and debug unattended processes on robots deployed to remote machines, including Linux robots that can run cross-platform projects.
Run and debug attended processes on robots deployed to remote machines, including Linux robots that can run cross-platform projects.
Run and debug attended and unattended processes on robots deployed to remote machines, including Linux robots that can run cross-platform projects.
If interactive authentication is enforced in Orchestrator and you want to run or debug an unattended process, then what conditions should the remote robot meet? ?
Choose one of the options below
1
Any one of the following:
- Connected to Orchestrator using interactive sign-in.
- Connected using the machine key and a user is also signed in from the Assistant.
- Connected using the machine key, no user is signed in from the Assistant, and a troubleshooting session is enabled in Orchestrator for the machine from Tenant > Robots > Unattended sessions.
2
The Enforce Check-In before Publish is enabled from the design settings.
3
All of the following :
- Connected to Orchestrator using interactive sign-in.
- Connected using the machine key and a user is also signed in from the Assistant.
- Connected using the machine key, no user is signed in from the Assistant, and a troubleshooting session is enabled in Orchestrator for the machine from Tenant > Robots > Unattended sessions.
4
Troubleshooting session is enabled in Orchestrator for the machine from Tenant > Robots > Unattended sessions.
1
Any one of the following:
- Connected to Orchestrator using interactive sign-in.
- Connected using the machine key and a user is also signed in from the Assistant.
- Connected using the machine key, no user is signed in from the Assistant, and a troubleshooting session is enabled in Orchestrator for the machine from Tenant > Robots > Unattended sessions.
