UiPath-ADPv1 Orchestrator Advanced Usage Practice Test 2 — 15 Questions

Question 1

A developer needs to configure a queue to automatically retry failed transactions a maximum of three times with a 10-minute delay between attempts. Which TWO queue settings must be configured? (Choose two.)

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Auto retry. To enable automatic retries with a maximum count, you must enable 'Auto retry' and set 'Max # of retries' to 3. The 'Retry interval' is not a queue setting, so the 10-minute delay must be handled in the automation logic or via a time trigger. 'Unique reference' and 'SLA' do not affect retry behavior. Thus, the two required queue settings are 'Auto retry' and 'Max # of retries'.

Answer

Unique reference

Answer

SLA

Answer

Retry interval

Question 2

You are using Orchestrator Triggers to schedule a process that must run every weekday at 6:00 AM. The process should not run on public holidays. The company observes holidays that vary each year. Which approach should you use to meet this requirement?

Accepted Answer

Create a time-based trigger with a cron expression that runs Monday through Friday at 6:00 AM, and add a holiday calendar to the trigger.. Orchestrator's time-based triggers with cron expressions allow precise scheduling, and the holiday calendar feature lets you exclude specific dates. By combining a Monday-Friday 6:00 AM cron with a holiday calendar, you ensure the process runs only on business days and skips holidays automatically, even as holiday dates change annually.

Answer

Create a queue-based trigger that adds items only on weekdays, and set a maximum number of items to process per day.

Answer

Create a time-based trigger that runs daily at 6:00 AM, and use a conditional 'If' activity in the process to check if the current date is a holiday.

Answer

Create a time-based trigger with a cron expression that runs Monday through Friday at 6:00 AM, and manually disable the trigger on holidays.

Question 3

Your company uses Orchestrator with multiple modern folders. A developer needs to run a process that must access a credential asset stored in a different folder named 'SharedAssets'. The developer's robot is provisioned only in the 'Finance' folder. What is the most appropriate way to grant access to the credential without duplicating it?

Accepted Answer

Use a tenant-level credential asset instead of a folder-level one.. Tenant-level assets are designed to be shared across all folders in Orchestrator, making them ideal for credentials needed by multiple folders. By converting the folder-level credential to a tenant-level asset, you provide access to the Finance robot without duplicating the credential or moving it from its original folder. This approach maintains a single source of truth and simplifies management.

Answer

Create a new credential asset in the Finance folder with the same values.

Answer

Move the credential asset to the Finance folder.

Answer

Assign the robot to the SharedAssets folder as well.

Question 4

Refer to the exhibit. A user is granted this specific policy in Orchestrator. When attempting to start a job for a process in Folder 123, the user receives an 'Unauthorized' error. What is the most likely cause?

Accepted Answer

The user is missing the 'Folders.View' permission.. The policy grants permission to create a job, but it lacks the necessary 'View' permission on the process itself or the folder. Orchestrator's security model requires users to have read access to the resource (process) to initiate an action against it. Without the 'Folders.View' or 'Processes.View' permissions, the Create action fails despite having explicit job creation rights defined in the policy.

Answer

The policy requires a 'Jobs.Edit' permission.

Answer

The user must have 'Administrator' access to the folder.

Answer

The policy syntax is invalid due to the trailing asterisk.

Question 5

When implementing a high-availability Orchestrator deployment, what is the primary consideration for handling the 'Orchestrator Database' during a failover event?

Accepted Answer

Use SQL Always On Availability Groups for database replication.. In a high-availability environment, the database is the single source of truth. Orchestrator nodes are stateless, but the SQL database holds all transaction logs, queue states, and assets. Ensuring consistent replication and minimal recovery time objectives (RTO) for the SQL layer is paramount. If the database is not synchronized, the application nodes will fail to recover, regardless of how many Orchestrator nodes are active in the load balancer pool.

Answer

The SQL database must be deployed on the same server as Orchestrator.

Answer

Disable the Orchestrator load balancer during database maintenance.

Answer

Change the connection string on every robot individually.

Question 6

Which Orchestrator feature is best suited for sharing sensitive credentials between multiple processes without exposing them in plain text or hardcoding them in workflows?

Accepted Answer

Using Orchestrator Assets with the 'Credential' type.. Assets, specifically 'Credential' type assets, provide a secure, encrypted mechanism to store sensitive information in Orchestrator. When accessed by a robot, the credentials are decrypted on-the-fly and only at runtime. This practice adheres to the security principle of abstraction, ensuring that developers never interact with actual passwords, and administrators can rotate them centrally without modifying or redeploying any automation workflows across the enterprise.

Answer

Storing the credentials in a local text file.

Answer

Embedding the password in a custom configuration JSON.

Answer

Passing credentials as arguments at runtime.

Question 7

Which THREE actions are required to successfully enable and utilize 'Modern Folders' in a fresh Orchestrator installation?

Accepted Answer

Enable 'Modern Folders' in the Orchestrator Tenant Settings.. Modern Folders represent a paradigm shift in how Orchestrator manages resources, providing hierarchical, multi-tenant-like isolation with simplified user management. Setting them up correctly requires a sequence of actions: enabling the feature in settings, creating the folder structure, and then mapping users or groups with appropriate roles. This setup is crucial for delegated administration and ensuring that robots only have access to the specific resources they need.

Answer

Restart all active Robots in the tenant.

Answer

Manually create an environment for each folder.

Question 8

An administrator wants to ensure that a specific process only runs during non-business hours. How should this be configured in Orchestrator?

Accepted Answer

