RPA (UiPath & Automation Anywhere) test (Intermediate)

Sample questions

5 sample questions from the RPA (UiPath & Automation Anywhere) test, with the answers. Samples are taken out of the live test, so you will not meet these when you sit it.

1. A bug was introduced in a UiPath workflow after multiple versions were created. What is the correct strategy to find and fix the bug using UiPath's versioning features?

   1. Edit the current version of the workflow directly without checking the version history.
   2. Deploy the workflow to UiPath Orchestrator and use the dashboard to monitor and debug the issue.
   3. Ignore the version history and manually search for the bug in the workflow.
   4. Use the version history in UiPath Studio to identify the change that introduced the bug and roll back to a stable version.

   Answer: D. Use the version history in UiPath Studio to identify the change that introduced the bug and roll back to a stable version.

   UiPath Studio provides version history for workflows, allowing developers to identify when a bug was introduced and roll back to a stable version. This ensures that the workflow can be fixed without losing prior functionality. Other options are incorrect because they do not directly relate to UiPath's versioning strategies or are not standard practices for fixing bugs in workflows.

2. Which of the following is the correct approach to handle a non-critical error in a UiPath activity where the workflow should continue execution?

   1. Use 'Throw' to propagate the error to the parent workflow.
   2. Use 'Retry Scope' to retry the activity indefinitely until success.
   3. Use 'Try Catch' to immediately stop the workflow and log the error.
   4. Use 'ContinueOnError' to allow the workflow to proceed and handle the error later.

   Answer: D. Use 'ContinueOnError' to allow the workflow to proceed and handle the error later.

   When using the 'ContinueOnError' property in UiPath, it allows the workflow to continue executing subsequent activities even if an error occurs, providing a way to handle errors at a later stage. This is appropriate in scenarios where the error is not critical to the overall process and can be addressed later. The other options are either incorrect or not directly related to the 'ContinueOnError' property.

3. A developer is encountering a bug in their UiPath automation where the workflow is not executing conditional logic properly. The workflow is currently using a Sequence workflow. What should they do to fix this issue?

   1. Use a Global Exception Handler activity in the Sequence workflow.
   2. Add a 'Try Catch' activity to the Sequence workflow.
   3. Use a Flowchart workflow instead of a Sequence workflow.
   4. Use a State Machine workflow instead of a Sequence workflow.

   Answer: C. Use a Flowchart workflow instead of a Sequence workflow.

   A Sequence workflow executes steps linearly, one after another, without any branching or decision-making. This can cause issues if there are conditional branches or multiple paths of execution, as the Sequence workflow does not support such logic. A Flowchart workflow, on the other hand, is designed to handle branching logic and decision points, making it the correct choice for scenarios where conditional execution is needed.

4. Which of the following best describes the correct approach to handling business and system exceptions in RPA workflows?

   1. Business exceptions should not be retried, while system exceptions should be retried with a limited number of attempts.
   2. Both business and system exceptions should be retried with a limited number of attempts.
   3. System exceptions should not be retried, while business exceptions should be retried with a limited number of attempts.
   4. Business exceptions should be retried indefinitely, while system exceptions should be ignored.

   Answer: A. Business exceptions should not be retried, while system exceptions should be retried with a limited number of attempts.

   Business exceptions typically involve invalid data or rule-based errors that cannot be resolved by simply retrying the process. These should be logged and escalated to a human for resolution. System exceptions, on the other hand, are technical failures (e.g., element not found, timeout) that may be resolved by retrying the process a limited number of times before escalating.

5. A task in Automation Anywhere is failing because it is not waiting for a dependent task to complete. What is the correct configuration for resolving this issue?

   1. The task is configured to start immediately, regardless of the dependent task's status.
   2. The task is configured to wait for the dependent task to complete before starting.
   3. The task is configured to run in parallel with the dependent task.
   4. The task is configured to run only if the dependent task has failed.

   Answer: B. The task is configured to wait for the dependent task to complete before starting.

   In Automation Anywhere, if a task is dependent on another task, it is configured to wait for the dependent task to complete before it starts. This ensures that the dependent task is fully executed before the dependent task begins. If a task is not configured properly, it may start before the dependent task has completed, leading to errors or incomplete processing. The other options do not accurately describe the behavior of task dependencies in Automation Anywhere.