Create a 'Time Trigger' with the desired schedule.. Orchestrator Triggers provide a comprehensive scheduling engine that allows for time-based, queue-based, or event-based execution. By configuring a 'Time Trigger' with a specific Cron expression or the built-in UI, administrators can precisely define when a robot should begin executing a task. This capability is essential for ensuring that intensive processes do not impact daytime system performance while maintaining full control over the execution window for reporting and compliance.

Answer

Use a 'Delay' activity at the start of the workflow.

Answer

Configure the Robot machine's OS Task Scheduler.

Answer

Ask the user to manually trigger the job.

Question 9

When migrating a process from a development environment to a production environment using Orchestrator, what is the best practice for managing environment-specific configurations?

Accepted Answer

Use Orchestrator Assets to store environment-specific values.. The 'Assets' and 'Per-Folder' settings are the industry-standard way to manage configuration differences between environments. By using Orchestrator Assets, you can keep the process code identical across environments (Dev, Test, Prod) while injecting different values, such as database connection strings or API endpoints, at runtime. This practice ensures that code promotion is clean and minimizes the risk of human error during deployment, as no manual modifications to the code are needed.

Answer

Hardcode the configuration values in the workflow.

Answer

Create separate versions of the workflow for each environment.

Answer

Store configurations in a plain-text file in the project folder.

Question 10

Which mechanism does Orchestrator use to ensure that the 'Queue Item' processing is handled in a First-In-First-Out (FIFO) manner across multiple robots?

Accepted Answer

Orchestrator uses a transactional locking mechanism.. Orchestrator Queues are intrinsically designed to manage work distribution via a transactional locking mechanism. When a robot requests a new item, Orchestrator provides the oldest item in the queue that is not currently being processed. This transactional model ensures that items are processed in order and that no two robots pick up the same item, providing the concurrency control necessary for reliable, large-scale, and orderly business process automation.

Answer

The queue items are automatically sorted by the robot's clock.

Answer

The robots must be synchronized using a shared local file.

Answer

FIFO is only supported if there is exactly one robot.

Question 11

How can an Orchestrator administrator identify the root cause of a 'System Exception' occurring during the execution of a process?

Accepted Answer

Navigate to the 'Jobs' tab and view the 'Error Details' column.. Orchestrator provides detailed job logs and error reporting for every execution. By reviewing the 'Job Details' page, an administrator can see the exact time, activity, and error message associated with the exception. This visibility is crucial for fast incident resolution, as it allows developers to pinpoint exactly where the workflow failed, review the input data that caused the failure, and determine whether a code fix or an infrastructure change is required.

Answer

Check the local Windows Event Viewer on the robot machine.

Answer

Rerun the process until it succeeds.

Answer

Reinstall the UiPath Robot service.

Question 12

Refer to the exhibit. What is the impact of this Orchestrator policy on a folder containing 10 available robots?

Accepted Answer

Orchestrator will queue the 6th job until a slot becomes free.. This policy sets a concurrency limit on the number of jobs that can run simultaneously within a single folder. Even if there are 10 robots available, Orchestrator will restrict the total number of active jobs to 5. This is a powerful mechanism for controlling resource consumption and preventing a single process from monopolizing all available infrastructure, ensuring that other critical processes have the resources needed to execute as required.

Answer

Only 5 robots will be allowed to connect to the folder.

Answer

The folder will automatically provision 5 additional robots.

Answer

The 6th job will automatically fail with a 'Resource Limit' error.

Question 13

Which Orchestrator feature should be used to monitor the long-term health and performance of unattended robot processes?

Accepted Answer

The Orchestrator Monitoring dashboards.. The 'Monitoring' tab in Orchestrator provides high-level dashboards and granular metrics regarding robot performance, process success rates, and infrastructure utilization. By tracking these metrics over time, administrators can identify trends, such as increasing execution times or high failure rates, which indicate that a process or robot needs optimization. This data-driven approach is essential for maintaining a high-performing automation platform and proactively addressing issues before they impact business operations.

Answer

Individual machine performance logs in Windows.

Answer

Daily manual checks of every robot's status.

Answer

Studio debugger execution reports.

Question 14

You need to automate the deployment of processes to multiple environments while ensuring that different production environments have distinct connection strings stored securely. Which Orchestrator feature should you utilize to manage these configurations efficiently?

Accepted Answer

Utilize Orchestrator Assets with Per-Folder scope.. Assets, specifically Per-Robot Assets or Folder-level Assets, are the standard mechanism for decoupling environment-specific configuration from the automation code. By defining assets within Orchestrator, developers can inject values like connection strings, URLs, or API keys at runtime without modifying the underlying process code. This separation of configuration from logic is critical for scaling enterprise deployments across Dev, UAT, and Production tiers effectively.

Answer

Use Environment Variables in the system OS.

Answer

Hardcode the connection strings in the workflow.

Answer

Configure global settings in the Orchestrator host.

Question 15

A production process is failing because the unattended robot cannot access an Orchestrator Queue. Which TWO of the following configurations must be verified to ensure the Robot has the necessary permissions?

Accepted Answer

The Robot account is assigned a Role with 'Queues' permissions in the specific Folder.. To successfully interact with Queues, a robot requires both the appropriate Folder-level permissions to see the Queue and the correct Role-based Access Control (RBAC) assigned to the Robot or Account. Verifying the Folder permissions ensures the robot is in the correct scope, while the Role confirms it has the 'Queues' permission set to read/write/edit, preventing runtime unauthorized access exceptions.

Answer

The Robot machine is joined to the domain.

Answer

The Robot is configured as a 'Development' type.

Answer

The Queue encryption is set to 'Standard'.